Skip to content

fix: Add specific error for increased message rates #1453

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

Merged
merged 3 commits into from
Aug 19, 2025

Conversation

filipecabaco
Copy link
Member

What kind of change does this PR introduce?

Add specific error for increased message rate errors but also refactored some logging approach to start simplifying that code

Copy link

vercel bot commented Jul 9, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment
Project Deployment Preview Comments Updated (UTC)
realtime-demo Ignored Ignored Preview Aug 18, 2025 6:11pm

@filipecabaco filipecabaco force-pushed the fix/message-per-second-error branch from 5c98ee0 to 9d0fb4d Compare July 9, 2025 11:59
@filipecabaco filipecabaco force-pushed the fix/message-per-second-error branch from 9d0fb4d to b7c2458 Compare August 12, 2025 22:57
@coveralls
Copy link

coveralls commented Aug 12, 2025

Coverage Status

coverage: 84.201% (-0.09%) from 84.292%
when pulling 48b7355 on fix/message-per-second-error
into 51a7533 on main.

@filipecabaco filipecabaco force-pushed the fix/message-per-second-error branch from 6bd8a66 to 7005a9c Compare August 14, 2025 11:57
@filipecabaco filipecabaco requested a review from edgurgel August 14, 2025 11:57
Add specific error for increased message rate errors
@filipecabaco filipecabaco force-pushed the fix/message-per-second-error branch from 7005a9c to f8d9308 Compare August 18, 2025 17:00
@filipecabaco filipecabaco merged commit a11fc67 into main Aug 19, 2025
6 of 9 checks passed
@filipecabaco filipecabaco deleted the fix/message-per-second-error branch August 19, 2025 15:58
@kiwicopple
Copy link
Member

🎉 This PR is included in version 2.42.4 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

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

Successfully merging this pull request may close these issues.

4 participants