-
Notifications
You must be signed in to change notification settings - Fork 461
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
Couldn't find message for key cmake-tools.configuration.cmake.options.advanced.statusBarLength.description #3616
Comments
It looks like the correct key is |
How do I resolve the issue if I don't have a package.json file? |
@IkeCuizhihui If you don't want to wait for the next extension release and it bothers you that much, you can switch to the prerelease version of the extension -- open the extension's page (go to Extensions and click on CMake Tools) then click the "Switch to Pre-Release Version" button under the extension description, next to the "Disable" and "Uninstall" buttons. Then after it switches, click Reload, and then you may need to close and reopen vscode once to fully get rid of the warning spam. But, to be honest, I wouldn't risk it if it's a prod environment you need to be sure the extension is stable and working. After all, it's not that big of a deal, more or less an aesthetic annoyance. |
It's been two months since this was merged. Any chance someone can cut a release that includes this? |
I'm seeing this as well - can we have a new release, please? :) |
@notpeter @georglauterbach, thanks for your reply. About this issue, it is fixed on CMakeTools extension release version 1.18 but this version has not been released yet. If you are in a hurry to use it, you could switch to the prerelease version of the extension -- open the extension's page (go to Extensions and click on CMake Tools) then click the "Switch to Pre-Release Version" button. Please refer to the mihailim's above comment. Thanks for your support. |
This went out with v1.18.41. Pre-release is not longer required anymore. Thanks all. |
Any updates on it? Release version |
@zhongxiang117 This has been fixed for a while. You may be referring to the similar but different issue with |
@mihailim thanks for your reply, it is the same issue. |
You're right, my apologies. I can confirm it's happening with the pre-release version |
@mihailim , OK, I will switch back to |
For version |
@mihailim @zhongxiang117 I'm not sure I fully understand from your comments, which error is happening where? |
With a quick test and viewing the source code, these issues are fixed in the most recent code. If you could tell me any steps you take to see this output, it'd be great so that I can test and see for myself. Thanks! |
@gcampbell-msft , as a brief conclusion, for my system, pre-version |
@zhongxiang117 Are you doing anything specific to get this output? I'm opening the extension on the most recent release and I don't see the issue |
Could you provide any steps? Are you using any other display language than English?
We don't have a dependency, but we do bundle with the one that you have in your screenshot. We hope to remove that bundle at some point as we implement and improve our own language services for CMake files. |
@gcampbell-msft it's not actually a dependency. It is just bundled with this extension. Anyone can uninstall it if they want to use a different language server extension for |
@bobbrow Good clarification, you are correct, it's not a dependency but a bundle. Thanks. I'll update my comment as well |
Yeah, the top-level readme has a link to another language server extension. |
@mihailim We have released this in the most recent pre-release. Additionally, we no longer use the key |
OK, I got it, thanks for you two. The steps is: I installed Now, it seems I cannot reproduce them, |
Brief Issue Summary
For a while now (at least 3 months), the
cmake-tools
extension has been spamming the shared log with the warning message reproduced below. This happens on startup, and then periodically throughout the session, regardless of whether or not anything cmake-related is open or running; the presence of the installed extension is sufficient to reproduce. Changing the logging level to debug doesn't affect anything in any direction.This is with vscode-cmake-tools v1.17.16 running on the latest MS-published vscode build (1.86.2) on Linux (repros on Ubuntu noble daily, Ubuntu jammy, Ubuntu bionic with the older still-compatible vscode 1.85.whatnot). No idea about other OS-es, sorry.
The locale environment is
LANGUAGE=en_US
andLANG=en_US.UTF-8
and it also reproduces withLANG=C
.CMake Tools Diagnostics
Debug Log
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: