Skip to content

APP-18196: Add refresh_dataset_cache to submit_custom_training_job - #1290

Closed
Katie Peters (katiepeters) wants to merge 1 commit into
mainfrom
katie/APP-18196
Closed

Katie Peters (katiepeters) wants to merge 1 commit into
mainfrom
katie/APP-18196

Conversation

@katiepeters

Copy link
Copy Markdown
Member

Adds an optional refresh_dataset_cache: bool = False keyword argument to MLTrainingClient.submit_custom_training_job and passes it on SubmitCustomTrainingJobRequest. When true, the job exports the dataset fresh instead of reusing a cached export, and replaces the cached export with the new one. The dataset export cache itself is in viamrobotics/app#13890.

Also records the field in MockMLTraining.SubmitCustomTrainingJob and asserts it in test_custom_submit_training_job.

Depends on viamrobotics/api#918, which adds refresh_dataset_cache = 10 to SubmitCustomTrainingJobRequest. This PR does not touch src/viam/gen. The generated field lands with the automated proto update after the api release. Until then, test_custom_submit_training_job and pyright fail because the request has no refresh_dataset_cache field.

Testing: ruff check/format clean. With ml_training_pb2 regenerated locally from the api branch (not committed), pytest tests/test_ml_training_client.py passes (10/10) and pyright reports no errors on the client.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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