23499418156
96%
main: 96%

Ran 24 Mar 2026 04:07PM UTC

Jobs 1

Files 904

Run time 2min

Badge

Embed ▾

Committed 24 Mar 2026 04:03PM UTC coverage: 96.105%. Remained the same

Build # 23499418156

Build Type

Pull #4057

github

Committed by

JoeCohen

Commit Message

Fix Trilogy::SynchronizationError after Puma fork

Replace the manual disconnect/establish_connection in on_worker_boot
with ActiveRecord::Base.clear_all_connections!, which clears all
connection pools (primary, cache, etc.) after fork.

The old code only disconnected the primary database connection,
leaving the SolidCache :cache role connection inherited from the
parent process with a stale Trilogy @owner thread reference.
When SolidCache's background expiry thread (expiry_method: :thread)
ran in a Puma worker, Trilogy detected the thread mismatch and raised
SynchronizationError.

This was always broken but became visible with Trilogy 2.11.0, which
now raises an explicit error on concurrent connection use rather than
proceeding with undefined behavior.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Pull Request Pull Request #4057: Clear connection after fork

Run Details

34521 of 35920 relevant lines covered (96.11%)

680.28 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	23499418156.1	24 Mar 2026 04:07PM UTC	904	96.11	GitHub Action Run

MushroomObserver / mushroom-observer / 23499418156
96%
main: 96%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 23499418156

MushroomObserver / mushroom-observer / 23499418156 96% main: 96%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 23499418156

MushroomObserver / mushroom-observer / 23499418156
96%
main: 96%

README BADGES
x