fix: resolve silent crashes and add user-friendly error handling for crashes#66
Open
simrannsv wants to merge 1 commit into
Open
fix: resolve silent crashes and add user-friendly error handling for crashes#66simrannsv wants to merge 1 commit into
simrannsv wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
This PR addresses the issue where the terminal application crashes silently or dumps raw unhandled background rejections when the WhatsApp Web connection drops or fails to initialize (e.g., when a user is offline or a session times out).
Key Adjustments:
start()insrc/bot.tsto anasyncmethod usingawaitinside a robusttry/catchblock to intercept internal Puppeteer/browser navigation walls.unhandledRejectionanduncaughtException) at the root of the file to capture deep background leaks from node_modules.chalklogging alerts (Red✕for fatal errors, Yellow⚠️for warnings) providing explicit, actionable instructions on how to recover.process.exit()fires only after terminal logs have finished writing completely.Related Issue Number
Fixes #43
Type of Change
How Was This Tested?
Tested locally under specific failure states:
npm run dev. Verified that the bot interceptedPage.navigate timed out, rendered the clear troubleshooting instructions, and exited cleanly.disconnectedlistener handled the heart-beat drop smoothly, printing recovery paths rather than cascading into an infinite loop or silent termination.Checklist
npm run build).npm test).