Bug: Netremote CLI prints incorrect success message for set-ssid
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- cli, networking
Research direction
Start at the netremote-cli wifi set-ssid command and trace how its success message receives the AP ID and SSID arguments. Reproduce with sudo netremote-cli wifi set-ssid wlo1 netremote2-ap-wlo1, then verify that the output names netremote2-ap-wlo1 as the SSID and wlo1 as the access point.
Written by the indexing model from the issue text.
Description
Describe the bug
When setting the SSID of an AP via netremote CLI, the success message switches the AP ID and the SSID.
Steps To Reproduce
Run sudo netremote-cli wifi set-ssid wlo1 netremote2-ap-wlo1.
Expected behavior
Printed message should say: Successfully set SSID to 'netremote2-ap-wlo1' for wifi access point 'wlo1'.
Actual behavior
Printed message says: Successfully set SSID to 'wlo1' for wifi access point 'netremote2-ap-wlo1'.
- Dominant language
- C++
- Stars
- 20
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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 microsoft/netremote
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
-
bug
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 52/100
All issues in microsoft/netremote
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100