sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: ~const makes rustdoc show duplicate bounds
Labels: T-rustdoc,C-bug

For example, see documentation for the [`Ord`](https://doc.rust-lang.org/std/cmp/trait.Ord.html) trait from the standard library:

```rust
pub trait Ord: Eq + PartialOrd<Self> {
    fn cmp(&self, other: &Self) -> Ordering;

    fn max(self, other: Self) -> Self { ... }
    fn min(self, other: Self) -> Self { ... }
    fn clamp(self, min: Self, max: Self) -> Self
    where
        Self: PartialOrd<Self>,
        //    ^^^^^^^^^^^^^^^^ - this bound is already specified above
    { ... }
}
```

This is slightly confusing IMO.

Related to #91187

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: Touch events doesn't work properly between PlatformView and Widget
Labels: framework,f: gestures,a: platform-views,has reproducible steps,P2,found in release: 3.3,found in release: 3.6,team-framework,triaged-framework

## Steps to Reproduce

Create a native view that you can move inside a container on the native side. The handling is done via a View.OnTouchListener.
Positioning the view on the Y axis on the native side should work without problems.

On the flutter side create a new view where you have a widget list like this:

```
ListView getDummyList() {
    return ListView(
      padding: const EdgeInsets.all(8),
      children: <Widget>[
        ListTile(title: Text('List 1')),
        ListTile(title: Text('List 2')),
        ListTile(title: Text('List 3')),
        ListTile(title: Text('List 4')),
        ListTile(title: Text('List 5')),
        ListTile(title: Text('List 6')),
        ListTile(title: Text('List 7')),
        ListTile(title: Text('List 8')),
        ListTile(title: Text('List 9')),
        ListTile(title: Text('List 10')),
        ListTile(title: Text('List 11')),
        ListTile(title: Text('List 12')),
        ListTile(title: Text('List 13')),
        ListTile(title: Text('List 14')),
        ListTile(title: Text('List 15')),
        ListTile(title: Text('List 16')),
        ListTile(title: Text('List 17')),
        ListTile(title: Text('List 18')),
        ListTile(title: Text('List 19')),
        ListTile(title: Text('List 20')),
        ListTile(title: Text('List 21')),
        ListTile(title: Text('List 22')),
        ListTile(title: Text('List 23')),
        ListTile(title: Text('List 24')),
        ListTile(title: Text('List 25')),
        ListTile(title: Text('List 26')),
        ListTile(title: Text('List 27')),
        ListTile(title: Text('List 28')),
      ],
    );
  }
 ```
 
 Integrate the platform view together with the list view using a stack layout:
 
 ```
  Stack(
        fit: StackFit.expand,
        children: [getDummyList(), PlatformView],
      )
 ```

The platformView is created using PlatformViewHitTestBehavior.translucent as hitTestBehaviour.
The platformView is created adding gestureRecognizers like this:
```
<Factory<OneSequenceGestureRecognizer>>{
        Factory<OneSequenceGestureRecognizer>(
          () =>  VerticalDragGestureRecognizer(),
        )
      }
```

My problem is that the scrolling of the view doesn't work smooth, some touches doesn't work at all. Same thing happen also with the touches on the platform view. I am not always able to drag&drop the view vertically on the screen. Click events work without any problem, it's just the scrolling and drag&drop that do not work. 

[Bug Video](https://drive.google.com/file/d/15cY_4wM992HiFAzLcfMDYHR04hOpVRu6/view?usp=share_link)

Any idea on how can I achieve this?
Repository: opencv
Issue: Allow exception-less compilation
Labels: feature

### Descripe the feature and motivation

Because of try/catch/throw, OpenCV cannot be compiled with exceptions disabled (with `-fno-exception` on clang). Compiling with exceptions creates significant binary-sized overhead (and sometimes even compilation and CPU overhead).  For embedded systems, having a binary as small as possible is needed. Google also does not use exceptions: https://google.github.io/styleguide/cppguide.html#Exceptions

In https://github.com/opencv/opencv/commit/7349b8f5cecfc6eb649b224e58da16d137c3c578, macros `CV_TRY/CV_CATCH` were introduced to use `try/catch` with exceptions and `abort` without, especially for embedded systems.

Those macros are still in 3.x but not in 4.x: https://github.com/opencv/opencv/blob/aba2167d9cc7dd7ff21cbca48a7713e55500da1a/modules/core/include/opencv2/core/cvdef.h#L176

Could they be brought back to 4.x/5.x ? I understand some OpenCV code relies on third party code and therefore exceptions (e.g. imgcodecs/videoio/dnn) but if most code can be compiled without exceptions, it will already be a win. I'll gladly make a pull request to switch most of the code to `CV_TRY/CV_CATCH` if they are back.

### Additional context

_No response_
Repository: godot
Issue: OptionButton popup doesn't take SubViewportContainer transformation into consideration
Labels: bug,confirmed,topic:gui

___

***Bugsquad note:** This issue has been confirmed several times already. No need to confirm it further.*

___

### Godot version

4.0.beta6.mono

### System information

Windows 11

### Issue description

When embedded in a SubViewportContainer whose scale is not 1, the popup menu of OptionButton is scaled and positioned as if the scale were 1.

Using the following scene structure:
![NodeLayout](https://user-images.githubusercontent.com/21371262/204009855-229ef722-a9fa-44b6-af26-a42bf0ff5747.png)

The SubViewportContainer with scale = 1:
![OptionButtonCorrect](https://user-images.githubusercontent.com/21371262/204009719-eb9cc7e4-854d-4c0a-95fa-2a869877299f.png)

The SubViewportContainer with scale = 2:
![OptionButtonIncorrect](https://user-images.githubusercontent.com/21371262/204009936-563810e9-898c-455c-ab8d-e933b06bc07a.png)

### Steps to reproduce

Put an OptionButton inside a SubViewportContainer hierarchy and set the scale of the SubViewportContainer to 2.

### Minimal reproduction project

[OptionButtonIssue.zip](https://github.com/godotengine/godot/files/10093696/OptionButtonIssue.zip)
Repository: vscode
Issue: Ability to scroll parameter hints window using keyboard shortcut
Labels: feature-request,accessibility,editor-parameter-hints

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

It is currently impossible to use a keyboard shortcut to scroll through current Vscode Intellisense details, eg. function description.

This is really important for efficiency and speed during development.

![image](https://user-images.githubusercontent.com/58826024/204011450-80da9bf1-3642-429a-a483-eaf58b820ef1.png)

It's ineffective having to use the mouse many times only for this while coding

[Here](https://stackoverflow.com/questions/74475709/vscode-scroll-through-current-intellisense-using-keyboard-shortcut) is also a Stackoverflow question asking ways to do this.
Repository: vscode
Issue: Support X11 primary selection buffer in inputs
Labels: help wanted,feature-request,linux,workbench-os-integration,keep

This affects Linux users who make use of the primary selection buffer.

Related: https://github.com/microsoft/vscode/issues/130208

Normally you can select something, and then you can paste your most recent selection by middle clicking. It seems like whenever you open an input, eg Command Palette or the File Picker, the contents of the input are considered as a "selection" by the OS so overwrite the primary selection buffer.

Eg, say you are on a website which says "Run the foo command from the command palette". You select "foo", switch to VS Code. Run command palette, and middle click expecting it to paste "foo", however, instead it pastes ">".
Repository: rust
Issue: let chains testing
Labels: F-let_chains

The appearance of #104843 has shown that bugs might still be in hiding for let chains. In order to make the implementation of let chains in rustc more robust, it would be useful to increase the number of places let chains are tested in.

There is an automatted tool to convert uses of the `if_chain` crate to let chains: https://github.com/Alexendoo/if-to-let-chain

One ways to increase testing would be to run the tool on some of the users of `if_chain`, e.g. clippy. Maybe this brings up new bugs like #104843.

@rustbot label F-let_chains
Repository: pytorch
Issue: Enable NCCL for PyTorch on Windows
Labels: oncall: distributed,module: windows,triaged

PyTorch has several backends for [distributed computing](https://pytorch.org/docs/stable/distributed.html). One of them is NVidia NCCL where main benefit is distributed computing for most Devices on GPU.

Unfortunately NVidia NCCL is not supported on Windows, but it is supported for other platforms. 

Goal of this ticket is map importance of this feature, find out blockers and if needed start up work stream on this feature.

**Open questions**
- Investigate impact of missing NCCL support (Who needs it? Is it important for Windows to support it?)
- If NCCL support is important for Windows, are there any blockers? What needs to be done to support it?

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @peterjc123 @mszhanyi @skyline75489 @nbcsm
Repository: neovim
Issue: LSP: textDocument/onTypeFormatting
Labels: enhancement,lsp


### Feature description

### Spec

https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_onTypeFormatting

### Incomplete list of capable servers

- [rust-analyzer](https://rust-analyzer.github.io/)
- [lua-language-server](https://github.com/sumneko/lua-language-server/blob/7400644545baad38c0830c2cbb596f51b88316e5/script/core/type-formatting.lua) 
- [tsserver](https://github.com/microsoft/TypeScript/blob/f6628a4573cd37c26912f78de3d08cd1dbf687a5/lib/protocol.d.ts#L25)
- [ccls](https://github.com/MaskRay/ccls/blob/8a93950fb9828182919df12083a0443ab7ad831e/src/message_handler.cc)

### Benefits

- Format code instantly at typing and reduce the need of requesting `textDocument/(range)formatting` and typing burden.
- Partially alleviate the reliance on indenting (perhaps even a replacement for it?) as most of the current vim indent plugins simply use regex which is not accurate enough, and the [tree-sitter one](https://github.com/nvim-treesitter/nvim-treesitter#indentation) seldom works now.
- The capability has been standardized in LSP along with `textDocument/(range)formatting` and the other two have been already implemented for a long time. I think it should be trivial and reasonable to add support for it either.

### Possible implementation

[coc.nvim](https://github.com/neoclide/coc.nvim/blob/2d0634eb8064fd483f78e38e72feed30d5a418b9/src/handler/format.ts#L107)

The support has been added there for years and the implementation is an excellent reference. The key listening is implemented by [a combination of autocmd events](https://github.com/neoclide/coc.nvim/blob/2d0634eb8064fd483f78e38e72feed30d5a418b9/src/handler/format.ts#L63-L77).

[A version use `vim.on_key`](https://github.com/yioneko/nvim-type-fmt/blob/main/lua/type-fmt.lua)

This one uses `vim.on_key` to make it possible to receive special inserted chars like `\r`, as some servers support `onTypeFormatting` on newline (`\n`). The caveat is that `vim.on_key` actually listens on rhs of mapping, which doesn't reflect what the char user actually typed. A better approach might be needed.
Repository: PowerToys
Issue: Request Treesize
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

a feature that allows you to quickly see the size of all files and folders from the root of a drive on tree view, like treesize view

### Scenario when this would be used?

right-clic and found treesize

### Supporting information

for example : 

![TreeSize](https://user-images.githubusercontent.com/33749403/204030122-aabc214f-899e-4ea6-a3ab-7fcb57628b2b.png)
Repository: go
Issue: x/net/http2: internal error: attempt to send frame on a closed stream
Labels: NeedsInvestigation


### What version of Go are you using (`go version`)?
1.19.3

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?
amd64 linux

### What did you do?

This is not an easy issue to reproduce because it seems requiring a lot of concurrency and high load of requests.
Under such high load scenario, we observe a panic in the go routine that is serving the http2 connection.

Because this panic occurs in the path of the serve(), and there is no panic recover, when it occurs, the connection is closed.
However, if the panic occurred in the scope of the runHandler, it would have been caught and recovered.
So, it is not clear to me why this particular is not covered by a panic handler.

Looking into the specific case, it seems that what is happening is that some frames are being queued to be written, and in parallel something triggered the close of a stream. 
During the loop of the serve() method, frames are dequeued to be written, which encounter a frame for a stream that was already closed, thus resulting in the panic.


### What did you expect to see?

The connection just fails because the panic occurs in the execution path of the serve() which doesn't recover from panics as it occurs if it was done within the runHandler method.

The http2 connection to recover from the panic and keep the http2 connection in a stable state and reusable.

### What did you see instead?
```
panic: internal error: attempt to send frame on a closed stream: [FrameWriteRequest stream=907097, ch=false, writer=http2.writeWindowUpdate]

goroutine 136 [running]:
golang.org/x/net/http2.(*serverConn).startFrameWrite(0xc0003f2300, {{0x1386c48, 0xc053eb8ce8}, 0xc00db48000, 0x0})
    golang.org/x/net/http2/server.go:1200 +0x439
golang.org/x/net/http2.(*serverConn).scheduleFrameWrite(0xc0003f2300)
    golang.org/x/net/http2/server.go:1323 +0x105
golang.org/x/net/http2.(*serverConn).writeFrame(0xc0003f2300, {{0x1386c48?, 0xc06bcbf5d0?}, 0x0?, 0x0?})
    golang.org/x/net/http2/server.go:1176 +0x1f3
golang.org/x/net/http2.(*serverConn).sendWindowUpdate32(0xc0003f2300, 0x0, 0xea)
    golang.org/x/net/http2/server.go:2369 +0xb8
golang.org/x/net/http2.(*serverConn).sendWindowUpdate(0xc0003f2300, 0xc00098b410?, 0xc0000dd759?)
    golang.org/x/net/http2/server.go:2353 +0x95
golang.org/x/net/http2.(*serverConn).closeStream(0xc0003f2300, 0xc00db48000, {0x137de60, 0xc00007e550})
    golang.org/x/net/http2/server.go:1591 +0x194
golang.org/x/net/http2.(*serverConn).wroteFrame(0xc0003f2300, {{}, {{0x1385398, 0xc016c23dd0}, 0xc00db48000, 0xc01c2b4360}, {0x0, 0x0}})
    golang.org/x/net/http2/server.go:1266 +0x165
golang.org/x/net/http2.(*serverConn).serve(0xc0003f2300)
    golang.org/x/net/http2/server.go:908 +0xc72
golang.org/x/net/http2.(*Server).ServeConn(0xc0007601c0, {0x1391f50?, 0xc0001ec000}, 0xc000018ef0)
    golang.org/x/net/http2/server.go:504 +0xbc5
```
Repository: deno
Issue: Deno Bundle uses weird require("internal/event_target")
Labels: bug,swc

Hello, `deno bundle` is generating thuis weird require("internal/event_target") code, which is syntax that I don't think Deno really supports! The problem then arises when converting to Node using `dnt`, because then it crashes when trying to use the node package.

I can't find anything related to this out there. Please someone bring some light into this.
Repository: storybook
Issue: [Bug]: Conflicting values for 'process.env.NODE_ENV' when using Angular builders
Labels: bug,angular

### Describe the bug

When using the `@storybook/angular:start-storybook` I get terminal logging, that I do not get when running without the builders and just triggering an `npm run storybook`. 
 
I get this with a fresh NG14 + Storybook setup.

```
WARNING in DefinePlugin
Conflicting values for 'process.env.NODE_ENV'

1 WARNING in child compilations (Use 'stats.children: true' resp. '--stats-children' for more details)

1 warning has detailed information that is not shown.
Use 'stats.errorDetails: true' resp. '--stats-error-details' to show it.
```

Do I have something misconfigured or do I need to apply additional configuration?

### To Reproduce

```shell
https://github.com/evtk/storybook-playground
```


### System

```shell
Environment Info:

  System:
    OS: macOS 13.0.1
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 16.18.0 - /opt/homebrew/opt/node@16/bin/node
    npm: 8.19.2 - /opt/homebrew/opt/node@16/bin/npm
  Browsers:
    Chrome: 107.0.5304.121
    Safari: 16.1
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: TsConfig solution-style throws warning
Labels: bug,angular,typescript

### Describe the bug

Running Storybook for Angular. I have a tsconfig project that contains the `solution-style` [setup](https://devblogs.microsoft.com/typescript/announcing-typescript-3-9/#solution-style-tsconfig). But running storybook throws a bunch of warnings on this:

```
6% setup before compile angular-compiler<i> [webpack-dev-middleware] wait until bundle finished
Warning: The inferred tsconfig file "/Users/**/Documents/git/storybook-playground/tsconfig.json" appears to be "solution-style" since it contains no root files but does contain project references.
This is probably not wanted, since ngcc is unable to infer settings like "paths" mappings from such a file.
Perhaps you should have explicitly specified one of the referenced projects using the --tsconfig option. For example:

  ngcc ... --tsconfig "./tsconfig.app.json"
  ngcc ... --tsconfig "./tsconfig.ide.json"
  ngcc ... --tsconfig "./tsconfig.spec.json"

Find out more about solution-style tsconfig at https://devblogs.microsoft.com/typescript/announcing-typescript-3-9/#solution-style-tsconfig.
If you did intend to use this file, then you can hide this warning by providing it explicitly:

  ngcc ... --tsconfig "tsconfig.json"
```
What I don't get is why Storybook would catch that tsconfig file, since I have configured the setup to use the `tsconfig.json` inside the `.storybook` folder. And this tsconfig is based on the `tsconfig.app.json` in the root.

```
        "storybook": {
          "builder": "@storybook/angular:start-storybook",
          "options": {
            "tsConfig": ".storybook/tsconfig.json",     <------ NOTICE
            "browserTarget": "storybook-playground:build:production",
            "port": 6006
          }
        },
```

Why do I still get this logging?
  

### To Reproduce

```shell
https://github.com/evtk/storybook-playground
```


### System

```shell
Environment Info:

  System:
    OS: macOS 13.0.1
    CPU: (10) arm64 Apple M1 Pro
  Binaries:
    Node: 16.18.0 - /opt/homebrew/opt/node@16/bin/node
    npm: 8.19.2 - /opt/homebrew/opt/node@16/bin/npm
  Browsers:
    Chrome: 107.0.5304.121
    Safari: 16.1
```


### Additional context

_No response_
Repository: rust
Issue: when rustc suggests alternative solutions, rustfix will apply none of them 
Labels: A-diagnostics,T-compiler,D-diagnostic-infra

<!--
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 -->
`src/test/ui/lint/let_underscore/let_underscore_drop.rs`
```rust
// check-pass
#![warn(let_underscore_drop)]

struct NontrivialDrop;

impl Drop for NontrivialDrop {
    fn drop(&mut self) {
        println!("Dropping!");
    }
}

fn main() {
    let _ = NontrivialDrop; //~WARNING non-binding let on a type that implements `Drop`
}
```

The current output is:

```
warning: non-binding let on a type that implements `Drop`
  --> src/main.rs:13:5
   |
13 |     let _ = NontrivialDrop; //~WARNING non-binding let on a type that implements `Drop`
   |     ^^^^^^^^^^^^^^^^^^^^^^^
   |
note: the lint level is defined here
  --> src/main.rs:2:9
   |
2  | #![warn(let_underscore_drop)]
   |         ^^^^^^^^^^^^^^^^^^^
help: consider binding to an unused variable to avoid immediately dropping the value
   |
13 |     let _unused = NontrivialDrop; //~WARNING non-binding let on a type that implements `Drop`
   |         ~~~~~~~
help: consider immediately dropping the value
   |
13 |     drop(NontrivialDrop); //~WARNING non-binding let on a type that implements `Drop`
   |     ~~~~~              +
```
It's great that we can suggest several solutions here BUT this will prevent rustfix from applying ANY of them :sweat_smile: 

````
The full error message was:

> Could not replace range 181...188 in file -- maybe parts of it were already replaced?

This likely indicates a bug in either rustc or cargo itself,
and we would appreciate a bug report! You're likely to see
a number of compiler warnings after this message which cargo
attempted to fix but failed. If you could open an issue at
https://github.com/rust-lang/rust/issues
quoting the full output of this command we'd be very appreciative!
Note that you may be able to make some more progress in the near-term
fixing code with the `--broken-code` flag
````

I wonder if we can be more clever about this, perhaps flags the first one somehow and and tell rustfix "apply this, and only if that fails to compile, try this other suggestion" ?
Repository: vscode
Issue: Expose User tasks and all task commands in vscode Web
Labels: feature-request,tasks,web

<!-- ⚠️⚠️ 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: Web
- OS Version: any

There are many task commands that are not available in the web version such as `Open User Tasks` based on the context key `SHOW_TASKS_COMMANDS_CONTEXT` defined in `src/vs/workbench/contrib/tasks/browser/task.contribution.ts`, which relies on support for shell and process tasks, while these commands can be useful for custom execution tasks.

Is it also possible to expose global tasks to extensions such as extension provides a task that is shared across any workspace. In our use case, the tasks users would like to run would remain consistent across any workspace so an extension being able to define and save a task in the global `tasks.json` would be hugely beneficial.

In the extension API the task constructor does take a scope parameter but as per the comment on it doesn't seem supported.

`		 * @param scope Specifies the task's scope. It is either a global or a workspace task or a task for a specific workspace folder. Global tasks are currently not supported.
`