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
Describe the bug
High values are not shown on download latency chart. Some of my test results have high (pardon the repetition) "high download latency". To be specific, the 2 that are missing on a graph are 1006ms and 1102ms. This makes chart discontinuous.
To Reproduce
Steps to reproduce the behavior:
Somehow get a result with more than 1000ms (not sure for the exact value) high download latency.
Go to /admin aka Dashboard.
Scroll down to "Download Latency" chart.
See error.
Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):
OS: linuxserver/speedtest-tracker:0.23.1 container inside an ubuntu-server 24.04.
Architecture: amd64
Browser: macOS safari, iOS safari, macOS chrome, Windows chrome
Version 0.23.1
Screenshots
Logs
Results have no error messages.
Additional context
None.
The text was updated successfully, but these errors were encountered:
Wow! That was crazy fast! Like, you know, off the charts fast (pun intended). Thank you.
TBH, I've tried to find a bug myself, like searching for the 1000 constant or analysing RecentDownloadLatencyChartWidget. But my lack of experience in PHP made this too tough 🥲. I had hope that your charts were made with some kind of JS lib.
Describe the bug
High values are not shown on download latency chart. Some of my test results have high (pardon the repetition) "high download latency". To be specific, the 2 that are missing on a graph are 1006ms and 1102ms. This makes chart discontinuous.
To Reproduce
Steps to reproduce the behavior:
/admin
aka Dashboard.Expected behavior
A clear and concise description of what you expected to happen.
Environment (please complete the following information):
Screenshots
Logs
Results have no error messages.
Additional context
None.
The text was updated successfully, but these errors were encountered: