You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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)
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?
The text was updated successfully, but these errors were encountered: