-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Internal Server Error when trying to access npm packages #20755
Comments
I think it's because package is missing a |
I purged all my existing packages, added added a description to this one as a test, and published again. Still receiving a 500 error {
"author": {
"name": "mp3three"
},
"name": "@steggy/home-assistant",
"displayName": "Home Assistant",
"license": "MIT",
"version": "22.33.13",
"scripts": {
"postinstall": "npx hass-type-generate"
},
"description": "HELLO WORLD",
"main": "./src/index.js",
"typings": "./src/index.d.ts",
"dependencies": {
// ...
},
"peerDependencies": {}
} Is there other fields I am missing? |
Then my assumption is wrong. Your data looks fine. I think the minimum required properties should be just |
Duplicate of #20670 But I missed to create a backport for that PR. |
Is it? Seems unrelated to unpublish here. |
I think this was fixed by #20675, it just referenced wrong issue it fixed |
I am able to confirm this issue is resolved already. Built a docker container from HEAD, and the page properly loads. I'm guessing the next real build will have the fix Thank you all |
Description
I cannot access the details of any of the NPM packages being published from my server from the web UI. Url:
/mp3three/-/packages/npm/@steggy%2Fhome-assistant/22.33.13
The published docker container seems fine, currently all of my npm packages are giving 500 errors. I am able to interact with them just fine via yarn (install, upgrade, etc), and there are no issues deleting the packages from the site management screen. Every time that I load the page giving me the 500 error, I get this line in the logs:
This is an an example
package.json
that was published with one of the packages:Gitea Version
gitea/gitea:latest docker image (1.17.0)
Can you reproduce the bug on the Gitea demo site?
Log Gist
No response
Screenshots
Git Version
No response
Operating System
Debian > Docker > Gitea
How are you running Gitea?
gitea/gitea:latest as of the time of opening this issue
Database
MySQL
The text was updated successfully, but these errors were encountered: