Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.
Related: #3189
The logs containing filepaths is the reason I haven't posted any debug logs. Offer to create 2 archives: 1 being the normal 'sensitive' one, and other where directories and filenames have been replaced by pseudonames.
2 because then you may before or later match up the problematic paths.
I think this would be a great enhancement. Someone will need to:
inventory all (or at least the most common) potential sensitive values
build the logic to replace these values with dummy ones that are still consistent throughout the logs (so the logs remain useful) and make it extensible enough that new sensitive values can easily be added to it over time
extend the user interface to support both modes
PR are always welcome. :)
In the mean time:
Global search and replace
Share only limited excerpts (can be edited and cleared of information deemed sensitive in a more manageable manner)
How to use GitHub
Related: #3189
The logs containing filepaths is the reason I haven't posted any debug logs. Offer to create 2 archives: 1 being the normal 'sensitive' one, and other where directories and filenames have been replaced by pseudonames.
2 because then you may before or later match up the problematic paths.
Paths before example:
After: