Jira (PUP-8297) webrick.rb:32 {sock.accept} no longer functions in Ruby >=2.3.6

[Eric Sorenson (JIRA)]

Title: Message Title

Eric Sorenson commented on PUP-8297   Re: webrick.rb:32 {sock.accept} no longer functions in Ruby >=2.3.6 Hi Rainbow! Your change to use puppetserver is the best thing - but you're right that although webrick is deprecated it's not completely gone. That said, I couldn't reproduce this under Ruby 2.4.1p111 on macOS and Linux - I fired up a webrick server and connected to it OK ... [root@enterprise-next ~]# puppet master --no-daemonize --masterport 8141 Warning: The WEBrick Puppet master server is deprecated and will be removed in a future release. Please use Puppet Server instead. See http://links.puppet.com/deprecate-rack-webrick-servers for more information. (at /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/application/master.rb:207:in `main') Notice: Starting Puppet master version 5.3.0 Notice: Compiled catalog for enterprise-next.slice.puppetlabs.net in environment production in 5.58 seconds Notice: Caught INT; exiting [root@enterprise-next ~]# /opt/puppetlabs/puppet/bin/ruby --version ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux] Can you provide more info on a way to reproduce? Also, I couldn't tell from the ruby redmine when the accept_nonblock option was introduced - to maintain compatibility with older rubies, do you think we need to detect which version we're running under and set the option appropriately, or has it always been available (where "always" = "since 2.x")? Add Comment   This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.