Skip to content
This repository has been archived by the owner on Feb 8, 2018. It is now read-only.

review computation of cached values #3729

Closed
chadwhitacre opened this issue Aug 31, 2015 · 11 comments
Closed

review computation of cached values #3729

chadwhitacre opened this issue Aug 31, 2015 · 11 comments
Milestone

Comments

@chadwhitacre
Copy link
Contributor

From @book at #3666 (comment):

[T]he "Takes" total is different from what I actually receive each week.

@chadwhitacre
Copy link
Contributor Author

+1 @anselmh on #3756.

@chadwhitacre chadwhitacre modified the milestones: Basic Math, Pivot Oct 23, 2015
@chadwhitacre
Copy link
Contributor Author

Looking at this w/ @kaguillera ...

@chadwhitacre
Copy link
Contributor Author

Picking up from #3721 (comment), here are the cached values we want to review:

       sum           count             sharing bit
       ------------------------------------------------
~user  giving        ngiving_to        anonymous_giving
       taking        ntaking_from      —

Team   receiving     nreceiving_from   —
       distributing  ndistributing_to  —

@chadwhitacre
Copy link
Contributor Author

#3756 and #3793 are subtickets of this one.

@chadwhitacre
Copy link
Contributor Author

Alright, so while it wouldn't be bad to review the computation of cached values, it seems that that's not the main problem. Let's assume we are computing cached values properly: the problem still remains that ~user expectations differ from what we're showing right now.

@chadwhitacre
Copy link
Contributor Author

So what's the expectation and what are we showing instead?

@chadwhitacre
Copy link
Contributor Author

#3756 and #3793 are subtickets of this one.

Not subtickets, unless our review of computation reveals actual computation bugs. See gratipay/inside.gratipay.com#383 (comment).

@chadwhitacre
Copy link
Contributor Author

Let's assume we are computing cached values properly

Now let's test that assumption. :-)

@chadwhitacre
Copy link
Contributor Author

Okay, #3793 is not due to bad math. It's a presentation bug.

@chadwhitacre
Copy link
Contributor Author

Neither is #3756. Closing.

@chadwhitacre
Copy link
Contributor Author

(And #3666 (comment), which lay behind this ticket, was folded into #3756.)

@chadwhitacre chadwhitacre mentioned this issue May 12, 2016
11 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant