polyrun 2.2.2 → 2.2.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a2d28bc9ddd04cf7beebdf3dc7588b61c32c5a17b9c2c97dc25a0135f84c0bef
-  data.tar.gz: 36dbe2a44021aeb42ef235fbddc994cfe823bac129bfe284f8945d60408f06fa
+  metadata.gz: de79eaae07044fa991b839a44011f7648df5ba16d0586a1ea2708c1d7160cf5e
+  data.tar.gz: f3cbab3bf642164ffa507aa75be1acaaf7a232057b1b1c5f3fcdb0f804c2a0a7
 SHA512:
-  metadata.gz: 701f77a58aad54da7963043a54065cf5a11b4905fbfe6fdb20a25345fa0bc7f5b9fe62730e3828cce94b3203986b99d2f724848bfca56c67815d538723bf0602
-  data.tar.gz: 6591a3dae32970c56b8f329cb7caec8a36b53d25d20ad882dadf8a8d059dad4bcacd97015d8f5cfb822ed7cf0c7b49c03662ede103f3530e4f80f07a7a1f6213
+  metadata.gz: f62f0cbc1760e3fc42a4711b7e55eace3b8b5bb038836abcae91eba876cfabf9b72832e2f04a284744fdf09247288bff6b60c7a3b1a38d00ee140d37634702df
+  data.tar.gz: 4f9b6d94992745419d35a5bbb40041094569f725470904f546566bfdba7a3e7eeca899f5b80844d9908ca36e744870fef3f8ecef6e20d589fa090d0363859147

data/CHANGELOG.md

@@ -1,5 +1,17 @@
 # CHANGELOG
 
+## Unreleased
+
+## 2.2.4 (2026-09-04)
+
+- Fix `DEBUG_SQL` / `POLYRUN_DEBUG_SQL` raising `NoMethodError` for `loggable_sql?` when the SQL subscriber runs on an RSpec example group.
+- Add `rfcs/` starter pack: process (RFC 0001), positioning (RFC 0002), and Standards Track design RFCs 0003–0006 for shard layouts, coverage merge, hooks, and partition config.
+
+## 2.2.3 (2026-08-16)
+
+- Fix `merge-failures` `Encoding::CompatibilityError` when JSONL or RSpec JSON contains UTF-8 and the process locale is US-ASCII; read fragments as UTF-8
+- Join worker output forwarders before closing pipe ends so shard logs keep the last bytes after a worker exits
+
 ## 2.2.2 (2026-07-25)
 
 - BREAKING: Require Ruby 3.4 or newer

data/CODE_OF_CONDUCT.md

@@ -1,31 +1,26 @@
 # Code of Conduct
 
-## Our pledge
+## Pledge
 
-We pledge to make participation in the Polyrun community a harassment-free experience for everyone. We operate on principles of mutual respect, privacy, and authentic engagement. We value substantive contributions and clarity on intentions.
+Participation is a harassment-free experience. Treat each other with respect. Keep private context private.
 
-## Our standards
+## Expected behavior
 
-Examples of behavior that contributes to a positive environment include:
+- Engage with genuine curiosity. Admit uncertainty.
+- Own every line you submit, including generated code.
+- Correct errors politely.
+- Use language that welcomes people and respects identity and privacy.
 
-- Authenticity: engaging with genuine curiosity and admitting uncertainty rather than feigning knowledge.
-- Responsible innovation: taking full responsibility for any content or code contributed, whether manually written or generated by automation tools.
-- Gentle correction: responding politely to errors. We view mistakes as opportunities for learning, provided they are addressed with humility.
-- Inclusive language: using language that welcomes diverse perspectives and respects the privacy and identity of all participants.
+## Unacceptable behavior
 
-Examples of unacceptable behavior include:
+- Harassment, trolling, or insulting comments, public or private.
+- Using jargon or volume, including automated spam, to silence others.
+- Sharing others' data or personal context without permission.
 
-- Harassment: public or private harassment, trolling, or insulting comments.
-- Weaponized complexity: using jargon or overwhelming volume (including automated spam) to silence others.
-- Publishing private information: sharing others' data or personal context without explicit permission.
+## Automation
 
-## Artificial intelligence and automation
-
-In accordance with our commitment to collective awareness:
-
-- Contributors are responsible for the accuracy and security of any AI-generated artifacts they submit.
-- "The AI wrote it" is not a valid excuse for introducing bugs, security vulnerabilities, or bias.
+You remain responsible for bugs, security holes, and bias in generated artifacts you submit.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at contact@kiskolabs.com. All complaints will be reviewed and investigated promptly and fairly.
+Report abusive or harassing behavior to contact@kiskolabs.com. Reports are reviewed and investigated.

data/CONTRIBUTING.md

@@ -1,106 +1,23 @@
-# Contributing to Polyrun
+# Contributing Guidelines
 
-## Development setup
+## Automation authorship
 
-```bash
-bundle install
-bundle exec appraisal install
-```
+You may use AI and automation tools. You remain the author of every line you submit: review, debug, and understand the change.
 
-## Tests
+Keep pull requests small enough to review. Annotate non-obvious logic.
 
-```bash
-bundle exec rspec
-# or
-bundle exec rake spec
-```
+Never send project secrets or private context to public models.
 
-Coverage merge performance (large synthetic payloads):
+## How to contribute
 
-Native extension (optional; compiles via `bundle install` or `cd ext/polyrun_coverage_merge && ruby extconf.rb && make`):
+### Reporting issues
 
-After pulling changes under `ext/**/*.c` or `ext/**/extconf.rb`, rebuild the extension before running specs or benchmarks:
+Verify the facts before filing. Use issue templates for goals, constraints, and reproduction steps.
 
-```bash
-make native-extension
-# or: bundle exec rake native_extension
-```
+### Pull requests
 
-If merge specs segfault or native acceleration behaves oddly after a pull, run `make clean` in `ext/polyrun_coverage_merge` and `make native-extension` again (or `bundle install` to trigger a full compile).
+Keep one pull request to one goal. Explain why the change is needed. Run smoke tests and regression checks locally before opening the request.
 
-CI compiles the extension on Linux and macOS (`.github/workflows/native-extension.yml`).
+### Review
 
-```bash
-bundle exec rake bench_merge
-# or: ruby benchmark/merge_coverage.rb
-```
-
-RSpec performance benchmarks (coverage merge + spec-quality peek; writes `tmp/benchmarks/profile_<sha>.log`):
-
-```bash
-bundle exec rake bench_performance
-# optional: STACKPROF=1 or BENCHMARK_IPS=1 for spec/performance/profiling_spec.rb
-# optional: BENCH_MEMORY=1 bundle exec rspec spec/performance/benchmark_merge_spec.rb spec/performance/benchmark_spec.rb --tag benchmark
-# optional env: BENCH_LINE_COUNT_REPS, BENCH_MEMORY_REPS
-```
-
-Run the suite under alternate Ruby constraints (see `Appraisals` and `gemfiles/`):
-
-```bash
-bundle exec appraisal ruby34 rspec
-bundle exec appraisal ruby40 rspec
-```
-
-## Linting
-
-[RuboCop](https://rubocop.org/) with [Standard](https://github.com/standardrb/standard) style, plus `rubocop-rspec` and `rubocop-thread_safety`. Project-specific cop tweaks and metric `Exclude` lists live in `.rubocop.yml`.
-
-```bash
-bundle exec rubocop
-bundle exec rubocop -a   # safe autocorrect
-bundle exec rake rubocop
-```
-
-## RBS
-
-Type signatures live under `sig/` and ship with the gem. Validate them after changes:
-
-```bash
-bundle exec rake rbs
-# equivalent: bundle exec rbs -I sig validate
-```
-
-Keep `require "polyrun"` free of RSpec/Minitest: optional wiring stays in `polyrun/rspec`, `polyrun/minitest`, and `polyrun/reporting/rspec_junit` (see README).
-
-[Trunk](https://trunk.io/) aggregates RuboCop, YAML, Markdown, shellcheck, and more (see `.trunk/trunk.yaml`):
-
-```bash
-trunk check
-trunk fmt
-```
-
-CI runs `rake ci` (RSpec + RuboCop). Optional Trunk workflow: `.github/workflows/trunk.yml`.
-
-## Adopting Polyrun in other repos
-
-- [docs/SETUP_PROFILE.md](docs/SETUP_PROFILE.md) — agent or human checklist (CI model A vs B, database, prepare).
-- `bundle exec polyrun init --list` — lists starter `polyrun.yml` and `POLYRUN.md` templates (see `examples/templates/README.md`).
-
-## Examples
-
-Runnable demos live under `examples/`. After changing the gem, smoke them:
-
-```bash
-cd examples && ./bin/ci_prepare
-cd examples/simple/simple_demo && RAILS_ENV=test bundle exec rspec
-# optional: complex polyrepo demo (multi-DB + three Vite clients + RSpec E2E)
-# cd examples/complex/polyrepo_demo && RAILS_ENV=test bin/rails db:prepare && bundle exec rspec
-```
-
-See `examples/README.md`.
-
-## Pull requests
-
-- One logical change per PR when possible.
-- Add or update specs for behavior changes.
-- Run `bundle exec rake ci` before pushing.
+Reviewers will ask about approach and trade-offs. Treat suggested changes as part of the work.

data/README.md

@@ -2,6 +2,8 @@
 
 Ruby gem for parallel test runs, merged coverage (SimpleCov-compatible JSON to JSON, LCOV, Cobertura, or console output), CI reporting (JUnit, timing), and parallel-test hygiene (fixtures, snapshots, per-shard databases, asset preparation). Ship it as one development dependency: no runtime gem dependencies beyond the standard library and vendored code.
 
+Design changes go through `rfcs/` (RFC 0001).
+
 ## Why?
 
 Running tests in parallel across processes still requires a single merged coverage report, stable shard assignment, isolated databases per worker so rows are not shared, and reliable timing data for cost-based splits—without wiring together many small tools and shell scripts.

data/SECURITY.md

@@ -2,26 +2,24 @@
 
 ## Reporting a Vulnerability
 
-Do not open a public GitHub issue for security vulnerabilities.
+Email security details to: security@kiskolabs.com
 
-Email security details to security@kiskolabs.com.
-
-Include: description, steps to reproduce, potential impact, and suggested fix (if available).
+Send the report only to that address. Include description, steps to reproduce, potential impact, and a suggested fix when you have one.
 
 ### Response Timeline
 
-- We will acknowledge receipt of your report
-- We will provide an initial assessment
-- We will keep you informed of our progress and resolution timeline
+- We will acknowledge receipt of your report.
+- We will provide an initial assessment.
+- We will keep you informed of our progress and resolution timeline.
 
 ### Disclosure Policy
 
-- We will work with you to understand and resolve the issue
-- We will credit you for the discovery (unless you prefer to remain anonymous)
-- We will publish a security advisory after the vulnerability is patched
-- We will coordinate public disclosure with you
+- We will work with you to understand and resolve the issue.
+- We will credit you for the discovery unless you prefer to remain anonymous.
+- We will publish a security advisory after the vulnerability is patched.
+- We will coordinate public disclosure with you.
 
-## Automation security
+## Automation Security
 
-- Context isolation: do not include production credentials, API keys, or personally identifiable information in prompts sent to third-party LLMs or automation services.
-- Supply chain: verify automated dependencies.
+- Keep production credentials, API keys, and personal data out of prompts sent to third-party models or automation services.
+- Verify automated dependencies.

data/lib/polyrun/reporting/failure_merge.rb

@@ -101,7 +101,7 @@ module Polyrun
           return rows_from_jsonl_file(path)
         end
 
-        text = File.read(path)
+        text = File.read(path, encoding: Encoding::UTF_8)
         data =
           begin
             JSON.parse(text)
@@ -126,7 +126,7 @@ module Polyrun
 
       def rows_from_jsonl_file(path)
         acc = []
-        File.readlines(path, chomp: true).each_with_index do |line, idx|
+        File.readlines(path, chomp: true, encoding: Encoding::UTF_8).each_with_index do |line, idx|
           line = line.strip
           next if line.empty?
 

data/lib/polyrun/rspec/example_debug_instrumentation.rb

@@ -11,9 +11,9 @@ module Polyrun
         rspec_config.around do |example|
           subscriber = ActiveSupport::Notifications.subscribe("sql.active_record") do |event|
             payload = event.payload[:sql]
-            next unless loggable_sql?(payload)
+            next unless ExampleDebug.loggable_sql?(payload)
 
-            line = sql_with_interpolated_binds(payload, event.payload[:type_casted_binds])
+            line = ExampleDebug.sql_with_interpolated_binds(payload, event.payload[:type_casted_binds])
             io.puts "+ #{line}"
           end
 

data/lib/polyrun/version.rb

@@ -1,3 +1,3 @@
 module Polyrun
-  VERSION = "2.2.2"
+  VERSION = "2.2.4"
 end

data/lib/polyrun/worker_output.rb

@@ -157,12 +157,14 @@ module Polyrun
     private_class_method :drain_remaining_output
 
     def drain_forwarders(entry)
+      # Join first so threads can drain pipe buffers after the child exits.
+      # Closing read ends before join races and can drop the final bytes.
+      entry[:threads].each(&:join)
       entry[:ios].each do |io|
         io.close unless io.closed?
       rescue IOError
         nil
       end
-      entry[:threads].each(&:join)
       entry[:forwarder].close
     end
     private_class_method :drain_forwarders

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: polyrun
 version: !ruby/object:Gem::Version
-  version: 2.2.2
+  version: 2.2.4
 platform: ruby
 authors:
 - Andrei Makarov