--cache-path Option Being Ignored? #1135
Assignees
Labels
bug
A confirmed issues that needs fixing
Comments
|
Definitely a bug. It's still writing zero-byte cache files to the old directories even if a custom path is provided. It's how I was testing what path is writable (#1060). Separately, the path provided should be a file rather than a directory, so |
🔒 Inactive issue lockThis issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. Comment generated by the GitHub Lock Issues workflow. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Paste the command
Describe the bug
I could just be doing something wrong, but when I try to use the new
--cache-pathoption, the trace log saysOr
But then the cache file still ends up in my home directory instead of where I want it.
Expected behavior
For the cache file to be created where
--cache-pathpoints to.Debug logs
output.log
DAT(s) used
No response
igir version
2.7.0
Node.js version
v22.2.0
Operating system
Arch Linux
Additional context
The super weird part is that if I run the exact same command a second time, it puts the cache file in the working directory (
--cache-path .), as I would expect it to.Also if I give it a name (
--cache-path ./cachetest.cache) it will always on first run put aigir.cachefile in my home directory, and then a second run it will put aigir.cachein the working directory. Which is to say, it's ignoring the filename I am specifying. But maybe that's expected, not sure.Actually, I just deleted both cache files (home directory and in my working directory of
/home/pcx/Desktop/test) and then ran this command:First time running it, it makes
igir.cachein my home directory, second time it's created in my working directory (???), third time and more it doesn't make any other files. The/home/pcx/Desktop/cachetest.cacheis never created. I am very confused on how it made one in my working directory when I never specified it in the command...Any help would be appreciated!
The text was updated successfully, but these errors were encountered: