Initial Ractor support #365
Conversation
sandlerr
force-pushed
the
sandlerr/ractor
branch
from
10e89a1 to
fea5c83
Compare
sandlerr
force-pushed
the
sandlerr/ractor
branch
from
fea5c83 to
e116ba5
Compare
|
Is there any outstanding feedback here? Thanks |
|
Great, I'll rebase and merge it today or tomorrow. |
flavorjones
force-pushed
the
sandlerr/ractor
branch
from
e116ba5 to
54959e6
Compare
|
So it seems like in Ruby 3.3, trying to pass a I'm not sure if this is intentional behavior or not. @sandlerr or @tenderlove do you know? Edit: to be explicit, the RemoteError is wrapping |
|
OK, that exception started to get raised in ruby/ruby@ce47ee00 as a fix, so I'm just going to adapt the test to the different behaviors before and after 3.3.0. |
flavorjones
force-pushed
the
sandlerr/ractor
branch
2 times, most recently
from
0f4db3d to
104ea23
Compare
|
The stress test hangs under Ruby 3.3 with as few as 3 ractor writers, and it's not clear to me why. |
flavorjones
force-pushed
the
sandlerr/ractor
branch
from
104ea23 to
6ccb27b
Compare
* main: (215 commits) version bump to v2.6.0 Database#enable_load_extension def only if extensions are available dep: update vendored sqlite to v3.49.1 dep: update vendored sqlite to 3.49.0 dep: update vendored sqlite to 3.48.0 build(deps-dev): update rdoc requirement from 6.11.0 to 6.12.0 dev: Add rake task `test:gdb` fix: tests pass on bigendian architecture dep: move style and docs deps into a separate group ci: test-gem-install should use `[` not `[[` test: skip database URI tests when using system libraries doc: update CHANGELOG dep: update rake-compiler-dock to v1.9.1 build(deps-dev): update rdoc requirement from 6.10.0 to 6.11.0 dep(doc): fixing psych installation on alpine dep(test): remove implicit dependence on benchmark gem build(deps-dev): update ruby_memcheck requirement from 3.0.0 to 3.0.1 dep: update rake-compiler-dock to v1.8.0 build(deps-dev): update rake-compiler requirement from 1.2.8 to 1.2.9 ci: bump test image tag from 3.4-rc to 3.4 ...
Allows users to create / open databases, send queries, and process ResultSets inside a Ractor. However, does not allow passing the gem's domain objects through the Ractor communication channels.
See #299 .