The real reason was a boring one and seemingly unrelated to that file. I just ran out of disk space. Still though, that’s not exactly a helpful error is it
Ah yes, the fabled ‘Task succeded failurely’
To be fair, most people who try to copy success fail.
Lot of && in that message. The success reason may not be related to the copy failure reason but to another part of the commands?
Without seeing the command it isn’t really possible to tell.
What does it matter what came before or after the offending command? Clearly,
/usr/bin/arsays it’s unable to copy a file because ofSuccess, which is a bullshit error message whithin or without [Edit:a pipe&&].In C/C++, it’s very common for a function to return an integer corresponding to any errors that occured within the function, including a “success” error code, because it has to return something, otherwise it’s undefined.
I’m not sure that’s what happened here but that’s why “successful” errors are a thing. Somewhere it got misinterpreted maybe.
