bucket page for failed retraces empty

[Brian Murray]

The bucket page for a failed retrace does not contain any information:

https://errors.ubuntu.com/bucket/?id=failed%3A%2Fusr%2Fbin%2Fupdate-notifier%3A11%3Ai686%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3400.1%2B120ce%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3400.1%2B108d8%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3400.1%2Bdad1%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3400.1%2B26e77%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3400.1%2B27d35%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Fgio%2Fmodules%2Flibgioremote-volume-monitor.so%2Bb0f9%3A%2Flib%2Fi386-linux-gnu%2Flibglib-2.0.so.0.3400.1%2B43c30%3A%2Flib%2Fi386-linux-gnu%2Flibglib-2.0.so.0.3400.1%2B469e3%3A%2Flib%2Fi386-linux-gnu%2Flibglib-2.0.so.0.3400.1%2B46d80%3A%2Flib%2Fi386-linux-gnu%2Flibglib-2.0.so.0.3400.1%2B471db%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgtk-3.so.0.600.0%2B195f5d%3A%2Fusr%2Fbin%2Fupdate-notifier%2B4ca2

Just choose any of the most common problems functions that start with failed (visible in the hyperlink) and you'll see an empty bucket page. Nothing shows up in the graph, versions table or examples table.

[Evan (ev)]

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

[Brian Murray (brian-murray)]

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)]

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)]

https://errors.ubuntu.com/bucket/?id=failed%3A%2Fusr%2Fbin%2Fwhoopsie%3A11%3Ai686%3A%2Fusr%2Fbin%2Fwhoopsie%2B43f8%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3507.0%2B10a52%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3507.0%2Bdd56%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3507.0%2B20e76%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3507.0%2B293a9%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3507.0%2B295a3%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3507.0%2B1255f%3A%2Fusr%2Flib%2Fi386-linux-gnu%2Flibgobject-2.0.so.0.3507.0%2B142c0%3A%2Fusr%2Flib%2Flibnm-glib.so.4.4.0%2Ba86e%3A%2Flib%2Fi386-linux-gnu%2Flibglib-2.0.so.0.3507.0%2B44e50%3A%2Flib%2Fi386-linux-gnu%2Flibglib-2.0.so.0.3507.0%2B482f3%3A%2Flib%2Fi386-linux-gnu%2Flibglib-2.0.so.0.3507.0%2B48690%3A%2Flib%2Fi386-linux-gnu%2Flibglib-2.0.so.0.3507.0%2B48b6b%3A%2Fusr%2Fbin%2Fwhoopsie%2B21ce%3A%2Flib%2Fi386-linux-gnu%2Flibc-2.17.so%2B19935

is another example of this.

[Evan (ev)]

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

[Brian Murray (brian-murray)]

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
message:
  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:

https://errors.ubuntu.com/problem/f95da5ec05ef4763b40272b088053a769aafece5

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