Uh oh!
There was an error while loading. Please reload this page.
Validate the reco counts report database ID - #3367
Merged
Merged
Conversation
Closes#3362. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
adamtheturtletemporarily deployed
to
development
August 9, 2026 08:15 — with 
GitHub Actions
Inactive
The previous wording described only behaviour which matches real Vuforia, which does not belong in this document. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 freeto 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.
Real Vuforia rejects a reco counts request whose path names a database its server keys do not belong to with a 401
AuthenticationFailure— observed against the real service in #3366, including when the database name is passed in place of the ID — where the mock accepted any ID, so code which built the path from a database name or a stale ID passed against the mock and failed for real.CloudDatabasenow has adatabase_idwhich defaults to a random string and round-trips throughCloudDatabaseDict,to_dict,from_dictand the target manager's create-database route, so the in-process and Flask/Docker backends do not disagree, and a newvalidate_database_id_matches_keysvalidator runs immediately after authorization, before themonthis looked at, matching the ordering observed from real Vuforia.The tests drop the per-backend ID helper and the redundant
vuforia_database_idfixture in favour of readingvuforia_database.database_id, and add verified cases for an ID belonging to no database and for a database name given in the ID's place;differences-to-vws.rstdrops the note that the mock cannot make this check.All 26 cases pass across the three mock backends, but the real-Vuforia leg has only been run here against placeholder credentials, so it is unverified until credentialed CI runs.
Closes#3362.
🤖 Generated with Claude Code