-
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
Verify repository exists before attempting to clone it #684
Comments
This is a Registry error, see the logs when we query the API using the job id from your logs:
That tag was created at |
@thomashoneyman any clue what might be happening here? The spago config seems alright |
The first error is strange:
We clone the repository early in publishing: registry-dev/app/src/App/API.purs Line 370 in ef989a1
Here's the implementation of that registry-dev/app/src/App/Effect/Source.purs Lines 78 to 81 in ef989a1
Under the hood it's just calling registry-dev/app/src/App/CLI/Git.purs Lines 74 to 80 in ef989a1
|
@f-f @flip111 The error is not good, but I would guess this is happening because the repository field in the Spago config is incorrect: It lists the repository as |
Thank you for looking into this. I changed the repo name and it worked. Let's keep this issue open to make a better error message. |
Ah indeed! Thanks Thomas. I guess both the registry and spago should check for the existence of the repo before doing their thing. |
What was actually output to the console from the Spago publish? The registry generally comments this line:
What error would y'all want instead? Some kind of preflight check that the repository exists, and an error "Repository |
Yeah, errors from |
The errors returned to the user are the ones appearing in the API call, and the first one is pretty confusing: |
I think a simple |
This works ...
Doesn't work
I don't have 2fa authenticated on github yet, not sure if that's related but i just mentioned it in case.
The text was updated successfully, but these errors were encountered: