Bump tensorboardX
to allow new protobuf
#1033
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR (permanently?) addresses protobuf version issues. OpenFL inadvertently capped
protobuf
to 3.x as a result oftensorboardX==2.6
.protobuf
3.20.x is >4y old at this point. So the plan is to get rid of this limitation.It was observed that protos in OpenFL-Security (internal) builds case were always built with the recent
protobuf
by respecting what setup actually asked for (i.e >3.20.x version), whiletensorboardX<=2.6
forcedprotobuf
to be 3.x.In summary,
tensorboardX<=2.6
currently dictatesprotobuf==3.x
to be used. They have long lifted this requirement of protobuf version with a minor version bump from 2.6 to 2.6.2.Using
tensorboardX>=2.6
allows usage of any recentprotobuf
version, making it flexible for any TPT package. Aside,tensorboardX
should be deprecated in favor of PyTorch's nativetensorboard
support. This will be addressed in a future PR.