-
-
Notifications
You must be signed in to change notification settings - Fork 387
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
Refactor get_password with a common method on QueryWithLogin #1202
Conversation
Hi there @saimn 👋 - thanks for the pull request! I'm just a friendly 🤖 that checks for issues related to the changelog and making sure that this pull request is milestoned and labeled correctly. This is mainly intended for the maintainers, so if you are not a maintainer you can ignore this, and a maintainer will let you know if any action is required on your part 😃. Everything looks good from my point of view! 👍 If there are any issues with this message, please report them here. |
Hello @saimn! Thanks for submitting the PR.
|
Codecov Report
@@ Coverage Diff @@
## master #1202 +/- ##
==========================================
+ Coverage 64.25% 64.36% +0.11%
==========================================
Files 144 144
Lines 11451 11431 -20
==========================================
Hits 7358 7358
+ Misses 4093 4073 -20
Continue to review full report at Codecov.
|
ping 🙌 |
We have a failure after the merge: |
I saw the same error on my other PR, so not related to the merge. It seems related to the recent release of secretstorage 3.1.0 (jaraco/keyring#338 (comment)) but I don't understand the error. It looks like keyring is installed with conda, so probably a dependency issue. |
Weird, the keyring version installed is quite old for that version. |
OK, so the failing build is using the same keyring as it used before. Also secretstorage is still around, but as of 3 days ago, it has a new release. I've just restarted the failing build. If it still fails, we may need to pin the secretstorage version to the one everything worked well before. |
OK, so the issue has been fixed directly in master. |
Following #1198.