paulgrainger85

### Describe the issue Receive an error executing the following flow on 0.16.6 on windows standalone ``` id: test namespace: blueprint tasks: - id: export type: io.kestra.plugin.jdbc.postgresql.Query url: jdbc:postgresql://postgres_server:5432/postgres username:...

### Describe the issue Executing a flow in Windows shows a warning message ```yaml id: myflow namespace: myteam description: execute sample flow labels: env: dev project: myproject tasks: - id:...

### Describe the issue Executing the following flow on Windows results in the following statement printed in the log: ```log C:UserspaulAppDataLocalTemp1ImK0NcqbsxIcmzIlGsNUa14572494380012919038.tmp ``` The expected output would be ``` C:\Users\paul\AppData\LocalTemp\1ImK0NcqbsxIcmzIlGsNUa\14572494380012919038.tmp ```...

### Describe the issue I am unable to configure the KubernetesTaskRunner to use GKE. I am following the steps [here](https://kestra.io/docs/concepts/task-runners/types/kubernetes-task-runner) ``` kubectl config view --minify --flatten apiVersion: v1 clusters: -...

### Issue description The `id` and `type` parameters are duplicated in the documentation, e.g. 

Hide deprecated features by default

2

## Next Steps We will: - [ ] not show deprecated plugins in the Editor's autocompletion (will be complex) - [ ] we will also filter them out in the...

As a follow-up to https://github.com/iree-org/iree/pull/17710, this patch renames the compiler target backend from `ROCM` to `HIP` to be consistent with driver. User-facing changes: `IREE_TARGET_BACKEND_ROCM` to `IREE_TARGET_BACKEND_HIP` `iree-hal-target-backends=rocm` to `iree-hal-target-backends=hip`

### Describe the issue Define these 2 flows ``` id: parent_flow namespace: sales tasks: - id: exec_subflow type: io.kestra.plugin.core.flow.Subflow namespace: sales flowId: subflow_test inputs: myfloat: 0.5 ----- id: subflow_test namespace:...

Execution chart shows Invalid date

2

### Describe the issue Add the following flow and wait a few minutes for data. Then view Executions for past 5 minutes (e.g. http://localhost:8080/ui/executions?scope=USER&timeRange=PT5M). All x-axis values show "Invalid Date"...

Add pebble function to access taskrun value for which the task failed in ForEach

1

### Feature description Take the example flow here. If this flow breaks during an iteration of ForEach, we should be able to access the value at the current `{{taskrun.value}}` ....