fix(reliability): add error logging to 25+ silent catch blocks across the codebase#887
fix(reliability): add error logging to 25+ silent catch blocks across the codebase#887Siddh2024 wants to merge 1 commit into
Conversation
…base
Replaces every empty catch {} and .catch(() => {}) with
meaningful console.debug or console.warn calls that include
the error context and a [LateMeet] prefix.
Affected files:
- background.ts: 14 catch blocks (state broadcast, usage tracking,
offscreen communication, session management)
- offscreen.ts: 4 catch blocks (relay, waveform, track-end notifications)
- content.ts: 3 catch blocks (participant polling, active speaker,
session save on unload)
- popup.ts: 2 catch blocks (microphone permission, initial state)
- dashboard.ts: 3 catch blocks (hostname parsing, microphone, clipboard)
- meetingTabs.ts: 2 catch blocks (URL parsing, tab resolution)
- popupCapture.ts: 1 catch block (microphone permission)
- dashboardCapture.ts: 1 catch block (microphone permission)
This makes production debugging possible by surfacing errors
that were previously invisible.
🚀 Thank You for Contributing to Late-MeetPlease ensure that:
Thank you for contributing 💙 |
github-actions
Bot
added
gssoc
|
👋 Thank you @Siddh2024 for your contribution to Late-Meet!
Please review any automated suggestions or code review comments that may appear below! We will review your PR as soon as possible! Please consider starring the repository ⭐ to show your support! |
|
Warning Review limit reached
Next review available in: 34 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (8)
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. Comment |
|
1 participant
Reliability fix: Add error logging to 25+ silent catch blocks across the codebase (#877)
Problem:
Over 25 locations across the codebase had empty catch blocks or .catch(() => {}) patterns that silently swallowed errors, making production debugging impossible. Critical failures in audio capture, message passing, state synchronization, and storage operations were invisible.
Changes by file:
src/background.ts (14 fixes):
src/offscreen.ts (4 fixes):
src/content.ts (3 fixes):
src/popup.ts (2 fixes):
src/dashboard.ts (3 fixes):
src/meetingTabs.ts (2 fixes):
src/popupCapture.ts (1 fix):
src/dashboardCapture.ts (1 fix):
Benefits: