Skip to content

fix(ui): the export dialog reports a failure only once the job has settled - #803

Merged
JArmandoAnaya merged 1 commit into
mainfrom
fix/export-dialog-running-job-error
Aug 26, 2026
Merged

fix(ui): the export dialog reports a failure only once the job has settled#803
JArmandoAnaya merged 1 commit into
mainfrom
fix/export-dialog-running-job-error

Conversation

@JArmandoAnaya

Copy link
Copy Markdown
Contributor

What changed

While an export job was still queued or running, the export dialog showed The export stopped without saying why. under the Exporting badge, and the sentence vanished on its own once the job succeeded. The condition that picks the job to explain treated every state other than succeeded as a stop; it now asks isSettled first, so a failure sentence belongs only to a job that has actually finished as failed or cancelled.

The condition has been this way since the job system arrived; it went unnoticed because the jsdom tests only ever rendered the dialog at one settled state per test, and a real export is fast enough that the sentence flashes.

  • frontend/ui-core/src/screens/DatasetScreen.tsx: stopped requires isSettled(job).
  • frontend/ui-core/src/screens/dataset.test.tsx: a test renders the dialog at queued and at running and asserts no export-job-error.

Checks

pnpm --filter @visionset/ui-core test (62 files, 1378 passed), pnpm -r lint, pnpm -r build. The new test fails on main and passes here.

@JArmandoAnaya
JArmandoAnaya force-pushed the fix/export-dialog-running-job-error branch from a535bbd to 1ca336e Compare August 26, 2026 12:42
@JArmandoAnaya
JArmandoAnaya merged commit 63aae31 into main Aug 26, 2026
15 checks passed
@JArmandoAnaya
JArmandoAnaya deleted the fix/export-dialog-running-job-error branch August 26, 2026 12:48
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