ghansham
ghansham
Does that mean all existing dags will have to be updated to mention the cmd shell to be unix shell (existing one) explicitly? Mostly things should work in mvdan also....
We are using linux mostly so we are depending on standard linux shell features only.
It will be interesting if we could have a verbose mode in dag execution which can save the verbose output in dag run log directory in a file named say...
For log messages we can open a log file where all messages get written: if _, ok := os.LookupEnv("DEBUG"); ok { var err error dump, err = os.OpenFile("messages.log", os.O_CREATE|os.O_TRUNC|os.O_WRONLY, 0o644)...
Earlier start time and end time for each step used to be a column. If we add that. We can do this by clicking column header
First of all this will be really interesting feature. Very much required. What happens to non scheduled runs which are running when scheduler stopped 1. Dagu going down 2. Machine...
One possible solution could be to use sub dag functionality and load dotenv files in those sub dags. I think you can pass these dotenv files as named params in...
There are chances we may need a trigger on file getting completely written.
Thinking beyond just file triggers, we can think of abstracting trigger. And create trigger events which may be related to files or even databases. And it we can bring this...
The original inotify had IN_CLOSE_WRITE for local disk. https://www.man7.org/linux/man-pages/man7/inotify.7.html But somehow absent in fsnotify. Don't know why? There are plain inotify wrappers in go https://github.com/illarion/gonotify