-
-
Notifications
You must be signed in to change notification settings - Fork 61
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: Dr4ft Crashing on JSON import #1432
Comments
GYP20.json
|
GYPO.json
|
We should really have another way to handle custom sets. We shouldn't save them in the DB but keep them just for the session the game. |
I'm a big fan of JSONschema for validating custom inputs. Happy to help someone set that up if validation on this entry point is something useful I've used |
We had another crash, caused by a user upload. See #1443 |
Seems unlikely to be a json issue, it's more likely to be related to that "url", it seems formatted wrong. |
after a LOT of trial and error I concluded the cause of the problem is uploading the same card name in two different sets. Simple repro steps:
|
This is really good to know. I'll try and hunt down why this causes a crash after I fix the bugs in the new export options |
Today I tried to reproduce it using the xml format using this minimal xml: <cockatrice_carddatabase>
<cards>
<card>
<name>test</name>
<set rarity="common">TEST1</set>
<prop></prop>
</card>
</cards>
</cockatrice_carddatabase> But the error didn't happen if I uploaded the same xml with TEST2 as the set afterwards, instead if I then used the json with TEST2 it did break. This means that this bug is related to the json import. Also the step 1 in my previous repro steps can be replaced with this xml, it only breaks on step 2. (note this isn't a valid xml for cockatrice, just the minimum for dr4ft) |
I also noticed something else, uploading the same card in the same set with new properties does not update the card or overwrite it, instead just nothing happens and the old card stays. |
Error seen in the logs, that we should investigate:
And what probably crashed the service, as there are no more relevant logs after this:
The text was updated successfully, but these errors were encountered: