238835 - Grand total in charting can show repeating zero values

Status: NEW

(Bugzilla :: Reporting/Charting, defect, P3)

Description

[Jussi Sirpoma]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: 

I have three datasets which are generated once in every 7 days. When I chart two
or more of these datasets, I get repeating zero grand total values. It could
have something to do with the odd frequency. I'll attach an image of this kind
of a chart.

Reproducible: Always
Steps to Reproduce:

Comment 1

[Jussi Sirpoma]

Attachment: Chart with wrong grand total

Here's a chart with wrong grand total curve. (Since I didn't mention it before,
I'm running cvs head version from a week ago)

Comment 2

[Gervase Markham [:gerv]]

Of course... now that you point it out, it's obvious that this will happen.

I'm not completely sure what to do about it, though... </me looks at code>

Gerv

Comment 3

[Gervase Markham [:gerv]]

This is one of those things where what seems like a small bug ends up being a
large architectural problem :-( I'm looking into creative ways to solve this
problem...

Gerv

Comment 4

[Dave Miller [:justdave]]

I'll take it if it gets fixed, but we're short on time and there's other
priorities I think...  not worth holding 2.18 for.

Comment 5

[Max Kanat-Alexander]

This bug has not been touched by its owner in over six months, even though it is
targeted to 2.20, for which the freeze is 10 days away. Unsetting the target
milestone, on the assumption that nobody is actually working on it or has any
plans to soon.

If you are the owner, and you plan to work on the bug, please give it a real
target milestone. If you are the owner, and you do *not* plan to work on it,
please reassign it to [e-mail] or a .bugs component owner. If you are
*anybody*, and you get this comment, and *you* plan to work on the bug, please
reassign it to yourself if you have the ability.

Comment 6

[Gervase Markham [:gerv]]

The correct fix here may be just to have all charts record once per day - i.e.
rip out the "frequency" parameter. I think I over-engineered...

Gerv

Comment 7

[Justin C. De Vries]

(In reply to comment #6)
> The correct fix here may be just to have all charts record once per day - i.e.
> rip out the "frequency" parameter. I think I over-engineered...
> 
> Gerv

This sound like an excelent solution. If you did this it would solve another problem that I descovered.

Comment 8

[Frédéric Buclin]

Only security and dataloss fixes will be accepted on the 2.20 branch.

Comment 10

[Frédéric Buclin]

The Bugzilla 3.0 branch is now locked to security bugs and dataloss fixes only. This bug doesn't fit into one of these two categories and is retargetted to 3.2 as part of a mass-change. To catch bugmails related to this mass-change, use lts081207 in your email client filter.

Comment 11

[Frédéric Buclin]

Bugzilla 3.2 is restricted to security bugs only. Moreover, this bug is either assigned to nobody or got no traction for several months now. Rather than retargetting it at each new release, I'm clearing the target milestone and the bug will be retargetted to some sensible release when someone starts fixing this bug for real (Bugzilla 3.8 more likely).

Comment 13

[martin.th.fei]

(In reply to Gervase Markham [:gerv] from comment #6)
> The correct fix here may be just to have all charts record once per day -
> i.e. rip out the "frequency" parameter. I think I over-engineered...

Do you mean this is something the creator of the data series should fix by setting frequency to 1? Or can you fix it programmatically? Such that, even though data is only recorded with odd frequency, the graph somehow interpolates missing intermittent values and thus builds correct grand totals and cumulates.