sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Select active zone with keyboard
Labels: Idea-Enhancement,Product-FancyZones

### Description of the new feature / enhancement

`override windows snap` allows for easily moving windows which are already in focus to a different zone and it works great. But I'm not aware of a way to select a zone with the keyboard. Maybe `win + alt + arrow` could could move the active zone selection in the direction pressed?

### Scenario when this would be used?

Any time you want to select a zone to move the top window or cycle the stack.

### Supporting information

Almost any other tiling window manager has a keyboard shortcut for selecting the active zone.
Repository: godot
Issue: Vulkan: Vertex colors glitch on 3D model due to automatic mesh LOD
Labels: bug,topic:rendering,confirmed,documentation,topic:import,topic:3d

### Godot version

v4.0.alpha.custom_build [2aee84c75]

### System information

Windows 11

### Issue description

https://user-images.githubusercontent.com/4235617/152444746-6d3e3279-3056-4ccc-a528-b92741715a07.mp4

Using vertex painting on a model. If I zoom/de-zoom on my model, there is a glitch as you can see above. 
It is working well in 3.4.2.

(Is it a LOD issue?)

### Steps to reproduce

- create a 3d mesh model, then add paint vertex. (or use the one attatched)
- import the model in **godot** (master). The previewer is working well.
- import the model in a **scene**, then zoom and dezoom on the model.

Files:
[cube vertex paint .blend + gltf.zip](https://github.com/godotengine/godot/files/7998926/cube.vertex.paint.blend.%2B.gltf.zip)
 

### Minimal reproduction project

[vertex painting 3.4.2.zip](https://github.com/godotengine/godot/files/7998904/vertex.painting.3.4.2.zip)
[vertex painting 4.0.zip](https://github.com/godotengine/godot/files/7998905/vertex.painting.4.0.zip)
Repository: terminal
Issue: Add icons to new SUI expanders
Labels: Help Wanted,Product-Terminal,Issue-Task,Area-SettingsUI

# Description of the new feature/enhancement

The new Settings UI in terminal utilizes expanders to group settings controls, which matches up with the other inbox apps shipped in Windows 11. Something that I believe should be added (both for the sake of consistency and visual hierarchy) is expander icons. 

At the moment, most inbox apps add an icon prefixed before each settings group that conveys it's semantic meaning. This both looks nice and makes it easier to quickly differentiate between groups.

Current:
![image](https://user-images.githubusercontent.com/42101043/152447297-5bdd470a-a065-45f3-9d46-0a6d76ae3a9e.png)

Notepad:
![image](https://user-images.githubusercontent.com/42101043/152447340-b0c83645-8b00-4b58-8f96-e00fb55944dd.png)

Clock:
![image](https://user-images.githubusercontent.com/42101043/152447409-a9edb029-7b92-470e-8424-518a00f18c50.png)

It's worth noting that not *every* app does this. For example, Snipping Tool has no icons in it's expanders, although I do still believe this could be an improvement.
Repository: react
Issue: autoFocus polyfill deviates from HTML autofocus global attribute spec
Labels: Type: Needs Investigation

Based on this comment: https://github.com/facebook/react/issues/11851#issuecomment-351672131, it appears `autoFocus` is meant to bring a consistent behavior to match HTML's `autofocus`.

https://html.spec.whatwg.org/multipage/interaction.html#the-autofocus-attribute

The above spec outlines that the first element with `autofocus` found in the DOM should be the one focused, and the others discarded ("flush autofocus candidates" steps 5.11.1 through 5.11.3).

However, the behavior of React's `autoFocus` polyfill is to set focus to the _last_ element in the DOM with the attribute.

Ideally React's implementation should match the spec, behavior-wise.
Repository: vscode
Issue: [Request] [Notebooks] Allow arbitrary values in a cell's language selector.
Labels: languages-basic,under-discussion,notebook

.NET Interactive notebooks allows different cell languages via the language selector in the bottom right of the cell.  Currently the only allowable values are languages that have been pre-registered with VS Code via the `"contributes"."languages"` field of the manifest.

A common scenario we're seeing is the user creating multiple connections to different SQL databases, e.g., `AdventureWorks` and `Northwind`.  Currently we handle this awkwardly by pre-registering a language `dotnet-interactive.sql` with an alias of "SQL (.NET Interactive)", but that doesn't actually let the user execute a query against a specific database connection.  They have to put a magic command at the top of the cell that we use to route the request.

For example, one cell might have the language set to "SQL (.NET Interactive)", but the contents of the cell look like this:

```
#!sql-AdventureWorks
SELECT * FROM ...
```

and the next cell also has it's language set as "SQL (.NET Interactive)", but its contents are:

```
#!sql-Northwind
SELECT * FROM ...
```

It would be much more instructive to the user if they could simply select from the dropdown "C# (.NET Interactive)", "F# (.NET Interactive)", "AdventureWorks", "Northwind", etc., where the last two items we dynamically added at runtime.
Repository: PowerToys
Issue: [FZ Editor] ability to reorder layouts
Labels: FancyZones-Editor,Product-FancyZones,Area-User Interface

### Description of the new feature / enhancement

Being able to change the order in which the fancyzones custom layouts are displayed would be great.

I have a few work-scopes and this means have a few fancyzone layout profiles for my stupidly wide screen. I have set shortcuts for `ctrl win alt #` which is great.

Being able to drag and drop could also auto-set the shortcut.

Ah man, I'm loving fancyzones!

### Scenario when this would be used?

In the case of someone with a great deal of layouts, being able to set the order would be quite useful for a visual-check.

### Supporting information

![image](https://user-images.githubusercontent.com/4994379/152448445-3c1f9b38-e667-4328-90c3-783e8d8e2e97.png)
Repository: PowerToys
Issue: [FancyZones] Auto-Place New Windows in the default zone.
Labels: Idea-Enhancement,Product-FancyZones

### Description of the new feature / enhancement

I have a question rather than a suggestion:

Right now I have the option to place a window manually between to zones (I'm using a layout of 2 columns of equal height), making it cover them both as kind of another "virtual" zone that is made of the two zones and the space beween them - when I start positioning it in zones and hold it over the space between them, both zones are selected.

Is it possible to set up the automatic window placement of new windows in that "virtual zone"?



### Scenario when this would be used?

When wanting to have a layout of columns, and a window that spans two columns (or ideally more) without needing to manually create overlapping zones by dragging them and resizing them - this way the zones are pixel-perfect in size and ratio.

### Supporting information

_No response_
Repository: material-ui
Issue: [Select] Render Select component value holder as real native select
Labels: new feature,component: select

### Duplicates

- [x] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Currently, the `<Select>` component uses an `<input>` as a value holder for all its value, for both simple and multiple/Chip list. Although the `native` property can be used currently, it does not match the expected MUI design.

The new system should keep the current design and having a hidden native `<select>` at the same time. A new attribute should be added to indicate that we want to use a select as value holder.

Another idea is to improve the current `native` property so it stills keep the design of MUI while still rendering a native select.

### Examples 🌈

```
<Select
    select
>
..
</Select>
```

### Motivation 🔦

With the current system, things get more even more complicated when we render a multiple select or a chip select and. When the whole FormData is submitted to the server, the input send a comma seperated ID `1,2,3,4` instead of a real array. Therefore rendering a real select match better the expectation of the developper.
Repository: material-ui
Issue: [Tabs] validateDOMNesting warning when Typography component is a child of TabPanel
Labels: component: tabs

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

The contents of a TabPanel component are wrapped in a typography component. When a Typography (or other) component is a child of a TabPanel, this causes a validateDOMNesting warning.


### Expected behavior 🤔

The TabPanel should be able to contain other components, other than just plain text, without causing a validateDOMNesting warning.

### Steps to reproduce 🕹

Steps:

1. Create TabPanel
2. Add a `<div>` or `<p>` element as a child of the TabPanel

Here is a codesandbox with the Tabs demo code, but with one of the TabPanels containing a Typography component.
[Codesandbox](https://codesandbox.io/s/cocky-roman-5i3l2)

### Context 🔦

This issue happened when trying to create UI that contains a Typography component inside of a TabPanel.

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  npmPackages:
    @emotion/react: latest => 11.7.1
    @emotion/styled: latest => 11.6.0
    @mui/material: latest => 5.4.0
    react: latest => 17.0.2
    react-dom: latest => 17.0.2
```
</details>
Repository: deno
Issue: Usage of `Deno.flockSync()` causes hangs in certain scenarios
Labels: bug,needs investigation,runtime

This might be a problem with the sqlite library, but the entire deno process hangs, so I guess there is some problem with the platform (or maybe even V8). This happens on Windows. I tested it on Mac, and it works fine.

I used 🦖 Deno ~1.18.1~ 1.18.2

If I use the following code in a worker, it causes the worker to hang. If I then call `terminate` on the worker, the entire deno process hangs:

```
// worker.ts
import { DB } from "https://deno.land/x/sqlite@v3.2.0/mod.ts";

console.log('Open a database');
const db = new DB("test.db");
db.query(`
  CREATE TABLE IF NOT EXISTS people (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    name TEXT
  )
`);
console.log('Close connection');
db.close();
console.log('completed');
```
```
// main.ts
const worker = new Worker(new URL("./worker.js", import.meta.url).href, { type: "module", deno: {namespace: true}});

setInterval(async()=> {
    console.log('heartbeat');
}, 1000);

setTimeout(async()=> {
    console.log('terminating the working');
    worker.terminate();
}, 10000);
```

To run this, first bundle the worker, then execute `main.ts`.

```
deno bundle worker.ts worker.js
deno run -A --unstable main.ts
```

This example starts a worker that tries to create a database using an SQLite library. It also prints a hearbeat every second. After 10 seconds, it `terminates` the worker. At this time, no more heartbeats are printed from the `main` program. You can also see that the worker process doesn't continue once it tries to create the DB,
Repository: PowerToys
Issue: Font Picker
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

In the same way that PowerToys offers a Color Picker, I would love a Font Picker. 

### Scenario when this would be used?

While browsing the web, or reading PDF/epub or similar documents with text, I might wonder "I like this font, I wonder what it is called.". 

### Supporting information

_No response_
Repository: pytorch
Issue: Feature request: a mode to disallow calling prototype or beta features
Labels: module: bc-breaking,triaged,topic: bc breaking,module: python frontend

PyTorch classifies features/components/modules into one of three stability categories: prototype, beta and stable. See https://pytorch.org/blog/pytorch-feature-classification-changes/ for details. While stable features are subject to our BC-breaking policy, prototype and beta features are not. Programs may accidentally rely on unstable features, however, even when they don't want to update frequently. Providing a mode that prevents reliance on unstable prototype and beta features would help enforce our recommended practice.

cc @ezyang @gchanan @albanD
Repository: go
Issue: x/pkgsite: "added in version" does not account for new packages
Labels: NeedsInvestigation,FeatureRequest,pkgsite

The "added in vX" notes on the rendered API pages are super useful, and they work for both the Go project itself, as well as any module with releases, e.g:

* https://pkg.go.dev/testing#T.Deadline - `added in go1.15`
* https://pkg.go.dev/github.com/ipld/go-ipld-prime/node/bindnode#ProduceGoTypes - `added in v0.14.0`

However, there's no such "added in" information when a package started existing at a specific version. Two examples:

* https://pkg.go.dev/embed appeared in go1.16
* https://pkg.go.dev/github.com/ipld/go-ipld-prime/node/bindnode appeared in v0.10.0

I think that information should be surfaced, because otherwise a user could easily fall into the trap that is assuming that, for example, https://pkg.go.dev/github.com/ipld/go-ipld-prime/node/bindnode#Prototype is safe to use on any version - since it has no "added in" information attached.

One solution would be to add "added in" information to the top of the package view, to inform at what version the package was added. This could be something as simple as "the first stable release the package was seen in this module", becauses I imagine and hope that adding a package, removing it, and adding it again should be extremely rare. I also imagine that the logic should be consistent with whatever algorithm the current API-based "added in" notes are computed with.

Another solution could be to add "added in" to all the APIs that were added with the package in the first place. This will be more visually consistent with what we've got now, and perhaps less prone to footguns, as a link to https://pkg.go.dev/github.com/ipld/go-ipld-prime/node/bindnode#Prototype will quickly give me that important information without me having to scroll all the way up and notice it.

I think the best solution is to do both; adding the information to each API is consistent and very clear, and adding it at the top is also relevant, because a package could have 0 exported API or have its own effect even if we don't use any of its API, via `init` functions.

cc @golang/pkgsite
Repository: terminal
Issue: Change + icon when hovering it with Alt held, like VS Code
Labels: Help Wanted,Area-UserInterface,Product-Terminal,Issue-Task,Priority-3

Watch this gif carefully. When the + is hovered with alt held, it changes to a split pane icon:

![image](https://code.visualstudio.com/assets/updates/1_57/tabs-split.gif)

(from https://code.visualstudio.com/updates/v1_57#_terminal-tabs)

We shouldn't change that button every time alt is pressed, just when it's hovered with alt IMO
Repository: vscode
Issue: Consider reducing requirements for results provided by extensions
Labels: extension-host,under-discussion

notice how the return type is now: `ProviderResult<data<T[] | CompletionList<T>>>`
```ts
export type data<T> = T extends Function
	? never
	: T extends object // recurse
	? { [k in keyof T]: data<T[k]>; }
	: T;

export interface CompletionItemProvider<T extends CompletionItem = CompletionItem> {
	//...
	provideCompletionItems(document: TextDocument, position: Position, token: CancellationToken, context: CompletionContext): ProviderResult<data<T[] | CompletionList<T>>>;
	//...
}
```

this would allow an extension to use the following (and not need to allocate a real range using `new vscode.Range`):

```ts
provideCompletionItems(/*...*/) {
	return [{
		label: 'hello',
		range: {
			start: { line: 10, character: 0 },
			end: { line: 10, character: 1}
		}
	}];
}
```
Repository: pytorch
Issue: Ability to assign to `tensor.require_grad` might lead to bugs
Labels: module: error checking,triaged,module: ux

### 🚀 The feature, motivation and pitch

Let PyTorch complain/warn that the user assigns something to `tensor.require_grad` instead of `tensor.requires_grad`.

For instance, when a user tries to load a pretrained model and freeze its parameter PyTorch will not complain:
```python
import torchvision
net = torchvision.models.vgg16(pretrained=True)
for params in net.parameters():
    params.require_grad = False
```

Some potential bugs can be found by googling for `"*.require_grad = False" at:github.com`.

### Alternatives

_No response_

### Additional context

_No response_
Repository: puppeteer
Issue: [Bug]: PDF Output: Text using OTF fonts is converted into vector graphics, blowing up file size.
Labels: bug,upstream,confirmed,P3

### Bug description

While exporting to PDF, text that uses OTF fonts is converted to vector graphics, which massively increases the file size.
Converting fonts to TTF instead prevents vectorization, the text is left as text and PDF file size becomes reasonable.

### Puppeteer version

13.1.3

### Node.js version

12.18.2

### npm version

7.0.0-beta.9

### What operating system are you seeing the problem on?

macOS

### Relevant log output

_No response_
Repository: kubernetes
Issue: Kube-apiserver exposes metrics with status code 0 for streaming requests
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

I was looking at the metrics exposed by the kube-apiserver and noticed that some of the `apiserver_request_total` metrics had a 
status code set to 0 in Kubernetes 1.23. Looking a bit more into the metrics, I noticed that it was affecting the `/healthz` and `/readyz` endpoints as well the streaming requests with the verbs `GET` and `POST`.

![2022-02-04-145959_2488x1049_scrot](https://user-images.githubusercontent.com/22327577/152542523-37a043a2-bd11-444e-a982-995279e7b5fa.png)

@benluddy pointed out this PR https://github.com/kubernetes/kubernetes/pull/107034 to me which should solve the problem for the health endpoint in 1.24, but the issue for the streaming requests doesn't seem to have been solved yet.

### What did you expect to happen?

I expected the status code reported in the metrics to be a valid HTTP status code.

### How can we reproduce it (as minimally and precisely as possible)?

1. Run kubectl port-forward
2. Check the `apiserver_request_total` metric that was generated based on the previous call. It will have `resource="pods"`, `subresource="portforward"` and `code="0"`.

### Anything else we need to know?

I also checked the audit logs and the requests that are logged have a valid status code:

![2022-02-04-145903_2425x562_scrot](https://user-images.githubusercontent.com/22327577/152543349-99811050-8de4-4d70-9898-ff78be03056f.png)


### Kubernetes version

<details>

```console
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"archive", BuildDate:"2021-11-18T21:20:32Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.3+b63be7f", GitCommit:"6f5a5295923a614a4202a7ad274b38b69f9ca8c0", GitTreeState:"clean", BuildDate:"2022-01-28T11:12:03Z", GoVersion:"go1.17.2", Compiler:"gc", Platform:"linux/amd64"}
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: terminal
Issue: The new 'Run as Administrator' feature returns a 'cannot find WindowsTerminal.exe' error
Labels: Issue-Bug,Product-Terminal,Needs-Tag-Fix,Priority-1

### Windows Terminal version

1.13.10336.0

### Windows build number

10.0.19044.1466

### Other Software

_No response_

### Steps to reproduce

Holding down Ctrl when clicking the + button to open a new window as admin opens the UAC prompt for elevation but after entering credentials, it returns an error saying WindowsTerminal.exe cannot be found.

### Expected Behavior

_No response_

### Actual Behavior

Windows cannot find 'C;\Program Files\WindowsApps\Microsoft.Windows.TerminalPreview_1.13.10336...\WindowsTerminal.exe'. Make sure you typed the name correctly, and then try again.
Repository: flutter
Issue: flutter test --reporter json includes Android embedding v1 deprecation warning
Labels: a: tests,platform-android,tool,has reproducible steps,P2,found in release: 2.10,found in release: 2.11,team-android,triaged-android

## Steps to Reproduce

1. Setup Android project with flutter <= 1.12
2. Update to flutter 2.10.0
3. run `flutter test --reporter json > test-results.json`

**Expected results:**

Test report contains only valid json representing the test results

OR When running either one

* `flutter --ignore-deprecation test --reporter json > test-results.json`
* `flutter test --ignore-deprecation --reporter json > test-results.json`

Test report contains only valid json representing the test results

**Actual results:** <!-- what did you see? -->

Test results are preceded by this warning

```
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Warning
──────────────────────────────────────────────────────────────────────────────
Your Flutter application is created using an older version of the Android
embedding. It is being deprecated in favor of Android embedding v2. Follow the
steps at

https://flutter.dev/go/android-project-migration

to migrate your project. You may also pass the --ignore-deprecation flag to
ignore this check and continue with the deprecated v1 embedding. However,
the v1 Android embedding will be removed in future versions of Flutter.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
The detected reason was:

  <path to project>/android/app/src/main/AndroidManifest.xml uses `android:name="io.flutter.app.FutterApplication"`
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
```

When running either of 

* `flutter --ignore-deprecation test --reporter json > test-results.json`
* `flutter test --ignore-deprecation --reporter json > test-results.json`

```
Could not find an option named "ignore-deprecation".

Run 'flutter -h' (or 'flutter <command> -h') for available flutter commands and options.
```

Might be related to: Flutter Test should support multiple reporters #69425

## Workaround

If you encounter this problem as well, here's my workaround

`flutter test --reporter json | grep '^{' > test-results.json`

This works because flutter's json reporter stores the test results as a valid json object per line and each json object must start with a `{`, and no line of the warning starts with `{ `