Skip to content

fix(spanner): remove unused mutex_m require - #276

Open
torreypayne wants to merge 1 commit into
mainfrom
fix-mutex-m-require
Open

torreypayne wants to merge 1 commit into
mainfrom
fix-mutex-m-require

Conversation

@torreypayne

Copy link
Copy Markdown
Member

RequestIdInterceptor required mutex_m but only uses core Mutex, and the gemspec never declared mutex_m. Ruby 3.4 made mutex_m a bundled gem, so require "google/cloud/spanner" raises LoadError in apps that don't list it (2.34.0 through 2.37.1). This removes the require, and the development Gemfile pin that hid the problem from CI.

Tested:

  • On Ruby 4.0.5, a clean bundle now loads the library.
  • Unit tests pass on Ruby 3.2, 3.3 and 4.0.
  • RuboCop, YARD and the gem build are clean.

Fixes #275

RequestIdInterceptor required mutex_m but only uses the core Mutex
class, and the gemspec never declared mutex_m. Ruby 3.4 made mutex_m a
bundled gem, so require "google/cloud/spanner" raised LoadError in any
bundle that didn't list it. Drop the require, and the development
Gemfile pin that kept CI from noticing.
@torreypayne
torreypayne requested a review from a team as a code owner November 18, 2026 01:02
@product-auto-label product-auto-label Bot added the api: spanner Issues related to the Spanner API. label Nov 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: spanner Issues related to the Spanner API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

google-cloud-spanner 2.34.0+ fails to load on Ruby 3.4+: cannot load such file -- mutex_m

2 participants