Hynek SchlawackAny Ghostty users having the problems with resource limits (on macOS)?
E.g., tox in parallel mode explodes with `OSError: [Errno 24] Too many open files` in Ghostty but works fine in WezTerm. I only see references to Linux cgroups in the docs.
dgelessus@hynek What does `ulimit -a` say about the file descriptor limit in each terminal? macOS in general has a lower default limit than Linux (256 rather than 1024, as far as I can tell) and that causes issues with some software.
Perhaps WezTerm automatically raises the limit by default? Or perhaps you have a shell profile that changes the limit and it's not getting loaded by one of the two terminals for some reason?
(am a Terminal.app user, so I have no more specific advice/experience here, sorry)
@dgelessus yeah it seems like various terminals change the limits differently. it's a a new can of worms!
Terminal and WezTerm raise to 2560 while iTerm and Ghostty leave it at 256. It's the first time I had to change anything on macOS but maybe my parallel tox matrices just got bigger
@hynek huh, interesting - when I simply open Terminal.app and run `ulimit -a`, it says the open file limit is 256. But if I use the "New Command" menu item to run `ulimit -a`, the open file limit is 2560! Similarly, if I start IDLE from the GUI and run `subprocess.check_output(["sh", "-c", "ulimit -a"])`, the open file limit is also 2560.
So it seems like 2560 may be the default and some terminals/shells *lower* it for some reason?? I always thought the "low" 256 was the system default!