-
Notifications
You must be signed in to change notification settings - Fork 925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cmd: add flag to start node on remote core #196
cmd: add flag to start node on remote core #196
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vgonkivs, this should work over ‘start’ command and not ‘init’. We should start the node with a remote core, even when the configuration is initialized to work with an embedded one. Essentially, flags should override configurations in runtime, not overwrite them on disk.
Thanks for explanation @Wondertan . Do we need to handle it for dev node? |
@vgonkivs, you can omit it this for the dev mode, as it is going to be reworked. |
@vgonkivs there is a failing test for starting the remote client - let me know if you can resolve this. Happy to help as well. |
Hi, @renaynay. Currently investigating what went wrong. Panic happened on newly added test for node starting over remote core.
Based on the stack trace, it seems that somehow pubsub subscription was not created... |
Now all my test have passed but another issue appears on TestSubscriber on pipeline with 1.16 |
Don't worry @vgonkivs, there is something wrong with the subscriber stuff on IPFS side I believe, so we're gonna ignore the flakeyness for now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Works flawlessly. No hickups so far 👏
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vgonkivs, man, this is amazing, thank you!
Left a few comments, but otherwise LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some nits but otherwise LGTM! and yes we need a rebase before merge :)
4df8c0f
to
4eed2e2
Compare
Please let me know if everything is ok , so I can squash commits into one. |
Hi @liamsi . It works for me with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Besides two nits, LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! Thanks again @vgonkivs.
Closes #142
P.S. Unfortunately, I was not able to test it properly. I have tried to create and run
StartRemoteClient()
fromcore/testing.go
but got an errorError: node: failed to start: client not running
. Did I do something wrong?