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

Remove pws set #162

Closed
wants to merge 3 commits into from
Closed

Remove pws set #162

wants to merge 3 commits into from

Conversation

robinkrahl
Copy link
Collaborator

This patch removes the pws set subcommand as part of the PWS interface
refactoring, see #139. Users should use pws add (for writing to new slots) or pws
update (for writing to existing slots) instead. This makes it less
likely to accidentally overwrite PWS data.

This patch removes the pws set subcommand as part of the PWS interface
refactoring.  Users should use pws add (for writing to new slots) or pws
update (for writing to existing slots) instead.  This makes it less
likely to accidentally overwrite PWS data.
This reverts commit ba2311e.  The
previous patch removed the code that caused problems with the MSRV
(u8::MIN and u8::MAX), so we no longer have to increase it.
let mut ncli = Nitrocli::new().model(model);
let _ = ncli.handle(&["pws", "set", "10", "clear-test", "some-login", "abcdef"])?;
let _ = ncli.handle(&["pws", "clear", "10"])?;
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm, why is that call needed?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It’s not needed, but I figured it would be good to check that we can clear an unprogrammed slot without errors. But we can also move that into a separate test case.

@d-e-s-o
Copy link
Owner

d-e-s-o commented Apr 21, 2021

Merged! Thank you Robin! FYI: I removed the pws clear 10 call that I didn't understand why we would need. Let me know if it had some deeper intention that I just didn't grok.

@d-e-s-o d-e-s-o closed this Apr 21, 2021
@d-e-s-o
Copy link
Owner

d-e-s-o commented Apr 21, 2021

Oh, and I didn't revert the MSRV bump. I honestly think it's fine to go a bit higher in the supported Rust version, so that we can use newer features over time; and 1.43.0 is already a year old by now. Let me know if there are some requirements to stay at 1.42 for packaging or something like that.

@robinkrahl robinkrahl deleted the remove-pws-set branch April 21, 2021 07:52
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