Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump github.com/jaegertracing/jaeger from 1.41.0 to 1.42.0 causes issues #18401

Closed
codeboten opened this issue Feb 7, 2023 · 8 comments · Fixed by #18485
Closed

Bump github.com/jaegertracing/jaeger from 1.41.0 to 1.42.0 causes issues #18401

codeboten opened this issue Feb 7, 2023 · 8 comments · Fixed by #18485
Labels
dependencies Pull requests that update a dependency file extension/jaegerremotesampling

Comments

@codeboten
Copy link
Contributor

Component(s)

extension/jaegerremotesampling

What happened?

Description

Updating the dependency from 1.41.0 to 1.42.0 causes the following error in the test because of the change in using api_v2.SamplingStrategyResponse from sampling.SamplingStrategyResponse:

--- FAIL: TestEndpointsAreWired (0.01s)
    --- FAIL: TestEndpointsAreWired/new (0.00s)
        http_test.go:86: 
                Error Trace:    /Users/alex.boten/workspace/opentelemetry-collector-contrib/extension/jaegerremotesampling/internal/http_test.go:86
                Error:          Not equal: 
                                expected: "{\"strategyType\":\"PROBABILISTIC\"}"
                                actual  : "{}"
                            
                                Diff:
                                --- Expected
                                +++ Actual
                                @@ -1 +1 @@
                                -{"strategyType":"PROBABILISTIC"}
                                +{}
                Test:           TestEndpointsAreWired/new
FAIL
FAIL    github.com/open-telemetry/opentelemetry-collector-contrib/extension/jaegerremotesampling/internal       10.753s
FAIL

The strategyType field in the api_v2 is not rendered because of the omitempty tag in the struct. What's the right way to address this in the extension?

See the PR here: #18400

Collector version

not-released-yet

Environment information

Environment

OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")

OpenTelemetry Collector configuration

No response

Log output

No response

Additional context

No response

@codeboten codeboten added the dependencies Pull requests that update a dependency file label Feb 7, 2023
@github-actions
Copy link
Contributor

github-actions bot commented Feb 7, 2023

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@jpkrohling
Copy link
Member

@frzifus, I think you did something related to this recently?

@codeboten
Copy link
Contributor Author

Thanks @jpkrohling

@frzifus
Copy link
Member

frzifus commented Feb 7, 2023

I assume you mean #18070? Let me see.

@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Apr 10, 2023
@frzifus frzifus removed the Stale label Apr 10, 2023
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Aug 14, 2023
@frzifus frzifus removed the Stale label Aug 14, 2023
codeboten pushed a commit that referenced this issue Sep 6, 2023
…ypes for sampling strategies (#18485)

Add featuregates to replace Thrift-gen with Proto-gen types for sampling strategies. Available featuregates are:
  - extension.jaegerremotesampling.replaceThriftWithProto
  - receiver.jaegerreceiver.replaceThriftWithProto
 
Closes #18401 
Ref #18047

--

cc @jpkrohling

---------

Signed-off-by: Benedikt Bongartz <bongartz@klimlive.de>
Co-authored-by: Juraci Paixão Kröhling <juraci.github@kroehling.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file extension/jaegerremotesampling
Projects
None yet
3 participants