ruby.git/test/socket, branch v3_3_11 The Ruby Programming Language merge revision(s) beb85e7eeee4163cd45b69645a60cdb942f72c05: [Backport #21705] 2025-11-30T01:36:56+00:00 nagachika nagachika@ruby-lang.org 2025-11-30T01:36:56+00:00 1974ccabbfdc73e78e758a6ad7ea8542e2119432 [PATCH] [Bug #21705] Fix segfaults on Windows It should check the type of the argument and coercion before converting the encoding. 
	[PATCH] [Bug #21705] Fix segfaults on Windows

	It should check the type of the argument and coercion before
	converting the encoding.
[Bug #20208] Revert "Set AI_ADDRCONFIG when making getaddrinfo(3) calls for outgoi… (#9791) 2024-03-14T16:27:05+00:00 KJ Tsanaktsidis kj@kjtsanaktsidis.id.au 2024-03-14T16:27:05+00:00 606dd03e9b0d4cf65ef56e52fab063e3ed5ef797 Revert "Set AI_ADDRCONFIG when making getaddrinfo(3) calls for outgoing conns" This reverts commit 673ed41c81cf5a6951bcb2c3dec82d7bd6ea7440. 
Revert "Set AI_ADDRCONFIG when making getaddrinfo(3) calls for outgoing conns"

This reverts commit 673ed41c81cf5a6951bcb2c3dec82d7bd6ea7440.
 Prevent a warning: assigned but unused variable - status 2023-12-12T01:31:37+00:00 Yusuke Endoh mame@ruby-lang.org 2023-12-12T01:31:14+00:00 73b43fffa163e11ce9e7e8880631acb870ac1695 






always omit test_ai_addrconfig.
2023-12-07T09:28:47+00:00

Tanaka Akira
akr@fsij.org

2023-12-07T09:28:47+00:00

abf192eb16ea845ac11743a32bd2f3e2d234488b












Set AI_ADDRCONFIG when making getaddrinfo(3) calls for outgoing conns (#7295)
2023-12-07T08:55:15+00:00

KJ Tsanaktsidis
kj@kjtsanaktsidis.id.au

2023-12-07T08:55:15+00:00

d2ba8ea54a4089959afdeecdd963e3c4ff391748

When making an outgoing TCP or UDP connection, set AI_ADDRCONFIG in the
hints we send to getaddrinfo(3) (if supported). This will prompt the
resolver to _NOT_ issue A or AAAA queries if the system does not
actually have an IPv4 or IPv6 address (respectively).

This makes outgoing connections marginally more efficient on
non-dual-stack systems, since we don't have to try connecting to an
address which can't possibly work.

More importantly, however, this works around a race condition present
in some older versions of glibc on aarch64 where it could accidently
send the two outgoing DNS queries with the same DNS txnid, and get
confused when receiving the responses. This manifests as outgoing
connections sometimes taking 5 seconds (the DNS timeout before retry) to
be made.

Fixes #19144




When making an outgoing TCP or UDP connection, set AI_ADDRCONFIG in the
hints we send to getaddrinfo(3) (if supported). This will prompt the
resolver to _NOT_ issue A or AAAA queries if the system does not
actually have an IPv4 or IPv6 address (respectively).

This makes outgoing connections marginally more efficient on
non-dual-stack systems, since we don't have to try connecting to an
address which can't possibly work.

More importantly, however, this works around a race condition present
in some older versions of glibc on aarch64 where it could accidently
send the two outgoing DNS queries with the same DNS txnid, and get
confused when receiving the responses. This manifests as outgoing
connections sometimes taking 5 seconds (the DNS timeout before retry) to
be made.

Fixes #19144






Fixup with review comment
2023-12-01T03:20:03+00:00

Misaki Shioi
shioi.mm@gmail.com

2023-12-01T01:23:14+00:00

52c2660163240a494b65eb9942c3978896ed807b

https://github.com/ruby/ruby/pull/9088#discussion_r1411490445





https://github.com/ruby/ruby/pull/9088#discussion_r1411490445







Relax test conditions to velify Socket::ResolutionError#error_code
2023-12-01T03:20:03+00:00

Misaki Shioi
shioi.mm@gmail.com

2023-12-01T00:31:33+00:00

1bfd30a1e3fa2c1d2729667ed698b7c604c2a1bd

The test for Socket::ResolutionError#error_code fails in the FreeBSD environment with this test condition. Because Socket::ResolutionError#error_code returns Socket::EAI_FAIL instead of Socket::EAI_FAMILY.

https://rubyci.s3.amazonaws.com/freebsd12/ruby-master/log/20231130T103002Z.fail.html.gz

This PR avoids the test failure by relaxing the condition.

Also changed the domain for testing to `example.com`.





The test for Socket::ResolutionError#error_code fails in the FreeBSD environment with this test condition. Because Socket::ResolutionError#error_code returns Socket::EAI_FAIL instead of Socket::EAI_FAMILY.

https://rubyci.s3.amazonaws.com/freebsd12/ruby-master/log/20231130T103002Z.fail.html.gz

This PR avoids the test failure by relaxing the condition.

Also changed the domain for testing to `example.com`.







Skip test_resolurion_error_error_code with FreeBSD environment
2023-11-30T11:17:27+00:00

Hiroshi SHIBATA
hsbt@ruby-lang.org

2023-11-30T11:17:27+00:00

722cb9a56d091a10fd6ff9eddfcc7773f06a393e

  https://rubyci.s3.amazonaws.com/freebsd12/ruby-master/log/20231130T103002Z.fail.html.gz





  https://rubyci.s3.amazonaws.com/freebsd12/ruby-master/log/20231130T103002Z.fail.html.gz







Fix the argument order
2023-11-30T04:36:11+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-11-30T04:36:11+00:00

e6d4441618161397610088192c65b42f217d4e38












Replace SocketError with Socket::ResolutionError in rsock_raise_socket_error
2023-11-30T04:27:19+00:00

Misaki Shioi
shioi.mm@gmail.com

2023-11-23T07:49:41+00:00

52f6de41961d511e82826d6266441d91a92dcd59

rsock_raise_socket_error is called only when getaddrinfo and getaddrname fail





rsock_raise_socket_error is called only when getaddrinfo and getaddrname fail