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

run Gratipay 136 #3088

Closed
seanlinsley opened this issue Jan 8, 2015 · 48 comments
Closed

run Gratipay 136 #3088

seanlinsley opened this issue Jan 8, 2015 · 48 comments

Comments

@seanlinsley
Copy link
Contributor

135

@clone1018
Copy link
Contributor

You can't click the first balanced link, only the second.

@seanlinsley
Copy link
Contributor Author

We really need to be recording people's legal names, even if we don't publicly display them.

@seanlinsley
Copy link
Contributor Author

There are a number of elsewhere accounts on the review dashboard that 404 when you click on them.

@seanlinsley
Copy link
Contributor Author

From the documentation it's not clear what we should be looking for when reviewing new accounts.

@seanlinsley
Copy link
Contributor Author

There are also G+ people in the review list that 404; #2965

@chadwhitacre
Copy link
Contributor

IRC

@rohitpaulk
Copy link
Contributor

You can't click the first balanced link, only the second.

Look like there's an extra / in the URL. For example, https://dashboard.balancedpayments.com/#//customers/CU70YXZ7dP8kr6GhQ0cZxlRl

@rohitpaulk
Copy link
Contributor

@clone1018 - Can you confirm that https://dashboard.balancedpayments.com/#/customers/CU70YXZ7dP8kr6GhQ0cZxlRl works? If so, I'll send in a PR to fix the extra /.

@seanlinsley
Copy link
Contributor Author

Apparently people get on the review list for connecting account. For example we have some people who've been on for a year, but just connected a bank account. The review page should list the reason they're on the list to begin with.

@chadwhitacre
Copy link
Contributor

@rohitpaulk We have a ticket about that. I think it's a bit more complicated because Balanced switched URL formats at some point, and we have instances of both (something like that). I'd search for the ticket but I'm dead. :-)

@rohitpaulk
Copy link
Contributor

SELECT COUNT(*) FROM participants WHERE balanced_customer_href NOT LIKE '/%'; gave me 0.

Did the old URL format have two /s in it?

@rohitpaulk
Copy link
Contributor

I can answer that myself. According to #2085, no it didn't.

@clone1018
Copy link
Contributor

I feel like we should also include people on this list who have recently started giving a multiple of x to someone.

@seanlinsley
Copy link
Contributor Author

We should be using something like S3 to store backups.

@clone1018
Copy link
Contributor

58 (6 left) accounts reviewed.

@clone1018
Copy link
Contributor

Backup taken and verified.

@clone1018
Copy link
Contributor

So the digitalocean droplet had a user named whit537 that you should use, this isn't documented.

Remote login for user root is disabled on the droplet.

Password reset based authentication works for the remote console in DigialOcean.

@clone1018
Copy link
Contributor

Droplet spun up and updated.

@clone1018
Copy link
Contributor

pid-2114 thread-140040540878592 (MainThread) Traceback (most recent call last):
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/gratipay/cli.py", line 28, in payday
pid-2114 thread-140040540878592 (MainThread)     Payday.start().run()
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/gratipay/billing/payday.py", line 133, in run
pid-2114 thread-140040540878592 (MainThread)     self.payin()
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/gratipay/billing/payday.py", line 157, in payin
pid-2114 thread-140040540878592 (MainThread)     holds = self.create_card_holds(cursor)
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/gratipay/billing/payday.py", line 427, in create_card_holds
pid-2114 thread-140040540878592 (MainThread)     holds = self.fetch_card_holds(participant_ids)
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/gratipay/billing/payday.py", line 407, in fetch_card_holds
pid-2114 thread-140040540878592 (MainThread)     cancel_card_hold(hold)
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/gratipay/billing/exchanges.py", line 236, in cancel_card_hold
pid-2114 thread-140040540878592 (MainThread)     hold.save()
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/env/lib/python2.7/site-packages/balanced/resources.py", line 177, in save
pid-2114 thread-140040540878592 (MainThread)     resp = method(href, data=attrs)
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/env/lib/python2.7/site-packages/wac.py", line 460, in put
pid-2114 thread-140040540878592 (MainThread)     return self._op(self.interface.put, uri, data=data, **kwargs)
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/env/lib/python2.7/site-packages/wac.py", line 512, in _op
pid-2114 thread-140040540878592 (MainThread)     handle_error(ex)
pid-2114 thread-140040540878592 (MainThread)   File "/home/whit537/gratipay.com/env/lib/python2.7/site-packages/wac.py", line 489, in handle_error
pid-2114 thread-140040540878592 (MainThread)     raise ex
pid-2114 thread-140040540878592 (MainThread) HTTPError: HTTPError(status='Conflict', category_code='cannot-void-authorization', additional=None, status_code=409, category_type='logical', extras={}, request_id='REDACTED', response=None, description='Hold already captured or voided. Your request id is REDACTED.')

@Changaco
Copy link
Contributor

Changaco commented Jan 8, 2015

That's a similar problem to last week, we didn't actually commit a fix on master.

@Changaco
Copy link
Contributor

Changaco commented Jan 8, 2015

Actually, maybe it's not the same problem.

@clone1018
Copy link
Contributor

Script ran for 15 minutes (0:15:41.935254).

@clone1018
Copy link
Contributor

Logs downloaded and uploaded is not documented.

@clone1018
Copy link
Contributor

Can't do masspay, need access credentials for Paypal

@clone1018
Copy link
Contributor

Can't login to twitter to pin twitter.

@clone1018
Copy link
Contributor

Logs downloaded and uploaded. Droplet destroyed.

@chadwhitacre
Copy link
Contributor

MassPay done and posted back for 79 users. Log downloaded and uploaded.

@chadwhitacre
Copy link
Contributor

Tweet pinned: https://twitter.com/Gratipay/status/553248050957664257.

Week 136—2924 users exchanged $10,581.80: https://gratipay.com/about/stats

Minor issues, I would've done:

Week 136—2,924 users exchanged $10,582: https://gratipay.com/about/stats.
  • comma in nusers
  • no cents
  • period at the end

@chadwhitacre
Copy link
Contributor

Escrow shuffled.

@chadwhitacre
Copy link
Contributor

@chadwhitacre
Copy link
Contributor

Hey @patcon I got hit by a bus this morning. ;-)

@chadwhitacre
Copy link
Contributor

Should've marked ★★★ when opened.

@chadwhitacre
Copy link
Contributor

Actually, reopening until we post-mortem and reticket.

@chadwhitacre chadwhitacre reopened this Jan 8, 2015
@patcon
Copy link
Contributor

patcon commented Jan 8, 2015

First reaction: oh god no.

Upon further reading: HOORAAAAAYYYYY!!

Go team!

@clone1018
Copy link
Contributor

@whit537 We should automate it if you want it so specific. :)

@chadwhitacre
Copy link
Contributor

I've set up multi-user access for @clone1018 at PayPal. Doesn't appear that we can use 2fa with that, however. :-/

@chadwhitacre
Copy link
Contributor

From the documentation it's not clear what we should be looking for when reviewing new accounts.

I added a new doc on this:

http://inside.gratipay.com/howto/review-accounts

@chadwhitacre
Copy link
Contributor

The review page should list the reason they're on the list to begin with.

@seanlinsley The reason is the same for everyone right now:

  • they are unreviewed (is_suspicious is null), and
  • they have a Balanced account attached (balanced_customer_href is not null).

See the dashboard source.

@chadwhitacre
Copy link
Contributor

We should be using something like S3 to store backups.

@seanlinsley We have some backups at Heroku and I store backups offsite. Do think we need a third layer?

@chadwhitacre
Copy link
Contributor

We should automate it if you want it so specific.

Begun in #3097.

Can't login to twitter to pin twitter.

Not possible from the API. :-(

https://twittercommunity.com/t/pin-a-tweet-with-the-twitter-api/13048

@chadwhitacre
Copy link
Contributor

We really need to be recording people's legal names, even if we don't publicly display them.

Reticketed as #3098.

@chadwhitacre
Copy link
Contributor

I feel like we should also include people on this list who have recently started giving a multiple of x to someone.

Reticketed as #3099

@chadwhitacre
Copy link
Contributor

So the digitalocean droplet had a user named whit537 that you should use, this isn't documented.

Remote login for user root is disabled on the droplet.

Password reset based authentication works for the remote console in DigialOcean.

@clone1018 Is there an action item here? Please reticket if so.

@chadwhitacre
Copy link
Contributor

Logs downloaded and uploaded is not documented.

Doc reviewed in gratipay/inside.gratipay.com@bcff70a.

http://inside.gratipay.com/howto/run-payday

@chadwhitacre
Copy link
Contributor

Pretty sure that's everything. Great work @clone1018, et al.! 💃

@patcon
Copy link
Contributor

patcon commented Jan 10, 2015

fwiw, this whole thread is a case-study in being awesome.

@seanlinsley
Copy link
Contributor Author

We should be using something like S3 to store backups.

@seanlinsley We have some backups at Heroku and I store backups offsite. Do think we need a third layer?

What @clone1018 and I had discussed was an append-only S3 bucket where database backups and payday logs could be pushed, preferably automatically.

@chadwhitacre
Copy link
Contributor

@seanlinsley Okay, I'll let you make a ticket. :-)

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

6 participants