-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Update protoconverter patch #36290
Update protoconverter patch #36290
Conversation
This serves to decouple protoconverter from the protobuf version it was forked off of. These changes should really be upstream, but upstream is experiencing technical issues taking patches right now, so we'll carry them here until those are resolved. Signed-off-by: Alejandro R. Sedeño <[email protected]>
CC @envoyproxy/dependency-shepherds: Your approval is needed for changes made to |
This is one of the roadblocks for updating our C++ Protobuf dependency. |
Do you have any more context on this? This is a huge patch. What was actually changed here? |
When protoconverter forked off of protobuf, it brought with it things it should not have. The crippling one was Since the fork, this file has changed in protobuf, and importantly, the definition of This parch is large, yes, but also very negative. Some of it is already in upstream, but not exported to github due to technical issues. The patch removes these files:
Additionally, it:
And in a few places it reformats things slightly. I tried to filter these formatting-only changes out, but some crept in. |
Signed-off-by: Alejandro R. Sedeño <[email protected]>
I've gone ahead and moved the file deletions to separate |
/retest |
/retest |
Okay, I don't know what's up with Envoy/Publish and verify.
|
that should be fixed now - i broke it earlier and landed a patch soon after |
argh - another 8( - ill fix it now ... |
should be half fixed - will follow up asap when i figure out the issue |
Carving off more of #36167. |
Nope, still fails.
|
im debugging it atm - but its taking a while |
Okay, we're good to go on CI again. Anything else on your end, @mattklein123? |
im really concerned about the amount of patching going on here - if we are going to land this there needs to be a strong justification for doing so my 2 questions are
|
We can't update protobuf without landing this because protoconverter upstream is currently tightly coupled to protobuf <27 and builds with newer protobuf will fail. It doesn't need to be nor should it be this tightly coupled. We can't upstream these changes until upstream fixes their export process from Google's internal repo. Or, rather, I can upstream them but it won't do us any good here until the export is fixed. In fact, some of these changes have already landed but have not been exported. |
if its to update protobuf - we arent going to do that until after the release anyway - so probably i would say take this one slowly and try to get the upstream issues resolved in the meantime |
I assume you mean 1.32.0, and not the 1.31.2 that just happened? Trying to fix upstream's issues is a parallel track I am working on, yes. |
yeah 1.32 is due in the next few weeks |
I've attempted to fix protoconverter upstream, but it has gotten itself tangled up with things marked google-internal and is currently not exportable in a way that builds. |
We can merge this to unblock things as long as you are still working towards fixing the upstream issues. Thank you! |
Thanks @mattklein123; to alleviate concerns, as soon as upstream export issues are fixed it is my intention that we be able to import this with no patches. |
This serves to decouple protoconverter from the protobuf version it was forked off of.
These changes should really be upstream, but upstream is experiencing technical issues taking patches right now, so we'll carry them here until those are resolved.
Risk Level: low
Testing: CI