ks
> around between SDKs and Runners though. But in some cases it would be
> easier for the SDK, eg to ensure VersionA of a transform is used vs
> VersionB, based on the existing transforma used in the job being updated.
>
>
> On Fri, Oct 27, 2023, 7:50 AM Kellen Dye via dev
> Auto is hard, because it would involve
> querying the runner before pipeline construction, and we may not even
> know what the runner is at this point
At the point where pipeline construction will start, you should have access
to the pipeline arguments and be able to determine the runner. What
> wrote:
>
>> Hi Kellen, thanks for figuring this out. Have you implemented
>> synchronizing on ctxt, or do you need someone else to try that?
>>
>> On Fri, Jan 28, 2022 at 12:36 AM Kellen Dye wrote:
>>
>>> We (Spotify) are experiencing flaky
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
