Robert Pająk

This is most likely fixed via dep bumps when I look at https://github.com/golangci/golangci-lint/blob/master/go.mod and https://github.com/timakin/bodyclose/issues/38#issuecomment-1304323617 I think it is worth to retest. FYI @ldez

What about installing `golangci-lint` using the new `go install` syntax like this: ``` go install github.com/golangci/golangci-lint/cmd/[email protected] ``` This way is (I believe) truly cross-platform and can be used e.g. like...

@ysmood It is cool. Personally, I would add an option to add a checksum validation for additional integrity checking. Supply chain attacks are becoming more and more frequent.

If this feature is added then we could offer it in https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation

I strongly disagree that this feature should be implemented as there are no common standards regarding `FORCE_COLOR`. If in future the `FORCE_COLOR` would be a standardized, then a change in...

`FORCE_COLOR` becomes a standard: https://force-color.org/

I think it may be worth to resurrect https://github.com/fatih/color/pull/156

Closing per https://github.com/open-telemetry/opentelemetry-go/pull/4092#issuecomment-1929025059

It should be fixed as part of https://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.17.0

From https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/sdk-environment-variables.md#jaeger-exporter > Jaeger exporter support will be removed from OpenTelemetry in July 2023. It is better to move to use OTLP as @Baliedge suggests.