-
Notifications
You must be signed in to change notification settings - Fork 308
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
Fix get_kernel_path
for AsyncFileManager
s.
#929
Conversation
Since `AsyncFileManager` never overrode `get_kernel_path`, the base (synchronous) implementation would call `self.dir_exists` and get back a coroutine (which always evaluates as true), but never await it.
@kevin-bates I vaguely remember reading somewhere that there was a way to get one of the Meeseeks to add a label to a PR with a special |
Hi @thetorpedodog. I'm not very familiar with the Meeseeks bot world. I've used MeeseeksDev to transfer issues between organizations, but that's about it. I just reproduced the issue you're resolving and trying out your fix now. Great catch, and thank you for the contribution! |
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.
These changes look good - thank you @thetorpedodog.
Thanks for the quick review! |
@meeseeksdev please backport to 1.x |
Awww, sorry thetorpedodog you do not seem to be allowed to do that, please ask a repository maintainer. |
aw beans |
@meeseeksdev please backport to 1.x |
Something went wrong ... Please have a look at my logs. |
Since
AsyncFileManager
never overrodeget_kernel_path
, the base(synchronous) implementation would call
self.dir_exists
and get backa coroutine (which always evaluates as true), but never await it.