-
Notifications
You must be signed in to change notification settings - Fork 122
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
Rubocop issue with 0.3.0 #286
Comments
I started getting this with 0.2.0 having upgraded to Rubocop 1.38.0. |
I'm running into the same problem after upgrading to rubocop 1.38.0. I was able to get the full exception for the error:
|
I also have this issue |
Also experiencing this. Is there currently a way to configure the RuboCop linter to fail with a non-zero exit code in this case? (I didn't see one.) |
@oehlschl the easiest |
Thanks @mvz; that makes sense. My hope was that erb-lint would fail loudly and return a non-zero exit code in this case, so this would have been caught in CI when we upgraded rubocop. That said, I can file that as a separate issue / feature request. |
I suppose the build failure on the first commit in #283 kind of points to there being a problem with RuboCop 1.38.0 ... |
Thanks for releasing v0.3.1!
Full trace is here:
This issue has already been fixed at rubocop/rubocop#11142 but has not yet been released. |
I couldn't figure out a smart way to pass the I modified this method as follows: def build_team
::RuboCop::Cop::Team.new(
cop_classes,
@rubocop_config,
extra_details: true,
display_cop_names: true,
autocorrect: true,
auto_correct: true,
stdin: "",
debug: true, # inserted
)
end Please let me know if there is a correct way to get RuboCop debug info... |
As of 0.3.0 we seem to be getting a Rubocop error (not a linting failure, an actual error) on what looks like every erb file in the project:
Unfortunately I can't figure a way to get erblint to pass along a debugger option to rubocop so I'm not sure what the cause might be.
This came up during a dependabot update here:
DFE-Digital/apply-for-teacher-training#7638
The text was updated successfully, but these errors were encountered: