Deploy failed
bug
My Github deploy.yml currently deploys to both Observable Cloud and Github Pages, while the migration is happening. Normally it works just fine, and I haven't changed anything in the script or in any of my pages since the last time I ran it, but it just failed. It seems to have built everything correctly on the Observable-hosted page, but it didn't make it to the Github deployment. Here's error log, which I'm pretty sure came from the Observable side of things:
```
Run npm run deploy -- --message "$(git log -1 --pretty=%s)"
npm run deploy -- --message "$(git log -1 --pretty=%s)"
shell: /usr/bin/bash -e {0}
env:
DEPLOY_TARGET: gh-pages
pythonLocation: /opt/hostedtoolcache/Python/3.13.5/x64
PKG_CONFIG_PATH: /opt/hostedtoolcache/Python/3.13.5/x64/lib/pkgconfig
Python_ROOT_DIR: /opt/hostedtoolcache/Python/3.13.5/x64
Python2_ROOT_DIR: /opt/hostedtoolcache/Python/3.13.5/x64
Python3_ROOT_DIR: /opt/hostedtoolcache/Python/3.13.5/x64
LD_LIBRARY_PATH: /opt/hostedtoolcache/Python/3.13.5/x64/lib
OBSERVABLE_TOKEN: ***
> deploy
> observable deploy --message Auto-update model_json_backup.json and objects_json_backup.json
┌ observable deploy v1.13.3
│
▲ Deploying data apps to Observable Cloud is now deprecated. Please migrate your
│ data app to another static site hosting provider, such as GitHub Pages, Render,
│ Cloudflare Pages, Vercel, or Netlify. For more details, please see:
│ https://observablehq.com/release-notes/2025-04-15-deprecating-observable-cloud
TypeError: fetch failed
at node:internal/deps/undici/undici:13510:13
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async doFetch (file:///home/runner/work/visualizing_intertextuality/visualizing_intertextuality/node_modules/@observablehq/framework/dist/observableApiClient.js:48:33)
at async ObservableApiClient._fetch (file:///home/runner/work/visualizing_intertextuality/visualizing_intertextuality/node_modules/@observablehq/framework/dist/observableApiClient.js:50:18)
at async ObservableApiClient.getCurrentUser (file:///home/runner/work/visualizing_intertextuality/visualizing_intertextuality/node_modules/@observablehq/framework/dist/observableApiClient.js:91:12)
at async Deployer.setApiClientAndCurrentUser (file:///home/runner/work/visualizing_intertextuality/visualizing_intertextuality/node_modules/@observablehq/framework/dist/deploy.js:73:23)
at async Deployer.deploy (file:///home/runner/work/visualizing_intertextuality/visualizing_intertextuality/node_modules/@observablehq/framework/dist/deploy.js:60:5)
at async Module.deploy (file:///home/runner/work/visualizing_intertextuality/visualizing_intertextuality/node_modules/@observablehq/framework/dist/deploy.js:44:22)
at async file:///home/runner/work/visualizing_intertextuality/visualizing_intertextuality/node_modules/@observablehq/framework/dist/bin/observable.js:124:7 {
[cause]: AggregateError [ETIMEDOUT]:
at internalConnectMultiple (node:net:1134:18)
at internalConnectMultiple (node:net:1210:5)
at Timeout.internalConnectMultipleTimeout (node:net:1742:5)
at listOnTimeout (node:internal/timers:590:11)
at process.processTimers (node:internal/timers:523:7) {
code: 'ETIMEDOUT',
Error: [errors]: [ [Error], [Error], [Error], [Error] ]
}
}
│
■ Error: fetch failed
│
● To see the full stack trace, run with the --debug flag.
│
│ If you think this is a bug, please file an issue at
└ https://github.com/observablehq/framework/issues
Error: Process completed with exit code 1.
```
I'm not sure how to "run with the --debug flag" to see the "full stack trace," but if someone can tell me how, I can presumably provide more information if needed.
关闭于 2025-08-01 3 条评论