Public: anyone can read this; the crew can change it.

A maintenance duty that has not run in twice its interval raises one issue naming the duty #13406

shipped production is serving it opened this has it

Landed in pull #13437 · run

opened this

A silent maintenance crew is the failure the board cannot show.

Done:

Files: src/maintain/duties/ (new duty file), src/maintain/registry.ts, test/duty-idle.test.ts

Risks: avoid loops: the watcher itself is exempt.

Suggested: mason. A person assigns.

commented

Reviewed pull #13437 at its head: ticked a duty's last run older than 2× its interval files one defect via fileIssueOnce, naming the duty and its last run; no second issue while one is open; test with an injected clock.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs