chore: rank and identify builder bid candidates in log - #9966
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4a4b0ada8c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Performance Report✔️ no performance regression detected Full benchmark results
|
a3de2eb to
887ca89
Compare
Ranked builder bid candidatesprints the candidates in the order the bid requests resolved, not ranked, and does not say which builder each bid came fromselectBestBidbuilderIndexand boosted total of each candidatekey=valuefields, the colon separator collides with the url schemetoPrintableUrlas done in all other builder logsbidSource, it is the first ranked candidate now andSelected builder blockalready logs the block sourceRanking compares the unscaled
boostFactor * totalGweias before, only the log scales down to print ETH.ranks builder bids without truncating boosted valuesused two structurally identical bids so the assertion matched either one, give them distinct builder indices and cover the max boost paths.