Authors CurseForge

Same here. There is no way to resolve this without the aid of a moderator, then? (as it doesn't let me use the same tag name again)

Thanks!

I've noticed that when I have this problem, that if I delete the tag that I pushed and re-tag, it'll get re-noticed by the packager and placed into its queue again.

It's not guaranteed to get packaged the second time either, but at least it gives me a chance to force the packager to run again without needing to hassle a moderator.

Quote from Torhal

We've been having intermittent problems with the task worker that starts the packager since our server migration this past Thursday. I'm hoping it will be resolved later this morning (Tuesday). Either way, once the task worker is restarted, the packager will continue to work on the projects in its queue - your project will be packaged.

I cannot overstate how much the packager downtimes are interfering with my ability to develop addon content. It seems like it's been down several times a day for the past two weeks or so, and on at least 5 separate occasions it has directly hampered my ability to push updates and test code to users, often for multiple hour stretches. The fact these problems also coincided with a major client patch has magnified the problem enormously.

I understand this issue is out of Torhal's direct control, but this is a major problem for addon devs that really needs to be fixed ASAP. Who should we be bothering about this? What can we do to expedite this?

Yeah, I'd have say a major patch release is a pretty awful time to do a server migration.

Practically speaking, though, you can always have your project pages transferred from the wowace.com domain to the curseforge.com domain so you can manually upload ZIP files; it will have absolutely no other effect on your project.

Please kick the packager thread to create a new beta release for Ovale, which was recently tagged for "5.4.9alpha2". It didn't seem to get picked up like it normally does after getting tagged in the SVN repository.

Thread Tools > Subscribe to this Thread > Instant email notification ;)

Looking at http://www.wowace.com/packager/, it seems like the packager is stuck in an infinite loop getting Assertion errors at the moment.