Incident Dossier

Deploy Argv Offset

An in-house deploy script reads its flags with hard-coded indices into process.argv. The production wrapper adds an extra prefix argument before the user flags, so canary toggles are silently skipped and the target region is read as undefined.

Initial failing signalcanary flag is missed when wrapped by an extra prefixExpected behavior: parseArgs(argv) === { canary: true, region: 'us-west-2' } · actual behavior: parseArgs(argv) === { canary: false, region: undefined }

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Inspect how the deploy script reads its argv.
Notice the hard-coded indices the parser uses.
Confirm the failure when the wrapper adds an extra prefix argument.
Make the smallest correction that walks the argv array instead of hard-coding indices.

Focus Mode

Start

src/deploy.js

Likely area

src/deploy.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicDeployment

DifficultyEasy

Est. time12 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace