-
Notifications
You must be signed in to change notification settings - Fork 66
Validate deploy numeric options before actions run #744
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
ralyodio
merged 1 commit into
profullstack:master
from
rissrice2105-agent:codex/sh1pt-deploy-numeric-options
Jun 14, 2026
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| import { describe, expect, it } from 'vitest'; | ||
| import { parsePositiveFiniteNumber, parsePositiveSafeInteger } from './deploy.js'; | ||
|
|
||
| describe('deploy numeric option parsers', () => { | ||
| it('accepts positive safe integer resource counts', () => { | ||
| expect(parsePositiveSafeInteger('4')).toBe(4); | ||
| }); | ||
|
|
||
| it.each(['nope', '0', '-1', '1.5', 'Infinity', '9007199254740992'])( | ||
| 'rejects invalid resource count %s', | ||
| (value) => { | ||
| expect(() => parsePositiveSafeInteger(value)).toThrow('positive safe integer'); | ||
| }, | ||
| ); | ||
|
|
||
| it('accepts positive finite memory and price values', () => { | ||
| expect(parsePositiveFiniteNumber('0.5')).toBe(0.5); | ||
| expect(parsePositiveFiniteNumber('12.75')).toBe(12.75); | ||
| }); | ||
|
|
||
| it.each(['nope', '0', '-1', 'NaN', 'Infinity', '-Infinity'])( | ||
| 'rejects invalid finite value %s', | ||
| (value) => { | ||
| expect(() => parsePositiveFiniteNumber(value)).toThrow('positive finite number'); | ||
| }, | ||
| ); | ||
| }); |
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Number('0x10')→16andNumber('1e2')→100both satisfy the safe-integer and finite-positive checks, so--cpu 0x10or--gpu-count 1e2pass validation and are forwarded to the action. A user who fat-fingers0xor uses scientific notation by accident would get an unexpected count rather than a validation error. Adding an explicit check (/^\d+$/for the integer parser,/^\d+(\.\d+)?$/for the float parser) before callingNumber()would close this gap without affecting normal decimal input.