Loïc Mathieu

> That syntax forcing user to double the states definition is not acceptable from the UX perspective. We discussed this when we allowed the flow trigger to listen for non-terminated...

This setting is not only for preconditions, it's for all possible conditions on the Flow trigger. By the way, a Flow trigger without conditions will work for this use case.

As a side note, using a `pauseDuration` instead of `timeout` on the Pause task would do the same than using `allowFailure: true`.

It may be another bug; please open a new issue with a flow reproducer. Be sure to test it on the latest version first.

@rishi-jat looking at the PR it seems this is not finished. If so, can you make your PR a draft PR so we know when it's ready to be review?

Hi, thanks for your contribution. Can you remove all your formatting change? They are not on par with our standard formatting and clutter the PR so it's hard to see...

Ideally we should validate the Docker environment before using it. There may be a way to do it via the client, I know testcontainers do it for ex.

@yawkat the same issue occurs if I disable the bean introspection module. @graemerocher we have our own Jackson mapper that we use in a bunch of places (JSONB support, Kafka,...

@graemerocher @yawkat we hit this issue again when trying to use the OpenLineage official client that uses the Blackbird module. You said that it may be a bug in Jackson...

See https://github.com/OpenLineage/OpenLineage/issues/4049