Flames misplaced on bug report page

Bug #528374 reported by Matthew Paul Thomas
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Abel Deuring

Bug Description

On a bug report page, there are flames sitting weirdly on a row by themselves, left-aligned with wherever the left edge of the first occurrence of the bug number happens to be. There's also an odd gap between the right edge of the timestamp and the right edge of the page.

Presumably the flames are supposed to be in the gap. Moving the flames anywhere else would also fix this bug.

Related branches

Revision history for this message
Matthew Paul Thomas (mpt) wrote :
Revision history for this message
Deryck Hodge (deryck) wrote :

This needs to be fixed before the 10.02 rollout.

Changed in malone:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Abel Deuring (adeuring)
milestone: none → 10.02
tags: added: story-bug-heat
Revision history for this message
Deryck Hodge (deryck) wrote :

Also, if you look at Ubuntu's hot bugs list, the hottest bug is missing it's image. Not sure if that is related to the landing that introduced this bug. If so, it should be fixed with this; if not, we should open a new bug.

Revision history for this message
Abel Deuring (adeuring) wrote :

I think the reason for this "7 out of 4 heat flames" bugs is already fixed in db-devel:

edge uses an old variant of the heat display which uses the constant MAX_HEAT. Its value is 5000, while the hottest Ubuntu bug has a heat value of 9676. And calculating floor(4 * 9676 / 5000) gives the value 7.

Since db-devel meanwhile uses a per-target max heat value, such an odd situation should not occur there. But since a value like floor(relative_heat * 4) is used in the new implementation too, and since this number is used to create the URL for an image, we should guard against that kind os nonsensical display by simply limiting the calulated "heat index" to 4

Revision history for this message
Abel Deuring (adeuring) wrote :

...just for the case that the per-project max heat value is outdated...

Deryck Hodge (deryck)
Changed in malone:
status: Triaged → In Progress
Revision history for this message
Diogo Matsubara (matsubara) wrote : Bug fixed by a commit
Changed in malone:
status: In Progress → Fix Committed
Abel Deuring (adeuring)
Changed in malone:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.