Reports with invalid data will continue to be sent every two hours for 7 days

Bug #979082 reported by Evan Dandrea on 2012-04-11
This bug affects 1 person
Affects Status Importance Assigned to Milestone
whoopsie-daisy (Ubuntu)
Evan Dandrea

Bug Description

The crash database replies with a 400 HTTP error code when it encounters invalid data. We currently interpet this as a failure to send and retry at the queue processing interval (2 hours, currently). This will continue to happen until the apport cron job notices that the report and its upload file have existed for 7 days.

Evan Dandrea (ev) on 2012-04-11
Changed in whoopsie-daisy (Ubuntu):
assignee: nobody → Evan Dandrea (ev)
importance: Undecided → High
status: New → Confirmed
milestone: none → ubuntu-12.04
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package whoopsie-daisy - 0.1.29

whoopsie-daisy (0.1.29) precise; urgency=low

  * Mark reports as complete when we get a HTTP response of 400 from the
    server, as these represent the server not liking what we sent it.
    Sending these again repeatedly would be pointless (LP: #979082).
 -- Evan Dandrea <email address hidden> Wed, 11 Apr 2012 17:36:32 +0100

Changed in whoopsie-daisy (Ubuntu):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers