wurk 1.7.2 → 1.7.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d535340ce300b6e688dbeed5657583ebd3c5795363b9737482a801b666bb8643
-  data.tar.gz: 805d1e4aa47fb526d3c6660c160a6c87a9de399070518a545d8d2f12a321920e
+  metadata.gz: 33b583b405b2f2cf26f62fea6c6551d0f6900c3d72879ec6968dd7c82c976f26
+  data.tar.gz: fe626c58ce7bd322765cd0df1f9655097647ab2fdcd5b9aa4200012d9dc09825
 SHA512:
-  metadata.gz: 551f19e3fc8f8008724d92d2851d4856af46b9fd7a7089f72d250439f03ff48107e5a5f327b0f279e728a8d9011bf70237a26b5f6355a7ddbc72549e745471d4
-  data.tar.gz: 72d3b2cd7123cf96219ff797217588bf366975c4eac07bfdb339c8f840d11d52bb32c1c1a024de345e895b6d2b2a8c768d815780c74d2f9c0696f1d5e133730a
+  metadata.gz: 177b520c3e822141886b62d740dfb88e16fc984bd5c21e949c039f5ecab578121d1e311e01dc917197257a419bb82ee1de23375a15c953b721de74ff22a3fc93
+  data.tar.gz: a14fb212831e08062df9211bdb2f4e78c6750d7b0380362c735985a662de11da8a7ea8cde08cb7df30c55c44279e959081a39b4e1e330b5129b07d6536a5b4ae

data/README.md

@@ -29,6 +29,8 @@ Wurk is wire-compatible with Sidekiq — same Redis keys, same job JSON, same Ru
 
 **On speed:** Wurk is not currently faster than stock Sidekiq — it runs at roughly 0.87×–1.02× depending on workload shape, with parity on CPU and I/O but still behind on framework overhead (noop) and boot time. Numbers, method, and the reproduction command are in [docs/benchmarks.md](docs/benchmarks.md); run them yourself with `rake bench:vs_sidekiq`.
 
+**Also from us:** [Ultimate](https://github.com/developerz-ai/ultimate) — the AI-first full-stack framework, for a weekend pet project or the system a company runs on. What a whole stack looks like when the one writing the code is an agent, not a human: [`bunx create-ultimate myapp`](#also-from-developerzai-ultimate).
+
 ## Install
 
 ```ruby
@@ -299,6 +301,18 @@ Wurk is MIT and stays that way. If what you need is a commercial support contrac
 
 Full walkthrough — config side-by-side, the Redis key/`sidekiq_options` mapping, known incompatibilities, and a one-page cutover checklist: **[docs/migrate-from-sidekiq.md](https://github.com/developerz-ai/wurk/blob/main/docs/migrate-from-sidekiq.md)**.
 
+## Also from developerz.ai: Ultimate
+
+**[Ultimate](https://github.com/developerz-ai/ultimate) — the AI-first full-stack framework.** Rails' opinions, Bun's speed, one command that means shippable. Wurk is what one AI-maintained *library* looks like; Ultimate is the whole stack built on the same bet — the best framework you can hand a coding agent, whether what you are building is a weekend pet project or the system a company runs on.
+
+```bash
+bunx create-ultimate myapp && cd myapp && x dev
+```
+
+Every framework of the last fifteen years optimised for a human typing the code. Ultimate assumes an agent writes it, and that rewrites the defaults: **one way to do each thing**, so there is nothing to choose between; conventions that are **build errors**, so the compiler corrects the agent instead of a reviewer; errors carrying a stable code, a cause, and the exact command that fixes it, so a failure costs one round-trip; docs shipped in `node_modules` and `--json` on every command, so nothing reaches for a wiki. `x verify` is the whole contract — green means shippable.
+
+TypeScript end to end, MIT, and as measured about its own claims as this file is: what is proven, what is not, and what it refuses to claim yet are all in [its README](https://github.com/developerz-ai/ultimate#readme).
+
 ## Contributing
 
 Issues and pull requests are welcome — see **[CONTRIBUTING.md](https://github.com/developerz-ai/wurk/blob/main/CONTRIBUTING.md)** for the dev setup, test layers, and conventions, and **[SECURITY.md](https://github.com/developerz-ai/wurk/blob/main/SECURITY.md)** to report a vulnerability.

data/lib/wurk/api/validation.rb

@@ -94,13 +94,12 @@ module Wurk
       # one without reopening this file. Baked into the literal rather than
       # appended at load, so the parallel test runner never observes a
       # half-built list.
-      # rubocop:disable Style/MutableConstant
+      # rubocop:disable-next Style/MutableConstant
       JOB_KEYS = %w[
         class args queue at retry jid backtrace tags dead
         retry_for retry_queue expires_in track timeout deadline
         encrypt unique_for unique_until collapse log_level locale wrapped
       ]
-      # rubocop:enable Style/MutableConstant
 
       # `push_bulk`'s envelope keys, on top of the job keys it shares.
       BULK_KEYS = %w[batch_size spread_interval].freeze

data/lib/wurk/cli.rb

@@ -240,7 +240,11 @@ module Wurk
 
     # --- run helpers ----------------------------------------------------
 
+    # Claim the worker boot before the host app loads, so the railtie's
+    # after_initialize hook knows this process already has a worker and does
+    # not fork a second one on top of it (#worker_boot_claimed?).
     def enter_server_mode
+      Wurk.claim_worker_boot!
       Wurk.enter_server_mode(@config)
     end
 

data/lib/wurk/rails_boot.rb

@@ -42,8 +42,14 @@ module Wurk
     # A process that won't run workers isn't a server: skip both server mode
     # and the swarm boot. Console mode is detected reliably here — the console
     # command file defines ::Rails::Console before initializers run.
+    #
+    # `Wurk.worker_boot_claimed?` covers the CLI: `bundle exec wurk` boots the
+    # host app itself and then runs a Launcher in this very process, so forking
+    # a swarm here as well would put two independent workers on one queue and
+    # run every job — every cron tick included — twice.
     def skip_boot?
       ENV['WURK_DISABLED'] == '1' ||
+        Wurk.worker_boot_claimed? ||
         building? ||
         defined?(::Rails::Console) ||
         ::Rails.env.test?

data/lib/wurk/stats.rb

@@ -116,9 +116,9 @@ module Wurk
     # Single pipeline for the cheap counters. Eagerly invoked at initialize
     # so callers can read many fields without paying per-method round trips.
     FAST_QUERIES = [
-      ['GET',   'stat:processed'],
-      ['GET',   'stat:failed'],
-      ['GET',   Keys::STAT_EXPIRED],
+      ['GET', 'stat:processed'],
+      ['GET', 'stat:failed'],
+      ['GET', Keys::STAT_EXPIRED],
       ['ZCARD', Keys::SCHEDULE],
       ['ZCARD', Keys::RETRY],
       ['ZCARD', Keys::DEAD],

data/lib/wurk/swarm.rb

@@ -65,6 +65,25 @@ module Wurk
     # them mid-tail, so its own wait always extends past theirs by this much.
     SHUTDOWN_GRACE = 5
 
+    # How often the drain re-relays TERM to whatever is still in the child
+    # table. A child forked in the instant before the drain can miss the first
+    # one outright: from `Process.fork` returning in the child until ChildBoot
+    # resets the inherited traps, the PARENT's handler is what a TERM finds
+    # there, and it writes the signal into the parent's self-pipe (or, once
+    # `fork_child` has dropped that pipe, into nothing) instead of stopping the
+    # child. The child then boots clean, drains nothing, and `wait_for_children`
+    # burns its whole budget before `hard_kill_stragglers` SIGKILLs it — taking
+    # its in-flight jobs with it. The window is the `_fork` hook chain
+    # (ActiveSupport's ForkTracker and friends all run child-side before
+    # `Process.fork` returns), so it widens with load: measured 10.5s drains
+    # against a 2.6s baseline once that chain is slowed. No child-side fix can
+    # close it — the window precedes any code the child controls — so the
+    # supervisor repeats itself instead. Re-sending is safe: by the second pass
+    # the child owns its handler, TERM to a child already draining is a no-op,
+    # and the pids come from the child table, where an exited child is a zombie
+    # until reaped and so can never be a recycled pid.
+    RETERM_INTERVAL = 1.0
+
     # USR2 is relayed (log reopen) — without a trap, a logrotate config that
     # signals the master pid would hit USR2's default disposition and kill the
     # whole swarm.
@@ -503,8 +522,13 @@ module Wurk
 
     def wait_for_children(timeout)
       deadline = monotonic + timeout
+      reterm_at = monotonic + RETERM_INTERVAL
       while monotonic < deadline && any_children?
         reap_children
+        if monotonic >= reterm_at
+          relay_signal('TERM')
+          reterm_at = monotonic + RETERM_INTERVAL
+        end
         sleep 0.1
       end
     end

data/lib/wurk/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Wurk
-  VERSION = '1.7.2'
+  VERSION = '1.7.4'
 end

data/lib/wurk.rb

@@ -225,6 +225,31 @@ module Wurk
       config[:server] = true
     end
 
+    # True once something in THIS process has taken responsibility for running
+    # the workers. The CLI claims it before it boots the host application; the
+    # railtie's `after_initialize` hook reads it and stands down.
+    #
+    # Without the claim, `bundle exec wurk` inside a Rails app runs two
+    # independent workers: the CLI boots the app, the railtie forks a swarm
+    # from after_initialize, and then the CLI starts its own Launcher in the
+    # parent. Both drain the same queue, so every job runs twice — including
+    # every cron tick. See #claim_worker_boot!.
+    def worker_boot_claimed?
+      !!@worker_boot_claimed
+    end
+
+    # Claimed by the wurk/wurkswarm CLI. Not part of `enter_server_mode`: the
+    # railtie enters server mode too, and claiming there would make the railtie
+    # skip its own boot and run no workers at all.
+    def claim_worker_boot!
+      @worker_boot_claimed = true
+    end
+
+    # Test seam, matching `attr_writer :server` above: the claim is
+    # process-global, so a test that runs the CLI has to hand it back or it
+    # leaks into whatever test class shares the worker process next.
+    attr_writer :worker_boot_claimed
+
     # Wurk ships Pro+Ent features in the free gem; these flags exist solely
     # for third-party gems that branch on Sidekiq.pro? / Sidekiq.ent?.
     def pro?

data/vendor/assets/dashboard/wurk-manifest.json

@@ -1,4 +1,4 @@
 {
-  "version": "1.7.2",
-  "timestamp": "2026-08-11T12:40:51.498Z"
+  "version": "1.7.4",
+  "timestamp": "2026-08-27T19:02:36.342Z"
 }

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: wurk
 version: !ruby/object:Gem::Version
-  version: 1.7.2
+  version: 1.7.4
 platform: ruby
 authors:
 - developerz.ai