Skip to content
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

Crash when using --config and --path with a Swift file #1694

Closed
marcelofabri opened this issue Jul 19, 2017 · 4 comments
Closed

Crash when using --config and --path with a Swift file #1694

marcelofabri opened this issue Jul 19, 2017 · 4 comments
Labels
bug Unexpected and reproducible misbehavior.

Comments

@marcelofabri
Copy link
Collaborator

Probably introduced on #1644. Reported by @valeriomazzeo on https://github.com/ashfurrow/danger-swiftlint/issues/49.

$ swiftlint lint --path foo.swift --config .swiftlint.yml
fatal error: Could not read configuration file at path '/Users/marcelofabri/dev/foo.swift/.swiftlint.yml': file /tmp/swiftlint-20170703-13452-ik99jk/Source/SwiftLintFramework/Models/Configuration.swift, line 167
/Users/marcelofabri/dev/foo.swift/.swiftlint.yml:File not found.
[1]    51731 illegal hardware instruction  swiftlint lint --path foo.swift --config .swiftlint.yml
@marcelofabri
Copy link
Collaborator Author

A current workaround is to provide an absolute path for --config.

@Sega-Zero
Copy link
Contributor

Sega-Zero commented Sep 24, 2017

Still having that issue on 0.22.0.

$ swiftlint lint --quiet --path ./App/ --config ./App/.swiftlint.yml
/Users/sega-zero/projects/App/App/.swiftlint.yml:File not found.
fatal error: Could not read configuration file at path '/Users/sega-zero/projects/App/App/.swiftlint.yml': file /Users/marcelofabri/projetos/SwiftLint/Source/SwiftLintFramework/Models/Configuration.swift, line 156
Illegal instruction: 4

@marcelofabri, danger-swiftlint still doesn't work because of it

@valeriomazzeo
Copy link

Still not working

@jpsim
Copy link
Collaborator

jpsim commented Apr 22, 2018

File new issues with steps to reproduce please.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Unexpected and reproducible misbehavior.
Projects
None yet
Development

No branches or pull requests

4 participants