From: simonpatp@gmail.com
To: ruby-core@ruby-lang.org
Subject: [ruby-core:95135] [Ruby master Bug#16186] Calling Net::HTTP from within an #inspect implementation hang when invoked from p
Date: Fri, 27 Sep 2019 22:34:38 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-16186.20190927223437.5635211c822dc769@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16186.20190927223437@ruby-lang.org
Issue #16186 has been reported by byteit101 (Patrick Plenefisch).
----------------------------------------
Bug #16186: Calling Net::HTTP from within an #inspect implementation hang when invoked from p
https://bugs.ruby-lang.org/issues/16186
* Author: byteit101 (Patrick Plenefisch)
* Status: Open
* Priority: Normal
* Assignee:
* Target version:
* ruby -v: ruby 2.7.0dev (2019-09-27T18:22:21Z trunk d53cf85474) [x86_64-linux]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
Using this script:
``` ruby
require 'net/http'
class Victim
def inspect
puts "before"
Net::HTTP.get('example.com', '/index.html') # this hangs. I haven't tried other network libraries
puts "After"
return "success"
end
end
puts Victim.new.inspect # for some reason this doesn't hang
puts "now we hang"
p Victim.new # but this implicit invocation of inspect does hang. Independent of ordering, and works on JRuby
puts "It worked!"
```
Expected:
```
$ rvm use jruby
$ ruby bug.rb
before
After
success
now we hang
before
After
success
It worked!
$
```
Actual:
```
$ rvm use ruby-head
$ ruby bug.rb
before
After
success
now we hang
before
^C^C^Z
[1] + 13423 suspended ruby bug.rb
$ kill %1
$ (time passes)
Traceback (most recent call last):
11: from bug.rb:12:in `<main>'
10: from bug.rb:12:in `p'
9: from bug.rb:5:in `inspect'
8: from /home/byteit101/.rvm/rubies/ruby-head/lib/ruby/2.7.0/net/http.rb:458:in `get'
7: from /home/byteit101/.rvm/rubies/ruby-head/lib/ruby/2.7.0/net/http.rb:476:in `get_response'
6: from /home/byteit101/.rvm/rubies/ruby-head/lib/ruby/2.7.0/net/http.rb:919:in `start'
5: from /home/byteit101/.rvm/rubies/ruby-head/lib/ruby/2.7.0/net/http.rb:930:in `do_start'
4: from /home/byteit101/.rvm/rubies/ruby-head/lib/ruby/2.7.0/net/http.rb:945:in `connect'
3: from /home/byteit101/.rvm/rubies/ruby-head/lib/ruby/2.7.0/timeout.rb:105:in `timeout'
2: from /home/byteit101/.rvm/rubies/ruby-head/lib/ruby/2.7.0/timeout.rb:99:in `block in timeout'
1: from /home/byteit101/.rvm/rubies/ruby-head/lib/ruby/2.7.0/timeout.rb:99:in `ensure in block in timeout'
/home/byteit101/.rvm/rubies/ruby-head/lib/ruby/2.7.0/timeout.rb:99:in `join': Interrupt
[1] + 13423 interrupt ruby /tmp/rng/koan.rb
$
```
The thing that is surprising to me is the explicit `print` + `inspect` works, whereas a straight `p` hangs.
--
https://bugs.ruby-lang.org/
next parent reply other threads:[~2019-09-27 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16186.20190927223437@ruby-lang.org>
2019-09-27 22:34 ` simonpatp [this message]
2019-09-29 16:40 ` [ruby-core:95146] [Ruby master Bug#16186] Calling Net::HTTP from within an #inspect implementation hang when invoked from p nobu
2019-09-29 17:31 ` [ruby-core:95147] " nobu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-16186.20190927223437.5635211c822dc769@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).