-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Bug?]: No candidates found in corporate environment #6477
Comments
I can confirm the issue. It oocurs on self hostet gitlab instances. It seems the metadata crawls only the official npm registries but not others, so maybe it also wont work on public repository packages? Yarn install should also look for a .yarnrc.yml and include the custom npm registry, which is not yet the case as it seems. |
Given the fact that the issue only reproduces on GitLab registries, which makes it quite hard for us to recreate the environment, would it be possible for any of you to debug it further using the unminified binary? If not, would it be possible for you to at least create a test GitLab registry that we could install a package from so that we can debug it ourselves? Details for debugging (Click to expand)
Basically, Yarn first loads the metadata from disk and puts it inside an in-memory cache ( For the metadata to be stale, something has to go wrong somewhere in those functions. |
I wonder if perhaps the gitlab self-hosted registry returns invalid caching headers. But as Paul said, we either need a reproduction we can run ourselves, or that you dig into it to find out where we miss something (you can run |
@paul-soporan I tried debugging as you said, inside is it possible to force yarn to receive the metadata from server every time for the time being? |
Self-service
Describe the bug
this issue is the same as #5989.
we have a npm registry in our corporate gitlab instance (https://gitlab.****/api/v4/projects/375/packages/npm/)
when i publish a new package to the repository and then try to install the new version in my project i get the following error:
this command
yarn npm info @******/utils
gives:the content of
~/.yarn/berry/metadata/npm/3fb1ad/gitlab.********/@*****-utils.json
:To reproduce
I cannot provide, as this only occurs in my company repo
Environment
System: OS: Linux 6.8 Ubuntu 24.04 LTS 24.04 LTS (Noble Numbat) CPU: (6) x64 Intel(R) Core(TM) i5-9600K CPU @ 3.70GHz Binaries: Node: 21.7.0 - /tmp/xfs-226a6d5a/node Yarn: 4.4.1 - /tmp/xfs-226a6d5a/yarn npm: 10.5.0 - ~/.nvm/versions/node/v21.7.0/bin/npm
Additional context
No response
The text was updated successfully, but these errors were encountered: