-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Check supabase if user quota data is not in redis #10
Comments
pls correct me if i'm wrong. in number 3, should it be "create" instead of "check"? @nang-dev |
yes. do you mind taking this up? @quangcito |
On it! @nang-dev |
legendary |
@nang-dev sr for the delay, ig i'll wait until fast-api refactoring completes. lmk if you guys need help with those unit tests or smth. |
@quangcito fast api wont affect this - you can proceed! |
@nang-dev awesome, gotcha!! |
how is this, quang? |
@nang-dev actively working on it rn 🥲! |
@nang-dev [BLOCKER] can I have access to Supabase dev account to look at the schema and setup the quota table if needed? |
@nang-dev any update on my access request? |
HOLY my bad. been busy with the move. DM'd! |
https://github.com/trypear/pearai-server/blob/8733caae595124959cf8ec34b301fb6b0ae5f2ba/api/app/services/quota_service.py#L15
current logic:
the logic should be
This is not that pressing atm as our redis cache is big enough for every user but should be done at some point for sure
The text was updated successfully, but these errors were encountered: