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

debug log all cache / index full paths #5963

Closed
ThomasWaldmann opened this issue Aug 21, 2021 · 10 comments · Fixed by #7388
Closed

debug log all cache / index full paths #5963

ThomasWaldmann opened this issue Aug 21, 2021 · 10 comments · Fixed by #7388

Comments

@ThomasWaldmann
Copy link
Member

Considering issues like #5954 are bad to solve / debug without this information, borg should debug log full paths of all caches / indexes it uses.

@Rsakhuja
Copy link

Rsakhuja commented Oct 6, 2022

Can I work on this issue if it's still open?

@ThomasWaldmann
Copy link
Member Author

@Rsakhuja sure, just take it! :-)

@sumeetdeveloper
Copy link

@Rsakhuja are you still working upon this issue

@ThomasWaldmann
Copy link
Member Author

@sumeetdeveloper if there is no response, i think we can just assume they are not working on this.

@sumeetdeveloper
Copy link

Shall I start working upon this issue then? if it is open?

@ThomasWaldmann
Copy link
Member Author

ThomasWaldmann commented Dec 22, 2022

Guess so, it's been a while since October. Thanks for helping!

@sumeetdeveloper
Copy link

@ThomasWaldmann can you help me to reproduce this issue or point any documentation or stuff

@ThomasWaldmann
Copy link
Member Author

@sumeetdeveloper Sure.

To start, just do a global search for cache_dir in the source.

@diivi
Copy link
Contributor

diivi commented Feb 26, 2023

@ThomasWaldmann How would you like this to be implemented? Should there be another command that logs the cache dir by using the get_cache_dir() function in fs.py? I need a little more context, thanks!

@ThomasWaldmann
Copy link
Member Author

@diivi read how the ticket linked from top post ended.

quite some work there could have been avoided if it were clear that it used a different cache dir than the user thought it did. maybe the user would have found the issue themselves, if --debug had output the full cache file path.

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.

4 participants