Skip to content

Keep rate-limited database setup in the backend plugin - #3744

Merged
adamtheturtle merged 1 commit into
mainfrom
decouple-rate-limit-fixture-20261013
Oct 13, 2026
Merged

adamtheturtle merged 1 commit into
mainfrom
decouple-rate-limit-fixture-20261013

Conversation

@adamtheturtle

Copy link
Copy Markdown
Member

Shared target-list fixtures currently create rate-limited databases through either the running in-memory mock or a target-manager HTTP request. Move rate_limited_database into the backend plugin and reuse the typed database-creation operation already supplied to recognition-report tests. The real backend returns its configured live database.

This two-file follow-up to #3742 and #3743 advances #3738, part of #3737. Further backend decoupling remains in #3738.

Validation:

  • Python 3.15: 68 target-list and recognition-report tests pass across the in-memory and Flask backends, using synthetic credentials with retries disabled. Five real-Vuforia cases are skipped locally.
  • Both database-creation paths and the mock rate-limited setup are covered. The retained real-backend return branch is not exercised locally.
  • Pre-commit and pre-push hooks pass, including CI partition validation, Mypy, Pyright, public type completeness, Ty, and Pyrefly. Pylint passes for both changed files, and git diff --check passes.

Full-suite coverage and real-Vuforia validation remain for hosted CI.

@adamtheturtle
adamtheturtle merged commit 81cdbf0 into main Oct 13, 2026
10 checks passed
@adamtheturtle
adamtheturtle deleted the decouple-rate-limit-fixture-20261013 branch October 13, 2026 11:49

This branch was successfully deployed

1 active deployment
development — 7476d2d6 Deployed Oct 13, 2026 by adamtheturtle via pages #2371
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant