Skip to content

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

@Fulguritude

Description

@Fulguritude

{"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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions