sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rustdesk
Issue: Multi-Monitor problem - clicking on first window results in click on other windows
Labels: bug

### Bug Description

Using Linux Mind Debian Edition LMDE 6, 4 Monitors (all different resolutions), connecting to a Windows-Client with 3 Monitors an different resolutions.

On Linux:  #2-Main 2560x1440 in the middle, #1 3840x2160 scaled to 150% on the left, #3 3840x2160 scaled 150% on the right, #4 1920x1080 scaled 100% top right.

On Windows Main: one Screen 1920x1080 left, main screen 2560x1440 middle, and last screen 1920x1080 on the right.

Now controlling from the Linux side moving a windows on the main screen to the right at some point (~3/4 of the screen) the windows flicks wild too the second (windows) monitor. I tried screenshoting the behaviour, hope this helps. 

Setup Linux: 
![setup-Linux](https://github.com/user-attachments/assets/6a620602-a389-4f7b-87ec-d1c4a89d8015)

Setup-Windows:
![setup-Windows](https://github.com/user-attachments/assets/6265b037-bb4e-4ff6-b2c6-6f0d2bbde07b)

Moving Explorer-Window on Main on Windows:
I start moving or using the mouse works fine at first, until the mouse moves too far right: 
![moving-ok](https://github.com/user-attachments/assets/1170c1a1-b4a8-4d07-aed8-025e70595a94)

it now jumps to the right monitor:
![suddenly-flickes-to-right-mon](https://github.com/user-attachments/assets/a0570390-0aa1-402e-952a-a9847fb9000e)

Mouse still on the middle monitor going up it jumps to the left monitor:
![flicks-to-left-monitor](https://github.com/user-attachments/assets/10fecce3-fcde-48f1-9a82-9a71f5fa5d8a)

And as a bonus all my clicks with the mouse get magically sent to the right or left monitor.



### How to Reproduce

Unsure, could also be a bug in Linux, but did not occur to me with any other application so far.

### Expected Behavior

The mouse should not switch to the second/third monitor while still active on the main one, I guess?

### Operating system(s) on local (controlling) side and remote (controlled) side

Linux -> Windows

### RustDesk Version(s) on local (controlling) side and remote (controlled) side

1.3.3. -> 1.3.3 (also previous versions up from 1.2.6)

### Screenshots


https://github.com/user-attachments/assets/551f2443-4316-473b-9bf4-a7a76e1da768



### Additional Context

_No response_
Repository: PowerToys
Issue: [Power toys-Image resizer]: Edit Buttons in Image Resizer Not Associated with Their Names and Dimensions.
Labels: Issue-Bug,Resolution-Fix Committed,Product-Image Resizer,Priority-2,Area-Accessibility,A11yE+D,A11ySev2,A11yWCAG

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Image Resizer

### Steps to reproduce

**Test environment:**
OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.1340)
Power toys version: v0.86.0
Screen Reader: Narrator

**Repro Steps:**

1. Open the Power Toys app in the desktop.
2. Select the Image Resizer option from left navigation pane.
3. Turn on narrator using Ctrl + Win + Enter.
4. Now navigate to the Edit buttons present below the Add new buttons.
5. Observe the issue.

**User Experience:**
Screen reader users will be unable to understand which button controls which dimension, making it difficult or impossible to resize images effectively.

**Note:**
Same issue is also repro for delete button.

**Attachments:**
![Image](https://github.com/user-attachments/assets/cb3417f7-7170-4f02-84d2-e15833643443)

https://github.com/user-attachments/assets/465eb498-0f60-413f-80a0-e66c58b38ff8

**Guideline reference:**
https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships


### ✔️ Expected Behavior

Each edit button in the image resizer should have a descriptive label, either visually or programmatically, that clearly identifies its function and the dimensions it controls (e.g., "Set Width to 500px", "Set Height to 300px").

### ❌ Actual Behavior

The edit buttons in the image resizer tool are not properly labeled or associated with the corresponding image dimensions (e.g., width, height).

### Other Software

_No response_
Repository: puppeteer
Issue: "[screenshot.spec] Screenshots ElementHandle.screenshot should run in parallel with page.close()" is flaky with Firefox
Labels: confirmed,P3,firefox

See https://github.com/puppeteer/puppeteer/actions/runs/12157249591/job/33902654440#step:11:807

```
29) Screenshots
       ElementHandle.screenshot
         should run in parallel with page.close():
     ProtocolError: Protocol error (browsingContext.create): unknown error TypeError: webProgress.browsingContext.currentWindowGlobal is null _sendCommandToBrowsingContext@chrome://remote/content/shared/messagehandler/transports/RootTransport.sys.mjs:132:9

      at Callback.<instance_members_initializer> (packages\puppeteer-core\src\common\CallbackRegistry.ts:125:12)
      at new Callback (packages\puppeteer-core\src\common\CallbackRegistry.ts:130:3)
      at CallbackRegistry.create (packages\puppeteer-core\src\common\CallbackRegistry.ts:28:22)
      at BidiConnection.send (packages\puppeteer-core\src\bidi\Connection.ts:105:28)
      at Session.send (packages\puppeteer-core\src\bidi\core\Session.ts:111:34)
      at Session.<anonymous> (packages\puppeteer-core\src\util\decorators.ts:63:21)
      at UserContext.createBrowsingContext (packages\puppeteer-core\src\bidi\core\UserContext.ts:146:29)
      at UserContext.<anonymous> (packages\puppeteer-core\src\util\decorators.ts:63:21)
      at BidiBrowserContext.newPage (packages\puppeteer-core\src\bidi\BrowserContext.ts:189:44)
      at Context.<anonymous> (test\src\screenshot.spec.ts:441:21)
```

In Nightly, it is flaky in the same test but with a different error message:

```
ProtocolError: Protocol error (browsingContext.create): no such frame DiscardedBrowsingContextError: BrowsingContext does no longer exist RemoteError@chrome://remote/content/shared/RemoteError.sys.mjs:8:8
MessageHandlerError@chrome://remote/content/shared/messagehandler/Errors.sys.mjs:14:5
DiscardedBrowsingContextError@chrome://remote/content/shared/messagehandler/Errors.sys.mjs:76:5
waitForCurrentWindowGlobal@chrome://remote/content/shared/messagehandler/transports/BrowsingContextUtils.sys.mjs:132:11

      at Callback.<instance_members_initializer> (packages\puppeteer-core\src\common\CallbackRegistry.ts:125:12)
      at new Callback (packages\puppeteer-core\src\common\CallbackRegistry.ts:130:3)
      at CallbackRegistry.create (packages\puppeteer-core\src\common\CallbackRegistry.ts:28:22)
      at BidiConnection.send (packages\puppeteer-core\src\bidi\Connection.ts:105:28)
      at Session.send (packages\puppeteer-core\src\bidi\core\Session.ts:111:34)
      at Session.<anonymous> (packages\puppeteer-core\src\util\decorators.ts:63:21)
      at UserContext.createBrowsingContext (packages\puppeteer-core\src\bidi\core\UserContext.ts:146:29)
      at UserContext.<anonymous> (packages\puppeteer-core\src\util\decorators.ts:63:21)
      at BidiBrowserContext.newPage (packages\puppeteer-core\src\bidi\BrowserContext.ts:189:44)
      at Context.<anonymous> (test\src\screenshot.spec.ts:441:21)
```
Repository: deno
Issue: `deno clean -e` / `deno clean --prod`
Labels: cli,suggestion,install

It would be great to add a mode to `deno clean` where it only cleans _some_ of the `DENO_DIR` / `node_modules` folder. I am imagining a `deno clean -e` that has the same behaviour as `deno clean && rm -rf node_modules && deno install -e`, and a `deno clean --prod` which has the same behaviour as `deno clean && rm -rf node_modules && deno install --prod`. Unlike the mentioned alternatives, this would not require re-downloading and untarring a bunch of packages however (this is slow!).

This would be very useful for Docker setups:

```Dockerfile
FROM denoland/deno

COPY . .

# install dependencies (including dev), to perform the build
RUN deno install
RUN deno task build

# remove all the dev dependencies
RUN deno clean -e main.ts # or RUN deno clean --prod

# warmup code cache
RUN timeout 2s deno run --cached-only -A main.ts || true

ENTRYPOINT ["deno", "run", "--cached-only", "-A", "main.ts"]
```

Right now this requires a multi step build, which is really annoying because it adds significant overhead because dependencies need to be installed twice.
Repository: storybook
Issue: [Investigation]: Support React 19
Labels: bug,dependencies,react

### Describe the bug

React 19 has been released. We should investigate all the changes that are needed to fully support it.

- Make sure that React 19 is supported in all packages that have it as peer dependency
  - [ ]  @storybook/ember
  - [x] @storybook/addon-links
  - [x]  @storybook/blocks
  - [x]  @storybook/react
  - [x]  @storybook/react-vite
  - [x]  @storybook/react-webpack5
  - [x]  @storybook/react-dom-shim
  - [x]  @storybook/react-webpack
  - [x]  @storybook/experimental-nextjs-vite
  - [x]  @storybook/react-native-web-vite
  - [x]  @storybook/nextjs
  - [x]  @storybook/icons
- [x] Replace react-confetti (dep of @storybook/addon-onboarding) with another one that supports React 19 https://github.com/storybookjs/storybook/pull/30098
- [x] Update [usage of act](https://bsky.app/profile/phry.dev/post/3lchyxhe2ts2b) in places [like this](https://github.com/storybookjs/storybook/blob/ceb8387e24f9b401bd3fc693dbb0f5b220a389d0/code/renderers/react/src/portable-stories.tsx#L66) https://github.com/storybookjs/storybook/pull/30037


#### To users:
You should be able to use Storybook with React 19, but if you found any inconsistency or unsupported feature, please let us know in this issue.
Repository: svelte
Issue: transition:slide does not apply overflow:hidden in Safari (Svelte 5 only)
Labels: transition/animation

### Describe the bug

After migrating to Svelte 5, all my "slide" transitions overflow their inner content in Safari.


https://github.com/user-attachments/assets/08dd4e87-b7cf-467b-a16d-aab52b540535

In the code for the slide transition, there is an 'overflow: hidden' css that's supposed to be applied (and it does in all browsers when using Svelte 4, and in all browsers except Safari when using Svelte 5).

https://github.com/sveltejs/svelte/blob/4c4f18b24c644f7e17cd9fea7fde777f3324e206/packages/svelte/src/transition/index.js#L126

I can finish my upgrade by adding `overflow-hidden` to all the places I use this transition at (and test them manually), but I feel like this should have just worked without any changes (and didn't want to risk new UI issues).

### Reproduction

https://svelte.dev/playground/2320dc5a6c8a4ef7aeba080f88b32208?version=5.5.3

### Logs

_No response_

### System Info

```shell
System:
    OS: macOS 15.1.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 1.05 GB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.18.1 - ~/.nvm/versions/node/v20.18.1/bin/node
    npm: 10.9.1 - ~/.nvm/versions/node/v20.18.1/bin/npm
    pnpm: 9.14.4 - ~/Library/pnpm/pnpm
    bun: 1.1.38 - /opt/homebrew/bin/bun
    Watchman: 2024.12.02.00 - /opt/homebrew/bin/watchman
  Browsers:
    Chrome: 131.0.6778.86
    Edge: 131.0.2903.70
    Safari: 18.1.1
  npmPackages:
    svelte: 5.5.3 => 5.5.3
```


### Severity

annoyance
Repository: go
Issue: all: remote file server I/O flakiness with "Bad fid" errors on plan9
Labels: OS-Plan9,NeedsInvestigation

```
#!watchflakes
post <- builder ~ `plan9-` && `:  Bad fid`
```
Intermittent `Bad fid` errors are observed especially on plan9-arm performing I/O to a remote file server. The most common context is demand-loading pages from a binary hosted on the LUCI swarming front-end (linux) machine:
```
2024-11-08 14:46 x_tools-go1.23-plan9-arm tools@8a0e08fb release-branch.go1.23@c390a1c2 x/tools/go/callgraph/rta.TestRTA/testdata/multipkgs.txtar ([log](https://ci.chromium.org/b/8731827708724902417))
=== RUN   TestRTA/testdata/multipkgs.txtar
    testfiles.go:141: err: exit status: 'go 65004: 1': stderr: go: error obtaining buildID for go tool asm: exit status: 'asm 65114: i/o error in demand load accessing /home/swarming/.swarming/w/ir/x/w/goroot/pkg/tool/plan9_arm/asm: Bad fid'
        
--- FAIL: TestRTA/testdata/multipkgs.txtar (3.30s)
```
But errors can occur in other contexts, for example reading an object file from the build cache (also on the LUCI front-end):
```
2024-11-19 18:04 go1.23-plan9-arm release-branch.go1.23@777f43ab cmd/link.TestCheckLinkname/badlinkname.go ([log](https://ci.chromium.org/b/8730806350947619521))
=== RUN   TestCheckLinkname/badlinkname.go
=== PAUSE TestCheckLinkname/badlinkname.go
=== CONT  TestCheckLinkname/badlinkname.go
    link_test.go:1454: build failed unexpectedly: exit status: 'go 74201: 1':
        # command-line-arguments
        link: cannot read object file:read /home/swarming/.swarming/w/ir/x/w/gocache/69/6932a64211f8ea57b303c16f21c046f130e2ca4053d7f9f2fa8ca6a5a87ac3be-d: Bad fid
--- FAIL: TestCheckLinkname/badlinkname.go (17.96s)
```
The fault is almost certainly not a go problem, but is within the plan9 file server: in this case, the variant of `exportsrv` built in to the `drawterm` command.
Repository: vscode
Issue: Rendered text has thinner lines and colors are off
Labels: bug,macos,editor-gpu

Testing #234762

| Without Gpu accel | With Gpu accel |
|----------|----------|
|   ![Image](https://github.com/user-attachments/assets/b0066d2a-1e8a-49c8-897c-aeba7e905e02)  |   ![Image](https://github.com/user-attachments/assets/3517c427-df4d-4cad-855c-c2cc44b2eb48)   |



![Image](https://github.com/user-attachments/assets/bf296773-544d-408a-9b45-3cf7442a0af8)

My editor settings: 

```
	"editor.codeLensFontFamily": "\"Jetbrains Mono\"",
	"editor.experimental.asyncTokenization": true,
	"editor.fontFamily": "JetBrains Mono, Menlo, Monaco, 'Courier New', monospace",
	"editor.fontLigatures": true,
	"editor.fontSize": 16,
	"editor.formatOnSave": true,
	"editor.inlayHints.enabled": "offUnlessPressed",
	"editor.inlayHints.fontSize": 14,
	"editor.insertSpaces": false,
	"editor.largeFileOptimizations": false,
	"editor.lightbulb.enabled": "off",
	"editor.renderWhitespace": "none",
	"editor.smartSelect.selectSubwords": true,
	"editor.tokenColorCustomizations": {
		"[Default Light+]": {
			"textMateRules": [
				{
					"scope": "entity.other.attribute-name",
					"settings": {
						"foreground": "#001080"
					}
				}
			]
		}
	},
	"editor.trimAutoWhitespace": false,
	"editor.unicodeHighlight.ambiguousCharacters": false,
	"editor.unicodeHighlight.invisibleCharacters": false,
	"editor.unicodeHighlight.nonBasicASCII": false,
```

Version: 1.96.0-insider
Commit: 64e869f7ddf58d76097dc5ab7f36515044304b25
Date: 2024-12-04T05:03:54.771Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.1.0
Repository: vscode
Issue: VSCode for GitHub: search results incomplete
Labels: bug,info-needed,search

<!-- ⚠️⚠️ 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. -->

<!-- 🪓 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: VSCode for GitHub
- OS Version: current GitHub version, Chrome version: 131.0.6778.87 (Official Build) (64-bit)

This issue is very similar to this one: https://github.com/microsoft/vscode/issues/116213

Steps to Reproduce:

1. Open a PR on GitHub.
2. Go to Files changed, press '.' on keyboard.
3. VSCode for GitHub is launched, open a changed file in this PR.
4. Open a changed file, select some entity that does appear in other files (function name, class, etc)
5. Press Ctrl-Shift-F, and search for said entity.
6. Only occurrences in the currently opened file are displayed.
7. Open some other file that mentions that entity.
8. Search again.
9. Now Search results show occurrences in two files, but not other ones, which do mention this entity.
10. Close one of the files, search again.
11. Now Search results show occurrences only in one file.

Expected Behavior: The search returns results for all instances of the string, regardless if the file is open or not.
Repository: PowerToys
Issue: FancyZones causing issues when used with Firefox (the browser window decreases in size until it's just a small line when scrolling/moving mouse)
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

I'm using the latest version of Firefox (133.0 64-bit). Have created zones with fancyzones and it was working fine, but recently a strange issue is now consistently happening. When I pin a Firefox window in one of the zones, the right side of the window moves to the left and the bottom side moves up until there is basically nothing left. It looks like it's getting smaller on it's own, but it's actually any interaction you have with the window (scrolling, clicking etc.). It keeps getting smaller until it's basically gone. While it's getting smaller, I can move the window, maximize it by moving it to the top of the screen, but it just keeps getting smaller again. The window is basically rendered useless when the issue starts.

### ✔️ Expected Behavior

Fixefox window should just pin in the selected fancyzone and not get smaller when I'm scrolling/clicking inside the window. 

### ❌ Actual Behavior

This isn't happening to any other application I'm using, including Chrome and Windows Explorer. This is also not happening when I use the built-in zone feature (hover on maximize button in a window and select a zone). It's only happening when using fancyzones. Sometimes it doesn't happen after pinning a window in a zone. When I do it multiple times, it does happen. The chance of it happening is about 30% based on my testing. It also doesn't matter which zone I'm using. When I move a Firefox tab outside of the window (creating a second/separate window), the new browser window is fine... until I snap it to a fancyzone. 

Have searched quite a bit and can't find anything online where people are experiencing this and I don't think it's something I'm supposed to share as a bug with the Firefox developers. Important to note, the window isn't "resizing" as I can see that the minimize/maximize/close buttons are not moving to fit in the window. When the window gets smaller, the entire interface including the content is simply being cut off.  Have closed all other applications to make sure something else isn't influencing this. 

### Other Software

_No response_
Repository: neovim
Issue: Node selection behavior changed after recent Treesitter update in Neovim
Labels: status:blocked-external,bug-regression,has:bisected,treesitter

This issue was originally reported on the nvim-treesitter repository. I was advised to open it here and attempt a bisect to identify the cause.

After a recent update to Neovim (commit 865ba42e0401043836bca567b4add164c5c46e6f), the behavior of Treesitter in R scripts has changed. Specifically, when placing the cursor at the beginning of an R script, a different node is now being selected compared to previous versions. This appears to be a regression introduced by the aforementioned commit.

Please let me know if you need additional details or steps to reproduce.

For this R code

```r
x <- 1L
y <- 2L
z <- 3L
```

The corresponding tree is

```
(program ; [0, 0] - [3, 0]
  (binary_operator ; [0, 0] - [0, 7]
    lhs: (identifier) ; [0, 0] - [0, 1]
    rhs: (integer)) ; [0, 5] - [0, 7]
  (binary_operator ; [1, 0] - [1, 7]
    lhs: (identifier) ; [1, 0] - [1, 1]
    rhs: (integer)) ; [1, 5] - [1, 7]
  (binary_operator ; [2, 0] - [2, 7]
    lhs: (identifier) ; [2, 0] - [2, 1]
    rhs: (integer))) ; [2, 5] - [2, 7]
```

with nvim 0.11.0 (this commit https://github.com/neovim/neovim/commit/3d1e6c56f08f420c0d91ffbee888c05b20806a5e), when the cursor is placed on `x`, this is line 3 in the tree that is selected

![image](https://github.com/user-attachments/assets/c88a2eac-120e-43b7-b19d-496071a6741e)

However, on nvim 0.11.0 (this commit https://github.com/neovim/neovim/commit/865ba42e0401043836bca567b4add164c5c46e6f) the selected node is `program`

![image](https://github.com/user-attachments/assets/f4d6e78e-4b6e-4176-a51e-c95f9d78ef15)


### Steps to reproduce


1. I am using bob (https://github.com/MordechaiHadad/bob) to switch between the two commits:

```bash
bob use 865ba42e0401043836bca567b4add164c5c46e6f
bob use 3d1e6c56f08f420c0d91ffbee888c05b20806a5e
```

2. Create an R file with this code *at the top of the file*:

```r
x <- 1L
y <- 2L
z <- 3L
```

3. Call `:InspectTree`.
4. Place the cursor on `x` (first line of the R code).
5. Compare which node is selected between 3d1e6c56f08f420c0d91ffbee888c05b20806a5e and 865ba42e0401043836bca567b4add164c5c46e6f.


### Expected behavior

Having the same node selected between the two commits.

### Nvim version (nvim -v)

NVIM v0.11.0-dev-865ba42e

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

I have not tried on vim. 

### Operating system/version

Linux Mint 22

### Terminal name/version

kitty 0.37.0 created by Kovid Goyal

### $TERM environment variable

xterm-kitty

### Installation

bob installer
Repository: PowerToys
Issue: black empty screen while using fancyzones
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

1. enter fancy zones editor
2. customize a new one (3 zones)
3. enable it and use it for a while (about 5 minutes)
4. hold and press Ctrl + Windows + Shift + B 
And then the black screen appeared, I tried everything. nothing worked but hitting the power button (to turn my laptop off). The screen kept being black, empty and it only displayed something when I turned my laptop on!

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_