~thopiekar/protobuf/+git/protobuf:fix_jruby_proto3_optional

Last commit made on 2024-01-03
Get this branch:
git clone -b fix_jruby_proto3_optional https://git.launchpad.net/~thopiekar/protobuf/+git/protobuf

Branch merges

Branch information

Name:
fix_jruby_proto3_optional
Repository:
lp:~thopiekar/protobuf/+git/protobuf

Recent commits

4040e13... by Jason Lunn <email address hidden>

Resolve conflicts.

fb761f7... by Jason Lunn <email address hidden>

Merge remote-tracking branch 'upstream/main' into fix_jruby_proto3_optional

# Conflicts:
# ruby/tests/stress.rb

9fa4393... by Jason Lunn <email address hidden>

Fix separate issues in JRuby's "native" "`dup` and `inspect` methods.

Update the stress test to exercise `proto3_optional` fields.

f4ff501... by Protobuf Team Bot <email address hidden>

Add manual epilogue for vectorized loop, and use the SIMD loop for 64 bit ints when AVX2 is available.

PiperOrigin-RevId: 595487765

5cfc9e7... by Joshua Haberman <email address hidden>

Breaking Change: Dropped support for Ruby DSL, [as previously announced](https://engdoc.corp.google.com/eng/doc/devguide/proto/news/2023-12-27.md#ruby-breaking-changes).

The generated code has not used the DSL since 23.0 (released May 8, 2023).

PiperOrigin-RevId: 595481605

f00fc70... by Protobuf Team Bot <email address hidden>

Auto-generate files after cl/595467581

3869318... by Protobuf Team Bot <email address hidden>

Add inner verification code to detect accessors missing required annotations.
This change has no behavior change, other than CHECK-fail `protoc` when a bug is detected instead of generating the buggy code.

PiperOrigin-RevId: 595467581

807f00b... by Mike Kruskal <email address hidden>

Fix typo in cache-clearing workflow

PiperOrigin-RevId: 595424484

2bf62b1... by Protobuf Team Bot <email address hidden>

Internal Code Change

PiperOrigin-RevId: 595410785

670e0c2... by Protobuf Team Bot <email address hidden>

Fix begin iterator for empty arrays.

If the underlying array for a repeated field is a nullptr (which is possible for const array access on a message field that hasn't been set) the begin iterator will currently contain garbage data, which can lead to an illegal access. This CL adds a nullptr check to `begin()`, similar to what already exists for `size()`.

PiperOrigin-RevId: 595217999