console-ninja icon indicating copy to clipboard operation
console-ninja copied to clipboard

[Bug]: Interactive Diagram does not work when I click the "Show Diagram"

Open omerson-cruz opened this issue 6 months ago • 4 comments

What happened?

I was expecting to see the visual data diagram when I click the diagram (as seen on the advertisement) but it does not work .

My project is using React/Next.js

Image

Version

1.0.441

CLI command to start your dev tool

next dev

Steps to reproduce (or sample repo)

I just run the next.js dev server like "yarn dev" then it executes next dev

Log output

10:27:57.637 info buildHook-17708 file processed (stat): 0 log points, error handler: true, network logging handler: true
10:28:11.308 info buildHook-17708 file processed (stat): 0 log points, error handler: true, network logging handler: true
10:28:16.323 info host client disconnected: runtimeHook 1001
10:28:16.324 info host client disconnected: runtimeHook
10:28:16.324 info host client disconnected: runtimeHook 1001
10:28:16.324 info host client disconnected: runtimeHook
10:28:16.324 info host client disconnected: runtimeHook 1001
10:28:16.324 info host client disconnected: runtimeHook
10:28:17.197 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 42577 }
10:28:17.210 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 42577 }
10:28:21.028 info buildHook-17708 file processed (stat): 0 log points, error handler: true, network logging handler: true
10:28:25.973 ERR! extension CodeExpectedError: cannot open vscode-remote://wsl%2Bubuntu20/node_modules/next/dist/client/next-dev.js. Detail: Unable to read file 'vscode-remote://wsl+ubuntu20/node_modules/next/dist/client/next-dev.js' (Error: Unable to resolve nonexistent file 'vscode-remote://wsl+ubuntu20/node_modules/next/dist/client/next-dev.js')
10:28:25.974 ERR! extension     at D5t.$tryOpenDocument (vscode-file://vscode-app/c:/Users/omers/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:1379:8485)
10:28:25.974 ERR! extension  unable to highlight %s:%s, error: %s file:///node_modules/next/dist/client/next-dev.js 28 Error [CodeExpectedError]: cannot open vscode-remote://wsl%2Bubuntu20/node_modules/next/dist/client/next-dev.js. Detail: Unable to read file 'vscode-remote://wsl+ubuntu20/node_modules/next/dist/client/next-dev.js' (Error: Unable to resolve nonexistent file 'vscode-remote://wsl+ubuntu20/node_modules/next/dist/client/next-dev.js')
10:28:25.974 ERR! extension     at D5t.$tryOpenDocument (vscode-file://vscode-app/c:/Users/omers/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:1379:8485)
10:28:34.513 info buildHook-17708 file processed (stat): 0 log points, error handler: true, network logging handler: true
10:28:36.278 info host client disconnected: runtimeHook 1001
10:28:36.278 info host client disconnected: runtimeHook
10:28:36.278 info host client disconnected: runtimeHook 1001
10:28:36.279 info host client disconnected: runtimeHook
10:28:36.849 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 42577 }
10:28:36.861 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 42577 }
10:28:44.067 info buildHook-17708 file processed (stat): 0 log points, error handler: true, network logging handler: true
10:28:50.953 info buildHook-17708 file processed (stat): 0 log points, error handler: true, network logging handler: true
10:28:55.259 info host client connected: runtimeHook { address: '127.0.0.1', family: 'IPv4', port: 42577 }
10:28:55.757 info buildHook-17708 file processed (stat): 0 log points, error handler: true, network logging handler: true
10:29:45.717 info buildHook-17708 file processed (stat): 3 log points, error handler: false, network logging handler: false
10:29:46.166 info buildHook-17708 file processed (stat): 0 log points, error handler: true, network logging handler: true

omerson-cruz avatar May 17 '25 02:05 omerson-cruz

Btw I'm using Cursor instead of VS Code if you need to take that in consideration

omerson-cruz avatar May 17 '25 02:05 omerson-cruz

Sorry I think figured it out already. But the first time it did not work so you guys might need to look into that also. What I did is to restart the Next.js server and try to log it again. Now it worked! This is an awesome feature. Also another thing is that sometimes when I close the "Interactive data view" it does not go back to the its normal view. But a restart of the next.js server does fix it. :)

Image

omerson-cruz avatar May 17 '25 02:05 omerson-cruz

Here's another issue which I was able to capture. The normal "text" log view does not immediately appear when I close the interactive diagram view.

https://github.com/user-attachments/assets/a78ff9ab-802c-4ad5-83de-de2d0d4a6544

omerson-cruz avatar May 17 '25 02:05 omerson-cruz

Hi, thanks for reporting the issue. We have released a new version 1.0.442 that should fix the problem. Can you please update to the latest version when it becomes available in Cursor and check if the issue with switching between the diagram and text logs view is fixed for you?

ArtemGovorov avatar May 17 '25 06:05 ArtemGovorov

Assuming that this is now working for you. If not, please let us know and we'll re-open the issue.

smcenlly avatar May 21 '25 00:05 smcenlly

Hi wallaby team sorry for the late reponse. It takes a few days before the new version is available in Cursor extension. But I can confirm that my issue has been resolved already. Thank you!

omerson-cruz avatar May 21 '25 05:05 omerson-cruz