Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
Has there been any progress with this? I'm still having issues with packaging on mercurial with tags and this has been going on a while... :(
Even the "package all commits" workaround doesn't seem to work 100% of the time - the system doesn't seem to properly parse the tag to determine alpha/beta/release status.
I tried tagging and pushing a new file [that still doesn't seem to be working right with Mercurial BTW :(] and then ended up uploading a new file and the "Abandoned" flag still hasn't been removed.
This is still not working on the addon I originally posted about (https://wow.curseforge.com/projects/whistle-master/). My other addons seem to be working correctly with the tagging and packaging, but this one continues to be an issue. :(
Thought I would add since I didn't in my original post, I'm using Mercurial on this addon (and all of my addons). Sounds like it's more an issue with the packager and less with the versioning system since it sounds like Proteyer and arith are both using SVN.
I'm having the same issue with a different addon/repo.
The Dashboard shows a build was made when the changes were pushed, but packaged files never made it to the site. Browsing the repo correctly shows the tag("v0.7.1.2-Beta").
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
0
FYI; this seems to be fixed now. Yay!
I tagged and pushed updates for WoW client v 7.2 today and they worked across all 4 addons I manage using Mercurial.
0
Has there been any progress with this? I'm still having issues with packaging on mercurial with tags and this has been going on a while... :(
Even the "package all commits" workaround doesn't seem to work 100% of the time - the system doesn't seem to properly parse the tag to determine alpha/beta/release status.
0
Thanks for the info on the workaround. Was just coming to check on this since I was still having issues.
Switching from Hg to Git isn't something I'm ready to consider yet, but the workaround is doable. ;)
0
Awesome, thanks :)
0
Torhal, can you fix one of my old projects too?
I tried tagging and pushing a new file [that still doesn't seem to be working right with Mercurial BTW :(] and then ended up uploading a new file and the "Abandoned" flag still hasn't been removed.
https://wow.curseforge.com/projects/light-speed
0
@Torhal, any updates on this? :(
0
This is still not working on the addon I originally posted about (https://wow.curseforge.com/projects/whistle-master/). My other addons seem to be working correctly with the tagging and packaging, but this one continues to be an issue. :(
0
Thought I would add since I didn't in my original post, I'm using Mercurial on this addon (and all of my addons). Sounds like it's more an issue with the packager and less with the versioning system since it sounds like Proteyer and arith are both using SVN.
0
I'm having the same issue with a different addon/repo.
The Dashboard shows a build was made when the changes were pushed, but packaged files never made it to the site. Browsing the repo correctly shows the tag("v0.7.1.2-Beta").
https://repos.curseforge.com/wow/whistle-master
0
Looks like it's working for me now. Only made one attempt and it went through. Huzzah!
Will report back in it starts acting up again, but hopefully thus ends the saga of the misbehaving mercurial repository :)
0
Thanks for checking in on it!
0
@ZeldoKavira Still getting 500 errors today... Is there any sort of public bug tracker we can follow tickets on?
0
0
Thought I'd add, repos.curseforge.com resolves to 104.16.41.248 for me using google's DNS servers.
0
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