Stephen Margheim

> So, I'm no owner of this gem, and my interest for sqlite3 is rather limited, but if the goal is to implement a statement timeout, I'm not offering a...

Another great use-case for a raw `progress_handler` is allowing apps/projects using a Fiber Scheduler to switch fibers during query execution

@tenderlove @flavorjones: I believe this is ready to go.

Just realized that in addition to switching fibers, this also unlocks the ability for apps to switch threads while queries are executing 👀

@flavorjones @tenderlove: Merged changes from `main`, resolved a couple Standard issues, and added a test demonstrating that the `progress_handler` can be used to improve concurrency. I'm still reading and thinking...

This is going to be a really nice feature when we merge it. I've been experimenting with using this to support better CPU saturation in multi-threaded environments and the results...

@rosa: When the PR to land this opens, I am going to open a corresponding PR to update the `/railties/lib/rails/generators/rails/app/templates/config/databases/sqlite3.yml.tt` template to use a separate `queue` database when Solid Queue...

@byroot: Interesting. I cannot reproduce locally. ``` $ bundle exec rake test:sqlite3 Using sqlite3 Run options: --seed 41270 Finished in 106.020541s, 81.4182 runs/s, 276.5973 assertions/s. 8632 runs, 29325 assertions, 0...

My first experiment failed, but I have honed in on where the issue arises, but without getting to the point of understanding precisely what the issue is. The issue has...

Making progress. I'm down to a few sporadic failures where the tests simply take longer than the `busy_timeout` and thus the busy exception is thrown.