release: v1.19.0 — PPD serves from the local snapshot; full history; two wrong-answer fixes - #71
Merged
Merged
Conversation
…two wrong-answer fixes Version bumped in the three places the reconcile job compares against the tag: pyproject.toml, server.json version, server.json packages[0].version. uv.lock regenerated, which `uv lock --check` in scripts/validate.sh catches otherwise. Contents are in the changelog entry. Two things worth repeating here because they change behaviour rather than adding to it: * REST now REFUSES unknown query parameters with 400 instead of discarding them. Requests that "succeeded" while carrying a typo now fail. * Subject-property lookup could return another property's sale history -- "2 Alexandra Road" answered with 25 Alexandra Road -- and separately refused 1 in 7 addresses that were never ambiguous. Both fixed. Deployment order is load-bearing and is recorded in the changelog: the image must reach the Machine BEFORE current.json is flipped to the full-history artifact, or a Machine still running the 1 GiB ceiling refuses the 1.19 GB bundle at boot and falls back to a live source that is currently 503-ing. ./scripts/validate.sh: 2220 passed, 28 skipped.
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.
Version bump + changelog. 31 commits since v1.18.2.
Bumped in the three places the new reconcile job compares against the tag —
pyproject.toml,server.json version,server.json packages[0].version— anduv.lockregenerated, whichuv lock --checkcatches otherwise (it did).Two behaviour changes worth seeing before you publish
REST refuses unknown query parameters (400). Requests that "succeeded" while
carrying a typo now fail. MCP clients cannot hit this — they read the tool's JSON
Schema and never assemble a query string.
Subject-property lookup could return another property's history. "2 Alexandra
Road" answered with 25 Alexandra Road, whose price then fed
subject_price_percentile. Separately it refused 1 in 7 addresses that werenever ambiguous. Both fixed.
Also:
epc_match_raterises andmedian_price_per_sqftmoves, becausenewly-matched comps bring floor areas into the median.
Deployment order is load-bearing
release.ymlchecks out the tag and deploys. Thisis why it must be the Release and not a local
fly deploy, which would ship aworking directory.
current.json.Reversed, a Machine still running the 1 GiB ceiling refuses the 1.19 GB bundle
at boot and falls back to a live source that is 503-ing.
What to expect
working — it means the two apps disagree on version.
ephemeral rootfs at the measured 63.6 Mbit/s). The service stays healthy — boot
is non-blocking and the app is ready in ~10 s — but it serves live meanwhile,
and live is down. Two restarts: this deploy, then the artifact flip.
artifact and is truncated at 2016-01-01. Declared, not silent — provenance
states the coverage and a warning names the narrowing — but keep the window
short.
A Fly Volume would remove the re-materialization entirely (the boot path already
reuses an existing materialization, and
PPD_SNAPSHOT_CACHE_DIRisconfigurable). Deliberately not in this release: better to add it against a
snapshot already proven working.
./scripts/validate.sh→ 2220 passed, 28 skipped.