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

[Bug Report] Sorting Scenes by Title yields Status Code 422 Message #1572

Closed
Cygon opened this issue Jul 12, 2021 · 3 comments · Fixed by #1607
Closed

[Bug Report] Sorting Scenes by Title yields Status Code 422 Message #1572

Cygon opened this issue Jul 12, 2021 · 3 comments · Fixed by #1607
Labels
bug Something isn't working help wanted Extra attention is needed investigate Investigation needed
Milestone

Comments

@Cygon
Copy link

Cygon commented Jul 12, 2021

Describe the bug
When I sort my scenes by "Title", I am seeing the following message:

Response not successful: Received status code 422

This error started without any update to the Stash application. I first noticed it with Stash 0.7.0 and initially, could go past it by simply hitting the reload button in my browser. That stopped working at some point. Upgrading to Stash 0.8.0 didn't change the issue.

The log shows json: error calling MarshalJSON for type json.RawMessage: invalid character '+' looking for beginning of value at the same time as the status code message.

To Reproduce
Steps to reproduce the behavior:

  1. Select the "Scenes" tab
  2. Change the default "Date" search criterion to "Title"
  3. (probably needs a secret ingredient, i.e. a movie with a problematic filename)
  4. Observe status code 422 being reported

Expected behavior
The scenes should be listed as usual, sorted by their "Title" field

Screenshots
stash-status-code-422

stash-error-422-logs

Stash Version: (from Settings -> About):
v0.8.0 0x417ad4 2021-07-01 23:59:02

Desktop (please complete the following information):

  • Gentoo Linux (stable, amd64) running as LXC container under QNAP Linux kernel 4.14.200
  • Firefox 78.10.1esr (amd64)

Smartphone (please complete the following information):
nope

Additional context
Since the logs show a JSON issue with a '+' character, I tried searching for this specific character. Entering a plus character in the search box does not reproduce the error and lists 12 scenes.

@Cygon Cygon added the help wanted Extra attention is needed label Jul 12, 2021
@jocphi
Copy link

jocphi commented Jul 25, 2021

I had the same error coming up on a scene (I used number of pages and pagenumber in url to find the entry that wouldnt show up).

I then used DB-browser (https://github.com/sqlitebrowser/sqlitebrowser) to take a look at the entry causing this error. The only difference to all the other scenes in the database was - the framerate was set to "Inf.". After resetting the framerate to "NULL" the scene didnt break the pageview.

The video codec on that particular file was vp6f.

Maybe something to look into?

@Cygon
Copy link
Author

Cygon commented Aug 1, 2021

I tried that and found one scene, imported from a .flv file with framerate "inf". I just wrote "30" in there because I didn't see any NULL rows.

ffprobe shows this for the file in question:

    Stream #0:0: Audio: adpcm_swf, 22050 Hz, stereo, s16, 176 kb/s
    Stream #0:1: Video: flv1, yuv420p, 448x336, 25 tbr, 1k tbn

However, that didn't seem to change anything (I stopped stash, replaced the database, started it again and Shift+Reloaded the browser, just in case).

I also noticed many rows had empty strings in the details and url columns and replaced those with NULL.

Surprisingly, after that change, I can navigate my scene directory again.

@jocphi
Copy link

jocphi commented Aug 1, 2021

I think there are more fields in the databasee that need additional sanity checks.
At least we got it working again :-)

@WithoutPants WithoutPants added bug Something isn't working investigate Investigation needed labels Aug 2, 2021
@WithoutPants WithoutPants added this to the Version 0.9.0 milestone Aug 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed investigate Investigation needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants