devnet: fix ws port clash for state-sync scenario #9125
Merged
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.
Getting an error in one of the bor nodes in devnet when trying to run the "state-sync" scenario:
This happens for scenarios with more than 1 node.
Digging further this regressions has happened due to this change: #8909
This PR fixes this by updating the devnet
NodeArgs
struct to set the corresponding--ws.port
arg
tag which now exists.