-
Notifications
You must be signed in to change notification settings - Fork 0
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
Weird threading or race condition problem, maybe #13
Comments
@stucka Sadly, at first glance this looks to be an FAA issue. At 15:16:59 UTC time:
As you can see, EWR exists with an end time of 11:30. At 15:18:00 UTC time:
EWR doesn't exist at all there. Then at 15:19:02 UTC time:
EWR exists again with an end time of 12:30 pm. I wish I understood more about how the FAA handles this API. It seems like instead of just updating the entry they completely remove it, then re-add it?? Maybe as a result of some legacy system (if I had to guess). Obviously the best way to handle this would be if the FAA would provide unique IDs for each event. I guess we could also either not refresh the data as quickly, or wait for a few runs to see if it gets re-added or if it truly was deleted. But either one of those options would add latency to posts. Any feedback or ideas would be appreciated. |
The text was updated successfully, but these errors were encountered: