Repository navigation
Cache CelesTrak queries and persist retry cooldowns - #66
Merged
Merged
Conversation
This was referenced Nov 7, 2026
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
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.
Summary
Closes #59.
Reuse GP responses for two hours and SATCAT searches for twelve hours, including valid no-match responses. Persist cached data and shared cooldowns across restarts, with a 50 MiB response-data budget.
Temporary rate limits pause downloads for two hours. Service failures pause downloads for ten minutes. Any other non-200 response also pauses downloads: two hours for HTTP 403, ten minutes otherwise. Recovery happens on demand. Both Compose environments mount the cache volume and rotate MCP logs at three files of 10 MiB each.
Evidence
OPENBLAS_NUM_THREADS=1 OMP_NUM_THREADS=1 apps/mcp-server/.venv312/bin/python -m pytest -q apps/mcp-server/testsin 118.55 seconds. Two existing dependency deprecation warnings remain.Merge Danger
Door: two-way.
The cache holds disposable upstream data. Reverting the server and Compose changes rolls back the behavior. Merging to main follows the existing MCP image build and EC2 deployment workflow.
Blast Radius: CelesTrak.
Orbital-data and satellite-name lookups share the cooldown. Unexpired cached results remain usable. Unavailable or full cache storage stops new downloads and returns an app error. The 50 MiB response-data budget has additional bounded SQLite metadata and journal overhead. Capacity-failure metadata is capped at 1,024 query records; reaching that cap stops new misses until records expire, while cached results remain usable.