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

[Bug]: "Deep Dependency Graph" is not drawn. #1077

Closed
Myeongseok-Kim opened this issue Nov 24, 2022 · 3 comments · Fixed by #1082
Closed

[Bug]: "Deep Dependency Graph" is not drawn. #1077

Myeongseok-Kim opened this issue Nov 24, 2022 · 3 comments · Fixed by #1082
Labels

Comments

@Myeongseok-Kim
Copy link

What happened?

After finding Trace
When I click the "Deep Dependency Graph" button, no graph is drawn.

Steps to reproduce

  1. Find Traces
  2. Deep Dependency Graph

Expected behavior

graph is drawn

Relevant log output

No response

Screenshot

image

image

image

Additional context

No response

Jaeger backend version

v.1.39.0

SDK

No response

Pipeline

No response

Stogage backend

Elasticsearch 7.x

Operating system

Linux

Deployment model

Kubernetes

Deployment configs

No response

@yurishkuro
Copy link
Member

update: I verified that the issue started after #1001

yurishkuro added a commit that referenced this issue Nov 25, 2022
Resolves #1077.

The upgrade was introduced in #1001. Sadly, we have no unit tests in
`/plexus/` module, so the break was not caught.

In #1001 the dependency viz.js was upgraded to the next major version
(2.1.2), however it had breaking changes which were not accounted for.

Alternative paths tracked in #1081.
@stevenkitter
Copy link

I have the same problem, in 1.39.0 the graph is not drawn.

@stevenkitter
Copy link

When I use 1.40 version of query image, it's fine.

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

Successfully merging a pull request may close this issue.

3 participants