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

False 'classname not in autoload module layout' now being thrown #140

Open
mschuchard opened this Issue Nov 7, 2017 · 3 comments

Comments

Projects
None yet
2 participants
@mschuchard
Member

mschuchard commented Nov 7, 2017

puppet-lint inside of linter-puppet-lint now throws a false classname not in autoload module layout when puppet-lint outside of it confirms nothing is wrong.

Test case:

  • any situation where the atom project is also the module

@mschuchard mschuchard self-assigned this Nov 7, 2017

@jeski

This comment has been minimized.

jeski commented Jan 2, 2018

still a problem

@mschuchard

This comment has been minimized.

Member

mschuchard commented Jan 3, 2018

Forgot about this while focusing on other projects. I have narrowed down the event that triggers this false warning (original issue updated) and feel like it is probably occurring due to some conflict Atom has with the new relative pathing code to respect the .puppet-lint.rc.

@mschuchard

This comment has been minimized.

Member

mschuchard commented Jan 3, 2018

Ok, I took the exact command and directory passed into sb-exec and executed it from the shell. It did not duplicate this issue. Therefore, puppet-lint and this package are fine and the issue is with a dependency of this package. I do not see a way to circumvent the issue in the dependency, so we will have to wait until the bug is fixed in the dependency.

Issue will remain open until the dependency is fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment