This happens when the underlying descriptor pool for a fast_cpp_proto is not the same as the C++ version, which happens in bazel builds where two or more instances of the protobuf implementation extension are loaded. Solving that issue needs better cc_shared_library support, or similar.
Add a fallback mechanism for a fast_cpp_proto that is not from the same pool in the C++ extension as in python.
https://github.com/pybind/pybind11_protobuf/issues/44
This happens when the underlying descriptor pool for a fast_cpp_proto is not the same as the C++ version, which happens in bazel builds where two or more instances of the protobuf implementation extension are loaded. Solving that issue needs better cc_shared_library support, or similar.