flight_control 2.0.0.beta.1 → 2.0.0.beta.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1ad093eeb61f357dc4aead0c094eb413607dfa234cd7cdf4ed15579a0fa0af51
-  data.tar.gz: a7774ba9273438d984569b4f739795019caaea77d1f1e42b033cd862e0af9231
+  metadata.gz: 92136b24112b7e322f86dce0e4bdcfa22e2ebdac86edd8bcecb52f25504ba107
+  data.tar.gz: 9c6461eca4e2f2124fd04c6bfe49d11c3a643c0d6cf84c946f86b64f62df5abd
 SHA512:
-  metadata.gz: 9ce93746fa317b44831c7fa4d12bca2590d25a76f4eeb375041df08895f326d1e8c25a414d10da06638b0c072c933c84bdbbe338bbf27a04dd77d0e93e8c9324
-  data.tar.gz: 986514c76126354436fe67b584289a17cf864314f126c9f7c159f1207e48c7dd3816860b82fde3115cc04ecde18e7e483528ae3b93a7d3f8127c2264f89053c5
+  metadata.gz: 60039b2a8752a3a0cad44eb15e3bfa11a3a15698c3c235e5e4357843663dd51775e5cadfb798d302a5ff9f298b362b7d7a8745696f207e57db5f68dd6c680355
+  data.tar.gz: 85d145d60c4fca2432cddba0703e93db012cc7db50a14790ae0c5f619daf833070fef642c6181dd12243c920901d0bb2f3815ea2221b47247ec7033d8654d9d5

data/CHANGELOG.md

@@ -2,7 +2,32 @@
 
 ## [Unreleased]
 
-## [2.0.0] - 2026-07-20
+## [2.0.0.beta.3] - 2026-09-09
+
+- Adds back `app/` and `config/` directories to the packaged gem.
+
+## [2.0.0.beta.2] - 2026-09-08
+
+Ported from mission_control-jobs (upstream 1.1.0...1.2.0 and later):
+
+- Adds `enqueued_at` and `scheduled_at` date-range filters, applied natively by Solid Queue.
+- Adds a `back_to_main_app_path` setting to point the "Back to main app" link somewhere other than the host's root.
+- Routes host-app route helpers used inside the engine through `main_app`, so a base controller redirecting to, say, `new_session_path` keeps working.
+- Loads the engine's stylesheets individually so they also work under Propshaft.
+- Shows the total of pending jobs on the queues page, and how many times a job has been retried.
+- Truncates long job arguments in job lists.
+- Orders failed jobs by when they failed rather than by job id.
+- Submits the job filters on `change` instead of debouncing keystrokes.
+- Swaps only the backtrace when toggling between clean and full.
+- Disables Turbo's prefetching of links on hover.
+- Redirects to the queues index when showing a queue that no longer exists.
+- Shows the raw error when a failed execution's error can't be parsed.
+- Fixes `config.active_job.default_page_size` not being applied.
+- Fixes the "Expires" tooltip of blocked jobs rendering its markup as text.
+- Fixes `JobProxy#duration` when `scheduled_at` isn't set.
+- Avoids N+1 count queries when listing Solid Queue queues.
+
+## [2.0.0.beta.1] - 2026-07-20
 
 - Drops support for Resque and Async adapters to focus on Solid Queue.
 - Drops support for Rails versions below 8.1.

data/README.md

@@ -107,6 +107,23 @@ If you do this, you can disable the default HTTP Basic Authentication using the
 config.flight_control.http_basic_auth_enabled = false
 ```
 
+Your base controller's code runs inside the engine, whose route helpers take precedence. Route helpers of your app that Flight Control doesn't define itself, like `new_session_path` from Rails' authentication generator, still work as they are, for example from a `before_action` that redirects to the login page. Helpers that both your app and Flight Control define, like `root_path`, resolve to Flight Control's; use `main_app.root_path` to reach your app's.
+
+#### Authentication via route constraints
+
+You can also keep authentication out of Flight Control's controllers altogether and restrict access when mounting the engine, using [route constraints](https://guides.rubyonrails.org/routing.html#advanced-constraints). For example, with the sessions created by Rails' authentication generator:
+
+```ruby
+# config/routes.rb
+Rails.application.routes.draw do
+  constraints ->(request) { Session.find_by(id: request.cookie_jar.signed[:session_id])&.user&.admin? } do
+    mount FlightControl::Engine, at: "/jobs"
+  end
+end
+```
+
+Requests that don't satisfy the constraint never reach the engine. As with a custom base controller, disable HTTP Basic Authentication if you don't want both.
+
 ### Other configuration settings
 
 Besides `base_controller_class`, you can also set the following for `FlightControl` or `config.flight_control`:
@@ -116,6 +133,7 @@ Besides `base_controller_class`, you can also set the following for `FlightContr
 - `internal_query_count_limit`: in count queries, the maximum number of records that will be counted if the adapter needs to limit these queries. True counts above this number will be returned as `INFINITY`. This keeps count queries fast—defaults to `500,000`
 - `scheduled_job_delay_threshold`: the time duration before a scheduled job is considered delayed. Defaults to `1.minute` (a job is considered delayed if it hasn't transitioned from the `scheduled` status 1 minute after the scheduled time).
 - `show_console_help`: whether to show the console help. If you don't want the console help message, set this to `false`—defaults to `true`.
+- `back_to_main_app_path`: an optional string path for the "Back to main app" link. Example: `'/admin'`. Defaults to the host app's `root_path` when available.
 - `backtrace_cleaner`: a backtrace cleaner used for optionally filtering backtraces on the Failed Jobs detail page. Defaults to `Rails::BacktraceCleaner.new`. See the [Advanced configuration](#advanced-configuration) section for how to configure/override this setting on a per application/server basis.
 - `filter_arguments`: an array of strings representing the job argument keys you want to filter out in the UI. This is useful for hiding sensitive user data. Currently, only root-level hash keys are supported.
 
@@ -223,6 +241,11 @@ ActiveJob.jobs.finished.where(job_class_name: "SomeJob")
 
 # All jobs in progress being run by a given worker
 ActiveJob.jobs.in_progress.where(worker_id: 42)
+
+# Filtering by dates takes a range, which can be open on either end
+ActiveJob.jobs.failed.where(enqueued_at: 2.days.ago..)
+ActiveJob.jobs.scheduled.where(scheduled_at: Time.now..1.hour.from_now)
+ActiveJob.jobs.finished.where(finished_at: ..1.week.ago)
 ```
 
 Some examples of bulk operations:

data/app/assets/config/flight_control_manifest.js

@@ -0,0 +1,3 @@
+//= link_directory ../stylesheets/flight_control .css
+//= link_directory ../../javascript/flight_control .js
+//= link_directory ../../javascript/flight_control/controllers .js

data/app/assets/stylesheets/flight_control/application.css

@@ -0,0 +1,5 @@
+/*
+ * Application-wide styles. The engine's stylesheets are linked individually from the layout,
+ * so that they load regardless of the host app's asset pipeline: Propshaft serves files as
+ * they are, without processing Sprockets directives.
+ */