Change:
<ins> error[E0107]: function takes 2 generic arguments but 1 generic argument was supplied --> $DIR/issue-107280.rs:4:5 | LL |     inner::<false>().await |     ^^^^^   ----- supplied 1 generic argument |     | |     expected 2 generic arguments | note: function defined here, with 2 generic parameters: `T`, `PING` --> $DIR/issue-107280.rs:13:10 | LL | async fn inner<T, const PING: bool>() {} |          ^^^^^ -  ---------------- help: add missing generic argument | LL |     inner::<false, PING>().await |                  ++++++ error[E0698]: type inside `async fn` body must be known in this context --> $DIR/issue-107280.rs:4:5 | LL |     inner::<false>().await |     ^^^^^^^^^^^^^^ cannot infer the value of const parameter `PING` declared on the function `inner` | note: the type is part of the `async fn` body because of this `await` --> $DIR/issue-107280.rs:4:21 | LL |     inner::<false>().await |                     ^^^^^^ error[E0698]: type inside `async fn` body must be known in this context --> $DIR/issue-107280.rs:4:5 | LL |     inner::<false>().await |     ^^^^^^^^^^^^^^ cannot infer the value of const parameter `PING` declared on the function `inner` | note: the type is part of the `async fn` body because of this `await` --> $DIR/issue-107280.rs:4:21 | LL |     inner::<false>().await |                     ^^^^^^ error[E0698]: type inside `async fn` body must be known in this context --> $DIR/issue-107280.rs:4:5 | LL |     inner::<false>().await |     ^^^^^^^^^^^^^^ cannot infer the value of const parameter `PING` declared on the function `inner` | note: the type is part of the `async fn` body because of this `await` --> $DIR/issue-107280.rs:4:21 | LL |     inner::<false>().await |                     ^^^^^^ error[E0698]: type inside `async fn` body must be known in this context --> $DIR/issue-107280.rs:4:5 | LL |     inner::<false>().await |     ^^^^^^^^^^^^^^ cannot infer the value of const parameter `PING` declared on the function `inner` | note: the type is part of the `async fn` body because of this `await` --> $DIR/issue-107280.rs:4:21 | LL |     inner::<false>().await |                     ^^^^^^ error[E0698]: type inside `async fn` body must be known in this context --> $DIR/issue-107280.rs:4:5 | LL |     inner::<false>().await |     ^^^^^^^^^^^^^^ cannot infer the value of const parameter `PING` declared on the function `inner` | note: the type is part of the `async fn` body because of this `await` --> $DIR/issue-107280.rs:4:21 | LL |     inner::<false>().await |                     ^^^^^^ error: aborting due to 6 previous errors Some errors have detailed explanations: E0107, E0698. For more information about an error, try `rustc --explain E0107`. </ins>

Discussion:
It appears that the is no longer working. I got this after running on a build that had no issues. I then ran and to do a fresh build and still got the error. I know it isn't related to incremental builds and it's currently giving me a headache.
Can you share some code that produced this error?
The link recently changed. If you don't mind, where did you find this link? (If it's somewhere official, we should change it.)
There is a link in the ICE message in "older" compilers. See for adding the template back
Thanks for explaining! Well, that's really easy to fix; all we need is time travel!
It was part of the compiler output on 1.66.1. Sorry, I can't share the code. I was in the middle of refactoring something and had this pop up. I was able to compile it on nightly and when the compile errors went away the stable compiler no longer had the issue. The project I was working on is ~2600 lines of code and I wouldn't even know where to start. If it happens again I'll do commits so that I can figure out what change triggered this.
Hi!

I seem to have found this ICE or a similar one with this output: It also reproduces in stable 1.66.1, However it doesn't reproduce on stable 1.66.1 or the current nightly (the below version for cargo, unfortunately the rustc version for nightly is hard) The reason I think I have the same or a similar ICE is because, well, it starts out the same as well as having the same query stack: I'll try to reproduce it on Friday ish to bisect where / when this happened, and why (so that we can probably mark it as already fixed, unless I happen to uncover a root cause that still exists)
MRE Full ICE: <details<summaryFull ICE</summary</detailscargo-bisect-rustc for start: Regression in searched nightlies: from nightly-2022-10-15 to nightly-2022-10-30 regressed nightly: nightly-2022-10-21 searched commit range: regressed commit: <details<summarybisected with <a href=''cargo-bisect-rustc</av0.6.5</summaryHost triple: aarch64-apple-darwin Reproduce with: </detailscargo-bisect-rustc for end: Regression in searched nightlies: from nightly-2022-10-21 to nightly-2023-02-24 regressed nightly: nightly-2022-11-27 searched commit range: regressed commit: <details<summarybisected with <a href=''cargo-bisect-rustc</av0.6.5</summaryHost triple: aarch64-apple-darwin Reproduce with: </details
Reading that leads me to which fixed