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

One instance timing out means I can't look at feed or list of subscribed communities #501

Open
Erikatharsis opened this issue Aug 28, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@Erikatharsis
Copy link

Windows 10, ASUS TUF Gaming F15, Liftoff 0.10.10

I'm signed into two instances. When one of the instances timed out earlier today — that's at least what I think caused this — going to the "everything" feed just showed a little spinning loading ring. When this happened, I went to look at an instance feed of an instance I knew wasn't timed out, but alas, the spinning ring was still there, and I think was eventually replaced with something along the lines of "unknown error". When I went into my list of subscribed communities, the spinning ring was there as well — and was eventually replaced by some sort of 504 error message involving the Lemmy API. Upon starting and restarting Liftoff, the feed from the working instance loaded just fine — it was only after attempting to open the everything feed that the working instance's feed also broke.

What I would at least like to happen is that if one instance is to time out, that attempting to open the everything feed or subscribed communities list would give a little message saying something like "[instance name] is unresponsive; disabling temporarily", essentially ignoring that instance until it becomes responsive again.

@Erikatharsis Erikatharsis added the bug Something isn't working label Aug 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant