[00:32] *** leah2 left
[00:32] *** leah2 joined
[00:50] *** mehbark joined
[01:06] *** hulk joined
[01:07] *** kylese left
[02:13] *** acidsys left
[02:13] *** acidsys joined
[02:15] *** hulk left
[02:15] *** kylese joined
[03:11] <[Coke]> getting the "too many open files" using rak. try to use ulimit -n <x> on my new ubuntu box, and get: ulimit: open files: cannot modify limit: Operation not permitted

[03:12] <[Coke]> Have done a bunch of googling, everything I've tried so far gives the same error. Any thoughts?

[03:14] <[Coke]> lizmat: is there a way to tell rak explicitly how many fds it can use?

[03:59] <wayland76> eea: A coding style checker is on my list of things to do (but only if no-one else has yet), but it's a fair way down, so it may be a while before I get to it.  

[04:01] <wayland76> eea: Context: We're currently in the middle of a replacement for the second stage of compilation.  The new one is called RakuAST.  It's going to make self-modifying code a lot easier.  

[04:02] <wayland76> It's already available in preview if you set the environment variable RAKUDO_RAKUAST=1 but it's likely that in the next few releases (maybe even the next) that we're going to make it the default going forward (ot possibly the only one).  

[04:04] <wayland76> [Coke]: Thanks for the ticket.  

[04:04] <wayland76> *wiki page, not ticket

[04:49] <japhb> [Coke]: You can tell rak how much concurrency it is allowed using --batch and --degree.  On a system with lots of cores or low ulimits, dropping those helps a lot.  For me, just forcing a smaller --degree did wonders.

[04:49] <japhb> ISTR there was also a delayed-close bug in rak at one point that lizmat already fixed, but if you haven't upgraded your rak in a while, you might be hitting.

[05:18] *** hwj joined
[05:25] *** acidsys left
[05:26] *** acidsys joined