Bug in DCGM Python3 bindings
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 38/100
Research direction
Start with bindings/python3/DcgmDiag.py, especially the import logger line, and compare it with the other Python binding modules listed in the issue. Re-run python3 -c "import DcgmDiag" and from DcgmDiag import DcgmDiag; done means both imports succeed without requiring an absent logger.py file.
Written by the indexing model from the issue text.
Description
Python3 bindings for DCGM 4.2.3 contains DcgmDiag Module. This module is unimportable because of a "logger" module.
root@ccw-1-3-gpu-210:/usr/share/datacenter-gpu-manager-4/bindings/python3# pwd
/usr/share/datacenter-gpu-manager-4/bindings/python3
root@ccw-1-3-gpu-210:/usr/share/datacenter-gpu-manager-4/bindings/python3# python3 -c "import DcgmDiag"
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/share/datacenter-gpu-manager-4/bindings/python3/DcgmDiag.py", line 18, in <module>
import logger
ModuleNotFoundError: No module named 'logger'
(.venv) root@ccw-1-3-gpu-210:/usr/share/datacenter-gpu-manager-4/bindings/python3# python3 -c "from DcgmDiag import DcgmDiag"
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/share/datacenter-gpu-manager-4/bindings/python3/DcgmDiag.py", line 18, in <module>
import logger
ModuleNotFoundError: No module named 'logger'
These bindings come from DCGM version 4.2.3.
dcgmi --version
dcgmi version: 4.2.3
"logger.py" is not a file contained in the package:
dpkg -L datacenter-gpu-manager-4-core | grep -E '/logger\.py$'
All other imports work successfully:
(.venv) root@ccw-1-3-gpu-210:/usr/share/datacenter-gpu-manager-4/bindings/python3# python3 -c "import dcgm_fields,dcgm_structs,pydcgm"
(.venv) root@ccw-1-3-gpu-210:/usr/share/datacenter-gpu-manager-4/bindings/python3# ls
DcgmDiag.py DcgmGroup.py DcgmJsonReader.py DcgmReader.py DcgmSystem.py common dcgm_collectd_plugin.py dcgm_field_helpers.py dcgm_fields_collectd.py dcgm_fluentd.py dcgm_telegraf.py denylist_recommendations.py
DcgmFieldGroup.py DcgmHandle.py DcgmLogging.py DcgmStatus.py __pycache__ dcgm_agent.py dcgm_errors.py dcgm_fields.py dcgm_fields_internal.py dcgm_structs.py dcgmvalue.py pydcgm.py
- Dominant language
- C++
- Stars
- 809
- Forks
- 115
- Avg merge
- 6d 10h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/DCGM
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
dcgmi InstallCtrlHandler unhandled returnMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
Similar issues
-
bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
chipsalliance/verible#2644 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
grafana/pyroscope-dotnet#470 ·
Maintainers usually reply within 1 day
-
documentation P5 XS
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-astro/AlpacaBridge#1848 ·
Maintainers usually reply within 1 day
-
DiskANN AnnIterator returns unconverted IP distances after the graph walk runs out of candidatesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
zilliztech/knowhere#1933 ·
Maintainers usually reply within 1 day