Package "Popularity" values inconsistent in different sources.
-
I confirm that this is an issue with aurweb's code and not a user-uploaded package. -
I have described the bug in complete detail in the Description section. -
I have specified steps in the Reproduction section. -
I have included any logs related to the bug in the Logs section. -
I have included the versions which are affected in the Version(s) section.
Description
Now I know that the "decay calculation" is supposed to be done by the clients, but I think that was only intended to be done for the data in the new git archive(s) to reduce the number of changes.
Current situation seems to be:
source | decay calc |
---|---|
rpc | yes |
git archives | yes |
gz archives | no |
package page | yes |
dashboard | no |
I think the desired situation was:
source | decay calc |
---|---|
rpc | yes |
git archives | no |
gz archives | yes |
package page | yes |
dashboard | yes |
(So basically the decay calc should be done everywhere but for the git archives)
yes = supposed to be done by aurweb
no = client needs to calculate itself
Reproduction
Check the popularity value for a package that has some votes/popularity (but did not get any votes in the last couple of days) and compare the different sources.
Version(s)
since v6.1.6