denoland / denoland/deploy_feedback

[Bug]: Deploying a project with no HTTP endpoints results in ISOLATE_INTERNAL_FAILURE

Open
#849 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
79
Forks
5
PR merge metrics
No merged PRs in 30d

Description

### Problem description

Attempting to deploy a project with no HTTP endpoints fails with the error:

`{"type":"error","code":"deploymentFailed","ctx":"The deployment failed: ISOLATE_INTERNAL_FAILURE"}`

Given that this error can be triggered by
`
// Deno.serve(() => new Response("Hello, world!"));
console.log("no chance")
`

whilst the following works fine

`
Deno.serve(() => new Response("Hello, world!"));
console.log("this works now")
`
it would appear that the error is in some way due to the lack of a HTTP endpoint.

There are quite a few scenarios in which it would be handy to use Deno's cron api on deploy without serving anything e.g. to interact with a Telegram bot.

### Steps to reproduce

1. create a project with entrypoint contents `console.log("foo")`
2. attempt to deploy

### Expected behavior

The project should deploy succesfully.

### Environment

_No response_

### Possible solution

_No response_

### Additional context

_No response_

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with a Deno Deploy project whose entrypoint is `console.log("foo")` and attempt deployment; compare it with the `Deno.serve` example. Done is a successful deployment for a project with no HTTP endpoints, while deployment with an HTTP endpoint continues to work.

Written by the indexing model from the issue text.

Assessment

Tech stack
deno
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.