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

directory should not leak operational errors to client #420

Open
nothingmuch opened this issue Nov 29, 2024 · 1 comment
Open

directory should not leak operational errors to client #420

nothingmuch opened this issue Nov 29, 2024 · 1 comment

Comments

@nothingmuch
Copy link
Collaborator

when failing to connect to redis, this is returned as a bad request error, when it should be a 500

see DanGould/pull/8 for failure mode

@nothingmuch nothingmuch changed the title directory leaks operational errors to client directory should not leak operational errors to client Nov 29, 2024
@nothingmuch
Copy link
Collaborator Author

in some cases i also saw a reset by peer instead of the error leaking, which is even worse as that borgs the error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant