wurk 1.7.4 → 1.7.6

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 33b583b405b2f2cf26f62fea6c6551d0f6900c3d72879ec6968dd7c82c976f26
-  data.tar.gz: fe626c58ce7bd322765cd0df1f9655097647ab2fdcd5b9aa4200012d9dc09825
+  metadata.gz: d232f2e0c78233c2bbd71051a07df6e791d1fb1c0d701c9e3ff0820035207077
+  data.tar.gz: 06d15b628db2d8ab75ab8440b48f372ea0943108a0c19533db0c2cf82a1b74fe
 SHA512:
-  metadata.gz: 177b520c3e822141886b62d740dfb88e16fc984bd5c21e949c039f5ecab578121d1e311e01dc917197257a419bb82ee1de23375a15c953b721de74ff22a3fc93
-  data.tar.gz: a14fb212831e08062df9211bdb2f4e78c6750d7b0380362c735985a662de11da8a7ea8cde08cb7df30c55c44279e959081a39b4e1e330b5129b07d6536a5b4ae
+  metadata.gz: 522ee07752a14d58635f770411bf7d74d53fca26141f04f73e0f6596e27374ea580b11d405cdcaf297c53aeaca3e08f06e1409b876159fea34cd6c91bbbcbf89
+  data.tar.gz: 1ffc5b66a6ce06ee39353e3593296f22ac99f8851000fa1b78fcbfb30ff7617a742804fdf6584a07b9a4b039477b736b26c644e8844c8f420766fb21670fc287

data/README.md

@@ -130,7 +130,7 @@ Method, per-invocation records, workload definitions, and the separate `rake ben
 
 ## Documentation
 
-- **[Website](https://developerz-ai.github.io/wurk/)** · **[Wiki / full docs](https://github.com/developerz-ai/wurk/wiki)** — the pitch, install, and the complete guide.
+- **[Website](https://developerz-ai.github.io/wurk/)** · **[Wiki](https://github.com/developerz-ai/wurk/wiki)** — the pitch, install, and short orientation guides; the complete reference is [`docs/`](https://github.com/developerz-ai/wurk/tree/main/docs), linked from every wiki page.
 - **[API reference (YARD)](https://developerz-ai.github.io/wurk/api/)** — generated docs for the public classes (`Wurk::Worker`, `Wurk::Client`, `Wurk::Configuration`, `Wurk::Batch`, `Wurk::Limiter`, `Wurk::Unique`, and the `Sidekiq::*` aliases). Machine-readable map for AI agents: **[llms.txt](https://developerz-ai.github.io/wurk/llms.txt)**.
 - **[Getting started & architecture](https://github.com/developerz-ai/wurk/blob/main/docs/idea/01-overview.md)** — how the swarm, manager, fetcher, and processor fit together.
 - **[Starting the worker](https://github.com/developerz-ai/wurk/blob/main/docs/running.md)** — Rails auto-start, the `wurk`/`wurkswarm` runners, and running standalone without Rails.
@@ -278,7 +278,7 @@ Infrastructure this basic should be free software. A Rails app shouldn't need a
 What has made that hard is maintenance: someone has to be paid to do it. Sidekiq funds a decade of *human* maintenance through its paid tiers, which is an honest trade. Wurk makes a different one — it is maintained **AI-first**: implementation, parity suite, docs, and benchmarks are written and kept current by AI agents under human review. A fix, a doc update, or a version bump is no longer somebody's week, which is what makes it practical to:
 
 - ship the entire Pro + Enterprise surface with no tier, no flag gate, and no license check;
-- keep parity honest mechanically rather than by hand — an independently written parity oracle suite, pinned to a documented Sidekiq revision, plus third-party gems (sidekiq-cron, sidekiq-unique-jobs, sidekiq-scheduler, sidekiq-status, sidekiq-failures, sidekiq-throttled) running their own upstream suites against Wurk on every push;
+- keep parity honest mechanically rather than by hand — an independently written parity oracle suite, pinned to a documented Sidekiq revision, plus sidekiq-cron's upstream suite running against Wurk on every push ([docs/idea/14-ecosystem-compat.md](https://github.com/developerz-ai/wurk/blob/main/docs/idea/14-ecosystem-compat.md) tracks the rest);
 - keep adding surface Sidekiq doesn't have — the [Wurk extras](#wurk-extras) above landed as one release;
 - hold ourselves to published numbers instead of adjectives — the suite runs against stock Sidekiq every release and ships the results [as measured](docs/benchmarks.md), including the unflattering ones.
 
@@ -297,7 +297,7 @@ Wurk is MIT and stays that way. If what you need is a commercial support contrac
 + gem "wurk"
 ```
 
-`bundle install && restart`. Wurk reads and writes the same Redis schema, so a rolling deploy can run Sidekiq and Wurk against the same Redis during the cutover. Third-party gems (sidekiq-cron, sidekiq-unique-jobs, sidekiq-scheduler, sidekiq-status, sidekiq-failures, sidekiq-throttled, …) are exercised by running their own upstream suites against Wurk in the [`ecosystem` CI job](https://github.com/developerz-ai/wurk/blob/main/.github/workflows/ecosystem.yml) (see [`test/ecosystem/`](https://github.com/developerz-ai/wurk/tree/main/test/ecosystem)).
+`bundle install && restart`. Wurk reads and writes the same Redis schema, so a rolling deploy can run Sidekiq and Wurk against the same Redis during the cutover. sidekiq-cron's upstream suite runs against Wurk in the [`ecosystem` CI job](https://github.com/developerz-ai/wurk/blob/main/.github/workflows/ecosystem.yml) (see [`test/ecosystem/`](https://github.com/developerz-ai/wurk/tree/main/test/ecosystem)). sidekiq-unique-jobs, sidekiq-scheduler, sidekiq-status, sidekiq-failures and sidekiq-throttled are target additions tracked in [docs/idea/14-ecosystem-compat.md](https://github.com/developerz-ai/wurk/blob/main/docs/idea/14-ecosystem-compat.md).
 
 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)**.
 

data/lib/wurk/encryption.rb

@@ -150,7 +150,13 @@ module Wurk
         version = Integer(envelope['v'])
         cipher = build_decrypt_cipher(envelope, key_for(version))
         plain = cipher.update(::Base64.strict_decode64(envelope['ct'])) + cipher.final
-        ::JSON.parse(plain, quirks_mode: true)
+        # No `quirks_mode:` — an encrypted arg may be a bare scalar ("hi", 42,
+        # null), and every json the gemspec's `>= 3.2` floor can resolve parses
+        # those at the top level by default (RFC 7159, json >= 2.0). The option
+        # was therefore already a no-op, and json 3.0.0 removed it outright:
+        # passing it raises ArgumentError and every encrypted job dies in the
+        # server middleware.
+        ::JSON.parse(plain)
       end
 
       # @return [Boolean] true if `value` looks like a Wurk crypto envelope.

data/lib/wurk/swarm.rb

@@ -360,7 +360,20 @@ module Wurk
     # stall signal delivery if the pipe fills. `exception: false` returns
     # :wait_writable instead of raising when full (drop the coalescible
     # duplicate); a closed pipe during shutdown is ignored too.
+    #
+    # The owner check is what keeps ONE child's signal from draining the whole
+    # fleet. A forked child inherits both this trap and the parent's live pipe,
+    # and `fork_child` cannot drop them until `Process.fork` RETURNS — the
+    # `_fork` hook chain runs child-side before that, so there is a window
+    # where an operator's `kill <child_pid>` writes TERM into the PARENT's
+    # supervise loop and drains every sibling. Measured: with that chain slowed
+    # the way a loaded box does, TERMing a single child killed the supervisor
+    # and all of it. Comparing pids instead closes it with no window at all —
+    # the inherited trap is inert in the child from its first instruction,
+    # because `@owner_pid` was stamped before the fork.
     def emit_signal(sig)
+      return unless owner?
+
       @signal_write&.write_nonblock("#{sig}\n", exception: false)
     rescue ::IOError, ::Errno::EPIPE, ::Errno::EBADF
       nil

data/lib/wurk/version.rb

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

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

@@ -1,4 +1,4 @@
 {
-  "version": "1.7.4",
-  "timestamp": "2026-08-27T19:02:36.342Z"
+  "version": "1.7.6",
+  "timestamp": "2026-09-07T19:30:05.829Z"
 }

metadata

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