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

Handled the case in which child span starts before and ends after parent span. #1780

Merged
merged 7 commits into from
Sep 12, 2023
Merged

Handled the case in which child span starts before and ends after parent span. #1780

merged 7 commits into from
Sep 12, 2023

Conversation

GLVSKiriti
Copy link
Contributor

                |----parent----|
         |------------child------------|

The above case is not handled in previous code
Resolves #1779

…t span

Signed-off-by: GLVS Kiriti <glvskiriti2003369@gmail.com>
@codecov
Copy link

codecov bot commented Sep 12, 2023

Codecov Report

Patch coverage is 100.00% of modified lines.

Files Changed Coverage
...ui/src/components/TracePage/CriticalPath/index.tsx 100.00%
...mponents/TracePage/CriticalPath/testCases/test8.js 100.00%
...CriticalPath/utils/sanitizeOverFlowingChildren.tsx 100.00%

📢 Thoughts on this report? Let us know!.

Copy link
Member

@yurishkuro yurishkuro left a comment

Choose a reason for hiding this comment

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

Please add unit test

…ction

Signed-off-by: GLVS Kiriti <glvskiriti2003369@gmail.com>
yurishkuro
yurishkuro previously approved these changes Sep 12, 2023
@GLVSKiriti
Copy link
Contributor Author

Basically the first test is to test computeCriticalPath function.
And second test for the whole criticalPath function i.e, memoizedTraceCriticalPath

But memoizedTraceCriticalPath returns the same as computeCriticalPath function. Then should I remove the 2nd test case??

Updated sentence in the test case

Co-authored-by: Yuri Shkuro <yurishkuro@users.noreply.github.com>
Signed-off-by: GLVSKiriti <116095646+GLVSKiriti@users.noreply.github.com>
@yurishkuro
Copy link
Member

I would remove the first one, it's calling internal implementation details which are irrelevant for the purpose of the test.

Signed-off-by: GLVSKiriti <116095646+GLVSKiriti@users.noreply.github.com>
Signed-off-by: GLVSKiriti <116095646+GLVSKiriti@users.noreply.github.com>
Signed-off-by: GLVSKiriti <116095646+GLVSKiriti@users.noreply.github.com>
Signed-off-by: GLVSKiriti <116095646+GLVSKiriti@users.noreply.github.com>
@yurishkuro yurishkuro merged commit 103fef5 into jaegertracing:main Sep 12, 2023
8 of 9 checks passed
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.

[Bug]: Prevent Critical Path code from throwing exceptions
2 participants