Skip to content
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

Publishing blocked by missing Publisher Agreement but it is not missing #868

Open
lukashass opened this issue Mar 4, 2024 · 6 comments
Open

Comments

@lukashass
Copy link

The last publishing of Vue.volar failed with a supposedly missing Publisher Agreement, but my profile says You signed the Eclipse Foundation Open VSX Publisher Agreement 2 years ago.

The failed job:

https://github.com/vuejs/language-tools/actions/runs/8135692427/job/22230676005

Previous working job:

https://github.com/vuejs/language-tools/actions/runs/8128800486/job/22215105819

@lukashass
Copy link
Author

The next release worked again. So maybe this is already fixed.

@AnHeuermann
Copy link

Similar issue for me. I have a freshly created account on Open VSX that says You signed the Eclipse Foundation Open VSX Publisher Agreement now.

But both ovsx and the web interface report:

You must sign a Publisher Agreement with the Eclipse Foundation before publishing any extension.

@AnHeuermann
Copy link

Sorry for the noise. Seems to be working now. Only needs quiet some time until it's working.

@kuniss
Copy link

kuniss commented Mar 18, 2024

I'm facing the same problem and it seems to be a general problem. Maybe, it should be investigated as it seems to happen sporadically.
The build tells me

Error: You must sign a Publisher Agreement with the Eclipse Foundation before publishing any extension.
    at IncomingMessage.<anonymous> (/home/runner/.npm/_npx/7e6088d414b28cf8/node_modules/ovsx/lib/registry.js:185:40)
    at IncomingMessage.emit (node:events:538:35)
    at endReadableNT (node:internal/streams/readable:1345:12)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)

But mine is signed since 3 years.
Moreover, I have 2 other extensions in the same build run which got successfully published just seconds before without showing the error.

Here is the GitHub Action log, if it helps:
logs_21812981459.zip

@sourishkrout
Copy link

The issue appeared to be solve and now it's back for me too.

@PEZ
Copy link

PEZ commented Apr 8, 2024

Happening for me now with an extension I've had a signed agreement for years and been publishing successfully hundreds of times.

I retried, thinking it was a rare glitch, but it still failed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo
Development

No branches or pull requests

5 participants