-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[Xcode 13.3] NSRangeException in ClosureEndIndentationRule.isFirstArgumentOnNewline(_:file:) #3830
Comments
Thanks for reporting this early! Hopefully this is early enough that it can be fixed in Swift before 5.6 is officially released. |
I'm not sure if this is a bug in Swift, SourceKit or SwiftLint, but this should avoid it for now: #3831 |
Is there a schedule for when there'll be a release with this fix in it, JP? I'm hitting the crash on CI after upgrading our runners to Xcode 13.3 beta 2. |
SwiftLint doesn't have a release schedule, but I'm happy to cut a release to unblock you. I'll do that today. Note that there are still some other known issues with Swift 5.6 beyond this though: https://github.com/realm/SwiftLint/issues?q=is%3Aissue+is%3Aopen+label%3Aswift-5.6 |
Thanks, JP - I really appreciate you doing that! 😄 |
New Issue Checklist
Describe the bug
A NSRangeException after upgrading to Xcode 13.3 beta 1:
In
ClosureEndIndentationRule.isFirstArgumentOnNewline(_:file:)
a range with a negative length gets passed toNSRegularExpression.firstMatch(in:options:range:)
:SwiftLint/Source/SwiftLintFramework/Rules/Style/ClosureEndIndentationRule.swift
Line 342 in f8909b5
Complete output when running SwiftLint, including the stack trace and command used
Environment
SwiftLint version: 0.46.2
Installation method used: Homebrew
Paste your configuration file: none. I guess rule
closure_end_indentation
needs to be enabled.Are you using nested configurations? No.
Which Xcode version are you using? Xcode 13.3, Build version 13E5086k
Do you have a sample that shows the issue?
The text was updated successfully, but these errors were encountered: