:transaction strategy: uncommitted data disappears after perform_enqueued_jobs on Rails ≥ 7.2
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 67/100
Línea de trabajo
Start at the :transaction strategy entry point and read the reproduction app's README, then run for i in {1..100}; do bin/rails test; done to observe the intermittent failure. Compare the strategy's connection setup and teardown with Rails' pinned transactional fixtures; done means the reproduction completes without RecordNotFound or lock-wait failures.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Below is summary of bug I have found in my company's app I work for. It is related to how database cleaner and rails internals handles the connections to database. I used AI to help investigating the problem but I verified (as far as I understand it) and reproduced the problem. Below is the summary of but I prepared a detailed rails app (see its' README) with instruction how to reproduce it https://github.com/radarek/database-cleaner-connection-bug.
Summary
On Rails ≥ 7.2, the :transaction strategy can intermittently cause ActiveRecord::RecordNotFound (and lock-wait timeouts on writes): a row created inside a test becomes invisible after an ActiveJob runs inline (perform_enqueued_jobs).
Reproduction app: https://github.com/radarek/database-cleaner-connection-bug (Rails 8.1, MySQL/trilogy, Minitest). for i in {1..100}; do bin/rails test; done should reproduce the problem at least once
Cause
The :transaction strategy opens its wrapping transaction on a leased connection:
connection = ActiveRecord::Base.lease_connection
connection.begin_transaction(joinable: false)
Running any ActiveJob wraps execution in Rails.application.reloader.wrap { … }. On completion, Rails' AR executor hook (ConnectionPool::ExecutorHooks.complete) sees a connection whose transaction is not joinable and releases it back to the pool — while it still holds the open transaction and all of the test's uncommitted rows.
The next query then leases a connection again. If the pool hands it a different physical connection (e.g. after the background Reaper reclaims a connection and reorders the LIFO free list), that connection is a separate DB session that can't see the uncommitted data → RecordNotFound. This is why it's intermittent and why it only shows up alongside other specs that grow the pool past one connection.
Suggested fix
On Rails ≥ 7.2, pin the connection instead of leasing it:
pool.pin_connection!(...) # setup
pool.unpin_connection! # teardown
A pinned connection is immune to the executor hook (checkout always returns the pinned connection), so the swap can't happen. This is exactly what Rails' own transactional fixtures do — and the pinned variant in the repro app passes 100% of runs.
Full mechanism write-up (LIFO free list, orphaned connections, Reaper timing) is in the repo README.
- Lenguaje dominante
- Ruby
- Estrellas
- 3k
- Forks
- 485
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de DatabaseCleaner/database_cleaner
-
Cleaning of dev DBAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
-
Cannot truncate a table referenced in a foreign key constraint (ActiveRecord::StatementInvalid)Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
DatabaseCleaner/database_cleaner#717 · 5 comentarios · 1 reacción ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
DatabaseCleaner/database_cleaner#716 · 2 comentarios ·
-
Dificultad 5/5 Más de una semana Aptitud para principiantes 10/100
DatabaseCleaner/database_cleaner#705 · 1 comentario · 5 reacciones ·
Todos los issues de DatabaseCleaner/database_cleaner
Issues similares
-
revoir les metions de la DGEAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
betagouv/conseillers-entreprises#4720 ·
Los mantenedores suelen responder en 3 días
-
bug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
zerocracy/judges-action#2692 · 1 comentario ·
Los mantenedores suelen responder en 6 días
-
agent:triaged bug bughunt pm:bundler priority:p1
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
SocketDev/socket-patch#896 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Add Catalan (ca) translationAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
eurosky-social/eu-haul#32 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
simp/pupmod-simp-auditd#293 ·