generated from TBD54566975/tbd-project-template
-
Notifications
You must be signed in to change notification settings - Fork 7
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
Console loads duplicate trace spans #3260
Comments
Open
pretty sure it's a simple js bug in the rendering template. I'll grab this next if wes doesn't beat me to it |
I think this is being caused by these errors
I would guess that these lead to us re-requesting the events starting from the beginning after this happens. I wonder what is causing these errors though 🤔 |
This was referenced Oct 31, 2024
wesbillman
added a commit
that referenced
this issue
Oct 31, 2024
See #3260 We can get some console connection errors in our deployed environment which causes streaming to get restarted. However, it seems like we don't clear the cache when this happens so duplicate events get returned from our streaming hooks. This change should ensure the events are cleared anytime we restart the stream.
The duplicate entries should be fixed with #3266 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Go to the traces view
Wait for 20ish seconds, go to other tabs.
The result is reloading the flame graph, which causes duplicate traces to appear
The text was updated successfully, but these errors were encountered: