bullmq-dash 0.3.0 → 0.3.2

package/README.md

@@ -7,10 +7,11 @@ Terminal UI dashboard for [BullMQ](https://bullmq.io/)
 ## Features
 
 - **Real-time monitoring** - Watch queues and jobs update live with configurable polling
-- **Queue overview** - View all BullMQ queues with job counts and status
+- **Queue overview** - View all BullMQ queues with job counts, failure counts, and task-size sorting
 - **Job inspection** - Browse jobs by status, view details, data, and error stacktraces
+- **Failed-job recovery** - Find failed jobs quickly and retry one job by ID or a filtered batch
 - **Scheduler monitoring** - View Job Schedulers (repeatable jobs) with patterns, iterations, and job history
-- **Job management** - Add, cancel, delete, and retry jobs directly from the dashboard
+- **Job management** - Delete jobs from the TUI and retry failed jobs from headless mode
 - **Global metrics** - Track enqueue/dequeue rates across all queues
 
 ## Requirements
@@ -85,6 +86,29 @@ bullmq-dash --tui --redis-url <redis-url> --queues email,notifications,payments
 bullmq-dash --tui --redis-url <redis-url> --poll-interval 5000
 ```
 
+### Headless Queue Operations
+
+Headless commands print JSON by default, so they are safe to pipe through `jq`
+or run from automation.
+
+```bash
+# Rank queues by task size, largest first
+bullmq-dash queues list --redis-url <redis-url> --sort-by task-size
+
+# Rank queues by failed jobs
+bullmq-dash queues list --redis-url <redis-url> --sort-by failed
+
+# Find failed jobs in a queue
+bullmq-dash jobs failed email --redis-url <redis-url>
+
+# Preview retrying one failed job, then run it
+bullmq-dash jobs retry email --redis-url <redis-url> --job-id 42 --dry-run
+bullmq-dash jobs retry email --redis-url <redis-url> --job-id 42 --yes
+
+# Preview a filtered batch retry
+bullmq-dash jobs retry email --redis-url <redis-url> --job-state failed --since 1h --dry-run
+```
+
 ## Connection Profiles
 
 Save Redis connections as named profiles so you don't have to remember (or paste)
@@ -98,14 +122,15 @@ and reference it with `--profile`:
     "local": { "redis": { "url": "<local-redis-url>" } },
     "prod": {
       "redis": { "url": "${REDIS_PROD_URL}" },
-      "queues": ["payments", "notifications"]
+      "queues": ["payments", "notifications"],
+      "cacheTtlMs": 86400000
     },
     "upstash": { "redis": { "url": "${REDIS_URL}" } }
   }
 }
 ```
 
-Each profile carries a single `redis.url`. The `${VAR}` form interpolates an environment variable as the **whole value** (partial substitution is intentionally not supported), which pairs nicely with managed providers (Upstash, Heroku Redis, Render, Railway, Fly) that hand you a single `REDIS_URL` env var. Prefer environment-backed profile values for authenticated Redis URLs.
+Each profile carries a single `redis.url`. `cacheTtlMs` controls the SQLite observation-cache TTL and defaults to 24 hours. The `${VAR}` form interpolates an environment variable as the **whole value** (partial substitution is intentionally not supported), which pairs nicely with managed providers (Upstash, Heroku Redis, Render, Railway, Fly) that hand you a single `REDIS_URL` env var. Prefer environment-backed profile values for authenticated Redis URLs.
 
 ```bash
 # Connect using the default profile (defaultProfile field above)
@@ -155,6 +180,7 @@ without auth — keep passwords out of the file itself.
 | `Enter`        | View job details    |
 | `d`            | Delete selected job |
 | `r`            | Refresh data        |
+| `s`            | Cycle queue sorting |
 | `q` / `Ctrl+C` | Quit                |
 
 ### Job Status Filter
@@ -225,7 +251,7 @@ bun run start
 # Audit the immutable 0.2.7 Socket target (historical evidence)
 bun run security:audit-0.2.7
 
-# Score the configured package version after it is published
+# Optional manual Socket score for an already-published version
 bun run security:score
 
 # Verify forbidden local-only files are ignored and not tracked
@@ -234,7 +260,7 @@ bun run security:verify-source-control
 # Verify Bun package manager pinning, bun.lock tracking, and frozen installs
 bun run security:verify-lockfile
 
-# Verify CI/publish workflows pin actions, lock down releases, and score after publish
+# Verify CI/publish workflows pin actions and lock down releases
 bun run security:verify-workflows
 
 # Verify source import policy, npm tarball contents, and stripped publish manifest
@@ -260,26 +286,19 @@ or gitleaks), enforces packed-tarball size and entry-count limits, and
 verifies the stripped publish manifest. Note: `ioredis` remains a transitive
 dependency through `bullmq`; the policy blocks _direct_ imports only.
 
-`bun run security:score` runs the Socket package score against the version in
-`package.json` (must already be published to npm). It compares the alert set
-against an accepted-alert allowlist that includes the capabilities a Redis
-monitoring tool legitimately needs (`networkAccess`, `urlStrings`,
-`filesystemAccess`, `envVars`), Socket's transient `recentlyPublished` window,
-and the transitive alert types present in the `bullmq` and `@opentui/core`
-graphs. The gate exits nonzero only when an alert type appears outside that set,
-which surfaces real regressions from dependency updates without paging on every
-publish.
+`bun run security:score` is an optional manual audit for a version that already
+exists on npm. It compares the Socket alert set against the accepted-alert
+allowlist, but it is intentionally not part of the publish workflow because
+Socket scoring can lag or fail after npm accepts the immutable package version.
 
 `bun run security:verify-workflows` rejects mutable GitHub Action refs,
 `pull_request_target` triggers, and direct `${{ github.event.* }}` interpolation
 in workflow commands. It also verifies CI and publish workflows run the
 source-control, lockfile, workflow, and package policy verifiers, CI uses
-read-only permissions, and the npm publish workflow scopes secrets to approved
-step env entries, is release-only, runs the source-control, lockfile, workflow,
-and package verifiers before publishing, uses least privilege, keeps npm
-lifecycle scripts enabled, publishes with provenance, installs the Socket CLI by
-the configured exact version `1.1.94`, and runs the post-publish Socket score
-gate.
+read-only permissions, and the npm publish workflow rejects publish secrets,
+is release-only, runs the source-control, lockfile, workflow, and package
+verifiers before publishing, uses least privilege, keeps npm lifecycle scripts
+enabled, and publishes with provenance.
 
 `bun run security:verify-source-control` rejects tracked `.env` / `.envrc` /
 `.npmrc` files, build output, publish manifest backups, and generated package