error: UnhandledPromiseRejectionWarning
See original GitHub issueGrammarly stopped working for me. It worked fine a few weeks ago. I’m getting this error on the output log:
(node:6916) UnhandledPromiseRejectionWarning: Error: Socket connection failed: NOT_AUTHORIZED
at GrammarlyClient._connect (/home/mshoegx/.vscode-server/extensions/znck.grammarly-0.14.0/dist/server/index.js:38903:19)
at GrammarlyClient._queueOrSend (/home/mshoegx/.vscode-server/extensions/znck.grammarly-0.14.0/dist/server/index.js:38978:18)
at /home/mshoegx/.vscode-server/extensions/znck.grammarly-0.14.0/dist/server/index.js:38876:18
at new Promise (<anonymous>)
at GrammarlyClient.send (/home/mshoegx/.vscode-server/extensions/znck.grammarly-0.14.0/dist/server/index.js:38874:16)
at GrammarlyClient.sendWithErrorHandling (/home/mshoegx/.vscode-server/extensions/znck.grammarly-0.14.0/dist/server/index.js:39102:31)
at GrammarlyClient.submitOT (/home/mshoegx/.vscode-server/extensions/znck.grammarly-0.14.0/dist/server/index.js:39194:21)
at TextGrammarCheckHost.sync (/home/mshoegx/.vscode-server/extensions/znck.grammarly-0.14.0/dist/server/index.js:39943:24)
at TextGrammarCheckHost.setText (/home/mshoegx/.vscode-server/extensions/znck.grammarly-0.14.0/dist/server/index.js:39886:19)
at Function.update (/home/mshoegx/.vscode-server/extensions/znck.grammarly-0.14.0/dist/server/index.js:39686:28)
(node:6916) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 3)
1637054685723 DEBUG [TextGrammarCheckHost] (66696c) Hosting file:///home/mshoegx/COMMIT_EDITMSG
Any idea what could be the problem?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Getting a UnhandledPromiseRejectionWarning when testing ...
The "Unhandled promise rejection" is also caused by the failed assertion, because if an error is thrown in a catch() handler, and there...
Read more >Fixing UnhandledPromiseRejectionWarning in Node.js
There's a little problem though. It's very easy to forget to handle Promise rejections, and this can lead to hard-to-debug issues. If we...
Read more >Unhandled Promise Rejections in Node.js - The Code Barbarian
If you want to suppress the unhandled promise rejection warning, all you need to do is call .catch() on the promise with an...
Read more >Unhandled Promise Rejection Warning - Codecademy Forums
I keep getting this error when I run my code UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by ...
Read more >Unhandledpromiserejectionwarn...
unhandledpromiserejectionwarning is an error NodeJS will throw if you fail to handle promise rejection. Learn more about the error and how you can...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@IEvangelist try use this workaround https://github.com/znck/grammarly/issues/183#issuecomment-879557150
Thanks that worked!