Expose message timestamps #109
Labels
Milestone
Comments
|
This field is actually required for progress messages as I've currently implemented them to work properly. I could change the implementation, but it would be really nice if the message timestamps were simply exposed instead. Either unix time in milliseconds, alternatively time since job started in milliseconds, would be fine. |
josteinaj
added a commit
to daisy/pipeline-webui
that referenced
this issue
May 25, 2016
- load messages separately from the rest of the job info - estimate timestamps. see: daisy/pipeline-framework#109 - use message depth to nest messages in the log; depth 0 and 1 are top-level, other levels are nested - all messages are displayed at the top regardless of message depth - filter out messages that are empty - ability to toggle sub-message lists - top-level messages gets colored red or yellow (error/warning) if one of its child messages have that color
josteinaj
added a commit
that referenced
this issue
Jun 21, 2016
bertfrees
pushed a commit
that referenced
this issue
Apr 11, 2017
bertfrees
pushed a commit
that referenced
this issue
Jul 31, 2017
bertfrees
pushed a commit
that referenced
this issue
Jan 8, 2018
bertfrees
pushed a commit
that referenced
this issue
Jan 9, 2018
bertfrees
pushed a commit
that referenced
this issue
Jul 5, 2018
|
This was fixed in 6fbf82f. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Messages (used for the job execution log) in the framework each seem to have a
timeStamp. It could be useful if this field were exposed through the Web API. Possibly as an integer: the amount of milliseconds since the job was started.The time for job created/started/finished would also be useful if possible.
The text was updated successfully, but these errors were encountered: