Compatibility with Protobuf 4.XX about fhir-py HOT 7 OPEN

Circling back here: we found the root cause: essentially our use of the "json_name" annotation on one of the FHIR data types is colliding with an additional check in the protobuf 4.x library -- so we need to change how we generate and protobufs and parse FHIR JSON into them.

The change is relatively straightforward (but not trivial) and we'll get to that after wrapping up an unrelated change in flight, so I think we can have this fixed in the next week or two.

from fhir-py.

Hi Rob, we'll look into it and report back, probably later this week. I suspect this may be related to protocolbuffers/protobuf#12525, which we can try working around by regenerating the FHIR protos with the appropriate option there.

-Ryan

from fhir-py.

thanks so much ryan, appreciate it!

from fhir-py.

great to hear, thank you for the update!

from fhir-py.

A quick update: the compatibility issue turned out to be a bit more involved than anticipated, but we have a targeted fix in the works and should push something in the next couple days.

from fhir-py.

The updated code should work with the Python protobuf 4.x libraries now.

Note that this will require using protoc >= 3.19, which isn't easily available on the current Ubuntu long-term support release used via GitHub actions (and many production systems), so I'm keeping the protobuf verison pinned in the 3.x range in this repository itself. However, if you're able to build this library and use a newer version of protoc, this should now work with the 4.x libraries.

from fhir-py.

Thank you! I'll give it a try

from fhir-py.