Internal server error during publishing to OpenVSX registry
Summary
Publishing to OpenVSX ends up with "Internal server error". Publishing via open-vsx.org is stuck forever after selection of the VSIX bundle and clicking on the "Publish" button.
Steps to reproduce
Publish a new version of the extension via ovsx
or open-vsx.org.
What is the current bug behavior?
It is impossible to publish anything to open vsx registry.
What is the expected correct behavior?
Publishing is successful.
Relevant logs and/or screenshots
The ovsx
output:
17:07:34.071 $ ovsx publish --pat **** ./vsce/explorer-for-endevor.vsix
17:07:36.607 ❌ Internal Server Error
17:07:36.607 See the documentation for more information:
17:07:36.607 https://github.com/eclipse/openvsx/wiki/Publishing-Extensions
17:07:36.607 error Command failed with exit code 1.
17:07:36.607 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
17:07:36.607 error Command failed.
17:07:36.607 Exit code: 1
17:07:36.607 Command: /usr/local/bin/node
17:07:36.607 Arguments: /opt/yarn-v1.22.19/lib/cli.js publish:ovsx **** ./vsce/explorer-for-endevor.vsix
17:07:36.607 Directory: /var/Jenkins50/workspace/Explorers/E4E Publishing Pipeline/packages/explorer-for-endevor
17:07:36.607 Output:
17:07:36.607
17:07:36.607 info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command.
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
A release of Explorer for Endevor extension of 1.8.0 version is blocked for open-vsx registry.