-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
fix: Rate limiting can fail when using Parse Server option rateLimit.redisUrl
with clusters
#8632
Conversation
I will reformat the title to use the proper commit message syntax. |
Thanks for opening this pull request! |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## alpha #8632 +/- ##
==========================================
- Coverage 94.15% 94.14% -0.01%
==========================================
Files 186 186
Lines 14688 14687 -1
==========================================
- Hits 13829 13827 -2
- Misses 859 860 +1 ☔ View full report in Codecov by Sentry. |
Testing in production to confirm this PR fixes the issue |
What's the verdict after testing this out in production? |
rateLimit.redisUrl
with clusters
# [7.1.0-alpha.3](7.1.0-alpha.2...7.1.0-alpha.3) (2024-03-24) ### Bug Fixes * Rate limiting can fail when using Parse Server option `rateLimit.redisUrl` with clusters ([#8632](#8632)) ([c277739](c277739))
🎉 This change has been released in version 7.1.0-alpha.3 |
Pull Request
Issue
Rate Limit with redisURL can fail if client is already opened.
Closes: #8631
Approach
Tasks