-
Notifications
You must be signed in to change notification settings - Fork 1.8k
internal: Show more project building errors to the user #11960
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -119,7 +119,9 @@ fn setup_logging(log_file: Option<&Path>) -> Result<()> { | |
None => None, | ||
}; | ||
let filter = env::var("RA_LOG").ok(); | ||
logger::Logger::new(log_file, filter.as_deref()).install()?; | ||
// deliberately enable all `error` logs if the user has not set RA_LOG, as there is usually useful | ||
// information in there for debugging | ||
logger::Logger::new(log_file, filter.as_deref().or(Some("error"))).install()?; | ||
Comment on lines
+122
to
+124
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Any arguments against this? The way this PR is structured now is that we do small error popups for build errors and others that only appear on project load and put the bulkier information into the server logs as most notification UIs (or maybe really only VSCode who knows) don't handle big messages that well. |
||
|
||
profile::init(); | ||
|
||
|
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.
We were never using this "error case" here, but once set we stop working through the build script output, so this might be the cause of #9720 not working for people without any apparent reason?