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

JSON parse runs forever when nan values are present in big file #19

Open
Fulguritude opened this issue Jul 29, 2021 · 1 comment
Open

Comments

@Fulguritude
Copy link
Collaborator

{"STRING": nan} and {"STRING": NaN} caused errors that would make JSON_parse hand indefinitely, taking up a lot of resources. Making these into {"STRING": ""} resolved the problem

@Fulguritude
Copy link
Collaborator Author

Other example of similar behavior

{"ENTITY":"<2896870736|4003528566|7270378501333190455>","OUTLET":"<3264642374|2475051834|4973027080943659186>","AUXILIARY":"<552523710|3814301558|6239292482561096750>","ANCILLARY":"<68004|2818859688|16085322268459127022>","CONTEXT":Context.AVESTERRA,"CLASS":Class.AVESTERRA,"SUBCLASS":Subclass.CART,"METHOD":Method.SET,"ATTRIBUTE":Attribute.MAIN,"INSTANCE":16,"NAME":"kz2Ku5SYoW1b5","TAG":Tag.STRING,"VALUE":"2b4PrQxYCx","INDEX":353,"COUNT":102,"PRECEDENCE":6,"PARAMETER":58,"MODE":Mode.AVESTERRA,"EVENT":Event.TIMER,"TIMEOUT":23,"ASPECT":Aspect.OBJECT,"AUTHORITY":"aa13079510c642d39bb87ab7080b8ff7"}

Probably a raw string (no quotes) after a colon that's the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant