Adding remote scenarios #202
Merged
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
zeroXbrock
approved these changes
May 1, 2025
Closed
This was referenced May 14, 2025
Merged
This was referenced May 19, 2025
Merged
This was referenced May 27, 2025
Merged
Merged
Merged
This was referenced Jul 14, 2025
Merged
This was referenced Aug 14, 2025
Merged
Merged
This was referenced Aug 28, 2025
Merged
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Motivation
Solves #133
Solution
We add a format
scenario:<SCENARIO_NAME>instead of the relative path of the scenario files, and we can fetch the file from Github storage.Example
contender setup scenario:uniV2.tomlcontender setup scenario:precompiles/modexp.tomlNote: We have to follow the directory structure of the scenarios directory, wherever it's hosted
PR Checklist