Release: 2.1.0.120 (Canary) 2025-06-24

[ts678]

@kenkendk

There is also a more agressive command (named abort internally) that will instead attempt to stop any processing immediately, potentially leaving partial files on the storage.

@kenkendk

The “Stop now” is the same as abort. It has a skull icon in ngclient, and you need to click “stop” before you can see that button.

Is the ngax “Stop now” supposed to error

instead of the ngax “Stop after the current file”

Often users think “A task was canceled” means they did something. It’s true here though.
I’m actually testing on 2.1.0.124, but the stop issue first began discussion roughly here…

@kenkendk

For the “soft stop” a new filelist will be uploaded, if any new data was encountered, as the backend will otherwise store “dangling” data until the next backup can upload a (synthetic) filelist.

If ngclient stop button is supposed to be like ngax “Stop now”, it seems to do a lot more, such as uploading a partial dlist file, and it also doesn’t need any changes to cause that.

2.1.0.122 Canary ngclient stop uploads a short dlist file

EDIT 1:

As evidence of no changes, I don’t have upload-unchanged-backups set, so no backup version and no dlist file is created on a normal repeat backup without any stops before it.