-
Notifications
You must be signed in to change notification settings - Fork 27
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]: How avoid this... ? #362
Comments
Thanks for being one of our PRO customers and for raising the issue. We'll take a look at this first thing next week and should get back to you on Monday. |
Based on the log file that you provided, we found and fixed a bug in Console Ninja that would have been causing Ninja to not display inline hover messages correctly. This is fixed in Console Ninja We can't tell from your screenshot as it is cut off, but we expect that you're seeing the predictive logging because you have a breakpoint set next to your function; this is a PRO feature. For example (see the red dot indicating a breakpoint): ![]() From our docs:
If you set a breakpoint on a line with a function,
If you're still seeing predictive logs when you believe they you shouldn't appear, can you please provide a screenshot of your entire editor? This will allow us to see other relevant markers/indicators that may help us understand what's going on. |
you are right. Maybe I understood what exactly the problem is, after setting the red dot and deleting this piece of code, sometimes this dot will save its position on a certain line.
I also recorded a video and attach the latest logs, please let me know if something is not clear or more information is needed. 2024-12-16.13-23-46.1.1.1.mp4 |
The breakpoint moving behavior is actually a part of VS Code and we aren't able to change that. Based on your Can you please update to the latest version of the Console Ninja VS Code extension, |
What happened?
Usually this happens after deleting code and putting it back, and commenting and uncommenting. I can't reproduce it 100% of the time, but it worries me that it appeared after I switched to the pro plan.
![Screenshot_11](https://private-user-images.githubusercontent.com/45768057/395467467-6df0fcb6-d717-41fa-9c83-ae0bb31eb33b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyNjY0NDcsIm5iZiI6MTczOTI2NjE0NywicGF0aCI6Ii80NTc2ODA1Ny8zOTU0Njc0NjctNmRmMGZjYjYtZDcxNy00MWZhLTljODMtYWUwYmIzMWViMzNiLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjExVDA5MjkwN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZlZWFhZjNhOGI1OTgzZGY2MmFlMThmYjIyN2Y1NDczNTlmZGI3ZWEyOWYxOTM3N2JkMjdmZDkyYzZjNGVlNTYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.Bvg9wTghBoRrMp9w9SnJQLKkn1v5eQ2-hYYhIKGRO10)
Prediction is disabled. What else could it be?
Version
1.03.373
CLI command to start your dev tool
npm run dev / astro dev
Steps to reproduce (or sample repo)
idk, but try remove some code and add it
Log output
The text was updated successfully, but these errors were encountered: