Skip to content

Add timeout customization options#1952

Merged
adamtheturtle merged 1 commit intomainfrom
adamtheturtle/custom-timeouts
Feb 15, 2026
Merged

Add timeout customization options#1952
adamtheturtle merged 1 commit intomainfrom
adamtheturtle/custom-timeouts

Conversation

@adamtheturtle
Copy link
Copy Markdown
Member

@adamtheturtle adamtheturtle commented Feb 15, 2026

Summary

  • Added --connection-timeout-seconds and --read-timeout-seconds CLI options to all VWS commands and Cloud Reco command
  • Options override the default 30-second HTTP timeout from vws-python
  • Both options accept values ≥ 0.05 seconds and default to 30 seconds
  • Timeout values are passed as a (connect, read) tuple to the underlying VWS and CloudRecoService constructors

Test plan

  • All 19 timeout-related and help text tests pass
  • Default timeout behavior unchanged (backward compatible)
  • Custom timeout values are respected in new tests

Note

Low Risk
Low risk: additive CLI options and plumbing into existing client constructors with test coverage; main risk is unintended behavior change in request timeout handling across commands.

Overview
Adds per-command HTTP timeout customization to the CLI by introducing --connection-timeout-seconds and --read-timeout-seconds options (defaults 30s, min 0.05s) and wiring them into all VWS commands and the vuforia-cloud-reco query command via request_timeout_seconds=(connect, read).

Updates generated help-text fixtures to document the new options and adds new tests that simulate delayed responses to verify smaller custom timeouts raise requests.exceptions.Timeout while larger values succeed.

Written by Cursor Bugbot for commit b7f15fa. This will update automatically on new commits. Configure here.

Users can now override the default 30-second HTTP timeout via
--connection-timeout-seconds and --read-timeout-seconds. These options
are available on all VWS commands and the Cloud Reco command, and are
passed as a (connect, read) tuple to the underlying vws-python library.

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

server_secret_key: str,
base_vws_url: str,
connection_timeout_seconds: float,
read_timeout_seconds: float,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent keyword-only parameter marker across commands

Low Severity

This PR adds *, to enforce keyword-only arguments in get_target_record, get_duplicate_targets, get_target_summary_report, and delete_target, but list_targets and get_database_summary_report are missing the same *, marker. Every other command function in the file now uses keyword-only parameters, making these two inconsistent outliers.

Additional Locations (1)

Fix in Cursor Fix in Web

@adamtheturtle adamtheturtle merged commit b13c9da into main Feb 15, 2026
16 checks passed
@adamtheturtle adamtheturtle deleted the adamtheturtle/custom-timeouts branch February 15, 2026 13:29
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