Skip to content

Issues: protocolbuffers/protobuf

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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Flurry of dependencies and conflicts brought in with latest protobuf bazel module untriaged auto added to all issues by default when created.
#19451 opened Nov 30, 2024 by daniel-b2c2
IndentationError
#19449 opened Nov 29, 2024 by DRepas
Generated C++ code with dllexport_decl and deprecated incompatible with GCC 12 or older untriaged auto added to all issues by default when created.
#19447 opened Nov 28, 2024 by cho-m
Can't not find folder : models\research\ untriaged auto added to all issues by default when created.
#19446 opened Nov 28, 2024 by Rays0205
The Message.FromString() Python method is missing from online documentation untriaged auto added to all issues by default when created.
#19433 opened Nov 27, 2024 by dlenskiSB
Set Ruby C calls as Ractor-safe ruby
#19321 opened Nov 19, 2024 by cretz
pip install of protobuff causes "ModuleNotFoundError: No module named 'google'" untriaged auto added to all issues by default when created.
#19234 opened Nov 12, 2024 by ScottGibb
[python] Add python_package and --prefix argument untriaged auto added to all issues by default when created.
#19212 opened Nov 11, 2024 by complynx
ProTip! Add no:assignee to see everything that’s not assigned.