bucket page for failed retraces empty

Bug #1154275 reported by Brian Murray on 2013-03-12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Changed in errors:
importance: Undecided → High
Evan (ev) wrote :

I think this is in daisy. We must not be bucketing the instances of the failed retrace into the 'failed:...' key.

Changed in errors:
status: New → Triaged
Brian Murray (brian-murray) wrote :

There is now a notification regarding the fact that it failed to retrace but the page still feels empty. Perhaps hiding the tables would make for a better experience.

Evan (ev) wrote :

I think the tables should have information in them, and that's the crux of this bug. The only thing we cannot show in the case of a failed retrace is the Stacktrace section. Everything else – the version counts, the average number of occurrences graph, the examples table – should have data in the from those reports that map to the Stacktrace Address Signature (which failed to retrace) for which this bucket represents.

Evan (ev) wrote :

The above problem had an instance count of two, despite there being nothing on the bucket page.

Brian Murray (brian-murray) wrote :

I'm pretty sure I fixed this yesterday with the following change:

revno: 453
committer: Brian Murray <email address hidden>
branch nick: errors
timestamp: Wed 2014-02-19 15:04:45 -0800
  urlencode and dequote bucketid so characters like + and probably \n work properly in bucketids

characters like + were not being urlencoded when being passed to the api so nothing was being returned. An example of this fix can be found here:


Notice the '+'s in the bucket id and that the version table is not empty nor is the instances table.

Changed in errors:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers