Skip to content

Publishing to vscode/open vsx marketplace has failed for 1.3.0/1.4.0/1.5.0 #385

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

Closed
jneira opened this issue Apr 22, 2021 · 15 comments
Closed

Comments

@jneira
Copy link
Member

jneira commented Apr 22, 2021

Publishing haskell.haskell@1.3.0...

 ERROR  {"$id":"1","customProperties":{"Descriptor":null,"IdentityDisplayName":null,"Token":null,"RequestedPermissions":0,"NamespaceId":"00000000-0000-0000-0000-000000000000"},"innerException":null,"message":"Access Denied: The Personal Access Token used has expired.","typeName":"Microsoft.VisualStudio.Services.Security.AccessCheckException, Microsoft.VisualStudio.Services.WebApi","typeKey":"AccessCheckException","errorCode":0,"eventId":3000}

Script failed with status 1

//cc @alanz

@jneira jneira changed the title Publishing to vscode marketplace has failed for 1.3.0 Publishing to vscode marketplace has failed for 1.3.0 due to token expiration Apr 24, 2021
@jneira
Copy link
Member Author

jneira commented Apr 24, 2021

  1. It seems a new token has to be generated by a maintainer of the extension in the vscode marketplace: https://marketplace.visualstudio.com/manage/publishers/haskell
  2. Then a maintainer of this repo should update the secret key $VS_CODE in travis configuration (i am afraid i have no admin rights to do it): https://travis-ci.org/github/haskell/vscode-haskell/settings
  • I hope @jaspervdj could help us with that (happy to do step 2 if i get permissions to do it)

@jaspervdj
Copy link
Member

@jneira Sorry, somehow this notification ended up in my spam folder. I added a new token, please try it out before closing this.

@jneira
Copy link
Member Author

jneira commented Apr 30, 2021

Dont worry and many thanks, pushing the tag again

@jneira
Copy link
Member Author

jneira commented Apr 30, 2021

@jaspervdj i am afraid the publish step now has failed with another error (only http status this time):

Publishing haskell.haskell@1.3.0...

 ERROR  Failed request: (401)

Script failed with status 1

@jaspervdj
Copy link
Member

I set up a new one, try again? If that doesn't work I'll investigate a bit further what could be happening.

@jneira
Copy link
Member Author

jneira commented May 1, 2021

@jaspervdj this time it seems the token is missing:

error: option '-p, --pat <token>' argument missing

Script failed with status 1

@jaspervdj
Copy link
Member

I added a new token and manually verified it using vsce login haskell. I hope things work now? If not -- are we sure it's the VSCode marketplace that's broken, and not the Open VSX one?

@jneira
Copy link
Member Author

jneira commented May 9, 2021

thanks again, afaiu the full log i think the publish step of vscode is not being successful, it is the first publish step
I have to retag the version to take in account recent user requests, after that I will try again and remove the open vscode publishing if it fails again, just in case

@jneira
Copy link
Member Author

jneira commented May 11, 2021

@jaspervdj

are we sure it's the VSCode marketplace that's broken, and not the Open VSX one?

You were right, i didn't interpret the log correctly (tbh i find it a little bit confusing) but https://travis-ci.org/github/haskell/vscode-haskell/jobs/769167514#L404-L408. Sorry for the inconveniences.

It would be great to have the token to publish to open vsx as described here: #250 (comment)
Thanks in advance again!

@jneira
Copy link
Member Author

jneira commented May 12, 2021

Last build for 1.4.0 has published the extension to vscode marketplace but failed for open vsx with the same error: https://travis-ci.org/github/haskell/vscode-haskell/jobs/770880194

@jneira jneira changed the title Publishing to vscode marketplace has failed for 1.3.0 due to token expiration Publishing to vscode/open vsx marketplace has failed for 1.3.0/1.4.0 May 12, 2021
@jneira
Copy link
Member Author

jneira commented Jul 28, 2021

@jaspervdj hi, sorry to have to bother you again but the recent travis-ci.org switch off has affected this repo. The repos has to be migrated to travis-ci.com and they continue offering a free plan there. I dont have admin rights to migrate it.

@jneira jneira changed the title Publishing to vscode/open vsx marketplace has failed for 1.3.0/1.4.0 Publishing to vscode/open vsx marketplace has failed for 1.3.0/1.4.0/1.5.0 Jul 28, 2021
@jaspervdj
Copy link
Member

@jneira I enabled this on travis-ci.com, but unfortunately it looks like we're out of credits for haskell/ for the time being; so builds have been disabled. Are there any plans to move this to a more generous CI runner? In the short term, I can also ask some funds from Haskell.org to keep this running: it's around $800-1600/year, so a bit expensive if we want to keep this around forever.

@jneira
Copy link
Member Author

jneira commented Jul 30, 2021

@jaspervdj Thanks for take care! We were thinking to switch to github actions since some time ago, and knowing that we will do asap. However the incoming hls release needs this one so i would try to only being able to make this one which hopefully will be the last one. Or they only let get anual credits?

@jneira
Copy link
Member Author

jneira commented Jul 30, 2021

I've signing up for travis-ci.com and i see this repo in my profile, it has a warning:

Builds have been temporarily disabled for public repositories due to a negative credit balance. Please go to the Plan page to replenish your credit balance or alter your Consume paid credits for OSS setting.

What is that Consume paid credits for OSS setting? could we get free credits though them? If i click in thos links i've got an error in their web, i suppose i dont have permission to access or something

Or they only let get anual credits?

I've checked there are per month ($69)

@jneira
Copy link
Member Author

jneira commented Aug 3, 2021

the publishing using gha worked as a charm for 1.5.0 so i am gonna close it

@jneira jneira closed this as completed Aug 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants