We (Spotify) are experiencing flaky tests on beam 2.35.0 as a result of
NullPointerExceptions during pipeline construction.
Stacktrace [1]. Root cause appears to be multiple threads
accessing DeserializationContext from
ValueProvider.Deserializer.deserialize [2] which, according to the javadocs
+1 to starters for Kotlin and Scala too. Scala at least as sbt as the
idiomatic build tool (as of like 10 years ago...) so a fully idiomatic repo
would look different and be helpful.
On Tue, Jan 25, 2022 at 10:54 AM David Cavazos wrote:
> We could also have Kotlin and Scala starter projects. I
Welcome to the team Danny! Very happy to have you.
On Wed, Jan 26, 2022, 4:11 PM Ahmet Altay wrote:
> Welcome!
>
> On Wed, Jan 26, 2022 at 2:39 PM Alexey Romanenko
> wrote:
>
>> Hi Danny,
>>
>> I added you as a contributor.
>> Welcome!
>>
>> —
>> Alexey
>>
>> > On 26 Jan 2022, at 22:53, Danny
This is your daily summary of Beam's current P1 issues, not including flaky
tests
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20priority%20%3D%20P1%20AND%20(labels%20is%20EMPTY%20OR%20labels%20!%3D%20flake).
See
This is your daily summary of Beam's current flaky tests
(https://issues.apache.org/jira/issues/?jql=project%20%3D%20BEAM%20AND%20statusCategory%20!%3D%20Done%20AND%20labels%20%3D%20flake)
These are P1 issues because they have a major negative impact on the community
and make it hard to