rust-lang / rust-lang/rust-clippy

Panic: thread '<unnamed>' panicked at 'forcing query with already existing `DepNode`

Open
#9,846 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
13.5k
Forks
2.2k
Avg merge
2d 10h
Merged PRs (30d)
32

Description

Full stack: https://github.com/simbleau/cddns/actions/runs/3456765281/jobs/5769737252

thread '<unnamed>' panicked at 'forcing query with already existing `DepNode`
- query-key: Canonical { max_universe: U0, variables: [], value: ParamEnvAnd { param_env: ParamEnv { caller_bounds: [], reveal: UserFacing, constness: NotConst }, value: Binder(TraitPredicate(<for<'a, 'b, 'c, 'd, 'e, 'f, 'g, 'h> {std::future::ResumeTy, &'a (dyn public_ip::Resolver<'b> + 'c), public_ip::Version, impl std::future::Future<Output = std::option::Option<std::net::IpAddr>>, ()} as std::marker::Send>, polarity:Positive), []) } }
- dep-node: evaluate_obligation(7881d5d93a575fb-b804294736d8ae02)', /rustc/6284998a2677d7e3e8420db783f3aa4fd80d7423/compiler/rustc_query_system/src/dep_graph/graph.rs:316:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust-clippy/issues/new

note: Clippy version: clippy 0.1.66 (6284998 2022-11-12)

query stack during panic:
#0 [evaluate_obligation] evaluating trait selection obligation `for<'a, 'b, 'c, 'd, 'e, 'f, 'g, 'h> {core::future::ResumeTy, &'a (dyn public_ip::Resolver<'b> + 'c), public_ip::Version, impl core::future::future::Future<Output = core::option::Option<std::net::ip_addr::IpAddr>>, ()}: core::marker::Send`
#1 [analysis] running analysis passes on this crate
end of query stack

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked GitHub Actions run to recover the source and toolchain context, then inspect rustc_query_system/src/dep_graph/graph.rs at line 316 and the evaluate_obligation query stack. Reproduce the internal compiler error and determine the smallest triggering case; done means the panic is explained and a verified regression or upstream report is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.