sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Document minimum supported versions of Solaris and Illumos
Labels: T-compiler,A-docs,O-solaris,C-discussion,O-illumos

### Location

https://doc.rust-lang.org/stable/rustc/platform-support.html

### Summary

Rust currently supports multiple Illumos and Solaris targets (see [Platform Support](https://doc.rust-lang.org/stable/rustc/platform-support.html)), but other than saying Rust supports Solaris 11, it doesn't clarify which versions of Illumos and Solaris are supported.

For context, https://github.com/rust-random/getrandom aims to supports all targets/platforms that Rust supports, [including Illumos/Solaris](https://github.com/rust-random/getrandom/blob/v0.2.14/src/solaris_illumos.rs). We currently have fallback logic to support old (pre 2018) Solaris/Illumos versions, and we are wondering when it would be OK to remove those fallbacks (both from `getrandom` and the standard library).

I would propose a minimum platform version of:
  - [Solaris 11.3](https://docs.oracle.com/cd/E53394_01/html/E54838/glrcj.html) (released October 2015)
  - [Illumos 0.29](https://github.com/illumos/illumos-gate/blob/eac40bb3773af39d290bd832c86fb016aa367ca4/usr/src/lib/libc/port/mapfile-vers#L183) (released 2018)

This would allow the standard library to unconditionally use the `getrandom(2)` syscall and unconditionally use [named threads](https://github.com/rust-lang/rust/blob/f9dca46218d4b8efa062aec4fd0820cbb4942aa2/library/std/src/sys/pal/unix/thread.rs#L189).

I'm not sure who's in charge of this decision, maybe @psumbera or @Toasterson
Repository: go
Issue: cmd/go: error on invalid package name
Labels: NeedsInvestigation,GoCommand

### Go version

1.22.2

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/Users/haris/Library/Caches/go-build'
GOENV='/Users/haris/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/haris/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/haris/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/homebrew/Cellar/go/1.22.2/libexec'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/homebrew/Cellar/go/1.22.2/libexec/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.22.2'
GCCGO='gccgo'
AR='ar'
CC='cc'
CXX='c++'
CGO_ENABLED='1'
GOMOD='/Users/haris/developement/apoteka/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/nm/vxlc0g9n7lj5chtlbqpv9rw40000gn/T/go-build2627262892=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

Unintentionally, I used - (hypen) in the package name.
Run 
go generate ./...

### What did you see happen?

Nothing happens. No output, no error.
go generate silently ignored the //go:generate instruction in the file with invalid package identifier

### What did you expect to see?

I expected to see an error indicating the invalid package name.
Repository: ant-design
Issue: Animate Tree subnodes on select
Labels: 🐛 Bug,help wanted,Inactive

### What problem does this feature solve?

Currently, when the user selects a Tree Node that has sub-nodes and we want those sub-nodes to expand, they are expanded without animation. While expanding/collapsing a parent Node has animation.

### What does the proposed API look like?

Maybe introduce a new bool prop animateOnSelect or something.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Maya navigation scheme breaks Viewport MMB panning
Labels: enhancement,topic:editor,topic:input,topic:3d

### Tested versions

- Reproducible in: v4.2.1.stable.official [b09f793f5]

### System information

Windows 11, v4.2.1.stable.official [b09f793f5]

### Issue description

Setting Navigation Scheme in Editor Settings->Editor->3D to Maya unnecessarily breaks/deactivates Viewport middle mouse button panning. While Maya navigation scheme defaults to Alt+MMB to pan, there is no reason to disable regular (non-Alt) MMB panning in the viewport. 

Not having to press Alt key fist to MMB pan is much more comfortable especially when working with 2D content, and is consistent across multiple editors. So that MMB for panning would be shared for 3D scenes, 2D scenes and editors such as Graph Editor.

There is no justification to disable the MMB drag in Maya navigation mode if it is not bound to anything else.

### Steps to reproduce

1. Go to Navigation Scheme in Editor Settings->Editor->3D and set Navigation Scheme
Result: MMB without Alt key doesn't pan the 3D scene viewport, while it does pan the 2D scene viewport
Expected: MMB without Alt key pans all viewports, regardless of their type

### Minimal reproduction project (MRP)

[MRP.zip](https://github.com/godotengine/godot/files/15159352/MRP.zip)
Repository: ollama
Issue: Chat2DB-SQL-7B
Labels: model request

https://huggingface.co/bartowski/Chat2DB-SQL-7B-exl2
Repository: ollama
Issue: Unable to pull model
Labels: bug,networking

### What is the issue?

PS C:\WINDOWS\system32> ollama run llama3
pulling manifest
Error: pull model manifest: Get "https://registry.ollama.ai/v2/library/llama3/manifests/latest": read tcp 10.204.34.68:61116->104.21.75.227:443: wsarecv: An existing connection was forcibly closed by the remote host.

### OS

Windows

### GPU

Intel

### CPU

Intel, AMD

### Ollama version

0.1.27
Repository: stable-diffusion-webui
Issue: [Bug]: fastapi needs to be updated
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### Description

On a fresh install sd-webui installs this combination of packages

fastapi-0.94.0
albumentations-1.4.4
pydantic-2.7.1 (Required by albumentations 1.4.4, incompatible with fastapi-0.94.0)

So when I try to run it i get a pydantic error (`ImportError: cannot import name 'Undefined' from 'pydantic.fields'`), and reinstalling the same pydantic version gives me this:

```
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
fastapi 0.94.0 requires pydantic!=1.7,!=1.7.1,!=1.7.2,!=1.7.3,!=1.8,!=1.8.1,<2.0.0,>=1.6.2, but you have pydantic 2.7.1 which is incompatible.
```

I solved it by updating fastapi to a version that supports pydantic 2.7.1

fastapi version 0.110.3 to be exact.
Repository: PowerToys
Issue: PowerToys Run: "Open Containing Folder" not selecting/highlighting program
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage,Run-Plugin

### Microsoft PowerToys version

0.80.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

- Activate PowerToys input box
- Type an installed program's name
- Arrow down to a program entry in the results
- Press CTRL-SHIFT-E to open the program's location (or click the sub-icon for _Go-to-location_)
- A Windows Explorer folder opens, albeit without scrolling to or selecting the program, instead unscrolled at the top

### ✔️ Expected Behavior

Expected behavior would be the program's location opening and the program being scrolled to and selected/highlighted

### ❌ Actual Behavior

Instead, PowerToys Run opens the program's folder albeit without scrolling to nor selecting the program, merely a folder unscrolled at the top. This necessitates the user having to manually locate the program in the folder, which can be arduous when a folder contains many numbers of similarly named files.

Windows Explorer has a built-in switch to open an Explorer window with a file pre-selected: `Explorer.exe /select \<file\>`, e.g. `Explorer.exe /select,"C:\Windows\System32\mspaint.exe"`

### Other Software

Windows 10 Pro x64 | 22H2 Build 19045.4291
Repository: pytorch
Issue: MaxPool2D memory leakage on device MPS
Labels: high priority,module: memory usage,triaged,module: mps

### 🐛 Describe the bug

On MPS device, allocated memory keeps increasing when the model has MaxPool2D modules. It raises an out of memory error when tensor sizes are too big. 

Here is an example:

```python 

import torch 
device = "mps:0"



torch_model = torch.nn.Sequential(
    torch.nn.Conv2d(32,32,3),
    torch.nn.MaxPool2d((2,2)),
    torch.nn.Conv2d(32,32,3),
    torch.nn.MaxPool2d((2,2)),
    torch.nn.Conv2d(32,32,3),
    torch.nn.MaxPool2d((2,2)),
    torch.nn.Conv2d(32,32,3),
    torch.nn.MaxPool2d((2,2))
)

input = torch.rand(64, 32, 256, 256).to(device)
torch_model.to(device)

for _ in range(10000):
    output = torch_model(input)
    loss = output.sum()
    loss.backward()
    print("allocated memory: ", torch.mps.driver_allocated_memory())
```

In the above code, allocated memory constantly increases at each iteration when MaxPool2D layers are present. Eventually it crashes due to out of memory.  However,  when I remove the MaxPool2D layers, it runs without a problem, as the allocated memory remains constant at each iteration

```python 

import torch 
device = "mps:0"



torch_model = torch.nn.Sequential(
    torch.nn.Conv2d(32,32,3),
    # torch.nn.MaxPool2d((2,2)),
    torch.nn.Conv2d(32,32,3),
    # torch.nn.MaxPool2d((2,2)),
    torch.nn.Conv2d(32,32,3),
    # torch.nn.MaxPool2d((2,2)),
    torch.nn.Conv2d(32,32,3)
    # torch.nn.MaxPool2d((2,2))
)

input = torch.rand(64, 32, 256, 256).to(device)
torch_model.to(device)

for _ in range(10000):
    output = torch_model(input)
    loss = output.sum()
    loss.backward()
    print("allocated memory: ", torch.mps.driver_allocated_memory())
```

This code runs without a problem. 

### Versions

PyTorch version: 2.3.0
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.4.1 (arm64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.3.9.4)
CMake version: Could not collect
Libc version: N/A

Python version: 3.11.5 (main, Sep 11 2023, 08:31:25) [Clang 14.0.6 ] (64-bit runtime)
Python platform: macOS-14.4.1-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M1 Pro

Versions of relevant libraries:
[pip3] numpy==1.26.4
[pip3] torch==2.3.0
[pip3] torchaudio==2.3.0
[pip3] torchvision==0.18.0
[conda] numpy                     1.26.4          py311he598dae_0  
[conda] numpy-base                1.26.4          py311hfbfe69c_0  
[conda] pytorch                   2.3.0                  py3.11_0    pytorch
[conda] torchaudio                2.3.0                 py311_cpu    pytorch
[conda] torchvision               0.18.0                py311_cpu    pytorch

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen
Repository: tauri
Issue: [bug] cannot fix the position of a webview and set auto_resize at the same time
Labels: type: bug,status: needs triage,scope: unstable flag

### Describe the bug

I create a webview and add it to my main window. I set a `LogicalPosition` to be cero in the horizontal axis, and an offset in the vertical axis. Finally I set `auto_resize`. With this config, the webview is not fixed on the vertical axis as I resize the window. However, If I remove the `auto_resize`, the webview is now fixed.
```
window.add_child(
    WebviewBuilder::new(label, WebviewUrl::External(url)).auto_resize(), 
    LogicalPosition::new(0, offset),
    window.inner_size().unwrap(),
)
```

### Reproduction

_No response_

### Expected behavior

Webview position should be fixed in the vertical axis and it is resizable.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.3.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 18.20.2
    - pnpm: 9.0.2
    - npm: 10.5.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.15
    - tauri-build [RUST]: 2.0.0-beta.12
    - wry [RUST]: 0.39.1
    - tao [RUST]: 0.27.0
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 2.0.0-beta.1

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../../dist/apps/exam-web
    - devUrl: http://localhost:3000/
    - framework: React
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

`auto_resize`:
https://github.com/tauri-apps/tauri/assets/46209454/833ce09d-d2c2-46ff-928f-3620ee5604e3

No `auto_resize`:
https://github.com/tauri-apps/tauri/assets/46209454/bd06caa4-ede7-415d-a0b3-736287add084
Repository: stable-diffusion-webui
Issue: [Feature Request]: "Installing open_clip" step may be no longer needed?
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

When doing a new installation: 
`Installing open_clip`
`Downloading https://github.com/mlfoundations/open_clip/archive/bb6e834e9c70d9c27d0dc3ecedeebeaeb1ffad6b.zip`
Compile and install it as `open_clip_torch==2.7.0`
And then install `open-clip-torch==2.20.0` from requirements_version.txt, uninstalling `2.7.0`.
So why not remove the step above?

### Proposed workflow

Just remove `Installing open_clip` as mentioned.

### Additional information

_No response_
Repository: react
Issue: [React 19] react-reconciler README is missing scheduler and form hooks
Labels: React 19

## Summary

I've been working on updating the types for react-reconciler, and found methods are still missing from its README after recent updates. These are detailed in https://github.com/pmndrs/react-three-fiber/pull/3242 based on implementation, but they are as follows:
- `NotPendingTransition` #26722
- `setCurrentUpdatePriority`, `getCurrentUpdatePriority`, `resolveUpdatePriority` #28751
- `resetFormInstance` #28804
- `requestPostPaintCallback` #25105
- `shouldAttemptEagerTransition` #26025
- `trackSchedulerEvent` #31528
- `resolveEventType`, `resolveEventTimeStamp` #31008

I can open a PR for updating the README specifically, but I haven't looked deeper to see if there was anything else missing in the repo.
Repository: ant-design
Issue: table组件嵌套子表格，设置scroll.y之后展示问题
Labels: Inactive,unconfirmed

### Reproduction link

[https://codepen.io/TinyD-the-bashful/pen/gOyJpvR?editors=0010](https://codepen.io/TinyD-the-bashful/pen/gOyJpvR?editors=0010)

### Steps to reproduce

表格设置了 scroll={{ x: 'max-content' }}，同时子表格设置scroll={{ y: 300 }}

### What is expected?

宽度正常，或者经设置宽度后正常

### What is actually happening?

出现子表格宽度1e 06px现象

| Environment | Info |
| --- | --- |
| antd | 5.16.4 |
| React | react18 |
| System | 14.1.2  |
| Browser | chrome 123.0.6312.87 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Remote Debugger only working once
Labels: bug,platform:android,topic:editor,confirmed,topic:export

### Tested versions

- Reproducible in: 4.1-stable - 4.2.2-stable

### System information

Godot v4.2.2.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3080 (NVIDIA; 31.0.15.5161) - Intel(R) Core(TM) i7-10700K CPU @ 3.80GHz (16 Threads)

### Issue description

I'm working on https://github.com/Nitwel/Immersive-Home, an app for XR Headsets, meaning I have to export to Android. When I start Godot the first time and then run the "Remote Debug" option, everything works as expected in that the remote debugger works fine.

When exporting a second time using the "Remote Debug" button, I can see that Godot sets all params properly when exporting:
```
0 param: --remote-debug
1 param: tcp://localhost:6008
2 param: --xr_mode_openxr
3 param: --use_immersive
Installing to device (please wait...): Oculus Quest 3
--- Device API >= 21; debugging over USB ---
--- DEVICE API >= 21; DEBUGGING OVER USB ---
Reverse result: 0
```
But the remote debugger just wont ever start again. Only after completely restarting Godot it works again, but only the first time.

I should add that I've asked @BastiaanOlij about this problem already and he mentioned that he never had that problem. 

### Steps to reproduce

1. Open Godot
2. Make sure "Debug > Deploy with Remote Debug" is enabled
3. Export to Android using "Remote Debug"
4. Everything works
5. Export to Android using "Remote Debug" again
6. Debugger doesn't start

### Minimal reproduction project (MRP)

[demo.zip](https://github.com/godotengine/godot/files/15162011/demo.zip)
Make sure to install godotopenxrvendors. (it was to large for upload)
Repository: vscode
Issue: Two code-actions entry points with same icon
Labels: ux,under-discussion,notebook

Both sparkle icons trigger code actions but the lower one has one more non-quick-fix code action. This is confusing.

![image](https://github.com/microsoft/vscode/assets/16353531/f25cbcf9-b8ee-4da8-a8bb-739ecd097198)

Version: 1.89.0-insider
Commit: dfa434a13c74b847c9edc4a82e5ca0588f24ce9d
Date: 2024-04-29T22:54:38.075Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0
Repository: angular
Issue: PromiseRejectionEvent not fired
Labels: area: zones

### Which @angular/* package(s) are the source of the bug?

zone.js

### Is this a regression?

No

### Description

The PromiseRejectionEvent is not triggered when zone.js is included on the webpage. The issue stems from zone.js's inability to construct a PromiseRejectionEvent because options parameter is undefined - `{ promise: undefined, reason: undefined }`

Event is not fired and silently ignored here: https://github.com/angular/angular/blob/main/packages/zone.js/lib/common/promise.ts#L82
Fails to construct PromiseRejection error here: https://github.com/angular/angular/blob/main/packages/zone.js/lib/browser/browser.ts#L316

![image](https://github.com/angular/angular/assets/12775440/62106906-5f09-4188-b753-9649cdf3c9ea)


Here is a minimal example to reproduce the issue. Note that if you remove the zone.js script, the event fires as expected.
```html
<!doctype html>
<html lang="en">
	<head>
		<meta charset="UTF-8" />
		<title>Title</title>
		<script src="https://cdn.jsdelivr.net/npm/zone.js@0.14.4/bundles/zone.umd.min.js"></script>
	</head>
	<body>
		<script>
			window.addEventListener('unhandledrejection', (event) =>
				console.log('unhandledrejection', event, event.promise, event.reason),
			)

			const scriptEl = document.createElement('script')
			scriptEl.innerHTML = "Promise.reject('Error happened :(')"
			document.body.append(scriptEl)
		</script>
	</body>
</html>

```

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
zone.js: latest
```


### Anything else?

_No response_
Repository: node
Issue: Define node::StreamBase's "onread" property as a JavaScript accessor
Labels: stream,v8 engine,deprecations

### Version

v22.0.0-pre

### Platform

_No response_

### Subsystem

_No response_

### What steps will reproduce the bug?

V8 is deprecating `v8::ObjectTemplate::SetAccessor(..)` (see https://crbug.com/336325111) which is used by node::StreamBase for defining "onread" property.
V8 suggests to use `v8::ObjectTemplate::SetNativeDataProperty(..)` instead but it has a slightly different behaviour and Node is currently relying on the old one.

The `SetAccessor(..)` defines a JavaScript data property which violates the JavaScript spec for the following use case:
```js
  var proto = stream;
  var obj = Object.create(proto);
  obj.onread = 42; // [*]
```
According to the spec `[*]` should set the `onread` property on `obj` while for a `SetAccessor`-defined property V8 would trigger the property setter callback.
The `SetNativeDataProperty`-defined property would behave like a regular data property according to the spec.

Node defines "onread" property on the stream's **prototype** object while it sets the value via stream **instance** objects. This approach heavily depends on non-standard `SetAccessor`'s semantics. 
The right fix would be to define "onread" property as a JavaScript accessor using `v8::ObjectTemplate::SetAccessorProperty(..)`. 

The following fix for Node-ci seems to work: https://github.com/v8/node/pull/183

### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior? Why is that the expected behavior?

_No response_

### What do you see instead?

n/a

### Additional information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Add upscale button to full screen view
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Add the individual upscale function to the full screen view

### Proposed workflow

1. Go to full screen view
2. Press upscale button
3. Upscale image


### Additional information

_No response_
Repository: rust
Issue: Tracking issue for future-incompatibility lint `uncovered_param_in_projection`
Labels: A-lints,A-trait-system,T-compiler,C-future-incompatibility,C-tracking-issue,T-types,A-coherence,L-uncovered_param_in_projection

This is a tracking issue for the lint `uncovered_param_in_projection` which was added in #117164.

The lint detects a violation of one of Rust's orphan rules for foreign trait implementations that concerns the use of type parameters inside trait associated type paths ("projections") whose output may not be a local type that is mistakenly considered to "cover" said parameters which is **unsound** and which will be rejected by a future version of the compiler.

Originally reported in #99554 (kept open) and tracked in rust-lang/types-team#104.

### Example

```rs
// dependency.rs

#![crate_type = "lib"]

pub trait Trait<T, U> {}
```

```rs
// dependent.rs

trait Identity {
    type Output;
}

impl<T> Identity for T {
    type Output = T;
}

struct Local;

impl<T> dependency::Trait<Local, T> for <T as Identity>::Output {}

fn main() {}
```

This will produce:

```
warning[E0210]: type parameter `T` must be covered by another type when it appears before the first local type (`Local`)
  --> dependent.rs:11:6
   |
11 | impl<T> dependency::Trait<Local, T> for <T as Identity>::Output {}
   |      ^ type parameter `T` must be covered by another type when it appears before the first local type (`Local`)
   |
   = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
   = note: for more information, see issue #124559 <https://github.com/rust-lang/rust/issues/124559>
   = note: implementing a foreign trait is only possible if at least one of the types for which it is implemented is local, and no uncovered type parameters appear before that first local type
   = note: in this case, 'before' refers to the following order: `impl<..> ForeignTrait<T1, ..., Tn> for T0`, where `T0` is the first and `Tn` is the last
   = note: `#[warn(uncovered_param_in_projection)]` on by default
```