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

Jellyseer showing non-existing requests #1499

Open
1 task done
Joly0 opened this issue Mar 18, 2025 · 7 comments
Open
1 task done

Jellyseer showing non-existing requests #1499

Joly0 opened this issue Mar 18, 2025 · 7 comments
Labels
awaiting triage This issue needs to be reviewed bug Something isn't working

Comments

@Joly0
Copy link

Joly0 commented Mar 18, 2025

Description

Hey, i have a weird problem with the requests of my jellyseer instance:

Image

Image

Somehow it shows 2 requests, but there are no pending onces. Also no failed onces. There are just a lot of unavailable, available and and processing ones, but this is to be expected.
But where are those 2 are coming from? Can i somehow check this? Is this stored in a database somewhere?

Version

2.5.1

Steps to Reproduce

I have no clue

Screenshots

No response

Logs

Platform

desktop

Database

SQLite (default)

Device

None

Operating System

None

Browser

None

Additional Context

No response

Code of Conduct

  • I agree to follow Jellyseerr's Code of Conduct
@Joly0 Joly0 added awaiting triage This issue needs to be reviewed bug Something isn't working labels Mar 18, 2025
@fallenbagel
Copy link
Owner

Check the database. Could be two corrupted requests

@fallenbagel
Copy link
Owner

Could also be related to #1431

@Joly0
Copy link
Author

Joly0 commented Mar 18, 2025

Check the database. Could be two corrupted requests

Ok, so i was able to open the sqlite3 database using db browser for sqlite, but i am not sure what i should be looking for to figure out the problem. I do know how to work with sqlite3 databases, but i am not sure what i am looking for in there

@Makifun
Copy link

Makifun commented Mar 19, 2025

I also have this issue. I had it since Overseerr though but I migrated today and so I also migrated my "1" pending invisible request that I have had for a few years now.

I tried using sqlitebrowser and removed something that looked strange(no mediaId on one row) but it didn't make a difference.

Any hints of what could be a corrupted request? What it might look like? :)

@fallenbagel
Copy link
Owner

sct/overseerr#4100

@Joly0
Copy link
Author

Joly0 commented Apr 7, 2025

sct/overseerr#4100

Hey, this looks like the problem we are having. Is this also a thing in jellyseer and if so, will this be implemented aswell?

@fallenbagel
Copy link
Owner

sct/overseerr#4100

Hey, this looks like the problem we are having. Is this also a thing in jellyseer and if so, will this be implemented aswell?

The reason why i linked the pr means it's coming. Soon.

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 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants