Diego Escobedo
Diego Escobedo
Currently, we're inconsistent with our use of backslaches, which has caused some pain when we go to the wrong address and get unexpected behavior. Some goals: 1. going to ...endpoint...
Eventually, event ingestion is going to be the bottleneck of our system. We are going to need some sort of event streaming database, a way of asynchronously processing requests, maybe...
This: https://flower.readthedocs.io/en/latest/
something along these lines: https://medium.com/@ryangordon210/build-a-python-ci-cd-system-code-quality-with-pylint-f6dea78461c6
Currently, we have all the queries that power our metric aggregation stored in `backend/metering_billing/aggregation`. Though they are functionally working, there are some things worth considering and possibly fixing: 1. We...
That's awesome! I'll take note of this perhaps a good idea to add to the developer section in case people want a bit of an easier workflow than doing it...
Currently working on https://github.com/uselotus/lotus/pull/639, which adds tests for `invoice.paid` and `invoice.past_due`. Necessary to write some more tests for the other ones we have so far using the same patching scheme.
Currently have tags for plans, but would be good to have them for customers too.