Alex Couture-Beil

here's buildkit logs from v0.6.7 ``` time="2022-07-22T19:57:57Z" level=debug msg="received shell connection" app=shellrepeater remote.addr="172.17.0.1:37026" time="2022-07-22T19:57:57Z" level=debug msg="closing existing shell connection" app=shellrepeater remote.addr="172.17.0.1:37026" time="2022-07-22T19:57:57Z" level=debug msg="session started" time="2022-07-22T19:57:57Z" level=debug msg=resolving time="2022-07-22T19:57:57Z" level=debug...

I don't think the `--shell-out-anywhere` flag affects `RUN` in anyway: ```Earthfile VERSION --shell-out-anywhere 0.6 foo: FROM alpine ARG VARNAME=$(hostname) RUN --entrypoint echo hello $VARNAME ``` still misses the arg: ```...

Thanks for the PR @ingwarsw , sorry about the delay in taking a look at this. I'm curious if it should be more of a manually triggered job or not...

@bhagyas It's currently possible to use the `inotifywait` command inside a container. Here's an example: consider a script that generates files, sleeps, and eventuall exits. Let's call it `make-files.sh`: ```...

Thanks for the contribution! Would you be able to add a test for this? after https://github.com/earthly/earthly/blob/main/tests/Earthfile#L547-L548 can you add a new target, perhaps something like: ``` env-quote-test: DO +RUN_EARTHLY --earthfile=env-quote.earth...

Why did you remove the `RUN test "$(env | grep weird)" = "really\"weird\"-key=yes"` test?

what about this test? ``` FROM alpine ENV "even\"weirder'quote" yes RUN env | grep 'even"weirder'\''quote=yes' ``` I'm worried that this PR is too fragile, and won't help us fix the...

> quick question: can user also refer to cloud-secrets(`earthly secrets set` command ) or only secrets set from command-line with --secret flag should be supported here? ideally yes; however if...

The new `--wait-block` feature introduces a new `WAIT` / `END` block, which allows one to mix commands in a fan-out-fan-in pattern. Under [v0.6.23](https://github.com/earthly/earthly/releases/tag/v0.6.23), it is now possible to run: ```Earthfile...

> except that the remote cache is not saved anymore in case of test failure. That's a great point! That's not something I considered while working on WAIT/END; I'll take...