The Stale Lock

The deploy gate refuses to start after yesterday's interrupted release. The recorded lock looks older than its configured lifetime, yet the process still treats it as active.

Initial failing signaldeploy refuses to start with an expired lockExpected behavior: An expired lock allows deployment to start. · actual behavior: An expired lock still blocks deployment.

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Compare a fresh lock with the stale incident fixture.
Trace the timestamp and lifetime values through the expiration decision.
Restore stale-lock recovery without ignoring active locks.

Focus Mode

Start

src/deploy-lock.js

Likely area

src/deploy-lock.js

Challenge Coach

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

TopicCI/CD & Pipelines

DifficultyEasy

Est. time15 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