Repository navigation
fix(buyer): re-award a job its worker failed to the next bidder (v0.3.68) - #367
Merged
Merged
Conversation
A Failed/Timeout receipt, or no receipt in time, used to end the auction, so the buyer (the Infernet jobs bridge) failed the whole job. 2026-11-14 an outside node fresh on the new house 7B won every chat (best bench, load 0) and failed each after ~60 s; Infernet then fell back to a daemon, ~60 s late. Now the job goes to the next-best bidder from the same auction (the failed worker excluded), up to MAX_REAWARDS (2) times and only inside the job's deadline; the twin re-award path is unchanged. should_reaward() is the rule, unit-tested. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Why: a Failed/Timeout receipt, or no receipt in time, ended the auction, so the buyer failed the whole job. Today an outside node fresh on the house 7B won every Infernet chat (best bench, load 0) and failed each after ~60 s; Infernet then fell back to a daemon ~60 s late. Anthony: "we need retry or re-distribute logic … it should [use] another node to run the job."
What: the job goes to the next-best bidder from the same auction (failed worker excluded), up to
MAX_REAWARDS(2) times and only inside the job's deadline. Twin re-award unchanged.should_reaward()is the rule (unit-tested). v0.3.68 so the jobs bridge and every node pick it up.Tests:
cargo test -p c0mpute-core --lib buyer25/25 on vienna (incl. newreaward_tests).🤖 Generated with Claude Code