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

[feature] See in logs when files were taken from the Download cache #14285

Closed
1 task done
MTomBosch opened this issue Jul 13, 2023 · 4 comments · Fixed by #14716
Closed
1 task done

[feature] See in logs when files were taken from the Download cache #14285

MTomBosch opened this issue Jul 13, 2023 · 4 comments · Fixed by #14716
Assignees
Milestone

Comments

@MTomBosch
Copy link

What is your suggestion?

Dear Conan dev team
As follow-up of #12129 I would like Conan (1.x and 2.x) to print to the debug log/Conan trace file when a file is not downloaded from the remote repository but instead taken from the download cache (and then unzipped into the package cache folder).

Our use case for this is:
We are heavily using the download cache (stored on a share network drive) and sometimes our Conan install duration is very long. We have the feeling that this is due to slow access to the download cache but to be sure we want to check if the long duration of Conan install happens when files are taken from the download cache.

Have you read the CONTRIBUTING guide?

  • I've read the CONTRIBUTING guide
@memsharded memsharded added this to the 2.0.9 milestone Jul 17, 2023
@memsharded
Copy link
Member

Hi @MTomBosch

Thanks for the suggestion.
I think it makes sense to have some output with this information. Even something minimal with the default logging level if possible, but if too much, then yes, at least as verbose output.

@MTomBosch
Copy link
Author

Since we are still stuck with 1.x for some more time it would be great if this feature could be added to 2.x and 1.x as well.

@memsharded
Copy link
Member

In 1.X it would be probably way more complicated, as it didn't implement logging levels correctly, and it can be very noisy.
This kind of UX improvement is likely that will be only targeted to 2.0, we will first target it and based on the final solution, consider backporting (but as said, this kind of improvement commonly doesn't get enough relevance to be backported)

@memsharded memsharded modified the milestones: 2.0.9, 2.0.10 Jul 19, 2023
@memsharded memsharded modified the milestones: 2.0.10, 2.0.11 Aug 20, 2023
@memsharded memsharded self-assigned this Sep 11, 2023
@memsharded
Copy link
Member

Implmented in #14716 for next 2.0.11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants