frequent, random HTTP import failure

[scarf005]

Version: deno 1.44.3+f4eead6 (canary, x86_64-unknown-linux-gnu)

Issue

deno cache/download for the first time (in CI) frequently fails, randomly, unexpectedly.

Steps to reproduce

test.ts

import { z } from "https://deno.land/x/[email protected]/mod.ts"
import { Command } from "https://deno.land/x/[email protected]/deps/cliffy.ts"
import { cliOptions } from "https://deno.land/x/[email protected]/utils/cli.ts"
import { timeit } from "https://deno.land/x/[email protected]/utils/timeit.ts"
import {
  applyRecursively,
  schemaTransformer,
} from "https://deno.land/x/[email protected]/utils/transform.ts"
import {
  type CataEntry,
  Entry,
  parseCataJson,
  readRecursively,
} from "https://deno.land/x/[email protected]/utils/parse.ts"
import { fmtJsonRecursively } from "https://deno.land/x/[email protected]/utils/json_fmt.ts"
import { match, P } from "https://deno.land/x/[email protected]/deps/ts_pattern.ts"
import { id } from "https://deno.land/x/[email protected]/utils/id.ts"

deno cache --reload --lock=deno.lock --lock-write test.ts

---

tracing log: error.log

[dworzycp]

We've also noticed this in our CI - seems to be related to the latest 1.44.3 release.

Downgrading deno to 1.44.2 fixes the problem, can do this with deno upgrade --version 1.44.2

[lucacasonato]

We are also noticing this internally. It is likely caused by 22f2779. We will pull 1.44.3 while we are investigating. Sorry for the troubles.

UPDATE: 1.44.3 has been pulled - installing Deno in CI should now install 1.44.2 again.

[scarf005]

UPDATE: 1.44.3 has been pulled - installing Deno in CI should now install 1.44.2 again.

https://github.com/cataclysmbnteam/Cataclysm-BN/actions/runs/9582298163/job/26422268220

it looks like CI still installs 1.44.3 given version range 1.x, should i trigger new CI using empty commits instead of re-run failed jobs?

[lucacasonato]

This should now be fixed @scarf005 - please try again by just re-running

[scarf005]

This should now be fixed @scarf005 - please try again by just re-running

it works now, thanks for the quick action @lucacasonato