Repository navigation
Return an error when the Secret Service prompt stream ends - #620
Merged
bilelmoussaoui merged 1 commit intoOct 23, 2026
Merged
Conversation
📊 Code Coverage Report
Coverage report generated by cargo-tarpaulin |
bilelmoussaoui
merged commit Oct 23, 2026
aab9efb
into
linux-credentials:main
16 of 17 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We use
oo7in Zed and Delta. Over the past 365 days, Sentry recorded 602 crash events with thisOption::unwrap()panic.We investigated the reports but haven't determined why the D-Bus
Completedsignal stream ends before yielding a message. The reports don't include the underlying D-Bus close reason. I think it is still a good idea to return an Error rather than panicking.Representative stack excerpt (unrelated runtime frames omitted):