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
re-implement cache folder detection #11130
Conversation
4c290e7
to
d6be77e
Compare
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #11130 +/- ##
==========================================
- Coverage 57.42% 57.11% -0.31%
==========================================
Files 129 133 +4
Lines 11299 11324 +25
==========================================
- Hits 6488 6468 -20
- Misses 4182 4230 +48
+ Partials 629 626 -3
☔ View full report in Codecov by Sentry. |
2f66695
to
943a049
Compare
If this implementation is copying the original code, we probably must include the copyright information from the original;
|
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
What I did
replace
xdg.CacheFile
with our own implementation (basically, a copy/paste) so that we detectHOME
is not set and don't assume we can use/
as a replacement. Unclear to me if this is legitimate from a Posix point of view, but we should offer users a better error message for diagnostic than "can't write /.cache/docker-compose"Related issue
closes #11126
closes #11137
(not mandatory) A picture of a cute animal, if possible in relation to what you did