Re: [RESULT] [VOTE] Release 2.53.0, release candidate #2

2024-01-05 Thread Jack McCluskey via dev
And with that, the 2.53.0 release is complete. Thank you, everyone! On Fri, Jan 5, 2024 at 2:39 PM Robert Burke wrote: > Done! > > On Fri, Jan 5, 2024, 11:30 AM Robert Burke wrote: > >> Going to try to get this done. Will report back when completed (or I get >> pulled elsewhere). >> >> On Thu,

Re: [RESULT] [VOTE] Release 2.53.0, release candidate #2

2024-01-05 Thread Robert Burke
Done! On Fri, Jan 5, 2024, 11:30 AM Robert Burke wrote: > Going to try to get this done. Will report back when completed (or I get > pulled elsewhere). > > On Thu, Jan 4, 2024, 11:23 AM Jack McCluskey via dev > wrote: > >> Hey everyone, >> >> Following up on this, I do need help from a PMC

Re: [RESULT] [VOTE] Release 2.53.0, release candidate #2

2024-01-05 Thread Robert Burke
Going to try to get this done. Will report back when completed (or I get pulled elsewhere). On Thu, Jan 4, 2024, 11:23 AM Jack McCluskey via dev wrote: > Hey everyone, > > Following up on this, I do need help from a PMC member for the PMC-only > finalization steps ( >

Re: (python SDK) "Any" coder bypasses registry coders

2024-01-05 Thread Robert Bradshaw via dev
On Fri, Jan 5, 2024 at 9:42 AM Joey Tran wrote: > > > I think my original message made it sound like what I thought was confusing > was how `Any` works. The scenario that I actually think is confusing is *if a > user registers a coder for a data type, this preference will get ignored in >

Re: (python SDK) "Any" coder bypasses registry coders

2024-01-05 Thread Joey Tran
Oh actually, overriding the fallback coder doesn't actually do anything because the issue is not with the fallback coders in the registry but the fastprimitivescoder's fallback coder On Fri, Jan 5, 2024 at 12:42 PM Joey Tran wrote: > > I think my original message made it sound like what I

Re: (python SDK) "Any" coder bypasses registry coders

2024-01-05 Thread Joey Tran
I think my original message made it sound like what I thought was confusing was how `Any` works. The scenario that I actually think is confusing is *if a user registers a coder for a data type, this preference will get ignored in non-obvious situations and can (and in my scenario, has) result in

Re: (python SDK) "Any" coder bypasses registry coders

2024-01-05 Thread Robert Bradshaw via dev
On Fri, Jan 5, 2024 at 7:38 AM Joey Tran wrote: > I've been working with a few data types that are in practice > unpicklable and I've run into a couple issues stemming from the `Any` type > hint, which when used, will result in the PickleCoder getting used even if > there's a coder in the coder

(python SDK) "Any" coder bypasses registry coders

2024-01-05 Thread Joey Tran
I've been working with a few data types that are in practice unpicklable and I've run into a couple issues stemming from the `Any` type hint, which when used, will result in the PickleCoder getting used even if there's a coder in the coder registry that matches the data element. This was pretty

[ACTION REQUESTED] Help me draft the Beam Board Report for January 2024

2024-01-05 Thread Kenneth Knowles
Hi all, The next Beam board report is due next Wednesday, January 10. Please help me to draft it at https://s.apache.org/beam-draft-report-2024-01. The doc is open for anyone to edit. Ideas: - highlights from CHANGES.md - interesting technical discussions - integrations with other projects

Re: Setting up beam locally

2024-01-05 Thread Shunping Huang via dev
That's right. You need to put quotes (single quotes or double quotes) around .[gcp,test] since the square brackets are interpreted as a glob-pattern in shell. We will also need to add the quotes to the command listed in the beam wiki page:

Re: Setting up beam locally

2024-01-05 Thread XQ Hu via dev
Assuming you run this under beam/sdks/python, since I use zsh, I have to do this `pip install -e ".[gcp,test]"`. On Fri, Jan 5, 2024 at 1:33 AM G Gautam wrote: > Hi everyone, > > Need help in setting beam locally. > > When trying to setup locally > on entering this command: pip install -e

Beam High Priority Issue Report (51)

2024-01-05 Thread beamactions
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/29926 [Bug]: FileIO: