Fix immediate automation pause, restored queue rendering and bounded disk reads; release 2.1.75
CI / verify (push) Canceled after 0s
CI / verify (push) Canceled after 0s
This commit is contained in:
1 parent
267a840853
commit
80eb878f1b
12 files changed
+168
-68
No files matched your search
@@ -152,7 +152,7 @@ The automatic queue limit counts preview, queued, server-selection, uploading, a
|
||||
|
||||
New matching files are collected after they have remained stable for the configured delay. The optional one-time existing-file scan, live watcher events, interval scans, and reconnect scans use the same filtering and admission path. Reconciliation checks the complete folder at the selected interval. A missing folder keeps its configuration; after it becomes reachable again, exactly one reconnect scan runs before normal interval scans continue. If no hosts are preselected, the application asks for destinations instead of starting a batch automatically.
|
||||
|
||||
**Finish and pause** saves the pause before allowing active uploads to finish. While paused, no watcher, reconciliation, queued upload start, automatic start, or active-batch injection can proceed. Manual files can still be imported as preview jobs. The pause survives an application restart. **Resume** explicitly removes it, restarts monitoring, and performs one reconciliation without automatically starting existing preview jobs.
|
||||
**Pause automation** immediately aborts active uploads and blocks new work, including while the pause is still being saved. Paused transfers restart from the beginning on **Resume**; completed uploads are kept. While paused, no watcher, reconciliation, queued upload start, automatic start, or active-batch injection can proceed. Manual files can still be imported as preview jobs. The pause survives an application restart. Resume restarts paused jobs and reconciles the monitored folder without automatically starting unrelated preview jobs. The official updater separately lets active uploads finish before installing.
|
||||
|
||||
For automation decisions, **already processed** describes current evidence only: exact paths in the current queue, successful history results, and successful entries in the application's upload log. It is not a permanent file registry. A basename-only match is accepted only when it identifies one candidate unambiguously; same-named files from different folders remain eligible unless exact current evidence identifies them.
|
||||
|
||||
@@ -332,6 +332,10 @@ The update first saves its resume intent, stops new admission and waits for curr
|
||||
|
||||
Use `mhu_capabilities` to inspect effective permissions and available actions before controlling an installation. `mhu_automation_pause` and `mhu_automation_resume` explicitly control the shared upload/automation pause; their queue equivalents remain supported. Resuming does not enable a disabled monitor. `mhu_automation_start` enables configured monitoring and returns `AUTOMATION_PAUSED` if the shared pause must first be resumed. Failed lifecycle operations return an MCP error, not a successful response containing an error string. A read-only status check never changes the pause state.
|
||||
|
||||
Pausing aborts active transfers immediately and prevents new uploads before waiting for settings to reach disk. Resuming waits for these aborted transfers to settle, then restarts the paused files from the beginning. Completed uploads and explicitly cancelled files are not restarted. The same behavior applies to the interface and MCP.
|
||||
|
||||
Upload file reads share a bounded pool of four concurrent reads. `mhu_io_limits_get` reports its active, waiting and maximum read counts; `mhu_io_limits_update` accepts `readConcurrency` from 1 to 32. This changes only the current process, does not abort uploads and returns to the default after restart. It is separate from upload concurrency and does not limit other applications' disk activity.
|
||||
|
||||
Structured settings updates also support upload parallelism scaling, partial filename-scrambling settings, history retention and hoster size-limit memory. Enabling automatic source deletion, a completion power action or limited history retention requires exact local confirmation. `mhu_shutdown_cancel` cancels the pending completion action immediately, then saves `nothing` as the policy. This does not authorize immediate system shutdown or unrestricted operating-system control.
|
||||
|
||||
The upload scheduler no longer reserves a global transfer slot while waiting for a hoster's configured start interval. Per-hoster spacing remains enforced at admission. Upload file metadata and chunk reads use asynchronous I/O. These changes do not reduce configured parallelism or change successful-upload confirmation requirements. Synthetic benchmark results demonstrate the targeted scheduling case only; server-specific throughput and freeze improvements require measurements after installing the new version.
|
||||
|
||||
Reference in new issue
Block a user