sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: options reminder on activation key press [feature request]
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Activation keys and combinations thereof are getting increasing in number (powertoys, VS Code)  and hard to remember.

My dream would be that if you push an activation key, you get a popup with all that exist under that key (+combination) to remind you of them.

If you push [window] you see all combinations [window]+{whatever there can be activated}
If you continue with [window]+[left Alt] you see all those combinations listed; [window]+[left Alt]+{whatever can now be activated}

The life of all of us with a limited wet-RAM would most certainly be very happy. Especially for those combinations that we use rarely.


### Scenario when this would be used?

everytime in VS code and powertools and I am sure there would be some combinations in MS Office that would profit.

### Supporting information

_No response_
Repository: godot
Issue: ViewportTexture does not update automatically when there is one more ViewportTexture in the scene
Labels: bug,topic:rendering,topic:shaders

### Godot version

4.0

### System information

Windows10, Vulkan, RTX3060

### Issue description

![1](https://user-images.githubusercontent.com/51391741/223617558-85c53cce-cf10-45da-9207-3e7d0acb5bf0.png)
![2](https://user-images.githubusercontent.com/51391741/223617563-23424ba5-b878-43f1-935f-6de25dfbedda.png)
![3](https://user-images.githubusercontent.com/51391741/223617565-a044979c-a7c0-47b4-b2ce-915529b69eae.png)
Everytime I reopen this scene, I need rechoose the viewporttexture of the "cloud".otherwise it would be purely white.

### Steps to reproduce

1. Viewport1 render a 2d scene to generate ViewportTexture1
2. Viewport2 render a 2d scene to generate ViewportTexture2
3. Mesh1 use the ViewportTexture1 in shader
4. Mesh2 use the ViewportTexture2 in shader


### Minimal reproduction project

[V4Test01.zip](https://github.com/godotengine/godot/files/10917148/V4Test01.zip)
Repository: vscode
Issue: Allow VS-code to respect native titlebar decorations configuration on GNOME/Linux
Labels: feature-request,upstream,linux,electron,titlebar

<!-- ⚠️⚠️ 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. -->
Coming from [#21](https://github.com/piousdeer/vscode-adwaita/issues/21) on [vscode-adwaita](https://github.com/piousdeer/vscode-adwaita), on GNOME Desktop environment (and on other distros as well) we can configure what titlebar decorations appear, viz Minimize, maximize buttons can appear or disappear via GNOME tweaks app.

VS-code doesn't support this by default, and for maximum cross-compatibility, we would like this feature to be customizable.

TLDR:
- allows maximize/minimize button to appear or disappear via settings, just like Microsoft Edge browser does by having  a small corner allocated for the native title bar buttons, while the rest of it is the internal browser GUI.
- Support native titlebar decorations depending on the Distribution/Platform.

Attaching image of window decorations on VS code with `window.titleBarStyle` set to `custom`, GNOME files (Nautilus) on libadwaita 1.2x, GNOME 43.2 and Microsoft Edge browser (Version 109.0.1518.70 (Official build) (64-bit)) with GNOME tweaks, **disabling** maximise and minimize buttons
![image](https://user-images.githubusercontent.com/56764399/223621610-189d27df-3561-4460-bca7-f07d521ed2ec.png)

And with GNOME tweaks **enabling** Maximise/Minimize buttons:
![image](https://user-images.githubusercontent.com/56764399/223622274-7ab25e7b-553b-4977-a0a8-89ed04565388.png)
Repository: TypeScript
Issue: `strictNullChecks` short-circuits the subsequent type checks
Labels: Suggestion,Needs Proposal

# Bug Report

hello， I encounter a strange bug when I use `strictNullChecks: true`, and here is an example:

```ts
interface A {
  a: number;
}
const list: A[] = [];
list[0] ??= {};  // throw an error: Property 'a' is missing in type '{}' but required in type 'A'
list[0] = list[0] ?? {};  // the type checking not work !
list[0] = list[0] || {};  // the type checking not work !
```

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is the behavior in every version I tried
### ⏯ Playground Link

It seems the type checking works after I close the `strictNullChecks` options
[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.2.3#code/JYOwLgpgTgZghgYwgAgILIN4FgBQzlwBcyIArgLYBG0A3LgL64ID2IAzmMgDbAfGoBtALrIAvMmF0cPDgIAMIgPyLxGelJlh5I8WACeABwjMY3XloVjR4gOSkQAEwgxQEBzeSLM9ZMU3aNc20xM1lLZW9AsJ1QixEAH3jIoA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->

```ts
interface A {
  a: number;
}
const list: A[] = [];
list[0] ??= {};  // throw an error: Property 'a' is missing in type '{}' but required in type 'A'
list[0] = list[0] ?? {};  // the type checking not work !
list[0] = list[0] || {};  // the type checking not work !
```

### 🙁 Actual behavior

`list[0] = list[0] ?? {};` doens't throw any errors

### 🙂 Expected behavior

I expect that `list[0] = list[0] ?? {};` should throw an error
Repository: pytorch
Issue: DISABLED test_scatter_uneven (__main__.DeviceMeshCollectiveTest)
Labels: oncall: distributed,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_scatter_uneven&suite=DeviceMeshCollectiveTest) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/11840114780).

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 2 failures and 2 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_scatter_uneven`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `distributed/_tensor/test_device_mesh.py` or `distributed/_tensor/test_device_mesh.py`

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu
Repository: terminal
Issue: Allow users to set the font size the way it worked in conhost
Labels: Issue-Feature,Product-Conhost,Area-Rendering

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

Currently, the font size options are slightly lower in granularity than Command Prompt or Powershell. You cannot match their default font size of 16. I understand moving away from using actual pixel measurements for the general user since CMD predates UI scaling and this system presumably is more consistent for that. However for the power user, the option to specify the exact pixel height is nice.

I propose that if the user enters a "px" suffix to the number in the font size input, it should be either translated to the matching font size or ideally just used directly.

At the very least greater granularity would be appreciated so that the font size can match that which it is supposed to replace. Thank you.
Repository: vscode
Issue: Adopt Markdown to use vscode log output channel
Labels: feature-request,debt,markdown

I see that Markdown extension is creating an output channel for logging. Recently we have introduced a log output channel that has following advantages

- You can log at different levels (trace, debug, info, warn, error)
- Respects the log level defined at the product level
- User can control the logging level from VS Code UI 
  - For the complete product
  - For only your log
  - Across restarts
- Will make your logs consistent with VS Code logging
- It will also allow you to remove some formatting code

It would be great if you can adopt to the new log output channel. If there are any gaps for adopting, please let me know.
Repository: PowerToys
Issue: PowerRename: Be able to rename using metadata
Labels: Idea-Enhancement,Product-PowerRename,Needs-Triage

### Description of the new feature / enhancement

When importing files from a camera and using $YYYY-$MM-$DD_$hh-$mm you get the date from when the file was "created" (imported). Would be nice to have the option and use date from metadata so you can use the actual date from the picture/video was taken.

### Scenario when this would be used?

I often record video with my camera and let the files stay on the SD card and import them to my computer once a week/month. After import I would like to change the filename using the metadata in the file. 

### Supporting information

The camera I use names the files as C0001, C0002 etc. The problem is that the camera start from the beginning once I've exported (removed) the files from the SD card. So without renaming the files there will be a filename collision when importing the next time.
Repository: vscode
Issue: Markdown: Don't highlight unmatched brackets
Labels: bug,editor-bracket-matching

I have a similar issue using math equations in markdown, the image on the left is version 1.76 and the one on the right is 1.75.1, both of them with the same settings (by sharing them). The fix suggested by @ithinkandicode did not resolve my problem. Should I open a new issue since it is a different language and context?


![parthesis issue](https://user-images.githubusercontent.com/60045376/222485804-455979aa-6f8f-4756-ac3b-ab1dd9727b9e.png)

_Originally posted by @darg2012 in https://github.com/microsoft/vscode/issues/175797#issuecomment-1452137547_
Repository: rust
Issue: #[derive(Clone, Copy)] doesn't work
Labels: A-diagnostics,A-macros,T-compiler,A-suggestion-diagnostics,D-newcomer-roadblock

I tried this code:

```rust
use std::marker::PhantomData;

#[derive(Clone, Copy)]
pub struct TypedAddress<T>{
    inner: u64,
    phantom: PhantomData<T>,
}

pub trait Memory {
    fn write_value<T>(&self, offset: TypedAddress<T>, value: &T);
    fn return_value<T>(&self, offset: TypedAddress<T>) -> T;
    fn update_value<T, F>(&self, offset: TypedAddress<T>, update: F)
        where F: FnOnce(T) -> T
    {
        let old = self.return_value(offset);
        let new = update(old);
        self.write_value(offset, &new);
    }
}
```

I expected to see it compiled.

Instead, this happened:
```
error[E0382]: use of moved value: `offset`
  --> src/test.rs:17:26
   |
12 |     fn update_value<T, F>(&self, offset: TypedAddress<T>, update: F)
   |                                  ------ move occurs because `offset` has type `test::TypedAddress<T>`, which does not implement the `Copy` trait
...
15 |         let old = self.return_value(offset);
   |                                     ------ value moved here
16 |         let new = update(old);
17 |         self.write_value(offset, &new);
   |                          ^^^^^^ value used here after move
   |
help: consider further restricting type parameter `T`
   |
13 |         where F: FnOnce(T) -> T, T: Copy
   |                                +++++++++

error[E0382]: use of moved value: `offset`
  --> src/ic.rs:53:26
   |
49 |     fn update_value<T, F>(&self, offset: TypedAddress<T>, update: F)
   |                                  ------ move occurs because `offset` has type `ic::TypedAddress<T>`, which does not implement the `Copy` trait
...
52 |         let old = self.return_value(offset);
   |                                     ------ value moved here
53 |         self.write_value(offset, &update(old));
   |                          ^^^^^^ value used here after move
   |
help: consider further restricting type parameter `T`
   |
50 |         where F: FnOnce(T) -> T, T: Copy
   |                                +++++++++

For more information about this error, try `rustc --explain E0382`.
```

### Meta

`rustc --version --verbose`:
```
rustc 1.67.1 (d5a82bbd2 2023-02-07)
binary: rustc
commit-hash: d5a82bbd26e1ad8b7401f6a718a9c57c96905483
commit-date: 2023-02-07
host: x86_64-unknown-linux-gnu
release: 1.67.1
LLVM version: 15.0.6
```

```
$ rustc --version --verbose
rustc 1.69.0-nightly (9aa5c24b7 2023-02-17)
binary: rustc
commit-hash: 9aa5c24b7d763fb98d998819571128ff2eb8a3ca
commit-date: 2023-02-17
host: x86_64-unknown-linux-gnu
release: 1.69.0-nightly
LLVM version: 15.0.7
```
Repository: excalidraw
Issue: Support create link for a group of elements
Labels: enhancement,discussion

Neither 'Create link' on context menu nor 'Link' on properties panel is shown for a group of elements. Is this feature not supported? For my use case, it is more reasonable to create link at group level.
Repository: pytorch
Issue: Better error message when trying to run fp16 weights on CPU
Labels: good first issue,module: error checking,triaged

### 🚀 The feature, motivation and pitch

Hey :wave: from the Hugging Face Open-Source team,

We're seeing the following issue over and over again across libraries
```
RuntimeError: "LayerNormKernelImpl" not implemented for 'Half'
```

or:

```
RuntimeError: "addmm_impl_cpu_" not implemented for 'Half'
```

E.g.: https://github.com/runwayml/stable-diffusion/issues/23

The problem here is that a PyTorch model has been converted to fp16 and the user tried to run it on CPU, e.g. the following:

```py
from torch import nn
import torch

linear = nn.Linear(2,2, dtype=torch.float16)

tensor = torch.ones((2,), dtype=torch.float16)

linear(tensor)
```

yields:

```
"addmm_impl_cpu_" not implemented for 'Half'
```

Could we maybe catch such errors in the forward of https://pytorch.org/docs/stable/_modules/torch/nn/modules/module.html#Module

and return a simpler error message that just says "Float16 cannot be run on CPU"?

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet
Repository: PowerToys
Issue: Hide mouse pointer while typing
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

This feature has been around since Windows 95 (maybe even in 3.1 - didn't use that). But it has never EVER worked! Legend says it should work in Office. Never seen it work though. In Excel the mouse pointer still hides the cell I just clicked on. 

Click > Type > What did I just type? > Move mouse > Ahh!

It would be awesome if it, after at least 27 years, finally could work :P

### Scenario when this would be used?

When clicking and entering data into any small field. User names, passwords, adresses, Github feauture suggestions etc.

### Supporting information

It might be tricky as the feauture would need to both know that an input field is active, and detect typing. Could be annoying if it read a keyboard command as typing for example.
Repository: PowerToys
Issue: Incorrect links upper case versus lower case
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

There are numerous links that have uppercase characters in the reference that should be lowercase like in keyboardeventhandlers.md line 5 where:
```
  1. [HandleSingleKeyRemapEvent](#HandleSingleKeyRemapEvent)
```
should be:
```
  1. [HandleSingleKeyRemapEvent](#handlesinglekeyremapevent)
```

similar problems are in different places in the files keyboardeventhandlers.md , keyboardmanager.md and keyboardmanagercommon.md
Repository: PowerToys
Issue: Fancy Zones not recalling correct window positions after (dual) monitors powered off
Labels: Issue-Bug,Product-FancyZones,Priority-1

### Microsoft PowerToys version

0.68.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Not recalling correct window positions after (dual) monitors powered off. 

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

Windows shift to secondary monitor. 

### Other Software

_No response_
Repository: PowerToys
Issue: Add options to paste clipboard content in different formats
Labels: Idea-Enhancement,Product-Advanced Paste

I would like to have more options to paste the clipboard content as plain text, such as:

- Paste in uppercase, lowercase, or title case
- Paste without letters, numbers, punctuation marks, or spaces
- Remove spaces and upper case the first letter of all words (camel case): myAge, mainViewController, defaultUserParameters
- It could be useful to get alternatives such as: PascalCase, snake_case, kebab-case: https://www.codingem.com/what-is-camel-case/
- bonus points if you can add regular expressions transformations

### Scenario when this would be used?

**Steps to reproduce:**
1. Copy some text from any source
2. Press a keyboard shortcut to open the “Paste as plain text” menu
3. Select one of the options to paste the clipboard content in a different format

**Expected behavior:**
The clipboard content is pasted as plain text in the selected format.

**Actual behavior:**
Currently, there is only one option to paste as plain text without any formatting.

### Supporting information

_No response_
Repository: vscode
Issue: Configuring transient state in notebook serializer is not working
Labels: bug,notebook-serialization

<!-- ⚠️⚠️ 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

using the vscode notebook api we configured notebooks to handle output and some metadqata as transient so we don't get marked as dirty state. In dib format output is not preserved so is not relevant to mark a notebook as modified after running a cell.

this is setup code in teh extension 
```js
        const notebookoptions: vscode.NotebookDocumentContentOptions = notebookType === contracts.DocumentSerializationType.Dib
            ? { transientOutputs: true, transientDocumentMetadata: { custom: true }, transientCellMetadata: { custom: true } }
            : {};

        const notebookSerializer = vscode.workspace.registerNotebookSerializer(notebookType, serializer, notebookoptions);
```

<!-- 🪓 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.77 insiders
- OS Version: Win11

Steps to Reproduce:

1.  use latest Polyglot Notebook extension
2.  create a notebook using dib format
3. write and execute some code
4.  save
5. run cell again
6. the document is marked as dirty
Repository: godot
Issue: Godot 4.0 Issues with long raycasts and TileMap
Labels: bug,regression,topic:2d

### Godot version

Godot 4.0.stable.official

### System information

Windows 11, Vulkan, GTX 980 Ti (528.02)

### Issue description

`Raycasts` do not detect `TileMap` collisions at all when their length is set to a large value (e.g ten million). It also seems to have issues if the `TileMap` is removed then added back into the scene. This causes a `CharacterBody2D` with even a slightly shorter raycast value (e.g ten thousand) to bug out when next to a wall. It also causes it to be grounded when jumping. Probably because the ray is hitting the top of each tile on the wall?

`TileMap`

![raycast2d_tilemap_bugs1](https://user-images.githubusercontent.com/14341036/223716006-5873c390-49f0-4803-b155-e2fda0b2881b.gif)

Giving the raycast a small length or insetting it in about 0.1 fixes this issue, however, using raycasts to get the ground is a common thing, if it doesn't lineup closely with edges of the `CharacterBody2D`'s `CollisionShape2D` you might get some odd behavior where the corner of the collider hits the ground but the raycast does not. Also these bugs do not happen with static bodies.

`StaticBody`

![raycast2d_tilemap_bugs2](https://user-images.githubusercontent.com/14341036/223716026-502bacac-ce0a-471b-9479-a9b2002b9b4a.gif)

**Also none these issues happen in 3.x.**

### Steps to reproduce

_See sample project._

### Minimal reproduction project

[RayCast2DTileMapBugs.zip](https://github.com/godotengine/godot/files/10920752/RayCast2DTileMapBugs.zip)
Repository: react
Issue: [DevTools Bug] Cannot add node "621" because a node with that id is already in the Store.
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://github.com/iprinceroyy/crwn-clothing

### Repro steps

Bug report:
1. Clone & run in the local environment.
2. Sign in.
3. Head over to the shop.
4. Add some items to cart.
5. Click on the cart icon.

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

4.27.2-1a88fbb67

### Error message (automated)

Cannot add node "621" because a node with that id is already in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:27863:41
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25892:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26061:14
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56323:39)
```


### Error component stack (automated)

_No response_

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot add node  because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```