* Fix#2473 - Use sidekiq scheduler to refresh PuSH subscriptions instead of cron
Fix an issue where / in domain would raise exception in TagManager#normalize_domain
PuSH subscriptions refresh done in a round-robin way to avoid hammering a single
server's hub in sequence. Correct handling of failures/retries through Sidekiq (see
also #2613). Optimize Account#with_followers scope. Also, since subscriptions
are now delegated to Sidekiq jobs, an uncaught exception will not stop the entire
refreshing operation halfway through
Fix#2702 - Correct user agent header on outgoing http requests
* Add test for SubscribeService
* Extract #expiring_accounts into method
* Make mastodon:push:refresh no-op
* Queues are now defined in sidekiq.yml
* Queues are now in sidekiq.yml
@ -25,8 +25,8 @@ class Pubsubhubbub::DeliveryWorker
.headers(headers)
.post(subscription.callback_url,body:payload)
returnsubscription.destroy!ifresponse.code>299&&response.code<500&&response.code!=429# HTTP 4xx means error is not temporary, except for 429 (throttling)
raise"Delivery failed for #{subscription.callback_url}: HTTP #{response.code}"unlessresponse.code>199&&response.code<300
returnsubscription.destroy!ifresponse_failed_permanently?(response)# HTTP 4xx means error is not temporary, except for 429 (throttling)
raise"Delivery failed for #{subscription.callback_url}: HTTP #{response.code}"unlessresponse_successful?(response)
subscription.touch(:last_successful_delivery_at)
end
@ -37,4 +37,12 @@ class Pubsubhubbub::DeliveryWorker