-
Notifications
You must be signed in to change notification settings - Fork 33
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
events: cannot be used as a library #481
Comments
Another idea is to nuke grpc and hope this issue goes away. |
looks like this isn't grpc specific, but due to vendoring |
So unvendoring |
Ah, ok, that's good actually. We shouldn't be vendoring anything under |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
events imports grpc, and grpc does something with net/http. Since we vendor grpc (rightly so, it releases breaking changes frequently), importing events from an external codebase causes a panic:
I am so tired of grpc's issues. This is not going to be easy to solve.
One idea is to break the events writers into separate packages. We could introduce and
rpc
package and move all grpc code there. Other packages would define interfaces so they don't need to import grpc.The text was updated successfully, but these errors were encountered: