mastodon/app/workers
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
..
admin
pubsubhubbub
scheduler
after_remote_follow_request_worker.rb
after_remote_follow_worker.rb
application_worker.rb
block_worker.rb
digest_mailer_worker.rb
distribution_worker.rb
domain_block_worker.rb
feed_insert_worker.rb
import_worker.rb
link_crawl_worker.rb
merge_worker.rb
notification_worker.rb
processing_worker.rb
push_update_worker.rb
regeneration_worker.rb
remote_profile_update_worker.rb
removal_worker.rb
salmon_worker.rb
soft_block_domain_followers_worker.rb
soft_block_worker.rb
thread_resolve_worker.rb
unfavourite_worker.rb
unmerge_worker.rb