Loïc Mathieu

icon indicating a website link https://www.loicmathieu.fr icon indicating an email [email protected]

icon company @kestra-io icon location Lille, France icon location Lead Software Engineer @kestra-io, Java & JVM passionate, performance, OSS contributor (mainly Quarkus). I like to learn stuff and share what I learned.

Results 473 comments of Loïc Mathieu

The `system` namespace is visible even when listing "User" flows

@Mahitej28 you can work on the issue but I'm not sure what needs to be done, if you didn't find it by yourself maybe find an easier issue to work...

Add "See all" options to Executions in progress + Next scheduled executions

@Chaitanya-087 it seems you don't have the correct Java version, we're using Java 21. Please ask help on our Slack contributors channel for help on contributing.

Add TerminateSuccessfully task to immediately end the execution in a Success state without processing any downstream tasks

@Malaydewangan09 please open a PR with what you have so far, it's too complex to explain how our Executor work so I'll take it over from their. Thanks a lot...

Autocompletion for the "error" property is aware of taskId but not aware of message and stackTrace properties

Oh yes! Sorry, I forgot them. We'll have them tomorrow

Add a Pebble function to generate a random number

Hi, thanks to volunteer to implement this. Pebble functions are implemented here: https://github.com/kestra-io/kestra/tree/develop/core/src/main/java/io/kestra/core/runners/pebble/functions You need to add a new class and configure it here: https://github.com/kestra-io/kestra/blob/develop/core/src/main/java/io/kestra/core/runners/pebble/Extension.java#L123 Don't forget to add a...

UI Execution logs tab shows a task run as Failed when its state is Success due to `allowWarning: true`

In fact, the discrepency is between the task run and the attempt, as here it's the attempt state that is displayed. For me it's correct: there is a fail attempt...

Preconditions.where with STATE field is missing autocompletion for state values

Yes, it's because value/values are dynamic and non-typed inside the where filter. There is no link between the field and the type of the value attribute in a where filter.

Add pluggable system to allow concatenating ForEachItem + ForEach outputs

If we do this, we should also provide the same for ForEach as this task also need to be able to concatenate its results (its subtask outputs). See for example:...

Add pluggable system to allow concatenating ForEachItem + ForEach outputs

This should fix https://github.com/kestra-io/kestra/issues/4996

Add displayName to flow level outputs

Reverted as it causes issue with subflow with outputs, see https://github.com/kestra-io/kestra/issues/6308