switch to WS engine communication update sequencer [Draft] #15
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
alexpeterson91
added
the
Blocked
alexpeterson91
force-pushed
the
voss/testFixCommunication
branch
from
0d2ab5d to
47084b0
Compare
alexpeterson91
force-pushed
the
voss/testFixCommunication
branch
from
a5f1dfb to
e38470e
Compare
alexpeterson91
added
enhancement
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.
update sequencer to latest docs, and change from http engine to WS engine, the HTTP engine is only via localhost it cant have rpc commands from outside the container.