-
-
Notifications
You must be signed in to change notification settings - Fork 146
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
Panic invalid memory address after reconnect a node #139
Comments
Hello, thanks for the report. May I ask you to run with |
Of course I will take a look soon Either it's missing a condition or there is a desync on some state (since disconnection of a node, trying to interact with previous demand) https://github.com/ergo-services/ergo/blob/master/gen/stage_dispatcher.go#L479
|
Thanks. It helped. Nice catch. PS: I wouldn't recommend to use this approach https://gist.github.com/davidroman0O/db04fa224c710a4ae33d53d28304e88b#file-consumer-go-L88
This code burns the CPU. The better way is using
|
Yeah I know, it was just to play around quickly 😄 |
Fixed. In the |
Damn I didn't even had the time to look at it |
Describe the bug
Using the example
genstage
, change it to have two nodes, connect one to the other, disconnect, reconnect and panicIt kills the producer process directly, the entire node does NOT crash
To Reproduce
Steps to reproduce the behavior:
I've made a gist with all the code and a readme there https://gist.github.com/davidroman0O/db04fa224c710a4ae33d53d28304e88b
Expected behavior
Maybe a better error why it has a nil pointer? why? where? stacktrace?
Or maybe it should just not panic
Environment (please complete the following information):
Additional context
I was just experimenting with the examples, trying to plug a bit of my codebase of some side projects and end up with this issue
I came back on the
examples
to test it again with very little modification and the error appear!The text was updated successfully, but these errors were encountered: