Closed napter closed 2 years ago
Is this the notion api bug? It happens quite frequently. It seems a bug after all the pages has been exported and when notion is trying to bundle them in a zip file.
"Task error: You cannot pipe after data has been emitted from the response." This is the error returned from the notion api.
@darobin was this fixed or something? I'd love to revisit if so.
Hi, thanks for publishing this. I am trying it out but I get this error during the export:
[...] Pages exported: 966 Task error: You cannot pipe after data has been emitted from the response. Task error: You cannot pipe after data has been emitted from the response. Task error: You cannot pipe after data has been emitted from the response. Task error: You cannot pipe after data has been emitted from the response. Task error: You cannot pipe after data has been emitted from the response. (node:1837) UnhandledPromiseRejectionWarning: Error: end of central directory record signature not found at /opt/hostedtoolcache/node/12.22.3/x64/lib/node_modules/notion-backup/node_modules/yauzl/index.js:187:14 at /opt/hostedtoolcache/node/12.22.3/x64/lib/node_modules/notion-backup/node_modules/yauzl/index.js:631:5 at /opt/hostedtoolcache/node/12.22.3/x64/lib/node_modules/notion-backup/node_modules/fd-slicer/index.js:32:7 at FSReqCallback.wrapper [as oncomplete] (fs.js:520:5) (node:1837) 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: 1) (node:1837) [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.