aIbrahiim commented on issue #38782: URL: https://github.com/apache/beam/issues/38782#issuecomment-4840786808
> It is most likely that the `resolution too deep` failure from [#38780](https://github.com/apache/beam/issues/38780) has the same root cause of this. I see there is a PR to fix that, but maybe we can simplify that to only upgrading tensorflow-transform, tensorflow-metadata and tfx_bsl version like [#39163](https://github.com/apache/beam/pull/39163)? [@aIbrahiim](https://github.com/aIbrahiim) > > I am experimenting this idea at [#39164](https://github.com/apache/beam/pull/39164). Agree it’s the same root cause as old TFT stack conflicting with apache beam gcp and #39163’s minimal bump of tensorflow-transform / tensorflow-metadata / tfx-bsl to 1.21.x is a cleaner fix than full pinning + constraints if CI confirms it resolves ResolutionTooDeep and I also hit a second failure after driver install (worker staging with pyarrow 10 / TF 2.16 wheels), which 1.21 may address via newer pyarrow wheels -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
