Page MenuHomePhabricator

Phabricator exception stack traces should include a call-to-action
Closed, WontfixPublic

Description

Most Phabricator users are engineers. Exception displays can be improved:

  1. Better formatting of the stack trace, links to diffusion where possible. This lowers the barrier to insta-debugging the problem.
  2. Include a call to action to dive in and fix the problem
  3. Link to create/edit a Maniphest task for the problem

Revisions and Commits

Event Timeline

aran triaged this task as Low priority.
aran added a project: Phabricator.
aran added subscribers: aran, epriestley.
epriestley changed file(s), attached 0: ; detached 0: .Jul 7 2011, 7:50 PM

It would also be good to have a "send this stack trace to the mothership" option here, especially if we do a bit of tracetool-style buildout to support trace management.

epriestley changed file(s), attached 0: ; detached 0: .Aug 17 2011, 9:32 PM

Still working on this? Seems useful. :)

I want to build the "send this back to the mothership" option. I'm thinking you get shown a dialogue that is pre-filled with

to: <bugs@phabricator.com> 
subject: exception in <filename> 
body: Please provide any relevant details to help reproduce this problem:
  <glorious white space>
  <exception>

Users can modify all that stuff.

I think that's enough to close this one out.

Sound good?

T7376 added some more information here and would let us produce "You are out of date / your junk is full of local custom code which we don't support" messages.

chad changed the visibility from "All Users" to "Public (No Login Required)".Jul 20 2015, 3:12 AM
epriestley claimed this task.
epriestley added a project: Nuance.

Given the modern realities of support, I don't actually think we'd be better off by making it easier to submit stack traces. We also explicitly don't want surprise patches.