Repository navigation
validate_and_wait: name the job and dataset when a validation job fails - #14
Merged
Merged
Conversation
A validation job that ends FAILED or CANCELED_BY_ADMIN now raises a JobError reading "Validation job <id> for dataset <id> ended <status>", with status and info unchanged. Both endings were checked live on the sandbox by cancelling a running job; the dataset was not left locked. The docstring now explains that a refused start is answered as a 423 (LockedError) and never becomes a job to poll. Adds a live-testing note.
nikolaos-paximadakis-eea
deleted the
fix/validation-job-error-context
branch
November 21, 2026 23:29
Merged
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When a validation job ends FAILED or CANCELED_BY_ADMIN,
easy.validate_and_waitnow raises aJobErrorthat names the job and the dataset, for exampleValidation job 123 for dataset 456 ended FAILED: <info>. The error used to say onlyJob FAILED.statusandinfoare unchanged.Live check (sandbox, Bearer). I started a validation and cancelled the running job through
PUT /orchestrator/jobs/cancelJob/{jobId}:jobShouldFail=truethe job ended FAILED. With ajobInfovalue it ended CANCELED_BY_ADMIN and theinfotext came through. In both casesvalidate_and_waitraised at once with the rightstatusandinfo.From the backend source (
MasterOneVersion): a refused start is stored as REFUSED and answered as423(LockedError), so it never becomes a job to poll. The docstring now says so.Also included: a new mocked test for both endings, a section in
docs/live_testing_notes.md, a CHANGELOG entry, and the regenerateddocs/reference/easy.md. Not part of a release yet.