Skip to content

Conversation

@dominicqi
Copy link

Fix Issue #3191

Copy link
Contributor

@puellanivis puellanivis left a comment

Choose a reason for hiding this comment

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

I don’t see anything that should break from this… I’ve not proven that it would solve the deadlock. But it’s a good step.

@dominicqi
Copy link
Author

I don’t see anything that should break from this… I’ve not proven that it would solve the deadlock. But it’s a good step.

I thought this change might help break the deadlock by decoupling the two locks — broker.lock and om.pomslock.RLock.

@puellanivis
Copy link
Contributor

I don’t see anything that should break from this… I’ve not proven that it would solve the deadlock. But it’s a good step.

I thought this change might help break the deadlock by decoupling the two locks — broker.lock and om.pomslock.RLock.

Yes, I think it should work as well. But I’m not certain that it would. The phrasing was a bit of a play on:

`Beware of bugs in the above code; I have only proved it correct, not tried it.'' —Knuth

@dominicqi
Copy link
Author

I don’t see anything that should break from this… I’ve not proven that it would solve the deadlock. But it’s a good step.

I thought this change might help break the deadlock by decoupling the two locks — broker.lock and om.pomslock.RLock.

Yes, I think it should work as well. But I’m not certain that it would. The phrasing was a bit of a play on:

`Beware of bugs in the above code; I have only proved it correct, not tried it.'' —Knuth

Haha, yeah — it’s not been properly verified yet.

@github-actions
Copy link

Thank you for your contribution! However, this pull request has not had any activity in the past 90 days and will be closed in 30 days if no updates occur.
If you believe the changes are still valid then please verify your branch has no conflicts with main and rebase if needed. If you are awaiting a (re-)review then please let us know.

@github-actions github-actions bot added the stale Issues and pull requests without any recent activity label Sep 18, 2025
@puellanivis
Copy link
Contributor

I still continue to approve this PR.

@github-actions github-actions bot removed the stale Issues and pull requests without any recent activity label Sep 19, 2025
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