Skip to content
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: send on closed channel #58

Merged
merged 1 commit into from
Jun 23, 2021
Merged

Conversation

fracasula
Copy link
Contributor

I noticed the panic while I had the manual acknowledgments branch running in our production systems.

I'm proposing the bugfix here so that I can rebase my other branch and remove the bugfix from there, since it's not related to the manual acknowledgments.

As usual I wrote the test first to make sure that I was able to replicate the panic. The test replicated the panic successfully at least once every three executions. Then I made the changes and ran the test in a loop for at least ~1k times. The panic does not occur anymore nor I was able to find deadlocks.

These changes are now live in production along with the manual acks changes. So far we haven't noticed anything unusual.

@fracasula fracasula mentioned this pull request Jun 16, 2021
@alsm alsm merged commit 4078148 into eclipse-paho:master Jun 23, 2021
@fracasula fracasula deleted the closed-ch branch June 23, 2021 16:26
bkneis pushed a commit to bkneis/paho.golang that referenced this pull request Aug 9, 2022
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.

2 participants