You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Feature request #448: Integrate WODebug crash reports into Rails backend

Kind feature request
Product WODebug
When Created , updated
Status open
Reporter Greg Hurrell
Tags no tags

Description

Taking request #446 one step further, it would be nice to integrate crash reports submitted by XML-RPC into the Rails backend. They could be automatically added to the bug reports database.

Comments

  1. Greg Hurrell

    Public changed:

    • From: false
    • To: true
  2. Greg Hurrell

    Summary changed:

    • From: REQUEST: Integrate crash reports into Rails backend
    • To: Integrate WODebug crash reports into Rails backend
  3. Greg Hurrell

    Ok, so the website is already able to accept new issues via an XML POST request, but I wonder if it might be better to accept crash reports as attachments rather than as inline content in the description field.

    I think seeing it in the description field is nicer in some ways, but given that this site expects wikitext input it means we'd have to enclose the submitted report in "pre" tags and that in itself might look a bit strange. So will have to weigh this up and think about which approach will be the best.

    See also:

  4. Greg Hurrell

    Going to change the product assignment seeing as most of the work has to be done in WODebug. The portin which (might) have to be done on the server side is probably already covered by ticket #1193.

  5. Greg Hurrell

    Product changed:

    • From: wincent.dev
    • To: WODebug
  6. Greg Hurrell 
    $ cat crash_report.xml 
<?xml version="1.0" encoding="UTF-8" ?>
<issue>
  <summary>Crash report</summary>
  <product_id>1</product_id>
  <description>Well, it don't work</description>
</issue>
$ curl -d @crash_report.xml -k https://localhost:3002/issues.xml
<html><body>You are being <a href="https://localhost:3002/issues/29">redirected</a>.</body></html>

    So it works already but there are a couple of possible changes I might want to make:

    • require some kind of basic (weak) authentication to protect against trivial (non-serious) spam attacks
    • specifically handle the redirect: ie. show it to the user in the UI so that they can track the issue if they want
Add a comment

Comments are now closed for this issue.

Menu