zig: always set a reasonable NOFILE rlimit max #15188
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
progress towards #918
this should fix the musl segfault in
test/js/bun/http/serve.test.ts
us_create_timer
is allowed to return a null pointer and our code doesn't currently handle thiswill send real fix in followup
additionally,
closes #15184
setting the ulimit manually should never be necessary but it appeared to be so because empirically the NOFILE rlimit was coming back as 1024/4096 on alpine and we were prematurely getting EMFILE in the course of normal operation