Skip to content
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

Merged
merged 4 commits into from
Mar 24, 2024

Conversation

dblythy
Copy link
Member

@dblythy dblythy commented Jun 11, 2023

Pull Request

Issue

Rate Limit with redisURL can fail if client is already opened.

Closes: #8631

Approach

Tasks

  • Add tests
  • Add changes to documentation (guides, repository pages, code comments)
  • Add security check
  • Add new Parse Error codes to Parse JS SDK

@parse-github-assistant
Copy link

I will reformat the title to use the proper commit message syntax.

@parse-github-assistant parse-github-assistant bot changed the title fix: rate limit with redisStore connecting if already opened fix: Rate limit with redisStore connecting if already opened Jun 11, 2023
@parse-github-assistant
Copy link

Thanks for opening this pull request!

@codecov
Copy link

codecov bot commented Jun 11, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 94.14%. Comparing base (b07ec15) to head (0577d9d).
Report is 1 commits behind head on alpha.

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.
📢 Have feedback on the report? Share it here.

@dblythy
Copy link
Member Author

dblythy commented Jun 11, 2023

Testing in production to confirm this PR fixes the issue

@dblythy dblythy requested a review from a team June 25, 2023 10:43
@mtrezza
Copy link
Member

mtrezza commented Jul 10, 2023

What's the verdict after testing this out in production?

@mtrezza mtrezza changed the title fix: Rate limit with redisStore connecting if already opened fix: Rate limiting can fail when using Parse Server option rateLimit.redisUrl with clusters Mar 24, 2024
@mtrezza mtrezza merged commit c277739 into parse-community:alpha Mar 24, 2024
22 of 26 checks passed
parseplatformorg pushed a commit that referenced this pull request Mar 24, 2024
# [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))
@parseplatformorg
Copy link
Contributor

🎉 This change has been released in version 7.1.0-alpha.3

@parseplatformorg parseplatformorg added the state:released-alpha Released as alpha version label Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
state:released-alpha Released as alpha version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Rate Limit with redisURL can fail if socket is already opened
3 participants