sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: TAIT: "hidden type captures lifetime" even if it's static, inside closure
Labels: F-type_alias_impl_trait

```rust
    let x: &'static u32 = &0;
    let _closure = move || {
        type T = impl Sized;
        let x: T = x;
    };
```

This code fails to compile [playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=bef54f38293950f9265140db79317e78) with: 

```
error[[E0700]](https://doc.rust-lang.org/nightly/error-index.html#E0700): hidden type for `T` captures lifetime that does not appear in bounds
 --> src/lib.rs:7:20
  |
7 |         let x: T = x;
  |                    ^
  |
  = note: hidden type `&u32` captures lifetime '_#8r
```

even though `x` is `'static`, so it shouldn't require adding any lifetime to `T`'s bounds.

If you move `x` inside the closure then it works:

```rust
    let _closure = move || {
        let x: &'static u32 = &0;
        type T = impl Sized;
        let x: T = x;
    };
```

Seems like `x` having to go through the closure captures makes TAIT not able to use the staticness of it somehow.

Nightly version: 1.67.0-nightly (2022-12-04 53e4b9dd74c29cc9308b)
@rustbot label F-type_alias_impl_trait
Repository: godot
Issue: Cannot override filter for Light2D texture, behavior difference between Vulkan and GL
Labels: bug,topic:core,topic:rendering,usability

### Godot version

4.0.beta7

### System information

Linux AMD R9 380 series, vulkan (both mobile and forward_plus), works OK with gl_compat

### Issue description

I have a 64×64 GradientTexture2D that I use for Light2Ds in my game. For bigger lights, I scale up the light using "texture scale".

This is what it looks like with global Default Texture Filter set to Nearest:
![light-nearest](https://user-images.githubusercontent.com/43048142/205674099-ae6a7782-dfcc-4d56-81da-7b5937d221de.png)

This is what it looks like with global Default Texture Filter set to Linear:
![light-linear](https://user-images.githubusercontent.com/43048142/205674148-7204ee1b-989a-445a-a4d3-3501b893134b.png)

I would like the light to look like the second screenshot, but the rest of the game to look like the first. The problem is that there appears to be no way to override filtering for just the light texture. I have changed CanvasItem property  `texture_filter` for the Light2D, however this makes no difference.

**Note:** It looks like this is only the case for the Vulkan rendering modes. In `gl_compat` mode the light is filtered using linear filtering. However, even there, the `texture_filter` setting on Light2D makes no difference.

### Steps to reproduce

- In project settings: Change Default Texture Filter set to Nearest, and Renderer to one of the Vulkan rendering modes
- Make a Light2D
- Assign a GradientTexture2D
  - Set up a simple gradient (any will do), keep the size small
  - Make its size 32×32 or so (something small to highlight the effect)
- On the Light2D
  - Change `texture_scale` to a higher value like `6`
  - Change `blend_mode` to Mix (not required, but makes the effect more apparent)
  - Change `texture_filter` to Linear

What I'd like: the light texture is filtered linearly
What I see: the light texture is filtered nearest

### Minimal reproduction project

N/A (pretty straightforward to test in any 2D project, but could provide one if desired)
Repository: rust
Issue: Diagnostic points at entire path instead of path argument if the latter does not satisfy a trait bound
Labels: A-diagnostics,T-compiler,D-papercut,D-verbose

Edit: outstanding case:

```rust
struct S<T: Copy>(T);

fn main() {
    let _: S<String>;
}
```

--------

## Generic Arguments

```rust
fn main() {
    let _ = Option::<[u8]>::None;
}
```

Stderr:

```
error[E0277]: the size for values of type `[u8]` cannot be known at compilation time
 --> src/main.rs:2:13
  |
2 |     let _ = Option::<[u8]>::None;
  |             ^^^^^^^^^^^^^^^^^^^^ doesn't have a size known at compile-time
  |
  = help: the trait `Sized` is not implemented for `[u8]`
note: required by a bound in `None`
```

Ideally, it should be:

```
error[E0277]: the size for values of type `[u8]` cannot be known at compilation time
 --> src/main.rs:2:13
  |
2 |     let _ = Option::<[u8]>::None;
  |                      ^^^^ doesn't have a size known at compile-time
  |
  = help: the trait `Sized` is not implemented for `[u8]`
note: required by a bound in `None`
```

## GAT Arguments Specifically

Given the following code:

```rust
struct S;
trait D {
    type P<T: Copy>;
}
impl D for S {
    type P<T: Copy> = ();
}
fn main() {
    let _: <S as D>::P<String>;
}
```

The current output is:

```
error[E0277]: the trait bound `String: Copy` is not satisfied
 --> src/main.rs:9:12
  |
9 |     let _: <S as D>::P<String>;
  |            ^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `String`
```

Ideally the output should look like:

```
error[E0277]: the trait bound `String: Copy` is not satisfied
 --> src/main.rs:9:12
  |
9 |     let _: <S as D>::P<String>;
  |                        ^^^^^^ the trait `Copy` is not implemented for `String`
```

The span is misleading because at first sight one might think that the compiler claimed that the projected type `()` ddid not implement `Copy`. In this simplified case, it's quite easy to see what's going on (especially after reading the message and the label) but I bet in more complex scenarios involving several type parameters and more complicated bounds, it's much more difficult to decipher the diagnostic.
Repository: rust
Issue: Group navigation items in the docs by source crate/module
Labels: T-rustdoc,C-enhancement,A-rustdoc-ui

> I posted [a thread in IRLO](https://internals.rust-lang.org/t/group-navigation-items-in-the-docs-by-source-crate-module/17903) for this feature request, and it seems nobody is against it. Therefore, I come to post an issue here.

For the documentation generated for a type, it seems great to me if the trait implmentations can be grouped by the name of source crate (even source module) in the left navigation panel. Usually, a type won't have too many methods but it can have numerous trait implmentations (especially for numberic related types such as [BigUint](https://docs.rs/num-bigint/0.4.3/num_bigint/struct.BigUint.html) and [rug::Integer](https://docs.rs/rug/1.17.0/rug/struct.Integer.html)).

People usually don't browse the trait implementations by the alphabetic order, they do directly by searching. But sometimes if I don't know which trait I'm looking for, but just want to know what functionalities the type support, it will be great if I can find the implementations by the crate / module name. For example, the implementation of all the arithmetic traits (Add, Sub, etc) can be grouped by the `core::ops` module name.

# Current behavior

(This documentation comes from [`dashu-int::UBig`](https://docs.rs/dashu-int/latest/dashu_int/struct.UBig.html))

![image](https://user-images.githubusercontent.com/9154441/205682469-59f63b65-e475-4d09-8c1d-acef27457a03.png)

# Proposed behavior

The style for the module names is to be defined.

![image](https://user-images.githubusercontent.com/9154441/205685172-c6fd0311-be1f-4931-aeea-9becf2ccf80b.png)
Repository: create-react-app
Issue: Facebook Wallet
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

(Write your answer here.)

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

(Describe your proposed solution here.)

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

(Write your answer here.)

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

(Write your answer here.)
Repository: flutter
Issue: Support Material 3 motion - Transitions
Labels: c: new feature,framework,f: material design,customer: crowd,p: animations,P2,team-design,triaged-design

https://m3.material.io/styles/motion/transitions/transition-patterns

There are now six common transition patterns:
- Container transform
- Forward and backward
- Lateral
- Top level
- Enter and exit
- Skeleton loaders

This work includes:
- [ ] making all of these available and to spec in the [animations](https://pub.dev/packages/animations) package
- [ ] ensuring framework transitions use these transitions rather than hardcoded defaults
Repository: rust
Issue: E0392 incorrectly claims generic parameter used in associated type bound is unused
Labels: A-diagnostics,A-trait-system,T-compiler,D-incorrect

Given the following code ([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=8156598825422fce2a021610c9ae54a0)):
```rust
trait Trait<T> {
    type Type;
}

struct X<U, F: Trait<(), Type = U>>(F);
struct Y<T, U, F: Trait<T, Type = U>>(F);
```

The current output is:
```
error[E0392]: parameter `T` is never used
 --> src/lib.rs:6:10
  |
6 | struct Y<T, U, F: Trait<T, Type = U>>(F);
  |          ^ unused parameter
  |
  = help: consider removing `T`, referring to it in a field, or using a marker such as `PhantomData`
  = help: if you intended `T` to be a const parameter, use `const T: usize` instead

error[E0392]: parameter `U` is never used
 --> src/lib.rs:6:13
  |
6 | struct Y<T, U, F: Trait<T, Type = U>>(F);
  |             ^ unused parameter
  |
  = help: consider removing `U`, referring to it in a field, or using a marker such as `PhantomData`
  = help: if you intended `U` to be a const parameter, use `const U: usize` instead
```

Note that there are no diagnostics for `X`. Indeed, removing `Y` causes the build to succeed.

The first instance of E0392 is allegedly correct according to #60214 and #53589. However, the second diagnostic claiming that `U` is unused seems to be incorrect. Otherwise, E0392 should also complain about `X`'s `U` parameter.

Ideally, the output should look like:
```
error[E0392]: parameter `T` is never used
 --> src/lib.rs:6:10
  |
6 | struct Y<T, U, F: Trait<T, Type = U>>(F);
  |          ^ unused parameter
  |
  = help: consider removing `T`, referring to it in a field, or using a marker such as `PhantomData`
  = help: if you intended `T` to be a const parameter, use `const T: usize` instead
```

@rustbot modify labels +A-traits +D-incorrect
Repository: TypeScript
Issue: Covariant inference widens primitive types inferred from other type params
Labels: Suggestion,Needs Proposal

# Bug Report

### 🔎 Search Terms

widening, inference, covariant, primitive

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link


[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.9.3#code/C4TwDgpgBAkgdgMwgJwKIDcJ2AFXBAHhwD4oBeKHKCAD2CwBMBnKAbwCgooBDBhjLMAAyASyb04KABShIALigjEKKAAUANFAB0O7sgDmTBdzggAlAvQB7EQwDc7AL6coAfjUuFkzMgfsGEADGADZ60AgArnCBwCJWcFAARkoMBC446un41HSMLPBIaJjYeJBExOzEUi7AevoQwAoZNfhN+JlcAPSdignAABbQyBDcwVAA7lbIwQxQgdxM0ANiPAYRALaCc1YRM0nQSoUQswjIVutQAAY4dQ0A2pfxACSspRCOlwC6ly7zwcGJbiBADWCikdTakDM5FI1ls7AsUDh9nY7Fk0AE2AAstwwOQ2L9giIQQpWHMiYIABpeDaJFSOBxcJRgCKNNhI0YRCAKcTIJT6KAMpx+AIhMLbODiKC1AwNUkuXj8YrCMQSFBEHISZhQYEQEBWBBQTHAHFgKropqaCDKhTG013HCfRHIhxC9jJOAMGS3YCaABEIWJwL9mnBBmhZFIHC4dQc3SgAD1XE4zA4gA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type InferEventType<T> = T extends {
  addEventListener(type: infer P, ...args: any): void;
}
  ? P
  : never;

declare function bind<
  T,
  Type extends InferEventType<T>
>(
  target: T,
  type: Type,
  // in the real world case this argument could be infered from `Target[`on${Type}`]`
  callback: (arg: Type) => void
): void;

type EventMap = {
  click: { clientX: number };
  input: { value: string };
};

declare const target: {
  addEventListener<T extends keyof EventMap>(type: T, event: EventMap[T]): void;
};

bind(target, "click", (arg) => {
  arg;
// ^? actual: keyof EventMap, expected: 'click' 
});
```

### 🙁 Actual behavior

The second type parameter gets inferred to the whole computed constraint thanks to those lines in `getCovariantInference`:
https://github.dev/microsoft/TypeScript/blob/048029edc210bc9554119a1a0cb75f0486bcafc0/src/compiler/checker.ts#L24431-L24432

### 🙂 Expected behavior

Since the constraint of the second type parameter is actually a primitive - I would expect this type param to be computed as `'click'`. The problem is that this constraint itself is computed based on the previous type param, so it's not recognized as a primitive.
Repository: TypeScript
Issue: Move 'completeFunctionCalls' into TypeScript language service
Labels: Suggestion,In Discussion

# Problem

In VS Code, the `javascript.suggest.completeFunctionCalls` and `typescriptscript.suggest.completeFunctionCalls` settings make VS Code automatically add parens and argument snipper stops when you complete a function call. For example:

```js
function foo(a, b, c) { }

fo|
```

Result inL

```js
function foo(a, b, c) { }

foo(a, b, c)
```

Users generally like this feature but we cannot properly implement it on the VS Code side as we don't have enough context about the completion or where the completion is occurring. This has resulted in number of bugs that severely limit the usefulness of this feature

## Request
I proposed that we move the logic from `completeFunctionCalls` into the TypeScript server. Not only does TS have more information about the context of the completion and would therefore be better able to implement this, adding this to TS server means that feature could also be used by other editors, including VS

For this, we may want to take inspiration for the snippets we return for overload functions. With these, we return the normal function name completion along with the full overload completion. Returning both completions for `completeFunctionCalls` would be useful as it is sometimes not possible to tell if the user meant to pass around the function as an object or call the function
Repository: youtube-dl
Issue: [OpenDirectory] Add extractor
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->
- http://onj3.andrelouis.com/phonetones/unzipped/Google/Pixel-7/ (Type 1, folder containing folders)
- http://onj3.andrelouis.com/phonetones/unzipped/Google/Pixel-7/ringtones/ (Type 1, folder containing media)
- http://34.81.101.90/ (Type 2, folder containing folders)
- http://34.81.101.90/2030/2022-12-04/ (Type 2, folder containing media)
- http://109.248.156.247/ (Type 3, folder containing folders, i unfortunately couldn't find a type 3 site with media yet)
- http://cds.n2p5u8x8.hwcdn.net/ (S3 bucket .xml file)

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

Please add support for extracting media recursively from common open directory formats, including folders. The open directories also contain metadata including filesize, descriptions, dates, names, hashes and filetypes, which would be nice to extract.
Repository: pytorch
Issue: Unexpected behaviour of 1.13.0
Labels: triaged,module: advanced indexing

### 🐛 Describe the bug

Hello, an unexpected behaviour appeared in PyTorch 1.13.0. I do not see it in Release Notes. Or is it a feature? Why can't I do it this way?

The following code works well in 1.12.1 but fails in 1.13.0:

```python
import torch

mask = torch.full((3,), True, dtype=bool, device='cuda')
array = torch.tensor([1, 2, 3], dtype=torch.float32, device='cpu')
array = array[mask]
print(array)
```

1.13.0 gives the following error:

```bash
RuntimeError: indices should be either on cpu or on the same device as the indexed tensor (cpu)
```

### Versions

pytorch=1.13.0
Repository: TypeScript
Issue: In-file JSX directives not recognized by unused import detection
Labels: Bug,Help Wanted

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.73.1 (Universal)
- OS Version: Darwin arm64 22.1.0

Steps to Reproduce:

I am trying to change the [JSX factory on a per-file basis](https://www.typescriptlang.org/tsconfig#jsxFactory). However, it seems that VS Code does not properly recognize this when it comes to unused import detection. As a result, running something like "Organize import" will remove the needed imports.

![SCR-20221205-gni](https://user-images.githubusercontent.com/134339/205697999-655a96a9-af47-4408-94f6-61a98d1558e5.png)

![SCR-20221205-gqx](https://user-images.githubusercontent.com/134339/205698040-e715ba71-5b61-4ea8-a5b5-6f54260294ec.png)


```js
// tsconfig.json
{
  "compilerOptions": {
    "target": "ESNext",
    "useDefineForClassFields": true,
    "lib": ["DOM", "DOM.Iterable", "ESNext"],
    "allowJs": false,
    "skipLibCheck": true,
    "esModuleInterop": false,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "ESNext",
    "moduleResolution": "Node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react-jsx",
    "paths": { "~/*": ["./src/*"] }
  },
  "exclude": ["node_modules", "cypress", "./cypress.config.ts"]
}
```
Repository: go
Issue: x/tools/cmd/bundle: make import resolution easier
Labels: NeedsInvestigation,Tools

<!--
Our proposal process is documented here:
https://go.dev/s/proposal-process
-->

> Step 1: https://github.com/golang/proposal#the-proposal-process
> The proposal author [creates a brief issue](https://golang.org/issue/new) describing the proposal.
Note: There is no need for a design document at this point.
Note: A non-proposal issue can be turned into a proposal by simply adding the proposal label.
Note: [Language changes](https://github.com/golang/proposal#language-changes) should follow a separate [template](https://github.com/golang/proposal/blob/master/go2-language-changes.md)

Its hard to resolve import conflicts with https://pkg.go.dev/golang.org/x/tools/cmd/bundle.

<https://cs.opensource.google/go/x/tools/+/refs/tags/v0.3.0:cmd/bundle/main.go;l=256>
@adonovan @shurcooL

If the "shadow" thing can't be solved, maybe you can do any of the following?

- default to alias
- allow user to replace an import with "" (removing it) using `-import old=""`
- allow user to replace an import with an alias `-import old="alias import"`
   - but don't reuse the same import twice in output.
-  allow user to define file that imports come from
Repository: vscode
Issue: Editor hover can jump around when accidentally hovering the link again
Labels: bug,editor-hover

![Recording 2022-12-05 at 10 53 46](https://user-images.githubusercontent.com/2193314/205719454-7297836f-b0f2-4d25-9bc9-f201dae354f3.gif)
Repository: rust
Issue: Use simpler abbreviations when reporting error types
Labels: A-diagnostics,T-compiler

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

![image](https://user-images.githubusercontent.com/547158/205720030-8131b086-ce7a-4921-aec0-ee4da615e164.png)


Ideally the output should look like:

Rather than printing the full types to the user, perhaps we want to have a kind of type abbreviation for readability.

The closure type `[closure@f52.rs:13:18 13:21]` is not one the user can type in, nor likely one they'll even track down in the source code. We could potentially just say closure (and specify it is unique in some way)

For the `std::slice::Iter`, I wonder if this is some we might abbreviate for readability. Granted `Iter` by itself is ambiguous, but perhaps there's a simpler way we could write this to allow more space for other information to the user.

<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

<!--
If dramatically different output is caused by small changes, consider also
adding them here.

If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions. The output might also be
different depending on the Edition.
-->
Repository: godot
Issue: Animated Texture stopping
Labels: bug,topic:rendering,confirmed,topic:animation

### Godot version

Godot 4 Beta 6

### System information

Windows 10, Vulkan, NVIDIA GeForce RTX 2080 Ti (527.37)

### Issue description

After leaving the game running in the background for a while the animated textures seem to stop completely most of the time but sometimes they are only stopped for a moment then speed up to seemingly catch up.

### Steps to reproduce

Put Sprite2D with an animated texture as the texture
Launch game and leave it in the background
Eventually it will either desync or stop the animations completely

### Minimal reproduction project

[minimal-reproduction.zip](https://github.com/godotengine/godot/files/10166903/minimal-reproduction.zip)