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
LRR Version and OS
Version 0.8.0, "Black Tie White Noise" OS: Windows 10
Bug Details
The total entries count shows a number above my current filecount, I executed the clean database and reset search cache commands but it remains the same. This was working correctly in 0.7.9 so not sure if is a visual bug or old entries that were deleted before and the clean database command can't catch.
Matching Logs
None
Screenshots
This is my current filecount
and this is what is displayed in the application without any filters applied
as you can see the total filecount goes up but the filtered count is the correct one.
The text was updated successfully, but these errors were encountered:
I'm aware of this issue; I made the total count use the keycount of the redis database so I can save an extra DB call, but it's slightly incorrect due to the DB having a few more keys for configuration.
my$total = $redis->dbsize; #TODO this is incorrect by a few keys due to the config keys being strewn about on the DB root.
The total count is just used for display so there shouldn't be undeletable entries strewn about or anything like that. I'll figure out a better way to handle this in a next release.
LRR Version and OS
Version 0.8.0, "Black Tie White Noise" OS: Windows 10
Bug Details
The total entries count shows a number above my current filecount, I executed the clean database and reset search cache commands but it remains the same. This was working correctly in 0.7.9 so not sure if is a visual bug or old entries that were deleted before and the clean database command can't catch.
Matching Logs
None
Screenshots
This is my current filecount
and this is what is displayed in the application without any filters applied
as you can see the total filecount goes up but the filtered count is the correct one.
The text was updated successfully, but these errors were encountered: