V1.1 and Windows 10 issues

[tomjn]

Hey! I help run the VVV project, which relies on this project to wrangle the hosts file.

Unfortunately, recent updates to this project have broken things for Windows users of VVV

See Varying-Vagrant-Vagrants/VVV#1458

Downgrading appears to fix the issue, though new users are popping up

Of note, @AlexandroPerez, @exlame, and @benlumia007 have encountered this today

[tomjn]

As an aside, when this happens I have no prompts for debugging information to acquire that I can feed back to this project, any pointers?

[ghost]

i would like to point out, that developers should test before they deploy a fix or an update just to avoid this problem in the future. i just spent like couple of hours resetting windows 10 for no reason and at the end finding out that the hostsupdater update is the problem.

so when i got home and tested by updating to 1.1.1 and it definitely did not work properly then rollback to 1.0.2 works perfectly fine.

[cgsmith]

Thanks for alerting me to the issue @tomjn - I am not aware of any debugging options currently but I will fire up a Windows 10 instance and see what is happening. I did push a gem so users that run vagrant plugin install will receive the 1.1.1.160 version which is just a retagged 1.0.2 version. I also yanked 1.1.1 and 1.1.0 from RubyGems.org - although the mirrors may not yank them immediately.

I'll look into some automated testing for hostsupdater on a few different environments as well.

[AlexandroPerez]

@cgsmith This may also be a problem with Windows 10 braking things up as always... So for reference:

Windows 10 Version 1709 (OS Build 16299-309)

Windows 10 forced an update on me recently, so maybe things were perfectly fine before that.

[ghost]

I highly doubt that it was a Windows 10, either if it breaks or not. I have been with the Windows Insider Program testing Windows 10 since first release and I have using vvv since 1.1 sometimes Windows 10 may cause issues, but this time is not a WIndows 10 issue, its just mostly something else.

[ghost]

I also have been using Mac and Linux and Windows and sometimes the output are slightly different, but I think we should think the vvv consists of a lot of different components to make it work. but yeah.

[tomjn]

I checked my local and I'm on 1.1.1 on Mac OS with no issues, so it's likely a windows only issue

…

On Wed, 4 Apr 2018 at 06:35, Benjamin Lu ***@***.***> wrote: I also have been using Mac and Linux and Windows and sometimes the output are slightly different, but I think we should think the vvv consists of a lot of different components to make it work. but yeah. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#160 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADl56eZlOsYl0-6XBxIyG-pAJjZZAMlks5tlFuHgaJpZM4TF_uf> .

[ghost]

just tested the 1.1.1.160 and since its a retag of 1.0.2 cool. but i did test on Mac OS and yes it does not have any issues with 1.1.1 if you need me to testing i'll be happy to do so. since i do have like 10 computers :)