sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: Run wasm directly
Labels: cli,suggestion

Bun can do the following, but Deno cannot. Is there a reason Deno execution of WASM must route through JS?

```
# cat hello.c
#include <stdio.h>
int main() {
        printf("HELLO WASM\n");
        return 0;
}
# emcc hello.c -o hello.wasm
# bun run hello.wasm
HELLO WASM
```
Repository: vscode
Issue: Launching External Terminal Changes Ctrl+C Handling Of Programs
Labels: bug,terminal-external

Type: <b>Bug</b>

Steps to reproduce:
1. Launch VSCode (anywhere)
2. Start new external terminal using Ctrl+Shift+C. I used Command Prompt in this case.
3. Launch new program that can handle Ctrl+C
4. Press Ctrl+C.

Expected result: Program handles Ctrl+C normally.
Actual result: Program doesn't sees Ctrl+C at all.

A simple program that can handle Ctrl+C for this example is Python. However any app that handles Ctrl+C is affected (such as [my simple WASAPI loopback program](https://github.com/MikuAuahDark/simple-wasapi-loopback/blob/master/program.cxx#L142)). Run this Python script within same terminal that VSCode creates at step 2.
```py
try:
    while True:
        pass
except KeyboardInterrupt:
    print("OK")
```

If Ctrl+C is pressed while that script is running:
* If the terminal/command prompt was launched by VSCode, pressing Ctrl+C does nothing.
* If the terminal/command prompt was launched by other means, pressing Ctrl+C prints "OK" and stops the infinite loop.

Reproducible both in insiders and stable (1.87.0).

VS Code version: Code - Insiders 1.88.0-insider (8c2b09c0443b94d75a73819ed35610f7e09375ae, 2024-02-28T18:53:20.095Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 4700U with Radeon Graphics          (8 x 1996)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.39GB (7.43GB free)|
|Process Argv|--crash-reporter-id ca2e3ed8-bdf1-4e2a-b9d7-b651fe0eba6b|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:30784851
c4g48928:30535728
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfcontrol:30963551
d34g3935:30961436
edj9j583:30943796
fegfb526:30952798
7j2b6412:30951517
bg6jg535:30946824
ccp1r3:30958150

```

</details>

<!-- generated by issue reporter -->
Repository: PowerToys
Issue: MouseWithoutBorders - firewall rule added at install even when feature is disabled
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.78

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

General, Mouse Without Borders

### Steps to reproduce

priority: low
may also be related: https://github.com/microsoft/PowerToys/issues/27337

hi,

1. set registry value to disable MouseWithoutBorders
`reg add "HKLM\SOFTWARE\Policies\PowerToys" /v "ConfigureEnabledUtilityMouseWithoutBorders" /t REG_DWORD /d 0 /f``
2. clean install of PowerToysSetup-0.78.0-x64.exe
3. observe a host firewall rule named "PowerToys.MouseWithoutBorders" is created

have tested in a Windows Sandbox to confirm it's part of the install process

### ✔️ Expected Behavior

firewall rule not to be created when application is configured to disable the associated feature

this may be subjective / my own bias, but would also argue (in a friendly way) that FW rules should be an off by default install option or left as a manual admin task

cheers

### ❌ Actual Behavior

host firewall rule named "PowerToys.MouseWithoutBorders" is created

### Other Software

_No response_
Repository: deno
Issue: Deno fast check does not work with triple-slash types import
Labels: bug,jsr

Version: Deno 1.40.5

I'm trying jsr out, but cannot get a @types package to work. Those are defined with a namespace declaration for I had to use triple slash:

```ts
/// <reference types="npm:@types/gapi.calendar@3.0.11" />

export function foo(): gapi.client.calendar.EventInput[] {
}
```

Error:

```console
$ deno publish
...
error: TS2503 [ERROR]: Cannot find namespace 'gapi'.
...
```

Normal `deno check` or `deno run` etc works, just `deno publish` does not work for me.
Repository: go
Issue: proposal: cmd/go: add a method to output test that might be worth running in parallel
Labels: Proposal,GoCommand

### Proposal Details

I am created https://go-review.googlesource.com/c/go/+/564995 and https://go-review.googlesource.com/c/go/+/564576, in this process, discover a way to find test possible worth running in parallel, which can be done automatically with go test .

This method is `go test -v` gets the run time for each of the tests, then excludes tests that have already been run in parallel and tests that have taken a short time, and the rest are tests that might be worth running in parallel.

For example:

get from `go test -v runtime`

```
=== RUN   TestSmhasherTwoNonzero
--- PASS: TestSmhasherTwoNonzero (9.09s)
```

This can determine that TestSmosherTwoNonzero may be worth running in parallel.

However, based on the experience gained in the aforementioned CL, it is more convenient for go test to perform this search.

because there may be many tests, there may be log and skip outputs, and there are clear rules for performing this lookup with `go test`.

Specific proposal content
Add a flag, name undetermined, use maybeparallel as placeholder for now, `go test -maybeparallel`  only provides this semantics, which reports tests that may be worth running in parallel.
One way to achieve this is outputs the name and time of the test that did not run in parallel and took longer than 0.4 seconds.

Worth discussing:
Maybe also should add a flag, set test that is not complete after a certain time, `go test -maybeparallel` only output these test name and test run time.
Repository: vscode
Issue: Side Scrollbar does not match scroll position in document
Labels: bug,diff-editor

Type: <b>Bug</b>

Open a large document (for example a diff view of packagelock.json via source control). No look for some highlight markers in the scrollbar.
These do not match the scrolled position in the document.

See in the screenshot, the diffs should be at the end of the view (according to scrollbar) but they are at the beginning.

Screenshot:
<img width="1295" alt="image" src="https://github.com/microsoft/vscode/assets/364896/15f8f305-08b8-4672-bb7c-ce62c064bf84">

In the next screenshot, the diffs should be in the middle, but they are not even visible:

<img width="1296" alt="image" src="https://github.com/microsoft/vscode/assets/364896/f2971ed5-425f-4a8b-a4dd-ce2d5bec682a">


slider mode:

<img width="359" alt="image" src="https://github.com/microsoft/vscode/assets/364896/8a698381-a7af-41cd-9a4a-cd17c2e3e61c">

but it also happens in mode "fit"


VS Code version: Code - Insiders 1.86.0-insider (Universal) (72cb92fdc5d08101d65d59e4b1c046d397896dd2, 2023-12-12T05:37:56.079Z)
OS version: Darwin arm64 23.1.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M1 Max (10 x 24)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|5, 4, 4|
|Memory (System)|32.00GB (0.06GB free)|
|Process Argv|--crash-reporter-id 42715b90-8f12-4d70-80b0-8d83b5e08ba7|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (13)</summary>

Extension|Author (truncated)|Version
---|---|---
githistory|don|0.6.20
vscode-jest-runner|fir|0.4.72
serenity-dsl-syntaxhighlight|kle|0.3.1
vscode-clangd|llv|0.1.26
git-graph|mhu|1.30.0
csdevkit|ms-|1.4.2
csharp|ms-|2.18.15
vscode-dotnet-runtime|ms-|2.0.1
vscodeintellicode-csharp|ms-|0.1.26
vscode-designer-addon|nod|1.1.9
indent-rainbow|ode|8.3.1
vscode-pets|ton|1.25.1
pretty-ts-errors|Yoa|0.5.3


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593:30376534
py29gd2263:30784851
c4g48928:30535728
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
fegfb526:30945144
bg6jg535:30946824

```

</details>

<!-- generated by issue reporter -->
Repository: next.js
Issue: Server Environment variables accessible from Client
Labels: bug

### Link to the code that reproduces this issue

https://github.com/kratos-respawned/next_env_issue

### To Reproduce

Start the repo I provided in dev mode and it will automatically throw hydration error because of client js trying to replace server env with null.
Same is the case with next start.
![image](https://github.com/vercel/next.js/assets/87561983/b213c2ba-55e3-4dd7-a1df-03a4d420de17)


### Current vs. Expected behavior

Server Vars should be null by default in client side instead of client js replacing it with null

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
Binaries:
  Node: 20.11.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.58 // Latest available version is detected (14.1.1-canary.58).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

_No response_
Repository: PowerToys
Issue: Registry Preview write/save to the registry should NOT be shortcut CTRL+W?
Labels: Idea-Enhancement,Cost-Small,Product-Registry Preview

### Description of the new feature / enhancement

Problem: CTRL+W is a rather standard shortcut for closing a application or window. The risk of unintentionally writing stuff back is a risk here.

Enhancement: Any other shortcut than CTRL+W or make it an option.

### Scenario when this would be used?

Writing back registry information

### Supporting information

_No response_
Repository: PowerToys
Issue: Registry Preview search and highlight
Labels: Idea-Enhancement,Needs-Triage,Product-Registry Preview

### Description of the new feature / enhancement

A search function with the possibility for highlighting.

### Scenario when this would be used?

Always! 😁

### Supporting information

_No response_
Repository: material-ui
Issue: [material-ui] Add readOnly prop to all form input elements
Labels: component: select,component: text field,component: switch,package: material-ui,enhancement

### Summary

Make the `readOnly` attribute available as a first order prop on all input elements like `TextField`, `Switch`, `Select` etc. just like `disabled` is right now.

### Examples

_No response_

### Motivation

Since `react-hook-form` have started to actually follow the HTML spec `disabled` input values are `undefined` on form submit. Instead we are supposed to correctly use the `read-only` attribute, which make sense thinking about it.

Hence it would be preferable if this prop was available directly on every input element in MUI instead of having to dig down into underlying props which is both less easy on the eye and less easy to find in the documentation.

Bonus points for having some kind of default styling indicating that a read-only element is indeed not mutable.

**Search keywords**: readonly prop input
Repository: ollama
Issue: Feature - Support Custom Actions
Labels: feature request,api

Support for custom actions to cal custom API/Code as part of llama response. possibly part of modelfiles via python scripts? chatGPT has similar with integrations with Zapier
Repository: godot
Issue: Inspector edited object selection history not controlled by history options
Labels: enhancement,discussion,topic:editor,usability

### Tested versions

v4.3.dev3.official [36e943b6b]

### System information

w10 64

### Issue description
Initially these buttons work fine as you can see in the video.
The error occurs when you repeatedly and alternately select the only two nodes in the tree.
Now the node select buttons think there are more nodes in the tree and do not lock correctly, you can press the same node select button repeatedly until at some point it locks.


![Captura4](https://github.com/godotengine/godot/assets/19652075/1a98e7f0-bad4-4a2a-bc2a-10ad1943a74e)


Shouldn't the buttons be arrows with up and down directions, so that if you press the button with an up arrow, the top node is selected and vice versa.


https://github.com/godotengine/godot/assets/19652075/2f55fece-b4e6-4be3-a5f0-1032eff13011


### Steps to reproduce

Watch the video

### Minimal reproduction project (MRP)

...
Repository: flutter
Issue: Wrong Arabic translation for `lockUpButtonLabel` 
Labels: framework,f: material design,a: internationalization,has reproducible steps,P2,team-design,triaged-design,found in release: 3.19,found in release: 3.20

### Steps to reproduce

1. Make sure your app/device is in Arabic 
2. Select any text in a textfield 
3. The option shown contains "النظر الى اعلى"

### Expected results

The translation for `Lock Up` into Arabic should be "بحث عام" because the old translation is a lettral translation which doesn't show the meaning  

### Actual results

The option shown contains "النظر الى اعلى"

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

![IMG_7195787ADA9F-1](https://github.com/flutter/flutter/assets/62833114/b5bc962d-9044-4f70-bcfb-6510bda0ad84)

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[Paste your output here]
```

</details>
Repository: neovim
Issue: Treesitter directives should apply to all captures.
Labels: enhancement,treesitter

### Problem

After #24738 is merged, the behavior for all directives bar `#set!` is to only trigger if the capture is 1 node only. I believe there can be improvements here.

As currently, `TSMetadata` is a `{lang, range, ...}` table + `capture_id, TSMetadata` pairs. Each capture of the list of quantified captures may have different metadata (i.e. different range). Because of that, with a `capture_id->metadata` table, we cannot store the relevant information for those captures.


### Expected behavior

I would like to ask for some methods for, i.e., `#offset!` to be applied to all quantified captures. An example would be, again, C injections in Go:

```go
(
  (comment)+ @injection.content 
  .
  (import_declaration
    (import_spec 
      path: (interpreted_string_literal) @_import_c))
  (#eq? @_import_c "\"C\"")
  (#lua-match? @injection.content "^//")
  (#set! injection.language "c")
  (#offset! @injection.content 0 2 0 0)
  (#set! injection.combined))
```

The example source code can be
```go
// #define FOO BAR
// #define FOO BAR
// #define FOO BAR
// #define FOO BAR
// #define FOO BAR
// #define FOO BAR
import "C";
```

Upon opening a go file with go parser + the injection query above, we get the intended error
```
Error in decoration provider treesitter/highlighter.win:                                       
Error executing lua: /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:573: #offset! d
oes not support captures on multiple nodes                                                     
stack traceback:                                                                               
        [C]: in function 'assert'                                                              
        /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:573: in function 'handler'  
        /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:823: in function 'apply_dire
ctives'                                                                                        
        /usr/local/share/nvim/runtime/lua/vim/treesitter/query.lua:966: in function '(for gener
ator)'                                                                                         
        ...l/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:849: in function 'f'       
        ...l/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:192: in function 'tcall'   
        ...l/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:383: in function '_add_inje
ctions'                                                                                        
        ...l/share/nvim/runtime/lua/vim/treesitter/languagetree.lua:446: in function 'parse'   
        ...al/share/nvim/runtime/lua/vim/treesitter/highlighter.lua:350: in function <...al/sha
re/nvim/runtime/lua/vim/treesitter/highlighter.lua:345>
```

I think there can be a way to also handle directives to all captures, but this will require breaking the `TSMetadata` structure completely
Repository: rust
Issue: Compiler complains about failing to infer the closure's argument's type when the issue is that a mutable reference to the closure is expected
Labels: A-diagnostics,T-compiler,D-confusing,D-newcomer-roadblock

### Code

```Rust
fn testing(t: &mut impl Fn(u8)) {
    t(8)
}

fn main() {
    testing(|u| {
        u.min(9);
    })
}
```


### Current output

```
Compiling playground v0.0.1 (/playground)
error[E0282]: type annotations needed
 --> src/main.rs:6:14
  |
6 |     testing(|u| {
  |              ^
7 |         u.min(9);
  |         - type must be known at this point
  |
help: consider giving this closure parameter an explicit type
  |
6 |     testing(|u: /* Type */| {
  |               ++++++++++++

For more information about this error, try `rustc --explain E0282`.
error: could not compile `playground` (bin "playground") due to 1 previous error
```


### Desired output

```
Compiling playground v0.0.1 (/playground)
error[E0308]: mismatched types
 --> src/main.rs:6:13
  |
6 |       testing(|u| {
  |  _____-------_^
  | |     |
  | |     arguments to this function are incorrect
7 | |         u.min(9);
8 | |     })
  | |_____^ expected `&mut _`, found closure
  |
  = note: expected mutable reference `&mut _`
                       found closure `{closure@src/main.rs:6:13: 6:16}`
note: function defined here
 --> src/main.rs:1:4
  |
1 | fn testing(t: &mut impl Fn(&[u8])) {
  |    ^^^^^^^ ----------------------
help: consider mutably borrowing here
  |
6 |     testing(&mut |u| {
  |             ++++

For more information about this error, try `rustc --explain E0308`.
error: could not compile `playground` (bin "playground") due to 1 previous error
```


### Rationale and extra context

The error suggest that a type hint is missing, when in reality the error is that a `testing` expects a mutable reference to the closure.
The type hint wouldn't solve the error, adding `&mut` does.

### Other cases

For some reason using the argument in a `for` loop rather than using one of its method leads to a good error message. The "desiried output" is copied from that case:

```Rust
fn testing(t: &mut impl Fn(&[u8])) {
    t(&[8])
}

fn main() {
    testing(|u| {
        for _ in u {}
    })
}
```


### Rust Version

Tested on the playground:

```
Nightly version: 1.78.0-nightly
2024-02-15 a4472498d7e88041f620
```


### Anything else?

The same issue arises when using `&mut dyn Fn`, `&impl Fn` and `&dyn Fn`, `Box<dyn Fn>`, with the same caveat that not using `u` in a for loop leads to a good suggestion.
Repository: next.js
Issue: Cannot move directories in app directory Windows 10
Labels: Upstream,bug

### Link to the code that reproduces this issue

https://github.com/radaalinmihai/nextjs-issue-windows10

### To Reproduce

1. Start the application using `next dev`
2. Go inside the app directory
3. Try moving directory _lib from inside `app` directory outside of directory `some-page`
4. Notice that you can't, because some node process in the background that is used by `next dev` is blocking the action
![Screenshot 2024-02-17 142528](https://github.com/vercel/next.js/assets/46570907/e1ba5a6f-2209-4ca5-a17d-2a73bd02546f)

### Current vs. Expected behavior

Current result: the action is blocked and cannot be completed, directory is never moved.
Expected result: the action is not blocked and the directory gets moved.

Please note that this apparently only happens on directories which names start with `_`, every other directory seems fine and is not affected by this blockage.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 18.17.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.58 // Latest available version is detected (14.1.1-canary.58).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Operating System (Windows, MacOS, Linux)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

This happened on my machine, locally, when running `next dev`. I've tested this on version `14.1.0` and also on the latest canary(as of today is `14.1.1-canary.58`)