I got this error a few times when pulling up a VM the first time. There doesn't seem to be any non-ASCII byte in the claimed location (P203). There are no errors on vagrant reload and everything seems to be working as expected.
Description
Details
Subject | Repo | Branch | Lines +/- | |
---|---|---|---|---|
Fix for "Error: invalid byte sequence in US-ASCII in ..." | mediawiki/vagrant | master | +10 -7 |
Related Objects
Event Timeline
On a closer look, it seems provisioning was aborted because of this (but done successfully on the next vagrant provision call).
The VM in question was created via vagrant destroy; vagrant up (so the /vagrant directory wasn't clean). The version used was rMWVAe66e98bd5b5f.
Prioritizing this as low based on its intermittence but please protest if you run into it again.
I still get this every once in a while (maybe one in five times I install a box from scratch?). Not complaining about the priority since re-running vagrant provision is an easy workaround, just noting. (Looks like I am the only person affected by this, I wonder if there is something wrong with my system setup?)
Change 258740 had a related patch set uploaded (by Ori.livneh):
Fix for "Error: invalid byte sequence in US-ASCII in ..."
Via IRC:
01:45 <kartikey0303> please help me with this when i run vagrant up 01:45 <kartikey0303> stdin: is not a tty 01:45 <kartikey0303> Error: invalid byte sequence in US-ASCII at /vagrant/puppet/modules/hhvm/manifests/init.pp:1 on node mediawiki-vagrant 01:45 <kartikey0303> Wrapped exception: 01:45 <kartikey0303> invalid byte sequence in US-ASCII 01:45 <kartikey0303> Error: invalid byte sequence in US-ASCII at /vagrant/puppet/modules/hhvm/manifests/init.pp:1 on node mediawiki-vagrant
I poked around a bit and found:
Change 258740 merged by jenkins-bot:
Fix for "Error: invalid byte sequence in US-ASCII in ..."