-
Notifications
You must be signed in to change notification settings - Fork 119
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
Analytics tab internal error #618
Comments
WunderGraph commits fully to Open Source and we want to make sure that we can help you as fast as possible. |
Hi @AesSedai, thanks for reporting. We will look into it. |
Hi @AesSedai, seems we are having this issue from ClickHouse version 24.2 onwards. While we work on a fix, please use version <= 24.1. |
This is fixed in the latest version of clickhouse. Please reopen if this occurs again. |
Component(s)
studio
Component version
0.70.4
wgc version
0.44.2
controlplane version
0.74.1
router version
0.72.0
What happened?
If possible, please create a PR with a failing test to illustrate the issue clearly.
Otherwise, please attach a minimum reproduction through a GitHub repository that includes
essential information such as the relevant subgraph SDLs.
Please also make sure that the instructions for the reproduction are clear, tested, and fully accurate.
Description
The Studio Analytics tab and traces tab show an internal server error when loading their pages
Steps to Reproduce
Run the "Local Development" steps in the readme
Make a request in the Studio -> Playground tab
Navigate to the Studio -> Analytics tab, select Traces
=> Could not retrieve analytics data, [internal] internal error
Expected Result
Studio -> Analytics tab should show Traces
Actual Result
Studio -> Analytics tab shows an error
Environment information
Environment
OS: WSL2 Ubuntu 20.04.5 LTS
Package Manager: pnpm: 8.15.4, nodejs: v20.11.1
Compiler(if manually compiled): go version go1.22.1 linux/amd64
Router configuration
Default "Local Development" setup
Router execution config
Default "Local Development" setup
Log output
Additional context
No response
The text was updated successfully, but these errors were encountered: