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

[AWS Xray]Change the type of content_length #2539

Merged

Conversation

JohnWu20
Copy link
Contributor

@JohnWu20 JohnWu20 commented Mar 3, 2021

Description:

There is a bug for aws xray nodejs sdk, it emits a string type for content_length.
This pr will make xray receiver to be able to deal with both the string and number type of content_length by changing the data type from *int to interface{}

Link to tracking Issue:
aws/aws-xray-sdk-node#385

Testing:
Unit test and end2end test.

Changes:
1, Changed the data type of content_length.
2, Added logic to deal with different types.
3, Added a test file to test the string type of content_length.
4, Changed the test cases of xray receiver and xray exporter relative files.

@JohnWu20 JohnWu20 requested a review from a team March 3, 2021 03:17
@codecov
Copy link

codecov bot commented Mar 3, 2021

Codecov Report

Merging #2539 (543d60f) into main (944622e) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #2539   +/-   ##
=======================================
  Coverage   91.20%   91.20%           
=======================================
  Files         417      417           
  Lines       20935    20942    +7     
=======================================
+ Hits        19093    19100    +7     
  Misses       1379     1379           
  Partials      463      463           
Flag Coverage Δ
integration 69.28% <ø> (+0.06%) ⬆️
unit 90.07% <100.00%> (+<0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files Coverage Δ
internal/awsxray/tracesegment.go 100.00% <ø> (ø)
...ceiver/awsxrayreceiver/internal/translator/http.go 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 944622e...543d60f. Read the comment docs.

@bogdandrutu bogdandrutu merged commit d8ed6a8 into open-telemetry:main Mar 5, 2021
@JohnWu20 JohnWu20 deleted the ChangeDataTypeForContentLength branch March 5, 2021 19:41
This was referenced Mar 15, 2021
pmatyjasek-sumo referenced this pull request in pmatyjasek-sumo/opentelemetry-collector-contrib Apr 28, 2021
* Change the type of attributes content_length

* Re-run integration test

* Add unit-test
alexperez52 referenced this pull request in open-o11y/opentelemetry-collector-contrib Aug 18, 2021
otlpexporter endpoint configuration allows for an `http` or `https` scheme. The scheme is stripped off when instantiating the gRPC channel. A scheme of `https` indicates a secure channel. This aligns the collector with this hopefully soon-to-be-merged specification PR open-telemetry/opentelemetry-specification#1729

**Link to tracking Issue:** #2539

**Documentation:** Updated readme
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants