openvsx "Error: Internal Server Error" on publish

The attempt to publish a platform-specific extension that previously was uploaded to MSFT's marketplace without errors. The vsix files are available here https://github.com/stateful/vscode-runme/releases/tag/1.1.1

npx ovsx publish --debug --packagePath runme-darwin-arm64-1.1.1.vsix -p <valid-token-redacted> --target darwin-arm64

The publish attempt results in a nebulous 500 internal server error:

{
 "timestamp": "2023-04-26T13:39:15.445+00:00",
 "status": 500,
 "error": "Internal Server Error",
 "path": "/api/-/publish"
}

Any pointers or directions you could provide for us to resolve this issue would be much appreciated. I've looked thru the server code for some time, but it's a bit like looking for a needle in a haystack.

Happy to provide more info.

Apr 26 '23 15:04 sourishkrout

Hi @sourishkrout, can you try to publish again?

May 03 '23 16:05 amvanbaren

Hi @sourishkrout, can you try to publish again?

Just retried and received this error message:

$ npx ovsx publish --debug --packagePath '/Users/sourishkrout/Downloads/runme-darwin-arm64-1.1.1.vsix' -p $TOKEN --target darwin-arm64
Error: Internal Server Error
    at IncomingMessage.<anonymous> (/Users/sourishkrout/.asdf/installs/nodejs/18.13.0/.npm/lib/node_modules/ovsx/lib/registry.js:185:40)
    at IncomingMessage.emit (node:events:525:35)
    at endReadableNT (node:internal/streams/readable:1359:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

Appreciate your help, @amvanbaren!

May 03 '23 21:05 sourishkrout

@sourishkrout I couldn't find anything related to the error you posted. I published the runme extension under my own namespace through the webui and it worked: https://open-vsx.org/extension/amvanbaren/runme.

When I try to publish the extension via the API using cURL, I get a 413: Request Entity Too Large:

curl -X POST --location 'http://open-vsx.org/api/-/publish?token=${token}' --header 'Content-Type: application/octet-stream' --data-binary @[email protected]

Response:

<head><title>413 Request Entity Too Large</title></head>
<body>
<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>
</body>
</html>

I'll create a new issue in the EclipseFdn/open-vsx.org repo to ask if this is a bug or a feature.

May 05 '23 08:05 amvanbaren

@sourishkrout I tried it again using ovsx and it worked: https://open-vsx.org/extension/amvanbaren/runme/1.1.1

May 11 '23 08:05 amvanbaren

@amvanbaren Seems the issue we are having is related to a duplicated namespace, see https://github.com/EclipseFdn/open-vsx.org/issues/877#issuecomment-1551886323

May 17 '23 18:05 degrammer

@amvanbaren publication still fails with a 500 internal server error under the stateful namespace for both ovsx and the web publication form. The fact it works under your own amvanbaren namespace does raise the question if it's connected to the namespace duplication https://github.com/EclipseFdn/open-vsx.org/issues/877#issuecomment-1551886323.

May 19 '23 13:05 sourishkrout

Yes, that's most likely the case. The server expects to get 1 namespace but gets 2 which results in an exception.

May 19 '23 15:05 amvanbaren

@sourishkrout I tried it again using ovsx and it worked: https://open-vsx.org/extension/amvanbaren/runme/1.1.1

Hi @amvanbaren, can you please un-publish amvanbaren.runme?

We had a user be confused by why stateful.runme is not available but a amvanbaren.runme. It served its purpose of testing publishing and since we now have identified the root-cause be a namespace clash, we should be able to remove it right?

Jul 16 '23 18:07 sourishkrout

Hi @amvanbaren, can you please un-publish amvanbaren.runme?

I've created issue https://github.com/EclipseFdn/open-vsx.org/issues/1980.

Jul 17 '23 09:07 amvanbaren