Thomas Schaffter

@thomasyu888 Is this a task you wish to assign to the new hire who will be responsible for the development of the client?

@jordanpowell88 Not yet.

@hallieswan I was able to reproduce the issue, which means I successfully crashed my dev container. ;-) What I did: ```bash nx run-many --target=build --projects=agora-* nx run-many --target=test --projects=agora-* ```...

## Time it takes to start the dev container This workflow step takes slightly less than 2 minutes based on the runtime of past runs. The Dev Container CLI performs...

## About stopping the dev container This step takes 4 seconds, which is not much. It's also probably safer to shutdown the container properly.

## GH Runner hardware resources - CPU cores: 2 - RAM: 7 GB - Storage: ```console Run df -h Filesystem Size Used Avail Use% Mounted on /dev/root 84G 62G 22G...

## About downloading the base dev container image - Without caching Docker images on the runner, it takes 58.1s to pull + extract the base image. - It takes 13s...

## About installing VS Code extension I thought that the dev container CLI was installing the VS Code extensions specified in `devcontainer.json` when running `devcontainer up`. However, there is nothing...

## Docker images are not cached Cache Docker layers says: ```console Run actions/cache@v3 with: path: /tmp/.buildx-cache key: Linux-single-buildx-82425368edcaf7acea638514ddd0cdc3809229bd restore-keys: Linux-single-buildx enableCrossOsArchive: false fail-on-cache-miss: false lookup-only: false env: NX_BRANCH: 1976 NX_RUN_GROUP:...

## Still need to find where image layer are store ```console devcontainer up --cache-from /tmp/.buildx-cache --workspace-folder ../sage-monorepo ``` does not save data to `/tmp/.buildx-cache` even if the folder is created...