-
Notifications
You must be signed in to change notification settings - Fork 662
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
elm publish - tried to fetch https://package.elm-lang.org... "But it came back as 413 Request Entity Too Large" #2299
Comments
Thanks for reporting this! To set expectations:
Finally, please be patient with the core team. They are trying their best with limited resources. |
I don't think it will work but maybe you can get more information by trying to publish with elm 0.19.0? At least that works for some projects with some sort of package json parsing error - though that seems to be unrelated to your issue |
Sadly it didn't work. The error was a little different but not much more useful:
|
maybe too much in your repo? elm-stuff folder is checked in, or something like that? |
Nothing like that checked in. I've now tried removing all extraneous codegen and npm stuff, leaving only the barebones elm. Still it fails with the same message. The full repo is 4.2mb. Is it not possible to publish a library of this size? |
@nunntom You might want to try increasing the git http post buffer size, as this failure seems to be happening when the CLI posts the automatic version commit to your repo: git config --global http.postBuffer 1048576000 This, then downgrading to 0.19.0 worked for me. |
@rektdeckard Thanks for the suggestion, sadly this didn't work in my case. :( |
Update. By checking the source of elm publish I found out that it sends a POST request to the package server with a payload containing among other things the docs.json. I stripped out all the doc comments from most of the functions and now with elm 19.0.0 I get this message which is a little more helpful:
Compare this with the less helpful message on 0.19.1
It would probably be more useful to stick to at least passing through the error message from the package server. I'll report this on the package server repo. |
I just tried to publish a shiny new package and got this error:
SSCCE
What do I need to do to get this package published?
The text was updated successfully, but these errors were encountered: