sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Aux window: xterm mouse tracking is broken in aux windows
Labels: bug,windows,terminal-input,workbench-auxwindow

### xterm mouse tracking is broken in aux windows, makes some TUI applications unusable.

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes



<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.85.1
- OS Version: Windows 11 23H2 22631.3078

Steps to Reproduce:

1. Launch a terminal in editor area (`Ctrl-p` - Create New Terminal in Editor Area - `enter`)
2. Connect to a linux `bash` through `wsl` or `ssh`
3. run `echo -e "\e[?1003;1006h"` to enable mouse tracking
4. Move cursor in the terminal. As tracking is enabled, you can see `35;x;yM` sequences for mouse moving and `32;x;yM` sequences for left-dragging. This is expected.
5. Rightclick on the terminal tab - Move into New Window 
6. Move cursor in the aux window terminal. `35;x;yM`'s for mouse moving is still available, but left-dragging gives no message. `0;x;ym`'s for mouse up is also missing

![upload](https://github.com/microsoft/vscode/assets/61686936/82584121-e041-4374-8d1d-a0340e9f6786)
Repository: rust
Issue: AST validation doesn't correctly deal with impls nested within associated functions
Labels: I-ICE,A-associated-items,T-compiler,C-bug,S-bug-has-test

The following programs get wrongfully rejected since my PR #119505 (nightly-2024-01-04):

```rs
pub struct S;

trait Trait {
    fn provided() {
        impl S {
            pub fn perform() {} //~ ERROR visibility qualifiers are not permitted here
        }
    }
}
```

```rs
pub struct S;
struct Expr<const N: u32>;

trait Trait {
    fn required(_: Expr<{
        impl S {
            pub fn perform() {} //~ ERROR visibility qualifiers are not permitted here
        }
        0
    }>);
}
```

---

The following program was incorrectly rejected even before my PR #119505 (nightly-2024-01-04):

```rs
#![feature(const_trait_impl, effects)]

pub struct S;

#[const_trait]
trait Trait {
    fn required();
}

impl const Trait for () {
    fn required() {
        impl S {
            pub fn perform() {} //~ ERROR visibility qualifiers are not permitted here
        }
    }
}
```

---

The following programs lead to an ICE even before my PR (e.g., in nightly-2023-12-31):

```rs
#![feature(const_trait_impl, effects)]

pub struct S;
#[const_trait]
trait Trait {
    fn provided() {
        impl S {
            fn perform<T: ~const Trait>() {} // should've gotten rejected during AST validation
            //~^ ICE no host param id for call in const yet no errors reported
        }
    }
}
```

```rs
#![feature(const_trait_impl, effects)]

pub struct S;
struct Expr<const N: u32>;

#[const_trait]
trait Trait {
    fn required(_: Expr<{
        impl S {
            fn perform<T: ~const Trait>() {} // should've gotten rejected during AST validation
            //~^ ICE no host param id for call in const yet no errors reported
        }
	0
    }>);
}
```

```rs
#![feature(const_trait_impl, effects)]

struct S;
#[const_trait]
trait Trait<const N: u32> {}

const fn f<T: Trait<{
    struct I<U: ~const Trait<0>>(U); // should've gotten rejected during AST validation
    //~^ ICE no host param id for call in const yet no errors reported
    0
}>>() {}
```

---

There are many more issues and probably many more ways to reproduce this, e.g. we don't visit attributes on associated functions under certain circumstances (I couldn't find a reproducer yet in which you can observe the bug).
Repository: next.js
Issue: [correct a typo] building when parallel route use, if you use generaterMetadata use together, occurs error
Labels: bug

### Link to the code that reproduces this issue

https://github.com/SeungYn/nextjs-bug-parallel

### To Reproduce

I didn't check the English spelling properly because I was in a hurry to make an example. I'm sorry.

error content
Type error: Type '{ params: { id: number; }; }' does not satisfy the constraint 'LayoutProps'.
  Property 'route1' is missing in type '{ params: { id: number; }; }' but required in type 'LayoutProps'.

   Linting and checking validity of types  ...% 

main code
```
import { ReactNode } from 'react';

export function generateMetadata({
  params: { id },
}: {
  params: { id: number };
}) {
  return { title: 'test' };
}

export default function Layout({
  children,
  route1,
  params: { id },
}: {
  children: React.ReactNode;
  route1: ReactNode;
  params: { id: number };
}) {
  return (
    <div>
      {/* {children}
      {route1} */}
    </div>
  );
}



```

route structure
```
├── src
   └── app
       ├── favicon.ico
       ├── globals.css
       ├── layout.tsx
       ├── page.tsx
       └── wrapperr
           └── [id]
               ├── @route1
               │   └── page.tsx
               ├── layout.tsx
               ├── page.tsx
               └── param
                   └── page.tsx
```

### Current vs. Expected behavior

building when parallel route use, if you use generaterMetadata use together, occurs error.
However, if you remove generataMetadata, it works well

exist generateMetadata build result

<img width="1096" alt="image" src="https://github.com/vercel/next.js/assets/66045666/c5337a2f-845e-470b-8d7f-7373aab7d079">

remove generateMetadata build result
<img width="953" alt="image" src="https://github.com/vercel/next.js/assets/66045666/0e54bf2d-08f5-4af1-bf7f-9d119622bf4f">



### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 21.6.0: Thu Sep 29 20:13:46 PDT 2022; root:xnu-8020.240.7~1/RELEASE_ARM64_T8101
Binaries:
  Node: 20.4.0
  npm: 9.7.2
  Yarn: 1.22.11
  pnpm: N/A
Relevant Packages:
  next: 14.0.4
  eslint-config-next: 14.0.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.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 build (local)

### Additional context

_No response_
Repository: godot
Issue: C# tool scripts without a parameterless constructor crash the editor on build
Labels: discussion,topic:editor,needs testing,topic:dotnet

### Tested versions

Reproducible in 4.2.1.stable

### System information

Godot v4.2.1.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21905.1001) - AMD Ryzen 7 2700X Eight-Core Processor (16 Threads)

### Issue description

## Problem
If you instantiate a C# tool script that has no parameter-less constructor in a scene and then rebuild, the editor will crash.

This can happen if you instantiate the tool script through another tool script.

## Expected behavior
I expect the editor not to crash and instead output an error message telling that it couldn't instantiate the culprit script.

AFAIK C# tool scripts always need a parameter-less constructor so I don't expect the editor to be able to reload such scripts. However the editor shouldn't crash because of such scripts.

### Steps to reproduce

1. open `scene.tscn` in the MRP
2. build a first time
3. reload the editor (an instance of a tool script without a parameter-less ctor will be added to the scene)
4. change the source of any C# script (e.g. add a newline)
5. rebuild
6. the editor crashes

### Minimal reproduction project (MRP)

[MRP.zip](https://github.com/godotengine/godot/files/13928273/MRP.zip)
Repository: create-react-app
Issue: issue while installing react-app in cmd prompt
Labels: needs triage

C:\Users\karth>npm i -g create-react-app
npm WARN deprecated tar@2.2.2: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.

changed 67 packages in 10s

5 packages are looking for funding
  run `npm fund` for details
Repository: godot
Issue: godot engine crashes
Labels: bug,platform:windows,topic:editor,needs testing

### Tested versions

Godot 4.2.1

### System information

windows 11, 8gb ram, GPU 0  	AMD Radeon(TM) Graphics  	Driver version:	31.0.12042.18002 	Driver date:	14-09-2023 	DirectX version:	12 (FL 12.1) 	Physical location:	PCI bus 3, device 0, function 0  	Utilization	5% 	Dedicated GPU memory	439/512 MB 	Shared GPU memory	0.1/3.6 GB 	GPU Memory	0.6/4.1 GB,CPU  	AMD Ryzen 3 7320U with Radeon Graphics   	Base speed:	2.40 GHz 	Sockets:	1 	Cores:	4 	Logical processors:	8 	Virtualization:	Enabled 	L1 cache:	256 KB 	L2 cache:	2.0 MB 	L3 cache:	4.0 MB  	Utilization	11% 	Speed	2.30 GHz 	Up time	0:22:21:31 	Processes	248 	Threads	3589 	Handles	212486, Memory  	8.0 GB  	Speed:	5500 MHz 	Slots used:	2 of 2 	Form factor:	Other 	Hardware reserved:	773 MB  	Available	1.4 GB 	Cached	1.5 GB 	Committed	10.2/15.2 GB 	Paged pool	593 MB 	Non-paged pool	590 MB 	In use (Compressed)	5.8 GB (206 MB), 

### Issue description

crash while starting the engine 

### Steps to reproduce

i happens while opening the exe file

### Minimal reproduction project (MRP)

it just for a while then closes instantly
Repository: godot
Issue: In a filesystem dock in split mode, the file view mode icon shows the next mode instead of the current mode
Labels: discussion,topic:editor,usability

### Tested versions

Reproducible in 4.2.1.stable

### System information

Godot v4.2.1.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21905.1001) - AMD Ryzen 7 2700X Eight-Core Processor (16 Threads)

### Issue description

More of a UX inconsistency than a bug.

In the filesystem dock, the icon/button that has focus in the image below shows the state the panel will be in if you click the button.
<img src="https://github.com/godotengine/godot/assets/7790167/56285970-3357-477c-891a-974451b00141" alt="drawing" width="300"/>

In itself this isn't a problem, but most other buttons/icons in the editor show the state the element is currently in, not the state it will be in if you click it.

My expectation here is that everything in the editor should follow the same UX conventions. In this case, buttons/icons should show the current state (and not the next one).

Not a huge deal but I was a bit confused by the current behavior at first. IMO changing it to fit the rest will help avoid confusion for other/new users.

### Steps to reproduce

To make the icon/button in question appear in an empty project, click the white square in the filesystem dock to switch it to split mode.

### Minimal reproduction project (MRP)

N/A
Repository: go
Issue: proposal: mime/multipart:  add WriteFile method to mime/multipart.Writer for streamlined file uploads from io.Reader
Labels: Proposal

### Proposal Details

## Abstract
This proposal suggests adding a new method, `WriteFile`, to the `mime/multipart.Writer` type in the Go standard library. The `WriteFile` method will simplify the process of adding file content to multipart forms directly from an `io.Reader`, enhancing the package's capability to handle file uploads efficiently, especially for large files or files sourced from streams.

## Background
The current `mime/multipart.Writer` API provides methods like `CreateFormFile` and `CreateFormField` for adding files and fields to multipart forms, which are widely used in HTTP client and server implementations for file uploads. However, after calling `CreateFormFile`, developers must manually copy the file content into the returned writer, which can be cumbersome.

## Proposal
I propose adding a new method to the `mime/multipart.Writer` type:

```go
func (w *Writer) WriteFile(fieldname, filename string, src io.Reader) error {
    p, err := w.CreateFormFile(fieldname, filename)
    if err != nil {
        return err
    }
    _, err = io.Copy(p, src)
    return err
}
```

This method will perform the following tasks:

- Create a form file part with the provided field name and filename.
- Stream data from the provided io.Reader to the form file part.
- Simplify adding file content to multipart forms, especially when the content is already available as an io.Reader (e.g., file streams, network data).

## Rationale

- **Ease of Use**: The WriteFile method abstracts away the boilerplate code associated with setting up form file parts and copying data, leading to cleaner and more concise client code.

- **Efficiency**: It's particularly beneficial for streaming large files or data from network sources, as it doesn't require loading the entire file content into memory.

- **Consistency with Existing APIs**: While the `mime/multipart` package already provides `WriteField` for simple text fields, there is no equivalent convenience method for files. `WriteFile` fills this gap and aligns with the existing API design.

## Compatibility
This change is fully backward-compatible. It introduces a new method to the existing **mime/multipart.Writer** type without modifying any existing functionality. It will not affect existing codebases using the **mime/multipart** package.

## Conclusion
Adding `WriteFile` to **mime/multipart.Writer** will enhance the Go standard library's ability to handle file uploads in a more efficient and user-friendly manner. This addition is a natural extension of the existing multipart API and will be beneficial for a wide range of applications that rely on file uploads, particularly those dealing with large or streamed files.
Repository: next.js
Issue: Css is not loaded correctly
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/competent-james-kzly2d

### To Reproduce

1: visit the sandbox: https://codesandbox.io/p/devbox/competent-james-kzly2d
2: update route to: https://kzly2d-3000.csb.app/dashboard/scheduler
3: as you can see i have global.css that is loaded inside the main page and inside scheduler page, with yarn dev all works fine, but in production this css has no effect and is not loaded.

### Current vs. Expected behavior

Actually css is not loaded, should be.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023
Binaries:
  Node: 18.17.0
  npm: 9.6.7
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.0.4
  eslint-config-next: 14.0.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A


warn  - Latest canary version not detected, detected: "14.0.4", newest: "14.0.5-canary.55".
        Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
        Read more - https://nextjs.org/docs/messages/opening-an-issue
Done in 1.93s.
```


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

Not sure, App Router

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

next start (local)

### Additional context

_No response_
Repository: PowerToys
Issue: Hosts File Editor: activate / deactivate all entries
Labels: Idea-Enhancement,Needs-Triage,Product-Hosts File Editor

### Description of the new feature / enhancement

Please implement a button that activates or deactivates all entries.

### Scenario when this would be used?

Temporarily grant / deny a program complete internet access - for example in the situation when the hosts file is used as a tracking blocker.

### Supporting information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Allow plugins to hook into latent noise generation
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Add a generate_latent_noise callback hook, that would by default use the normal(0,1) tensor, but which could be overridden to let plugins control the distribution of latent noise.  Currently there's no way to override the latent noise, but other distributions such as beta are better suited to the -4/+4 clamped latent range/provide support for non-spherical distributions and there are a few techniques such as brownian/procedural surfaces that could be used to nudge generations in very interesting ways.

### Proposed workflow

(this could/would be part of a plugin, but the callback needs to exist for it to work afaict)

1. Go to txt2img or img2img
2. Enable alternate noise generation, and choose between pixel space (rgb/hsl) and latent space noise, then drag sliders to control beta distributions for each channel in whatever space I'm working in to shape the noise in that channel.
3. Optionally specify a procedural surface generator to introduce autocorrelation in the noise and nudge the generation with micropatterns.


### Additional information

_No response_
Repository: vscode
Issue: [css] Outline doesn't show @layer 
Labels: feature-request,css-less-scss

If you are editng a CSS file with layers, the **Outline** panel doesn't show them. It does show `@media` rules however.

```css
@layer abc {}
```

I hope the Outline panel would show `@layer` rules they are useful for organizing code.
Repository: vscode
Issue: Folder collapses after rename when changing letter case
Labels: bug,file-explorer,macos

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: Version: 1.86.0-insider (Universal) and Version: 1.85.1 (Universal)
- OS Version: macOS 14.1.1

Steps to Reproduce:

1. Open a file located inside any folder.
2. Rename the parent folder while it is expanded, keeping the name the same but changing only the letter case. (For example, `name` → `Name` or `Name` → `NAME` )

Expected Result:
The folder should stay expanded after renaming is done, similar to the behavior observed when the final name is different.

Actual Result:
Folder collapses.

Screencast:

https://github.com/microsoft/vscode/assets/116561995/43e6e735-3702-44f1-8095-e768a3c787f6
Repository: deno
Issue: Abortable single-character reader for stdin
Labels: suggestion,runtime

## The Problem

In my CLI application, I need to read single characters from stdin until an event happens (eg. a timer runs out), and then I need to cancel all the pending reads and change back to normal stdin mode, so that things like `alert` work.

This is the code I've used:
```ts
async function* readKeys(signal: AbortSignal) {
  const decoder = new TextDecoder();
  const key = new Uint8Array(1);

  Deno.stdin.setRaw(true, { cbreak: true });
  while (!signal.aborted) {
    await Deno.stdin.read(key);
    if (signal.aborted) break;
    yield decoder.decode(key);
  }
  Deno.stdin.setRaw(false);
}

alert("When you're ready, press Enter, then you have 5s to press various keys.");

const ac = new AbortController();
setTimeout(() => {
  console.log("Time's out!");
  ac.abort();
}, 5_000);

for await (const key of readKeys(ac.signal)) {
  console.log("Key pressed: ", key);
}
alert("Good job, you pressed keys.");
```

If you try to run this, you'll notice that after the _“Time's out!”_ message, the application hangs until you press another button, and only then it will print out _“Good job, you pressed keys.”_ That is because the function `Deno.stdin.read(key)` is still locked and waiting for another key. Since `Deno.stdin.read` doesn't accept an AbortSignal as an argument, there is really no way to cancel the read.

One might naïvely think (as I did) that not awaiting the call would fix the problem. It doesn't: the read function is still blocking the stdin stream, and resetting the mode to non-raw before the function finishes makes the problem even worse, as it will only release the stream once the user presses Enter.

## A Possible Solution
Adding a second optional parameter of type [`AbortSignal`](https://deno.land/api@v1.39.3?s=AbortSignal) to [`Deno.stdin.read`](https://deno.land/api@v1.39.3?s=Deno.Reader#method_read_0) fix my issue. However, considering that `Deno.Reader` is deprecated, a solution using `Deno.stdin.readable` would be preferable.
Repository: godot
Issue: Geometry2D.clip_polygons() Geometry2D.merge_polygons() returns [(0,0)]
Labels: bug,topic:core,needs testing

### Tested versions

- Tested on: 4.2,stable  4.2.1

### System information

windows 11 - Godot 4.2x

### Issue description

Maybe there is something I need to the packedVector2Arrays before passing them as arguments for clip_polygon() or merge_polygon() but there is no documentation about it. 

### Steps to reproduce

- create a scene, add two polygon2D or collisionpolygon2D nodes, create polygons on the editor that overlap.
- on the root script:
```
func  _ready():
	var _poly1 = $CollisionPolygon2D
	var _poly2 = $CollisionPolygon2D2
	var _new_poly: Polygon2D = Polygon2D.new()
	var clipped_poly: PackedVector2Array
	
	var _poly1_vec2array =  _poly1.polygon #you can use .get_polygon() result is the same
	print(poly1_vec2array) # the polygons are assigned correctly
	var _poly2_vec2array = _poly2.polygon
	print(poly2_vec2array) # the polygons are assigned correctly

	clipped_poly = Geometry2D.clip_polygons(poly1_vec2array,poly2_vec2array)

	print_debug(clipped_poly) # returns a single point on PackedVector2Array = [(0,0]] 

```

### Minimal reproduction project (MRP)

[Tests.zip](https://github.com/godotengine/godot/files/13929008/Tests.zip)
Repository: PowerToys
Issue: Mouse Without Borders Waking Remote Machine Disable Option
Labels: Idea-Enhancement,Needs-Triage,Product-Mouse Without Borders

### Description of the new feature / enhancement

MWB is able to wake a remote machine in S3 sleep.  I would strongly like to have the option to fully disable this function.


### Scenario when this would be used?

I often leave both my host and remote machine in S3 sleep.  There are occasions where I want to only wake and use the host machine.  When waking the host, MWB automatically refreshes the connection and therefore wakes the remote machine every time.

### Supporting information

This seems to be only semi related to this closed issue.
https://github.com/microsoft/PowerToys/issues/26261