Viacheslav Vasilyev

xref. https://github.com/aws/aws-cdk/issues/24370, https://github.com/aws/aws-cdk/discussions/25956

do you think that the `socket_vmnet` verification should be really strict as it is now? could it be relaxed? https://github.com/lima-vm/lima/pull/2662

as stated in the https://github.com/lima-vm/lima/pull/2662#issuecomment-2380644324 this will work if only my user is a member of the admin group, for example, if my primary group is "staff", it won't work...

This is all valid if a user is a member of the admin group (`%admin`). My user is not a member of the admin group for the sake of said...

@jandubois I assume you're referring to [a caveat](https://www.sudo.ws/docs/man/sudoers.man/#Including_other_files_from_within_sudoers) when a sudoers file has a dot somewhere in its file name, in this case my sudoers file name has no dots...

The issue I have had reported before is now fixed 👍

speaking of consistency, with the SSH connection over `docker context` we have 30 seconds [timeout](https://github.com/docker/cli/blob/cfbf88fd9fd0824f4f2931dda18c96b500a1eab5/cli/connhelper/connhelper.go#L78), however the direct remote connection timeout in `docker buildx` is 20 seconds, which is hardcoded...

sure, here is the relevant part (line no. 17) ``` +(/opt/homebrew/Cellar/pyenv/2.4.7/libexec/pyenv-exec:48): exec /Users/user.name/.pyenv/versions/3.10.14/bin/python3.10 -m venv /Users/user.name/.pyenv/versions/3.10.14/envs/venvname +(/opt/homebrew/bin/pyenv-virtualenv:610): shopt -s nullglob +(/opt/homebrew/bin/pyenv-virtualenv:611): for extra_binary in "$PREFIX"/bin/python*-config ++(/opt/homebrew/bin/pyenv-virtualenv:612): basename /Users/user.name/.pyenv/versions/3.10.14/bin/python-config +(/opt/homebrew/bin/pyenv-virtualenv:612): extra_binary_linkname=/Users/user.name/.pyenv/versions/3.10.14/envs/venvname/bin/python-config...

to sum up, I have to use `ln -fsn` instead of `ln -fs` to overcome that

This MR also adds: - Waiter - Key generation