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

run Gittip 93 #2134

Closed
chadwhitacre opened this issue Mar 13, 2014 · 21 comments
Closed

run Gittip 93 #2134

chadwhitacre opened this issue Mar 13, 2014 · 21 comments

Comments

@chadwhitacre
Copy link
Contributor

92

@chadwhitacre
Copy link
Contributor Author

Don't neglect #777!

@chadwhitacre
Copy link
Contributor Author

Reviewed 36 accounts. Left two as unreviewed because I'm nervous after #2125 last week and these two aren't giving anything. Reticketed #2135.

@chadwhitacre
Copy link
Contributor Author

Backup started ...

@chadwhitacre
Copy link
Contributor Author

I manually disconnected @rachelwalexander's bank account by setting last_ach_result to NULL and removing her bank account in the Balanced Dashboard. That's what happens when a user disconnects a bank account themselves: the bank-account.json endpoint calls gittip.billing.clear. I would have rather not removed the bank account at Balanced, but ach_credit in payday doesn't give me any less drastic hooks.

@chadwhitacre
Copy link
Contributor Author

Droplet spun up and accessed. Updating ...

@chadwhitacre
Copy link
Contributor Author

Backup finished and verified.

@chadwhitacre
Copy link
Contributor Author

Script started.

@chadwhitacre
Copy link
Contributor Author

Script ran for {age} (3:04:47.713286).

@chadwhitacre
Copy link
Contributor Author

Log downloaded.

@chadwhitacre
Copy link
Contributor Author

Tweet tweeted on Twitter.

@chadwhitacre
Copy link
Contributor Author

We only had two more active users than last week. Did we have another rash of CC failures?

@chadwhitacre
Copy link
Contributor Author

Hmmm ... not more than usual:

$ grep "Charging.*failed" gittip-90.log|wc -l
     326
$ grep "Charging.*failed" gittip-91.log|wc -l
     335
$ grep "Charging.*failed" gittip-92.log|wc -l
     357
$ grep "Charging.*failed" gittip-93.log|wc -l
     370
$

Just a slow week, I guess?

@chadwhitacre
Copy link
Contributor Author

Droplet destroyed.

@chadwhitacre
Copy link
Contributor Author

Running MassPay from #2099 branch.

@chadwhitacre
Copy link
Contributor Author

Eep! The transfer from New Alliance to PayPal happened twice last week! D:

@chadwhitacre
Copy link
Contributor Author

I'm going to run MassPay as usual and then deal with the shuffling.

@chadwhitacre
Copy link
Contributor Author

Double-checked @rachelwalexander's account. Looks like we avoided sending all her money back to her. :-)

@chadwhitacre
Copy link
Contributor Author

I moved money from Balanced to New Alliance, and from PayPal back to New Alliance (per our new policy). Once those clear we can move money from New Alliance to Ally.

@chadwhitacre
Copy link
Contributor Author

Aaaaaaaand I think that does it?

@chadwhitacre
Copy link
Contributor Author

MassPay posted back to Gittip.

@chadwhitacre
Copy link
Contributor Author

MassPay logs stored.

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