-
Notifications
You must be signed in to change notification settings - Fork 308
run Gittip 101 #2362
Comments
Reviewed 62 accounts. Left 3 unreviewed (see #2341). |
Backup taken and verified. |
Droplet spun up and updated. |
Script started. |
|
I updated the droplet improperly. I forgot to pull before making. |
Script restarted. |
|
|
Why is pending NULL? |
Pending is NULL for 43972 participants. |
There are 73659 participants total. |
Maybe @aaronwinborn was added to the Drupal team during payday? |
That's the sort of thing that happened the last time we had issues around pending, way back (will have to dig for that). |
|
Last payday (#2340) was 2014-05-01. |
The only place where pending is explicitly set to NULL is in |
But I seem to recall that NULL + 0 results in a NULL, and that we've had that happen before. |
|
Sanity check:
|
Why is |
@Changaco We use |
Okay! @aaronwinborn hasn't joined Gittip. :-) |
That is, https://www.gittip.com/aaronwinborn/ is redirecting to https://www.gittip.com/on/github/aaronwinborn/. |
So the question is, how is aaronwinborn part of the DrupalMedia team without being a member of the site? |
Okay! So, aaronwinborn's participant record was created at 2012-07-11 14:48:30.679927+00, which is before we started using randomized usernames for stub participants. The bug is that stub participants can be added as members of a team. A quick query of username and ctime shows that 2012-09-13 is the cutoff. That was the date we started using randomized usernames for stub participants. Precluding adding stub participants as team members ticketed as #2364. Randomizing usernames for old stub participants reticketed as #2365. |
So what's the fix here? We should delete from |
That's out of scope here, anyway. That's not a bug we need to fix or repair here. |
We've so far identified two causes of duplicate transfers:
Does that account for all of the duplicates we're seeing? |
Let's assume for the moment that all of the duplicate transfers before last payday are due to taking from a team that gives to you. Let's look at just the duplicates from last payday. Let's assume there are up to three amongst the 66 that are also legitimate. So we have 63-66 bad duplicates. Here's the question (IRC): What are the dollar amounts involved? Turns out there are only five duplicates that are $10 or more. They're all on the Gittip team. The sixth-highest (at $4) is also from Gittip. Here's a breakdown:
There are 23 teams affected by this. It's really only the Gittip team where the dollar amounts are at all problematic. One option is to simply say that this was a mistake and let the teams eat it. Right now the teams are eating it. Some team members received more than their fair share. Except for Gittip, the amounts are so low and the teams are so barely active that it's really not a big deal. Since we are Gittip :-) we can ask ourselves: are we okay with 12 of our members getting a bonus last week? Here are the people in question and the amounts of their bonuses:
Personally I'm fine giving these folks a bonus. I think that makes more sense than spending more time trying to reverse this. In which case, we can call it case closed on the assessment and db repair, and move on to fixing the bugs that landed us here in the first place. Any objections? |
I'm going to proceed on that basis. |
Object if you want to! :-) |
Cool. I'd like to do a one-time split with @rummik, if that's cool. I've just adjusted Kim's amount accordingly, and I'll adjust back after payday :) |
Now I'm looking at this constrained by I'm writing up a blog post about this, somewhere to point people if/when they notice.
|
Awesome, thanks @patcon! :-) |
|
That's $163.33 total. |
Not sure why my result differs from @Changaco's: #2362 (comment). |
The |
Now I'm at 141.34, which fits with @Changaco's earlier result. |
Now to determine which teams never got paid at all. |
This would be any teams after the first failure. |
Actually, any later members of the team we were processing when we crashed would also have not gotten a payout. |
Using |
This is also inferrable from their Members page: |
Okay, so how many teams are after the DrupalMedia team? |
|
|
Blog post published: https://twitter.com/Gittip/status/466684829040656387. |
Case closed. |
100
The text was updated successfully, but these errors were encountered: