Juha
Juha
I'll review the tests before that.
Where we have timestamps: - Pipeline output logs. - Pipeline run list (lists the historical runs for pipeline). Probably best would be to allow setting timezone in configuration and create...
We also need to improve timestamp management on UI. Currently on some servers if I run the task I see it running 16 hours ago immediately. Once we have proper...
Implemented a fix in #68 Strategy: - Generate all timestamps in backend in UTC - Convert in frontend from UTC to local timezone.
We could add that to the `status.json` of the run. I'm not sure where it would fit nicely on the UI, maybe above/below the log-box.
We have been thinking to start using Jinja2 as the templating engine and they just [merged a tojson filter two weeks ago](https://github.com/pallets/jinja/issues/458). That would allow to do something like `{{...
First step would be to add timeout to bash_executor.py. There is `_timeout` in the `sh` package that we use to run the commands: https://amoffat.github.io/sh/sections/special_arguments.html?highlight=timeout#timeout @zbal looks ok to you? Ok...
I implemented the `_timeout` and set it to 1 hour for bash tasks. This is at least a partial solution for this issue.