Robert Pająk

I think for big repositories you can take advantage of the test cache and additionally set up a `cron` job to run all tests (e.g. on a nightly basis). I...

1. Your collector configuration is suited for `metrics` - not traces. The example is made for traces. 2. I do not believe `otel/opentelemetry-collector:0.6.0` was supporting metrics - however, I have...

Have you built your application against the correct architecture? This looks like a mismatch: > Architecture:X86 vs > /go1-16-linux-amd64/src/runtime/panic.go:965 +0x1b9\nmath/rand.(*rngSource).Uint64(...)/ Moreover, Go 1.16 is not supported. See: https://github.com/open-telemetry/opentelemetry-go#compatibility

1. It looks as if you build against `amd64` arch instead of `386`. 2. From the information that you provided I can redirect you to create an issue in https://github.com/golang/go...

I see that you changed the environment information 👍 Can you please provide the exact steps to reproduce? Does it happen on all CentOS versions? Can you create a test...

@zhyChesterCheung @shivanshu1333 Thanks a lot for your feedback. The first thing we should do is to agree on some constraints (I feel that requirements could be defined as we go)....

> 1. Can we create a new repository for this? How should it be named? `opentelemetry-go-demo`? I think it should be as few projects as possible. Maybe even one to...

@MrAlias @Frefreak I need to go asleep but won't the following interface solve the problem better? ```go type Clock interface { Now() time.Time // default implementation: time.Now() End(start time.Time) time.Time...

For now, I think that documenting it as part of the changelog is good enough (until there are more complaints)

@jpkrohling > This was an adjustment done to ensure that there can be two distributions running at the same time at the same node. Is there any issue where this...