We received email that three of our addons were not marked as 5.0 compatible. When I then went to check them and tried to download them, all three of them came up as 404s.
I suspect they've ended up in guarded-addons. -> jbalogh to investigate and fix
For the record, in the emails we got about these not being Firefox 5 compatible, we received links that didn't work as well:
We can't be the only people this happened to.
Any updates on this? These are two of our most popular addons.
2 : from addons.models import Addon
3 : a = Addon.objects.get(id=11160)
4 : a.current_version.all_files
5 : a.current_version
6 : f = a.current_version.all_files
7 : f.unhide_disabled_file()
8 : f.copy_to_mirror()
9 : a = Addon.objects.get(id=13703)
11: f = a.current_version.all_files
14: a = Addon.objects.get(id=12518)
15: f = a.current_version.all_files
18: _ip.magic("hist ")
OK, they're back.
So, why did they disappear?
And why can't I view the validation results from the 4.0->5.0 thing?
I still don't see any answers to my question.
And this comment:
> Files are getting stuck in /guarded-addons for some reason
Did these files get stuck in guarded because of the 4.0->5.0 version bump?
Why don't the validation links work?
Why are you working around the problem instead of figuring out why it broke?
We've been seeing add-ons stuck in /guarded-addons for the past few weeks. We haven't determined a cause or a pattern but it doesn't have to do with the 4.0->5.0 version bump.
If the validator wasn't expecting to find your add-ons in /guarded-addons when it ran, the links will be broken.
The patch above fixes the problem and adds additional logging so we can determine what is causing it. As I mentioned, we haven't seen a pattern yet.
Thanks for the fix, jbalogh.
Interesting. So it was a chicken and egg problem.
I thought they were not available because of the version bump.
But it turns out they failed to get the version bump because they weren't available.
Thanks for the explanation.