You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proto2 files that use the required keyword now have the generated code throw InvalidProtocolBufferException, which has its constructor marked as internal and the generated classes cannot be compiled.:
Cannot access '<init>': it is internal in 'InvalidProtocolBufferException'
Using latest 0.14.0 version.
The text was updated successfully, but these errors were encountered:
Oh shoot. We missed this in our unit tests because they're part of the same project as the runtime, so they have access to internal members. I'll get a fix for this out in the next few days.
Proto2 files that use the
required
keyword now have the generated code throwInvalidProtocolBufferException
, which has its constructor marked asinternal
and the generated classes cannot be compiled.:Using latest
0.14.0
version.The text was updated successfully, but these errors were encountered: