You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love the "waiting for new logs" spinner, but one thing I liked about the previous iteration was that it told me explicitly when it had reached the end and there were genuinely no new logs to present. Currently, it seems that the spinner is shown at all times, whether it's actively loading new logs to present, or truly waiting for new logs to show up. Is it possible to differentiate somehow between being caught up to the present time, vs loading more logs to display?
The text was updated successfully, but these errors were encountered:
It is shown at all times because it is checking for new logs every 500 ms. It never really stops.
I tried this out and it ended up feeling more like a bug with the spinner as it was stopping and starting a lot and felt like the spinner was just breaking and stuck in a loop.
I had considered adding some kind of "Last Checked" like how we do for stats.
I love the "waiting for new logs" spinner, but one thing I liked about the previous iteration was that it told me explicitly when it had reached the end and there were genuinely no new logs to present. Currently, it seems that the spinner is shown at all times, whether it's actively loading new logs to present, or truly waiting for new logs to show up. Is it possible to differentiate somehow between being caught up to the present time, vs loading more logs to display?
The text was updated successfully, but these errors were encountered: