Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Web interface showing "0 messages found" when specifying absolute time stamp #1266
When I specify an absolute timestamp in the web interface and search, I always get "0 messages found".
Elasticsearch query before absolute time selection:
For some reason it seems to be "stuck" at UTC, since the time here (and the time zone config) it set to CEST, 2 hours later that is.
Elasticsearch query after time selection:
Time zone info:
I've tried that, didn't make a difference at the time.
After some more trial and error I found that restarting the browser and clearing all cache/cookies after rebuilding solved the issue. I don't know if this really can be classified as a bug, but users should probably be made aware of this if someone else runs into the same issue and rebuilding the index doesn't make the trick right away.
@huksley Ok, thanks.
If the former is the case, you might want to turn on
So I'm actively having this issue when the following takes place:
Absolute time rang search is empty, BUT manually performing recalculate index ranges fixes it until the bug occurs again.
IF a new index is created and the oldest index is not deleted based on retention rules, this bug does not occur.
Is this what is being addressed in Fix several index retention problems #1208 ? I ask because all issues related to this appear to be closed, yet this issue is not resolved.
Edit it appears #779 is still open in reference to this.