Carlos

Hi, I am installing the library through Conan with version and revision (both latest): ``` jwt-cpp/0.6.0@#cd6b5c1318b29f4becaf807b23f7bb44 ``` After installing, I ran into a very similar error where `picojson.h` is not...

Pinging @eigenraven to pick their brains. Is there something we are completely overlooking here?

@eigenraven thanks for the tips! For ASAN, as you say, I think there might be another problem. For TSAN, changing the `history_size` to 0 does not help. I am a...

Hey @FlowDrucka64 , `inv codegen` generates machine code from an existing `.wasm` file. And `inv codegen.local` generates machine code for all the `.wasm` files used in the tests. Before generating...

@Shillaker you are right, I got confused (twice) by the fact that `func.local` and `libfake` were in the same line. @FlowDrucka64 it should be present in the container indeed. Outside...

Exactly, that's the problem. Something went off rails during compose instantiation.

Maybe do the following (from a new terminal, no virtual environments neither): ```bash # Outside the container docker compose down ./bin/cli.sh cpp inv func.local exit ./bin/cli.sh faasm ls /usr/local/faasm/wasm ```

Have you done all the steps before (emphasis on `docker compose down` + fresh terminal session)? It seems to work form me on a fresh clone: ``` git clone https://github.com/faasm/faasm...

Essentially what is happening is that, upon `docker compose up` time, the env. variable [`FAASM_LOCAL_MOUNT`](https://github.com/faasm/faasm/blob/main/.env#L18) was not overriden by a shell env. variable. This is done by default in [`./bin/cli.sh`](https://github.com/faasm/faasm/blob/main/bin/cli.sh#L75),...

No, the env. variables will only be visible to the process that starts the container process. Note that when running `./bin/cli.sh` we always `exec` into a running container.