Development experience improvements to devnet.sh #3130
Draft
Conversation
This file contains 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
vvp
force-pushed
the
feat/custom-binary-devnet
branch
from
f4f7227
to
49bd2f6
Compare
vvp
force-pushed
the
feat/custom-binary-devnet
branch
from
e5d621d
to
986e95a
Compare
vvp
changed the title
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.
This PR introduces two improvements to development experience when using devnet.sh to start dev nodes locally.
Support for custom executables. This PR enables devnet.sh to start local devnet nodes using a custom executable instead of currently installed
snarkosexecutable, by setting the path to an environment variable. For example:When
SNARKOS_BINis set, the script skips the question of whether to rebuild+install thesnarkosexecutable.Auto-restart option. This PR also implements a simple auto-restart for
snarkOS-processes using a infinite while-loop in bash. With this, you can test dev nodes going off and back online simply by sendingSIGTERMsignals to processes. The length of the auto-restart delay can be configured during script startup.