sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Trait argument from associated type has conflicting impl
Labels: A-associated-items,C-bug,T-types,A-coherence

<!--
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.
-->

I tried this code:

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=5a6bc60775d41ce5ef3ff9656d489c51

```rust
#![feature(try_trait_v2)]
struct Flip<T>(T);
impl<T> std::ops::FromResidual<Flip<T>> for Option<T>
{
    fn from_residual(residual: Flip<T>) -> Self {
        Some(residual.0)
    }
}
```

I expected to see this happen: Code compiles successfully

Instead, this happened:

```
error[[E0119]](https://doc.rust-lang.org/nightly/error-index.html#E0119): conflicting implementations of trait `std::ops::FromResidual<Flip<_>>` for type `std::option::Option<_>`
 --> src/lib.rs:3:1
  |
3 | impl<T> std::ops::FromResidual<Flip<T>> for Option<T>
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: conflicting implementation in crate `core`:
          - impl<T> FromResidual for Option<T>;
```

As you you see, the stdlib has

```rust
impl<T> FromResidual for Option<T> {}
```

Which makes use of a default type arg on `FromResidual` - `<Self as Try>::Residual`. For `Option<T>`, that is `Option<Infallible>`.

So apparently, `FromResidual<Option<Infallible>>` conflicts with `FromResidual<Flip<T>>`.

Playing devil's advocate, we could assume that `FromResidual` is being conservative with its conflicts because `Try::Residual` could change, but it could never change to a type I own.

### Meta
<!--
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.
-->

`rustc --version --verbose`:
```
rustc 1.64.0-nightly (3924dac7b 2022-07-29)
binary: rustc
commit-hash: 3924dac7bb29bc8eb348059c901e8f912399c857
commit-date: 2022-07-29
host: aarch64-apple-darwin
release: 1.64.0-nightly
LLVM version: 14.0.6
```


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"lcnr"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: neovim
Issue: build: Cannot cross-compile because of dependencies configure failed
Labels: enhancement,build

### Feature already in Vim?

No, it is only about building neovim.

### Feature description

I have tried cross-compiling in [4513ECHO/neovim-prebuilt](https://github.com/4513ECHO/neovim-prebuilt), but it has failed.

According  to the error message, we have to add the `--host` parameter to the configure program, however we cannot modify arguments of dependencies configure. How about add a new way to modify it?
Repository: godot
Issue: --convert-3to4 doesn't convert shaders
Labels: bug,topic:editor

### Godot version

5c6744ae54189869580d713a6c31caa90492838a

### System information

Win 10/64 NVIDIA GeForce GTX 1060/PCIe/SSE2

### Issue description

According to my incomplete conversion log found in issue #63672, all my shaders in `assets/shaders` were converted. However the work is far from complete.

* There are new .gdshader files, but all the old .shader files are still there and weren't deleted or renamed.

* The new shaders have `render_mode async_visible`, which GD4 doesn't support and gives an error.

* In fact, the shaders were hardly touched at all. The only difference I see is NORMAL_MAP. There are so many more issues.

These are all of the necessary conversions I have identified for my shaders. I'm not sure about backlight. It appears to be a functional replacement, but it is a poor quality replacement. I haven't decided if it needs an issue filed yet.

```
			$line =~ s/async_visible,?//g;
			$line =~ s/depth_draw_alpha_prepass/depth_draw_opaque/g;
			$line =~ s/hint_color|hint_albedo/source_color/g;
			$line =~ s/hint_white/hint_default_white/g;
			$line =~ s/hint_black_albedo|hint_black/hint_default_black/g;
			$line =~ s/hint_aniso/hint_anisotropy/g;
			$line =~ s/NORMALMAP/NORMAL_MAP/g;
			$line =~ s/INV_CAMERA_MATRIX/VIEW_MATRIX/g;
			$line =~ s/CAMERA_MATRIX/INV_VIEW_MATRIX/g;
			$line =~ s/WORLD_MATRIX/MODEL_MATRIX/g;
			$line =~ s/TRANSMISSION/BACKLIGHT/g;
			$line =~ s/ALPHA_SCISSOR/ALPHA_SCISSOR_THRESHOLD/g;
```

@qarmin
Repository: yt-dlp
Issue: [udemy] Index of video within a chapter
Labels: site-enhancement

### Checklist

- [X] I'm asking a question and **not** reporting a bug or requesting a feature
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2022.07.18** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar questions **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Please make sure the question is worded well enough to be understood

I currently use

    -o '%(playlist_title)s/%(chapter_number)s - %(chapter)s/%(playlist_index)s-%(title)s.%(ext)s'

It download video like

```
Playlist1/1 - Chapter1/1 - Video1.mp4
Playlist1/1 - Chapter1/2 - Video2.mp4
Playlist1/1 - Chapter1/3 - Video3.mp4

Playlist1/2 - Chapter2/4 - Video4.mp4
Playlist1/2 - Chapter2/5 - Video5.mp4
Playlist1/2 - Chapter2/6 - Video6.mp4
```

But I want to be like:

```
Playlist1/1 - Chapter1/1 - Video1.mp4
Playlist1/1 - Chapter1/2 - Video2.mp4
Playlist1/1 - Chapter1/3 - Video3.mp4

Playlist1/2 - Chapter2/1 - Video4.mp4
Playlist1/2 - Chapter2/2 - Video5.mp4
Playlist1/2 - Chapter2/3 - Video6.mp4
```
I mean I want to number video from each chapter starting with 1.

How can I do that?

### Provide verbose output that clearly demonstrates the problem

- [x] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [x] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: flutter
Issue: [tool]Unreadable characters in the debug log
Labels: tool,platform-windows,a: build,P2,team-tool,triaged-tool

## Steps to Reproduce
A New Project can reproduce this issue on my computer.

1. Create a new project.
2. `flutter run --verbose` with built in terminal or external terminal.
3. I can see some strange characters as below:

![image](https://user-images.githubusercontent.com/55800697/181907691-bd65208b-f0dd-4d46-93f1-4cd21abb7ee7.png)

  <summary>Logs</summary>

[Dart-Code-Log-2022-06-06 18-17-15.txt](https://github.com/flutter/flutter/files/9226053/Dart-Code-Log-2022-06-06.18-17-15.txt)

My OS is Win10 professional, Chinese/China.
Visual studio is 2022 community version with language(both English and Chinese Simplified).

I also checked the related issue https://github.com/flutter/flutter/issues/102451 and tried the temporary solution but no help.

The output of flutter doctor:
flutter doctor
Flutter assets will be downloaded from https://storage.flutter-io.cn. Make sure you trustthis source!
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel stable, 3.0.5, on Microsoft Windows [版本 10.0.19044.1826], locale  
    zh-CN)
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2022 17.2.6)
[√] Android Studio (version 2021.2)
[√] VS Code (version 1.69.2)
[√] Connected device (3 available)
[√] HTTP Host Availability

• No issues found!        

Thank you.
Repository: flutter
Issue: Enable text selection handles on desktop platforms with touch screen
Labels: a: text input,c: new feature,framework,c: proposal,a: desktop,good first issue,P3,team-text-input,triaged-text-input

Currently text selection handles are only shown on mobile platforms via Material or Cupertino widgets.

Handles should also be enabled on desktop platforms with touch screen e.g. Windows and Linux laptops, similarly to what Word does:

![text-handles](https://user-images.githubusercontent.com/72562119/181909280-cd669558-ab07-4661-a681-98acb97d9c60.png)
Repository: godot
Issue: Missing OS.get_current_audio_driver_index()
Labels: feature proposal,discussion,topic:audio

### Godot version

3.x

### System information

All

### Issue description

NOTE: This is not a Godot proposal, because I think it belongs to the category which deserves some `leeway` (as stated in godot-proposals).

---

For video driver, you can get the current one by calling `OS.get_video_driver_name(OS.get_current_video_driver())`

Something equivalent should exist for getting the current audio driver.

Currently we can only fetch the following info, which is does not allow to properly narrow it down:

```gdscript
	print(AudioServer.get_device()) # prints: Default
	for d in AudioServer.get_device_list():
		print(d)
        # prints:
        # * Default
        # * alsa_output.pci-0000_00_1f.3.analog-stereo
        # * alsa_output.pci-0000_02_00.1.hdmi-stereo-extra1
	for i in OS.get_audio_driver_count():
		print(OS.get_audio_driver_name(i))
        # prints:
        # * PulseAudio
        # * ALSA
        # * Dummy
```

an `OS.get_current_audio_driver_index()` which fits to `OS.get_audio_driver_name(index)` should be implemented to align with e.g. video driver info.

There's also the "audio/driver" property in the project settings, but that only works if there's a value entered that's actually valid.

In master branch, the `get_audio_driver_count` and `get_audio_driver_name` are not in OS anymore, but in AudioDriverManager, which has no bindings afaics… For Godot 4, this should get exposed again, or at least the latter including `OS.get_current_audio_driver_index()`


### Steps to reproduce

…

### Minimal reproduction project

_No response_
Repository: rust
Issue: showing "the trait bound `impl TArray: TList` is not satisfied" instead of the more correct "the trait bound `<impl TList + TArray as TList>::Element: TSigned` is not satisfied"
Labels: A-diagnostics,T-compiler

Given the following code: [playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=5c4a1be2ec2d4e51abeb8ab5d60fc9d9)
```rust
trait TSigned {}
impl TSigned for i32 {}

trait TList {
    type Element;
}
trait TArray {}

struct ArrayListI32 {}
impl TList for ArrayListI32 {
    type Element = i32;
}
impl TArray for ArrayListI32 {}

struct ArrayListU32 {}
impl TList for ArrayListU32 {
    type Element = u32;
}
impl TArray for ArrayListU32 {}


trait TList2D {
    type Row: TList;
}

struct List2D {}
impl TList2D for List2D {
    type Row = ArrayListI32;
}


fn main() {
    fn2(fn1());
}

fn fn1() -> impl TList2D<Row = impl TArray> {
    List2D {}
}

fn fn2<T>(some: T)
where
    T: TList2D,
    <T::Row as TList>::Element: TSigned,
{
}
```

The current output is:
```
error[[E0277]](https://doc.rust-lang.org/stable/error-index.html#E0277): the trait bound `impl TArray: TList` is not satisfied
  --> src/main.rs:33:5
   |
33 |     fn2(fn1());
   |     ^^^ the trait `TList` is not implemented for `impl TArray`
   |
   = help: the following other types implement trait `TList`:
             ArrayListI32
             ArrayListU32
```

However, `impl TArray: TList` is not the trait bound that is not being satisfied. It is `<impl TArray as TList>::ELement: TSigned` that's not being satisfied.

Further more, help actually suggest `ArrayListU32` as a possible replacement for `impl TArray`, even though `u32` does not implement `TSigned`.

Once you change the return type to `impl TList2D<Row = impl TArray + TList>` the error message makes much more sense:
```
error[[E0277]](https://doc.rust-lang.org/stable/error-index.html#E0277): the trait bound `<impl TList + TArray as TList>::Element: TSigned` is not satisfied
  --> src/main.rs:33:5
   |
33 |     fn2(fn1());
   |     ^^^ the trait `TSigned` is not implemented for `<impl TList + TArray as TList>::Element`
   |
   = help: the trait `TSigned` is implemented for `i32`
note: required by a bound in `fn2`
  --> src/main.rs:43:33
   |
40 | fn fn2<T>(some: T)
   |    --- required by a bound in this
...
43 |     <T::Row as TList>::Element: TSigned,
   |
```

However, sometimes `TList` is private to another crate, making adding `TList` to the return type impossible which then makes the error message much harder to decrypt.

It would be nice if the second error message would be shown without having to add `TList` to the return type. Perhaps showing `<impl TArray as TList>::Element: TSigned` instead to match what was written as the return type.
Repository: godot
Issue: Going to a method or property in editor help sometimes saves to history twice
Labels: bug,topic:editor,usability,regression

### Godot version

v4.0.alpha13.official [59dcddc45]

### System information

-

### Issue description

When following a link in the editor help, two history entries are created if a new help page is being opened:

https://user-images.githubusercontent.com/61291296/181920299-c751e36a-9a35-41cd-b8b2-a7a53e3b5109.mp4

### Steps to reproduce

Ctrl-click on `_ready()` in a new script, then click the back arrow. If the `Node` help page wasn't already open, there will be two entries in the script editor history instead of one.

### Minimal reproduction project

_No response_
Repository: vscode
Issue: Wrong Path of Files Listed Under "Problems" Tab
Labels: bug,tasks

Issue Type: <b>Bug</b>

All extensions temporarily disabled.

I have .ts files in two locations of project. Relative to tsconfig.json file, one folder is "./src", the other is "./SPREST/src". The root path is "d:\dev\SharePoint\SPTools" (this fact is important in the issue). The latter folder was created with 'git submodule add <repo>'. I do a build with the default task, created with Configure Default Build Task. The tsc runs correctly, pointing to the tsconfig.json file. The compiler finds the errors and lists them under "Problems" as expected.

When I try to click open the file that has the errors, the path is all wrong. Suppose the actual path to the source file is "d:\dev\SharePoint\SPTools\SPREST\src\SPListREST.ts". Hovering over the file name under Problems tab brings up the tool tip: "d:\dev\SharePoint\SPTools\SharePoint\SPTools\SPREST\src\SPListREST.ts" and clicking on it says brings up a "File is not found. Create the file?" Note that part of the path is duplicated "\SharePoint\SPTools" and I have not observed this before in working with VSCode ever. 

VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.22000
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz (8 x 1190)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|11.82GB (2.88GB free)|
|Process Argv|--crash-reporter-id 72770bc9-9704-4ad5-8690-6709345d0a89|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
pylanb8912:30529769
vsclangdf:30486550
c4g48928:30535728

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: Snap lines sometimes don't display in editor
Labels: bug,topic:rendering,topic:editor,regression,topic:2d

### Godot version

v4.0.alpha13.official [59dcddc45]

### System information

Pop!_OS 22.04 LTS, Vulkan, GeForce GTX 1660 Ti Mobile

### Issue description

At a particular zoom level, the red snap lines sometimes don't appear in the 2D editor:

https://user-images.githubusercontent.com/61291296/181934768-e9f9ebe9-00ae-4b0d-a040-19289ec3030f.mp4

The behaviour seems to depend on the editor window size (or aspect ratio?):

https://user-images.githubusercontent.com/61291296/181935483-0c928599-62cf-434a-9bf8-cd09899d4098.mp4




### Steps to reproduce

Try moving one icon around with smart snap enabled in the reproduction project.

### Minimal reproduction project

[snap_lines_minimal.zip](https://github.com/godotengine/godot/files/9227003/snap_lines_minimal.zip)
Repository: godot
Issue: VisibleOnScreenEnabler2D has to be visible to work
Labels: enhancement,topic:editor,topic:2d

### Godot version

v4.0.alpha13.official [59dcddc45]

### System information

Windows 10

### Issue description

In Godot 4.0 alpha 13, VisibleOnScreenEnabler2D must be toggled visible in the editor, otherwise it won't work.
That wasn't necessary in alpha 12.

### Steps to reproduce


https://user-images.githubusercontent.com/42905358/181935343-92b62078-1f99-4131-888d-a4fa73a4d607.mp4



### Minimal reproduction project

[VisibleOnScreenEnabler2D.zip](https://github.com/godotengine/godot/files/9227026/VisibleOnScreenEnabler2D.zip)
Repository: pytorch
Issue: Use NestedTensor in RNN models
Labels: triaged,enhancement,module: nestedtensor

### 🚀 The feature, motivation and pitch

Now that NestedTensor is in core, I believe a high-impact application would be to replace many RNN utils, such as:

```
torch.nn.utils.rnn.pad_sequence
torch.nn.utils.rnn.pad_packed_sequence
torch.nn.utils.rnn.pack_sequence
```
with nested tensors. LSTM/GRUs are still heavily used in RL, where long episodes can result in a batch of sequences from 1 to 10,000 timesteps. The entire batch must be zero-padded to the length of the longest episode, which uses a ton of memory (or perhaps the RNN utils do something smarter). The RNN utils also pass around list of indices and sort the outputs, which the user must unsort. Furthermore, the above methods are not flexible -- they do not allow a sequence of zero length, for example.

It would be fantastic to stack a bunch of episodes/rollouts into a ragged NestedTensor and pass this straight into an LSTM. I believe all that's needed are sigmoid, tanh, and linear operations which I believe NestedTensor already supports.

I don't think you would have to worry about backwards compatibility. You can check `instanceof(lstm_input, torch.NestedTensor)` and branch from there.

### Alternatives

_No response_

### Additional context

cc @cpuhrsch @jbschlosser @bhosmer @drisspg
Repository: flutter
Issue: [Linux] support flutter sdk distribution in the form of RPM and DEB packages
Labels: c: new feature,tool,a: first hour,platform-linux,c: proposal,P3,team-tool,triaged-tool

This are the two most common packaging format in the Linux world, please provide them.
Repository: PowerToys
Issue: Is there an option to disable fuzzy search in Powertoys Run?
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

Fuzzy search seems to not always find the right match, and lists several entries that match the fuzzy algorithm, when the actual (exact) match is several entries deep down the list.
I can see why fuzzy search can be useful however.
But is there an option to disable fuzzy search in Powertoys Run?  If not can it be added?
Thanks.

### Scenario when this would be used?

Part of normal usage of Powertoys Run.

### Supporting information

_No response_
Repository: flutter
Issue: Add Dropdown support to `FilterChip`
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

## Use case

This will allow a filter chip to make filter selections via a drop down menu, as showcased in the [Material 3 Design specifications](https://m3.material.io/components/chips/guidelines#dcf3eb06-5f81-4f7d-8299-e32a950d8572). This is mostly useful for desktop, but mobile in some situations too. `DropdownButton` is not customizable enough to support this use-case, and there is no *simple* way to open a drop down menu from a click (see [here](https://github.com/flutter/flutter/issues/104182)).


## Proposal

Either the introduction of a new widget, perhaps `DropdownFilterChip`, modifications to the existing `FilterChip`, or a programmatic way to open up a dropdown menu from an arbitrary widget (preferred, seeing as this would be useful for various other use cases).
Repository: node
Issue: Unexpected path.join behaviour with windows drives
Labels: windows,path

### Version

14.0.0

### Platform

Microsoft Windows NT 10.0.19044.0 x64

### Subsystem

_No response_

### What steps will reproduce the bug?

I typically expect `path.join(path.join(...paths1), ...paths2) === path.join(...paths1, ...paths2);`

This is defied with:
```js
let paths1 = [ 'C:' ];
let paths2 = [ 'abc' ];
```

Essentially because `path.join('C:', 'abc') === 'C:\\abc';`, I expect that `path.join(path.join('C:'), 'abc') === 'C:\\abc';`.

I also expect that if `path.isAbsolute(myPath)` is `false`, so too will `path.isAbsolute(path.join(myPath, anotherPath))` be `false`. This can be summarized by saying "if a path is relative, a child path of that path is also relative", and seems like a very reasonable expectation - but it's defied when:
```js
console.log( path.isAbsolute('C:') ); // false
console.log( path.isAbsolute(path.join('C:', 'abc')) ); // true
```

I also expect `path.join(...cmps).split(path.sep)` to give me a clone of `cmps` in most cases (specifically when `cmps` doesn't contain any `..` or `.` components). This is defied when:
```js
let cmps = [ 'C:' ];
console.log( path.join(...cmps).split(path.sep) ); // I expect [ 'C:' ], but get [ 'C:.' ] (note the "." character)
```

### How often does it reproduce? Is there a required condition?

No context needed

### What is the expected behavior?

```js
assert(path.join(path.join('C:'), 'abc') === 'C:\\abc');
assert(path.isAbsolute('C:') === true);

let cmps = path.join('C:').split(path.sep);
assert(cmps.length === 1);
assert(cmps[0] === 'C:');
```

### What do you see instead?

```js
path.join(path.join('C:'), 'abc') === 'C:abc';
path.isAbsolute('C:') === false;
path.join('C:').split(path.sep)[0] === 'C:.';
```

### Additional information

_No response_
Repository: pytorch
Issue: Is there Doc that explains how to call an extension op in another extension implementation?
Labels: module: docs,module: cpp,triaged

### 📚 The doc issue

For example, there is an extension op which is installed from public repo via `pip install torch-scatter`, and in Python code, it's easy to use this extension:

```py
import torch
output = torch.ops.torch_scatter.scatter_max(x, index)
```

However, I'm writing an C++ extension and want to call this extension as well, but I cannot find any doc that guides how to do this, or I don't know whether Pytorch C++ extension can even support it or not. Briefly, this is something I'd like to do in extension function:

```cpp
torch::Tensor my_op(torch::Tensor x, torch::Tensor y, torch::Tensor z) {
  auto temp = torch::ops::torch_scatter::scatter_max(z, y.view(-1)); // not working
  ..
  return temp;
}
```

### Suggest a potential alternative/fix

_No response_

cc @svekars @holly1238 @jbschlosser