validate yaml for forbidden extra fields #5
Merged
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.
also small optimization to reuse test model instead of repushing if both train and predict are set.
Summary:
This PR forbids extra fields in YAML configurations and optimizes model reuse to avoid redundant pushes, with added logging for prediction URLs.
Key points:
ConfigDict(extra="forbid")
toTestCase
,FuzzConfig
,PredictConfig
,TrainConfig
, andConfig
classes incog_safe_push/config.py
to forbid extra fields in YAML.cog_safe_push/main.py
by introducingreuse_test_model
to avoid redundant pushes when both train and predict are set.cog_safe_push
function to handlereuse_test_model
parameter.cog_safe_push/predict.py
for better traceability.Generated with ❤️ by ellipsis.dev