Add nosync flag to init #1929
Merged
Add nosync flag to init #1929
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
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.
I'm running boost in a devent environment for demonstrating a new deal making protocol. Running lotus in a devnet environment naturally leads to networks that are very out of sync with devnet beacon and get into this state in a racy way dependent on the time between init and running the lotus-miner.
boostd runhad a very helpful flag--nosyncwhich allows devnets to avoid failing on this race condition.It would be helpful for my usecase and minimally invasive to add this flag to
boostd inittoo.