fix: use console.error for permanent disconnect in useActiveUsers#13509
Conversation
When the active-users presence WebSocket exhausts retries and stops, it logged at warn — same severity as a temporary blip. This is a terminal event: presence tracking is offline and won't recover. Operators need error-level visibility. Signed-off-by: AdeshDeshmukh <adeshkd123@gmail.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
✅ Deploy Preview for kubestellarconsole ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
👋 Hey @AdeshDeshmukh — thanks for opening this PR!
This is an automated message. |
There was a problem hiding this comment.
Pull request overview
Single-line log severity bump in the active-users presence WebSocket hook: when the reconnect loop exhausts its max attempts, the message is now emitted via console.error instead of console.warn to reflect that the presence tracker is permanently offline (mirroring the same change previously made in the update-progress hook).
Changes:
- Promote permanent-disconnect log from
console.warntoconsole.errorinstartPresenceConnection.
|
@kubestellar-hive[bot]: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@kubestellar-hive[bot]: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
There was a problem hiding this comment.
LGTM — same pattern as #13508, terminal disconnect elevated to console.error. CI green.
|
@kubestellar-hive[bot]: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@kubestellar-hive[bot]: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@kubestellar-hive[bot]: changing LGTM is restricted to collaborators DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
2ce3e2b
into
kubestellar:main
|
Thanks @AdeshDeshmukh! 🎉 Same principle, same clean fix — terminal disconnect events belong at error level. Merged via squash. |
✅ Post-Merge Verification: passedCommit: |
Same as the update-progress hook — a max-retries-exceeded
disconnect means the presence tracker is permanently offline. It
was logging at warn, same level as a routine reconnection.
Bumped to console.error. Terminal events should surface as errors.