Eduardo Pinto

I think I'm facing the same issue. While on colima: ```bash $ colima version colima version HEAD-030393c git commit: 030393ccc5ab74153809ed00dbe965325d3cd7af $ python3 -m http.server Serving HTTP on :: port 8000...

> You do not need the `--add-host` flag for Colima. `host.docker.internal` works out of the box except you specify a custom dns server. I see now, it actually works if...

Understood, thank you very much @abiosoft ! 🙇

Now, after reading [this](https://github.com/opentracing/specification/blob/master/semantic_conventions.md#span-and-log-errors) I'm not so sure anymore if this is one case that warrants the error setting.

I'm going to split this PR in 2: 1. the logic to correctly propagate tracing headers into the metadata available from `actionContext` 2. new specific sample for tracing demonstration This...

So, providing an update here, I've rebased the PR against the `release-1.5` branch and updated the samples to use the latest java version and new dependency repo. I was starting...

Btw for completeness, this exists already for `CloudEvent` but not for `JwtClaims`.

Would probably be good to also clarify: - initial value vs subsequent requests - the use of RequestParam vs PathParam due to being non-required - example of such setup

On a second thought though, actually we can currently call such endpoint (just confirmed) with: ```shell > curl -i -XPOST localhost:9000/counter/hello/test -H "Content-Type: application/json" -d '"test dsf ds f"' HTTP/1.1...

> True, but at the same time, in real life, you will end up with different kinds of tests. Some integration tests might use only the proxy, and some of...