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

Better Way to handle 500: Internal Server error #1219

Open
1 task done
dj0024javia opened this issue Jan 4, 2025 · 0 comments
Open
1 task done

Better Way to handle 500: Internal Server error #1219

dj0024javia opened this issue Jan 4, 2025 · 0 comments
Labels
awaiting triage This issue needs to be reviewed enhancement New feature or request

Comments

@dj0024javia
Copy link

Description

So I am from India and i get a lot of 500: Internal Server error when scrolling through the page. Sometimes it loads 4 5 pages without any issues but when a get an error, all the search results are gone, even the ones already loaded are gone. I know this is an ISP/DNS issue but from the UI perspective, IMO, the already fetched data should stay as it is and the error message should be shown at the last, (where we can also show loader). What do you think on this?
I can spin up a PR but only if it seems to be a good idea and only the maintainers are onboard with it.

Desired Behavior

See Above.

Additional Context

image

Code of Conduct

  • I agree to follow Jellyseerr's Code of Conduct
@dj0024javia dj0024javia added awaiting triage This issue needs to be reviewed enhancement New feature or request labels Jan 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
awaiting triage This issue needs to be reviewed enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant