Last modified: 2014-05-10 11:46:00 UTC
In trunk after the FileBackend branch merge, many error messages related to files have mwstore:// URLs as message parameters. This risks being even more confusing than the "public" placeholder that I introduced in filerepo, which drew many complaints from users. I think replacing the "mwstore://local-backend/local-public" prefix with a simple "..." by default would be less confusing to ordinary humans. For sysadmins, optionally converting the mwstore:// URLs to some backend-specific identifier (for example actual filesystem paths) would be a useful debugging tool.
Milestone 1.19.0 since these errors are mostly seen by non-Wikimedia users.
(In reply to comment #0) > I think replacing the "mwstore://local-backend/local-public" prefix with a > simple "..." by default would be less confusing to ordinary humans. Maybe...I'd prefer to keep the container, in case a failed up was moving some file from one zone to another, likely with the same relative paths. > For sysadmins, optionally converting the mwstore:// URLs to some backend-specific > identifier (for example actual filesystem paths) would be a useful debugging > tool. Can't we just use trigger_error() or something and put more descriptive paths in there (e.g. absolute FS paths or real swift paths)? This would aid in debugging without conflating UI errors with detailed errors for admin debugging.
Error logs should be better with r112347.
With r112347, this is hopefully good enough for most purposes. Will fix up right eventually. Taking off of Aaron since this he probably won't have time for this soon.
I got this when uploading a file on installation close to master (55b5b9f52dad8466749ea43819c1aff23b0044cd) and I got this: Das Verzeichnis „mwstore://local-backend/local-public/e/e0“ konnte nicht angelegt werden, which is "directorycreateerror".
Note: As this has the 1.21.0 target milestone set (bumped from 1.20, bumped from 1.19), this would require some final cleanup as written in comment 4. If this does not happen in the next weeks, the Target Milestone will likely get removed.
