Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently logs from stdout and stderr can be displayed out of order when the streams (containers) or files (projects and executables) for each are processed and fed into the log viewer.
This PR partially addresses this by doing a couple of things:
The clearest way to see this in action right now is with the catalog (postgres) container in the repo right now. It has both stdout/stderr logs and they are currently written out of order. With this PR, they're written in order.
If timestamps or log level indicators are present, sorting/grouping will take place. But if they're not present, all log entries will just be written in the order they're received.
Project and executable logs do not currently have timestamps (and are not guaranteed to the way container logs are) but it is simple enough to add.
Note that for the moment the only timestamp format we support is RFC3339 (including RFC3339Nano used by docker logs). We can add more support in the future as needed.