fix: tolerate missing budgets in job list output#51
Open
antfleet-ops wants to merge 1 commit into
Open
Conversation
Constraint: preserve existing TTY and JSON behavior.\nRejected: BigInt(j.budget) without presence check | valid v2 jobs can omit budget.\nConfidence: high\nScope-risk: narrow\nDirective: keep CLI formatters tolerant of nullable backend fields.\nTested: npm run typecheck; npm run build\nNot-tested: live backend job list response.
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
1 participant
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
acp job listhandle missing v2 budgets the same way as TTY outputN/Ainstead of callingBigInt()on a missing budgetFixes #39.
Verification
npm run typechecknpm run buildAntFleet audit provenance
Filed from antfleet-ops after AntFleet's two-model Virtuals repo scan found the non-TTY formatter could crash on valid active v2 jobs whose
budgetfield is absent.