NikoMar 23

hi there rust peeps

does anyone have any clue why a tokio runtime would have a hard cap on the number of tasks at 32,768?

hitting this limit silently fails to spawn new tasks and existing tasks hit "device or resource busy" errors when they need to use IO

no ulimits have been hit as far as i can tell (83 open files, well under limit of 16,384, and all other limits are either unlimited or unrelated to this issue)

given the failure mode is completely silent i have no clue where to start debugging this

Show thread💙🩷💜Brett🐡🍉🐧Mar 23
@[email protected] not rust particularly but maybe its open files limit or something on your OS?

(In openbsd this is set in /etc/login.conf, I have no idea where linux would have hidden these settings nowadays)
Show threadNiko

@brettm edit didn't federate to your instance i assume

i checked open files at the time of this issue, 83 open files against a limit of 16,384

no other limits were near their cap/others were unlimited

Mar 23 at 9:06amWeb
Show thread💙🩷💜Brett🐡🍉🐧Mar 23
@[email protected] oh no i did not see that. snac does not seem to bother with edits 🙂