Currently, when I have a new batch of PFDs and one of them is causing an issue with the parser, pfd-parser simply explodes trying to execute _(filing.save(dataPath)) (https://github.com/PublicI/pfd-parser/blob/master/bin/pfdparser#L19) due to filing being undefined.
It's very unclear from traceback which filing is causing the issue due to the streaming nature of the tool and the file information is lost somewhere inside of the parser.
I'm trying to unwind this so that when there is some kind of issue, it gets caught and reported at the source of the error itself where there is still context around the actual source file. Logging this here because it's been a persistent issue.
Currently, when I have a new batch of PFDs and one of them is causing an issue with the parser, pfd-parser simply explodes trying to execute
_(filing.save(dataPath))(https://github.com/PublicI/pfd-parser/blob/master/bin/pfdparser#L19) due to filing being undefined.It's very unclear from traceback which filing is causing the issue due to the streaming nature of the tool and the file information is lost somewhere inside of the parser.
I'm trying to unwind this so that when there is some kind of issue, it gets caught and reported at the source of the error itself where there is still context around the actual source file. Logging this here because it's been a persistent issue.