Closed tstirrat15 closed 1 month ago
I'm not entirely sure what's going on here.
The general problem we're running into (or at least my understanding of it) is that the protobuf
version available to the runtime needs to be the same as the protobuf
version used to generate the code, or else there may be mismatches at runtime. That seems to be roughly what's causing the test failures.
I think there's a mismatch between the grpc_python_lib
installed by brew in my environment and the protobuf
version being listed by the library. I've got a TODO item for myself to get this lib using the python-supplied plugins rather than those supplied by buf for the purposes of generation, but that'd go on HEAD rather than here.
Which is to say that I think there's a way to get this working but I haven't yet figured it out.
I ran into version issues when I attempted to regenerate the client. I'm going to assume that the client should still work with the relaxed restrictions, since semver says there are no breaking changes, and cut a release on this branch for testing.
This passed the user's CI and was released in https://github.com/authzed/authzed-py/releases/tag/v0.14.1. I'm going to close this as merging it wouldn't mean much.
I'm mostly opening this to validate that our checks succeed on this release cut.