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.

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

Figure out missing pieces #16

Closed
Jake-Shadle opened this issue Nov 14, 2019 · 1 comment · Fixed by #152
Closed

Figure out missing pieces #16

Jake-Shadle opened this issue Nov 14, 2019 · 1 comment · Fixed by #152
Labels
bug Something isn't working

Comments

@Jake-Shadle
Copy link
Member

Running cargo fetch immediately after cargo fetcher sync still results in several seconds of work on Linux, when it should be basically nothing. There is probably something missing during a sync that cargo relies on for a "freshness" check, but I haven't found a likely culprit. This is far worse on Windows however, which is the bigger problem.

@Jake-Shadle Jake-Shadle added the bug Something isn't working label Nov 14, 2019
@Jake-Shadle
Copy link
Member Author

I think this was improved a bit with 0.7.0, but there is still a big problem, particularly on Windows with the index. It seems that Windows just reclones the entirety of the index which is very obvious since it takes like 3 minutes, but it's possible the same problem exists on linux, you just don't notice it because the filesystem isn't stupid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant