Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
task_small.png
CLOSED  Task #160  -  Integrate the crash reporter with the new bug tracker.
Posted Feb 20, 2012 - updated Mar 08, 2012   Shortlink: http://arx.vg/160
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Done" and resolution "RESOLVED".
Issue details
  • Type of issue
    Task
  • Status
     
    		 Done
  • Assigned to
  • Progress
       
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    Daniel Scharrer
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    Not determined
  • Resolution
    RESOLVED
  • Priority
    Not determined
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
The crash reporter should be able to automatically open bug reports.

#4
icon_reply.pngReply
Comment posted by
Guest user
Feb 21, 03:03
I haven't done a lot of web programming before, so i'll post some info here as a reference for me and maybe others too smileys/2.png

POST METHOD  ⇑ top

Getting the post data sent by the form (with Chrome)  ⇑ top

  • Open the page for which you want to obtain the POST info, and fill the form
  • In chrome, activate Chrome Developer Tools by pressing Shift+Ctrl+I
  • Switch to the Network tab
  • Send the form data... Chrome should log all network operations
  • Right-click on the row containing information about the POST (should be the first row), then select "Copy entry as HAR"
  • Switch to the Console tab
  • Type "HAR=" then paste the HAR and press enter

Sending post data from C++  ⇑ top

  • Should we use libcurl ? Seems to be available on all platforms

Attaching a file  ⇑ top

  • With TBG, this has to be done after the issue is created
  • It also needs to have a user logged in
#5
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Feb 23, 20:17
Should we use libcurl ? Seems to be available on all platforms


Since we already use Qt for the crash reporter, QNetwork would be the best choice, right?
#6
icon_reply.pngReply
Comment posted by
SebastienLussier
Feb 25, 01:59
QNetwork could be an option, unless you want to provide another reporting command line app...
#7
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Feb 25, 02:06
I don't think there is a point in a command-line reporting app as it would need to be interactive. Just dumping the complete crash report to a file if crashreporter / Qt is not available should be enough.

#10
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Feb 25, 02:16
Anyway:

Login  ⇑ top

POST to https://bugs.arx-libertatis.org/do/login

with 

 tbg3_password=<password>
 tbg3_referer=<login_redirect>
 tbg3_username=<username>


will set a cookie

Create Issue  ⇑ top

POST to https://bugs.arx-libertatis.org/arx/issues/new

with 

 project_id=2
 issuetype_id=1
 title=<title>
 description=<description>
 reproduction_steps=
 build_id=1
 component_id=
 category_id=0
 reproducability_id=0
 estimated_time=
 priority_id=0
 resolution_id=0
 severity_id=0


will redirect to /arx/issues/<issue_number>

Test issue to play around with: https://bugs.arx-libertatis.org/arx/issues/163
#12
icon_reply.pngReply
Comment posted by
SebastienLussier
Mar 08, 01:17
I think we can mark this task as done smileys/2.png There are other issues for remaining problems/features

The issue was updated with the following change(s):
  • This issue has been closed
  • The status has been updated, from New to Done.
  • This issue's progression has been updated to 100 percent completed.
  • The resolution has been updated, from Not determined to RESOLVED.