vws-python-mock 2026.9.8__tar.gz → 2026.9.12__tar.gz

{vws_python_mock-2026.9.8 → vws_python_mock-2026.9.12}/.vale.ini

@@ -4,7 +4,8 @@ MinAlertLevel = error
 Packages = https://github.com/tbhb/vale-ai-tells/releases/download/v1.29.0/ai-tells.zip
 
 [*.{rst,md}]
-BasedOnStyles = ai-tells
+BasedOnStyles = ai-tells, snapper
+snapper.SemanticLineBreaks = error
 
 # These rules misclassify established technical, example, or release-note prose
 # in this repository. All other ai-tells rules remain enforced.

{vws_python_mock-2026.9.8 → vws_python_mock-2026.9.12}/CHANGELOG.rst

@@ -3,6 +3,25 @@ Changelog
 
 .. towncrier release notes start
 
+2026.09.12
+----------
+
+- Validate decoded Model Target request values before processing them.
+
+- Type target-manager request defaults as database dictionaries instead of arbitrary mappings.
+
+- Type parsed Target Manager request bodies using recursive JSON values.
+
+- Accept integer ``response_delay_seconds`` values when mocking ``requests`` calls.
+
+2026.09.08.1
+------------
+
+- The URL of a reco counts report now has the shape of the presigned cloud storage URL which real Vuforia returns.
+  The report file is named ``{date}-{hour}.csv`` for the current month and ``{month}.csv`` for the previous month, so two requests for the same month in the same hour name the same file and serve the report which the first request generated.
+  The URL carries the query parameters of a presigned URL, and the mock honors ``X-Amz-Date`` and ``X-Amz-Expires`` as real Vuforia's storage does, so a URL which is out of date or which has no query parameters gives the ``403`` XML error document which Amazon S3 gives.
+  A report which is not yet generated gives the ``404`` ``NoSuchKey`` XML error document which Amazon S3 gives, as real Vuforia has now been observed to do, rather than an empty body.
+
 2026.09.08
 ----------
 
@@ -36,9 +55,11 @@ Changelog
 
 - Return a ``BadImage`` response, rather than failing to respond, when an image given to the Target API is truncated before the end of its image data.
 
-- ``MockVWS`` now intercepts ``httpx2`` requests, synchronous and asynchronous, alongside ``requests`` and ``httpx``. The ``httpx2`` path uses native ``httpx2`` requests and responses, and does not need ``httpx2.alias_httpx()``.
+- ``MockVWS`` now intercepts ``httpx2`` requests, synchronous and asynchronous, alongside ``requests`` and ``httpx``.
+  The ``httpx2`` path uses native ``httpx2`` requests and responses, and does not need ``httpx2.alias_httpx()``.
 
-- Fix nested ``MockVWS`` instances on the ``httpx`` backend: an inner mock is now the only one which answers while it is running, matching the ``requests`` and ``httpx2`` backends. Previously the outer mock kept answering and requests to the inner mock's URL were refused.
+- Fix nested ``MockVWS`` instances on the ``httpx`` backend: an inner mock is now the only one which answers while it is running, matching the ``requests`` and ``httpx2`` backends.
+  Previously the outer mock kept answering and requests to the inner mock's URL were refused.
 
 - Return a response, rather than raising an uncaught ``JSONDecodeError``, when an empty body is given to a VWS endpoint which takes a JSON body.
   As real Vuforia does, ``POST /targets`` and ``PUT /targets/<target_id>`` now return a 500 ``Fail`` response, the reco counts report endpoint returns a 400 ``Fail`` response, and the VuMark instance generation endpoint returns a 400 ``BadRequest`` response.
@@ -69,16 +90,17 @@ Changelog
 - Return a response, rather than raising an uncaught ``PIL.Image.DecompressionBombError``, when an image with a small file size but a huge number of pixels is given to ``POST /targets`` or ``POST /v1/query``.
   As real Vuforia does, ``POST /targets`` now returns the ``ImageTooLarge`` result code for an image with more than 37748736 pixels, and the Query API applies no pixel count limit.
 
-- Return targets in a deterministic order from the Query API, ``GET /targets``
-  and ``GET /duplicates/{target_id}``.  Targets are ordered by upload date and
-  then by target ID, so repeated runs agree with each other.  This order is not
-  Vuforia's match score order.
+- Return targets in a deterministic order from the Query API, ``GET /targets`` and ``GET /duplicates/{target_id}``.
+  Targets are ordered by upload date and then by target ID, so repeated runs agree with each other.
+  This order is not Vuforia's match score order.
 
 - Document the Docker containers' configuration with the environment variable names and values which the applications actually read, starting with ``TARGET_MANAGER_BASE_URL``.
 
 - Build the Docker images from a committed ``uv.lock`` with a ``.dockerignore``, so that image contents are reproducible from a commit, source edits no longer invalidate the dependency layer, and repository files such as tests and documentation are no longer copied into the images.
 
-- Store Model Target datasets in the target manager service rather than in the VWS application. In the Docker deployment, datasets now survive a restart of the VWS container, matching how cloud databases and their targets are stored. The VWS application also no longer imports the target manager module's state: it constructs its own request rate limiter and reco counts report store.
+- Store Model Target datasets in the target manager service rather than in the VWS application.
+  In the Docker deployment, datasets now survive a restart of the VWS container, matching how cloud databases and their targets are stored.
+  The VWS application also no longer imports the target manager module's state: it constructs its own request rate limiter and reco counts report store.
 
 - Report the Docker containers as unhealthy without a traceback in the health check probe output while nothing is yet listening on the port.
 
@@ -114,9 +136,7 @@ Changelog
 
 - Reject Model Target dataset creation requests with ``views`` entries which are not JSON objects, which are missing ``guideViewPosition`` or ``name``, or which have wrongly typed ``guideViewPosition`` or ``name`` values.
 
-- Model VWS request rate limits per endpoint with the new
-  ``CloudDatabase.request_rate_limits`` setting, including the limits which
-  Vuforia documents as ``mock_vws.request_rate_limits.DOCUMENTED_REQUEST_RATE_LIMITS``.
+- Model VWS request rate limits per endpoint with the new ``CloudDatabase.request_rate_limits`` setting, including the limits which Vuforia documents as ``mock_vws.request_rate_limits.DOCUMENTED_REQUEST_RATE_LIMITS``.
   No request rate limit is applied by default.
 
 - Change the ``ProjectHasNoAPIAccess`` result code to ``ProjectHasNoApiAccess``, matching Vuforia's result codes table.
@@ -136,19 +156,16 @@ Changelog
 2026.08.04.2
 ------------
 
-- Replace the PyTorch image-quality stack with OpenCV and a lightweight BRISQUE
-  implementation. This reduces dependency download and installation sizes and
-  removes the need to configure PyTorch's CPU-only package index.
+- Replace the PyTorch image-quality stack with OpenCV and a lightweight BRISQUE implementation.
+  This reduces dependency download and installation sizes and removes the need to configure PyTorch's CPU-only package index.
 
 - Allow VuMark generation requests to be configured to return ``QuotaExceeded``, ``LicenseCheckFailed``, or ``AuthorizationFailed`` responses.
 
-- Cloud databases with ``request_quota=0`` now return a
-  ``RequestQuotaReached`` response from VWS endpoints.
+- Cloud databases with ``request_quota=0`` now return a ``RequestQuotaReached`` response from VWS endpoints.
 
 - Add a mock implementation of the Model Target Web API, including OAuth2 token creation, standard and advanced dataset creation, status polling, dataset download, and deletion.
 
-- Improve Model Target Web API mock authentication failure responses, including
-  malformed and unsecured JSON Web Token headers.
+- Improve Model Target Web API mock authentication failure responses, including malformed and unsecured JSON Web Token headers.
 
 - Match real Vuforia Model Target dataset creation validation error shape, including per-request UUID, details list, and status codes (415 for unsupported media type, 400 with ``BAD_REQUEST`` validation details).
 
@@ -159,11 +176,9 @@ Changelog
 
 - Match real Vuforia Model Target Web API error responses for invalid request bodies, invalid dataset creation payloads, unknown datasets, and downloads of still-processing datasets.
 
-- Add configurable ``TargetQuotaReached``, ``ProjectSuspended``, and
-  ``ProjectHasNoAPIAccess`` responses from VWS endpoints.
+- Add configurable ``TargetQuotaReached``, ``ProjectSuspended``, and ``ProjectHasNoAPIAccess`` responses from VWS endpoints.
 
-- Add configurable ``TooManyRequests`` responses from VWS endpoints using the
-  ``CloudDatabase.requests_per_second_limit`` setting.
+- Add configurable ``TooManyRequests`` responses from VWS endpoints using the ``CloudDatabase.requests_per_second_limit`` setting.
 
 - Add ``CloudQueryFailureResponse`` and the ``MockVWS.cloud_query_failure_response`` parameter for returning configurable Cloud Query failure status codes, headers, and raw bodies through the ``requests`` and ``httpx`` backends.
 

{vws_python_mock-2026.9.8 → vws_python_mock-2026.9.12}/CODE_OF_CONDUCT.rst

@@ -11,19 +11,9 @@ Our Standards
 
 Examples of behavior that contributes to creating a positive environment include:
 
-Using welcoming and inclusive language
-Being respectful of differing viewpoints and experiences
-Gracefully accepting constructive criticism
-Focusing on what is best for the community
-Showing empathy towards other community members
-Examples of unacceptable behavior by participants include:
-
-The use of sexualized language or imagery and unwelcome sexual attention or advances
-Trolling, insulting/derogatory comments, and personal or political attacks
-Public or private harassment
-Publishing others' private information, such as a physical or electronic address, without explicit permission
-Other conduct which could reasonably be considered inappropriate in a professional setting
-Our Responsibilities
+Using welcoming and inclusive language Being respectful of differing viewpoints and experiences Gracefully accepting constructive criticism Focusing on what is best for the community Showing empathy towards other community members Examples of unacceptable behavior by participants include:
+
+The use of sexualized language or imagery and unwelcome sexual attention or advances Trolling, insulting/derogatory comments, and personal or political attacks Public or private harassment Publishing others' private information, such as a physical or electronic address, without explicit permission Other conduct which could reasonably be considered inappropriate in a professional setting Our Responsibilities
 
 Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
 
@@ -32,12 +22,17 @@ Project maintainers have the right and responsibility to remove, edit, or reject
 Scope
 -----
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
+Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+Representation of a project may be further defined and clarified by project maintainers.
 
 Enforcement
 -----------
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at adamdangoor@gmail.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at adamdangoor@gmail.com.
+All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances.
+The project team is obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 

{vws_python_mock-2026.9.8/src/vws_python_mock.egg-info → vws_python_mock-2026.9.12}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: vws-python-mock
-Version: 2026.9.8
+Version: 2026.9.12
 Summary: A mock for the Vuforia Web Services (VWS) API.
 Author-email: Adam Dangoor <adamdangoor@gmail.com>
 License-Expression: MIT
@@ -21,7 +21,7 @@ Requires-Dist: beartype>=0.22.9
 Requires-Dist: flask>=3.0.3
 Requires-Dist: httpx>=0.27.0
 Requires-Dist: httpx2>=2.12
-Requires-Dist: mock-response-delay>=2026.9.7
+Requires-Dist: mock-response-delay>=2026.9.12
 Requires-Dist: numpy>=2.4.4
 Requires-Dist: opencv-contrib-python-headless>=5.0.0.93
 Requires-Dist: pillow>=12.2.0

{vws_python_mock-2026.9.8 → vws_python_mock-2026.9.12}/docs/source/ci-setup.rst

@@ -24,12 +24,9 @@ Create environment variable files for secrets:
    $ cp vuforia_secrets.env.example ci_secrets/vuforia_secrets_1.env
    $ ...
 
-Populate every variable listed in :file:`vuforia_secrets.env.example`.
-Each file needs distinct active Cloud database credentials so concurrent jobs
-do not modify the same database. The files can share the inactive Cloud,
-active and inactive VuMark, and Model Target credentials.
-Add at least as many consecutively numbered files, starting at zero, as there
-are builds in the GitHub test matrix.
+Populate every variable listed in :file:`vuforia_secrets.env.example`. Each file needs distinct active Cloud database credentials so concurrent jobs do not modify the same database.
+The files can share the inactive Cloud, active and inactive VuMark, and Model Target credentials.
+Add at least as many consecutively numbered files, starting at zero, as there are builds in the GitHub test matrix.
 
 Choose a passphrase for the secrets.
 In the GitHub repository > Settings > Secrets, add a secret with the name ``PASSPHRASE_FOR_VUFORIA_SECRETS`` and the chosen passphrase.

{vws_python_mock-2026.9.8 → vws_python_mock-2026.9.12}/docs/source/contributing.rst

@@ -56,8 +56,7 @@ Create an environment variable file for secrets:
    $ cp vuforia_secrets.env.example vuforia_secrets.env
 
 Some tests require Vuforia credentials.
-To run these tests, add the Vuforia credentials to the file :file:`vuforia_secrets.env`.
-See :ref:`connecting-to-vuforia`.
+To run these tests, add the Vuforia credentials to the file :file:`vuforia_secrets.env`. See :ref:`connecting-to-vuforia`.
 
 Then run ``pytest``:
 
@@ -73,14 +72,12 @@ Connecting to Vuforia
 To connect to Vuforia, Vuforia target databases must be created via the Vuforia Web UI.
 Then, secret keys must be set as environment variables.
 
-The test infrastructure allows those keys to be set in the file :file:`vuforia_secrets.env`.
-See :file:`vuforia_secrets.env.example` for the environment variables to set.
+The test infrastructure allows those keys to be set in the file :file:`vuforia_secrets.env`. See :file:`vuforia_secrets.env.example` for the environment variables to set.
 
 Do not use a target database that you are using for other purposes.
 This is because the test suite adds and deletes targets.
 
-To create a target database, first create a license key in the `Vuforia License Manager`_.
-Then, add a database from the `Vuforia Target Manager`_.
+To create a target database, first create a license key in the `Vuforia License Manager`_. Then, add a database from the `Vuforia Target Manager`_.
 
 To find the environment variables to set in the :file:`vuforia_secrets.env` file, visit the Target Database in the `Vuforia Target Manager`_ and view the "Database Access Keys".