Re: beam/jackson NPE during test

I manually unwrapped a bunch of the code while debugging and synchronizing on ctxt worked in that case; I haven't built new beam artifacts. I can submit a PR (effectively just adding a synchronized block), but am/was unsure if beam maintainers had some other insight into the jackson-beam

P1 issues report (66)

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

Flaky test issue report (44)

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

Re: beam/jackson NPE during test

If I understand correctly, the documentation does imply that such synchronization at [2] should not be necessary and that [4] and [5] are correct. Of course it would be better if the docs said _how_ this guarantee is provided, or perhaps more than that it is a matter of restating it as a

Re: Swap gradle task.create() with task.register() if applicable?

+1 very good initiative. Kenn On Fri, Jan 28, 2022 at 7:27 AM Kerry Donny-Clark wrote: > Sounds great. Is there a Jira issue? Also, are you planning on > implementing this? > > On Thu, Jan 27, 2022 at 9:00 PM Brian Hulette wrote: > >> I'm +1 for this, it's frustrating to run into issues with

PulsarIO Connector

Hi folks, I have been working on the first version of PulsarIO Connector and I recently raised the following PR-16634 , I am sharing the PR here in order to get feedback and possibly a review from you. Thanks in advance. -- *Marco Robles* *|*