Data Resource Manager crashes when non-JSON file is encountered
Opened this issue · 1 comments
gregmundy commented
If a non-JSON file is encountered in the location where the data resource API retrieves files it will crash. This sometimes happens when configurations are pulled from a repository that may have additional files (such as README). The Data Resource Manager should gracefully ignore this invalid file and continue to process valid files. Ideally, this issue should be seen in logs.
loganripplinger commented
Probably just need to wrap the json.loads() commands in try/except and catch JSONDecodeError per https://docs.python.org/3/library/json.html
https://docs.python.org/3/library/json.html#json.JSONDecodeError