Smalyshev added a comment.
While full stack trace is not always useful, at least exception details often are the only thing that allows to figure out what actually happened. I know there are logs, but they are quite hard to link to a specific user's action, so user capturing the output is still the best. Now, the middle part of the trace is probably mostly useless, it's the root cause (deepest items) and the error message that are important. So if there's a way to compact it, like we do in logs, that'd be fine. But replacing it with blanket "something went wrong, no idea what" page I think would make it worse. BTW, I don't think `proxy_intercept_errors` changed much - we've always produced stack traces for errors like 400 and 500, e.g. see T115788 <https://phabricator.wikimedia.org/T115788>. TASK DETAIL https://phabricator.wikimedia.org/T216701 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel, Smalyshev Cc: gerritbot, Smalyshev, Gehel, Aklapper, CucyNoiD, Nandana, NebulousIris, Gaboe420, Versusxo, Majesticalreaper22, Giuliamocci, Adrian1985, Cpaulf30, Lahi, Gq86, Baloch007, Darkminds3113, Bsandipan, Lordiis, Lucas_Werkmeister_WMDE, GoranSMilovanovic, Adik2382, Th3d3v1ls, Ramalepe, Liugev6, QZanden, EBjune, merbst, LawExplorer, Lewizho99, Maathavan, _jensen, Jonas, Xmlizer, jkroll, Wikidata-bugs, Jdouglas, aude, Tobias1984, Manybubbles, Mbch331
_______________________________________________ Wikidata-bugs mailing list Wikidata-bugs@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
