Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[MLIR:Python] Fix race on PyOperations. #139721
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
base: main
Are you sure you want to change the base?
[MLIR:Python] Fix race on PyOperations. #139721
Changes from all commits
51ea007
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dumb question: is there a way to put a runtime assert/check here that the mutex is actually held? so that there's some way for people that don't read the doc strings (...like me...) to save themselves via compiling with asserts. e.g. i'm wondering if
nanobind::ft_mutex::lock()
is a no-op if the mutex is already held/locked by the thread?if that's too tedious/onerous a change than i propose we rename the method to something like
setInvalidWhileLocked
(although that implies the method will be a no-op "when unlocked", which is not true)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That would be nice, wouldn't it.
Sadly
PyMutex_IsLocked
isn't a public CPython API; I filed python/cpython#134009 for that.It would probably be possible for nanobind to clone that code, much as we're doing for
PyUnstable_TryIncRef
, but let me wait until we hear back on the CPython issue before I send them a PR adding a.is_locked()
method on the nanobindft_mutex
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should add: there's no particular reason we have to use a
nb::ft_mutex
here, they aren't particularly special. We could use another mutex that does have this API. However,nb::ft_mutex
has the nice property of being present if and only if we are in GIL-disabled mode.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems special enough to me. we can file this as a
TODO
and just do the tedious thing instead for now (rename the affected methods).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whoops should've read everything first - guess you already did rename things. cool