9 Commits (b534249a8dc68e8a0eea028d90a1ad81e9c06baa)

Author	SHA1	Message	Date
ThibG	10f6793fd0	Fix PuSH workers (#6200)	2018-01-05 23:04:35 +01:00
Daigo 3 Dango	a0bbeafb04	Suppress backtrace when failed to communicate with a remote instance (#5076)	2017-09-24 11:14:06 +02:00
abcang	1aad015bbb	Revert unique retry job (#4937) ... * Revert "Enable UniqueRetryJobMiddleware even when called from sidekiq worker (#4836)" This reverts commit 6859d4c028. * Revert "Do not execute the job with the same arguments as the retry job (#4814)" This reverts commit be7ffa2d75.	2017-09-14 15:12:43 +02:00
abcang	be7ffa2d75	Do not execute the job with the same arguments as the retry job (#4814)	2017-09-05 20:56:20 +02:00
Eugen Rochko	6e186b9c77	When PuSH subscribe attempts are exhausted, unsubscribe (#4422)	2017-07-28 17:21:14 +02:00
Clworld	994d948c39	Add callback_url/acct information for Sidekiq PuSH workers Exception. (#4281) ... * Add destination informations to exception on SubscribeWorker and DeliveryWorker. * Simplify delivery error message. * Prevent changing Exception type... * fix typo.	2017-07-27 00:38:20 +02:00
Eugen Rochko	34ccc058fa	Limit total subscribe retries to 10, but space them out more (#4142) ... Since there is little point in retrying so often when a service is down or does not exist anymore. Subscriptions are renewed 1 day before they should expire, so retrying in 30 minutes, then 2 hours, then 12 hours is fine. If even after that, the remote server does not work, there is little sense in retrying more often than once a day Also, uniqueness of the job should ensure that failed retries will not result in multiple retries for the same endpoint when the next resubscription cycle comes	2017-07-10 18:04:23 +02:00
Eugen Rochko	b8e166894b	Fix Scheduler::SubscriptionsScheduler (#2834) ... * Fix Scheduler::SubscriptionsScheduler, add worker test for it * Change production log level of Sidekiq to "warn" instead of "info"	2017-05-06 13:05:03 +02:00
Eugen Rochko	81584779cb	More robust PuSH subscription refreshes (#2799) ... * 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	2017-05-05 02:23:01 +02:00