Closed Bug 274043 Opened 21 years ago Closed 20 years ago

collectstats.pl seems to fail if bugzilla site is https://...

Categories

(Bugzilla :: Reporting/Charting, defect)

x86
Linux
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 211164

People

(Reporter: holger.d.patzelt, Assigned: gerv)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 We have two sites using https (besides other, which don't) and these face the problem that collectstats.pl seems to lack a correct counting because since 2.18rc3 (was 2.16.3 before) the count in all "NEW style" charts are 0. Using the "old style" charts, counts are correct. Looking into the series_data table collectstats.pl produces a long list of entries with a series_value = 0 I rate this bug as critical, because it mangles the charting data. Reproducible: Always Steps to Reproduce: 1.deleting the series_value=0 entries from the table -> charts are correct 2.running collectstats.pl -> Charts show 0 count for all (!!) states Actual Results: Charts show 0 count for all (!!) states Expected Results: expected would be the same count as queries show for each state
Flags: blocking2.18+
sorry must be collectstats, not chart.pl because of the data in the database...
Summary: collectstats.pl or chart.pl seems to fail if bugzilla site is https://... → collectstats.pl seems to fail if bugzilla site is https://...
Flags: blocking2.18+ → blocking2.18?
Holger: I've just noticed that the chart migration code gives the migrated charts an owner of 0 - that is to say, no-one. That means that any bugs which are in groups will not be counted. Are all the bugs in your https:// installations in at least one group? Gerv
Hi Gerv, your suggestion sounds reasonable to me, you might be right. Since I don`t have the time to check today, I'll have a try in the next days and will give you feedback then. holger
Hi Gerv, you are right. Only bugs get counted, which do not belong to a group. Is there any chance to get some kind of fix here (eg. within the final 2.18 release ??) I think the user/group access rights have to be checked while generating the charts, because how else is there a chance to make sure the user does not get knowledge by the statistics he would not get otherwise. (eg. to see, that there are more serious bugs than he can see by doing a querry.) bye, hop
From what I gather, do you think it is possible to RESOLVE this bug INVALID and remove the pending blocking2.18?
This shouldn't block 2.18. It's a limitation of the current charting system. Holger: you can sort this out by editing your database so that all of the automatically-generated charts have a different owner - someone with permission to see all the bugs. UPDATE series SET creator = X where creator = 0; where X is the userid (number) of a user with the appropriate permissions. You can get userids from the profiles table. Gerv
Flags: blocking2.18?
Please reopen if I'm wrong. *** This bug has been marked as a duplicate of 211164 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.