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

Where to report issues about very slow plugin downloads? (broken IPv6) #768

Open
jochumdev opened this issue May 4, 2024 · 5 comments
Open

Comments

@jochumdev
Copy link

jochumdev commented May 4, 2024

It seems like trunk upgrade -v is very very slow here.

image

I've tested it much longer as well.

Anyone can help with that?

Infos about my system:

OS: Manjaro Linux Sway Edition
CPU: AMD Ryzen 9 5900X 12-Core Processor
RAM: 48093 MiB

@jochumdev
Copy link
Author

Works on my ArchLinux box as intended.

@TylerJang27
Copy link
Collaborator

Hi @jochumdev! Sorry you're having this issue. This is definitely a good place to report this, although it may be easier to join our Slack channel.

Just to clarify, is it usually the prettier install that takes a long time? Is it always prettier or sometimes other tools?

If you could provide 2 other things, it would help us investigate:

  1. Your .trunk/trunk.yaml file
  2. After enabling a new version of prettier, run trunk check --debug and grab the full log output. Feel free to upload as a gist or via DM in Slack.

@jochumdev
Copy link
Author

jochumdev commented May 5, 2024

Hey @TylerJang27 thanks for answering. I found the root cause. It was half working IPv6. Once I disabled IPv6 on my link everything worked as intended.

So with broken IPv6 trunk doesn't works as intended.

@jochumdev jochumdev changed the title Where to report issues about very slow plugin downloads? Where to report issues about very slow plugin downloads? (broken IPv6) May 5, 2024
@TylerJang27
Copy link
Collaborator

Thanks for investigating. We'll take a closer look and get to the bottom of this

@TylerJang27
Copy link
Collaborator

Could you try setting:

export NODE_OPTIONS=--dns-result-order=ipv4first

Then running:

trunk daemon shutdown
# if necessary, clear ~/.cache/trunk/tools
trunk check

It appears this issue can result from certain misconfiguration of IPv6 and the npm package registry. We'll look into documenting this appropriately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants