railwatch 0.3.2 → 0.3.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a2929e5724d581361c5ce2e20a4184dcde4ad190edca068527a5f565043c5a9c
-  data.tar.gz: e63ea3bc8d89318bc4e296d17c006eb87dfb3ea06be0db5dea4dea6035a0dfc5
+  metadata.gz: 9c88b489c82195c106d414c397d391d8cf2e8d3e499dd67715d3db14fc4f7dae
+  data.tar.gz: 3a2bb00def3c244d0eb9630f1eb6b3d4fddb29ea17cf34e2c8023123c92bdaf3
 SHA512:
-  metadata.gz: b9477f54a79df466ad5113b56d7206cc7da3d6dd76db86e30c568bc6a9e6378a6545d2a3013fae33d6cef2ffd4d986fd18e9b07051ba67429a52fe38bb33fdee
-  data.tar.gz: '0892577170dc73fcd351ce620da0908afd9d2bd4b78f672e2931efb7130eacde83219664cd8d6afac36416d97c691d4897ab2355e6ff5c3f976ec3b4e73ac80b'
+  metadata.gz: f616d461f05f956503d2fa37d20dd238f98f1f77624665e6c352c675b9df12704b2a912e15b8bcf6d992192a86016b3ee39e8924b7b4a70d9bbe24f61d5c4845
+  data.tar.gz: 8d372cfaed4dd585b39a8bbd6f042b9af6bada233e92dc7e0021613507e6bc0d570cc120bce4f1f5ef163c223ea8855a730781c16bc5fd34321a9cff10020607

data/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## 0.3.3 (2026-09-19)
+
+- Fix `railwatch:install --local` writing test databases that parallel test
+  runners cannot share. The generated `test` entries named
+  `storage/test_railwatch*.sqlite3` with no `TEST_ENV_NUMBER`, so every worker
+  in a parallel run opened the same two SQLite files and raced through them:
+  `ActiveRecord::PendingMigrationError` and `SQLite3::IOException: disk I/O
+  error` out of `configure_connection`, on every shard. Rails' own test
+  database naming carries the number for this reason, and the generated names
+  now do too. An app with no parallel runner sets no `TEST_ENV_NUMBER`, so its
+  generated file is unchanged and no existing install needs migrating.
+
 ## 0.3.2 (2026-09-19)
 
 - Fix an embedded install's rake tasks reporting over HTTP instead of into

data/lib/generators/railwatch/install/install_generator.rb

@@ -383,12 +383,26 @@ module Railwatch
             lines.insert(start + 1, "  primary:\n")
             stop += 1
           end
-          entries = format(RAILWATCH_DATABASES, env: env).lines.map { |line| "  #{line}" }
+          entries = format(RAILWATCH_DATABASES, env: database_prefix(env)).lines.map { |line| "  #{line}" }
           lines = insert_lines(lines, stop, entries.join).lines
         end
         lines.join
       end
 
+      # What the database filenames are built from. For test that has to carry
+      # TEST_ENV_NUMBER, the way Rails' own test database naming does: runners
+      # like parallel_tests give each worker its own number and expect a
+      # database per worker. Without it every worker in a run opens the same
+      # two SQLite files and they fight over them -- observed as
+      # PendingMigrationError and "disk I/O error" from configure_connection,
+      # on an app running four workers. An app with no such runner sets no
+      # TEST_ENV_NUMBER, so the suffix is empty and the name is unchanged.
+      def self.database_prefix(env)
+        return env unless env == "test"
+
+        %(test<%= ENV["TEST_ENV_NUMBER"] %>)
+      end
+
       # Unconditional: `bundle exec puma` evaluates this file before it loads
       # the Rack app, so `if defined?(Railwatch)` would be false there and the
       # writer would never start. The plugin itself is inert when Railwatch is

data/lib/railwatch/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Railwatch
-  VERSION = "0.3.2"
+  VERSION = "0.3.3"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: railwatch
 version: !ruby/object:Gem::Version
-  version: 0.3.2
+  version: 0.3.3
 platform: ruby
 authors:
 - Cole Robertson