Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When grouped, the last crash is given the same "ago" time as the first crash #37

Open
uli-on opened this issue Oct 20, 2021 · 5 comments
Labels
bug Something isn't working properly

Comments

@uli-on
Copy link

uli-on commented Oct 20, 2021

Prerequisites:
Settings "Combine same apps" and "Combine same crashes" are both activated.

Whenever crashes are listed from several dates, there's a weird thing happening, that looks like the topmost crash is restacked to the very bottom in that app's group (or a duplicate is made and restacked to bottom? Can't tell yet because of #36).

@uli-on
Copy link
Author

uli-on commented Oct 20, 2021

FYI: It must not be several "dates", literally taken, it's also enough if there's any time difference at all, like "just now" and "1 min ago"

@uli-on
Copy link
Author

uli-on commented Oct 20, 2021

Nope, no duplicates, just the wrong position. Just found several prooves.

@TacoTheDank TacoTheDank changed the title Weird order of crashes Selecting crashes doesn't include number of crashes in a grouping Oct 20, 2021
@TacoTheDank TacoTheDank added the bug Something isn't working properly label Oct 20, 2021
@TacoTheDank TacoTheDank changed the title Selecting crashes doesn't include number of crashes in a grouping Weird order of crashes Oct 20, 2021
@TacoTheDank
Copy link
Owner

Edited wrong issue smh

@TacoTheDank TacoTheDank changed the title Weird order of crashes When grouped, the last crash is given the same "ago" time as the first crash Apr 29, 2022
@TacoTheDank
Copy link
Owner

Notes for myself:

What happens is that a new crash comes in and is put at the top of the list. For some reason, the crash at the bottom of the list is given the same "ago" time as the newest crash, even though the crashes are ordered by age (from top to bottom).

When "combine same apps" is disabled, this issue does not manifest (for some reason).

unbiaseduser pushed a commit to unbiaseduser/Scoop that referenced this issue Oct 24, 2022
@opusforlife2
Copy link

opusforlife2 commented Dec 2, 2022

I've been seeing this for ages and finally decided to get off my ass and report it. Turns out...

BTW if you delete the newer crash the old one gets back its correct time-ago.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working properly
Projects
None yet
Development

No branches or pull requests

3 participants