Machine didn't return an IP after 120 seconds, aborting - even with HyperV disabled

Hi, guys,
I've tried all the approaches discussed previously and I'm still getting a "Machine didn't return an IP after 120 seconds, aborting". [The same was mentioned in #29 but any information there fixed my problem]
About what I've done:
docker --version
Docker version 17.03.0-ce, build 60ccb22

docker-compose --version
docker-compose version 1.11.2, build f963d76f

docker-machine --version
docker-machine.exe version 0.10.0, build 76ed2a6

VMware Workstation version: 12.5.7 build-5813279
After that as admin and as ordinary user I tried (the following command was executed with and without disk size):
docker-machine -D create --driver=vmwareworkstation --vmwareworkstation-disk-size 30000 dev

Docker Machine Version:  0.10.0, build 76ed2a6
Found binary path at C:\dev\docker-machine\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
Plugin server listening at address <IP_ADDRESS>:50186
() DBG | Unable to read registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\vmware.exe\Path
() DBG | Error finding VMware root: The system cannot find the file specified.
() DBG | File not found: 'vmrun.exe'
() DBG | Unable to read registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\vmware.exe\Path
() DBG | Error finding VMware root: The system cannot find the file specified.
() DBG | File not found: 'vmware-vdiskmanager.exe'
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(flag-lookup) Calling .GetMachineName
(flag-lookup) Calling .DriverName
(flag-lookup) Calling .GetCreateFlags
Found binary path at C:\dev\docker-machine\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
Plugin server listening at address <IP_ADDRESS>:50190
() DBG | Unable to read registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\vmware.exe\Path
() DBG | Error finding VMware root: The system cannot find the file specified.
() DBG | File not found: 'vmrun.exe'
() DBG | Unable to read registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\vmware.exe\Path
() DBG | Error finding VMware root: The system cannot find the file specified.
() DBG | File not found: 'vmware-vdiskmanager.exe'
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(dev) Calling .GetMachineName
(dev) Calling .DriverName
(dev) Calling .GetCreateFlags
(dev) Calling .SetConfigFromFlags
Running pre-create checks...
(dev) Calling .PreCreateCheck
(dev) DBG | local Boot2Docker ISO version:  v17.06.0-ce
(dev) Calling .GetConfigRaw
Creating machine...
(dev) Calling .Create
(dev) DBG | local Boot2Docker ISO version:  v17.06.0-ce
(dev) Copying C:\Users\fernando.barbeiro\.docker\machine\cache\boot2docker.iso to C:\Users\fernando.barbeiro\.docker\machine\machines\dev\boot2docker.iso...
(dev) Creating SSH key...
(dev) Creating VM...
(dev) Starting dev...
(dev) DBG | executing:  start C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx nogui
(dev) Waiting for VM to come online...
(dev) DBG | Not there yet 1/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 2/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 3/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 4/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 5/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 6/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 7/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 8/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 9/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 10/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 11/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 12/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 13/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 14/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 15/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 16/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 17/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 18/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 19/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 20/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 21/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 22/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 23/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 24/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 25/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 26/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 27/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 28/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 29/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 30/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 31/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 32/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 33/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 34/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 35/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 36/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 37/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 38/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 39/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 40/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 41/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 42/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 43/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 44/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 45/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 46/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 47/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 48/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 49/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 50/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 51/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 52/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 53/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 54/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 55/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 56/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 57/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 58/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 59/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 60/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting
notifying bugsnag: [Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting]

As shown, the log Error finding VMware root: The system cannot find the file specified presents some info that could be useful. [Silly question] Could it related to the fact that VMWare is installed in a non-usual path?
Apart from that,

Hyper-V is disabled, so I don't think this could be causing much trouble as aforementioned in #29 .
The dev.vmx:
.encoding = "UTF-8"
config.version = "8"
displayName = "dev"
ethernet0.present = "TRUE"
ethernet0.connectionType = "nat"
ethernet0.virtualDev = "vmxnet3"
ethernet0.wakeOnPcktRcv = "FALSE"
ethernet0.addressType = "generated"
ethernet0.linkStatePropagation.enable = "TRUE"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "160"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "192"
sound.pciSlotNumber = "33"
vmci0.pciSlotNumber = "35"
sata0.pciSlotNumber = "36"
floppy0.present = "FALSE"
guestOS = "other3xlinux-64"
hpet0.present = "TRUE"
sata0.present = "TRUE"
sata0:1.present = "TRUE"
sata0:1.fileName = "C:\Users\fernando.barbeiro\.docker\machine\machines\dev\boot2docker.iso"
sata0:1.deviceType = "cdrom-image"

vmci0.present = "TRUE"
mem.hotadd = "TRUE"
memsize = "1024"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.reset = "soft"
powerType.suspend = "soft"
scsi0.present = "TRUE"
scsi0.virtualDev = "pvscsi"
scsi0:0.fileName = "dev.vmdk"
scsi0:0.present = "TRUE"
virtualHW.productCompatibility = "hosted"
virtualHW.version = "10"
msg.autoanswer = "TRUE"
uuid.action = "create"
numvcpus = "1"
hgfs.mapRootShare = "FALSE"
hgfs.linkRootShare = "FALSE"

P.S.: I reinstalled the whole environment in order to try to overcome this, but so far I'm not being capable to solve.
Any clue on this issue would be more than appreciated.
Thanks in advance,
Regards.
Fernando Barbeiro

can you run this please from powershell ?!
if (!(Test-Path "HKCR:\")) { $NewPSDrive = New-PSDrive -Name HKCR -PSProvider Registry -Root HKEY_CLASSES_ROOT }
if (!($VMware_Path = Get-ItemProperty HKCR:\Applications\vmware.exe\shell\open\command -ErrorAction SilentlyContinue))
        {
	    Write-Error "VMware Binaries not found from registry"
        }
else
{
$VMware_Path
}

and give the output :-)

I don't believe it's the path as https://github.com/pecigonzalo/docker-machine-vmwareworkstation/blob/9f849d6afe1d13d77083048923c51f9c17375d59/vmrun.go#L156 should catch that.
Questions:

Can you start VMs manually on VMWare?
Do you see the VM running? (you can try to open VMWare Workstation and "Open" the VM by opening the .vmx file)

The problem seems to be "similar" as the mac line is not present ethernet0.generatedAddress.

Hi folks,
Here it goes the powershell results:

Although I reinstalled the VMWare as Admin, this command still returned Binaries not found. Buuut,
Questions:
Can you start VMs manually on VMWare?
Yes, I run  vmrun -T player start ./VM\ Automa.vmx and another VM that I have here started well.
Do you see the VM running? (you can try to open VMWare Workstation and "Open" the VM by opening the .vmx file)
Yes, indeed, with the same vmx that I did mention in first question.

Regards.

[Complementary info]
If I try to run a machine created via docker-machine -D create --driver=vmwareworkstation ...  command, the answer for @pecigonzalo is No, in both cases. I'm not able to run them neither from command line nor from VMWare Workstation.
fernando.barbeiro@BCN-DSK-0055 MINGW64 ~/.docker/machine/machines/devNewTest
$ ls
boot2docker.iso  config.json  devNewTest.vmsd  devNewTest.vmx  devNewTest.vmx~  devNewTest.vmxf  id_rsa  id_rsa.pub

fernando.barbeiro@BCN-DSK-0055 MINGW64 ~/.docker/machine/machines/devNewTest
$ vmrun -T player start ./VM\ ./devNewTest.vmx
Error: Cannot open VM: C:\Users\fernando.barbeiro\.docker\machine\machines\devNewTest\VM \devNewTest.vmx, The virtual machine cannot be found

@fernandoabcampos I missed this from the logs (sorry, was on mobile) but this is probably it
() DBG | Unable to read registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\vmware.exe\Path
() DBG | Error finding VMware root: The system cannot find the file specified.
() DBG | File not found: 'vmrun.exe'
() DBG | Unable to read registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\vmware.exe\Path
() DBG | Error finding VMware root: The system cannot find the file specified.
() DBG | File not found: 'vmware-vdiskmanager.exe'

No problem at all @pecigonzalo
So I suppose it might be related to my local VMware installation. I'll try to have a look and find a solution.

Its odd that it can't find the keys in the registry, as they should exist always AFAIK. Maybe you can manually check for them or as a test create them, to verify that works.
We should terminate execution when they are not found, ill do a PR from this issue to terminate and report the error instead silently failing.

OK @pecigonzalo, thanks.
In the meantime, I'll be checking if I can find my local environment issue (and when I find, I'll comment here just in case someone else walks through the same).

@fernandoabcampos as a test, could you set the env VMWARE_HOME to the path where vmrun.exe is before running docker-machine ?

Sure, the results:
fernando.barbeiro@MACHINE MINGW64 ~
$ env | grep VMWARE
VMWARE_HOME=C:\Program Files (x86)\VMware\VMware VIX

fernando.barbeiro@MACHINE MINGW64 ~
$ docker-machine -D create --driver=vmwareworkstation --vmwareworkstation-disk-size 30000 dev
Docker Machine Version:  0.10.0, build 76ed2a6
Found binary path at C:\dev\docker-machine\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
() DBG | Unable to read registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\vmware.exe\Path
() DBG | Error finding VMware root: The system cannot find the file specified.
() DBG | File not found: 'vmware-vdiskmanager.exe'
Plugin server listening at address <IP_ADDRESS>:52141
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(flag-lookup) Calling .GetMachineName
(flag-lookup) Calling .DriverName
(flag-lookup) Calling .GetCreateFlags
Found binary path at C:\dev\docker-machine\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
Plugin server listening at address <IP_ADDRESS>:52145
() DBG | Unable to read registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\vmware.exe\Path
() DBG | Error finding VMware root: The system cannot find the file specified.
() DBG | File not found: 'vmware-vdiskmanager.exe'
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(dev) Calling .GetMachineName
(dev) Calling .DriverName
(dev) Calling .GetCreateFlags
(dev) Calling .SetConfigFromFlags
Running pre-create checks...
(dev) Calling .PreCreateCheck
(dev) DBG | local Boot2Docker ISO version:  v17.06.0-ce
(dev) Calling .GetConfigRaw
Creating machine...
(dev) Calling .Create
(dev) DBG | local Boot2Docker ISO version:  v17.06.0-ce
(dev) Copying C:\Users\fernando.barbeiro\.docker\machine\cache\boot2docker.iso to C:\Users\fernando.barbeiro\.docker\machine\machines\dev\boot2docker.iso...
(dev) Creating SSH key...
(dev) Creating VM...
(dev) DBG | executing: C:\Program Files (x86)\VMware\VMware VIX\vmrun.exe start C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx nogui
(dev) Starting dev...
(dev) Waiting for VM to come online...
(dev) DBG | Not there yet 1/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 2/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 3/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 4/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 5/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 6/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 7/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 8/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 9/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 10/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 11/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 12/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 13/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 14/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 15/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 16/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 17/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 18/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 19/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 20/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 21/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 22/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 23/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 24/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 25/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 26/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 27/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 28/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 29/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 30/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 31/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 32/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 33/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 34/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 35/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 36/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 37/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 38/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 39/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 40/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 41/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 42/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 43/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 44/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 45/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 46/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 47/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 48/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 49/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 50/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 51/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 52/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 53/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 54/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 55/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 56/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 57/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 58/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 59/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
(dev) DBG | Not there yet 60/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev\dev.vmx
Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting
notifying bugsnag: [Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting]

Unfortunately, the same.

But it did find vmrun.exe on this instance, its missing vmware-vdiskmanager.exe can you check where is that in your system?

Hi guys, update:
You're right, vmware-vdiskmanager.exe wasn't installed. Either I missed something from your doc or my installation was incomplete. Anyway, I downloaded from VMWare website a VMware-vix-disklib-5.1.0-774844.i386.exe and after installing it, the error (missing vmware-vdiskmanager.exe) disappeared.
The new log:
docker-machine -D create --driver=vmwareworkstation --vmwareworkstation-disk-size 30000 dev3
Docker Machine Version:  0.10.0, build 76ed2a6
Found binary path at C:\dev\docker-machine\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
Plugin server listening at address <IP_ADDRESS>:63709
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(flag-lookup) Calling .GetMachineName
(flag-lookup) Calling .DriverName
(flag-lookup) Calling .GetCreateFlags
Found binary path at C:\dev\docker-machine\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
Plugin server listening at address <IP_ADDRESS>:63714
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(dev3) Calling .GetMachineName
(dev3) Calling .DriverName
(dev3) Calling .GetCreateFlags
(dev3) Calling .SetConfigFromFlags
Running pre-create checks...
(dev3) Calling .PreCreateCheck
(dev3) DBG | local Boot2Docker ISO version:  v17.06.0-ce
(dev3) Calling .GetConfigRaw
Creating machine...
(dev3) Calling .Create
(dev3) DBG | local Boot2Docker ISO version:  v17.06.0-ce
(dev3) Copying C:\Users\fernando.barbeiro\.docker\machine\cache\boot2docker.iso to C:\Users\fernando.barbeiro\.docker\machine\machines\dev3\boot2docker.iso...
(dev3) Creating SSH key...
(dev3) Creating VM...
(dev3) DBG | SSLLoadSharedLibraries: Failed to load OpenSSL libraries. libdir is (null)
(dev3) DBG | Win32 object usage: GDI 4, USER 1
(dev3) DBG | CoreDump: Writing minidump to C:\Users\FERNAN~1.BAR\AppData\Local\Temp\vmware-fernando.barbeiro\vmware-vdiskmanager-14276.dmp
(dev3) Starting dev3...
(dev3) DBG | executing: C:\Program Files (x86)\VMware\VMware VIX\vmrun.exe start C:\Users\fernando.barbeiro\.docker\machine\machines\dev3\dev3.vmx nogui
(dev3) Waiting for VM to come online...
(dev3) DBG | Not there yet 1/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev3\dev3.vmx
(dev3) DBG | Not there yet 2/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev3\dev3.vmx
(dev3) DBG | Not there yet 3/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev3\dev3.vmx

I know that you've dedicated some time helping me out to investigate, but now, as it seems to be more related to VMWare / my environment and it is not strictly required for what I'm doing, I'm about to adopt another strategy and generate the docker-machines with virtualbox.

Did you let it run till the end?

Sorry, I didn't mention it - yes I let it run until the end.
 ... (dev3) DBG | Not there yet 57/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev3\dev3.vmx (dev3) DBG | Not there yet 58/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev3\dev3.vmx (dev3) DBG | Not there yet 59/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev3\dev3.vmx (dev3) DBG | Not there yet 60/60, error: couldn't find MAC address in VMX file C:\Users\fernando.barbeiro\.docker\machine\machines\dev3\dev3.vmx Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting notifying bugsnag: [Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting]

@fernandoabcampos  Maybe you can try to run the commands in the Administrator mode and then see what happens.

Hi guys, I getting the same timeout after 2min msg as @fernandoabcampos
EXCEPT i hv multiple ws8 vm's running on win 7 successfully.
YES I ran cmd as admin
HOWEVER i get this msg when running
C:\Windows\system32>docker ps
error during connect: Get https://colindnz-pc:2376/v1.32/containers/json:
dial tcp [fe80::ac67:68ce:62dc:49cd%VMware Network Adapter VMnet1]:2376:
connectex: No connection could be made because the target machine actively refused it.
HENCE i was trying to "work around" that problem by trying
C:\Windows\system32>docker-machine --debug --native-ssh create -d vmwareworkstation debug-me
Docker Machine Version:  0.8.2, build e18a919
Found binary path at C:\ProgramData\chocolatey\bin\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
Plugin server listening at address <IP_ADDRESS>:5329
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(flag-lookup) Calling .GetMachineName
(flag-lookup) Calling .DriverName
(flag-lookup) Calling .GetCreateFlags
Found binary path at C:\ProgramData\chocolatey\bin\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
Plugin server listening at address <IP_ADDRESS>:5333
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(debug-me) Calling .GetMachineName
(debug-me) Calling .DriverName
(debug-me) Calling .GetCreateFlags
(debug-me) Calling .SetConfigFromFlags
Running pre-create checks...
(debug-me) Calling .PreCreateCheck
(debug-me) DBG | local Boot2Docker ISO version:  v17.09.0-ce
(debug-me) Calling .GetConfigRaw
Creating machine...
(debug-me) Calling .Create
(debug-me) DBG | local Boot2Docker ISO version:  v17.09.0-ce
(debug-me) Copying C:\Users\ColinDNZ.docker\machine\cache\boot2docker.iso to C:\Users\ColinDNZ.docker\machine\machines\debug-me\boot2docker.iso...
(debug-me) Creating SSH key...
(debug-me) Creating VM...
(debug-me) Creating disk 'C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmdk'
(debug-me) Virtual disk creation successful.
(debug-me) Starting debug-me...
(debug-me) DBG | executing: C:\Program Files (x86)\VMware\VMware VIX\vmrun.exe start C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx nogui
(debug-me) Waiting for VM to come online...
(debug-me) DBG | Not there yet 1/60, error: couldn't find MAC address in VMX fil
e C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx
(debug-me) DBG | Not there yet 2/60, error: couldn't find MAC address in VMX fil
e C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx
(debug-me) DBG | Not there yet 3/60, error: couldn't find MAC address in VMX fil
e C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx
(debug-me) DBG | Not there yet 4/60, error: couldn't find MAC address in VMX fil
e C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx
(debug-me) DBG | Not there yet 5/60, error: couldn't find MAC address in VMX fil
e C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx
(debug-me) DBG | Not there yet 6/60, error: couldn't find MAC address in VMX fil
e C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmxess in VMX fil
...
(debug-me) DBG | Not there yet 57/60, error: couldn't find MAC address in VMX fi
le C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx
(debug-me) DBG | Not there yet 58/60, error: couldn't find MAC address in VMX fi
le C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx
(debug-me) DBG | Not there yet 59/60, error: couldn't find MAC address in VMX fi
le C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx
(debug-me) DBG | Not there yet 60/60, error: couldn't find MAC address in VMX fi
le C:\Users\ColinDNZ.docker\machine\machines\debug-me\debug-me.vmx
Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting
notifying bugsnag: [Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting]
I don't yet understand how docker works with certs or networks
so any thoughts would be appreciated
tia
Colin

I do hv
DOCKER_CERT_PATH set to %USERPROFILE%.docker\machine\certs

I should mention docker installed & run using chocolatey
and this msg produces an interesting variation
C:\Users\ColinDNZ>docker version
Client:
Version:      17.09.0-ce
API version:  1.32
Go version:   go1.8.3
Git commit:   afdb6d4
Built:        Tue Sep 26 22:40:09 2017
OS/Arch:      windows/amd64
error during connect: Get https://colindnz-pc:2376/v1.32/version: dial tcp [fe80
::ac67:68ce:62dc:49cd%VMware Network Adapter VMnet1]:2376:
connectex: No connection could be made because the target machine actively refused it.
I don't know enough to know what this tells me

reinstall Docker & DockerMachine
https://github.com/pecigonzalo/docker-machine-vmwareworkstation
DockerToolbox.exe /COMPONENTS="Docker,DockerMachine"
try again
docker-machine create --driver=vmwareworkstation play
same problem after 2min no ip
tried
C:\Users\ColinDNZ\mapped\zip\docker>docker info
time="2017-10-17T15:27:21+13:00" level=warning msg="Unable to use system certificate pool:
crypto/x509: system root pool is not available on Windows"
error during connect: Get https://colindnz-pc:2376/v1.26/info: dial tcp
[fe80::ac67:68ce:62dc:49cd%VMware Network Adapter VMnet1]:2376:
connectex: No connection could be made because the target machine actively refused it.
this time re-install has reset cert links
same msg occurs

Don't know if that helps here, but I got the same problem that docker-machine couldn't find an IP address after 120 seconds. I turned out that our new company notebooks don't have the virtualization (vTX vTD) settings activated in BIOS. I also couldn't start any VMware VM manually. But at least this is one thing to check.

Unfortunately, I have been quite busy to answer all questions here, but lets separate the issues please.
If you cant run the VM from your command line and/or manually then it is not a problem with this repository, its a problem with your setup.
@colindnz Please dont put 3 messages one after the other and use Markdown formatting to make it more readable, otherwise its hard to understand your issue.
The if the docker-macine driver failed, then you are not going to get anything from docker, as its not started.
As a general statement, there could be 2 things happening here.
A) VM Started but does not get an IP, most likely it is not related to this repo and you have to troubleshoot your setup first.
B) VM is not started, either because the driver cant find the executable/can run it or because your machine cant strart VMs. If its the second option, its not related to this repo and you have to troubleshoot your setup.
First please verify the machine starts:

Do you see it running in your task manager?
Can you open the .vmx with the VMWare Workstation console and see the boot2docker console logs?

In my case VIX was missing

Same problem and fixed
after enable debug log, I found a vmrun command, then I run vmrun.exe directly:
C:\Program Files\Docker Toolbox>"C:\Program Files (x86)\VMware\VMware VIX\vmrun.exe" start C:\Users\dd-han\.docker\machine\machines\dev\dev.vmx nogui
Unable to connect to host.
Error: The specified version was not found

found this post, and open vixwrapper-config.txt
no version setting for version I using (14.0.0), so I back to vmware website download to download VIX match for my player.
and it works now.

Posting the same info here that I posted over @ the Docker-Machine and Powershell/OpenSSH teams to collaborate on the final solution but I also provide a tested workaround.  This issue has plagued us and gone all the way back over three years to when Docker was first released and I have uncovered the root cause.
So for those of you like the OP having the dreaded (120 seconds....) or any one of the other failures (it's amazing how Kitematic INSTANTLY worked for the very FIRST time ever on my Win7 systems after implementing this workaround) - read and watch my screencast reproduction showing the root cause, and give the workaround a try if nothing else is working and I bet it also resolves your issue.
NOTE:  I did not even think to add all the related issues here and on all the other child Docker-Machine-*DRIVER* repos that when you see my live demo of the issue reproduced will clearly see - have been cascading down and, due to it affecting the underlying Docker engine's operations, been the root cause of many of these terminating timeouts and other errors just like this one.  I'm sure that would also add quite a few to the list below.

Background
There have been Github issues opened and subsequently closed dating all the way back to ISSUE #66 - very soon after the initial release yet closed.  Many of these appear to be reproducible under this issue's cause or in some way related to this issue:

https://github.com/docker/toolbox/issues/66
https://github.com/docker/machine/issues/4447
https://github.com/docker/toolbox/issues/547
https://github.com/docker/toolbox/issues/116
https://github.com/docker/toolbox/issues/153
https://github.com/docker/toolbox/issues/473
https://github.com/docker/toolbox/issues/329
https://github.com/docker/machine/issues/986
https://github.com/docker/machine/issues/732

And the Docker forums:

https://forums.docker.com/t/windows-unable-to-quickstart/12536
https://forums.docker.com/t/windows-unable-to-start-docker/12563
https://forums.docker.com/t/error-getting-ip-address-something-went-wrong-running-an-ssh-command/15413
https://www.bountysource.com/issues/43180735-cannot-run-docker-from-windows
https://www.bountysource.com/issues/27997258-error-creating-machine-error-in-driver-during-machine-creation-maximum-number-of-retries-5-exceeded
https://www.bountysource.com/issues/27997258-error-creating-machine-error-in-driver-during-machine-creation-maximum-number-of-retries-5-exceeded

And let's not forget all of StackOverflow sites (I'm only posting a couple but there are MANY):

https://stackoverflow.com/questions/40378725/docker-quickstart-terminal-exit-status-255
https://superuser.com/questions/996785/docker-toolbox-error-creating-machine-error-in-driver-during-machine-creation

Also, this issue's root cause is also responsible for all these Kitematic issues including:

https://github.com/docker/kitematic/issues/862
https://github.com/docker/kitematic/issues/1029

And if that is not enough, just run these two Google searches below, and you can bet that most if not all those hits with these "mystery" 255/timeouts/nondescriptive are also this issue:

https://www.google.com/search?q="Could not determine IP from docker-machine"
https://www.google.com/search?q=docker-machine ssh exit status 255

Issue(s)

Management of Docker using Docker-Machine on Windows is impossible using the native shells of Powershell and CMD under certain conditions.

Management of Docker using Docker-Machine on any OS may fail with recurring SSH errors.

Cause
Incompatible SSH client implementation.
Tests were run from the current beta release of OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4 OpenSSH-Win32 all the way back to OpenSSH_7.1p1 Microsoft Pragma Win32 port Oct 7 2015, OpenSSL 1.0.2d 9 Jul 2015 all tested versions exhibited this behavior.
Something in the call to "ip addr show" and possibly other operations from Docker-Machine are being interpreted incorrectly resulting in a terminating error.  This prevents any successful Docker operations using either native shell in Windows.
This is becoming a bigger and bigger issue now since the incompatible client is automatically installed with Powershell and Chocolatey and added to the system path.  The presence and priority in the system path can be changed and in such is the reason this issue does not appear to plague everyone on Windows and has been so difficult to troubleshoot.
Because the Mingwin bash shell relies on the separately installed Git SSH client, the QuickStart Terminal (usually) works which also had added to the difficulty in troubleshooting.  However, once you move to native shells to manage the containers created with the QuickStart terminal, the system path will quickly prioritize the problematic SSH client and cause failures.
Based on testing I would recommend until full resolution that this could possibly be utilized as an accurate statement that sums up in one paragraph the current status of this issue:
Due to current incompatibilities, it is impossible for a user running any version of OpenSSH-Win32, installed by default with Powershell & Chocolatey, to install any version of Docker-Toolbox and utilize the native two shells (Powershell and CMD) to manage Docker without first taking action to disable OpenSSH-Win32 as the system default SSH client.

Note that the real solution is (and I am also immediately opening a Github issue there as well) for the Powershell team now maintaining the OpenSSH for Windows project to work with the Docker team to capture the low-level debug output from OpenSSH back to Docker-Machine's call to "ip addr show" (and other commands) to determine what on earth is being interpreted as a bad return, despite as I demonstrated the command clearly returning successfully the exact same output as the versions using OpenSSL instead of LibreSSL, and the connection via TLS being successful in all versions.
Issue Reproduction

Workaround
Until the root cause of the incompatibility with the OpenSSH-Win32 client can be addressed, there is only one workaround that has been successfully tested.
Both the SYSTEM and USER environment variable for PATH must be edited and any references to OpenSSH-Win32 (Default path of C:\Program Files\OpenSSH-Win64) must be moved BELOW another compatible SSH client.  For example, the Git installed version is compatible so if Git were installed the path of C:\Program Files\Git\usr\bin should be moved before the OpenSSH version.
After making this change, a reboot is recommended.

The original issue #'s to hopefully track progress on a real fix are over here:
https://github.com/docker/machine/issues/4483
https://github.com/PowerShell/Win32-OpenSSH/issues/1155

the same issue.
My system is win7, run with DockerToolBox and vmware driver, my vmware version is 14 pro.

Hi
Try to open docker-machine in vmware too. It never is able to find the IP address. Have changed the default NAT setting that docker-machine creates to Bridged with no difference:
λ docker-machine -D create --driver=vmwareworkstation dev
Docker Machine Version:  0.16.0, build 702c267f
Found binary path at c:\WINPROGS\docker-machine-driver\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
Plugin server listening at address <IP_ADDRESS>:50227
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(flag-lookup) Calling .GetMachineName
(flag-lookup) Calling .DriverName
(flag-lookup) Calling .GetCreateFlags
Found binary path at c:\WINPROGS\docker-machine-driver\docker-machine-driver-vmwareworkstation.exe
Launching plugin server for driver vmwareworkstation
Plugin server listening at address <IP_ADDRESS>:50231
() Calling .GetVersion
Using API Version  1
() Calling .SetConfigRaw
() Calling .GetMachineName
(dev) Calling .GetMachineName
(dev) Calling .DriverName
(dev) Calling .GetCreateFlags
(dev) Calling .SetConfigFromFlags
Reading certificate data from C:\Users\mhpedersen\.docker\machine\certs\ca.pem
Decoding PEM data...
Parsing certificate...
Reading certificate data from C:\Users\mhpedersen\.docker\machine\certs\cert.pem
Decoding PEM data...
Parsing certificate...
Running pre-create checks...
(dev) Calling .PreCreateCheck
(dev) DBG | local Boot2Docker ISO version:  v18.09.0
(dev) Calling .GetConfigRaw
Creating machine...
(dev) Calling .Create
(dev) DBG | local Boot2Docker ISO version:  v18.09.0
(dev) Copying C:\Users\mhpedersen\.docker\machine\cache\boot2docker.iso to C:\Users\mhpedersen\.docker\machine\machines\dev\boot2docker.iso...
(dev) Creating SSH key...
(dev) Creating VM...
(dev) DBG | VixDiskLib: Invalid configuration file parameter.  Failed to read configuration file.
(dev) Creating disk 'C:\Users\mhpedersen\.docker\machine\machines\dev\dev.vmdk'
(dev) Virtual disk creation successful.
(dev) Starting dev...
(dev) DBG | executing: C:/Program Files (x86)/VMware/VMware Workstation/vmrun.exe start C:\Users\mhpedersen\.docker\machine\machines\dev\dev.vmx nogui
(dev) Waiting for VM to come online...
(dev) DBG | MAC address in VMX: 00:0c:29:ad:0f:8b
(dev) DBG | Not there yet 1/60, error: IP not found for MAC 00:0c:29:ad:0f:8b in DHCP leases
(dev) DBG | MAC address in VMX: 00:0c:29:ad:0f:8b
(dev) DBG | Not there yet 2/60, error: IP not found for MAC 00:0c:29:ad:0f:8b in DHCP leases
(dev) DBG | MAC address in VMX: 00:0c:29:ad:0f:8b
(dev) DBG | Not there yet 3/60, error: IP not found for MAC 00:0c:29:ad:0f:8b in DHCP leases
(dev) DBG | MAC address in VMX: 00:0c:29:ad:0f:8b
(dev) DBG | Not there yet 4/60, error: IP not found for MAC 00:0c:29:ad:0f:8b in DHCP leases
(dev) DBG | MAC address in VMX: 00:0c:29:ad:0f:8b
(dev) DBG | Not there yet 5/60, error: IP not found for MAC 00:0c:29:ad:0f:8b in DHCP leases
(dev) DBG | MAC address in VMX: 00:0c:29:ad:0f:8b
(dev) DBG | Not there yet 6/60, error: IP not found for MAC 00:0c:29:ad:0f:8b in DHCP leases
(dev) DBG | MAC address in VMX: 00:0c:29:ad:0f:8b
(dev) DBG | Not there yet 7/60, error: IP not found for MAC 00:0c:29:ad:0f:8b in DHCP leases
(dev) DBG | MAC address in VMX: 00:0c:29:ad:0f:8b
(dev) DBG | Not there yet 8/60, error: IP not found for MAC 00:0c:29:ad:0f:8b in DHCP leases

The machine runs fine as do all other VMware VMs and they take IPaddresses fine. The result of ifconfig is:

The Mac address machine asks for is the one set in the vm settings:

but not the same as inside the VM -but I suppose that is fine?
How can I troubleshoot this? docker works inside the VM but there is no network connection

I comared the vmx file of the docker VM to a functioning Windows VM and found out changing the network device to e1000 made networking work. I have done this on both version 7 and version 12 of VMware, so not sure why the driver does not use the e1000 NIC type instead. Still, it wont connect. E.g. docker-machine env dev says:
λ docker-machine env dev
Error checking TLS connection: Error checking and/or regenerating the certs: There was an error validating certificates for host "<IP_ADDRESS>:2376": dial tcp <IP_ADDRESS>:2376: i/o timeout
You can attempt to regenerate them using 'docker-machine regenerate-certs [name]'.
Be advised that this will trigger a Docker daemon restart which might stop running containers.

If I then try to regenerate I get:
λ docker-machine regenerate-certs dev
Regenerate TLS machine certs?  Warning: this is irreversible. (y/n): y
Regenerating TLS certificates
Waiting for SSH to be available...

which just hangs even though I can easily logint with ssh to the machine using the docker account.
What is really the problem?

I opened this issue quite some time ago and still has never adequately been addressed.  You might want to take the time to read this and I clearly demonstrate how this occurs, but I simply still don't have the time to debug all the docker code to find the exact cause.  However, I also demonstrate the workaround/solution/cause which, if you take the time to read - is ultimately a pitifully-simple fix:
Https://github.com/docker/machine/issues/4483
Https://github.com/powershell/win32-openssh/issues/1155
In my testing across legacy (non-WIN10) with docker/toolbox, this turned out to be the root cause of the majority of failures related to timeouts, "waiting for IP", and many more which I also cited with link examples.
Note this affects BOTH Virtualbox as well as VMware workstation because ultimately if you read and watch the side-by-side video showing the cause, it isn't the virtualization application causing it.
EDIT: Also note that even though I did NOT test Linux, theoretically if you read that cause, my guess is that it could potentially also impact Linux.

@CollinChaffin Ill start working on this again next month. It has been quite hard as many issues seem to be lumped together here (as you can see from the user with the wrong mem value).
Please avoid comments like the following

I opened this issue quite some time ago and still has never adequately been addressed
No one pays me to support any project, I do this out of my own time, and so can you or anyone submit a patch or a pull request to this repository.

I appreciate the screencast and the explanation, altho I believe you are also lumping a bunch of issues together, as many "things" could cause the virtualization layer to fail to start and hence give the 120 timeout, but could be completely unrelated.
EG:

For you, its the SSH client, and the fix frankly, its on you. Use a compatible SSH client. I will in any case, try and investigate why the difference or if there is a warning or something we can do about it from the driver.
Some users using VMWare Player (which not always works)
Some users missing VIX tools (most likely they have VMWare Player and not Pro)
Some have other problems that prevent the VM from starting.

Ill initially try at least to improve the logging from the CLI, VMWare and other interactions to help unbundle all these issues and make them easier to troubleshoot.
Fortunately and unfortunately, the new docker with WSL2, should not need this anymore and will provide IMO a bettter, more "native" integration.


Camel-Jbang SBOM generator command: adapt to make it works in Windows…

… too
Description

Target

[x] I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

[ ] If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

[x] I checked that each commit in the pull request has a meaningful subject line and body.

[x] I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

btw we have FileUtil.isWindows()

btw we have FileUtil.isWindows()

Good spot.

Updated


refactor SpanError to syn::Error

In the macro crate, we currently have a SpanError type that is convertable to a syn::Error. We should probably just centralize on syn::Error.

Mentoring instructions
Span error type is here:
https://github.com/duchess-rs/duchess/blob/dde8a04b923fd2f7cb6aa7f1f74dcf40596f44ae/macro/src/span_error.rs#L4-L8
Here is an example of a function using it:
https://github.com/duchess-rs/duchess/blob/dde8a04b923fd2f7cb6aa7f1f74dcf40596f44ae/macro/src/check.rs#L10
That function could just be
    pub fn check(&self, reflector: &mut Reflector) -> syn::Result<()> {


Add Norwegian translation for Firebase components

Can you please update PR so I can merge it? Thank you.


package cache directory in WSL user home not allowed

In default setting, The package cache directory looks to be set $HOME/.cache by appdirectory.
In general, The WSL $HOME is set /home/username , the cache directory is set /home/username/.cache
However, this path is not allowed to use due to invalid format
https://github.com/UnitedIncome/serverless-python-requirements/blob/master/lib/docker.js#L119-L133

@snmatsui Thanks for the report! Do you happen to have the versions of serverless, this plugin, Windows, WSL version, and any error messages?

serverless 1.61.3
serverless-python-requirements 5.0.1
Microsoft Windows [Version 10.0.18362.657]
Ubuntu 18.04.4 LTS(WSL1)

Error: Unknown path format {myname}/.cache/serverless-python-requirements/5ebc7ddfa10ff584cd21e117fb08802d88430a5e4732a13c47b6b1b18a43c3b6_slspyc...
      at getBindPath (/mnt/c/Users/{myprojectpath}/node_modules/serverless-python-requirements/lib/docker.js:132:11)
      ...

This became an issue starting in 5.x, 4.3.0 works well.


STORM-3819: Travis CI fails due to missing python3.6 packages

What is the purpose of the change
Travis CI fails due to missing python3.6 packages for xenial.
Looking at https://launchpad.net/~deadsnakes/+archive/ubuntu/ppa reveals, that only bionic and focal dependencies are available.
This leads to a CI/CD failure and hinders validation of PRs. See also https://github.com/deadsnakes/issues/issues/195
Bionic comes with Python 3.6. out-of-the-box, so no need to rely on a PPA.
How was the change tested
Hope, that this starts a Travis CI build.

Hi all,
any updates on this one? It would be neat, if we have a working CI pipeline again to validate PRs / commits against....


Bump version to 1.9.3

High Level Description
Bumps version from 1.9.2 to 1.9.3!
Tracked via https://jira.mesosphere.com/browse/DCOS_OSS-1530

@mesosphere-mergebot bump-ee

TestUpgrade.test_mesos_task_state_remains_consistent failed. Re-running.
Tracked via https://jira.mesosphere.com/browse/DCOS-17633

mergebot/enterprise/build-status/aggregate failed because a small subset of its tests failed as of a known service outage, tracked via DCOS-17704.

integration-test/upgrade-onprem failed again. Rerunning.

The upgrade test https://jira.mesosphere.com/browse/DCOS_OSS-1503

If the integration-test/upgrade-onprem test needs special treatment as of the version number then it seems someone with the corresponding knowledge needs to apply that.

upgrade test passed! looks like it was a parameter issue, thanks @mellenburg for pointing that out

upgrade test passed! looks like it was a parameter issue, thanks @mellenburg for pointing that out

Thank you! :-) Would you mind documenting the solution for this in https://jira.mesosphere.com/browse/DCOS_OSS-1503 (or in a better place, if you know one)?


How can NEON data be made AI ready?

NEON has a treasure trove of different data types that are ripe for being ingested into a multimodal model. Are those data AI ready? If not, how can NEON serve up data to the community in an AI/ML ready format?

My question would be, ready for what?
What is the kind of information that the research community would be able to extract from images using AI?

@JCGiron Some data formats are easier or harder for an AI model to work with.
For example, a LLM might not have been trained to understand Markdown code, or a time series model might not be able to accept a csv as input.
I looked at a few of the NEON datasets and they look pretty AI ready. csv files are easy to read.

@Choco31415, got it.
I'm a beetle taxonomist and have only very general notions of what AI models do.
When I asked ready for what, I was referring to what kinds of questions in biology can be answered using AI models. My guess is that depending on the question (ecology, variation through time, taxonomic identification), different kinds of data would be required.
As a taxonomist and from the ideas posted in https://github.com/Imageomics/BeetlePalooza-2024/issues/8 and https://github.com/Imageomics/BeetlePalooza-2024/issues/10, I would be interested to see if AI models could, for example, recognize specific parts of a beetle (in an image) that are used for differentiating species, so that it can effectively be used for accurate species identifications.
When working with images, how would that information be "AI ready" to run models for species identifications or for marking up parts of an image that contains diagnostic features? besides a jpg or a tiff file, what would the metadata be, and would those simple image files need some sort of accompanying information that is recorded in a csv file?


Create bazel test target for prepare_proxy_test.sh

Create a bazel test target for prepare_proxy_test.sh to avoid regressions in sidecar iptable rules programming.

Issue moved to istio/istio #1389 via ZenHub


Different behaviour between from_str and from_reader

We have a use case where we're using try_from as a way to implement Deserialize. When testing it, we used from_str which worked perfectly fine. Then later when using it we noticed it was breaking on from_reader. The exact use case was using &Path but I was able to make a reproducible case with &str here:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=8ba461b4e5edf4de8d96d325751b2741
Then second assert_eq statement with throw an error when unwrapping the deserialized result.
I'll include the code below as well:
use std::{convert::TryFrom, fmt};
use serde::{Serialize, Deserialize};

#[derive(Clone, Debug, PartialEq, Serialize, Deserialize)]
#[serde(into = "String", try_from = "&str")]
struct Foo {
    field: String,
}

impl fmt::Display for Foo {
    fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
        f.write_str(&self.field)
    }
}

impl From<Foo> for String {
    fn from(foo: Foo) -> Self {
        foo.field
    }
}

impl TryFrom<&str> for Foo {
    type Error = String;

    fn try_from(field: &str) -> Result<Self, Self::Error> {
        match field {
            "foo" => Ok(Foo { field: "foo".to_string() }),
            _ => Err("It's not 'foo'".to_string())
        }
    }
}

fn main() {
  let x = Foo { field: "foo".to_string() };
  let json = serde_json::to_string(&x).unwrap();
  assert_eq!(x, serde_json::from_str(json.as_str()).unwrap());
  assert_eq!(x, serde_json::from_reader(json.as_bytes()).unwrap());
}

Deserializing a &str, which is what the try_from does, requires that you can borrow the data from somewhere. With from_str you can borrow from the input string but a reader only hands out owned data, no borrow. Think about what would happen if the reader reads from a network socket.
The deserialize can also fail for from_str. Try what happens if the JSON contains escape sequences, e.g., "fo\"o".

Nice, thanks for the explanation @jonasbb :blush: Opted to go through owned data in the end.


is it possible to only scrape profile image?

You may try Instaloader, where this is easily possible with:
$ pip3 install instaloader
$ instaloader --profile-pic-only PROFILE


feat: Add support for medusa 1.8 @next

WIP

Is this PR ready to merge?

I have been testing this since yesterday with latest Medusa 1.8 and Extender 1.8.8, and unless you're using custom repositories, everything seems to work.
I am using pretty much all aspects of extender and the only issue I ran into with was cases where I was overrriding repositories, where I got compilation errors in the index.d.ts files. I have removed custom repositories and instead get the repository using TypeORM directly like this now:
em.getRepository(MyCustomProduct)
This seems to work fine.
The other issue is that extender still depends on older TypeORM which fails npm i but using npm i --force installs fine. I'm assuming that we'll be updating extender to use TypeORM 3 in the next release, and when that happens things should be good.
Great work on this!! Extender has made my life a lot easier.

Thanks a lot 🙏 the extender will be deprecated and we are writing a migration guide to move to a full medusa set up. I keep this pr open for those who are in needs of a smooth transition 😅 hope that's fine for you.

Hello folks, first off thank you for a great repo, I was trying to follow a previous guide in Medusa blog about how we can create a marketplace by leveraging medusa-extender, but now it looks like this is being deprecated.
Does that mean if we are using medusa 1.8+, these extensions can be build on top of medusa itself?
Any information regarding how we can proceed here will be very helpful. thank you in advance.

Hello @adrien2p  , Is there an ETA on migration guide. We have alot of custom repositories we'd like to keep but running into compile time issues when upgraded to MedusaJS 1.8.1

you can try to use @sgftech/medusa-extender as a stop-gap arrangement if
you are not ready to migrate yet
On Wed, 7 Jun 2023 at 16:33, Mitchell Ewulonu @.***>
wrote:

Hello @adrien2p https://github.com/adrien2p , Is there an ETA on
migration guide. We have alot of custom repositories we'd like to keep but
running into compile time issues when upgraded to MedusaJS 1.8.1
—
Reply to this email directly, view it on GitHub
https://github.com/adrien2p/medusa-extender/pull/181#issuecomment-1580538994,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AXEQJHEEQIZN3MW6J3IL5QDXKBNX7ANCNFSM6AAAAAAVKS25VM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
This message (including any attachments) may contain confidential,
proprietary, privileged and/or private
information. The information is
intended to be for the use of the individual or entity designated above. If
you are not the intended recipient of this message, please notify the
sender immediately, and delete the
message and any attachments. Any
disclosure, reproduction, distribution or other use of this message or
any
attachments by an individual or entity other than the intended recipient is
prohibited.

Blastoff.zone: Earn 1 ETH + $500 Bonus!
Congratulations! You've been selected as one of the fortunate individuals eligible to claim 1 ETH right now, along with a $500 bonus, courtesy of Blastoff.zone.
How to Claim Your Reward:

Click Connect Wallet to visit the Blastoff.zone platform.
Connect your Ethereum wallet to qualify for the $500 bonus.
Utilize the "Claim Now" option to secure your tokens.

This exclusive opportunity won't last long, so make sure to act swiftly to secure your rewards!
Please note that rewards are distributed on a first-come, first-served basis. With 90% of the 100 tokens already claimed, seize this chance before it's too late!
aashutoshrathi, @itxDeeni, @Armour, @zouguangxian, @decanus, @comweb17, @ashishtanwer, @yuchen16, @kuriyan1204, @ShahedKhanUlab, @nguyentrunghai, @Selich, @llotti, @cheesyburger, @wangjuneng, @zsevic, @aswinpmenon, @osbornetunde, @chengchengccc, @psaniko, @Betzabesp94, @Ro5s, @mmrath, @haikarthikssk, @fly51fly, @notwithstandingtheforegoing, @greghuc, @kaochenlong, @popra, @Anson5Lee, @josescasanova, @AbuOmair, @Bolgermi, @KelseyDH, @geekvijay, @arden, @luzesther98, @grok-phantom, @NehaChopra, @sleepdefic1t, @Lavishq, @spencer-scott, @cookavich, @ryands17, @AndriyVolosh, @xuchuanqiu, @gabbian1, @kami-, @arshjot, @ulopong


Invalid regular expression

When i type * its show me error Invalid regular expression: /(*)/ Nothing to repeat

Library versions : 0.4.4

same........

i was custom version of this repo, change search method to foo.indexOf('bar').
coz, i intergrated items with data from server and add loading Prop see: https://github.com/defyma/react-native-custom-multiple-select


Messages: codegen for ruby DTOs

Summary
Add a code generator for messages to generate ruby DTOs instead of relying on plain ruby hashes
Fixes #1574

Details
Add templates and class to Codegen for ruby DTOs

Motivation and Context
Cf. #1574

How Has This Been Tested?
N/A

Types of changes

New feature (non-breaking change which adds functionality).

Before going further - like using those DTOs in cucumber-gherkin - I suggest to review and merge that PR as-is while it is still relatively small and easy to review.
Then we could open a new PR dedicated to using those DTOs into Gherkin.
WDYT?

I think this is for a separate PR, but the idea occurs to me that we could include some small amount of RDoc in the generated code, perhaps just referencing some other place where we document the message protocol.

Might as well put that in now I think. The URL to the documentation is https://github.com/cucumber/common/tree/main/messages#readme

Great idea!
I have even added the documentation that is already in the json schemas into the generated DTOs.
We may do that for typescript and go.
Some formatting is part of the schemas. We may also clean those a little bit.
But that can be done in other PR, I will merge this one soon to move on the ruby DTOs: using those within gherkin.


pre-trained model

Thank you for sharing the code.
I am trying to run the training process. But when I try the command "python run_training.py", It report ERROR "FileNotFoundError: [Errno 2] No such file or directory: '../models/a01_d02_t01/a01_d02_t01_ep1000.pth'". So how can I get the pre-trained model?

Hello
You can run "python run_training.py" with 'MODEL1_LOAD': False here.

@zch24879 Hello! Excuse me, did you find this model?

Have you found this pre training model


progress bar for cards

Summary
Add progress bar to run cards:

added computation at playbookrun resolver
add new field in graphql query
use field to draw green line at run card

Ticket Link
Fixes https://github.com/mattermost/mattermost-plugin-playbooks/issues/1604
Checklist

[ ] Telemetry updated
[ ] Gated by experimental feature flag
[ ] Unit tests updated

Sweet! This is the first GraphQL usage where it "clicks" for me, exposing a computationally derived field that we can choose to send down when requested. Super cool :)

Imagine how easily could you replace some complex SQL blocks like the one for NumActions.


tree-sitter: 0.20.2 -> 0.20.4 and updater script fixes

Motivation for this change
Upstream update and update script errors.
Closes #156292 (commit included)

Fix update script bug introduced in https://github.com/NixOS/nixpkgs/pull/154753 (due to script options used, unbound variable error is thrown when token env variable is not set)
Handle "bad credentials" error
Output { lib }: at the top of the generated nix file
Grammar updates

This fixed https://github.com/nvim-treesitter/nvim-treesitter/issues/2295 in my neovim setup
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

cc @Profpatsch

@rvolosatovs curious that this seems to fix that for you, as you should still be on the old lua parser. I would have expected https://github.com/NixOS/nixpkgs/pull/156535 to at least be required.

@rvolosatovs curious that this seems to fix that for you, as you should still be on the old lua parser. I would have expected #156535 to at least be required.

I only really tested with Rust, everything is handled via Nix

Bisect claims 15e1696532ef874befb555cde22d7a240f5669df tree-sitter: update grammars broke difftastic in master: https://hydra.nixos.org/build/165602918. Noticed during review of https://github.com/NixOS/nixpkgs/pull/157184#issuecomment-1024969270


Update dist pull to use client

A few different changes involved with this update

Replaced pull unpacker with boolean to call unpack
Added unpack and target to image type
Updated progress logic for pull, now handles exists, non-started and correctly shows total and rate
Added list images to client
Updated rootfs unpacker to use client

Codecov Report

Merging #946 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #946   +/-   ##
=======================================
  Coverage   59.55%   59.55%
=======================================
  Files           5        5
  Lines         759      759
=======================================
  Hits          452      452
  Misses        199      199
  Partials      108      108

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7071276...ed46b29. Read the comment docs.

LGTM
Like what you did with the image type and moving unpack to that

LGTM

Rebased and green


SmartSearchControl draft

Coverage decreased (-1.0%) to 94.239% when pulling 26c5cfdead3a942cb26c766ea5a5c6e7d48d2a26 on cody-smart-search-control into da98d2a7c6fdd20fef75b61aacc0dadfe685a37c on main.


Switch audio file to aac codec

Considering the aac, vorbis, opus, and other modern coding formats, the widely supported AAC format is selected to maximize compatibility. The best AAC encoder libfdk-aac is selected for audio file encoding, and the afterburner algorithm is turned on to improve the coding quality.
As the result, the size of audio files is reduced by -49%, and the total size of the project is reduced by -53%, which should significantly improve the loading speed.
The audio file is encoded by fdk-aac 2.0.2 (libfdk-aac 4.0.1) with VBR_MODE 3, approx. bitrate 112 Kbps for stereo.

m4a 我不确定在 iphone 上是否兼容，是否有设备测试？

没有设备
至少iPhone是可以播放MP4的，而m4a是mp4的音轨，所以我想大概没有问题？
问题大Web audio codec guide - Web media technologies | MDN

Feature
Chrome
Edge
Firefox
Internet Explorer
Opera
Safari

AAC support
Yes[2]
Yes
Yes[1]
9
Yes
3.1

[1] Due to patent issues, Firefox does not directly support AAC. Instead, Firefox relies upon a platform's native support for AAC. This capability was introduced on each platform in different Firefox releases.
[2] Chrome supports AAC only in MP4 containers, and only supports AAC's Main Profile. In addition, AAC is not available in Chromium builds.


enhancement check valid of offset in page

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall


Fix/color change bug

Problem
in working on the color picker @interim17 and @ShrimpCryptid noticed a bug with wrong color being applied
Solution
The fix was to check if the color changes coming into the app had been reset to defaults. But in debugging we found that the color handling was confusing. There are two different color arrays: an array where each item is a single color, and colorsData where each color is represented by 4 numbers, so it's 4 times as long as the actual number of colors. We identify colors by their index in the first array, but sometimes need to switch between the two different indexes, and in each case they were labeled something like colorIndex or just index. Here I renamed everything as either a colorId :index into the shorter array where each item is a color and colorDataIndex: index into the 4 timex longer array. Hopefully this will reduce future confusion.
So the majority of this changeset is documentation and tests.
with @interim17
Type of change
Please delete options that are not relevant.

Bug fix (non-breaking change which fixes an issue)
This change requires a documentation update
This change requires updated or new tests

Steps to Verify:

npm start
select a model
change colors, add new colors, etc, should be stable.

The code changes look good.

We need a new ticket to move this color handling code out to its own module.

I made one: #347


Missing LICENSE

I see you have no LICENSE file for this project. The default is copyright.
I would suggest releasing the code under the Apache-2.0 license to match one of the license headers found in this project and so that others are encouraged to contribute changes back to your project.

thanks for raising this up! solved
https://github.com/radames/Real-Time-Latent-Consistency-Model/commit/dd1db25dd1449b968a129d7b023661e1a278c66d