`ViteRuby#dev_server_running?` broken on MacOS 27

[bensheldon]

• I have tried upgrading by running bundle update vite_ruby.
• I have read the troubleshooting section before opening an issue.

Description 📖

ViteRuby#dev_server_running? relies on checking the socket and expecting that to raise an exception. That does not happen on current Rubies on MacOS 27:

• https://bugs.ruby-lang.org/issues/22223
• [Bug #22223] Check SO_ERROR after waiting for nonblocking connect ruby/ruby#18203

Reproduction 🐞

# NOT MacOS 27
irb(main):007> Socket.tcp("127.0.0.1", 9999).close
/Users/dzunk/.rubies/ruby-3.4.10/lib/ruby/3.4.0/socket.rb:68:in 'Socket#connect': Connection refused - connect(2) for 127.0.0.1:65534 (Errno::ECONNREFUSED)

# On MacOS 27

irb(main):016> Socket.tcp("127.0.0.1", 9999, connect_timeout: 1).close
=> nil

[ElMassimo]

Thanks for reporting!

If I understand correctly this is a bug that will be fixed in Ruby eventually?

In the meantime, I've released #621 in vite_ruby-3.11.0, which default to a filesystem check instead.

[bensheldon]

That's correct it's a problem that arises in upstream Ruby.

I saw this backlinked in the a Ruby bug as a potential workaround: hashicorp/vagrant#13842

...though I also like the filesystem check. I'll upgrade and report if that resolves my problem of the dev server being incorrectly detected.

Thanks for the help and the fantastic library (really, this library has renewed my hope in a low-fuss frontend story in Rails ❤️)

[bensheldon]

@ElMassimo I upgraded the gem, but I think it also needs a vite-plugin-ruby version release too to write the tmp file.