Byse rejects MKV files that carry an attachment (for example an embedded
.nfo text file) with "Not video file format". Verified with clips cut from
a rejected episode: the full clip is rejected, the same clip without the
attachment track is accepted.
For Byse uploads the Attachments element header is now rewritten into EBML
Void elements of the same length while streaming. File size, offsets and
all video, audio and subtitle tracks stay unchanged, the source file on disk
is not modified, and other hosters receive the original bytes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The total only counted the initial tasks, so batches that grew through
addJobs() logged results such as ok=200 fail=-197.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
npm audit flagged Electron <42.11.3 (HID/USB permission checks attributed
to the wrong origin), which failed CI. Electron 42 no longer downloads its
binary in postinstall; none of the other 42.0 breaking changes apply.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Automation-triggered starts and auto-retry rounds restarted every job in
error state, including files a hoster permanently rejected (e.g. Byse
"Not video file format"). Each new file in the watched folder thus
re-uploaded the rejected 3-4 GB files again on two Byse accounts.
Automatic starts now skip file-rejected jobs; manual starts still retry them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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>
The shared upload limiter started with a full second of tokens and refilled
up to one second during short idle gaps, so new uploads could briefly send
almost twice the limit. In a parallel-upload test it released 3.87 MB in one
second at a 2 MB/s limit. Uploads now reserve send time on one shared
schedule with at most a 200 ms burst and exact waits.
Speeds and limits used 1024-based kB and MB while being shown as kB/s and
MB/s, so a limit of 100 meant 104.9 MB/s. Limits, measured speeds, ETA and
the speed graph now use 1 MB = 1,000,000 bytes. Saved limits are converted
once so the displayed value stays the same.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mhu_queue_resume only lifts the shared pause and continues the queue
with the settings that were active before mhu_queue_pause, so it no
longer requires the local confirmation dialog when source deletion or
shutdown-after-finish is enabled. Starting, retrying and reconciling
uploads via MCP still require confirmation in that case.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Setting UV_THREADPOOL_SIZE in main.js had no effect: Electron
initialises libuv before the main script runs, so the uploader kept the
default four threads for upload reads, logs and queue saves. Packaged
builds now relaunch once at startup with UV_THREADPOOL_SIZE=32 before
the single-instance lock. Portable and development runs are unchanged.
App info and the startup marker report the effective threadpool size.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>