regression: restore reactive ConnectionStatusBar updates during reconnection

[ggazzo]

Summary

• ServerProvider now drives its status snapshot off Meteor.status's Tracker reactivity (via meteorBackedSdk.onMeteorStatusChange) instead of Meteor.connection._stream reset/disconnect events. Stream events only fire when the socket itself reconnects or drops, so internal connecting↔waiting cycles and per-second retryTime ticks were silently dropped — ConnectionStatusBar stayed pinned on a stale status (or never appeared) while a reconnection ran.
• subscribeStatus recomputes the snapshot immediately after wiring the bridge so the value useSyncExternalStore returns on first mount can't stay stuck on whatever cachedStatus was at module load, closing the race when the socket connected before <ServerProvider> mounted.

Regression from #40482.

Test plan

• Boot the app with DevTools open, throttle network or hit the WS endpoint with a temporary block, and observe ConnectionStatusBar cycling through connecting → waiting → connecting with the countdown ticking down each second instead of freezing.
• Pause the WS server, let the bar reach waiting, resume the server, and confirm the bar disappears as soon as Meteor's status flips back to connected (no manual page refresh needed).
• Hard reload while the dev server is offline: bar should render with the current status on mount instead of staying on whatever was captured at module evaluation.
• Re-run with SDK_TRANSPORT_ENABLED=true to confirm the SDK-transport branch still behaves the same.

https://rocketchat.atlassian.net/browse/CORE-2203

Summary by CodeRabbit

• Bug Fixes
  • Improved connection status synchronization to prevent stale status data on initialization, ensuring accurate server connectivity information is displayed immediately when the app loads.

[dionisio-bot]

Looks like this PR is not ready to merge, because of the following issues:

• This PR is missing the 'stat: QA assured' label

Please fix the issues and try again

If you have any trouble, please check the PR guidelines

[changeset-bot]

⚠️ No Changeset found

Latest commit: 118ac14

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

Meteor connection status bridging is refactored from direct stream event listening to reactive Tracker.autorun on Meteor.status() updates. The initial snapshot race where cached status could be stale is closed by synchronously recalculating and updating status when listeners subscribe.

Changes

Connection Status Bridging Race Fix

Layer / File(s)	Summary
Meteor status bridge via Tracker reactivity apps/meteor/client/lib/sdk/meteorBackedSdk.ts	onMeteorStatusChange is refactored to use Tracker.autorun driven by Meteor.status() reactivity instead of listening to Meteor.connection._stream lifecycle events. Adds Tracker import, environment guards for missing Meteor.status/Tracker.autorun, a firstRun skip to prevent immediate callback firing, try/catch wrapping, and cleanup via computation.stop().
Initial status snapshot synchronization apps/meteor/client/providers/ServerProvider.tsx	subscribeStatus now synchronously computes the latest connection status when a listener subscribes, updates the cached status if it differs, and immediately invokes the listener to close the race window and ensure correct initial useSyncExternalStore snapshot.

Possibly related PRs

• RocketChat/Rocket.Chat#40446: Modifies ServerProvider.tsx connection-status caching logic to adjust useSyncExternalStore snapshot updates.
• RocketChat/Rocket.Chat#40445: Modifies meteorBackedSdk.ts onMeteorStatusChange with alternative connection-status bridging approach.

Suggested labels

type: bug

Suggested reviewers

• tassoevan

---

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'regression: restore reactive ConnectionStatusBar updates during reconnection' accurately summarizes the main change: restoring reactive status updates for the ConnectionStatusBar during reconnection by switching from stream-based to Tracker-based reactivity.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 2 files

_{Re-trigger cubic}

[codecov]

Codecov Report

❌ Patch coverage is 66.66667% with 5 lines in your changes missing coverage. Please review.
✅ Project coverage is 69.67%. Comparing base (a44b12e) to head (118ac14).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop   #40616      +/-   ##
===========================================
+ Coverage    69.63%   69.67%   +0.03%     
===========================================
  Files         3323     3323              
  Lines       122762   122752      -10     
  Branches     21898    21899       +1     
===========================================
+ Hits         85481    85522      +41     
+ Misses       33915    33881      -34     
+ Partials      3366     3349      -17     

Flag	Coverage Δ
e2e	59.30% <66.66%> (+0.10%)	⬆️
e2e-api	47.05% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.