Skip to content

Conversation

@nguyer
Copy link
Contributor

@nguyer nguyer commented Oct 26, 2021

This is supposed to fix #265

I'm not 100% sure my unit test accurately reproduces the exact situation we're running into in that issue though. Adding the extra check does indeed make this test pass. However, I'm not sure we can count on ws.closed to be set correctly 100% of the time before writing to the channel.

Signed-off-by: Nicko Guyer <nicko.guyer@kaleido.io>
Copy link
Contributor

@awrichar awrichar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems fine. Happy to put this in and see if it helps things.

Signed-off-by: Nicko Guyer <nicko.guyer@kaleido.io>
Signed-off-by: Nicko Guyer <nicko.guyer@kaleido.io>
Signed-off-by: Nicko Guyer <nicko.guyer@kaleido.io>
@nguyer nguyer merged commit ce74fe3 into main Oct 28, 2021
@nguyer nguyer deleted the fix-websocket-panic branch October 28, 2021 15:35
@awrichar
Copy link
Contributor

Didn't work 🙁 I'm still seeing the panic on writing to a closed channel.

peterbroadhurst added a commit to kaleido-io/firefly that referenced this pull request Jan 20, 2022
Signed-off-by: Peter Broadhurst <peter.broadhurst@kaleido.io>
peterbroadhurst added a commit that referenced this pull request Jan 21, 2022
Signed-off-by: Peter Broadhurst <peter.broadhurst@kaleido.io>
awrichar pushed a commit that referenced this pull request Jan 21, 2022
Signed-off-by: Peter Broadhurst <peter.broadhurst@kaleido.io>
awrichar pushed a commit that referenced this pull request Jan 21, 2022
Signed-off-by: Peter Broadhurst <peter.broadhurst@kaleido.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FireFly crashed after attempting to send on closed websocket channel

3 participants