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: add prefix check to prevent unwanted error message #4

Merged

Conversation

ankit-kumar-jat
Copy link

added prefix check on onMessage handler of ClusterMemoryStoreWorker to prevent Error: ClusterMemoryStoreWorker:1: response recieved without matching open request when using multiple instences of ClusterMemoryStoreWorker

Closes #3

added prefix check on onMessage handler of ClusterMemoryStoreWorker to prevent
Error: ClusterMemoryStoreWorker:1: response recieved without matching open request
when using multiple instences of ClusterMemoryStoreWorker

Closes express-rate-limit#3
Copy link
Member

@nfriedly nfriedly left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, that is simpler than the fix I had in mind. I think we'll go with your version. Thanks!

@nfriedly nfriedly merged commit f41cb77 into express-rate-limit:main May 29, 2024
10 checks passed
@nfriedly
Copy link
Member

Ok, it should get released to npm as v0.2.1 shortly. Thanks again!

@nfriedly
Copy link
Member

FYI, I'm also adding npm package provenance support to the release process and publishing that as v0.3.0. (I thought of it right after releasing v0.2.1 or I would have published them together.)

I just wanted to clarify that since they're coming out so close together.

@ankit-kumar-jat
Copy link
Author

Great, Thanks for your quick support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants