We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Running rivalcfg --battery-level with no supported device connected returns an unrecognized arguments error.
rivalcfg --battery-level
$ rivalcfg --battery-level usage: rivalcfg [-h] [--list] [--version] [--no-save] [--update-udev] [--print-udev] [--print-debug] rivalcfg: error: unrecognized arguments: --battery-level
I would expect an error message saying that no supported device was found.
→ always reproducible
RIVALCFG ======== Version: 4.9.0 udev rules installed: True udev rules up to date: True Installation path: /usr/lib/python3.11/site-packages/rivalcfg OPERATING SYSTEM ================ OS: Linux Platform: Linux-5.15.114-2-MANJARO-x86_64-with-glibc2.37 Version: #1 SMP PREEMPT Sun Jun 4 10:32:43 UTC 2023 Distribution issue: Manjaro Linux \r (\n) (\l) PYTHON ====== Python version: 3.11.3 HIDAPI version: 0.14.0 PLUGGED STEELSERIES DEVICES ENDPOINTS =====================================
I have already fixed the issue locally and will submit a pull request soon.
The text was updated successfully, but these errors were encountered:
Merge branch 'LennardKittner-Unrecognized-arguments-error-when-no-dev…
591a9ac
…ice-is-found.-#213'
Fixed by #214, it will be released in next rivalcfg version :)
Sorry, something went wrong.
No branches or pull requests
Bug description
What happened
Running
rivalcfg --battery-level
with no supported device connected returns an unrecognized arguments error.What was expected
I would expect an error message saying that no supported device was found.
Step to reproduce
→ always reproducible
rivalcfg --battery-level
System information
Resolving the Issue
I have already fixed the issue locally and will submit a pull request soon.
The text was updated successfully, but these errors were encountered: