-
Notifications
You must be signed in to change notification settings - Fork 793
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
key: Do not require users for parsing #1146
key: Do not require users for parsing #1146
Conversation
(Sorry for the force push - didn't realize this would happen. Please The CI passed, but I guess this means there were no keys without User IDs in the test suite. Perhaps it would be good to add one, and test that we can parse it but not encrypt with it? Re. npm, you might have to |
e2afcf1
to
3602a1e
Compare
I was just looking at the commit list wondering what happened... thanks for the instructions! 👍
Yep, definitely. I'll be back with some more comprehensive test. Still I was surprised that not one test out of over 700 failed... 😱
Install still fails with:
but don't worry. I can create a test even without that and push it here and see it fail+pass. (it's weird that I ran the instructions even in Have a nice day! 👋 |
fb2f3c5
to
02ab76d
Compare
Okay, phew. For such a tiny change I think this is now ready for review. Take a look at it @twiss and see if you can spot some places that are in need of improvement :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 Thanks! ^.^
02ab76d
to
8a91818
Compare
This is a draft PR to get the CI results until I figure out why my
npm test
complains about missing asmcrypto modules :)