satellite should be able to deal with corrupt/outdated/unreadable JSON file in queue
Bug #634321 reported by
Chris Wagner
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Resonate |
Confirmed
|
Low
|
Chris Wagner | ||
Bug Description
As of now, the satellite will just keep attempting to re-read and re-parse the JSON file. If there is an error in parsing the JSON, we should have some mechanism for either removing that unreadable file or skipping over it for the time being.
| Changed in resonate: | |
| status: | New → Confirmed |
| Changed in resonate: | |
| assignee: | nobody → Chris Wagner (chris-wagner) |
| importance: | Undecided → Medium |
Revision history for this message
| Chris Wagner (chris-wagner) wrote | #1 |
| Changed in resonate: | |
| importance: | Medium → Low |
To post a comment you must log in.
At present, these unreadable/corrupt files will be skipped over by the satellite (until it runs through the queue on the next pass)... Should the satellite attempt to delete such files, though? The answer to that is unclear to me at this time.