fix: driven-detection only marks the newest session per cwd #22

Merged

ClaudiuSchuster merged 1 commit from oss-oo/fix-false-running into main

2026-09-24 14:58:12 +00:00

ClaudiuSchuster commented

2026-09-24 14:58:09 +00:00

Owner

A lock proves ONE driver per cwd — notification steers were mass-flagging entire projects as 'running' (32 false positives). Only the newest session per locked cwd gets driven=true now.

ClaudiuSchuster added 1 commit

2026-09-24 14:58:09 +00:00

fix: driven-detection only marks the newest session per cwd

Checks / Functional checks (pull_request) Successful in 14s

Details Explain this check

2de46ecef6

A dispatcher lock proves ONE driver in a cwd — but the old code marked
EVERY session sharing that cwd as 'running'. Notification steers (one
lock on the parent's project cwd) were mass-flagging whole projects
(30+ sessions) as running. Now only the most recently updated session
in each locked cwd gets 'driven=true'; all others fall back to
DB-status + freshness detection.

ClaudiuSchuster merged commit 5cf2c678e1 into main

2026-09-24 14:58:12 +00:00

ClaudiuSchuster referenced this pull request from a commit

2026-09-24 14:58:13 +00:00

fix: driven-detection only marks the newest session per cwd (#22)

ClaudiuSchuster referenced this pull request from a commit

2026-10-14 12:14:03 +00:00

Pinky ZZZ: the night's second congress — ten owner-sharpened items (v1.83.0)

ClaudiuSchuster referenced this pull request

2026-10-14 12:14:18 +00:00

Pinky ZZZ: the night's second congress — ten owner-sharpened items (v1.83.0) #116