Aleks-Daniel Jakimenko-Aleksejev

While we are discussing this to death, here's [the plan](https://irclog.perlgeek.de/perl6/2017-09-01#i_15103550): boldly document important bugs. Here's [an example of a bug that needs to be mentioned](https://github.com/perl6/doc/issues/1474). There are more than 1500...

Well, there's `SEVERE` tag that may be used for that. See [RT](https://fail.rakudo.party/t/SEVERE) and [GH](https://github.com/rakudo/rakudo/issues?q=is%3Aopen+is%3Aissue+label%3Asevere). But that tag is not being used consistently (IIRC I'm the only one using it), so...

So basically a way to write a snippet that will eventually fail when you run xtest and the bug is fixed? @coke what do you think?

OK, while this change indeed fixes the bug mentioned in the ticket, I don't think it can be merged as is. It seems that it somewhat breaks the live update...

Not completely useless, but it does mean that you have to manage indexes yourself. On Thu, 6 Nov 2025, 10:40 Jonas Strassel, ***@***.***> wrote: > *boredland* left a comment (drizzle-team/drizzle-orm#2976)...

The problem is not in the error message, it's just that this works: ```bash echo "foo" | perl6 -ne 'say "$_"' # foo ``` But this doesn't: ```bash echo "foo"...

First of all, a commit didn't fix it because it failed to build: ``` #15 [ 9/11] RUN zef install --force --/test --deps-only . #15 6.335 ===> Searching for missing...

There's no box for building, it's all in GitHub actions. You can try changing the dockerfile. On Sun, 17 Aug 2025, 13:47 Elizabeth Mattijsen, ***@***.***> wrote: > *lizmat* left a...

@lizmat yep, you did everything right, thank you! Committing to the main branch results in restarting all the bots (and they come back with a random delay). For bots that...

@lizmat I have restarted the bots manually, and they came back online… but really they need to crash when “connection reset by peer” happens instead of just hanging.