Skip to content

v3.0.2 — Fix premature processing of in-progress file transfers

Choose a tag to compare

View all tags
@jarynclouatre jarynclouatre released this 19 Apr 00:04
v3.0.2
85f371c

What's fixed

Bindery was processing files that hadn't finished copying yet.

When dropping files into /Comics_in via FileBrowser, the file watcher would start a conversion before the transfer was complete. FileBrowser (and most copy tools) briefly pause between write chunks — if that pause hit Bindery's 2-second poll window, the file appeared stable when it wasn't. KCC then tried to convert a partial/corrupt CBZ, failed, and renamed it to .failed, which blocked FileBrowser from finishing the copy.

Changes

  • wait_for_file_ready now requires 3 consecutive stable size readings (~6 seconds) instead of 1 before passing a file to the converter
  • inotify mode now also handles on_closed (IN_CLOSE_WRITE), which fires only after the writing process fully closes the file — a definitive "transfer complete" signal for clients like FileBrowser

No config changes needed. Existing setups will pick this up automatically on container restart.

Assets 2
Loading