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

Revert "Fix #301." #367

Merged
merged 1 commit into from
Dec 6, 2022
Merged

Revert "Fix #301." #367

merged 1 commit into from
Dec 6, 2022

Conversation

lthibault
Copy link
Collaborator

This reverts commit a2ae8c4.

This reverts commit a2ae8c4.
Copy link
Contributor

@zenhack zenhack left a comment

Choose a reason for hiding this comment

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

For posterity: this is the source of #349; the analysis in the (now removed) comment is correct insofar as it identifies what was causing a data race before, but doing it the other way panics, because when the finish message comes in the message will be freed, possibly before answerQueue.fulfill() is done with it, causing a panic.

My next task is to come up with a proper fix for both of these issues, but the consequences of the data race are less bad than the panic, and this is blocking @lthibault from releasing, so we're reverting this for the moment.

@lthibault lthibault merged commit 7f52e85 into main Dec 6, 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