Files
spacedrive/docs
Jamie Pine dc40a85a48 Stop jobs lingering in the client after they finish
JobStarted was emitted for every job while JobCompleted, JobFailed and
JobCancelled were all gated behind should_emit_events. So any job that
opted out of events still announced a start and never announced an end,
and the client had a row nothing could clear. That is every ephemeral
browse, since should_emit_events is should_persist unless the job is
indexing a whole volume.

Gating the start the same way makes an event-free job invisible end to
end, which is what the flag was for.

Also reorders the completion arm. Clients refetch the job list when they
see a completion, and the job was removed from running_jobs after the
event went out, so a refetch that landed first got the job back in the
answer with nothing further coming to clear it. Reading the output,
removing, then announcing closes that window.
2026-08-25 22:17:56 -07:00
..
2025-11-14 21:40:49 -08:00
2025-11-14 21:31:21 -08:00
2025-11-14 21:31:21 -08:00
2025-11-14 21:31:21 -08:00
2025-11-14 21:31:21 -08:00
2025-11-14 21:40:49 -08:00

Spacedrive Documentation

This repository contains the Mintlify-powered documentation for Spacedrive.

Structure

  • docs/ - Symlink to main spacedrive repo documentation
  • mint.json - Mintlify configuration