Smalyshev added a comment.
> On our end we can run it and retrieve the stack trace. Provided it reproduces, which is not always the case - can be user error, can be intermittent factors, can be that by the time we get to triage the error, the data has changed. It's much better to see the error as the user saw it - otherwise we'd get a lot of "can't reproduce" back and forth with the user, which is frustrating from both sides. When we have full diagnostics, at least we know what we've dealing with. > Our 500 page could include helpful link to phabricator to report query that failed. Not every failed query should be reported to phabricator. But if you report it, providing stack trace is usually very helpful. Reporting just "this query breaks" provides one more step to resolution that can - and often does - miss data. > but a world-wide accessible trace seems a problem security wise. How it's a problem security wise? What security is violated by this? Our code is open source, our data is open source. Which specifically security boundary is crossed? What are we trying to hide there? TASK DETAIL https://phabricator.wikimedia.org/T216701 EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Gehel, Smalyshev Cc: Nuria, hoo, csteipp, dpatrick, Lucas_Werkmeister_WMDE, abian, Mvolz, gerritbot, Smalyshev, Gehel, Aklapper, CucyNoiD, Nandana, NebulousIris, Gaboe420, Versusxo, Majesticalreaper22, Giuliamocci, Adrian1985, Cpaulf30, Lahi, Gq86, Baloch007, Darkminds3113, Bsandipan, Lordiis, 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
