-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
Error with latest version of the docker container when running in GHA #356
Comments
Oooch until we find a fix, I suggest you use the previous version of the docker image :/ |
Thanks for your response. No problem, I rolled back to 13.0.2 and I'll stick to that version until an update. |
any idea @stevenh ? :) |
Can you find out which version triggers the issue? The initial error looks like your code doesn't compile "WARNING: Compilation error" |
Can you also provide the full text stack trace, not as an image as that makes it impossible to search ;-) |
I think that's what you want |
And before that I have this kind of errors for, I guess, all my classes.
|
Thanks @ClementDelannoySlateDigital this does look like the compile step is failing inside CodeNarc. This isn't something that has changed to my knowledge, but it could be its more visible than it used to be due to changes with flow and logging. Could you confirm if the missing classes are available? If yes are they in the standard path or would it need a custom classpath to resolve? Can you confirm the behaviour recent previous versions, specifically are you seeing these errors reported? |
@ClementDelannoySlateDigital looks like the stack is truncated, looking for where it was triggered from the npm-groovy-lint code. |
@nvuillam it would seem that using an older version is useless since NPM_GROOVY_LINT_VERSION value is always pointing to latest in the dockerfile. Manual overwrite is needed |
@dav-pascual yes but when we generated a previous version of a npm-groovy-lint docker image, "latest" was the related previous version ^^ |
This issue has been automatically marked as stale because it has not had recent activity. If you think this issue should stay open, please remove the |
No problem with v13.0.2
Unfortunately, I can't tell you much more...
Thanks a lot!
The text was updated successfully, but these errors were encountered: