-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
add ws socket address in config and e2e test for event #2597
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.
LGTM, thanks for the test
Hold on, we should not need yet another address for doing websocket stuff |
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.
Let's please not add another network interface
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.
Great to have an end to end test.
Maybe, try emitting more than one event, or just run that NFT thing twice?
While I do not like that we're needing to add another networking interface for something that can be trivially done via other web frameworks, i'll remove my blocking review with the understanding that we should fix this at some point
53cc57a
to
427b9d5
Compare
* add ws socket in config and e2e test * rebase & comments
as title