-
Notifications
You must be signed in to change notification settings - Fork 552
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
secrets/ldap: return error on read #2156
Conversation
@@ -305,7 +305,7 @@ func TestReadEntity(t *testing.T) { | |||
expectedRetries: 5, | |||
wantError: fmt.Errorf(`failed reading %q`, | |||
entity.JoinEntityID("retry-exhausted-custom-max-412")), | |||
retryWait: time.Millisecond, | |||
retryWait: 500 * time.Millisecond, |
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.
This test is flaky so I am bumping this up to see if it will fix it. Not related to this PR at all but I couldn't help myself.
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.
Nice, things look a lot more robust under stress testing 👍🏼
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.
Thoughts on having a lint workflow that catches missed error handling? https://golangci-lint.run/usage/linters/#errcheck
@@ -305,7 +305,7 @@ func TestReadEntity(t *testing.T) { | |||
expectedRetries: 5, | |||
wantError: fmt.Errorf(`failed reading %q`, | |||
entity.JoinEntityID("retry-exhausted-custom-max-412")), | |||
retryWait: time.Millisecond, | |||
retryWait: 500 * time.Millisecond, |
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.
Nice, things look a lot more robust under stress testing 👍🏼
Description
We are swallowing errors which results in incorrect and confusing behavior when Vault returns an error on Read.
Relates #2155
Checklist