Nikohi 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
critters.zip 
This smells like a signed 16-bit-shaped thing.. And very generic IO errors smell like a C API error.. Maybe it's hitting an implementation limit in one of the C-level primitives it uses, like