-
Notifications
You must be signed in to change notification settings - Fork 32
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
Message.to_dict()
argument always_print_fields_with_no_presence
has no effect on Windows
#483
Comments
Thanks for bug report and clean reproduction! Can you clarify that this does reproduce exactly only on Windows? We're investigating another very deep issue related to python on windows and I'm trying to see how likely this is to be another symptom of that. |
Fixes #18045 This should also cover googleapis/proto-plus-python#483 once we release it. PiperOrigin-RevId: 671925586
Fixes #18045 This should also cover googleapis/proto-plus-python#483 once we release it. PiperOrigin-RevId: 671934556
Fixes #18045 This should also cover googleapis/proto-plus-python#483 once we release it. PiperOrigin-RevId: 671934556
* upb: fix uninitialized upb_MessageValue buffer bugs Fixes #18045 This should also cover googleapis/proto-plus-python#483 once we release it. PiperOrigin-RevId: 671934556 * Regenerate stale files --------- Co-authored-by: Eric Salo <salo@google.com>
Fixed via protocolbuffers/protobuf#18160 |
Yup, only Windows. But I see I'm late to answer. :) Thanks for the quick fix by the way, I'll be waiting for release. Is there an ETA for that? |
Environment details
1.24.0
Steps to reproduce
pip install proto-plus
Message
without setting all fieldstype(message).to_dict(message, always_print_fields_with_no_presence=False)
Fields that are not set will still be present in the returned dictionary, even if
always_print_fields_with_no_presence
should prevent that.This happens only on Windows with
protobuf>=5.28
, pinningprotobuf
to<5.28
prevents it.I created a small repo to reproduce the issue.
https://github.com/silvanocerza/protobuf-bug
See workflow runs that reproduce the issue: https://github.com/silvanocerza/protobuf-bug/actions/runs/10723276739
The text was updated successfully, but these errors were encountered: