My apologies if my last message wasn't clear. To clarify, I observed this
issue specifically when running the pipelines with the *Prism* runner.
The Reshuffle change doesn't seem to affect other runners based on my
observations.

On Tue, May 6, 2025 at 10:11 AM Shunping Huang <shunp...@google.com> wrote:

> -0 (not binding)
>
> I tested a bunch of anomaly detection pipelines on my end. While most of
> them run fine, I noticed that Python pipelines
> with custom windows followed by Reshuffle fail to run. The problem was
> introduced in the change of Reshuffle in Python and
> was not caught until rc1.
>
> An issue was created (https://github.com/apache/beam/issues/34829) and
> the fix has been submitted and merged to master (
> https://github.com/apache/beam/pull/34830).
> As the problem affects a common usage pattern, I hope a new pre-release
> version (rc2) will be issued that includes this fix.
>
> Thanks!
>
> On Sat, May 3, 2025 at 9:30 AM XQ Hu via dev <dev@beam.apache.org> wrote:
>
>> +1 (not binding). Tested it with the Beam Python RC1 using Dataflow:
>> https://github.com/google/dataflow-ml-starter/actions/runs/14804862281/job/41571312161
>>
>> On Fri, May 2, 2025 at 5:09 PM Yi Hu via dev <dev@beam.apache.org> wrote:
>>
>>> Hi everyone,
>>> Please review and vote on the release candidate #1 for the version
>>> 2.65.0, as follows:
>>> [ ] +1, Approve the release
>>> [ ] -1, Do not approve the release (please provide specific comments)
>>>
>>>
>>> Reviewers are encouraged to test their own use cases with the release
>>> candidate, and vote +1 if
>>> no issues are found. Only PMC member votes will count towards the final
>>> vote, but votes from all
>>> community members are encouraged and helpful for finding regressions;
>>> you can either test your own
>>> use cases [13] or use cases from the validation sheet [10].
>>>
>>> The complete staging area is available for your review, which includes:
>>> * GitHub Release notes [1],
>>> * the official Apache source release to be deployed to dist.apache.org
>>> [2], which is signed with the key with fingerprint D20316F712213422 as
>>> automated [3],
>>> * all artifacts to be deployed to the Maven Central Repository [4],
>>> * source code tag "v2.65.0-RC1" [5],
>>> * website pull request listing the release [6], the blog post [6], and
>>> publishing the API reference manual [7].
>>> * Python artifacts are deployed along with the source release to
>>> dist.apache.org [2] and PyPI[8].
>>> * Go artifacts and documentation are available at pkg.go.dev [9]
>>> * Validation sheet with a tab for 2.65.0 release to help with validation
>>> [10].
>>> * Docker images published to Docker Hub [11].
>>> * PR to run tests against release branch [12].
>>> * Github Release pre-release page for v2.65.0-RC1 [13].
>>>
>>> The vote will be open for at least 72 hours. It is adopted by majority
>>> approval, with at least 3 PMC affirmative votes.
>>>
>>> For guidelines on how to try the release in your projects, check out our
>>> RC testing guide [13].
>>>
>>> Thanks,
>>> Release Manager
>>>
>>> [1] https://github.com/apache/beam/milestone/29
>>> [2] https://dist.apache.org/repos/dist/dev/beam/2.65.0/
>>> [3] https://dist.apache.org/repos/dist/release/beam/KEYS
>>> [4]
>>> https://repository.apache.org/content/repositories/orgapachebeam-1403/
>>> [5] https://github.com/apache/beam/tree/v2.65.0-RC1
>>> [6] https://github.com/apache/beam/pull/34821
>>> [7] https://github.com/apache/beam-site/pull/682
>>> [8] https://pypi.org/project/apache-beam/2.65.0rc1/
>>> [9]
>>> https://pkg.go.dev/github.com/apache/beam/sdks/v2@v2.65.0-RC1/go/pkg/beam
>>> [10]
>>> https://docs.google.com/spreadsheets/d/1qk-N5vjXvbcEk68GjbkSZTR8AGqyNUM-oLFo_ZXBpJw/edit?gid=1941137270#gid=1941137270
>>> [11] https://hub.docker.com/search?q=apache%2Fbeam&type=image
>>> [12] https://github.com/apache/beam/pull/34794
>>> [13] https://github.com/apache/beam/releases/tag/v2.65.0-RC1
>>> [14]
>>> https://github.com/apache/beam/blob/master/contributor-docs/rc-testing-guide.md
>>>
>>> --
>>>
>>> Yi Hu, (he/him/his)
>>>
>>> Software Engineer
>>>
>>>
>>>

Reply via email to