Improve semi-automatic bug reporting

[eblot]

... before releasing 0.11.

The improved error report generates wikified data that users are not able to report properly on trac.edgewall.org.
This new report leads to badly formatted bug reports, which requires manual fix (time consuming, error prone).

I'm not sure how to fix this problem, but 0.11 should not be released before the error report is improved.

[cboos]

athomas fixed a bug in the semi-automatic error reporting (r5663) and apparently since then, the reports are OK, at least their how I expect them to be. See #5511 - do you see anything to improve there?

[cboos]

I guess it's mostly OK as it is, but there's one improvement I'd like to see, mainly the list of plugins and their versions in the System Information.

Having this would probably help a lot when dealing with people upgrading to 0.11.

[ThurnerRupert]

its not a bug, so it seems to block 0.11 unecessarily ...

[cboos]

It doesn't block 0.11, but it would nevertheless be really useful to have it in time for 0.11, as explained in comment:3. Motivated by #6948 of this morning, I decided to do it. I think we should help people to report plugin failures to their appropriate maintainer, as we have all the relevant information.

This currently doesn't work well for eggs, partly because of a bug in the admin code. So while this is not the final version of the patch, it already works well and provides useful information.

Feedback on attachment:show-enabled-plugins-in-error-page-r6658.diff appreciated.

[cboos]

This adds the relevant plugins information to the error page. It also tries to identify the faulty plugins (this part needs to be expanded to handle plugins installed as eggs).

[cboos]

Fixed and improved version of the patch

[cboos]

The new version of the patch (needs r6675) is a greatly enhanced version of the initial patch.

It now properly identifies the culprit plugin if any, even those installed as eggs. If a plugin is involved, the searching link and Create button are not targeting t.e.o's Trac but rather the one indicated by the plugin metadata information (trac entry - I have yet to check if that's possible for eggs) or trac-hacks if the home_page points there.

[cboos]

I'll try to rework the patch to simplify it and focus on identifying which plugin is eventually involved in the backtrace, as this is the really important information and it can't always be deduced by simply looking at the backtrace.

[anonymous]

I would like my customers to automatically report bugs to my Trac system. How do I install this feature on development machine? How is the bug report routed to my location? What happens when the user decides to report the bug?

[eblot]

Replying to anonymous:

I would like my customers to automatically report bugs to my Trac system. How do I install this feature on development machine? How is the bug report routed to my location? What happens when the user decides to report the bug?

About support questions:
Support and installation questions should be asked on the mailing list or IRC channel, not filed as tickets. Also, please check whether the issue you've encountered has been reported before.