unable to connect to isolate, terminated

[Smilex11]

unable to connect to isolate, terminated code: DEPLOYMENT_FAILED

[satyarohith]

Hi, @Smilex11. Can you provide details about your project?

This is an issue we are seeing recently. The error message is cryptic and we will improve it.

[Smilex11]

This is the project address https://github.com/Smilex11/NetEaseCloudMusicLyric, This project references cryptojs from npm, I think the main error comes from deno importing cryptojs

[doronaviguy]

I have the exact same issue ,

I use an npm package using require ( probably using the same package )

[Clownsw]

@satyarohith

[Smilex11]

I update my code, use unstable import npm package, But it still doesn't work @satyarohith

[Smilex11]

https://github.com/Smilex11/NetEaseCloudMusicLyric/blob/master/common.js#L5

[cleverplatypus]

Having the same issue. No access to meaningful error log. Only showing

unable to connect to isolate, terminated
2022-09-05 08:34:50

And by the way, the Log UI generally only shows a truncated tail of the logs, often missing the part of the error with the useful info.

[cleverplatypus]

Gaaak! Found the culprit, unless it's a red herring.

There was a comma at the end of a deconstructed object in an import

Changed

import {
  AppConfigSchema,
  SponsorshipTypeSchema,
  AuthoredFragmentSchema,
  StallApplicationSchema,
  SponsorshipInfoRequestSchema,
  UserSchema, // <-------
} from '../schema.ts';

to

import {
  AppConfigSchema,
  SponsorshipTypeSchema,
  AuthoredFragmentSchema,
  StallApplicationSchema,
  SponsorshipInfoRequestSchema,
  UserSchema
} from '../schema.ts';

and the issue went away.

There must be a better way to spot these issues without resorting to lucky guesses and fumbling and sifting through commits.

I love Deno and Deno Deploy but this is one of the hurdles that can seriously affect early adoption.

Peace

[gvbl]

I'm seeing this after deploying the Fresh bootstrap project, no changes. I did setup a custom domain. Is it possible this gateway error occurs until DNS propagation?

Update: My problem was that I took a guess thinking I needed to link index.tsx. I see now main.ts has a star by it which should have been indication enough to select it!

[Industrial]

I'm also getting this issue. I deployed a Fresh app and it worked but as I made changes and deployed more complicated code then basic examples the deployment stopped working and I got this error message.

Would just printing out the error that happened expose too much information?

[Industrial]

I fixed my bug with this: https://github.com/denoland/fresh/issues/774#issuecomment-1249933168