Wong Zhao Wu, Bryan
Wong Zhao Wu, Bryan
Github's documentation on ["Collaborating with pull requests"](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests) seems like a good introduction. Some important ones are: - [About forks](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks) - [Fork a repo](https://docs.github.com/en/get-started/quickstart/fork-a-repo) - [Syncing a Fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork) - [Creating a...
The following are my two-cents after reading through the source code and documentations for slowapi and fastapi-limiter: ### Storage Options - slowapi: Redis (Cluster), Memcached, MongoDB, In-built Memory - fastapi-limiter:...
Sure, so there will be around ~3 PR for this issue: 1. redis-in-docker-compose 2. implement-fastapi-limiter 3. limiter-load-testing @GraemeHarris have you started any code on this? If yes, then few free...
@andreaskoepf I have completed a working prototype for the rate-limiter. There is one part that I wish to clarify which is the limits on multiple keys portion: AFAIK, the existing...
@andreaskoepf Another part is for the `OasstErrorCode`, will `TOO_MANY_REQUESTS = 429` be a suitable error code? (since that also is the HTTP error code for too many requests). ```python class...
@andreaskoepf & @GraemeHarris, backend rate limiting PoC is now completed and is up for PR. A few To-Dos that I have identified: - [ ] Identify list of endpoints that...
Hi @zaidansani , I have the same idea with you on a forum/reddit-like feature whereby students could create, edit, comment and share their module plan with others in an integrated...
@GraemeHarris do you intend to add `redis` (and `redis-insights`) to Line 7 in the `docker-compose.yml` such that both `redis` and `redis-insights` will be started up for `backend-dev` purpose? ```yaml backend-dev:...