Commit Graph
6 Commits
Author SHA1 Message Date
SucukdeluxeandClaude Opus 5.5 23fc22fd7d Ignore staged source deletions in folder automation
CI / verify (push) Canceled after 0s
Deleting a source after a successful upload first renames it to
.<name>.mhu-delete-<uuid> and then unlinks it. On a slow disk the unlink
can take several seconds. With an empty extension filter the folder
watcher and the reconcile scan reported the staged file as a new file,
so the automation queued and uploaded it again until the unlink removed
it. The jobs for the vanished staged file were then restarted by every
automatic start and skipped with "Datei nicht gefunden".

- source-cleanup-policy: shared stagedSourceName/isStagedSourceFile.
- folder-monitor and file-discovery skip staged delete files.
- Automatic starts no longer restart queue jobs that point at a staged
  delete file; manual starts are unchanged.
- An ENOENT while unlinking the staged file counts as deleted instead of
  a failed unlink with a restore attempt. EBUSY/EPERM keep their retries
  and stay visible as failures.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 17:25:55 +02:00
SucukdeluxeandClaude Opus 5.5 b7be8d492a Let a later cleanup group take over a source whose earlier group has finished
When the same file was registered for cleanup a second time (for example a
repeated upload to one hoster), both groups blocked each other through the
source lease and the file was never deleted, even after every hoster had
succeeded. A later group now takes over the lease once every job of the
earlier group has reached a terminal state; the earlier group is audited as
superseded. Groups with a still running job keep blocking as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 22:19:19 +02:00
SucukdeluxeandClaude Opus 5.5 d12a5de45b Delete each uploaded source as soon as its links and queue state are saved
Previously sources were only removed when the whole upload batch ended. In
automation mode a batch keeps growing for hours, so hundreds of finished
files stayed on disk. A file is now removed once every required hoster
succeeded, its links are flushed to the upload log, the automation ledger
is written and the renderer confirmed the queue save. Without that evidence
the file still waits for the batch end as before.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-21 02:59:54 +02:00
Sucukdeluxe d7c9f287e4 release: restore v2.1.19 baseline for v2.1.24
CI / verify (push) Has been cancelled
Restore the v2.1.19 application baseline and retain only the focused import preflight summary with duplicate, unavailable, destination, job, and size-limit visibility.
2026-08-17 04:25:22 +02:00
Sucukdeluxe 67978cb81f Harden source cleanup durability barriers
Separate provisional upload success from persistently confirmed cleanup state, invalidate prior confirmations before retries, and promote completion only inside the final queue persistence handshake. Preserve source files when history or queue persistence fails and add regression coverage for restart, retry, rollback, and real Electron finalization paths.
2026-08-13 19:45:31 +02:00
Sucukdeluxe 03136e9fef release: Multi-Hoster-Upload 2.1.7 2026-08-11 16:10:13 +02:00