Sabah Kaldwin
Sabah Kaldwin17mo ago

Running `deno cache` fails often with internal server errors when importing

Example message
error: Import 'https://deno.land/std@0.175.0/path/_constants.ts' failed: 500 Internal Server Error
May 29 10:30:08 AM #14 309.3 at https://deno.land/std@0.175.0/path/win32.ts:12:8
May 29 10:30:08 AM ------
May 29 10:30:08 AM Dockerfile:18
May 29 10:30:08 AM --------------------
May 29 10:30:08 AM 16 | WORKDIR /app
May 29 10:30:08 AM 17 |
May 29 10:30:08 AM 18 | >>> RUN deno cache ./main.ts
May 29 10:30:08 AM 19 |
May 29 10:30:08 AM 20 | CMD ["run", "--allow-net", "--allow-read", "--allow-env", "--allow-write", "main.ts"]
May 29 10:30:08 AM --------------------
May 29 10:30:08 AM error: failed to solve: process "/bin/sh -c deno cache ./main.ts" did not complete successfully: exit code: 1
May 29 10:30:08 AM error: exit status 1
error: Import 'https://deno.land/std@0.175.0/path/_constants.ts' failed: 500 Internal Server Error
May 29 10:30:08 AM #14 309.3 at https://deno.land/std@0.175.0/path/win32.ts:12:8
May 29 10:30:08 AM ------
May 29 10:30:08 AM Dockerfile:18
May 29 10:30:08 AM --------------------
May 29 10:30:08 AM 16 | WORKDIR /app
May 29 10:30:08 AM 17 |
May 29 10:30:08 AM 18 | >>> RUN deno cache ./main.ts
May 29 10:30:08 AM 19 |
May 29 10:30:08 AM 20 | CMD ["run", "--allow-net", "--allow-read", "--allow-env", "--allow-write", "main.ts"]
May 29 10:30:08 AM --------------------
May 29 10:30:08 AM error: failed to solve: process "/bin/sh -c deno cache ./main.ts" did not complete successfully: exit code: 1
May 29 10:30:08 AM error: exit status 1
The above happens often to our deployments, and it's usually a deno.land package. Rerunning the deployment usually succeeds, so we aren't really blocked, but this is frustrating with how frequent it is
1 Reply
Leokuma
Leokuma17mo ago
I think you could open an issue about it and share your code if possible so that people can reproduce and analyze the error