pablobm left a comment (openstreetmap/openstreetmap-website#6713)
I had a look. The author of the activerecord-postgis explains their decision at
https://github.com/seuros/activerecord-postgis/issues/13. I quote:
> Ruby 3.2 has some weird bug in Async and fiber.
> (...)
> [If you want to use Ruby 3.2,] you fork, change the requirement, and use your
> fork until you upgrade. I cannot guarantee you compatibility in a version i
> don't even have installed in my machines.
I interpret that (plus a link they provide) specifically as "a bug when doing
concurrency with fibers". I have asked to clarify in any case.
I think that this problem doesn't affect us. Unless I'm mistaken our app
doesn't use fibers, neither does Rails/ActiveRecord (unless specifically
configured), and I don't think Phusion Passenger does either. Caveat: I have
never used fibers myself, I might be missing something.
If I'm correct, then we can create a fork that allows for Ruby 3.2 for a while,
at least until the next Ubuntu LTS which should be published in April.
If not... well, I'd rather not having to park this for another 2-3 months!
:sweat_smile: But the alternative wouldn't really be great: if we used
activerecord-postgis-adapter, everyone would have to set `adapter: postgis`,
and then change it back to `adapter: postgres` in the future if we decide to
actually change gems for any reason. It doesn't sound like much, but I can see
it becoming a DX problem for many inexperienced contributors.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6713#issuecomment-3854041331
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/6713/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
