Attach path to failed put errors about bupstash HOT 4 OPEN

Yeah, at the very least it should be mentioning the path.

Any chance of getting an strace log to help track down the cause?

from bupstash.

My initial debugging plan rested on the assumption that this is some IO error, in which case knowing the file and maybe also the operation in code that failed should be enough to debug it. However, it looks like this error may also come from different operations, for example spawning threads, in which case I'll probably have to do some strace inspection. I'd like to avoid it if possible though, especially since I think that we should have those error messages anyways.

from bupstash.

Interesting, it could be hitting some resource limits.

from bupstash.

For the error handling, it looks like enabling the "backtrace" feature on the anyhow crate and then RUST_BACKTRACE=1 should be enough to get source information from all errors. Only thing left to test is if the error printing at the bottom of the main function also automatically makes use of that information.

For better or for worse, I can't reproduce my original error which prompted this investigation on master anymore. So it must have been fixed between 0.12 and 7082d77 somehow.

from bupstash.