Improve bulk stability #6

New Issue

pendulum · 2020-08-14T13:44:34Z

pendulum commented

2020-08-14 13:44:34 +00:00

Various issues occur when scraping many scenes.

- bind message supplies 28850 parameters, but prepared statement "" requires 290994
    at Parser.parseErrorMessage (/home/blergh/staxxx/node_modules/pg-protocol/src/parser.ts:357:11)
    at Parser.handlePacket (/home/blergh/staxxx/node_modules/pg-protocol/src/parser.ts:186:21)
    at Parser.parse (/home/blergh/staxxx/node_modules/pg-protocol/src/parser.ts:101:30)
    at Socket.<anonymous> (/home/blergh/staxxx/node_modules/pg-protocol/src/index.ts:7:48)
    at Socket.emit (events.js:315:20)
    at addChunk (_stream_readable.js:295:12)
    at readableAddChunk (_stream_readable.js:271:9)
    at Socket.Readable.push (_stream_readable.js:212:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:186:23)
(node:11814) 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: 2)
(node:11814) [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

Various issues occur when scraping many scenes. ``` - bind message supplies 28850 parameters, but prepared statement "" requires 290994 at Parser.parseErrorMessage (/home/blergh/staxxx/node_modules/pg-protocol/src/parser.ts:357:11) at Parser.handlePacket (/home/blergh/staxxx/node_modules/pg-protocol/src/parser.ts:186:21) at Parser.parse (/home/blergh/staxxx/node_modules/pg-protocol/src/parser.ts:101:30) at Socket.<anonymous> (/home/blergh/staxxx/node_modules/pg-protocol/src/index.ts:7:48) at Socket.emit (events.js:315:20) at addChunk (_stream_readable.js:295:12) at readableAddChunk (_stream_readable.js:271:9) at Socket.Readable.push (_stream_readable.js:212:10) at TCP.onStreamRead (internal/stream_base_commons.js:186:23) (node:11814) 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: 2) (node:11814) [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 ```

pendulum commented

2020-08-19 19:59:09 +00:00

Partially improved with 50c5f921f5, but parameter binding error supposedly still occurs.

Partially improved with https://gitea.unknown.name/pendulum/traxxx/commit/50c5f921f54ca63d7a15634c8505b1d7132bef52, but parameter binding error supposedly still occurs.

pendulum added the

bug

label 2020-08-19 20:00:14 +00:00

Sign in to join this conversation.