darobin / notion-backup

Simple command to backup a Notion workspace
MIT License
423 stars 63 forks source link

Missing output files #1

Closed salmanjt closed 3 years ago

salmanjt commented 3 years ago

Hi Darobin!

First of all, thanks for creating a simple workflow for automating notion backups. I forked the repository and have successfully ran the workflow through github actions. It says the workflow was run successfully.

Unfortunately, I cant seem to locate the output files in my github repo. Do I first need to create the markdown and html directories? Please let me know thanks.

darobin commented 3 years ago

No, you shouldn't need to create the directories first.

salmanjt commented 3 years ago

Thanks for getting back, so after checking the workflow logs I have identified the error below at the Run backup stage

  notion-backup
  shell: /usr/bin/bash -e {0}
  env:
    NOTION_TOKEN: ***
    NOTION_SPACE_ID: ***
(node:1966) UnhandledPromiseRejectionWarning: Error: Request failed with status code 401
    at createError (/opt/hostedtoolcache/node/12.22.1/x64/lib/node_modules/notion-backup/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/opt/hostedtoolcache/node/12.22.1/x64/lib/node_modules/notion-backup/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/opt/hostedtoolcache/node/12.22.1/x64/lib/node_modules/notion-backup/node_modules/axios/lib/adapters/http.js:260:11)
    at IncomingMessage.emit (events.js:326:22)
    at endReadableNT (_stream_readable.js:1241:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:21)
(node:1966) 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:1966) [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.
darobin commented 3 years ago

Error 401: this looks like you have the wrong token or space ID. Are you sure they're correct?

salmanjt commented 3 years ago

Yes, I didn't have the token_v2 copied correctly into GitHub secrets. Just updated the value and re-run the workflow, the pages are now being exported, a long wait now haha.

Thanks for your help, I appreciate it 👍🏼