https://bugs.kde.org/show_bug.cgi?id=525171
--- Comment #5 from Bharadwaj Raju <[email protected]> --- (In reply to Nate Graham from comment #4) > Yeah, which is all good! > > Basically I'm wondering if we really need to consider this an error from a > reporting standpoint. It leaks Vault paths into the log, at a minimum, which > isn't great. True, it was useful for debugging in the early stages, but I guess we can remove it now. Alternatively, since vaults *do* have a StorageAccess, we could check its `encrypted` property and only print the log if it's not encrypted... but that's probably overthinking it. -- You are receiving this mail because: You are watching all bug changes.
