Skip to content
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

work out why rocksdb doesn't like being cached #4

Closed
alsuren opened this issue Dec 16, 2021 · 1 comment · Fixed by #7
Closed

work out why rocksdb doesn't like being cached #4

alsuren opened this issue Dec 16, 2021 · 1 comment · Fixed by #7

Comments

@alsuren
Copy link
Contributor

alsuren commented Dec 16, 2021

No description provided.

@alecmocatta
Copy link
Collaborator

My current best guess is this is due to tokio_tar::Entry::unpack_in touching the mtime of a directory when it unpacks a file inside that directory? See alexcrichton/tar-rs#217. Mildly surprising that cargo's rerun-if-changed would trigger on a directory mtime changing.

@alecmocatta alecmocatta mentioned this issue Dec 18, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Correctly set directory mtimes cargo-quick/kache
2 participants
@alsuren @alecmocatta