Maximilian Knespel
Maximilian Knespel
I'm not even sure whether FUSE and/or fusepy allows such as setup but I didn't try. For the mount point, it forks off a background process that keeps running. Maybe...
> It is an interesting idea, but I'm afraid will not work in our case, > because the various archives (and directories) are residing on > different disks > so...
> This generates ENORMOUS memory pressure on the system (especially when ratarmount distributed as AppImage because each invocation has seprate nonshared instance of python interpreter) Are you sure the only...
Care has to be taken because the daemonizing forks into the background and I have to join all threads, e.g., for the parallel bz2 decoder, before that fork and reopen...
> i can workaround by avoiding using `run_in_executor` and just calling the tool so not a huge blocker for us, and it speeds things up considerably compared to copying out...
Maybe you could also post a minimal example so I can reproduce it easily for testing purposes?
Btw, I'm not sure if it applies to your use case but you could also avoid forking into the background by specifying `--foreground` and then keep that process or thread...
It should only happen when the archive changes. Can you run with `-d 3`? I hope it has some more helpful output.
The check looks correct. Could it be that there are multiple archives named `file.tar`? It looks like there might be a collision when determining the save-location for the index. Is...
Then, I'm out of ideas and I can't reproduce it to test it in depth :/. I'm not sure how much time you are willing to put in to fix...