-
Notifications
You must be signed in to change notification settings - Fork 314
Use fallback build settings if build system doesn’t provide build settings within a timeout #1700
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
Conversation
@swift-ci Please test |
72e073a
to
558ef62
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
558ef62
to
415bba0
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
body: @escaping @Sendable () async throws -> T?, | ||
resultReceivedAfterTimeout: @escaping @Sendable () async -> Void | ||
) async throws -> T? { | ||
let didHitTimeout = AtomicBool(initialValue: false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nothing seems to set this to true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, thanks for catching that!
…tings within a timeout When we receive build settings after hitting the timeout, we call `fileBuildSettingsChanged` on the delegate, which should cause the document to get re-opened in sourcekitd and diagnostics to get refreshed. rdar://136332685
415bba0
to
78217ec
Compare
@swift-ci Please test |
@swift-ci Please test Windows |
1 similar comment
@swift-ci Please test Windows |
When we receive build settings after hitting the timeout, we call
fileBuildSettingsChanged
on the delegate, which should cause the document to get re-opened in sourcekitd and diagnostics to get refreshed.rdar://136332685