Mathieu Pillard

@dependabot rebase

@dependabot rebase

Weird that it would happen on stage - can't be related to fastly if that's the case - need to investigate.

@ioanarusiczki If you are testing from a third party service like https://httpie.io/app that would explain the problem: there is no guarantee they'd be using the same IP for all requests....

We chatted about this and discovered it was caused by `extensions.addonAbuseReport.url` not being set correctly. Digging further though: - On dev, throttling does seem broken atm specifically for [services.addons-dev.allizom.org](http://services.addons-dev.allizom.org/) requests...

With https://github.com/mozilla/addons/issues/14929 fixing the first item from my comment above we should be ok now.

For visibility: QA also filed https://github.com/mozilla/addons/issues/14905 We think both are low priority for the moment. We can revisit when this goes live.

This is annoying but not a deal-breaker. Worst case scenario it's on the reviewer not to select ignoring actions for resolving appeals.

Can you attach the full zip of your add-on, and tell us the approximate date & time of the last time you tried uploading it ?

I suspect the problem is the huge number of files - could you submit a version that only includes the bundle, omitting `node_modules` etc, and submit the source code zip...