sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Supply label names in tuple types using type-level strings
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

Labelled tuples

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

It's already possible to manually specify labels when defining a tuple type:

```ts
type MyTuple = [foo: number, bar: string];
```

I propose that there be some syntax to allow these labels to be supplied explicitly in mapped types, eg.

```ts
type Labels = ["foo", "bar"]
type Values = [number, string]
type MyTuple = {
    // Hypothetical syntax
    [I in keyof Values]: Values[I] as Labels[I]
}
```

To be clear: there is still no way to "access" labels of tuples under this proposal. It's purely a way to add extra documentation into existing type definitions.

If the provided name can be determined to be a literal string type, then the value of that literal string is used as the tuple element name. In all other cases, the element is unnamed as before.


### 📃 Motivating Example

There are many cases where the developer can supply useful names, such as if the tuple is somehow derived from an object type, or similar.

My particular case involves taking a user-supplied array like the following:

```ts
const path = ["examples", param("exampleId"), "line", param<number>("lineNumber")] as const;
```

And I use this constant to generate a type for paths, which in this case would look like:
```ts
type Path = TypeMagic<typeof path>;
// type Path = ["examples", string, "line", number]
```

It would be nicer if I could generate this type instead:
```ts
type Path = TypeMagic<typeof path>;
// type Path = ["examples", exampleId: string, "line", lineNumber: number]
```

### 💻 Use Cases

This came up while integrating TanStack Query into an application.

Since this is purely a documentation improvement, the workaround for the moment is to simply do without labels.
Repository: flutter
Issue:  flutter run --watch option
Labels: c: new feature,tool,c: proposal,P3,team-tool,triaged-tool

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Not everyone uses official editors to develop flutter apps, or may use scripts or other configurations that can't access the watch functionality of the IDE.

build_runner, which is maintained by the dart/flutter team offers --watch as an option too, but for machine-generated code.

### Proposal

implement a ` flutter run --watch` option as mentioned in #6199.
Repository: kubernetes
Issue: APF should handle Deletecollection verb
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

APF doesn't do much for Deletecollection verb, even though it's more expensive than list (list + delete one by one)
https://github.com/kubernetes/kubernetes/blob/2b4ef19578f6bec7f4a76c82b7afcac2c228648d/staging/src/k8s.io/apiserver/pkg/util/flowcontrol/request/width.go#L112-L126

### What did you expect to happen?

Deletecollection should take similar amount of seats as list so that there are not too many deletecollection calls get processed at the same time.

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

Deleting a namespace will trigger namespace controller to garbage collected resources in that namespace using deletecollection verb. If the number objects are large enough. There can be performance issues when there are too many deletecollection calls.

### Anything else we need to know?

_No response_

### Kubernetes version

All versions with APF feature.

### Cloud provider

OSS

### OS version

_No response_

### Install tools

<details>

</details>


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

<details>

</details>


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

<details>

</details>
Repository: flutter
Issue: flutter/flutter CI should automatically detect all dart packages under //dev and run their tests
Labels: a: tests,team-infra,P2,triaged-infra

Today, tests under //dev are run as part of the framework misc shard, specified by this code: https://github.com/flutter/flutter/blob/3f722c1442fa07e6afc2442853bc2a7813a3ba8c/dev/bots/test.dart#L982.

This requires hard coding the path to each dart package and then invoking `flutter test` or `dart test` on them. However, it is easy to overlook this (for example, currently tests under //dev/tools do not get run). Instead, test.dart should automatically detect every pubspec.yaml under //dev and run flutter test on it.
Repository: kubernetes
Issue: APF: Add a separate flowSchema (and priorityLevelConfiguration) for SubjectAccessReview
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

Add a separate flowSchema (and priorityLevelConfiguration (PLC)) for SubjectAccessReview and other that related to authorization.
Option 1: add a new default `flowSchema` and corresponding PLC
Option 2: add a new default `flowSchema` that maps to a PLC like workload-high


### Why is this needed?

We have seen a common use case that user uses HPA controller that talks to a metrics server (an extension apiserver). 
HPA (part of kube-controller-manager) is in `kube-system` namespace and uses `workload-high` PLC.
Metrics server (e.g. prometheus adaptor) is commonly not in `kube-system` namespace and uses `workload-low` PLC.

The related workflow is linked here:
https://kubernetes.io/docs/tasks/extend-kubernetes/configure-aggregation-layer/#authentication-flow

HPA can have 500s when there is APF throttling in `workload-low` PLC that causes metrics server's `SubjectAccessReview` to be dropped (step 7 in the flow).
This issue is very non-trivial for users to understand and troubleshoot. In order to make users have a better experience and also hide some unnecessary complexity from users. I want to propose to adding additional default APF config as mentioned above. 

![authentication-flow](https://d33wubrfki0l68.cloudfront.net/3c5428678a95c3715894011d8dd4812d2cf229b9/e745c/images/docs/aggregation-api-auth-flow.png)
Repository: pytorch
Issue: Regression on CUDA 12.1 for vanilla transformer layer
Labels: needs reproduction,module: performance,module: cuda,triaged

### 🐛 Describe the bug

Hi, we are benchmarking [deep vit](https://github.com/lucidrains/vit-pytorch/blob/main/vit_pytorch/deepvit.py) models and found out the CUDA 12.1 binary are actually slower than CUDA 11.8 for PyTorch 2.1.0 release. This is not expected as we see better perf on other LLMs like Megatron(GPT) and OPT. One potential reason is those repos are using flash-attention or xformers which benefit from CUDA 12 and transformer engine on H100 GPUs. While deep VIT is using vanilla implementation: https://github.com/lucidrains/vit-pytorch/blob/main/vit_pytorch/deepvit.py. But we are not expecting a regression. Any ideas? thanks!

here is the output showing ~10% regression on single node
PT 2.1.0 + CUDA 11.8
```
[1,0]<stdout>:time taken for the last 1 steps is 2.420312336000279, the throughput is 13.221434078579314 images/stime taken for forward pass is 0.261821381000118time taken for backward pass is 1.758593597000072
[1,0]<stdout>:Average elapsed time is 2.3975933989263996, throughput is 13.34671675953439peak allocated memory is 25.845419008Average forward time is 0.24408430756846333Average backward time is 1.75420702246313
```

PT 2.1.0 + CUDA 12.1

```
[1,0]<stdout>:time taken for the last 1 steps is 2.7207883900000525, the throughput is 11.76129687910032 images/stime taken for forward pass is 0.26708757999995214time taken for backward pass is 1.9990846610003246
[1,0]<stdout>:Average elapsed time is 2.72146025645262, throughput is 11.75839328321167peak allocated memory is 25.845419008Average forward time is 0.26492700765261123Average backward time is 2.001053710136823

```

attached training script and reproduciable steps

```
pip install vit-pytorch
pip install packaging
torchrun --nnodes=1 --nproc_per_node=8 train.py
```



### Versions

PyTorch 2.1.0
cuda 11.8 vs cuda 12.1
tested on AWS P5.48xlarge

cc @ezyang @gchanan @zou3519 @kadeng @ptrblck
Repository: godot
Issue: OpenGL: Clearcoat has no effect if BaseMaterial3D roughness is exactly 0
Labels: bug,topic:rendering,topic:3d

- *Related to https://github.com/godotengine/godot/issues/95207.*

### Godot version

4.2.beta1

### System information

Fedora 38, GeForce RTX 4090 (NVIDIA 535.104.05)

### Issue description

When using the Compatibility rendering method, Clearcoat has no effect if BaseMaterial3D roughness is exactly 0:

![Screenshot_20231013_012642 webp](https://github.com/godotengine/godot/assets/180032/606d21d1-e43a-4faa-897c-454c25e80138)


However, it works if roughness is set to 0.01 or 1.0:

Roughness 0.01 | Roughness 1.0
-|-
![Screenshot_20231013_012628 webp](https://github.com/godotengine/godot/assets/180032/d10fd77e-3a6b-472c-a7dd-f53415d555bf) | ![Screenshot_20231013_012638 webp](https://github.com/godotengine/godot/assets/180032/8505f671-fd4e-4baa-ab9a-c15cb0aae973)

This issue only occurs in Compatibility, not Forward+ or Mobile. I noticed it while working on a solution for https://github.com/godotengine/godot/issues/69327.

### Steps to reproduce

- Add a MeshInstance3D and DirectionalLight3D (so that clearcoat can be seen).
- Assign a BaseMaterial3D to the MeshInstance3D, with Roughness set to exactly `0.0` and enable Clearcoat.

### Minimal reproduction project

[Clearcoat_Test_2.zip](https://github.com/godotengine/godot/files/12887825/Clearcoat_Test_2.zip)
Repository: godot
Issue:  Instancing Staticbody3D within a thread which contains a CollisionShape3d causes an error
Labels: bug,topic:core

### Godot version

v4.1.2.stable.official [399c9dc39]

### System information

Godot v4.1.2.stable - Linux Mint 21.2 (Victoria) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 Ti (nvidia; 535.86.05) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

Instancing a Staticbody3D that contains a CollisionShape3D results in an error that says 
 ```
E 0:00:00:0659   get_transform: This function in this node (CollisionShape3D) can only be accessed from either the main thread or a thread group. Use call_deferred() instead.
  <C++ Error>    Condition "!is_readable_from_caller_thread()" is true. Returning: (Transform3D())
  <C++ Source>   scene/3d/node_3d.cpp:314 @ get_transform()
```

Deleting the child CollisionShape3D from StaticBody3D fixes the offending issue.

### Steps to reproduce

1. Create a Staticbody3D that contains a Collisionshape3D
2. Create a function that instances said Staticbody3D
3. Run said to function in a new thread


### Minimal reproduction project

[bug.zip](https://github.com/godotengine/godot/files/12887964/bug.zip)
Repository: neovim
Issue: terminal is cleared after exiting (mintty, works in Windows Terminal)
Labels: bug,platform:windows,environment,tui

### Problem

After running and exiting nvim, my terminal window is "cleared." This means that the lines of the terminal above where I ran nvim are cleared and the terminal prompt shows up on the line after that (unlike running `clear` itself). When I run other commands or programs like vim, I can see the previous commands I ran in the terminal window still there after I exit:
![vim](https://github.com/neovim/neovim/assets/22417446/c3ce6baa-7ef0-4497-b44b-0b2f3a94e331)
With nvim, before running:
![nvim-before](https://github.com/neovim/neovim/assets/22417446/952cb984-c7f1-485d-934f-fa2af0b893c3)
![nvim-before1](https://github.com/neovim/neovim/assets/22417446/c0cacdcd-c61a-4f1e-9c52-fa2b2179caed)
After running:
![nvim-after](https://github.com/neovim/neovim/assets/22417446/77c31613-c7ac-4e8c-acc4-fca3ceb0f450)
![nvim-after1](https://github.com/neovim/neovim/assets/22417446/e4c31793-e56a-489f-9dba-5d433d311aaf)

I tried running and exiting nvim in cmd.exe and Windows Terminal and they work fine. I also tried the nightly release on mintty and the problem persists.

### Steps to reproduce

```
nvim
:q
```

### Expected behavior

The previous terminal history should not be cleared.

### Neovim version (nvim -v)

v0.9.4

### Vim (not Nvim) behaves the same?

no, 9.0.1976

### Operating system/version

Windows 10

### Terminal name/version

mintty 3.6.5

### $TERM environment variable

xterm-256color

### Installation

pacman -S mingw-w64-ucrt-x86_64-neovim
Repository: PowerToys
Issue: FancyZones: App Window Invisible/Missing Due to Opening on a Non-Active Monitor
Labels: Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

I have 2 monitors active, with both having a single zone. 
I open NotePad++ and place it on my secondary monitor. 
I close NotePad++.
I Disable my secondary monitor using windows Display settings.
I reopen NotePad++, and it is off of my primary screen. It is positioned "virtually" outside the left of my primary screen - where the secondary monitor was. 
I am able to right-click on the tab in the taskbar, select Move, and use the arrow key to bring it into position to grab and place on the primary monitor. 

The same happens if I shut down my computer and open it with the secondary monitor not connected to the computer.


### Scenario when this would be used?

I DO have the "Move newly created windows to their last known zone" SELECTED. Thus it is appropriate for the NotePad++ window to be placed there. 

HOWEVER, given that the application is completely invisible, I feel it would be beneficial to provide a sub-Option to the above Option to allow the user to decide if they wish for that setting to NOT apply if the last-known-zone is currently NOT available. 

Further, to avoid potential user confusion with the invisible app, I believe that this new sub-Option should be ON by default if the user Enables the "Move newly created windows to their last known zone" option.

### Supporting information

![PowerToys FancyZones New Windows Sub Option MOD](https://github.com/microsoft/PowerToys/assets/2779491/462b61f4-3fca-4f73-8b76-d3e1462e97de)
Repository: rust
Issue: Non-Send values that are assigned to a variable but not used across an await point incorrectly mark the entire Future as non-Send
Labels: T-compiler,C-feature-request,A-async-await,AsyncAwait-Triaged,WG-async

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=f9f172724348c228b481bcd813cc92e5

```rust
use std::sync::Mutex;

fn main() {
    assert_send(foo(&Mutex::new(SomeStruct)));
}

struct SomeStruct;

impl SomeStruct {
    fn some_method(&self) -> u32 {
        return 1;
    }
}

async fn foo(mutex: &Mutex<SomeStruct>) {
    let guard = mutex.lock().unwrap();
    guard.some_method();
    std::mem::drop(guard);
    bar().await;
}

async fn bar() {
}

fn assert_send<T: Send>(_t:T) {}
```

It fails to compile since the future is not Send.

Since the guard is explicitly dropped before the await point, I would expect this future to be Send.  Indeed, if I remove the variable `guard` and condense those three lines onto a single line, like so:

```rust
async fn foo(mutex: &Mutex<SomeStruct>) {
    mutex.lock().unwrap().some_method();
    bar().await;
}
```

...it compiles and runs fine.  [I created a second Playground to confirm this](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=a48f7c7724f5ff64fce04d55599be36c) that does some additional testing to make sure the future runs correctly.

I suspect, therefore, that this is a bug.  I've confirmed it's present in the most recent stable, nightly, and beta releases of the compiler available from rustup.

Of note is that the bug occurs even if I remove the call to `some_method()`.  Merely assigning the guard to a variable is sufficient to make the future non-`Send`.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustup run stable rustc --version --verbose`:
```
rustc 1.73.0 (cc66ad468 2023-10-03)
binary: rustc
commit-hash: cc66ad468955717ab92600c770da8c1601a4ff33
commit-date: 2023-10-03
host: x86_64-unknown-linux-gnu
release: 1.73.0
LLVM version: 17.0.2
```

`rustup run nightly rustc --version --vernose`:
```
rustc 1.75.0-nightly (475c71da0 2023-10-11)
binary: rustc
commit-hash: 475c71da0710fd1d40c046f9cee04b733b5b2b51
commit-date: 2023-10-11
host: x86_64-unknown-linux-gnu
release: 1.75.0-nightly
LLVM version: 17.0.2
```

`rustup run beta rustc --version --verbose`:
```
rustc 1.74.0-beta.1 (b5c050feb 2023-10-03)
binary: rustc
commit-hash: b5c050febf10c9bcc0459d41fe2a1e190ad30b8d
commit-date: 2023-10-03
host: x86_64-unknown-linux-gnu
release: 1.74.0-beta.1
LLVM version: 17.0.2
```
Repository: rust
Issue: Rust compiler hangs when using macro_rules! to generate code with complex type parameters
Labels: A-macros,T-compiler,C-bug,I-hang

<!--
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.
-->
### Code

`cat hang.rs`

```rust
trait Trait {
    type Assoc;
}
impl Trait for () {
    type Assoc = ();
}
macro_rules! m {
    ([$($t:tt)*] [$($open:tt)*] [$($close:tt)*]) => {
        m!{[$($t)*][$($open)*$($open)*][$($close)*$($close)*]}
    };
    ([] [$($open:tt)*] [$($close:tt)*]) => {
        fn _f() -> $($open)*()$($close)* {}
    };
}
m! {[###########][impl Trait<Assoc =][>]}
```
### Command
`rustc  -C opt-level=0 hang.rs`

I expected to see this happen: *The compiler compiles successfully or outputs an error message.*

Instead, this happened: *The code, as provided below, appears to encounter a hang*

The same problem is reproduced on the nightly version(1.75.0-nightly (https://github.com/rust-lang/rust/commit/d627cf07ce46d230a93732a4714d16f00df9466b 2023-10-10)) as well.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.73.0 (cc66ad468 2023-10-03)
binary: rustc
commit-hash: cc66ad468955717ab92600c770da8c1601a4ff33
commit-date: 2023-10-03
host: x86_64-unknown-linux-gnu
release: 1.73.0
LLVM version: 17.0.2
```
There is not any error information or stack information when using `export RUST_BACKTRACE=1`
<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
<backtrace>
```


</p>
</details>
what's more, to get more information,I also tried '-Z time-passes' (using nighly version):

```sh
time:   0.000; rss:   30MB ->   32MB (   +2MB)  parse_crate
```
Repository: flutter
Issue: ResizeImage width should be of type double, not type int because you usually resize based on constraints in double
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

ResizeImage width should be of type double, not type int because you usually resize based on constraints in double
```
      return LayoutBuilder(builder: (context, constraints) {
        return Image(
            image: ResizeImage(
          FileImage(File(pathRefImage)),
          width:
              (constraints.maxWidth * MediaQuery.of(context).devicePixelRatio)
                  .toInt(),
        ));
```

### Proposal

ResizeImage width should be of type double, not type int because you usually resize based on constraints in double
Repository: PowerToys
Issue: [Image Resizer] Option for Padded resize
Labels: Idea-Enhancement,Product-Image Resizer,Needs-Triage

### Description of the new feature / enhancement

_This can be thought of as a reframe of the proposal #3403 that has gone silent and that might make sense with a change of nomenclature._

The proposal would add an option to **Image Resizer** called `Fit with Padding`. 

This option would resize up or down each image selected similar to the normal `Fit` concept, such that none of its content is cropped and that its appropriate dimension is flush with the specified size, and additional add padding where necessary to the alternative dimension such that each image is filled out to match this specified size.

One can imagine a version of this option that colors this added padding black or an option that allows specification of the padding color.

### Scenario when this would be used?

This would be most relevant to situations where one has a variety of aspect ratios of images and wants to guarantee the resulting images that come out are:
* exactly of the specified size
* contain all of the contents from the original image
* present all of the contents from the original image front and center

Currently when choosing to `Fit` resize a batch of images and specifying a target image size there is no guarantee that the resulting set of images are actually going to be of that image size. 

### Supporting information

That the images come out in all different sizes doesn't feel immediately obvious. If we want to build Image Resizer to be a tool for all, someone who doesn't know the nuance of what `Fit` means might expect to have the tool give them images at the size they specified.

It also doesn't feel like a user centric experience, more a technical engineering based decision. One criticism often leveled at Windows is that features don't always feel created based on natural usage, this feels like an intuitive option.

Happy to work on this PR if the feature request is approved! <3
Repository: godot
Issue: Menu items overlap scrollbar
Labels: bug,topic:editor,usability

### Godot version

4.2 beta 1

### System information

Windows 10, Radeon RX 560 Series

### Issue description

When you select an item in the menu, it is superimposed on top of the scrollbar, it doesn’t look right.
![0](https://github.com/godotengine/godot/assets/130399274/de5de93f-68ec-46f4-9dfe-8e8e3ba31e82)


### Steps to reproduce

Open settings editors or project settings

### Minimal reproduction project

Anyone can do this, regardless of the project.