Repository navigation
Re-emit job events when start, duration or reduction changes - #327
Merged
Merged
Conversation
`job` was sent once per uuid so a job's reduction stayed frozen at first sight. `jobs_active` now keeps start_time/duration/reduction per uuid and re-sends `job` when any changes. Same event shape, `completed_job` and first-sync unchanged. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
netniV
approved these changes
Oct 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
jobwas sent once per uuid per session, so a job'sreductionstayed at the value from when the mod first saw it.jobs_activenow remembersstart_time,durationandreductionper uuid, andjobis sent again when any of them changes. Same event shape, no new keys, no config changes.Notes
away_assignment(feat: sync away team assignments #295, Include trait demand in away assignment events #318) andbuff, ajobis re-sent in an unflagged batch when its state changes, with the same shape; treat ajobfor a uuid you already hold as an update. This already happens for every active job after a restart.completed_jobandX-PRIME-SYNCbehave as before.Verified
Windows client build 271, mod built from
dev+ this change, against a logging sync target: a 10-day speed-up on a research job produced a newjobwith the same uuid andreduction+864,000; a 5-hour one +18,000. Alliance helps also re-send (each help trims ~1% of the remaining time). Finishing a job with speed-ups producedcompleted_job. Untouched jobs produced no events. macOS not tested.Checks
Local MSVC release build clean; macOS not built locally. No CHANGELOG, version, proto or config changes.
🤖 Generated with Claude Code