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
{{ message }}
This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
Describe the bug
In the Logs UI, when you let the logs to generate past the height of the logs container, it will show a box with a down arrow and the count of new logs shown below the visible container. Clicking on the box will scroll down to the most recent log message. However, when there are more logs, the box will appear again with an incorrect count.
Steps to Reproduce
Navigate to the Logs tab in the UI
Wait for the log lines to populate past the visible container
You should see a box on the top right corner of the logs container with a down arrow and a count of new log lines
Click the box and it scrolls down to the most recent log message
Wait again and you'll see the box appear with the count starting at a much higher number
Expected behavior
The count to start back up from the beginning
Waypoint Platform Versions
Additional version and platform information to help triage the issue if
applicable:
Waypoint CLI Version:
Waypoint Server Platform and Version: (like docker, nomad, kubernetes)
Describe the bug
In the Logs UI, when you let the logs to generate past the height of the logs container, it will show a box with a down arrow and the count of new logs shown below the visible container. Clicking on the box will scroll down to the most recent log message. However, when there are more logs, the box will appear again with an incorrect count.
Steps to Reproduce
Expected behavior
The count to start back up from the beginning
Waypoint Platform Versions
Additional version and platform information to help triage the issue if
applicable:
docker
,nomad
,kubernetes
)aws/ecs
,pack
,azure
)Additional context
https://user-images.githubusercontent.com/107074/115421818-ece32000-a1c1-11eb-9210-7901e9491fa7.mov
The text was updated successfully, but these errors were encountered: