Open
Conversation
…ecution time across eval runs
…g time across validator eval runs
camfairchild
approved these changes
Apr 30, 2026
ibraheem-abe
approved these changes
Apr 30, 2026
Contributor
ibraheem-abe
left a comment
There was a problem hiding this comment.
Lgtm 👍
Just need to add the DB migration
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
3 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.
Changelog
This PR updates the agent score calculating logic to take into account the running time. The
evaluations_hydratedview was updated to calculate the average running seconds across all validator evaluation runs.This is then used by the weight-receiving agent query to order the agents by score, runtime, and creation date. The top agents query was also updated with this logic to make sure agents are ordered correctly.