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

Console.log in extensions no longer seem to show in the Debug Console #26641

Closed
eamodio opened this issue May 15, 2017 · 5 comments
Closed

Console.log in extensions no longer seem to show in the Debug Console #26641

eamodio opened this issue May 15, 2017 · 5 comments
Assignees
Labels
*as-designed Described behavior is as designed debug Debug viewlet, configurations, breakpoints, adapter issues *question Issue represents a question, should be posted to StackOverflow (VS Code)
Milestone

Comments

@eamodio
Copy link
Contributor

eamodio commented May 15, 2017

  • VSCode Version: Code - Insiders 1.13.0-insider [Unsupported] (f6ab171, 2017-05-12T06:11:44.129Z)
  • OS Version: Windows_NT ia32 10.0.16193

Steps to Reproduce:

  1. Add a console.log() statement in an extension
  2. 🐛 the output of that console.log() doesn't show in the Debug Console pane
@isidorn
Copy link
Contributor

isidorn commented May 15, 2017

Works for me, can you please share your extension repo on GitHub or let me know what you are doing differently than me.
I have tried both OS X and win and both work fine

consolelog

@isidorn isidorn added debug Debug viewlet, configurations, breakpoints, adapter issues info-needed Issue requires more information from poster labels May 15, 2017
@isidorn isidorn added this to the May 2017 milestone May 15, 2017
@eamodio
Copy link
Contributor Author

eamodio commented May 15, 2017

@isidorn hrm -- thanks for looking into it. I checked some more, and it seem to only happen with GitLens. Not sure why yet, but another of my extensions Restore Editors, for example works fine, but they practically share a logging class.

EDIT: unless the application insights package is doing something to console.log -- that is about the only difference. I will check that out later today.

@isidorn
Copy link
Contributor

isidorn commented May 15, 2017

@eamodio ok. Let me know once you have more information. Thanks

@eamodio
Copy link
Contributor Author

eamodio commented May 16, 2017

@isidorn I've verified it is monkey patching that the application insights package is doing (even though I have it explicitly turned off).

@eamodio eamodio closed this as completed May 16, 2017
@isidorn
Copy link
Contributor

isidorn commented May 16, 2017

@eamodio thanks for looking into it

@isidorn isidorn added *as-designed Described behavior is as designed *question Issue represents a question, should be posted to StackOverflow (VS Code) and removed info-needed Issue requires more information from poster labels May 16, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed debug Debug viewlet, configurations, breakpoints, adapter issues *question Issue represents a question, should be posted to StackOverflow (VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants