Repository navigation
fix(nodes): merge per-node 24h jobs across aggregators (v0.3.66) - #364
Merged
Merged
Conversation
Each status aggregator keeps its 24h job window in memory, and the board took one aggregator's answer whole (the one seeing the most workers). The dev2 aggregator restarts on every web deploy, so the jobs/earnings columns reset to zero even while the vienna seed still held the whole day. getNodesPayload now reads every aggregator and overlays each node's jobs_24h from whichever counted the most jobs for it. Bumps to 0.3.66 so the seed aggregators (release binaries) start computing jobs_24h too (from #363). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ThreatCrush Security Scan14 finding(s) HIGH/CRITICAL: 2 | MEDIUM: 8 | LOW: 4
Snippets are redacted; ThreatCrush never prints matched credential material. |
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
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.
Follow-up to #363. After deploy, /nodes showed 0 jobs for every node even though the network had 61 completed jobs in 24h: the dev2 aggregator (inside c0mputecom-app) restarts on each web deploy and resets its in-memory window, and the board took one aggregator's answer whole. The vienna seed (:8091) has the full day but runs the 0.3.65 release binary, which has no
jobs_24h.getNodesPayloadreads/nodesfrom every configured aggregator, keeps the board from the one seeing the most workers (unchanged), and overlays each node'sjobs_24hfrom whichever aggregator counted the most jobs for it (mergeJobStats).jobs_24hafter they update.🤖 Generated with Claude Code