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

The drift alarm reads git once per pull head and main tip, so a second reading with nothing moved starts no git process per pull #6502

Closed opened this has it

Pull #6507 was closed

opened this

Part of #5930. alarmDrift in src/flow/alarm_drift.ts runs git for every open pull on every reading; once home and the tick read it (#6346), that is a git process per pull per minute.

Done:

Files: src/flow/alarm_drift.ts, test/flow-alarm-drift.test.ts.

Before pushing: bun x tsc --noEmit and bun test test/flow-alarm-drift.test.ts.

commented

Replaced by #6535. Pull #6507 was handed to a person after three reviews. Each one called the cache sound; the asks left were scope (the as any edits to older tests) and my own unmeasured timing claim in this issue's first title. #6535 keeps branch scout/6502-the-drift-alarm-reads-each-pull-s-distan. It asks for the older test lines back exactly as on main, and for a new pull with no timing claim.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs