coty•3mo ago

Debug deno deploy failures ISOLATE_INTERNAL_FAILURE

how can you debug deno deploy failures?

cotyhamilton dev/no-build (main)
➜ deployctl deploy --project=no-build --entrypoint=mod.ts
ℹ Using config file '/Users/cotyhamilton/dev/no-build/deno.json'
✔ Deploying to project no-build.
✔ Entrypoint: /Users/cotyhamilton/dev/no-build/mod.ts
ℹ Uploading all files from the current dir (/Users/cotyhamilton/dev/no-build)
✔ Found 37 assets.
✔ No new assets to upload.
✖ Deployment failed.
error: The deployment failed: ISOLATE_INTERNAL_FAILURE

cotyhamilton dev/no-build (main)
➜ deployctl logs --project=no-build
ℹ Using config file '/Users/cotyhamilton/dev/no-build/deno.json'
✔ Project: no-build
2024-05-21T04:35:51.362199787Z   gcp-us-east4 isolate start time: 16.20 ms
2024-05-21T04:35:54.596194223Z   gcp-us-east4 isolate start time: 16.19 ms
2024-05-21T04:35:57.966894225Z   gcp-us-east4 isolate start time: 27.15 ms
2024-05-21T04:36:01.619310600Z   gcp-us-east4 isolate start time: 21.97 ms
2024-05-21T04:36:05.593898029Z   gcp-us-east4 isolate start time: 27.28 ms

cotyhamilton dev/no-build (main)
➜ deployctl deploy --project=no-build --entrypoint=mod.ts
ℹ Using config file '/Users/cotyhamilton/dev/no-build/deno.json'
✔ Deploying to project no-build.
✔ Entrypoint: /Users/cotyhamilton/dev/no-build/mod.ts
ℹ Uploading all files from the current dir (/Users/cotyhamilton/dev/no-build)
✔ Found 37 assets.
✔ No new assets to upload.
✖ Deployment failed.
error: The deployment failed: ISOLATE_INTERNAL_FAILURE

cotyhamilton dev/no-build (main)
➜ deployctl logs --project=no-build
ℹ Using config file '/Users/cotyhamilton/dev/no-build/deno.json'
✔ Project: no-build
2024-05-21T04:35:51.362199787Z   gcp-us-east4 isolate start time: 16.20 ms
2024-05-21T04:35:54.596194223Z   gcp-us-east4 isolate start time: 16.19 ms
2024-05-21T04:35:57.966894225Z   gcp-us-east4 isolate start time: 27.15 ms
2024-05-21T04:36:01.619310600Z   gcp-us-east4 isolate start time: 21.97 ms
2024-05-21T04:36:05.593898029Z   gcp-us-east4 isolate start time: 27.28 ms

3 Replies

coty•3mo ago

I figured out it's because I was trying to use the declarative server

export default {
  fetch(request: Request) {
    return app.fetch(request);
  },
};

export default {
  fetch(request: Request) {
    return app.fetch(request);
  },
};

Deno AI Helper•3mo ago

I wasn't able to find the answer to your question in the official Deno documentation. However, based on the information you've provided, the ISOLATE_INTERNAL_FAILURE error suggests that there is an internal issue with the Deno Deploy infrastructure. From the snippet you've shared, I don't see any obvious syntax errors or mistakes in the commands you've used. The commands appear to be correct for deploying a project and retrieving logs with deployctl. Since this advice is not based on the Deno documentation, please double-check the accuracy of the advice given. For further assistance, you may want to reach out to the Deno community or maintainers for more specific guidance on the ISOLATE_INTERNAL_FAILURE error. They might be able to provide more context or help you troubleshoot the issue further.

Helpful Links: Deno 1.36: More flexible security and expanded testing APIs Deno 1.4 Release Notes Deno 1.21 Release Notes How to setup a blog with Hugo and Deno Deploy Deploy Quick Start | Deno Docs Deployments | Deno Docs CI and GitHub Actions | Deno Docs Prisma error when trying to push/migrate db - Deno import plotly.js : invalid or unexpected token ? - Deno

dantheman•3mo ago

I've also had internal failure happen when I forgot to set up an http server... they should give a better error