8000 Ability to specify where to store the checksum cache · Issue #1060 · emmercm/igir · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Ability to specify where to store the checksum cache #1060

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
TheBrainScrambler opened this issue Apr 1, 2024 · 4 comments · Fixed by #1115
Closed

Ability t 8000 o specify where to store the checksum cache #1060

TheBrainScrambler opened this issue Apr 1, 2024 · 4 comments · Fixed by #1115
Assignees
@emmercm
Labels
enhancement New feature or request

Comments

@TheBrainScrambler
Copy link

Is your feature request related to a problem?

I use igir as a package for the NixOS linux distributions, where all packages are stored in a read-only filesystem. igir is for example stored in /nix/store/3p7v7hfk60kqwhca514l3khvl4nbwa3f-igir-2.6.1. The problem is that igir tries to write the checksum cache in that directory, as you can see in the error below:

Σ Scanning for DATs ·········· | ██████████████████████▒░░ | 278/312 | ETA: 8snode:internal/process/promises:289
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: EROFS: read-only file system, open '/nix/store/3p7v7hfk60kqwhca514l3khvl4nbwa3f-igir-2.6.1/lib/node_modules/igir/igir.cache.v6n76u{
  errno: -30,
  code: 'EROFS',
  syscall: 'open',
  path: '/nix/store/3p7v7hfk60kqwhca514l3khvl4nbwa3f-igir-2.6.1/lib/node_modules/igir/igir.cache.v6n76u'
}

Node.js v20.11.1

As can you see in the error, it's with igir 2.6.1

Describe the solution you'd like

It would be better to have the cache stored in the user's $HOME, for example in the right XDG directory, or in $HOME/.cache/igir . But at least it would be nice if I had a flag to say myself where I want the cache to be store. Something ike --cache-dir <dir> perhaps ?

Additional context

No response
@TheBrainScrambler TheBrainScrambler added the enhancement New feature or request label Apr 1, 2024
@emmercm
Copy link
Owner
emmercm commented Apr 2, 2024

This is a good suggestion, I will work on it. You will probably need to use v2.5.3 until the problem can be fixed.

I've been working on fixing a performance regression affecting "raw copying" (when copying or moving without explicitly zipping or extracting). I'll work on this after.

@emmercm emmercm mentioned this issue Apr 6, 2024
Merged
@emmercm
Copy link
Owner
emmercm commented Apr 6, 2024

@TheBrainScrambler could you test #1070 on your machine? It should at least prevent the EROFS error.

@TheBrainScrambler
Copy link
Author

Testing v2.6.2, it seems to work, I get the cache file in ~/igir.cache

@emmercm emmercm mentioned this issue Apr 8, 2024
Closed
@emmercm emmercm mentioned this issue May 8, 2024
Merged
@emmercm emmercm self-assigned this May 8, 2024
@emmercm emmercm mentioned this issue May 22, 2024
Closed
@github-actions GitHub Actions
Copy link
github-actions bot commented Jun 8, 2024

🔒 Inactive issue lock

This 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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@emmercm emmercm

Labels 434C
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Feature: cache path option emmercm/igir
2 participants
@emmercm @TheBrainScrambler
0