OK, I am going to give it a little more time to consider. If I understand
correctly, the problem already existed in 2.61.0 and our options are: (1)
leave it in 2.62.0 or (2) upgrade enough dependencies that it might be high
risk.
If that is correct and there is no more information that comes up, I
I tested this with my mackbook and with a clean venv and pip install
"apache-beam[gcp]==2.61.0". numpy==2.1.3 is installed.
On Fri, Jan 17, 2025 at 5:25 AM Valentyn Tymofieiev via dev <
dev@beam.apache.org> wrote:
> @Chamikara Jayalath Does this bug also happen in
> 2.61.0 ?
>
> I am seeing that
Yeah, this seems to be happening for numpy 2.1.3. as well so likely the
issue existed before the current release.
On Fri, Jan 17, 2025 at 6:50 AM XQ Hu via dev wrote:
> I tested this with my mackbook and with a clean venv and pip install
> "apache-beam[gcp]==2.61.0". numpy==2.1.3 is installed.
>
Thanks for confirming, then I am fine to call it a known issue in 2.62.0,
2.61.0 and fix for 2.63.0 and I retract my -1 vote.
On Fri, Jan 17, 2025 at 5:49 PM Chamikara Jayalath via dev <
dev@beam.apache.org> wrote:
> Yeah, this seems to be happening for numpy 2.1.3. as well so likely the
> issue
This is your daily summary of Beam's current high priority issues that may need
attention.
See https://beam.apache.org/contribute/issue-priorities for the meaning and
expectations around issue priorities.
Unassigned P1 Issues:
https://github.com/apache/beam/issues/33569 [Task]: Remove Goog
@Chamikara Jayalath Does this bug also happen in
2.61.0 ?
I am seeing that the numpy 2.x upgrade was first introduced earlier in
2.61.0:
https://github.com/apache/beam/commit/6129c9a56d52ebb060417cb397e0764cdd8791bc
In this case the regression would be a preexisting known issue and
according to
