Skip to content

[Core][BugFix] Add content equality of SegmentRef#30

Merged
kezhenxu94 merged 1 commit intomasterfrom
bugfix/equality-of-segment-ref
Jul 2, 2020
Merged

[Core][BugFix] Add content equality of SegmentRef#30
kezhenxu94 merged 1 commit intomasterfrom
bugfix/equality-of-segment-ref

Conversation

@kezhenxu94
Copy link
Copy Markdown
Member

No description provided.

@kezhenxu94 kezhenxu94 added the bug Something isn't working label Jul 2, 2020
@kezhenxu94 kezhenxu94 added this to the 0.2.0 milestone Jul 2, 2020
@kezhenxu94 kezhenxu94 requested a review from wu-sheng July 2, 2020 07:02
@kezhenxu94 kezhenxu94 force-pushed the bugfix/equality-of-segment-ref branch from 7083b85 to 50c4772 Compare July 2, 2020 07:13
@wu-sheng
Copy link
Copy Markdown
Member

wu-sheng commented Jul 2, 2020

Is python facing duplicated trace id?

@kezhenxu94
Copy link
Copy Markdown
Member Author

kezhenxu94 commented Jul 2, 2020

Is python facing duplicated trace id?

No, this fixes the duplicate refs when one framework is built on another, for example, Flask is built on top of requests

if ref not in self.refs:
self.refs.append(ref)

@kezhenxu94 kezhenxu94 merged commit 1736c24 into master Jul 2, 2020
@kezhenxu94 kezhenxu94 deleted the bugfix/equality-of-segment-ref branch July 2, 2020 09:42
@wu-sheng
Copy link
Copy Markdown
Member

wu-sheng commented Jul 2, 2020

Oh, I see. So, python agent only had ref override self trace id mechanism, no ref override and ignorance mechanisms, right?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants