sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Mouse Without Borders is not working
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.83.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Refresh connections to use MWB

### ✔️ Expected Behavior

MWB works

### ❌ Actual Behavior

MWB doesn't work

### Other Software

_No response_
Repository: godot
Issue: Android USB Remote Debug Session not starting with Godot 4.3 stable
Labels: bug,platform:android,topic:editor

### Tested versions

- v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 4070 (NVIDIA; 32.0.15.5585) - 13th Gen Intel(R) Core(TM) i5-13400F (16 Threads)

### Issue description

Hey, so Godot isn't starting up a remote debug session with the one click remote install. I have followed all the steps to create android APKs and set up remote debugging and that's all working. But when I click "Remote Debug" in the top-right, I choose my device and it'll build and install, but when it runs Godot won't do anything. It won't show to remote panel, or give me access to the game running on my device at all, so no std logs or anything either.

I have activated and deactivated "Debug -> Deploy with Remote Debug" and neither seems to make a difference.

I also followed steps spoke about in this issue: https://github.com/godotengine/godot/issues/91359 like closing the java process and running Godot as admin, but unfortunately nothing's worked yet. I've also revoked debugging permission on my device and re-given permission but still nothing.

It just seems to be Godot doesn't know the game is running on the device. This also doesn't seem anything to do with my project as I've attached just a tiny 1-scene project and it still doesn't debug correctly on my machine.

Ouput:
```
0 param: --remote-debug
1 param: tcp://localhost:6007
2 param: --xr_mode_regular
3 param: --use_immersive
Installing to device (please wait...): Google Pixel 6
--- Device API >= 21; debugging over USB ---
--- DEVICE API >= 21; DEBUGGING OVER USB ---
Reverse result: 0
```

Java version:
```
PS C:\Users\jacob> java --version
openjdk 17.0.11 2024-04-16
OpenJDK Runtime Environment Temurin-17.0.11+9 (build 17.0.11+9)
OpenJDK 64-Bit Server VM Temurin-17.0.11+9 (build 17.0.11+9, mixed mode, sharing)
```

### Steps to reproduce

- dl test-remote project
- connect android phone (make sure it's all set up correctly)
- run "Remote Debug" in the top-right
- See that Godot doesn't know it's running and not showing the Remote panel

### Minimal reproduction project (MRP)

[test-remote.zip](https://github.com/user-attachments/files/16848696/test-remote.zip)
Repository: electron
Issue: [Feature Request]: `ready-to-show` event on `webContents`
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

I moved from `BrowserWindow` to a `BaseWindow` with one or more `webContents` (via `WebContentsView`). I'd like to know when each of the `webContents` are `ready-to-show`.

### Proposed Solution

I propose this API:

```js
webContents.on("ready-to-show", () => console.log("ready-to-show"));
```

### Alternatives Considered

* Having `ready-to-show` on the `BaseWindow` (see #42291). — I think having it on the `webContents` makes more sense as a `BaseWindow` can contain multiple `webContents`.
* Using `did-finish-load`. — Workaround for now.

### Additional Information

`ready-to-show` already seems to be available on `webContents` internally:

https://github.com/electron/electron/blob/c41a28d7c850df00118b31aec67b0941cd0471eb/lib/browser/api/web-contents.ts#L827

For some reason, the following doesn't work though:

```js
webContents.on("ready-to-show", () => console.log("ready-to-show"));
```

The event also isn't documented.
Repository: godot
Issue: `lerp` accepts Variant as a `weight`, should be float
Labels: enhancement,topic:core,breaks compat

### Tested versions

Reproducible in v4.3.stable.official [77dcf97d8] or any 4.x

### System information

Windows 11

### Issue description

`lerp` accepts any Variant as a weight, altough it only supports float. Giving other values causes the function to fail silently. This problem was mentioned in #64332 as well, but I think it is a separate issue.
![kuva](https://github.com/user-attachments/assets/4e4a616c-51ee-4b36-a50d-2fa080d0beee)

The function is registered with a macro `FUNCBINDVR3`, which doesn't offer flexibility around the argument types. Possible solutions: inline the contents of the macro and write correct `get_argument_type(int p_arg)` function. Or modify the macro to relay the correct argument types.

### Steps to reproduce

Write
```
lerp(0.0, 10.0, "hello")
```
or just see the reference...

### Minimal reproduction project (MRP)

N/A
Repository: stable-diffusion-webui
Issue: [Feature Request]: example: extension "sd-webui-birefnet" for removing background
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 ?

so its a fast and great extension for removing background in very good qualitiy

it works so fare with a1111 and webui

but if i have file names usual  "image(103).png" -> the file after removing background is "image103.png"
**also upscale and all other stuff, the name is not the same if i have brackets !**


### Proposed workflow

![grafik](https://github.com/user-attachments/assets/81e86972-4660-435b-a47c-0edd65377cda)


### Additional information

_No response_
Repository: ui
Issue: [feat]: `react-big-calendar` for calender options and event handling
Labels: area: request

### Feature description

[react-big-calendar](https://github.com/jquense/react-big-calendar) is a very good calender library that can enhance and work well with calender enhancements.

### Affected component/components

Calender

### Additional Context

Additional details here...

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: pytorch
Issue: `torch.unique` behaves strange for large input arrays on Windows
Labels: needs reproduction,module: windows,triaged,module: correctness (silent)

### 🐛 Describe the bug

We been having problem with updating our CI in torchmetrics (https://github.com/Lightning-AI/torchmetrics/pull/2671) to the newest version torch. A particular test that utilizes `torch.unique` is constantly failing on Windows for version v2.4.0 of Pytorch.

To reproduce:
```python
import torch
len(torch.randint(low=0, high=4, size=(100000, )).unique())
```
will return that the length is much larger of the unique array than the expected four values the array consist of.

On my local Windows machine this breaking point where `torch.unique` is no longer working as expected happens exactly at size 32767 and 32768 e.g. 
```python
import torch
print(len(torch.randint(low=0, high=4, size=(100000, )).unique()) == 4)  # True
print(len(torch.randint(low=0, high=4, size=(100000, )).unique()) == 4)  # False
```
32768 corresponds to 2^15 so I expect there is some limitation in place here.

### Versions

Collecting environment information...
PyTorch version: 2.4.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 11 Enterprise
GCC version: Could not collect
Clang version: Could not collect
CMake version: Could not collect
Libc version: N/A

Python version: 3.11.5 | packaged by Anaconda, Inc. | (main, Sep 11 2023, 13:26:23) [MSC v.1916 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.22631-SP0
Is CUDA available: True
CUDA runtime version: 12.3.107
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 4070 Laptop GPU
Nvidia driver version: 546.12
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture=9
CurrentClockSpeed=2400
DeviceID=CPU0
Family=198
L2CacheSize=11776
L2CacheSpeed=
Manufacturer=GenuineIntel
MaxClockSpeed=2400
Name=13th Gen Intel(R) Core(TM) i7-13700H
ProcessorType=3
Revision=

Versions of relevant libraries:
[pip3] mypy==1.7.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] pytorch-lightning==1.9.5
[pip3] torch==2.4.0+cu121
[pip3] torch-fidelity==0.3.0
[pip3] torchaudio==2.4.0
[pip3] torcheval==0.0.7
[pip3] torchmetrics==1.4.0.dev0
[pip3] torchvision==0.16.0+cu121
[conda] numpy                     1.26.4                   pypi_0    pypi
[conda] pytorch-lightning         1.9.5                    pypi_0    pypi
[conda] torch                     2.4.0+cu121              pypi_0    pypi
[conda] torch-fidelity            0.3.0                    pypi_0    pypi
[conda] torchaudio                2.4.0                    pypi_0    pypi
[conda] torcheval                 0.0.7                    pypi_0    pypi
[conda] torchmetrics              1.4.0.dev0               pypi_0    pypi
[conda] torchvision               0.16.0+cu121             pypi_0    pypi

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @peterjc123 @mszhanyi @skyline75489 @nbcsm @iremyux @Blackhex
Repository: go
Issue: proposal: container/set: new package to provide a generic set type
Labels: Proposal

This proposal is entirely based on the initial proposal and following discussion at https://github.com/golang/go/discussions/47331 and https://go.dev/blog/range-functions. There was a proposal to reopen this discussion 2 weeks ago (https://github.com/golang/go/issues/69033) but from what I understand proposals must include what's actually proposed. I apologize if this is not the proper way to do things.

### Proposal details

```go
// Package set defines a Set type that holds a set of elements.
package set

// A Set is a set of elements of some comparable type.
// The zero value of a Set is an empty set ready to use.
type Set[Elem comparable] struct {
	// contains filtered or unexported fields
}

// Add adds elements to a set.
func (s *Set[Elem]) Add(v ...Elem)

// Remove removes elements from a set.
// Elements that are not present are ignored.
func (s *Set[Elem]) Remove(v ...Elem)

// Contains reports whether v is in the set.
func (s *Set[Elem]) Contains(v Elem) bool

// Len returns the number of elements in s.
func (s *Set[Elem]) Len() int

// All is an iterator over the elements of s.
func (s *Set[Elem]) All() iter.Seq[Elem]

// Union constructs a new set containing the union of s1 and s2.
func Union[Elem comparable](s1, s2 Set[Elem]) Set[Elem]

// Intersection constructs a new set containing the intersection of s1 and s2.
func Intersection[Elem comparable](s1, s2 Set[Elem]) Set[Elem]

// Difference constructs a new set containing the elements of s1 that
// are not present in s2.
func Difference[Elem comparable](s1, s2 Set[Elem]) Set[Elem]
```

This is a partial copy of the API proposed at https://github.com/golang/go/discussions/47331, with the doc comment modified following https://github.com/golang/go/discussions/47331#discussioncomment-1168081, and a new `All` function that comes from https://go.dev/blog/range-functions.
Repository: terminal
Issue: sp; mf ... leaves cursor visible in the inactive pane
Labels: Issue-Bug,Area-TerminalControl,Product-Terminal,Priority-3

When I, for example, `wt sp cmd.exe; mf 1`, the cursor remains visible in the inactive pane.  This is unlike moving focus in other situations; normally the cursor is hidden in an inactive pane.
Repository: next.js
Issue: Changing search params on the same page does not reset the not found boundary
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/ali-idrizi/next-not-found-search-params-reproduction

### To Reproduce

This is a very minimal reproduction. In the `/about` page if the `q` search param is `"404"`, then `notFound` is called.

The layout has three buttons that call `router.push`, one to `/`, one to `/about` and the last to `/about?q=404`. Clicking the last button correctly shows the not found page. However, afterwards clicking `/about` no longer resets it. The 404 page goes away only after navigating to an entirely different page, or hard reloading.

In the network tab, I can see that the request for RSC payload is being sent, and it does not contain the `NEXT_NOT_FOUND` error, but the client fails to update the content.


https://github.com/user-attachments/assets/5e417703-8f70-4c35-9495-20e90318adbe



### Current vs. Expected behavior

Once `notFound` has been called on `/about?q=404`, clicking the `/about` button should correctly render the page, but instead it keeps showing the not found error.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Oct 5 21:02:42 UTC 2023
  Available memory (MB): 38098
  Available CPU cores: 24
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: N/A
  pnpm: 8.15.1
Relevant Packages:
  next: 15.0.0-canary.139 // Latest available version is detected (15.0.0-canary.139).
  eslint-config-next: N/A
  react: 19.0.0-rc-fb9a90fa48-20240614
  react-dom: 19.0.0-rc-fb9a90fa48-20240614
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


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

Navigation

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

next dev (local), next start (local)

### Additional context

_No response_
Repository: vscode
Issue: Emmet dot snippet is triggered after quotes
Labels: bug,emmet

<!-- ⚠️⚠️ 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.92.2 
- OS Version: OS: Darwin arm64 23.6.0

Steps to Reproduce:

1. Create empty `index.html`
2. Type `hello".` and hit enter (accept suggestion)
3. A snippet is inserted -- `hello"<div class=""></div>`

![8efc0c8d-f0e3-4f84-b69a-03f760ca1e94](https://github.com/user-attachments/assets/b003e57f-c1f6-42a2-8714-3df74b30ba8a)

I'm not sure whether this is intended behaviour or not, but looks more like a bug to me.
Repository: node
Issue: Node 22.1+ crashes process when a lot of VM processes are created/destroyed in parallel workers
Labels: child_process,regression,worker,v22.x

### Version

22.1.0

### Platform

```text
Darwin MacBook-Air.local 23.5.0 Darwin Kernel Version 23.5.0: Wed May  1 20:16:51 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T8103 arm64
```


### Subsystem

_No response_

### What steps will reproduce the bug?

- Clone https://github.com/vitest-dev/vitest
- Run `pnpm install --prefer-offline`
- Run `pnpm build`
- Run `cd test/core`
- Run `pnpm test:vmThreads --run`
- See a crash - sometimes it's instant, sometimes it's after a few tests ran

### How often does it reproduce? Is there a required condition?

Always

### What is the expected behavior? Why is that the expected behavior?

No crash

### What do you see instead?

`Command failed with exit code 129.` with no error.

### Additional information

This is most likely an issue with Vitest itself, but I am having a hard time debugging it. The error started happening on 22.1.0, 22.0.0 works as before. The changelog didn't help me. 

The issue seems to be with Worker Threads + VM as `vmForks` pool works fine or at least doesn't crash completely (it uses `child_process` under the hood instead, but the code for VM is the same) - looks like `child_process` just exists without crashing the main process, but it also doesn't print anything useful.
Repository: go
Issue: x/tools/go/ssa/ssautil: deprecate AllFunctions
Labels: Tools

I would like to deprecate the AllFunctions helper function, because it's a poorly specified mess (my bad).
As its doc comment says:

```go
// I think we should deprecate AllFunctions function in favor of two
// clearly defined ones:
//
//  1. The first would efficiently compute CHA reachability from a set
//     of main packages, making it suitable for a whole-program
//     analysis context with InstantiateGenerics, in conjunction with
//     Program.Build.
//
//  2. The second would return only the set of functions corresponding
//     to source Func{Decl,Lit} syntax, like SrcFunctions in
//     go/analysis/passes/buildssa; this is suitable for
//     package-at-a-time (or handful of packages) context.
//     ssa.Package could easily expose it as a field.
```

Before we can consider doing that (which will require a proposal), we should stop using it ourselves in x/tools and x/vuln. Its existing uses are:

```
// These test could use a simpler ad hoc algorithm, or an efficient CHA:
go/ssa/stdlib_test.go
go/ssa/builder_test.go

// both CHA and static do essentially the same reachability fixed point
// iteration and could do (the good bits of) AllFunctions themselves:
go/callgraph/cha/cha.go -- AllFunctions is not even correct here! see #66429
go/callgraph/static/static.go

--

// VTA uses AllFunctions to produce a set of entry points. 
// I suspect it is both a massive overapproximation and yet still not always correct (see #66251)
// What exactly does vta.CallGraph need?
cmd/callgraph/main.go
go/callgraph/vta/vta_test.go
go/callgraph/vta/graph_test.go
go/callgraph/callgraph_test.go
x/vuln/internal/vulncheck/utils.go

// just for debugging; could easily be deleted.
go/callgraph/vta/helpers_test.go 
```

I will tackle the first half. @zpavlinovic perhaps you could look at the VTA-related ones? What we need at this stage is just crisp descriptions of the exact requirements of each of these algorithms.
Repository: bitcoin
Issue: intermittent issue in wallet_upgradewallet.py                                    AssertionError: [node 2] Node returned unexpected exit code (1) vs (0) when stopping
Labels: CI failed

https://cirrus-ci.com/task/4629002713825280?logs=ci#L3296


```
 test  2024-09-03T07:00:27.797000Z TestFramework (ERROR): Assertion failed 
                                   Traceback (most recent call last):
                                     File "/ci_container_base/test/functional/test_framework/test_framework.py", line 132, in main
                                       self.run_test()
                                     File "/ci_container_base/ci/scratch/build-x86_64-pc-linux-gnu/test/functional/wallet_upgradewallet.py", line 150, in run_test
                                       self.stop_node(2)
                                     File "/ci_container_base/test/functional/test_framework/test_framework.py", line 581, in stop_node
                                       self.nodes[i].stop_node(expected_stderr, wait=wait)
                                     File "/ci_container_base/test/functional/test_framework/test_node.py", line 409, in stop_node
                                       self.wait_until_stopped(expected_stderr=expected_stderr)
                                     File "/ci_container_base/test/functional/test_framework/test_node.py", line 444, in wait_until_stopped
                                       self.wait_until(lambda: self.is_node_stopped(**kwargs), timeout=timeout)
                                     File "/ci_container_base/test/functional/test_framework/test_node.py", line 842, in wait_until
                                       return wait_until_helper_internal(test_function, timeout=timeout, timeout_factor=self.timeout_factor)
                                     File "/ci_container_base/test/functional/test_framework/util.py", line 289, in wait_until_helper_internal
                                       if predicate():
                                     File "/ci_container_base/test/functional/test_framework/test_node.py", line 444, in <lambda>
                                       self.wait_until(lambda: self.is_node_stopped(**kwargs), timeout=timeout)
                                     File "/ci_container_base/test/functional/test_framework/test_node.py", line 423, in is_node_stopped
                                       assert return_code == expected_ret_code, self._node_msg(
                                   AssertionError: [node 2] Node returned unexpected exit code (1) vs (0) when stopping
Repository: godot
Issue: Opening 2D/3D scene when no scene was previously open no longer switches to 2D/3D viewport
Labels: bug,topic:editor,usability,regression

### Tested versions

- Reproducible in 4.3.stable and 4.4.dev (514c564a8c855d798ec6b5a52860e5bca8d57bc9)
- Not reproducible in 4.2.2.stable

### System information

Fedora Linux 40 (KDE Plasma) - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 7600M XT (RADV NAVI33) - AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16 Threads)

### Issue description

Godot has this nifty behavior that it can detect the type of a scene (2D or 3D) based on its root node, and infer the viewport (2D/3D) to open for that scene accordingly.

This seems to have regressed in 4.3.stable and later.

What works:
- Open a 2D scene and make sure to be on the 2D viewport.
- Open a 3D scene: it will switch to the 3D viewport.
- Close the 2D scene, reopen it: it will switch to the 2D viewport.

What **doesn't** work:
- Have no scene open, make sure to be on the 2D viewport.
- Open a 3D scene: it stays on the 2D viewport.
- Close the 3D scene, make sure to be on the 3D viewport.
- Open a 2D scene: it stays on the 3D viewport.

CC @KoBeWi 

### Steps to reproduce

See above.

### Minimal reproduction project (MRP)

[Test2DAnd3DScenes.zip](https://github.com/user-attachments/files/16851150/Test2DAnd3DScenes.zip)