This repository was archived by the owner on Dec 12, 2023. It is now read-only.
fixed bug while attempting to execute script for running op-node #3
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
…ould prevent the script from running
👷 Deploy request for opstack-docs pending review.Visit the deploys page to approve it
|
|
No bro, the problem is the extra spaces on the line before that. Take a look at how I solved it here: |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Removed
--sequencer.enabled \flag from the op-node script, which now allows for it to run succesfully.Tests
With
--sequencer.enabled \Fixes
Without
--sequencer.enabled \