Loïc Mathieu

@anna-geller on https://github.com/kestra-io/kestra/pull/3570 we pass the task timeout to "remote" taks runners that have a `waitForCompletion` property, but for the Docker task runner we did nothing. I think this one...

I find how to dot it. We need to import `message` then define our message like this ``` const msg: Message = { content_type: "application/json", body: message.data_section(new Buffer(JSON.stringify(user), "utf8")) };...

The config endpoint is defined as is: ```java @Slf4j @Controller("/api/v1") public class MiscController { @Get("{/tenant}/configs") @ExecuteOn(TaskExecutors.IO) @Operation(tags = {"Misc"}, summary = "Get current configurations") public Configuration configuration() throws JsonProcessingException {...

@graemerocher indeed there isn't anything that seems to be able to cause such issue. We are rolling back to the old version of Micronaut, I'll confirm tomorrow if it fixes...

I can confirm that rolling back to 4.3.4 works in the environment where it causes the issue. I'll try to create a reproducer but as it seems "random" this may...

The last comment of @sdelamo is interesting, we had to switch to the ServerCookieDecoder implementation due to a bug in Micronaut 4 so we configured it to `io.micronaut.http.netty.cookies.NettyLaxServerCookieDecoder`. As far...

The reference issue we had we cookie parsing, it may be related to this issue: https://github.com/micronaut-projects/micronaut-core/issues/10435

The issue may be in Micronaut Security, there was changes in the JWT token validator and we do use JWT tokens: https://github.com/micronaut-projects/micronaut-security/compare/v4.6.6...v4.6.9

Don't know if it helps but we have the following cookie after login 

We reproduce the issue on one of our preview environment with only the JWT cookie, no other cookie exists. As it's a preview env we can experiment if someone has...