-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Stuck on "GroovyLint is analyzing code" #157
Comments
Same issue. Any progress? |
Hello |
|
Same here (bit faster though):
|
Would it be possible to share the groovy files you try to analyze so I can try to reproduce the problem locally ? |
Unfortunately I am unable to share the files |
I'll email you the problematic script. It was the first file I opened upon installing on a cleanly installed laptop that caused this so I figured it was an installation problem but now I've opened a few more and then it works. |
thanks to @verheyenkoen 's script, I succeeded to reproduce. I investigate... |
Fixed it in v1.9.1 :) (you'll need to reload VsCode once the patch is automatically installed) @verheyenkoen @kjr6721 please let me know if it's now ok on your side :) If it is, don't hesitate to rate the extension -> https://marketplace.visualstudio.com/items?itemName=NicolasVuillamy.vscode-groovy-lint |
@nvuillam That fixed it for me. Great work. Thanks very much! |
Thanks for your feedback:) |
Hi :) I Currently have this on the latest version as well, nothing on the output panel other than "Start analyzing file" Edit - |
Hello, thanks for making this extension!
I am trying to use it (and it works great on some of my files) but on two it is stuck on this message:
[{
"resource": ****,
"owner": "GroovyLint0",
"code": "GroovyLintWaiting",
"severity": 2,
"message": "GroovyLint is analyzing code...",
"source": "GroovyLint",
"startLineNumber": 1,
"startColumn": 1,
"endLineNumber": 1,
"endColumn": 1
}]
Any idea why this is happening on only some files and how I can fix it?
The text was updated successfully, but these errors were encountered: