-
Notifications
You must be signed in to change notification settings - Fork 80
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
Publish API erroring with spurious "unregistered dependencies" error #692
Comments
I had to add it as an explicit dependency (even though it's a transient dep) with the range # spago.yaml
...
dependencies:
...
+ - node-fs: ">=9.1.0 <9.2.0"
... |
This is funny - @thomashoneyman @MonoidMusician do you have any insight on this? |
On the server I can see node-fs@9.2.0 is there in the registry metadata as of 2024-06-24: "9.2.0": {
"bytes": 13894,
"hash": "sha256-Sg0vkXycEzkEerX6hLccz21Ygd9w1+QSk1thotRZPGI=",
"publishedTime": "2024-06-24T07:23:53.247Z",
"ref": "v9.2.0"
} I can see the publish request for postgresql, which looks like it all succeeded, and then for node-stream-pipes (which failed). A few things stand out:
It's odd that node-fs@9.2.0 is considered missing. We can see registry-index and registry refresh calls here and everything is up to date as per Git. I also manually checked the registry and registry-index repositories on the machine and they include node-fs@9.2.0. The registry was pulled a few hours before this package was published:
So was the registry-index:
Here are the full logs of the failed node-stream-pipes publish.
I noticed that there is no node-fs@9.2.0 in the registry cache where we've downloaded packages:
Surely it should have been downloaded as part of the attempt to build node-stream-pipes, though, since it's there in metadata and the index and requested for the build? I'm really not sure what's going on here. |
I've been noticing issues with the registry solver lately changing its mind or disagreeing between builds, for example repeated |
Trying to publish my package
postgresql
andnode-stream-pipes
and getting the following error:This is definitely not true, since as far as I can tell it's as registered as it could be 😕
spago
: bleeding, masterpurs
: 0.15.15Full output
spago.yaml
spago.lock
The text was updated successfully, but these errors were encountered: