diff --git a/CHANGELOG.md b/CHANGELOG.md index 38708ad..3dd4b0b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -20,7 +20,8 @@ release (0.x.y) only fixes bugs. Breaking changes are called out below. job id, or when polling is refused, it waits for the user notification as before, and now also stops on a refused, canceled or failed notification. New keyword `provider_id` (the handle passes its own); `start_validation` also takes - `dataflow_id` and `provider_id`. + `dataflow_id` and `provider_id`. Checked live on the sandbox (normal run, and a + second start while one runs, which gets `LockedError`). ## 0.1.3 (2026-11-19) diff --git a/docs/reference/easy.md b/docs/reference/easy.md index cd84ae5..8a6ed33 100644 --- a/docs/reference/easy.md +++ b/docs/reference/easy.md @@ -627,8 +627,10 @@ and exports). A job that ends FAILED, REFUSED or CANCELED raises `JobError` with the job's `status` and `info`; a FINISHED job with an `info` text (for example "There are canceled validation tasks", so the results may be partial) warns with it and puts it in the result's `attrs["validation_note"]`. Read from the -backend source (`MasterOneVersion` branch); the job polling is not yet tested -live for validations. +backend source (`MasterOneVersion` branch) and checked live on the sandbox +(Bearer): the start answered a job id and polling it reached FINISHED. A start +while another job runs on the dataset gets `LockedError` (423) at once. The +FAILED/REFUSED/CANCELED and FINISHED-with-note endings are tested with mocks only. Without a job id (older backends), or when the poll route is refused, the signal is the user notification the backend creates when a run ends diff --git a/reportnet_api/easy.py b/reportnet_api/easy.py index ebd5c1f..860f599 100644 --- a/reportnet_api/easy.py +++ b/reportnet_api/easy.py @@ -508,8 +508,10 @@ def validate_and_wait( with the job's `status` and `info`; a FINISHED job with an `info` text (for example "There are canceled validation tasks", so the results may be partial) warns with it and puts it in the result's `attrs["validation_note"]`. Read from the - backend source (`MasterOneVersion` branch); the job polling is not yet tested - live for validations. + backend source (`MasterOneVersion` branch) and checked live on the sandbox + (Bearer): the start answered a job id and polling it reached FINISHED. A start + while another job runs on the dataset gets `LockedError` (423) at once. The + FAILED/REFUSED/CANCELED and FINISHED-with-note endings are tested with mocks only. Without a job id (older backends), or when the poll route is refused, the signal is the user notification the backend creates when a run ends