-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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 #6808
Comments
@busFred TKS! Downgrading protobuf to 4.25 works. |
Thanks for flagging this. Looks like the new parameter was added less than 2 months ago in protocolbuffers/protobuf#15703, so it would only be present in very recent versions of protobuf dependencies, which might be a bit restrictive. For now, I'll add a restriction for the protobuf dependency to be < 5.0.0, and eventually we can update it to use the new parameter when we need to bump this dependency again for some reason. |
…king change. See tensorflow#6808 for details.
[detailed] - This issue is referenced in tensorflow/tensorboard#6808. It appears that protobuf deprecated an argument and tensorflow just restricted the version of protobuf to avoid issues. Since it's unclear when they're going to update, lets restrict the version ourselves to avoid complications.
…king change. (tensorflow#6814) The protobuf release 5.26.x is the first one in the major version 5, which introduces a breaking change. This change adds a restriction on that dependency. See tensorflow#6808 for details.
@arcra Adding the upper bound like that is not really a great solution, because any reasonable solver with a constraint on protobuf>=5 will just go ahead and backtrack from tensorboard v2.17.0 to v2.16.2, and then remain broken. A more compatible way to solve this is detect protobuf version and fix the call into |
Instead of restricting protobuf<5.0.0 due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to #6808 and should resolve #6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to tensorflow#6808 and should resolve tensorflow#6887.
Instead of restricting `protobuf<5.0.0` due to the removal to `including_default_value_fields` kwarg in `json_format.MessageToJson` (replaced by `always_print_fields_with_nopresence`), we can instead detect the currently installed protobuf version and use the appropriate kwarg. Contributes to #6808 and should resolve #6887.
…ersion. [detailed] - tensorflow/tensorboard#6808 has been resolved, so we can now remove the explicit dependency to protobuf by bumping tensorboard to 2.17.1.
google.protobuf.json_format.MessageToJson()
including_default_value_fields
argument has been deprecated and removed since protobuf v5.26. need to use `always_print_fields_with_nopresence instead.tensorboard/tensorboard/plugins/hparams/hparams_plugin.py
Line 148 in 71952d6
protocolbuffers/protobuf@2699579#diff-8de817c14d6a087981503c9aea38730b1b3e98f4e306db5ff9d525c7c304f234L89-L94
temporary fix is to just downgrade protobuf to 4.25
The text was updated successfully, but these errors were encountered: