This is an automated email from the ASF dual-hosted git repository.
shunping pushed a change to branch resolution-too-deep
in repository https://gitbox.apache.org/repos/asf/beam.git
discard 0c7521da7ad Remove numpy and pandas bounds
discard b9e30c56617 Update version.
discard 06b6c0efdb5 Update dep
discard ee4a8484561 Run with 1.17
discard b831a82ef1b Upgrade lower bound
discard 528eea52a35 Debug again.
discard 4c7701a69bf Revert back to tft 1.15.0
discard ba24026520d Drop in uv to resolve deps.
discard 39eb3a9ff26 Change tft upper bound.
discard 1fdbb089b51 Set up debug environment as the failed gradle task.
discard 47673b91969 Add debugging pip step
discard 721eab59fd3 Comment out successful steps
new dac2848f4ae Upgrade TFX stack to 1.21.x and remove numpy/pandas bounds
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (0c7521da7ad)
\
N -- N -- N refs/heads/resolution-too-deep (dac2848f4ae)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.../beam_Inference_Python_Benchmarks_Dataflow.yml | 290 +++++++++------------
.../apache_beam/testing/load_tests/build.gradle | 2 +-
2 files changed, 130 insertions(+), 162 deletions(-)
