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 472 comments of Loïc Mathieu

Store Kestra version inside the database

Implementation idea: we can use the settings table for that.

Killing workflow executions does not work if workflow is in Retry

Killing is inherently racy, you send a killing command to the executor that will kill the execution. But if during the time you click on the UI and the time...

feat(system): use available processor count number of executor threads

Will be merged when our deadlock issues would be fix to avoid making things worst. See #9778

Unable to use Blackbird with Micronaut

Micronaut 4.9 and Jackson 2.20.

Unable to use Blackbird with Micronaut

Unfortunatly, it cannot seems to be reproduced easily at least with a simple Micronaut project using Jackson. The only way I can reproduce it is buy adding this module to...

[Kestra EE] SQL Triggers broken in 0.19

I tried it with 0.19.2 (and develop) and I cannot reproduce the error. Which backend do you use, JDBC or Kafka? Do you also use multi-tenancy?

[Kestra EE] SQL Triggers broken in 0.19

Fixed by https://github.com/kestra-io/plugin-jdbc/pull/399 It will be included in today 0.19 release

fix(system): possible deadlock on worker_job_running table

Closing it for now in favor of https://github.com/kestra-io/kestra/pull/9102 as there is a risk that worker job was not resubmitted if locked but not processed. We may revisit that later.

Don't run CI on draft PR

Hi @phoenix24 in this repository only it's OK. I'll review it next week as we are in the preparation for the next release so we won't touch the CI now.

Flows set to execute later from UI don't show up in Dashboard "Next Scheduled Executions"

Next Schedule Execution are executions that will be created by triggers, which is something predictable. When you start an execution "for later" or a subflow execution "for later" this is...