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.

Sign up for GitHub

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

Jump to bottom

"Error: Internal Server Error" on publish #731

Open
sourishkrout opened this issue Apr 26, 2023 · 9 comments
Open

"Error: Internal Server Error" on publish #731

sourishkrout opened this issue Apr 26, 2023 · 9 comments

Comments

@sourishkrout
Copy link

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.
@sourishkrout sourishkrout mentioned this issue Apr 26, 2023
Closed
@amvanbaren
Copy link
Contributor

amvanbaren commented May 3, 2023 •
edited

Hi @sourishkrout, can you try to publish again?

@sourishkrout
Copy link
Author

sourishkrout commented May 3, 2023 •
edited

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!

@amvanbaren
Copy link
Contributor

@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 @stateful.runme-1.2.1682533874@darwin-arm64.vsix

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.

@amvanbaren amvanbaren mentioned this issue May 5, 2023
Closed
@amvanbaren
Copy link
Contributor

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

@degrammer
Copy link

@amvanbaren Seems the issue we are having is related to a duplicated namespace, see EclipseFdn/open-vsx.org#877 (comment)

@sourishkrout
Copy link
Author

@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 EclipseFdn/open-vsx.org#877 (comment).

@amvanbaren
Copy link
Contributor

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

@sourishkrout sourishkrout mentioned this issue May 22, 2023
Closed
@sourishkrout
Copy link
Author

sourishkrout commented Jul 16, 2023 •
edited

@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?

@amvanbaren
Copy link
Contributor

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

I've created issue EclipseFdn/open-vsx.org#1980.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Eclipse Open VSX
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
3 participants
@sourishkrout @degrammer @amvanbaren