Conversation
Flight numbers don't repeat until next day's operation, so Arrived/Canceled/Diverted status is safe to cache much longer than the active refresh interval. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…he from controller to mimic that of the aero client
asubowo
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Primarily addresses some minor bug fixes, some log level cleanups and what is logged, and moved cache in the WMATA service to the client vs the controller itself.
To help save on API calls, settled flights are marked in the cache for 4 hours. This is usually the case for international flights where the flight number for the specific plane changes based on route. Rarely (I think?) does a flight number persist between multiple legs, unassociated with each other. Hoping this works. It made sense in my head though.
Also introduces DB cleanup operations. Right now, we leave uninstalled UUIDs in the DB, they're just marked as revoked. DB operation schedules every 24 hours a cleanup