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

No way to stop asking about 'debug' setting for logging #348

Closed
rchiodo opened this issue Oct 29, 2020 · 3 comments
Closed

No way to stop asking about 'debug' setting for logging #348

rchiodo opened this issue Oct 29, 2020 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@rchiodo
Copy link
Contributor

rchiodo commented Oct 29, 2020

When this warning comes up:

You have enabled debug logging for the Jupyter extension, which will continue to write logs to disk. Would you like to turn debug logging off?

It would be nice to have a 'dont ask me again' setting. I want it to be on.

@rchiodo rchiodo added the bug Issue identified by VS Code Team member as probable bug label Oct 29, 2020
@DonJayamanne
Copy link
Contributor

DonJayamanne commented Oct 29, 2020

I don't think we want it on. Other extension authros have complained about this & i'd say to be good citizens we shouldn't leave this on. Else we might as well turn this on always. But theres a reason this was put in place.

Why leave it on indefinitely, when you only need it when something is wrong & you want to diagnose it.
As an developer on the extension it is annoying, but for a user I don't think we should give that option.

@rchiodo
Copy link
Contributor Author

rchiodo commented Oct 29, 2020

Other extension authros have complained about this

I believe other extension authors have complained because we were filling up the developer console. We're not doing this anymore. It all goes to an output tab.

@IanMatthewHuff
Copy link
Member

Validated. Verified the setting, picked don't ask again and I wasn't.
image.png

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

3 participants