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

Question: dropping grpc dependency from errors? #6910

Closed
jonjohnsonjr opened this issue May 22, 2023 · 1 comment · Fixed by #6917
Closed

Question: dropping grpc dependency from errors? #6910

jonjohnsonjr opened this issue May 22, 2023 · 1 comment · Fixed by #6917
Assignees

Comments

@jonjohnsonjr
Copy link

I'd like to pull in goodkey as a dependency, but this method ends up pulling in grpc. This method doesn't doesn't appear to be used in this repo, but presumably it's used elsewhere?

I see you are receptive to a similar change in #6651, but I don't see a clean non-breaking option in this case :/

Any thoughts on dropping/moving this method?

@jsha
Copy link
Contributor

jsha commented May 22, 2023

A related question: why does goodkey depend on berrors at all? Looks like it's just for this one line:

return berrors.InternalServerError("error checking blocklist for key: %v", key)

But we don't need to explicitly return InternalServerError because a plain fmt.Errorf will get turned into an internal server error at the WFE layer. I suspect if you change that line to a fmt.Errorf you will find that goodkey no longer depends on berrors or gRPC. I'm pretty sure we would accept that as a PR.

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 a pull request may close this issue.

4 participants