Skip to content

feat(realtime): subscribe retry improvements #747

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

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

grdsdev
Copy link
Collaborator

@grdsdev grdsdev commented Jul 14, 2025

What kind of change does this PR introduce?

#742

What is the current behavior?

Please link any relevant issues here.

What is the new behavior?

Feel free to include screenshots if it includes visual changes.

Additional context

Add any other context or screenshots.

@coveralls
Copy link

coveralls commented Jul 14, 2025

Pull Request Test Coverage Report for Build 16275932755

Details

  • 99 of 105 (94.29%) changed or added relevant lines in 3 files are covered.
  • 3 unchanged lines in 1 file lost coverage.
  • Overall coverage increased (+0.3%) to 76.944%

Changes Missing Coverage Covered Lines Changed/Added Lines %
Sources/Realtime/RealtimeChannelV2.swift 95 101 94.06%
Files with Coverage Reduction New Missed Lines %
Sources/Realtime/RealtimeChannelV2.swift 3 68.18%
Totals Coverage Status
Change from base Build 16215796628: 0.3%
Covered Lines: 5393
Relevant Lines: 7009

💛 - Coveralls

grdsdev added 3 commits July 14, 2025 12:49
- Add missing return statement in subscribeWithError() to prevent infinite retries
- Add heartbeat response handling in testBehavior test
- Fix test expectations for retry attempts
- Ensure proper cleanup on subscription failure

This fixes the issue where successful subscriptions would continue retrying
and tests would fail due to incorrect retry attempt counting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants