Extension log level is not persisted across reload

[alexr00]

Testing #167384

1. Change the log level for an extension that uses the extension logging API
2. Reload the window
3. 🐛 The extensions log level will be reset to info.

[alexr00]

Actually, it seems that the log level is persisted, but it doesn't show correctly in the "Set Log Level..." quick pick.

[alexr00]

Nope, I take it back. I checked the log level via the API and it is not persisted. Though somehow, I see both info and debug getting logged even though the log level after reload is info.

[sandy081]

This is expected that extension log level changes are not persisted across reloads.

[alexr00]

I don't think this is a drop in replacement for extensions that currently use a setting for log level then. What if I want to capture extension activation trace logs?

[alexr00]

One possible option would be for extension to be able to set their own log level and handle the persistence themselves. I would be fine with that too, though it seems like each extension would be duplicating this effort as persistent log levels are likely something many extension authors want.

[sandy081]

There is a command line arg supported for such cases - code --log vscode.git:trace this sets log level to trace by default for git extension

[alexr00]

I don't think asking users to run via a command line is a good replacement for the existing, extension provided, setting.

[sandy081]

Agreed. It is nice to have. But I think this is not often asked. I see it is needed, if you want to reload/restart an extension with verbose log level. In that case, we can ask to restart VS Code from CLI with necessary log level. I will open as a feature request and tackle it if often asked for.

[vscodenpa]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!