run Gratipay 232 #888

Closed
gratipay-bot opened this Issue Nov 10, 2016 · 20 comments

Comments

Projects
None yet
6 participants
@gratipay-bot

gratipay-bot commented Nov 10, 2016

← Payday 231


Docs

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

Checklist
Rotation
Month Pilot Copilot
November @clone1018 ✈️ @rohitpaulk
December @whit537 @clone1018
January @rohitpaulk @whit537
February @clone1018 @rohitpaulk
March @whit537 @clone1018
April @rohitpaulk @whit537
May @clone1018 @rohitpaulk
June @whit537 @clone1018
July @rohitpaulk @whit537
August @clone1018 @rohitpaulk
September @whit537 @clone1018
October @rohitpaulk @whit537
@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor

Let's go!

Contributor

clone1018 commented Nov 10, 2016

Let's go!

@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor

Reviewed accounts!

Contributor

clone1018 commented Nov 10, 2016

Reviewed accounts!

@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor
$ cat migrate-tips.log
Done.
Contributor

clone1018 commented Nov 10, 2016

$ cat migrate-tips.log
Done.
@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor

Backups are taking an extra amount of time, doing extra verification. I took two also

Contributor

clone1018 commented Nov 10, 2016

Backups are taking an extra amount of time, doing extra verification. I took two also

@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor
    schema_name     |                       relname                        |    size    | table_size
--------------------+------------------------------------------------------+------------+------------
 public             | packages                                             | 300 MB     |  314294272
 public             | elsewhere                                            | 87 MB      |   91258880
 public             | transfers                                            | 40 MB      |   42016768
 public             | events                                               | 27 MB      |   28278784
 public             | participants                                         | 26 MB      |   26853376
 public             | transfers_tippee_idx                                 | 14 MB      |   14745600
 public             | transfers_tipper_idx                                 | 14 MB      |   14655488
 public             | packages_package_manager_name_key                    | 13 MB      |   13393920

Well that makes sense!

Backup taken and verified.

Contributor

clone1018 commented Nov 10, 2016

    schema_name     |                       relname                        |    size    | table_size
--------------------+------------------------------------------------------+------------+------------
 public             | packages                                             | 300 MB     |  314294272
 public             | elsewhere                                            | 87 MB      |   91258880
 public             | transfers                                            | 40 MB      |   42016768
 public             | events                                               | 27 MB      |   28278784
 public             | participants                                         | 26 MB      |   26853376
 public             | transfers_tippee_idx                                 | 14 MB      |   14745600
 public             | transfers_tipper_idx                                 | 14 MB      |   14655488
 public             | packages_package_manager_name_key                    | 13 MB      |   13393920

Well that makes sense!

Backup taken and verified.

@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor
Script ran for 53 seconds (0:00:53.959495).
Contributor

clone1018 commented Nov 10, 2016

Script ran for 53 seconds (0:00:53.959495).
@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor

Fees match!

Contributor

clone1018 commented Nov 10, 2016

Fees match!

@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor

POSTed MassPay back to Gratipay for 92 users.

!!! ~30 more masspay users?

Contributor

clone1018 commented Nov 10, 2016

POSTed MassPay back to Gratipay for 92 users.

!!! ~30 more masspay users?

@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor

Escrow Shuffle

$
MassPay 1,853.15
5x 9,265.75
Balance 8,940.67
Added 1,000.00
Contributor

clone1018 commented Nov 10, 2016

Escrow Shuffle

$
MassPay 1,853.15
5x 9,265.75
Balance 8,940.67
Added 1,000.00
@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor

image

10% decline rate

Contributor

clone1018 commented Nov 10, 2016

image

10% decline rate

@clone1018

This comment has been minimized.

Show comment
Hide comment
Contributor

clone1018 commented Nov 10, 2016

@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor

Done!

Contributor

clone1018 commented Nov 10, 2016

Done!

@clone1018 clone1018 closed this Nov 10, 2016

@clone1018

This comment has been minimized.

Show comment
Hide comment
@clone1018

clone1018 Nov 10, 2016

Contributor
Hello Luke,

Just thought you'd like to know Gratipay sent you $0.54 USD.

Neat.

Contributor

clone1018 commented Nov 10, 2016

Hello Luke,

Just thought you'd like to know Gratipay sent you $0.54 USD.

Neat.

@mattbk

This comment has been minimized.

Show comment
Hide comment
@mattbk

mattbk Nov 10, 2016

Contributor

Do we still try to re-run credit cards that fail, or does it wait until next week? Just got this on Freshdesk in response to the failed charge email:

I'm fix my credit card. Now you can charge it.

Contributor

mattbk commented Nov 10, 2016

Do we still try to re-run credit cards that fail, or does it wait until next week? Just got this on Freshdesk in response to the failed charge email:

I'm fix my credit card. Now you can charge it.

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Nov 10, 2016

Contributor

We wait until next week. My card failed last week and this week it looks like I got charged for both last week and this. This confused me a little because I thought we changed it to avoid accumulating for months when a card fails (to avoid unpleasant surprises) but maybe if it's only one week then we do double the charge?

Contributor

chadwhitacre commented Nov 10, 2016

We wait until next week. My card failed last week and this week it looks like I got charged for both last week and this. This confused me a little because I thought we changed it to avoid accumulating for months when a card fails (to avoid unpleasant surprises) but maybe if it's only one week then we do double the charge?

@rohitpaulk

This comment has been minimized.

Show comment
Hide comment
@rohitpaulk

rohitpaulk Nov 13, 2016

Contributor

but maybe if it's only one week then we do double the charge?

Yep, that is the current behaviour. We only exclude cards that are marked as failed - So in the first payday, your card was included because it was not marked as failed yet (was going to fail later in the payday script), and in the second payday it was included because it you'd fixed it. :)

Contributor

rohitpaulk commented Nov 13, 2016

but maybe if it's only one week then we do double the charge?

Yep, that is the current behaviour. We only exclude cards that are marked as failed - So in the first payday, your card was included because it was not marked as failed yet (was going to fail later in the payday script), and in the second payday it was included because it you'd fixed it. :)

@chadwhitacre

This comment has been minimized.

Show comment
Hide comment
@chadwhitacre

chadwhitacre Nov 14, 2016

Contributor

So if I had taken an extra week to fix it then I still would've been charged the same amount?

  • week n — card fails — $20 due
  • week n+1 — card still failing — $20 due
  • week n+2 — card fixed — $40 due

Like that?

Contributor

chadwhitacre commented Nov 14, 2016

So if I had taken an extra week to fix it then I still would've been charged the same amount?

  • week n — card fails — $20 due
  • week n+1 — card still failing — $20 due
  • week n+2 — card fixed — $40 due

Like that?

@rohitpaulk

This comment has been minimized.

Show comment
Hide comment
@rohitpaulk

rohitpaulk Nov 14, 2016

Contributor

Yes, correct. To make it clear, if there was another week in the middle:

  • week n — card fails — $20 due
  • week n+1 — card still failing, no extra dues added — $20 due
  • week n+2 — card still failing, no extra dues added - $20 due
  • week n+3 — card fixed — $40 ($20 due from payday n, and $20 from payday n+3) charged
Contributor

rohitpaulk commented Nov 14, 2016

Yes, correct. To make it clear, if there was another week in the middle:

  • week n — card fails — $20 due
  • week n+1 — card still failing, no extra dues added — $20 due
  • week n+2 — card still failing, no extra dues added - $20 due
  • week n+3 — card fixed — $40 ($20 due from payday n, and $20 from payday n+3) charged
@rohitpaulk

This comment has been minimized.

Show comment
Hide comment
@rohitpaulk

rohitpaulk Nov 14, 2016

Contributor

I think that is sensible - do you think this should be changed?

Reasons I think this works well:

  • Works well for a (normal/usual?) giver who fixes their CC on time (within the first week) - Their tips will be processed as if the hiccup never happened.
  • Safeguards against nasty surprises when a giver forgets about Gratipay and ends up fixing their credit card after a long time

We could move the dial towards one side more than the other, but that'd be at the cost of one of the above scenarios - unless we present an option to the user and let them choose.

Contributor

rohitpaulk commented Nov 14, 2016

I think that is sensible - do you think this should be changed?

Reasons I think this works well:

  • Works well for a (normal/usual?) giver who fixes their CC on time (within the first week) - Their tips will be processed as if the hiccup never happened.
  • Safeguards against nasty surprises when a giver forgets about Gratipay and ends up fixing their credit card after a long time

We could move the dial towards one side more than the other, but that'd be at the cost of one of the above scenarios - unless we present an option to the user and let them choose.

@JessaWitzel

This comment has been minimized.

Show comment
Hide comment
@JessaWitzel

JessaWitzel Nov 14, 2016

Contributor

I think that the logic fits. I assume we send a notification when a card has failed. Can we edit the copy so that it describes this behavior? ie "Hi friend! Please update your credit card information so that we can process your tips. We only process payroll once each week but if you update your information before the next processing you will see a charge for both week's tips at the same time. We will never try to process more than two weeks tips so if it takes you a little longer, no worries."

Contributor

JessaWitzel commented Nov 14, 2016

I think that the logic fits. I assume we send a notification when a card has failed. Can we edit the copy so that it describes this behavior? ie "Hi friend! Please update your credit card information so that we can process your tips. We only process payroll once each week but if you update your information before the next processing you will see a charge for both week's tips at the same time. We will never try to process more than two weeks tips so if it takes you a little longer, no worries."

@gratipay-bot gratipay-bot referenced this issue Nov 17, 2016

Closed

run Gratipay 233 #897

15 of 15 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment