-
Notifications
You must be signed in to change notification settings - Fork 128
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
"Authorization by Eclipse required" error when attempting to publish with valid access token #913
Comments
It's the Eclipse access token that is missing or has expired. I'm currently looking into the Eclipse OAuth flow. Keep an eye on #912. |
is this something that can be set to never expire, or refreshed automatically? i'd rather not have to manually login and do this every month (or however often it expires) |
I'll add a job that checks for expired Eclipse access tokens and tries to refresh them. |
We are seeing the same issue.
As we use a service account on open-vsx which doesn't match my eclipse account github username, is the expectation to create a new eclipse account for all open-vsx users? |
In general it's the user associated with the personal access token that gets checked for a valid publisher agreement. |
Disregard what I said before. Release v0.15.4 fixes the issue. It will go live as soon as @kineticsquid has had a chance to review it. |
@amvanbaren I approved the PR. |
now i'm getting a different error:
https://github.com/DetachHead/basedpyright/actions/runs/9286481118/job/25553279137 |
@DetachHead Getting https://api.eclipse.org/account/profile/detachhead works for me. I guess it was a temporary outage. |
my extension is failing to publish with the following error:
(output from https://github.com/DetachHead/basedpyright/actions/runs/9094505273/job/24995738039)
i have not changed the access token since the previous release, and it's still valid on open-vsx.org:
it's definitely using that token since it updated the "Accessed" time. any ideas?
The text was updated successfully, but these errors were encountered: