Add Ruuster home listings and fix MusicBrainz rate-limit retries - #104
Merged
Merged
Conversation
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.
MusicBrainz upcoming releases repeatedly failed with HTTP 503 because
Retry-After: 0caused an immediate retry. MusicBrainz requests now share a process-wide queue, wait at least 1.1 seconds between requests, and retry with 5/15/45 second backoff while honoring longer numeric or HTTP-date retry hints. Temporary cover-art failures are no longer cached as missing artwork. A read-only test from the production container recovered from 503 to 200 after the first five-second wait.Adds a
ruusteradapter and hourlyruuster-san-jose-homessource for the supplied San Jose saved search, plus thesan-jose-homesfeed and a database-free JSON export script. The adapter preserves search filters, removes tracking, pages through public JSON, fetches property details and attribution, and combines syndicated MLS copies by listing number and address. It respects the worker detail budget/deadline and resumes unfinished pages. Historical entries keep their last observed status when they leave the search; disappearing listings are not classified as sold.Validation: live Ruuster export returned 38 unique properties from 104 upstream records; hidden-address/deleted records are omitted. Focused regression tests and repository lint pass. Final local suite against current main: 1,629 passed, zero failures; one PostgreSQL-only migration test is covered by CI. Provider reuse restrictions are documented in README.