-
Notifications
You must be signed in to change notification settings - Fork 0
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
dataclass_wizard.errors.UnknownJSONKey: A JSON key is missing from the dataclass schema for class Video
. unknown key: 'tags'
#75
Comments
Hi @KaneDM , thanks for opening this issue. I have to create a scheduled job that runs to make API requests, and then create an issue or attempt to fix code if there are any missing fields that are encountered.. this is on my bucket list for now. In the meantime, can you try setting env variable $ export RAISE_ON_UNKNOWN_KEY=0
$ <call script> https://github.com/rnag/wystia/blob/main/wystia/constants.py#L26 |
Hi @rnag, Appreciate the update. Thankfully, for my particular use case, it wasn't affecting any of the actual operations of the script (it even does what it's supposed to do on that line, just crashes after). I wrapped that part of the script in a try/except to catch the error and it's currently running fine. If you want me to try your proposed solution for testing purposes, let me know and I can do that. |
Yes, please try the proposed solution and let me know if it works. |
Not confident enough in setting env variables to know if I did that right, but if I go to line 26 of the file you linked and change |
Description
Crashed while running my Wistia upload/HTML dump script, which has worked previously. Code here:
https://github.com/KaneDM/wistia-upload-embed/blob/main/tvid.py
The video was uploaded successfully, and the thumbnail was successfully created and assigned, but something went wrong during the thumbnail assignment.
What I Did
Crashed on line 83 of my script, where I call
WistiaApi.update_video(vidid, thumbnail_media_id=tn.hashed_id)
.Appears to be the same kind of problem as issue #59.
The text was updated successfully, but these errors were encountered: