-
Notifications
You must be signed in to change notification settings - Fork 209
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
FireFly crashed after attempting to send on closed websocket channel #265
Comments
Seems like this may have been the same issue: |
Same on this one: |
Another instance fyi @awrichar or @nguyer if you have cycle for an investigation into this one: |
I just ran into this one too: https://github.com/hyperledger/firefly/runs/4014224317 I'll take a look and see what I can do to fix this. It's getting annoying. |
Reopening because I'm definitely still seeing this locally. This is a confusing issue - but it boils down to 3 threads contending over the
The problem actually isn't related to websockets at all. It's simply the way this Go channel is managed, and the fact that one method may close it and then another attempt to use it. |
https://github.com/hyperledger/firefly/actions/runs/1720901977 hit this in #418 e2e
|
While running E2E tests, I observed that one of the FireFly nodes suddenly went down and did not come back up. Logs (below) reveal that FireFly attempted to invoke
wc.send
fromdispatchChangeEvent
after the websocket was already closed, which triggered a fatal panic.The text was updated successfully, but these errors were encountered: