brian-mulier-p

@graemerocher do you manage to have a working example with that above sample based on [this](https://github.com/kestra-io/kestra/issues/2844#issuecomment-1984065070) ? I don't :cry:

Since we're doing a lazy fetch, moving the filtering to an endpoint is currently not possible (or at least it's a pain to implement). It's not a very costful op...

We should auto-detect if it's a ionl (maybe also add that to json function). Basically the usecase is simple, a user gets some ion-formatted data (in the usecase a user...

I agree but I believe it's a non-sense that we don't have a ion function to parse it while every task output is in such format. Even though it's not...

As said on [slack](https://kestra-io.slack.com/archives/C03FQKXRK3K/p1712566217380399?thread_ts=1712335044.992799&cid=C03FQKXRK3K) you may have a corrupted ~/.ssh/known_hosts file as I can't reproduce the issue even if deleting it

I tried locally but erasing my whole known_host file

Following [this](https://github.com/micronaut-projects/micronaut-security/issues/1683), it seems that core > 4.3.13 removed the failing cookie decoder which solves the issue. Otherwise adding [this service](https://github.com/kestra-io/kestra/blob/9f0f312ebda12e57857038188eb3f5924d7256b3/webserver/src/main/resources/META-INF/services/io.micronaut.http.cookie.ServerCookieDecoder) will fix the issue for those in lower versions

I guess it's the same issue as https://github.com/kestra-io/kestra/issues/2364 See https://kestra-io.slack.com/archives/C04HTFM3VL6/p1709724906043089 but there is 2 issues to tackle: - https://github.com/kestra-io/kestra/blob/c15e971ed6884cfb8b4f836aac43ea4a75a39fd2/cli/src/main/resources/application.yml#L70 which leads to some property erasure in case of default values...

I have to test it again but looks strange because if that was the case it would look not working at all :thinking:

Draft as it needs more work to support runtime hot reload properly updating class loaders