fix: correct standalone sequencer command to use config file path#423
Open
vpavlin wants to merge 1 commit intologos-blockchain:mainfrom
Open
fix: correct standalone sequencer command to use config file path#423vpavlin wants to merge 1 commit intologos-blockchain:mainfrom
vpavlin wants to merge 1 commit intologos-blockchain:mainfrom
Conversation
The standalone mode command was missing the '--' separator and the full config file path. Changed from directory path to the complete config file path: sequencer/service/configs/debug/sequencer_config.json
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
3 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.
🎯 Purpose
The standalone mode command was missing the '--' separator and the full config file path. Changed from directory path to the complete config file path: sequencer/service/configs/debug/sequencer_config.json
⚙️ Approach
Describe the core changes introduced by this PR.
🧪 How to Test
How to verify that this PR works as intended.
Run the command
🔗 Dependencies
Link PRs that must be merged before this one.
None
🔜 Future Work
List any work intentionally left out of this PR, whether due to scope, prioritization, or pending decisions.
None
📋 PR Completion Checklist
Mark only completed items. A complete PR should have all boxes ticked.