sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Shortcut Mapper Unable To Handle Multiple Keys
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.57.0

### Running as admin

- [ ] Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Keyboard shortcuts provided by Microsoft Whiteboard have multiple keys. Example `Alt + W + 1` or `Alt + W + 2`, etc. However Power Toys do not support such multiple keys to be remapped.

Multiple non-modifier keys are not accepted and only the last pressed non-modifier key in sequence is recorded. In the above instance, pressing `Alt + W + 1` records only `Alt + 1`.

### ✔️ Expected Behavior

Multiple non-modifier keys support is expected. In the above instance, `Alt + W + 1` must be captured.

### ❌ Actual Behavior

Only one non-modifier key is supported. In the above instance `Alt + 1` is recorded.

### Other Software

Microsoft Whiteboard
Repository: create-react-app
Issue: # Issue: Question
Labels: needs triage

If you have a general question about Create React App or about building an app with Create React App we encourage you to post in GitHub Discussions instead of this issue tracker. The maintainers and other community members can provide help and answer your questions there: https://github.com/facebook/create-react-app/discussions

If you're looking for general information on using React, the React docs have a list of resources: https://reactjs.org/community/support.html

If you've discovered a bug or would like to propose a change please use one of the other issue templates.

Thanks!

https://github.com/facebook it

https://github.com/facebook/create-react-app
Repository: vscode
Issue: Unable to drag text into another tab
Labels: feature-request,editor-drag-and-drop


Issue Type: <b>Bug</b>

1. Open two tabs and set to left-right layout.
2. Select the text in the left tab.
3. Drag the text and drop it into the editor on the right.

After releasing the mouse, the text does not appear in the correct position (in the editor on the right).

VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:04.419Z)
OS version: Darwin x64 21.4.0
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz (8 x 2300)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<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>webgl: enabled<br>webgl2: enabled|
|Load (avg)|3, 3, 3|
|Memory (System)|8.00GB (0.03GB free)|
|Process Argv|--crash-reporter-id 72ac00d9-af96-4259-bbd2-7832832bed42|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (19)</summary>

Extension|Author (truncated)|Version
---|---|---
project-manager|ale|12.5.0
vscode-eclipse-keybindings|alp|0.14.0
dart-code|Dar|3.36.0
flutter|Dar|3.36.0
es7-react-js-snippets|dsz|4.4.3
prettier-vscode|esb|9.5.0
auto-close-tag|for|0.5.14
auto-rename-tag|for|0.1.10
vscode-language-pack-ja|MS-|1.66.1
vscode-language-pack-zh-hans|MS-|1.66.1
python|ms-|2022.4.0
vscode-pylance|ms-|2022.3.4
jupyter|ms-|2022.3.1000901801
jupyter-keymap|ms-|1.0.0
jupyter-renderers|ms-|1.0.6
color-highlight|nau|2.5.0
vetur|oct|0.35.0
material-icon-theme|PKi|4.15.0
LiveServer|rit|5.7.5


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
pynewfile477:30463512

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: Redundant quotes inserted when autocopleting a signal name after dollar syntax sugar
Labels: bug,topic:gdscript,topic:editor

### Godot version

3.4.4 stable

### System information

Windows 7 SP1

### Issue description

Redundant quotes are inserted after autocompleting a signal name when quotes are already there.
This:
`
$"Timer".connect("")`

becomes this:

`$"Timer".connect(""tree_entered"")`

### Steps to reproduce

Trigger autocomplete suggestions inside `connect` and autocomplete some signal.

### Minimal reproduction project

https://downgit.github.io/#/home?url=https://github.com/hilfazer/Projects/tree/EngineIssues/Godot/EngineIssues/SignalAutocomplete
Repository: vscode
Issue: Source Control view ignores filesystem scheme
Labels: git,under-discussion

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->

Does this issue occur when all extensions are disabled?: No

- VS Code Version: 1.66
- OS Version: Windows 10 + WSL 2

I've created a VSCode extension that uses the VSCode FileSystemAPI.

It's registers my filesystem using something like...

```typescript
  const fsURI= Uri.parse("myFS:/root");
  workspace.updateWorkspaceFolders(1, 0, {
    uri: fsURI,
    name: "My FS",
  });

  workspace.registerFileSystemProvider(fsURI.scheme, myProvider, {
    isCaseSensitive: true,
    isReadonly: true,
  })
```

The implementation of the provider is irrelevant here (I think) and the `myFS` filesystem itself works as I want it to.

Note that I've used `/root` as the root directory of `myFS`.  Coincidentally, because I'm using WSL, I have all the repos that I've downloaded over the years as subdirs in my root dir e.g. `/root/vscode`.

Once the extension has started and `My FS` appears as a second folder under the VSCode file explorer, the `Source Control` view adds all the git repos I've downloaded over the years into its view.  So `/root/vscode` repo is added when I'm not working on that repo.  I believe this is a bug.  I'd expect this if I had added `file:///root` as a workspace folder but I haven't, I've added `myFS:/root`

I can only think that the Source Control view ignores the URI scheme of the workspace folders and treats `myFS:/root` as `file:///root`.

Am I doing something wrong here e.g. registering `myFS` incorrectly?  Even so - why is the Source Control view deciding that the `/root` in my filesystem is the `/root` in the WSL filesystem?
Repository: pytorch
Issue: Offical libtorch (pytorch c++ frontend) docker image
Labels: module: binaries,feature,triaged

### 🚀 The feature, motivation and pitch

Would it be possible to provide an official libtorch docker image mirorring the official pytorch image? This would lower the barrier to getting setup and deploying applications using libtorch, particularily becuase libtorch is not distributed with any package manager.

I noticed that images are [already created](https://github.com/pytorch/builder/tree/main/libtorch) to build each distribution of libtorch. Based on my understanding it would mostly involve adding extra stages to the docker build to create an image for each platform.

### Alternatives

_No response_

### Additional context

_No response_

cc @seemethere @malfet @osalpekar @atalman @ezyang
Repository: node
Issue: Documentation Parameter's Syntax
Labels: doc

### Affected URL(s)

https://nodejs.org/api/timers.html#setintervalcallback-delay-args

### Description of the problem

![image](https://user-images.githubusercontent.com/52013393/161441817-c0744a53-75e4-44e4-a883-161220ae8789.png)

This `(callback[. delay[, ...args]])` is very confusing. Why is that wierd syntax being used? Can you please use an easier and clearer syntax?
Repository: vscode
Issue: Inline suggestions are not displayed as ghosted text with HC themes
Labels: under-discussion,ghost-text

<!-- ⚠️⚠️ 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. -->
I don't see any reason why inline suggestions wouldn't be displayed as ghosted (grayed) text with high contrast themes. Currently, they are white with all dark HC themes and black with all light HC themes.

I would like if you add one new color setting available to themes for foreground color of inline suggestions and maybe even another setting for their background color.
Repository: godot
Issue: GraphNode offset incorrectly changes if selected from code while dragging another node  
Labels: bug,topic:gui

### Godot version

v3.4.4.stable.official [419e713a2] and `master` [ac591d9]

### System information

Windows 10

### Issue description

```GraphNode.offset``` is set incorrectly if you select it from code while already dragging another node:
![example_gif](https://user-images.githubusercontent.com/13070655/161439143-34f3e455-07d4-48f4-8c77-379fd4a59862.gif)


### Steps to reproduce

1. Start dragging ```GraphNode1```.
2. Set ```GraphNode2.selected = true```, for example from ```GraphNode1.offset_changed()``` signal callback.
3. ```GraphNode2.offset``` is set incorrectly.

### Minimal reproduction project

[GraphEditTest.zip](https://github.com/godotengine/godot/files/8405225/GraphEditTest.zip)
Repository: vscode
Issue: [scss] interpolation validation issues
Labels: bug,css-less-scss

Issue Type: <b>Bug</b>

VSCode misinterprets certain code snippets when [interpolation](https://sass-lang.com/documentation/interpolation) is used, giving errors and warning when the code snippets actually work fine.

Example:
```scss
$function: 'translateY';

.class {
  @if ($function) {
    transform: #{$function}(0); // scss(css-semicolonexpected) after '#{$function}'
  } @else { // scss(unknownAtRules)
    transform: translateY(0);
  }
} // scss(css-ruleorselectorexpected)

@keyframes #{$keyframe-name} { // breaks syntax highlighting on the keyframe selectors (from, to, 100%...)
  from {
    transform: #{$function}(0) translateX(0); // scss(css-semicolonexpected) after '#{$function}'
  }
  100% { // scss(css-ruleorselectorexpected) on '100%'
    transform: #{$function}(100%); // 'transform' is thought to be a selector, scss(css-lcurlyexpected) after 'transform'
  } // scss(css-ruleorselectorexpected)
}
```

VS Code version: Code 1.66.0 (e18005f0f1b33c29e81d732535d8c0e47cafb0b5, 2022-03-30T05:50:14.623Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
pythonvspyl392:30443607
pythontb:30283811
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
pynewfile477:30463512

```

</details>

<!-- generated by issue reporter -->
Repository: rust
Issue: Audit string literals in inline assembly syntax for correct unescaping
Labels: A-inline-assembly

When trying to refresh the status of https://github.com/rust-lang/rust/issues/60495 I noticed that `ast::InlineAsm` (and its nested structures) is the only AST structure that uses plain strings `String` and `Symbol`s.

Other literals in AST use either `ast::Lit` in contexts where arbitrary literals are supported, of `ast::StrLit` in contexts where only string literals (possibly raw) are supported.

This is suspicious and may mean that string literals used in inline assembly are not always unescaped as any other Rust string literals.
"Unescaped as any other Rust string literals" means that e.g. `"\x72ax"` is always treated as semantically equivalent to `"rax"`.

Implementation of inline assembly needs to be audited to make sure that the unescaping happens in all contexts, and some parts of `ast::InlineAsm` may need to use `StrLit` instead of plain strings or symbols.
Repository: vscode
Issue: Syncing changes dialog shows wrong icon
Labels: feature-request,ux,scm,under-discussion,web

<img width="558" alt="CleanShot 2022-04-03 at 16 38 53@2x" src="https://user-images.githubusercontent.com/35271042/161453896-866c8b25-197e-4570-89f0-f985541ca30b.png">

1. open vscode.dev where you had uncommitted changes
2. dialog asking if you want to sync
3. :bug: error appears indicating there may breaking changes

Since this is an error state, the warning icon should not be used here but instead the "error" icon
Repository: rust
Issue: Tracking Issue for `slice_flatten`
Labels: T-libs-api,C-tracking-issue,disposition-merge,finished-final-comment-period

These methods stabilized in #125561 for rust 1.80 🎉 

This issue is now tracking their const-stability.

---

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(slice_flatten)]`

This is a tracking issue for the methods `flatten` and `flatten_mut` on `[[T; N]]`, and `into_flattened` on `Vec<[T; N], A>`.

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
// core::slice

impl<T, const N: usize> [[T; N]] {
    pub fn as_flattened(&self) -> &[T];
    pub fn as_flattened_mut(&mut self) -> &mut [T];
}

// alloc::vec

impl<T, A: Allocator, const N: usize> Vec<[T; N], A> {
    pub fn into_flattened(self) -> Vec<T, A>;
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Implementation: #95579
- [x] Final comment period (FCP)
- [x] #125171
- [x] Stabilization PR #125561
- [ ] Stabilize `<[T]>::as_flattened` const

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilzation PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- ~~Are these the best possible names?~~
Repository: opencv
Issue: undefined references in `libopencv_core.so` (3.2 and 4.2)
Labels: category: core

##### System information (version)
- OpenCV => 3.2 and 4.2
- Operating System / Platform => Ubuntu 18.04 and 20.04 for OpenCV 3.2 and 4.2, respectively
- Compiler => clang 12

##### Detailed description

```
undefined reference to `cv::ocl::Program::Program(const String&)'
undefined reference to `cv::SparseMatConstIterator::operator--()'
```

- `cv::ocl::Program::Program(const String&)`: defined in [ocl.hpp#L604](https://github.com/opencv/opencv/blob/3.2.0/modules/core/include/opencv2/core/ocl.hpp#L604), but not implemented in OpenCV 3.2
- `cv::SparseMatConstIterator::operator--()`: defined in [mat.hpp#L3058-L3061 (3.2)](https://github.com/opencv/opencv/blob/3.2.0/modules/core/include/opencv2/core/mat.hpp#L3058-L3061),  [mat.hpp#L3255-L3258 (3.4)](https://github.com/opencv/opencv/blob/3.4/modules/core/include/opencv2/core/mat.hpp#L3255-L3258), and [mat.hpp#L3255-L3258 (4.x)](https://github.com/opencv/opencv/blob/4.x/modules/core/include/opencv2/core/mat.hpp#L3255-L3258), but not implemented in OpenCV 3.2/3.4/4.x

##### Steps to reproduce

```bash
# install OpenCV 3.2 for Ubuntu 18.04
# install OpenCV 4.2 for Ubuntu 20.04
sudo apt install libopencv-dev
```

For OpenCV 3.2:

```console
$ objdump -TC /usr/lib/x86_64-linux-gnu/libopencv_*.so | grep cv::ocl::Program::Program
0000000000161610 g    DF .text	0000000000000011  Base        cv::ocl::Program::Program(cv::ocl::Program const&)
000000000016eb20 g    DF .text	000000000000000c  Base        cv::ocl::Program::Program(cv::ocl::ProgramSource const&, cv::String const&, cv::String&)
000000000016eb20 g    DF .text	000000000000000c  Base        cv::ocl::Program::Program(cv::ocl::ProgramSource const&, cv::String const&, cv::String&)
0000000000161600 g    DF .text	0000000000000008  Base        cv::ocl::Program::Program()
0000000000161600 g    DF .text	0000000000000008  Base        cv::ocl::Program::Program()
0000000000161610 g    DF .text	0000000000000011  Base        cv::ocl::Program::Program(cv::ocl::Program const&)
0000000000000000      DF *UND*	0000000000000000              cv::ocl::Program::Program(cv::ocl::ProgramSource const&, cv::String const&, cv::String&)
```

For OpenCV 3.2 and 4.2:

```console
$ objdump -TC /usr/lib/x86_64-linux-gnu/libopencv_*.so | grep cv::SparseMatConstIterator::operator
000000000013d890 g    DF .text	0000000000000094  Base        cv::SparseMatConstIterator::operator++()
0000000000000000      DF *UND*	0000000000000000              cv::SparseMatConstIterator::operator++()
```

##### Issue submission checklist

 - [x] I report the issue, it's not a question
 - [x] I checked the problem with documentation, FAQ, open issues,
       forum.opencv.org, Stack Overflow, etc and have not found any solution
 - [x] I updated to the latest OpenCV version and the issue is still there
 - [ ] There is reproducer code and related data files: videos, images, onnx, etc
Repository: pytorch
Issue: Disable Python mode (torch dispatch mode) inside of mode-induced __torch_dispatch__call
Labels: triaged,actionable,module: __torch_dispatch__

### 🚀 The feature, motivation and pitch

When working with Python modes it is very easy to trigger infinite recursion, since most calls to any PyTorch function will end up back in the `__torch_dispatch__` for the mode. This makes, e.g., debug printing a pain, since you have to `no_dispatch` first.

I propose that we should switch the default around: by default, when we enter a `__torch_dispatch__` triggered by a mode, we should *disable* the mode (NB: this is different than `no_dispatch`!). If a user wishes `torch.add` to call back into `__torch_dispatch__`, they can explicitly reenable the mode (they can also explicitly recurse into themselves simply by invoking `self.__torch_dispatch__` directly). The argument is similar to the one posed at https://github.com/pytorch/pytorch/issues/75130 where we shouldn't reenable dispatcher features like autograd by default, and only reenable them if the user wants to reentrantly use the dispatcher on inner objects.

Note that there is a subtlety: I do not recommend we disable tensor-based torch dispatch (triggered by a tensor subclass which defines `__torch_dispatch__`), and the guidance here is irrelevant when considering a `__torch_dispatch__` induced by tensor-based dispatch (since there is no mode to disable). The reasoning here is twofold: (1) if a `__torch_dispatch__` mode is compositional, it may wish to trigger the `__torch_dispatch__` handlers of value objects after it is done performing its transformation--this would not happen by default if we disabled dispatch entirely with `no_dispatch`; (2) classic OO expectations demand that if you make calls on a subclass, those calls should dispatch to the subclass (and not the parent). Doing otherwise would violate this expectation. Instead, we should provide a way for people to, e.g., cast a subclassed tensor object back into an ordinary tensor, or balance at a knife's edge with `no_dispatch`.

This should probably be accompanied by a patch that makes torch dispatch mode work more like https://github.com/pytorch/pytorch/pull/75154 which has a more robust API that allows for chaining modes together.

cc @albanD @zou3519 @rgommers @peterbell10 @bdhirsh @Chillee 

### Alternatives

_No response_

### Additional context

_No response_
Repository: TypeScript
Issue: Ambient type for constructor parameter property with default does not include 'undefined' when the parameter is followed by one without a default
Labels: Bug,Help Wanted,Domain: Declaration Emit

# Bug Report


### 🔎 Search Terms

constructor parameter property default undefined


### 🕗 Version & Regression Information

This is the behaviour in every version in the Playground (3.3 through to 4.6.2)


### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.6.2&ssl=1&ssc=53&pln=1&pc=54#code/MYGwhgzhAEDC0G9rAPYDsIBcBOBXYmK2AFAA64BGIAlsNGNALzQCMATAMwA00FAXNCzZqaAOYBKRAF9oUoA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
class C { constructor(public a = 123, b: string) {} }
```

### 🙁 Actual behavior

`.d.ts` emit:
```ts
declare class C {
    a: number;
    constructor(a: number, b: string);
}
```

### 🙂 Expected behavior

Parameter `a` should be of type `number | undefined`. Otherwise, it's impossible to initialise the field to its default.

Note that if parameter `b` is removed, given a default, or made optional, `a` is then correctly emitted as optional (`a?: number`). Clearly TypeScript won't emit an optional followed by a required parameter, but it also doesn't add the `undefined` type.

If `a` is _not_ a property (remove `public`) the emitted signature correctly includes `undefined`.

**Secondary bug:** `undefined` is also missing from the type hint for `a`. However, the compiler correctly accepts `undefined` when the class is declared inline:

<img width="501" alt="Screen Shot 2022-04-04 at 1 06 18 pm" src="https://user-images.githubusercontent.com/33473032/161467275-cf1449eb-0d4a-4e60-b619-7eb93c615f08.png">

That differs from the behaviour when only the `.d.ts` definition is available, where the compiler then rejects `undefined` in the same position.
Repository: pytorch
Issue: DISABLED test_reduce_full_group_max (__main__.TestDistBackendWithSpawn)
Labels: oncall: distributed,skipped

Platforms: mac

This test was disabled because it is failing on master ([recent examples](http://torch-ci.com/failure/test_reduce_full_group_max%2C%20TestDistBackendWithSpawn)).

I just looked into why flaky test bot didn't catch this, and it looks like the upload test stats step failed due to missing permissions. Where are the instructions to add the lambda invokefunction permission to the runner? https://github.com/pytorch/pytorch/runs/5761918999?check_suite_focus=true

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang