-
Notifications
You must be signed in to change notification settings - Fork 527
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
"NoneType object is not callable" on stopping P2P #237
Comments
@slush0 Thanks for reporting! That's a bug in hivemind, I'll it fix it :) |
For report clarity, this is the failing script.
|
Update: I still haven't fixed this bug, since I didn't understand its cause after a short investigation and switch to tasks with higher priority. I'd appreciate if someone (including new contributors) looks into it. |
@slush0 I can't reproduce this bug in the latest versions of hivemind and Petals, I assume it could have been resolved in hivemind/Petals or their dependencies. I'll close this issue, but please let me know if this bug still happens in your environment (even when you update hivemind & Petals). |
Please also note that the |
The issue is still relevant: #368 (comment) |
Fixing it in learning-at-home/hivemind#579 |
Understood! Yes from what I understand there is no concept of multi-version installation in pip. Thank you for the quick reply and PR, I'll wait for the merge and next release of |
@ivangabriele You don't have to wait for the next release, since the Petals main branch depends on the latest master branch of hivemind. I've merged the hivemind fix, so now you can just upgrade
Let us know if you meet any other issues! |
Fix bigscience-workshop/petals#237, bigscience-workshop/petals#368 (comment). (cherry picked from commit 6f5c471)
@borzunov I didn't reply yesterday but I just confirm here that your |
I have very simple inference testing script. No threading or any advanced stuff. Basically "hello world" inference on Petals. Everything is going well, but when the script is exiting, I always get this error:
It is rather cosmetic issue, but something is not OK there.
The text was updated successfully, but these errors were encountered: