Lukas Oberhuber

I had the same behaviour when I downgraded to 0.4.1 docker-machine from a machine I'd previously upgraded to 0.5.0. I ended up rebuilding my vm. On 13 Nov 2015 00:05,...

Didn't notice this when I added my PR #917. That PR also has a breaking test. Would be very helpful for one of the two PRs to be merged.

Given the slow pace of incorporating changes, I've created a gem that patches this issue. All you have to do is include it in your `Gemfile`: ```ruby gem 'savon_fixes' ```...

This is a duplicate of #917 which has been merged (with test). This should be closed.

Given this issue is still open, and I've seen it in the wild, I've been trying to get a bit more insight into what is happening. This commentary on fixing...

This fixes the problem for Circle CI builds (thanks to Circle CI support for providing the fix!) Add these in the step in `config.yml` where you are calling `create-dmg`. It...

I'm having this exact same issue. I don't think it should only repeat on error 16.

I think the gosu osx wrappers might be for ruby 2 now, but I'm not sure. I haven't gotten it working so can't really vouch. Here's a ruby 2.1.2 wrapper:...

Is there a solution/workaround for a MacOS guest? I'm running Monterey and have seen the clock go out of sync.

For macOS guest I've used [ChronyControl](https://whatroute.net/chronycontrol.html) and then set ``` # As a VM the time can get badly out of sync. This allows big steps makestep 1 -1 ```...