{"action":"created","issue":{"url":"https://api.github.com/repos/BerlinVagrant/vagrant-dns/issues/59","repository_url":"https://api.github.com/repos/BerlinVagrant/vagrant-dns","labels_url":"https://api.github.com/repos/BerlinVagrant/vagrant-dns/issues/59/labels{/name}","comments_url":"https://api.github.com/repos/BerlinVagrant/vagrant-dns/issues/59/comments","events_url":"https://api.github.com/repos/BerlinVagrant/vagrant-dns/issues/59/events","html_url":"https://github.com/BerlinVagrant/vagrant-dns/issues/59","id":306495478,"number":59,"title":"Problems with async-io ^1.3?","user":{"login":"mpdude","id":1202333,"avatar_url":"https://avatars0.githubusercontent.com/u/1202333?v=4","gravatar_id":"","url":"https://api.github.com/users/mpdude","html_url":"https://github.com/mpdude","followers_url":"https://api.github.com/users/mpdude/followers","following_url":"https://api.github.com/users/mpdude/following{/other_user}","gists_url":"https://api.github.com/users/mpdude/gists{/gist_id}","starred_url":"https://api.github.com/users/mpdude/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mpdude/subscriptions","organizations_url":"https://api.github.com/users/mpdude/orgs","repos_url":"https://api.github.com/users/mpdude/repos","events_url":"https://api.github.com/users/mpdude/events{/privacy}","received_events_url":"https://api.github.com/users/mpdude/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":4,"created_at":"2018-03-19T14:51:09Z","updated_at":"2018-04-11T10:51:10Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"I just upgraded to Vagrant 2.0.3 and since then had issues starting VMs and/or resolving DNS names provided by vagrant-dns. From skimming Vagrant debug output, I am under the impression that this plugin might have something to do with it. But I am not a Ruby developer, so I might be entirely wrong.\r\n\r\nSo, in order to fix it, I first tried `vagrant plugin expunge`, which re-installed all plugins and dependencies as follows:\r\n\r\n```\r\nFetching: vagrant-bindfs-1.1.0.gem (100%)\r\nFetching: vagrant-disksize-0.1.2.gem (100%)\r\nFetching: daemons-1.2.6.gem (100%)\r\nFetching: nio4r-2.3.0.gem (100%)\r\nBuilding native extensions.  This could take a while...\r\nFetching: hitimes-1.2.6.gem (100%)\r\nBuilding native extensions.  This could take a while...\r\nFetching: timers-4.1.2.gem (100%)\r\nFetching: async-1.3.0.gem (100%)\r\nFetching: async-io-1.4.0.gem (100%)\r\nFetching: async-dns-1.0.0.gem (100%)\r\nFetching: rubydns-2.0.1.gem (100%)\r\nFetching: vagrant-dns-2.1.0.gem (100%)\r\nFetching: vagrant-hostsupdater-1.0.2.gem (100%)\r\nFetching: bundler-1.16.1.gem (100%)\r\nFetching: vagrant-triggers-0.5.3.gem (100%)\r\nInstalled the plugin 'vagrant-bindfs (1.1.0)'!\r\nInstalling the 'vagrant-disksize' plugin. This can take a few minutes...\r\nInstalled the plugin 'vagrant-disksize (0.1.2)'!\r\nInstalling the 'vagrant-dns' plugin. This can take a few minutes...\r\n\r\nInstalled the plugin 'vagrant-dns (2.1.0)'!\r\nInstalling the 'vagrant-hostsupdater' plugin. This can take a few minutes...\r\nInstalled the plugin 'vagrant-hostsupdater (1.0.2)'!\r\nInstalling the 'vagrant-triggers' plugin. This can take a few minutes...\r\nInstalled the plugin 'vagrant-triggers (0.5.3)'!\r\n```\r\n\r\nThen, `vagrant dns --start --ontop` gives me:\r\n\r\n```\r\n/Users/mp/.vagrant.d/gems/2.4.3/gems/async-dns-1.0.0/lib/async/dns/server.rb:128:in `block in setup_handlers': undefined method `socket_type' for #<Async::IO::HostEndpoint:0x0000000102870f70> (NoMethodError)\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/async-io-1.4.0/lib/async/io/endpoint.rb:66:in `block in each'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/async-io-1.4.0/lib/async/io/endpoint.rb:62:in `each'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/async-io-1.4.0/lib/async/io/endpoint.rb:62:in `each'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/async-dns-1.0.0/lib/async/dns/server.rb:127:in `setup_handlers'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/async-dns-1.0.0/lib/async/dns/server.rb:109:in `run'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/rubydns-2.0.1/lib/rubydns.rb:39:in `run_server'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/vagrant-dns-2.1.0/lib/vagrant-dns/service.rb:38:in `block in run!'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/daemons-1.2.6/lib/daemons/application.rb:270:in `block in start_proc'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/daemons-1.2.6/lib/daemons/application.rb:279:in `start_proc'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/daemons-1.2.6/lib/daemons/application.rb:300:in `start'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/daemons-1.2.6/lib/daemons/controller.rb:56:in `run'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/daemons-1.2.6/lib/daemons.rb:197:in `block in run_proc'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/daemons-1.2.6/lib/daemons/cmdline.rb:92:in `catch_exceptions'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/daemons-1.2.6/lib/daemons.rb:196:in `run_proc'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/vagrant-dns-2.1.0/lib/vagrant-dns/service.rb:31:in `run!'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/vagrant-dns-2.1.0/lib/vagrant-dns/service.rb:17:in `start!'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/vagrant-dns-2.1.0/lib/vagrant-dns/command.rb:105:in `manage_service'\r\n\tfrom /Users/mp/.vagrant.d/gems/2.4.3/gems/vagrant-dns-2.1.0/lib/vagrant-dns/command.rb:77:in `execute'\r\n\tfrom /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/cli.rb:46:in `execute'\r\n\tfrom /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/lib/vagrant/environment.rb:269:in `cli'\r\n\tfrom /opt/vagrant/embedded/gems/2.0.3/gems/vagrant-2.0.3/bin/vagrant:151:in `<main>'\r\n```\r\n\r\nThis leads us to `async-dns`, where I found https://github.com/socketry/async-dns/issues/6.\r\n\r\nSo – I am dropping this here to 1) let you know and 2) kindly as whether there is anything you can to to quickly work around this, for example by forcing the `async-dns` dependency < 1.3?\r\n\r\nThanks!\r\n"},"comment":{"url":"https://api.github.com/repos/BerlinVagrant/vagrant-dns/issues/comments/380410150","html_url":"https://github.com/BerlinVagrant/vagrant-dns/issues/59#issuecomment-380410150","issue_url":"https://api.github.com/repos/BerlinVagrant/vagrant-dns/issues/59","id":380410150,"user":{"login":"ioquatix","id":30030,"avatar_url":"https://avatars1.githubusercontent.com/u/30030?v=4","gravatar_id":"","url":"https://api.github.com/users/ioquatix","html_url":"https://github.com/ioquatix","followers_url":"https://api.github.com/users/ioquatix/followers","following_url":"https://api.github.com/users/ioquatix/following{/other_user}","gists_url":"https://api.github.com/users/ioquatix/gists{/gist_id}","starred_url":"https://api.github.com/users/ioquatix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ioquatix/subscriptions","organizations_url":"https://api.github.com/users/ioquatix/orgs","repos_url":"https://api.github.com/users/ioquatix/repos","events_url":"https://api.github.com/users/ioquatix/events{/privacy}","received_events_url":"https://api.github.com/users/ioquatix/received_events","type":"User","site_admin":false},"created_at":"2018-04-11T10:51:10Z","updated_at":"2018-04-11T10:51:10Z","author_association":"CONTRIBUTOR","body":"I apologise for this issue. It's my fault.\r\n\r\nI will investigate the issue and report back.\r\n\r\nYes, there were some \"internal\" API changes, but it did require both gems to be updated. Perhaps I should have bumped major version, but I considered it to be implementation detail.\r\n"}}
{"actor":{"display_login":"ioquatix"}}