fix(runner): fail safe on invalid output size config - #47
Open
fallintoplace wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Parse
SANDBOX_OUTPUT_MAX_SIZEwithsafeInt, using 1024 when the value is invalid.Why
The current
Number(...)conversion turns a typo such asSANDBOX_OUTPUT_MAX_SIZE=bananaintoNaN. The runner uses this value in comparisons while streaming stdout and stderr. Every comparison withNaNis false, so the configured output cap is effectively disabled and output can keep accumulating in memory.The existing
safeInthelper already handles invalid, non-positive, and fractional values. This change uses that helper for the output limit only. Valid integer settings continue to work as before.Tests
bun test api/src/config.test.ts api/src/validation.test.tsbanana,-5,3.7, and2048through the config module.