-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Events are not properly ordered #1846
Comments
We sort by newest first in the UI, but it looks like the events might have the same timestamp. |
@spadgett depends on the time granularity. As you can see in the command line output, they are properly ordered, that means that either they come in order from the API query, or that they have miliseconds granularity. In the web ui, there is no miniseconds granularity, so I guess that ordering of things that happens in the same second can be not in the real order they happened. |
As far as I can tell, the API response is coming back with only second granularity and the events are not returned in order. @fabianofranz How is the CLI sorting events? |
In |
I hope the API does return them sorted as otherwise would be awkward to look at a big list of events. |
Doing a build, I go to the events and see:
NOTE: Events are sorted by time in the UI.
Which don't make much sense in that order.
I verify that command line the events are ordered.
Version v3.6.0-rc0
The text was updated successfully, but these errors were encountered: