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

minor: Set tracing level to debug when cargo config get env fails #17744

Merged
merged 1 commit into from
Jul 30, 2024

Conversation

alibektas
Copy link
Member

@alibektas alibektas commented Jul 30, 2024

fixes #17739

@rustbot rustbot added the S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. label Jul 30, 2024
@Veykril
Copy link
Member

Veykril commented Jul 30, 2024

@bors r+

@bors
Copy link
Collaborator

bors commented Jul 30, 2024

📌 Commit 02c066c has been approved by Veykril

It is now in the queue for this repository.

@bors
Copy link
Collaborator

bors commented Jul 30, 2024

⌛ Testing commit 02c066c with merge 4feec4b...

@bors
Copy link
Collaborator

bors commented Jul 30, 2024

☀️ Test successful - checks-actions
Approved by: Veykril
Pushing 4feec4b to master...

@bors bors merged commit 4feec4b into rust-lang:master Jul 30, 2024
11 checks passed
@ilkerBaltaci
Copy link

Stack backtrace:
0: std::backtrace_rs::backtrace::dbghelp64::trace
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library\std\src....\backtrace\src\backtrace\dbghelp64.rs:91
1: std::backtrace_rs::backtrace::trace_unsynchronized
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library\std\src....\backtrace\src\backtrace\mod.rs:66
2: std::backtrace::Backtrace::create
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library\std\src\backtrace.rs:331
3: std::backtrace::Backtrace::capture
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library\std\src\backtrace.rs:296
4: anyhow::error::::msg
5: project_model::utf8_stdout
6: project_model::env::cargo_config_env
7: project_model::workspace::ProjectWorkspace::load
8: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::fold
9: core::ops::function::FnOnce::call_once{{vtable.shim}}
10: std::sys_common::backtrace::__rust_begin_short_backtrace
11: std::thread::Builder::spawn_unchecked
12: alloc::boxed::impl$48::call_once
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library\alloc\src\boxed.rs:2063
13: alloc::boxed::impl$48::call_once
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library\alloc\src\boxed.rs:2063
14: std::sys::pal::windows::thread::impl$0::new::thread_start
at /rustc/051478957371ee0084a7c0913941d2a8c4757bb9/library\std\src\sys\pal\windows\thread.rs:52
15: BaseThreadInitThunk
16: RtlUserThreadStart
2024-08-01T17:54:16.796246Z ERROR Failed to discover cargo config env: "C:\Users\ilker.baltaci\.cargo\bin\cargo.exe" "-Z" "unstable-options" "config" "get" "env" failed, exit code: 101
stderr:
error: config value env is not set

I am getting like the error above. when I use opessl crate with vendored feature, this error is throwen by rust-analyzer. It may be related to proc_macro's. But I am not sure. Using Windows 11. cargo version 1.80.0

@alibektas
Copy link
Member Author

With the latest version this error has been downgraded to a debug log. If there's anything else wrong with your rust-analyzer workflow, this is not the cause.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
S-waiting-on-review Status: Awaiting review from the assignee but also interested parties.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

rust-analyzer fails with "error: config value env is not set"
5 participants