-
Notifications
You must be signed in to change notification settings - Fork 308
Conversation
I've printed out payday.py and started combing through it. The reason why #3399 (comment) doesn't result in escrow or complicated graph settling is that it ... doesn't do complicated graph settling: b can't feed their $1 back into the system. I think we should run with that, so that we can move towards #1383 with this. |
I believe since we're not cycling the graph multiple times per payday, we don't need to use the |
Basically, the work here is to implement the prototype I wrote in Python, in the SQL inside |
I'm starting with the |
There is some interaction between |
On the one hand it seems like we should avoid tackling the arrears issue (#3378) on this PR. On the other hand ... |
Okay! I believe with that last commit we've gotten rid of the feedback. 🎤 😵 screeeeeeeeeeeeee Now to introduce teams ... |
P.S. We still make payments from preexisting balances, which means we can avoid tackling #3378 here. Phew. |
We're simplifying payday to only iterate once.
taken from bea8481
To go with subscriptions
This is a temporary table for keeping track of teams during payday.
Wow. Caching is a 🐰-hole. I'm going to stub it out for now. We'll migrate caching of |
The test suite uses this extensively. I want to modify payday tests so I really need this.
I'm also going to not worry about the payroll side this week. Gratipay is the only one of the half-dozen or so teams we're aiming to run with today that uses payroll. We'll just let the full amount clear to our bank account this week. Sorry, Gratipay team. :-/ |
Next up is implementing process_draws (for owners), then, probalby later on, process_takes.
I believe that's it for this PR. |
Alright, Travis is green. ✅ Here we go! Nothing ventured, nothing gained! |
👯 |
Part of #3399.