Repository navigation
Conversation
Backend unit coveragePASS · minimum combined coverage 98.00%. Tests: 11965 passed, 0 failed, 0 skipped. Source files: 400.
Unit coverage includes every backend workspace. PostgreSQL/Redis integration tests run separately. Commit: 23fffeb · HTML, JSON, XML reports and job logs · attempt 1 |
1 of 2 tasks
|
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.



What changes and why?
Ignored tracking parameters currently create distinct server-cache entries for identical public responses. Owned cached public endpoints now opt into query normalization based on FastAPI's native dependency metadata. A request such as
/v1/feed?limit=1&utm_source=secondcan reuse the response for the same declared filters with another tracking value.Aliases, dependency fields, repeated-value ordering, path parameters and policy/schema identities remain significant. Declared parameter values are not coerced, so validation failures cannot reuse valid responses. Query models and complex alias paths conservatively retain all parameters because unknown keys can carry validation semantics. Custom cache policies remain exact by default.
Before/after PostgreSQL measurements
A local x86-64 PostgreSQL 18 / session-mode PgBouncer / Redis comparison ran three
samples per policy with alternating order. The baseline uses the original exact
query identity (normalization metadata omitted); the candidate uses native declared
query metadata. Warm-up is excluded. A separate observer role captured all workload
PostgreSQL statements, including driver setup, read-only transactions and pooler
DISCARD ALL, rather than relying only on SQLAlchemy application SQL events.The warmed pool has one existing backend, so backend startups were zero in both
modes. The fixture reads the same approved source detail with unchanged inputs.
There is no new SQL path or schema change. The native policy regression exercises
both exact and normalized identities with available cache, unavailable cache and
public-epoch churn. The avoided work depends on actual irrelevant-query traffic;
these fixtures do not establish production container savings. Native ARM64 and a
representative traffic/pooler canary remain required before promotion. Equal work
under cache failure does not mean the database can absorb an arbitrary cache outage.
Validation
extra=forbid, malformed declared values, mounted routes and policy revisions.Rollout notes
No cache TTL, schema, resource-limit or production deployment changes. Existing declared-query identities remain compatible; the policy opt-in drops only ignored query keys. Future policies whose response depends on arbitrary
Request.query_paramsmust retain exact identities. The query-identity guide documents conservative fallbacks and reproduction.Ready for review