run-manager automatic run selection #514
Open
Conversation
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
dsocolobsky
force-pushed
the
dy/run-manager-automatic-run-selection
branch
3 times, most recently
from
163bc83 to
50fd4f6
Compare
dsocolobsky
commented
Jan 23, 2026
dsocolobsky
force-pushed
the
dy/run-manager-automatic-run-selection
branch
from
50fd4f6 to
308a0fa
Compare
dsocolobsky
changed the title
dsocolobsky
force-pushed
the
dy/run-manager-automatic-run-selection
branch
from
b1723b0 to
9be6a25
Compare
This reverts commit 49a6f18.
dsocolobsky
force-pushed
the
dy/run-manager-automatic-run-selection
branch
from
913b598 to
85f35e4
Compare
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.
RUN_IDis not provided the run-manager will scan the solana RPC for those contracts owned by the Coordinator Program, list the runs and attempt to join one at random (which is not halted).RUN_IDis provided then the behavior is the same as usual and it attempts to join the specified run.halted()since I used that in this code, but it shouldn't change any of the logic.