-
-
Notifications
You must be signed in to change notification settings - Fork 8
prs do not strip comments of gpg_id file #22
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
Comments
Thanks for your report! I cannot reproduce this myself, but did add logic for stripping comments from fingerprints. Would you mind to compile from source and give the latest commit from |
The bad newsIt did not worked,
the good news, I've tested the code that filters and it filters rightCreated simple project with
The file content of
Got output of
The question is
So I'm unable to put breaking points with
Thanks |
Ok I got this, 1, Yes we solved the problem of the remarks This will not work
This will work
What I thought would happen
Example from cpp pgpme project
Screenshot example from c++ debuggerAs you can see in
Question
|
The code you've suggested is exactly the same as what happens internally, for stripping remarks off the fingerprints. What happens when you run the following? prs housekeeping sync-keys Also, do you have the same issues when running cargo run --no-default-features --features backend-gnupg-bin --
cargo run --no-default-features --features backend-gpgme -- |
Hope I've done it correctly, the short id notation fails to sync
The short notation to produce in browser terminal from long notation might be let a= "E68783F3D26DBF30EEA62C6A800421D3A4728717"
undefined
a.substr(-16)
'800421D3A4728717'
And for the full ID
Test with
|
The ubuntu I have is a virtual test/dev machine, so I don't mind
I got this issue on production machine too with a (macos) |
Ok Heres the tested fix I got, I'll upload a pull request (without the debug line)
|
in pass we have (line 101)
however
prs
consider the complete line as UserId and no whatever before the ' # ' onlyTo Reproduce
Steps to reproduce the behavior:
Something like:
3, Change something
prs, will now say it can not find the ID (After inspecting with
export RUST_BACKTRACE=1
)Expected behavior
prs should not care if entry has ramarks or not.
if it helps
in my implementation of
pass
pass simple I've used simplyPseudocode
Sorry I'm not a
Rust
developer and I can not just submitPR
,but I can gladly test and confirm problem solved after it will be fixed.
The text was updated successfully, but these errors were encountered: