-
Notifications
You must be signed in to change notification settings - Fork 7
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
Can you drop dependency on nvidia-ml-py3
?
#481
Comments
What is the stance of the comet maintainers on this issue? This is a blocker for adopting comet for anybody who wants to use a recent version of gpustat. |
I also linked the related gpustat issue |
Hi all. Taking a look at this. Will get back to you ASAP |
Any news here? |
Hi. Is there an update to this issue? |
Hi all. The dev team has identified the issue and found a viable workaround that will maintain current Comet functionality while fixing this issue. The fix will be released within the next two weeks. |
Hi @mattip @xwjiang2010 |
From version 3.31.9 onwards |
Thanks! |
Describe the Bug
A clear and concise description of what the bug is.
Both
nvidia-ml-py3
andnvidia-ml
are installing the samepynvml.py
module, causing issues with the newestgpustat
release. Error msg:Expected behavior
A clear and concise description of what you expected to happen.
Where is the issue?
To Reproduce
Steps to reproduce the behavior:
Stack Trace
If possible please include the full stack trace of your issue here
Comet Debug Log
If possible, please follow the instructions here to run Comet in debug mode and attach the resulting log file.
Screenshots or GIFs
If applicable, add screenshots/gifs to help explain your problem.
Link to Comet Project/Experiment
If applicable, please provide a link to your Comet Project or Experiment.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: