Closed FrancYescO closed 2 weeks ago
This is almost like the opposite of burst. In burst, I am trimming. But perhaps, if there is no logs, I should try to find more logs?
a little workaround is to redo another request starting from the "previous to", but the best solution maybe is to keep searching for at least a line in the past before giving an empty result
This should be fixed with https://github.com/amir20/dozzle/pull/3230 but it's a little hard to test it. So I might just merge it unless you can figure out a way to easily test it @FrancYescO.
i'm not able to easy retest it as without optimization of https://github.com/amir20/dozzle/pull/3230 pretty often i get a full freeze of the UI, i'll keep an eye on it
btw it should be easy replicable when the log flow is not regular:
🔍 Check for existing issues
How is Dozzle deployed?
Standalone Deployment
📦 Dozzle version
8.2.1
✅ Command used to run Dozzle
NR
🐛 Describe the bug / provide steps to reproduce it
if the loadmore request put a
from
andto
timeframe with no logs you will be unable to load older logs.... you can keep try to scroll up but the request will be fired asking for logs in the same timeframe giving the same empty resulti'm sure there are some older log but i have no way to increase the timeframe to load as it will be guessed automatically
💻 Environment
NR
📸 If applicable, add screenshots to help explain your bug
No response
📜 If applicable, attach your Dozzle logs. You many need to enable debug mode. See https://dozzle.dev/guide/debugging.
No response