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

Inbox sometimes gets stuck loading infinitely when "unread only" is on #1544

Closed
Sjmarf opened this issue Dec 27, 2024 · 7 comments · Fixed by mlemgroup/MlemMiddleware#121 or #1784
Closed
Assignees

Comments

@Sjmarf
Copy link
Member

Sjmarf commented Dec 27, 2024

This is still an issue in some cases

@Sjmarf Sjmarf added the bug label Dec 27, 2024
@Sjmarf Sjmarf added this to the v2.0 milestone Dec 27, 2024
@Sjmarf Sjmarf assigned Sjmarf and unassigned Sjmarf Dec 27, 2024
@Sjmarf Sjmarf removed the bug label Jan 23, 2025
@Sjmarf
Copy link
Member Author

Sjmarf commented Feb 11, 2025

Repro:

  • Start with the "unread only" switched off
  • Mark only one item as unread
  • Toggle "unread only" on
  • Observe that loading symbol gets stuck

@Sjmarf
Copy link
Member Author

Sjmarf commented Feb 21, 2025

I'm able to repro this again 🤔

@Sjmarf Sjmarf reopened this Feb 21, 2025
@EricBAndrews
Copy link
Member

Hmm, I was able to reproduce once but can't do it again. It was the same issue (loader got stuck in .idle), but I'm not sure how it got there 🤔

I'll put the "load more" button back in as a fallback for this--I don't love it as a band-aid but I'm stumped on this one. Maybe it'll go away with these planned changes

@Sjmarf
Copy link
Member Author

Sjmarf commented Feb 21, 2025

I can consistently repro this using the steps in my comment above on both of my accounts 🤔

@EricBAndrews
Copy link
Member

Yeah, I had it consistently until I stepped through in the debugger and now I can't get a single repro

@EricBAndrews
Copy link
Member

Can you try to repro on eric/idle-debugging? I've added a bunch of test prints that may shed some light.

@EricBAndrews
Copy link
Member

Band-aid fix is in place so I'm taking this off 2.0, but keeping it open because the root cause is still unknown

@EricBAndrews EricBAndrews removed this from the v2.0 milestone Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants