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

More verbose error message for redis connection failure (#479) #480

Merged
merged 1 commit into from
Nov 4, 2021

Conversation

lkatalin
Copy link
Contributor

@lkatalin lkatalin commented Nov 3, 2021

This PR adds a bit more context to the panic that results when Rekor can't connect to the redis server. It will look like this:

2021-11-03T16:07:17.091-0400	PANIC	api/api.go:165	failure connecting to redis instance: 
dial tcp 127.0.0.1:6379: connect: connection refused

rather than

2021-11-03T12:54:43.331-0400	PANIC	api/api.go:165	dial tcp 127.0.0.1:6379: connect: 
connection refused

Closes #479

Signed-off-by: Lily Sturmann <lsturman@redhat.com>
@lukehinds lukehinds merged commit 0d3023a into sigstore:main Nov 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error message confusing when rekor fails to connect to redis
2 participants