The version 0.13.16 leads build failed.

[PonyCui]

This is the build failed message.

    Compiler message:
    file:///Users/jenkins/.pub-cache/hosted/pub.dartlang.org/protobuf-0.13.16/lib/src/protobuf/builder_info.dart:43:34: Error: Method not found: 'MapFieldInfo.map'.
        _addField(MapFieldInfo<K, V>.map(name, tagNumber, index, PbFieldType.M,
                                     ^^^
    file:///Users/jenkins/.pub-cache/hosted/pub.dartlang.org/protobuf-0.13.16/lib/src/protobuf/field_info.dart:45:9: Error: '_mapEntryBuilderInfo' isn't an instance field of this class.
            _mapEntryBuilderInfo = null {
            ^^^^^^^^^^^^^^^^^^^^
    file:///Users/jenkins/.pub-cache/hosted/pub.dartlang.org/protobuf-0.13.16/lib/src/protobuf/field_info.dart:61:9: Error: '_mapEntryBuilderInfo' isn't an instance field of this class.
            _mapEntryBuilderInfo = null;
            ^^^^^^^^^^^^^^^^^^^^
    file:///Users/jenkins/.pub-cache/hosted/pub.dartlang.org/protobuf-0.13.16/lib/src/protobuf/field_info.dart:68:9: Error: '_mapEntryBuilderInfo' isn't an instance field of this class.
            _mapEntryBuilderInfo = null {
            ^^^^^^^^^^^^^^^^^^^^
    file:///Users/jenkins/.pub-cache/hosted/pub.dartlang.org/protobuf-0.13.16/lib/src/protobuf/field_info.dart:82:12: Error: '_mapEntryBuilderInfo' isn't an instance field of this class.
          this._mapEntryBuilderInfo])
               ^^^^^^^^^^^^^^^^^^^^
    file:///Users/jenkins/.pub-cache/hosted/pub.dartlang.org/protobuf-0.13.16/lib/src/protobuf/field_info.dart:199:9: Error: Superclass has no constructor named 'FieldInfo._'.
          : super._(
            ^^^^^
    file:///Users/jenkins/.pub-cache/hosted/pub.dartlang.org/protobuf-0.13.16/lib/src/protobuf/field_info.dart:195:21: Error: Final field '_mapEntryBuilderInfo' is not initialized.
    Try to initialize the field in the declaration or in every constructor.
      final BuilderInfo _mapEntryBuilderInfo;

[aaronlademann-wf]

I can confirm that protobuf 0.13.16 is causing every build in our company's CI system to fail right now.

Appears to be related to #280

@nwparker @sigurdm @szakarias

[nwparker]

Yeah Aaron, without me looking further have you also tried to regenerate the dart files from protobuf? If that is that is the fix, we should have versions the release differently. But please try that first.

…

On Thu, Sep 12, 2019, 07:27 Aaron Lademann ***@***.***> wrote: I can confirm that protobuf 0.13.16 is causing every build in our company's CI system to fail right now. Appears to be related to #280 <#280> @nwparker <https://github.com/nwparker> @sigurdm <https://github.com/sigurdm> @szakarias <https://github.com/szakarias> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#284>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7SPTCU3ZDWI3MOGP3XFRDQJJGVNANCNFSM4IWCZECQ> .

[jakemac53]

The version needs to be rolled back (0.13.6) as it is a breaking change. The rollback should be published as 0.13.7 or 0.13.16+1.

cc @sigurdm

[kevmoo]

We should do this ASAP. Much breaking. 😢

[jakemac53]

Note that the workaround here is to pin protobuf to <0.13.6:

dependency_overrides:
  protobuf: <0.13.16

[jakemac53]

We have now published bazel_worker version 0.1.22 which allows proto 0.14.x and should also resolve the issue if you pub upgrade (assuming you don't have other packages blocking the latest proto).

[jakemac53]

I pushed a branch to do the revert https://github.com/dart-lang/protobuf/tree/revert-0.13.16.

This should be published and then merged into master.

[jakemac53]

Ok actually I managed to get the keys from an owner and publish on my own. I sent out the PR to merge the changelog entry into master #287. I also tagged the release in the repo.

[sigurdm]

Sorry - i published 0.13.16 from the wrong commit.
Thanks @jakemac53 for publishing a revert!