-
-
Notifications
You must be signed in to change notification settings - Fork 6
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 Error #117
Comments
I'm using the latest version and I have not encountered this "bug" that you speak of. Perhaps it was self induced? |
Here's an example of some of the JSON formatting problems within this. No idea of the cause as of yet. Note the "}: null," part. Where the error is, seems to vary by the alerts.
|
Another alert with exact issue.
|
Self induced by the script. I will try to look over the script and see where the problem is. |
Made some updates to it. This recognizes the improper formatting of JSON files. Resets to default. Good temp fix until I get some time to look at it more. |
Describe the bug
JSON errors prevents getting and clearing alerts.
To Reproduce
Steps to reproduce the behavior:
Improperly format the data.json file to reproduce.
Expected behavior
Errors within the json should either delete or ignore, varying by error reason, and continue with getting alerts, or clearing.
Files
/tmp/SkywarnPlus/data.json
Screenshots
N/A
Node (please complete the following information):
Additional context
This was noticed after days of alerts that were no longer active for the counties. It was noticed by trying to run skydescribe and returned an error.
Unfortunately the json file was removed as I was testing, and didn't manage to keep the invalid formatted one. There was a line in the description that caused it to be in correctly formatted.
Example of the format noticed in description. It was missing the outer quote.
"description": "This alert was manually injected as a test.,
The text was updated successfully, but these errors were encountered: