[ruby-core:108069] [Ruby master Bug#18661] Net::HTTP behavior changed between 2.6 and 3.1 on windows.

Issue #18661 has been reported by jleblanc (Joshua LeBlanc).

----------------------------------------
Bug #18661: Net::HTTP behavior changed between 2.6 and 3.1 on windows.
https://bugs.ruby-lang.org/issues/18661

* Author: jleblanc (Joshua LeBlanc)
* Status: Open
* Priority: Normal
* ruby -v: ruby 3.1.1p18 (2022-02-18 revision 53f5fc4236) [x64-mingw-ucrt]
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN
----------------------------------------
We are upgrading a rails application from Ruby 2.6 to Ruby 3.1 on Windows.

Running rails systems tests hang on Ruby 3.1, while they succeed on Ruby 2.6. 

I tracked this down to Ruby 3.1's Net::HTTP using Socket.tcp rather than the old TCPSocket. 

Specifically, in `socket.rb`, `connect_internal` calls `connect_nonblock(self, exception: false)`, which ultimately hangs until timing out on windows.
Modifying the `socket.rb` source to use `connect(self)` instead results in a successful operation.

To be clear, the hanging operation is `socket.rb#connect_nonblock`, which is on line 1214

Reproduction:

1. Install Ruby 3.1 on Windows - I used RubyInstaller: https://github.com/oneclick/rubyinstaller2/releases/download/RubyInstaller-3.1.1-1/rubyinstaller-devkit-3.1.1-1-x64.exe
2. Clone the reproduction project: https://github.com/joshleblanc/windows_net_http_problem
3. Run `bundle install`
4. Run `rails test:system`

Chrome will open, however a connection will never be made, ultimately timing out.

To test this same process in earlier versions of ruby, simply create a new rails project with `rails new -O -J -S <name>`, add the `ffi` and `tzinfo-data` gems to the gemfile, and scaffold a new resource. Running `rails test:system` from this point should succeed.





-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>