sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: [Bug] Empty ending bracket in `"surroundingPairs"` results in bad selection range
Labels: bug,editor-autoclosing

add a bracket pair to `"surroundingPairs"` under `language-configuration.json`, with the end bracket being empty/blank
```json
"surroundingPairs": [
    [ "(", "" ]
]
```
Make a selection around some text and press `(`
![image](https://github.com/microsoft/vscode/assets/33529441/1f7ef380-a7ec-47b6-aa56-3378ff524b85)

Expected: ✅
resulting selection is still around `text`
![image](https://github.com/microsoft/vscode/assets/33529441/536a8113-169d-4138-857d-df63807e19ac)

Actual: ❌
resulting selection ends up being moved 1 to the left
![image](https://github.com/microsoft/vscode/assets/33529441/b322ebad-cab0-41b8-bafb-f968afc94f7c)


This could have been used as a workaround for https://github.com/microsoft/vscode/issues/202386
Repository: vscode
Issue: File nesting for enumeration of files with same basename
Labels: under-discussion,file-nesting

<!-- ⚠️⚠️ 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 am working with Paraview, and the output of some code gives me a big enumeration of files, like this :

```
solution_00000000
    ├── solution_00000000_0.pvu
    ├── solution_00000000_1.pvu
    ├── solution_00000000_2.pvu
    ...
    └── solution_00000000.pvtu
```

I have thousands of files inside this folder, and it's a visual clutter. I would like to have a way to configure the file nesting to group those files together :

```
solution_00000000
├── solution_00000000.pvtu
└── solution_00000000.pvu
    ├── solution_00000000_0.pvu
    ├── solution_00000000_1.pvu
    ├── solution_00000000_2.pvu
    ...
```
Repository: rust
Issue: Shadow call stack should be supported on `aarch64-unknown-none`
Labels: T-compiler,A-sanitizers,C-bug,O-AArch64

Passing the `-Zsanitizer=shadow-call-stack` flag to rustc when compiling for the `aarch64-unknown-none` target results in the following error:
```
error: shadow-call-stack sanitizer is not supported for this target
```
However, as long as the x18 register is reserved during codegen (see #121970), there shouldn't be any problem with enabling the shadow call stack sanitizer on `aarch64-unknown-none`. It is already supported on several other aarch64 targets (see #121966).

The Linux Kernel uses the `aarch64-unknown-none` target when compiling Rust code for aarch64. This flag is needed so that we can enable `CONFIG_SHADOW_CALL_STACK` when using Rust in the kernel.

For more information on this sanitizer, please see [the relevant chapter in the unstable book](https://doc.rust-lang.org/beta/unstable-book/compiler-flags/sanitizer.html#shadowcallstack).

Related to [this thread on LKML](https://lore.kernel.org/rust-for-linux/20240304-shadow-call-stack-v1-1-f055eaf40a2c@google.com/).

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: Material Alternative for CupertinoTimerPicker (DurationPicker)
Labels: c: new feature,framework,f: material design,f: date/time picker,would be a good package,c: proposal,P3,team-design,triaged-design

### Use case

If want to pick a Duration (minutes, seconds, etc.) and there currently is no option in material design.
For cupertino there is [CupertinoTimerPicker](https://api.flutter.dev/flutter/cupertino/CupertinoTimerPicker-class.html).
[TimePickerDialog](https://api.flutter.dev/flutter/material/TimePickerDialog-class.html) doesn't fit, as it results in TimeOfDay only, and isn't customizable for seconds, milliseconds, etc.

### Proposal

It could work just like a time picker, but without 'am', 'pm' and with duration instead:
https://m3.material.io/components/time-pickers/overview

See also time duration picker here: https://experience.sap.com/fiori-design-android/pickers/
Repository: PowerToys
Issue: Rename window in the taskbar
Labels: Idea-New PowerToy

### Description of the new feature / enhancement


![image](https://github.com/microsoft/PowerToys/assets/60144847/7f3e84c5-e689-4150-b189-15ff718e723b)

Like this situation, it is hard to find the terminal I want.
I want to rename the name of window in taskbar.

### Scenario when this would be used?

When using multiple similar windows simultaneously

### Supporting information

_No response_
Repository: node
Issue: fs.readdir recursive: is `parentPath` supposed to be the same as `path`?
Labels: question,doc,fs

### Affected URL(s)

_No response_

### Description of the problem

I'm curious what the purpose of `parentPath` is on Dirent objects when using `fs.readdir` or `fs.readdirSync` when both `withFileTypes` and `recursive` are set to true. 

The reason for this issue is that I haven't found a situation where `parentPath` differs from `path`, it's always the same value. My hunch is that it's not supposed to be and there is probably a bug. 

FWIW, I think it would be more useful to include the `relative` path versus `parentPath`, since `parentPath` is just the `path.dirname(path)` of each path, isn't it? If not, perhaps `parentPath` isn't the best name? Maybe it should be `base` or `root` or something?
Repository: svelte
Issue: Docs: The concept of "component initialisation" is mentioned several times in the docs without ever being explained.
Labels: documentation

### Describe the problem

The concept of "component initialisation" is mentioned several times in the docs, but it is never explained what it is.

Mentioned several times on this page:
https://github.com/sveltejs/svelte/blob/main/documentation/docs/03-runtime/01-svelte.md

And one time here:
https://svelte.dev/docs/svelte-components#script-4-prefix-stores-with-$-to-access-their-values

I've been thinking over this and haven't come up with a clean one sentence explanation or else I would have jumped right to a PR. Opening this bug report because this concept deserves a little introduction in the docs before being used repeatedly.

Li Hau Tan has a long explanation of youtube: https://www.youtube.com/watch?v=PI54YD4GsCc

### Describe the proposed solution

Add a short concise explanation of what component initialisation is to the docs.

### Importance

would make my life easier
Repository: godot
Issue: Vibration not working on 'Nanco PS4 Revolution Pro Controller'
Labels: bug,topic:input

### Tested versions

- Reproducible in Godot Engine v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3080 Laptop GPU (NVIDIA; 31.0.15.2824) - AMD Ryzen 9 5900HX with Radeon Graphics (16 Threads)

### Issue description

I am experiencing an issue with the Input.start_joy_vibration function in Godot Engine, specifically when attempting to utilize vibration features during gameplay. This problem arises exclusively when using the Nacon PS4 Revolution Pro Controller. Despite correctly implementing the vibration code, no feedback is observed with this particular controller.

However, when switching to a PS4 DualShock controller paired with an 8bitdo USB adapter, the vibration functionality operates flawlessly, indicating that the issue is not with the code itself but rather with compatibility between the Godot Engine and the Nacon controller.

Further investigation into this matter revealed that the Nacon PS4 Revolution Pro Controller functions as expected in other Steam games, providing proper vibration feedback. This observation leads me to believe that the root cause is a specific compatibility issue between the Godot Engine and the Nacon controller.

I have also conducted a thorough search on Google and reviewed the existing issues on this repository but found no mention of similar problems with the Nacon PS4 Revolution Pro Controller, though there are reports for other controllers. This absence of reports suggests that the issue might not be widely recognized or reported yet.

I am reaching out to the community for insights or solutions regarding this compatibility issue. Any assistance or guidance on resolving this problem would be greatly appreciated.

### Steps to reproduce

```gdscript
extends  Node2D

func _process(delta):
	Input.start_joy_vibration(0, 1, 1, 1)
```


### Minimal reproduction project (MRP)

```gdscript
extends  Node2D

func _process(delta):
	Input.start_joy_vibration(0, 1, 1, 1)
```
Repository: pytorch
Issue: Add flags for device that does not support fused or foreach ops
Labels: module: cpp-extensions,triaged,module: mta

### 🚀 The feature, motivation and pitch

My team is working on adding a custom backend for pytorch and would like to add flags for devices that do not support fused or foreach ops.
I noticed that currently, all privateuseone devices are assumed to support fused and foreach ops by default (https://github.com/pytorch/pytorch/blob/main/torch/utils/_foreach_utils.py). However, not all of the devices support those ops. What should developers of custom backends do if their backends do not support fused and foreach ops?

### Alternatives

_No response_

### Additional context

_No response_

cc @malfet @zou3519 @crcrpar @mcarilli @janeyx99
Repository: PowerToys
Issue: Maximize window when placing it in a zone that covers the entire screen
Labels: Idea-Enhancement,FancyZones-Layouts,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

When moving a window into a FancyZones zone that covers the entire screen, the application should be maximized (potentially with an option to enable/disable this behavior).

### Scenario when this would be used?

Most windows have special styling for when they're full-screen - removal of round corners, no access to resize handles, etc. When using FancyZones to move a window into a position that covers the entire screen, this isn't applied, even if the zones have 0 gap. This causes what could be considered bugs, where the mouse can catch a resize handle on a "maximized" application.

### Supporting information

https://github.com/microsoft/PowerToys/assets/4542461/f31e5cbf-f2ab-4414-87d1-3a0e4f2c5000

This is **not** a duplicate of #279. That issue is about keeping maximized applications contained to their zones. This issue is about maximizing applications when moving them to zones that cover the entire screen.

This **is** a duplicate of #3258, but that issue is (erroneously) closed.
Repository: deno
Issue: `deno compile` cross compilation does not work Linux -> Windows
Labels: bug,compile

### Discussed in https://github.com/denoland/deno/discussions/22685

<div type='discussions-op-text'>

<sup>Originally posted by **mabasic** March  4, 2024</sup>
I'm not opening an issue yet, because I'm typing this on mobile ... here it goes.

I'm using Deno 1.41.1 and when I run deno compile on Linux with target Windows, the command generates a .exe file without issues. But when I copy that file to my windows machine and run it I get a error deno panic something something.

I have tried running it with rust_backtrace="full" but I can't find anything useful in the output. Just a bunch of gibberish.

Things that I have tried:
- deno compile on linux without target (to linux binary) and it works on linux
- deno compile on linux with windows target and it does not work on windows (panics)
- **BUT** when I clone the repo to my windows machine and run `deno compile` from there, it generates a .exe file and the executable works as expected.

This signals to me that the issue is somewhere in the cross compilation, and not in the compilation in general.

I have even reduced the bug in my source code to a specific NPM package: https://github.com/sindresorhus/ink-big-text

When I comment out the import for this package and any related code from my application, the cross compilation works.

Hopefuly, someone will find this info useful. I have tried reading the source code for cli/tools/compile.rs but I can't seem to find anything interesting there, also I'm not a rust programmer yet so maybe that is the issue too 😊

I will try to create a reproduction repository and open a issue in the following week.</div>
Repository: angular
Issue: Ability to disable "NG3: The containing function or module body is too large for control flow analysis. [plugin angular-compiler]" rule
Labels: area: compiler

### Which @angular/* package(s) are relevant/related to the feature request?

common, compiler-cli, compiler

### Description

Recently our team upgraded Angular version from 16 to 17. But we couldn't start the project because of "NG3: The containing function or module body is too large for control flow analysis. [plugin angular-compiler]" error. Not all components have this problem.

### Proposed solution

Ability to disable the "NG3: The containing function or module body is too large for control flow analysis. [plugin angular-compiler]"

### Alternatives considered

We considered refactoring our code but it is simply too time consuming.
Repository: vscode
Issue: [json] include copies of the `package.json`, `jsconfig.json`, `eslint.json` schemas
Labels: feature-request,json

<!-- ⚠️⚠️ 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. -->
For various JSON files VSCode uses SchemaStore to get information on what is allowed or not in these files. For example: package.json, tsconfig.json and eslint.json.
For these files VSCode grabs them from the schemastore website [schemastore.org](https://www.schemastore.org/json/)

However, in modern days websites could be offline which is what happened today as well (and I believe it happened more recently as well) as this issue shows: https://github.com/SchemaStore/schemastore/issues/3620

It would be nice if VSCode could cache these results (it would also save the website some bandwidth) and only update when things have changed, perhaps when nodejs packages have been updated or just weekly/montly instead of what it is now. The main issue right now is that it doesn't have a fallback and currently shows errors on every json file you open

<img width="800" alt="image" src="https://github.com/microsoft/vscode/assets/1716267/6d022be3-4f98-402f-961e-8d986ac1ce3c">



<img width="800" alt="image" src="https://github.com/microsoft/vscode/assets/1716267/2a0cce94-a0c2-4c9c-9d99-72b1a16075dc">

<br/>

<img width="500" alt="image" src="https://github.com/microsoft/vscode/assets/1716267/29946385-e513-4bb9-a782-55d5a411f5e1">
Repository: godot
Issue: Buttons consume all button events regardless of button mask
Labels: discussion,topic:input,topic:gui

### Tested versions

4.2.1 mono

### System information

Godot v4.2.1.stable.mono (b09f793f5) - Arch Linux #1 ZEN SMP PREEMPT_DYNAMIC Sat, 24 Feb 2024 04:03:29 +0000 - X11 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1050 Ti (nvidia; 550.54.14) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

When the cursor is over a button and any mouse button is pressed, that event becomes consumed by the button and not passed to the parent, e.g. an item in a list has a delete button, which should only activate with the left button, right clicking anywhere on the item should open a popup menu with options but right clicking with the cursor on the delete button consumes the input. The mouse filter for the delete button may not be set to pass because it would activate both the delete button and the list item.

### Steps to reproduce

* Create a node, which handles right click inputs
* Add a button as a child of it with button mask set to mouse left
* Run the scene and try to right click the parent control with the cursor over the button

### Minimal reproduction project (MRP)

This project shows the example described in the project description.
[buttonmask.zip](https://github.com/godotengine/godot/files/14482239/buttonmask.zip)
Repository: tauri
Issue: [bug] can't create non focused window on MacOS
Labels: type: bug,platform: macOS,status: needs triage

### Describe the bug

I use latest tauri from `dev`
And I try to create non focused (minimized) window on `MacOS`
in `tauri.conf.json` -> `windows[0]` I set  `focus` to `false` but when the app opens in MacOS the window is focused instead of being in background / minimized.
The same happens as well with dynamic created windows with `focused(false)`.





### Reproduction

```json
    "windows": [
      {
        "fullscreen": false,
        "height": 600,
        "resizable": true,
        "title": "app",
        "width": 800,
        "label": "main",
        "focus": false // still focused and not minimized on launch
      }
    ]
```
or
```rust
WebviewWindowBuilder::new(&app, "second", tauri::WebviewUrl::External(Url::from_str("https://github.com".into()).unwrap())).focused(false).build().unwrap(); // still focused and not minimized on execute
```

### Expected behavior

Newly created window should be non focused (minimized?) 

### Full `tauri info` output

```text
app npx tauri info
WARNING: no lock files found, defaulting to npm

[✔] Environment
    - OS: Mac OS 14.2.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 18.19.0
    - npm: 10.2.3

[-] Packages
    - tauri [RUST]: 2.0.0-beta.8
    - tauri-build [RUST]: 2.0.0-beta.6
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.1
    - tauri-cli [RUST]: 1.5.9
    - @tauri-apps/api : not installed!
    - @tauri-apps/cli [NPM]: 2.0.0-beta.1

[-] App
    - build-type: bundle
    - CSP: unset
```


### Stack trace

_No response_

### Additional context

Looks like an issue in tao, it happens there as well.
Repository: angular
Issue: Failed to implement CSP Policy's for styles with CSP_NONCE token 
Labels: area: core,area: security,core: stylesheets,cross-cutting: CSP

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

When implementing the CSP policy for styles, we decided to go with the CSP_NONCE token because we are caching index.html.
In order to implement this token we decided to use APP_INITIALIZER to receive a nonce token from the server before the application is loaded and use it afterwards.
For this, we wrote a simple nonce service that is responsible for getting and saving the token
![image](https://github.com/angular/angular/assets/156127155/fc463e8f-0bf0-493d-bea0-ac01a1157920)
After that we added this configuration to app.module.ts :
``` 
export function receiveNonce(nonceService: NonceService) {
  return () => {
    console.log('APP_INITIALIZER useFactory function start working');
    return nonceService.receiveNonce();
  }
}


Providers: [
NonceService,
      {
        provide: APP_INITIALIZER,
        useFactory: receiveNonce,
        deps: [NonceService, HttpClient],
        multi: true
      },
      {
        provide: CSP_NONCE,
        useFactory: (nonceService: NonceService) => {
          console.log('CSP_NONCE useFactory function start working');
          return nonceService.getNonce();
        },
        deps: [NonceService, HttpClient],
        multi: true
      }
]
```

![image](https://github.com/angular/angular/assets/156127155/5034fab0-b735-4294-920e-c17d25fe7ff1)
Example of execution order.

And as a result we get incorrect behavior our СSP_NONCE is executed before APP_INITIALIZER for some reason. Because of this we can not get nonce token from the server, also useFactory does not work with asynchronous operations not anywhere except APP_INITIALIZER that's why we decided to use it.
Expected Behavior:  CSP_NONCE token should work fine with factory approach 


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Node version - 18.16.0
Angular version - 16.2.12
```


### Anything else?

_No response_
Repository: vscode
Issue: Double-clicking on `...` used as argument value selects more than `...`
Labels: bug,confirmed,python

I'm reading through the [FastAPI tutorial](https://fastapi.tiangolo.com/tutorial/query-params-str-validations/#required-with-ellipsis) and they allow you to pass `...` to `Query.default` to indicate that there is no default value and the parameter is in fact required.

## Code Snippet

```python
from fastapi import Query
from pydantic import BaseModel, Field

async def read_items(q: int = Query(default=...)): # Selects everything from = to :
    pass

class Model(BaseModel):
    c: int = Field(...) # Selects everything from ( to )
```

## Repro Steps

1. Double click on the `...` on line 4 (`default=...`).

## Expected behavior

Only `...` is selected so that you could then replace the `...` with something else.

## Actual behavior

`=...)):` is selected.

Similarly, if you double-click on the `...` on line 8 (`Field(...)`), `(...)` is selected.
Repository: PowerToys
Issue: Run plugins to provide Immediate Results
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

I use PowerToys Run for switching between open windows and it is amazing. What would be even more amazing is if PTRun displayed a list of all the open windows when i first launch it, or whenever the search box is empty. That would let me quickly scan what is open, so i know what to search for. It should be a toggleable option to autopopulate results without input from user. 

### Scenario when this would be used?

If it is not possible to list all the open windows automagically on start then second best would be some keyword to list all of them. For example * (asterisk) or desktop or desktop 1 (to filter those on desktop 1 only). 

### Supporting information

Should probably respect the Number of results shown setting:
![image](https://github.com/microsoft/PowerToys/assets/1708294/f79fb745-b433-4af2-8abf-c9dd6e3c6cd6)
Sort order is important, perhaps based on last accessed if that information is available.
Repository: angular
Issue: Animation in not active material mat-tab makes animated element get stuck in the DOM
Labels: area: animations

### Which @angular/* package(s) are the source of the bug?

animations

### Is this a regression?

No

### Description

If triggering an animation for a component that is currently in an inactive `mat-tab`, that animation sticks to the DOM and is not removed as it should.

See the attached stackblitz.

1. Click on the tab "Second" and wait 2 seconds.
2. Click on the tab "First".

The result is that the div with `item0` that was animated got stuck for the `TestComponent` that was inside of the first `mat-tab`.

Test example start
![image](https://github.com/angular/angular/assets/7062803/f15e5c11-db2f-4d92-a711-ae33020e3010)

and end, where the animated div gets stuck in one of the `TestComponent`
![image](https://github.com/angular/angular/assets/7062803/a0e20f88-babf-4d85-a127-623f95f7d1f0)


Might be related to:
#53492

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/23y3d9

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

_No response_

### Anything else?

_No response_