Skip to content
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

[crmsh-4.6] Dev: utils: Introduced detect_duplicate_device_path function in utils #1582

Conversation

liangxin1300
Copy link
Collaborator

  • A new function detect_duplicate_device_path has been added to utils.py.
  • This function checks for duplicated device paths in a given list of devices, raising a ValueError if duplicates are found.

To fix issue #1581

- A new function `detect_duplicate_device_path` has been added to `utils.py`.
- This function checks for duplicated device paths in a given list of devices,
  raising a ValueError if duplicates are found.
@liangxin1300 liangxin1300 marked this pull request as ready for review October 11, 2024 06:54
Copy link

codecov bot commented Oct 11, 2024

Codecov Report

Attention: Patch coverage is 20.00000% with 8 lines in your changes missing coverage. Please review.

Project coverage is 67.27%. Comparing base (df8b180) to head (3192fe8).
Report is 7 commits behind head on crmsh-4.6.

Files with missing lines Patch % Lines
crmsh/utils.py 22.22% 7 Missing ⚠️
crmsh/sbd.py 0.00% 1 Missing ⚠️
Additional details and impacted files
Flag Coverage Δ
integration 52.98% <20.00%> (-0.02%) ⬇️
unit 49.67% <20.00%> (-0.02%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
crmsh/sbd.py 91.75% <0.00%> (-0.24%) ⬇️
crmsh/utils.py 66.05% <22.22%> (-0.21%) ⬇️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@liangxin1300
Copy link
Collaborator Author

This will be ported to the master branch with #1491

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants