You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Occasionally (not always) when I run the code I get this error message; I've noticed when I view myturn.gov that sometimes I get token errors or other unexpected responses, perhaps that's what's throwing?
(node:21415) UnhandledPromiseRejectionWarning: Error: Protocol error (Target.closeTarget): Tar get closed. at /Users/beltzner/myturn/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:71 :63 at new Promise (<anonymous>) at Connection.send (/Users/beltzner/myturn/node_modules/puppeteer/lib/cjs/puppeteer/common /Connection.js:70:16) at Page.close (/Users/beltzner/myturn/node_modules/puppeteer/lib/cjs/puppeteer/common/Page .js:1204:44) at checkForEach (/Users/beltzner/myturn/index.js:119:8) at async actionFunc (/Users/beltzner/myturn/index.js:137:7) at async /Users/beltzner/myturn/index.js:155:3 (Use node --trace-warnings ...to show where the warning was created) (node:21415) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error origina ted either by throwing inside of an async function without a catch block, or by rejecting a pr omise 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.ht ml#cli_unhandled_rejections_mode). (rejection id: 1) (node:21415) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non -zero exit code.
The text was updated successfully, but these errors were encountered:
Occasionally (not always) when I run the code I get this error message; I've noticed when I view myturn.gov that sometimes I get token errors or other unexpected responses, perhaps that's what's throwing?
(node:21415) UnhandledPromiseRejectionWarning: Error: Protocol error (Target.closeTarget): Tar get closed. at /Users/beltzner/myturn/node_modules/puppeteer/lib/cjs/puppeteer/common/Connection.js:71 :63 at new Promise (<anonymous>) at Connection.send (/Users/beltzner/myturn/node_modules/puppeteer/lib/cjs/puppeteer/common /Connection.js:70:16) at Page.close (/Users/beltzner/myturn/node_modules/puppeteer/lib/cjs/puppeteer/common/Page .js:1204:44) at checkForEach (/Users/beltzner/myturn/index.js:119:8) at async actionFunc (/Users/beltzner/myturn/index.js:137:7) at async /Users/beltzner/myturn/index.js:155:3 (Use
node --trace-warnings ...to show where the warning was created) (node:21415) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error origina ted either by throwing inside of an async function without a catch block, or by rejecting a pr omise 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.ht ml#cli_unhandled_rejections_mode). (rejection id: 1) (node:21415) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non -zero exit code.
The text was updated successfully, but these errors were encountered: