Repository URLs are slug-based. The API is currently the only endpoint that I'm aware of that is ID-based. I've actually had the internal server error a couple of times, but subsequent pushes did what was expected. Not ideal, and something the devs need to work on, but not world-ending. If this isn't your experience, please report.
A few days passed and it is still 500. I managed to push version BEFORE original post in this thread, so I think it is not something tied to local data.
So I was able to push a few successful changes after the migration using hg (so I know it has worked before), but today all I'm getting are these same 500 errors. No changes to the settings on my end. :(
if it's a critical fix for your addon(s), i suggest you try to package the zip file yourself and upload that zip to curseforge... maybe that works until they fix things.
take time to verify that the zip file that ends up published is what you intend to publish though because after the migration curseforge is altering uploaded zip files before publishing them. (hopefully they will disable this new behaviour sometime soon)
Updating to HG 4.0 doesn't help either - but that's expected, since no matter what the version of client, HTTP API should never answer 500 if it is working correctly.
I've got mercurial version 3.7.3 running. I'm trying to push 4 commits to the remote. The commit changes include adding one new sub-folder and file, renaming (moving) a few existing files, and a few edits on existing files.
This is the repo:
https://repos.curseforge.com/wow/prospect-me
the specific error is
hg push --new-branch default
pushing to https://repos.curseforge.com/wow/prospect-me/
searching for changes
abort: HTTP Error 500: Internal Server Error
Completed with errors, see above
try using project id (numerical) instead of project name.. i think there might currently be a bug with the names
garrison-mission-manager = 86844
(on https://mods.curse.com/addons/wow/garrison-mission-manager look at the "project site" URL to see the numerical id)
Repository URLs are slug-based. The API is currently the only endpoint that I'm aware of that is ID-based. I've actually had the internal server error a couple of times, but subsequent pushes did what was expected. Not ideal, and something the devs need to work on, but not world-ending. If this isn't your experience, please report.
Well, I've tried pushing about dozen times before posting this it is 500 all the time. Can you please check push to this particular project in logs?
A few days passed and it is still 500. I managed to push version BEFORE original post in this thread, so I think it is not something tied to local data.
So I was able to push a few successful changes after the migration using hg (so I know it has worked before), but today all I'm getting are these same 500 errors. No changes to the settings on my end. :(
Still 500. Any news on that?
if it's a critical fix for your addon(s), i suggest you try to package the zip file yourself and upload that zip to curseforge... maybe that works until they fix things.
take time to verify that the zip file that ends up published is what you intend to publish though because after the migration curseforge is altering uploaded zip files before publishing them. (hopefully they will disable this new behaviour sometime soon)
It's not critical for me, just inconvenient.
Still happening today :(
Thanks for the report guys, the devs are looking into this!
We cannot seem to replicate this inhouse, can you give us some more details?
What exactly are you trying to push with this push? What version of HG are you using? Any other info that would help us replicate.
Thanks!
HG version 3.5.2, tried both command line and thg GUI (kinda pointless, since it just calls command line under the hood).
Updating to HG 4.0 doesn't help either - but that's expected, since no matter what the version of client, HTTP API should never answer 500 if it is working correctly.
Sorry, I should have been more clear, what data are you pushing? Small changes, massive changes, new files, ect ect
I've got mercurial version 3.7.3 running. I'm trying to push 4 commits to the remote. The commit changes include adding one new sub-folder and file, renaming (moving) a few existing files, and a few edits on existing files.
This is the repo:
the specific error is
Thought I'd add, repos.curseforge.com resolves to 104.16.41.248 for me using google's DNS servers.
7 commits, 3 files modified, no new files.
Thanks guys, it seems to be an issue with the box or HG. We have a ticket in with IT to take a look at it :)
@ZeldoKavira Still getting 500 errors today... Is there any sort of public bug tracker we can follow tickets on?