Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

request timed out #215

Closed
ralyodio opened this issue Nov 14, 2021 · 19 comments
Closed

request timed out #215

ralyodio opened this issue Nov 14, 2021 · 19 comments
Labels
bug Something isn't working

Comments

@ralyodio
Copy link

error: Import 'https://cdn.esm.sh/v57/nlcst-to-string@2.0.4/es2021/nlcst-to-string.js' failed: 408 Request Timeout
    at https://cdn.esm.sh/v57/parse-latin@5.0.0/es2021/parse-latin.js:2:27264
import { retext } from 'https://cdn.esm.sh/v57/retext@8.1.0/es2021/retext.js';
import retextKeywords from 'https://cdn.esm.sh/v57/retext-keywords@7.1.0/es2021/retext-keywords.js';
import retextPos from 'https://cdn.esm.sh/v57/retext-pos@4.1.0/es2021/retext-pos.js';
@ralyodio ralyodio added the bug Something isn't working label Nov 14, 2021
@talentlessguy
Copy link
Contributor

is this bug still present?

@samlaycock
Copy link

samlaycock commented Nov 17, 2021

I'm getting the same trying to import @aws-sdk/client-kinesis:

import * as Kinesis from "https://esm.sh/@aws-sdk/client-kinesis@3.41.0?pin=v57&no-check";
Download https://cdn.esm.sh/v57/@aws-crypto/crc32@2.0.0/deno/crc32.js
error: Import 'https://cdn.esm.sh/v57/@aws-crypto/crc32@2.0.0/deno/crc32.js' failed: 408 Request Timeout

Had it with other @aws-sdk packages, but they eventually worked after waiting a while. This has been like this since I originally tried to download it 2 days ago...

@jacque006
Copy link

I'm also encountering this. Seems to fail for some packages but works for others.

HTTP 408

Works fine

Looks like some more heavily used/common packages that are already cached are okay.

Workaround

Use https://cdn.skypack.dev or another similar esm shim provider/cdn.

@deckchairlabs
Copy link

Had this output presented to me, after I received a 408 previously. Looks like the CDN has cached the output of the process even though it failed to process the request.

You should be able to see the same output by visiting https://esm.sh/react-router-dom/server

yarn add react-router-dom@6.0.2: yarn add v1.22.11
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning " > react-router-dom@6.0.2" has unmet peer dependency "react@>=16.8".
warning " > react-router-dom@6.0.2" has unmet peer dependency "react-dom@>=16.8".
warning "react-router-dom > react-router@6.0.2" has unmet peer dependency "react@>=16.8".
error Could not write file "/tmp/esm-build-92694869e2404d4459722e05644d3c3e93d6fb6e-4812977b/yarn-error.log": "ENOSPC: no space left on device, open '/tmp/esm-build-92694869e2404d4459722e05644d3c3e93d6fb6e-4812977b/yarn-error.log'"
error An unexpected error occurred: "ENOSPC: no space left on device, mkdir '/tmp/esm-build-92694869e2404d4459722e05644d3c3e93d6fb6e-4812977b/node_modules/react-router'".
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.

@ije
Copy link
Member

ije commented Nov 18, 2021

I just released v58, fixed the build cache problem (build task did not delete the cache directory after build randomly that stolen a lot of system storage space).

@jacque006
Copy link

Confirmed that issue is resolved/fixed on my end, thanks @ije !

@samlaycock
Copy link

@ije thanks for the update, but I'm still having problems importing into Deno. It seems that /es2021 builds are fine, but the /deno ones still seem to time out.

I can run this project locally and it appears to work fine using localhost:8080, it's only when downloading from https://esm.sh that the timeouts happen.

@ije
Copy link
Member

ije commented Nov 21, 2021

@samlaycock which package you import? i will look into it

@DetachHead
Copy link
Contributor

@ije getting 408 trying to use any of my packages, eg. https://esm.sh/@detachhead/ts-helpers

@clo4
Copy link

clo4 commented Nov 22, 2021

I'm getting timeouts with the lastest AJV versions (8.6.3 works for me but it might be cached, 8.7.0+ is broken)
https://esm.sh/ajv@8.8.2/dist/jtd

@ije
Copy link
Member

ije commented Nov 22, 2021

@separaterecords I just recovered the stable queue used before in c2677ef

@samlaycock
Copy link

@ije Hey, sorry for the delayed response. My issue was around some dependencies related to @aws-sdk/* packages, but it appears this is now fixed with the latest changes. Thanks!

@myobie
Copy link

myobie commented Nov 24, 2021

I'm seeing timeouts for preact/debug and preact/test-utils. preact and preact/hooks are working. I've tried to pin back a couple versions, but they timeout as well.

@johanbrook
Copy link

As of today, with esm.sh v58, I'm also seeing timeouts for https://esm.sh/preact@10.

@johanbrook
Copy link

Now it works again, but I briefly saw this while refreshing:

/* esm.sh - error */
throw new Error("[esm.sh] " + "yarn add preact@10.6.1: yarn add v1.22.17\ninfo No lockfile found.\n[1/4] Resolving packages...\n[2/4] Fetching packages...\n[3/4] Linking dependencies...\nerror An unexpected error occurred: \"ENOENT: no such file or directory, copyfile '/esms/yarn/v6/npm-preact-10.6.1-e14de611b65aea5e656249d19582c457fb0aa255-integrity/node_modules/preact/README.md' -\u003e '/tmp/esm-build-1c052b647e58939025a8add6a7b5c259e7bded07-f613e5bd/node_modules/preact/README.md'\".\ninfo If you think this is a bug, please open a bug report with the information provided in \"/tmp/esm-build-1c052b647e58939025a8add6a7b5c259e7bded07-f613e5bd/yarn-error.log\".\ninfo Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.\n");
export default null;

@myobie
Copy link

myobie commented Nov 25, 2021

Just FYI – I've setup a copy of esm.sh to run in my infra and it is able to build and serve all the packages I am using without any timeouts, so I do think the production builds of some packages are stuck in some way I don't understand. Also, thanks for making it so easy to boot up and host ❤️

@ije
Copy link
Member

ije commented Nov 26, 2021

i improved the nodejs service in 65f0b94, which may block the message channel then case the timeout problem

@myobie
Copy link

myobie commented Nov 26, 2021

So far, every package I've tested on esm.sh has worked, so your fix may have indeed fixed the timeouts. I'll keep checking for the next few days and let you know if I see anymore.

@nnmrts
Copy link

nnmrts commented Nov 27, 2021

Yup, this fixed everything, thanks @ije. For example, react@18 just didn't work before, now it does without any problems.

@ije ije closed this as completed Dec 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests