-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Version 1.7.8 error Newtonsoft.Json.JsonSerializationException: Cannot deserialize the current JSON array #481
Comments
Thanks for that... I'm doing some testing at my end, but wondered if you could help me narrow it down. If you look at the surrounding logs, does it indicate which ROM it failed on? If so, would you be able to provide the full file name and hash? |
These are the full log lines.
|
@Bladestar2105: Would you be able to update to v1.7.9-preview.1? It will cause all DATs to be reimported. On the settings page, you should see the "Signature Ingestor" process running. Once completed, would you then be able to manually run the Rematcher service, and let me know if you get any errors again? |
With the updated version it works fine! |
Great news! :) Thanks for the feedback! I'll push a full release by the end of (my) day. |
There is another error now with updated version 1.7.9.
|
Ok, looks like it's the same error. Leave it with me. |
Hi @Bladestar2105; so it looks like the issue is around loading the attributes the come from the DAT's when loading a list of ROMs, or an individual ROM. I'm not able to replicate it myself, but it appears to be around a badly formatted entry in the ROMs table. The fix I've applied in v1.7.10-preview.1 (released just a few minutes ago) is to wrap loading the attributes in a try/catch. An error will still be logged (with some more detailed error messaging), but it shouldn't cause any issues anymore other than an extra log message. Would you be able to install v1.7.10-preview.1 and try loading those effected ROMs again? Edit: if you see the new error message, would you be able to send it through to me? I'd be interested to see what's in your database to see what needs to be fixed to permanently resolve this error. |
Okay now it seems that it crashes:
|
Is Gaseous server just endless restarting is it? Nothing I changed in this preview build should have caused that to happen. Is the database container still running? Can you post your compose file? When you performed the update to the preview, how did you apply it? Could you try |
Nevermind, it works now. In the folder with the ROMs I also had the BIOSes. I think this was causing the error. 😄 |
That's good to hear :) Are you ok with closing this issue? If so, I'll release this current preview. |
Fixed and closed 😊 |
Hello,
with the newest version I get this error after Library Scan:
The text was updated successfully, but these errors were encountered: