David Elliott11/03/2022, 2:17 PM
infra? I’m finding that the agent creates the job + pod just fine (and it the flow + pod run through to completion) but after X seconds (per that timeout parameter) the agent logs
per this even though the job is mid-way through running? ie it doesn’t seem to have any negative effect on the flow, it’s just telling me the job didn’t complete even when the job is very much still running..? Feels like something’s not quite right, just wanting to understand what the intention is….
Job 'xxxxx': Job did not complete.
set because I was finding the pod (flow) logs were being intermittently streamed back to the agent which felt dodgy, and
appears to have stopped that, but now I have this error…
= false (so as not to stream the logs back to the agent) it skips the part where it follows the pod logs (presumably until the flow is completed) • in skipping that part, it jumps right to wait for job to complete section • however it appears to be exiting per the else clause after the
. • Feels like the intended behaviour is to wait until the job returns as completed, but it appears that the
is not yielding anything after a short period and the for loop exits prematurely, resulting in this error log… Any thoughts on why this might happen / whether it should be fixed?
Zanie11/03/2022, 4:01 PM
so it was declared incomplete
David Elliott11/03/2022, 4:05 PM
also wants to be False by default as well..? seems odd to have the agent streaming out the logs of its flows/pods..? in 1.0 I was quite used to the agent just being a creator / watcher of flow runs, rather than streaming the logs out
Zanie11/03/2022, 4:08 PM
David Elliott11/03/2022, 4:10 PM
setting to switch off the behaviour 🙂 it is there in the docs though so that’s on me!
Jarvis Stubblefield11/08/2022, 6:46 PM
Zanie11/09/2022, 5:07 PM