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

build(scripts-tracecontext-integration-test.sh): fixed issue #4105 #4109

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Metal-Bat
Copy link

@Metal-Bat Metal-Bat commented Aug 6, 2024

updated TRACECONTEXT_GIT_TAG to latest

Description

Fixes #4105
updated TRACECONTEXT_GIT_TAG version for avoid warnings in test time

Type of change

  • Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

  • read 5 years of git log in konsole to see if i can find any deprication (nothing found but the docs are not really good)
  • just tested the script

Does This PR Require a Contrib Repo Change?

  • Yes. - Link to PR:
  • No.

Checklist:

  • Followed the style guidelines of this project
  • Changelogs have been updated
  • Unit tests have been added
  • Documentation has been updated

@Metal-Bat Metal-Bat requested a review from a team August 6, 2024 21:42
@@ -1639,3 +1639,5 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
([#3778](https://github.com/open-telemetry/opentelemetry-python/pull/3778))
- Fix license field in pyproject.toml files
([#3803](https://github.com/open-telemetry/opentelemetry-python/pull/3803))
- bump trace-context to e99a85d12df8c25c51ec1d5d234f20e918265b75
([#4109](https://github.com/open-telemetry/opentelemetry-python/pull/4109))
Copy link
Member

@emdneto emdneto Aug 7, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should move this to the "# Unreleased" section at the beginning of the CHANGELOG.md file

# hard-coding the git tag to ensure stable builds.
TRACECONTEXT_GIT_TAG="98f210efd89c63593dce90e2bae0a1bdcb986f51"
TRACECONTEXT_GIT_TAG="e99a85d12df8c25c51ec1d5d234f20e918265b75"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think won't be so to easy to point to the lastest :) There's a failing test test_tracestate_duplicated_keys.

In w3c/trace-context#477

The test_tracestate_duplicated_keys was broken, it demanded to drop
the whole tracestate when a duplicate key was found. This does not match
what the specification mandates in that situation. Instead,
implementations MAY remove the duplicates from tracestate or even leave
them in as-is.

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.

Update tracecontext tests
2 participants