mission_control-jobs 0.1.0 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 63e12a3c6650d55dd75e269ca604320316a5400c6e7b9429b16a05de167717a7
-  data.tar.gz: 617b2ea6236f481ed4ee6b6c22e5b72570b75d9e2bcf69e0cf60ba18eec69e06
+  metadata.gz: 3c261d6b55b908312495212d5f925b3b4150f59a895b185a5667ce0b9754f9f6
+  data.tar.gz: db330e0f62f17e8b3e46f63233b8f7fffe5a126f746b7d83bc3afa94c9e07664
 SHA512:
-  metadata.gz: 91a3206ed4772d01f441d7fe6ed10b0e8dc27beb6828333b3805ad65cc314d13157c9a6e2d07f0bed46f09f911549d28250244f320a9dc637883135e5c10f627
-  data.tar.gz: c6f173db8d4d4be438b91ad8925d381f5eb44aabda18fcd9f4b174f91bf80922c779ca7eb71132046c952b496c379209c29c7da1aec94f667f01365a51b79c3a
+  metadata.gz: 670df5d56e857f5f9b230c884447738763379c803be0014933016554277463bcaf9aa74c0e52289cf3c54783f74ed16fc13338637e8d78b70b1bfd82ffa7849c
+  data.tar.gz: cad6605c7296b828d1078ef09def60152267dc3d07196481a51f1b5f49cec70b5a0b0b9b8fcc1add4739d28bf8ad6b38c7a62197111c0c047a5771ce1504cc4a

data/README.md

@@ -1,6 +1,6 @@
 # Mission Control — Jobs
 
-This gem provides a Rails-based frontend to Active Job adapters. It currently supports [Resque](https://github.com/resque/resque/) and [Solid Queue](https://github.com/basecamp/solid_queue). Its features depend on those offered by the adapter itself, but at a minimum, it allows you to inspect job queues, jobs currently waiting in those queues, and inspecting and retrying or discarding failed jobs.
+This gem provides a Rails-based frontend to Active Job adapters. It currently supports [Resque](https://github.com/resque/resque/) and [Solid Queue](https://github.com/basecamp/solid_queue). Its features depend on those offered by the adapter itself. At a minimum, it allows you to inspect job queues and jobs currently waiting in those queues and inspect and retry or discard failed jobs.
 
 ## Installation
 Add this line to your application's Gemfile:
@@ -55,12 +55,12 @@ Besides `base_controller_class`, you can also set the following for `MissionCont
 - `delay_between_bulk_operation_batches`: how long to wait between batches when performing bulk operations, such as _discard all_ or _retry all_ jobs—defaults to `0`
 - `adapters`: a list of adapters that you want Mission Control to use and extend. By default this will be the adapter you have set for `active_job.queue_adapter`.
 
-This library extends Active Job with a querying interface, and the following setting:
+This library extends Active Job with a querying interface and the following setting:
 - `config.active_job.default_page_size`: the internal batch size that Active Job will use when sending queries to the underlying adapter and the batch size for the bulk operations defined above—defaults to `1000`.
 
 ## Advanced configuration
 
-When we built Mission Control Jobs, we did it with the idea of managing multiple apps' job backends from a single, centralized app that we used for monitoring, alerts and other tools that related to all our apps. Some of our apps run in more than one datacenter and we run different Resque instances with different Redis configurations in each. Because of this, we added support for multiple apps and multiple adapters per app. Even when running Mission Control Job within the app it manages and a single DC, as we migrated from Resque to Solid Queue, we needed to manage both adapters from Mission Control.
+When we built Mission Control Jobs, we did it with the idea of managing multiple apps' job backends from a single, centralized app that we used for monitoring, alerts and other tools that related to all our apps. Some of our apps run in more than one datacenter, and we run different Resque instances with different Redis configurations in each. Because of this, we added support for multiple apps and multiple adapters per app. Even when running Mission Control Job within the app it manages, and a single DC, as we migrated from Resque to Solid Queue, we needed to manage both adapters from Mission Control.
 
 Without adding any additional configuration to [the one described before](#basic-configuration), Mission Control will be configured with one single app and a single server for your configured `active_job.queue_adapter`.
 
@@ -105,9 +105,9 @@ SERVERS_BY_APP.each do |app, servers|
 end
 ```
 
-This is an example for two different apps, BC4 and HEY, each one with two servers. BC4 has two Resque servers with two different configurations and HEY has one Resque server and one Solid Queue server.
+This is an example for two different apps, BC4 and HEY, each one with two servers. BC4 has two Resque servers with two different configurations, and HEY has one Resque server and one Solid Queue server.
 
-Currently only one Solid Queue configuration is supported, but support for several Solid Queue backends (with different databases) [is planned](https://github.com/basecamp/mission_control-jobs/issues/35).
+Currently, only one Solid Queue configuration is supported, but support for several Solid Queue backends (with different databases) [is planned](https://github.com/basecamp/mission_control-jobs/issues/35).
 
 This is how we set Resque and Solid Queue together when we migrated from one to the other:
 
@@ -141,9 +141,9 @@ As mentioned, the features available in Mission Control depend on the adapter yo
 
 ## Console helpers, scripting and dealing with big sets of jobs
 
-Besides the UI, Mission Control provides a light console helper to switch between applications and adapters. Some potentially destructive actions aren't exposed via the UI (for example, discarding jobs that aren't failed, although this might change in the future) but you can always perform these from the console if you know very well what you're doing.
+Besides the UI, Mission Control provides a light console helper to switch between applications and adapters. Some potentially destructive actions aren't exposed via the UI (for example, discarding jobs that aren't failed, although this might change in the future), but you can always perform these from the console if you know very well what you're doing.
 
-It's also possible that you need to deal with very big sets of jobs that are unmanageable via the UI, or that you wish to write a script to deal with an incident, some cleanup or some data migration. The console helpers and the querying API with which we've extended Active Job come handy here.
+It's also possible that you need to deal with very big sets of jobs that are unmanageable via the UI or that you wish to write a script to deal with an incident, some cleanup or some data migration. The console helpers and the querying API with which we've extended Active Job come in handy here.
 
 First, when connecting to the Rails console, you'll see this new message:
 
@@ -193,7 +193,7 @@ ActiveJob.jobs.failed.where(job_class: "SomeJob")
 # All pending jobs of a given class with limit and offset
 ActiveJob.jobs.pending.where(job_class: "SomeJob").limit(10).offset(5)
 
-# For adpaters that support these statuses:
+# For adapters that support these statuses:
 # All scheduled/in-progress/finished jobs of a given class
 ActiveJob.jobs.scheudled.where(job_class: "SomeJob")
 ActiveJob.jobs.in_progress.where(job_class: "SomeJob")
@@ -229,7 +229,7 @@ MissionControl::Jobs.delay_between_bulk_operation_batches = 5.seconds
 
 ## Contributing
 
-Thanks for your interest in contributing! To get the app running locally just run:
+Thanks for your interest in contributing! To get the app running locally, just run:
 ```
 bin/setup
 ```

data/app/controllers/concerns/mission_control/jobs/job_scoped.rb

@@ -2,7 +2,7 @@ module MissionControl::Jobs::JobScoped
   extend ActiveSupport::Concern
 
   included do
-    before_action :set_job, except: :index
+    before_action :set_job
   end
 
   private

data/app/controllers/mission_control/jobs/jobs_controller.rb

@@ -1,6 +1,8 @@
 class MissionControl::Jobs::JobsController < MissionControl::Jobs::ApplicationController
   include MissionControl::Jobs::JobScoped, MissionControl::Jobs::JobFilters
 
+  skip_before_action :set_job, only: :index
+
   def index
     @job_class_names = jobs_with_status.job_class_names
     @queue_names = ApplicationJob.queues.map(&:name)

data/lib/mission_control/jobs/version.rb

@@ -1,5 +1,5 @@
 module MissionControl
   module Jobs
-    VERSION = "0.1.0"
+    VERSION = "0.1.1"
   end
 end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: mission_control-jobs
 version: !ruby/object:Gem::Version
-  version: 0.1.0
+  version: 0.1.1
 platform: ruby
 authors:
 - Jorge Manrubia
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2024-01-30 00:00:00.000000000 Z
+date: 2024-01-31 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rails