Collect errors while building up the settings index#12781
Merged
dhruvmanila merged 1 commit intomainfrom Aug 12, 2024
Merged
Conversation
dhruvmanila
commented
Aug 9, 2024
42a3c78 to
5b3a5ae
Compare
Contributor
|
5b3a5ae to
ea694f4
Compare
CodSpeed Performance ReportMerging #12781 will not alter performanceComparing Summary
|
ea694f4 to
b3bc35d
Compare
MichaReiser
approved these changes
Aug 12, 2024
Member
|
Thanks. This is a great addition! |
b3bc35d to
2004c6a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Related to astral-sh/ruff-vscode#571, this PR updates the settings index builder to trace all the errors it encountered. Without this, there's no way for user to know that something failed and some of the capability might not work as expected. For example, in the linked PR, the settings were invalid which means notebooks weren't included and there were no log messages for it.
Test Plan
Create an invalid
ruff.tomlfile:Logs:
Notification Preview:
Another way to trigger is to provide an invalid
cache-dirvalue:Same notification preview but different log message:
With multiple
pyproject.tomlfile: