ghansham
ghansham
I think historical timeline was discussed earlier as well: https://discord.com/channels/1095289480774172772/1095291629344149544/1322389653449474070 @kriyanshii has implemented status wise search. If it is worth it, I think she would be happy to submit a...
I also feel if we can improve the history data structure to include status in history filename, things may improve drastically. But let us keep this on our todo list...
Retry should be happening only after last retry is complete. I am not sure if it is a race condition. If each retry step is closing log file, we should...
It's better to keep a single log file but at the start of every retry we should print some message mentioning retry no. X (Start Time: ......)
@yottahmd I like the part that error column is showing a message and not simply the exit code. Can we get the error message generated by a step in this...
we can try displaying last line (or last N bytes as you recommend) of the stderr stream. And the link to open the stderr stream can be moved here from...
We are building a queueing system within dagu which actually allows user to manage the jobs in dagu. But we have a configurable parameter called waiting queue length which controls...
This feature may be more useful for non cron dags where the execution time is relatively more and you have data received from sensors at regular intervals for processing. Basically...
One of the other complex scenario can be that one dag generates some output which is sent via mail to user. User clicks on the link sent via email which...