sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Switching between panes after changing clipboard with globalFindClipboard=true causes search field to be focused erroneously
Labels: bug,editor-find

<!-- ⚠️⚠️ 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.93.1
- OS Version: macOS 13.6.5

This bug drives me crazy when switching between panes, because the keyboard focus will shift to the wrong part of the UI and cause my typing to show up in the find panel rather than the actual file I'm trying to edit.

Steps to Reproduce:

1. Set user preference `editor.find.globalFindClipboard` to `true`
2. Open a new window
3. Pick the menu View > Editor Layout > Two Columns
4. With the left column focused, type in some text, any text. (It doesn't matter what it is.)
5. Pick the menu Edit > Find to open the find panel. 
6. Type 'foo' into the find panel
7. Select the text you typed in the leftmost column so that the find panel does not have keyboard focus
8. Switch focus to the rightmost column
9. Pick the menu File > New Text File
10. Pick the menu Edit > Find to open the find panel in the rightmost pane
11. Type 'bar' into it
12. Click inside the leftmost column to attempt to move keyboard focus to it
13. Note that the focus actually erroneously moves to the find pane, _not the text editor!_
Repository: neovim
Issue: Weird visual selection rendering for double-width character under cursor
Labels: bug-vim,tui,has:workaround,display,unicode  💩,visual-mode

### Problem

Since 26be6446e5ea1c5b22c50bfd9a0e5aa85927aff9, some new characters are treated as double-width rather than single. However the rendering of the cursor when on these characters is not consistent with the previous double width characters, e.g. emojis:

- Cursor doesn't take up two columns
- Visual selection doesn't account for the extra column

See below:
![image](https://github.com/user-attachments/assets/46614f4d-0c69-456c-998d-427fac0f8ee5)
(blank space in visual selection, should look like this:)
![image](https://github.com/user-attachments/assets/ee86c25c-26ac-4b19-bb24-97c3df7f2fc9)


### Steps to reproduce

`nvim --clean` `:edit foo` `i🗹<Esc>`

### Expected behavior

The new double width characters act like emojis, where the cursor takes up two columns which prevents the weird rendering

### Neovim version (nvim -v)

v0.11.0-nightly+b6e350a

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

no, vim 9.1

### Operating system/version

NixOS, linux kernel 6.10.7

### Terminal name/version

kitty 0.36.1

### $TERM environment variable

xterm-kitty

### Installation

build from source
Repository: pytorch
Issue: DISABLED test_pcontext_wait_on_a_child_thread (__main__.StartProcessesAsFuncTest)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22distributed%2Felastic%2Fmultiprocessing%2Fapi_test.py%3A%3AStartProcessesAsFuncTest%3A%3Atest_pcontext_wait_on_a_child_thread%22%5D)).

Error occurs because ROCm CI is still on py3.8. We are in the process of upgrading ROCm CI jobs to py3.10 - https://github.com/pytorch/pytorch/pull/134108 - which should resolve this issue.

cc @jeffdaily @sunway513 @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: go
Issue: x/website: show header on mobile devices
Labels: NeedsFix,website

### What is the URL of the page with the issue?

https://go.dev/tour

and all subsequent `/tour` pages

### Description

On desktop the header `h2` is clearly visible on the tour screens:

<img width="1063" alt="image" src="https://github.com/user-attachments/assets/92d48090-abf3-461d-9ea5-16ff4f98424c">

However, on mobile devices, the header is obscured due to incorrect padding:

<img width="427" alt="image" src="https://github.com/user-attachments/assets/a50a3b71-e22f-46e2-97a7-5937dfc5edb6">

As viewed here via devtools:

<img width="428" alt="image" src="https://github.com/user-attachments/assets/76b67130-01dd-41e7-b6ec-eeaa2f77d9d1">

### What did you see happen?

The header was hidden when viewed on a mobile device

### What did you expect to see?

The header displayed on mobile as it is on desktop
Repository: go
Issue: x/tools/gopls: issue an event when tests change
Labels: gopls,Tools

In my work to integrate #59445 into vscode-go, I am relying on file-change notifications to keep the test tree up to date as files change. @hyangah pointed out that the ideal solution would be to use notifications that tests were changed instead. I'm opening this issue to discuss whether it is feasible for gopls to send notifications to the editor when test discovery results change, and if so how that may be achieved.

As a followup, it would be powerful to extend change detection to arbitrary symbols and to follow the reference graph to affected tests, so that changing a function called by a test (and more generally, a symbol within the test's reference graph) would trigger an event and (in an editor with an active continuous test run) re-execute the test. I think the reference graph tracing should be reasonable to do within a package. I would be happy to submit a separate proposal for this.

CC @adonovan @findleyr
Repository: next.js
Issue: Search parameters are not invalidating  `notFound` cached responses in rsc
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/zen-cache-g8k798?workspaceId=835aa8f9-26fc-4cf6-be40-c1760c26a9e1

### To Reproduce

In the csb:
    1. Go to the client page
    2. It will start on the current year page 2024, which isn't found
    3. go to 2025. It will not be found (despite being there)
    4. Refresh the page on 2025, it will load.
    5. Go back to 2024. Not found, as expected.
    6. Return to 2025, Not found, this seems like a bug.

### Current vs. Expected behavior

Expected: changing pages search params should cause the server component to re-render

Actual: once a `notFound` path is hit, the response seems to be cached.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #41-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug  2 20:41:06 UTC 2024
  Available memory (MB): 32038
  Available CPU cores: 16
Binaries:
  Node: 20.17.0
  npm: 
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.0.0-canary.156
  eslint-config-next: 14.2.11
  react: 19.0.0-rc-f2df5694-20240916
  react-dom: 19.0.0-rc-f2df5694-20240916
  typescript: 5.6.2
```


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

Navigation

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

next dev (local)

### Additional context

First noticed in 14.2, but I can reproduce in  15 canary-156. I haven't tried on vercel.
Repository: ui
Issue: [feat]: components for react-email library integration
Labels: area: request

### Feature description

I are proposing the addition of a set of components designed specifically for email integrations within React/Express applications.

### Affected component/components

_No response_

### Additional Context

- Responsive Design: Components that adapt to various screen sizes and devices.
- Customizability: Options to adjust styling and layout to match application themes.
- Accessibility: Features to ensure that email components are accessible to all users.
- Pre-styled Elements: Consistent design elements for a unified user experience.

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: PowerToys
Issue: Put to the side Windows
Labels: Needs-Triage

### Description of the new feature / enhancement

Implement a feature that allows users to slide windows to the edges. Creating a partially visible overlay that doesn't obstruct the main application. Windows should automatically hide when not in focus, providing a clean and clutter-free workspace. 

This is similar to the "Slide Over" feature on Apple devices and Preme for Windows aplication.


### Scenario when this would be used?

This feature would be particularly useful for power users who frequently work with multiple applications simultaneously, especially those using laptops or small screens. By sliding windows to the sides of the screen, users can easily access and interact with them without cluttering their workspace. This is especially helpful for applications that are used frequently but don't require constant focus, such as chat clients, email, or task management tools.

Exemple of [an user using Preme for Windows:](https://imgur.com/a/happy-preme-windows-slideover-Z7D4T1c)

### Supporting information

Where the ideia came from: 
[r/Windows - Slideover alternative for Windows](https://www.reddit.com/r/Windows11/comments/uuibtg/slideover_for_windows/)


[Slide Over Apple](https://support.apple.com/pt-br/102576)
[Slide Over explained by Apple Support](https://support.apple.com/pt-br/guide/ipad/ipadfe7c65e9/ipados)
[Preme for Windows](http://www.premeforwindows.com/)
[SlidePad App Browser](https://slidepad.app/)
Repository: flutter
Issue: Make `ColorSwatch` not extend `Color`
Labels: c: proposal,P2,team-framework,triaged-framework

Today `ColorSwatch` extends `Color`.  It doesn't make any sense why since for all the behaviors it inherits it just responds to them with the primary color provided in the constructor.  The swatch is `const` so you can't change this.  This also creates a weird situation where you could have recursive `ColorSwatch`es.  I don't think there is a good reason for them to extend `Color`.  The only meaningful reason that it would be a `Color` is if we are doing runtime checks to check for `ColorSwatch` instead of incorporating the behavior in the `Color`'s interface, which would be brittle.
Repository: three.js
Issue: WebGLRenderTarget: Allow opt-in for output transforms / image formation
Labels: Suggestion

### Description

In recent three.js versions,`renderer.outputColorSpace`, `render.toneMapping`, and `renderer.toneMappingExposure` (jointly, the image formation step) are applied only when writing to the canvas drawing buffer (or WebXR) and disabled when writing to a render target. I think that's the right default. But it does constrain users' choices, and can force an additional (expensive!) pass in a post-processing stack. Based on feedback, this is problematic for mobile applications.

### Solution

I'd like to suggest that we add a new property to WebGLRenderTarget, perhaps called `target.needsOutputTransform`. If enabled, WebGLRenderer would apply ...

- renderer.toneMapping
- renderer.toneMappingExposure
- renderer.lookCDL (#28544)

when drawing to that render target. I believe `renderer.outputColorSpace` is not relevant here, since the render target already has a `.colorSpace` property.

### Alternatives

Alternatively, we could make WebGLRenderer always apply these settings when drawing to a render target, and require explicit changes to the renderer's properties by the user. I expect this would be a significant breaking change, however.

### Additional context

I don't know what this looks like in WebGPURenderer, or whether similar changes would be required there.

/cc @WestLangley
Repository: electron
Issue: [Bug]: Incorrect initial content bounds height on windows
Labels: platform/windows,bug :beetle:,has-repro-gist,31-x-y

### 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 bug report that matches the one I want to file, without success.

### Electron Version

31.2.1

### What operating system(s) are you using?

Windows

### Operating System Version

Windows 10 Home

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Calling getContentBounds on a BaseWindow should provide the correct height

### Actual Behavior

Calling getContentBounds on a newed BaseWindow provides the incorrect height (appears to be missing the menu size), if you wait half a second or more the correct height is reported, but no events (resize, etc) are emitted

### Testcase Gist URL

https://gist.github.com/LiamBest/00521c721d2b05e5412266aa89874a68

### Additional Information

Tried the gist provided on 31, 32 and 33. Same issue across all versions.
The bug is not present on mac, and appears to be related to the menu size (~26 px offset fixes it).
Repository: godot
Issue: TextEdit/LineEdit inconsistency when non-editable
Labels: discussion,topic:gui

### Tested versions

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

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Mobile) - dedicated AMD Radeon RX 6600 (Advanced Micro Devices, Inc.; 32.0.11029.1008) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

A TextEdit and LineEdit do not draw their StyleBoxes in the same way when `editable = false`. I would expect these to look visually more similar than they do.
![image](https://github.com/user-attachments/assets/749a9f49-0b7c-4d44-a205-9a525dc47532)


### Steps to reproduce

1. Create a TextEdit and a LineEdit next to each other.
2. Uncheck `editable` for both
3. Notice that the TextEdit is notably more solid-looking than the LineEdit

### Minimal reproduction project (MRP)

[mrp_textedit.zip](https://github.com/user-attachments/files/17022732/mrp_textedit.zip)
Repository: excalidraw
Issue: Excalidraw Plus: Presentation export in PDF or PPTX is set to 4:3 ratio, presentation frames are 16:9 default.
Labels: Excalidraw+

**App:** Excalidraw Plus on https://app.excalidraw.com, September 17th 2024

**Issue**: PDF and Powerpoint export of presentations downloads in an unexpected / unconfigurable ratio.

When using frames to develp a presentation, it looks like the default frame is approx. 16:9 ratio. This presents well on the equivalent screen when using presentation mode.

When exporting either a PDF or PPTX you are provide with a file in a 4:3 ratio meaning content layout has whitespace at header and footer.

This can be worked around in the PPTX with a resize but is baked in for the PDF without an editor.

May have missed it (newbie!) but there doesn't seem to be a way to configure the export for either the PDF or PPTX target.

Thanks for an awesome app!
Repository: vscode
Issue: Failing to persist Explorer folder expanded/collapsed state
Labels: bug,file-explorer,macos,confirmation-pending

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.93.1 (Universal)
- OS Version: macOS 14.6.1 (23G93)

Steps to Reproduce:

1. Launch `code .` on a project with some directories with very many files.

Unfortunately, VSCode insists on expanding every directory in the Explorer at launch. I often interact with projects with a large number of assets lexicographically earlier than implementation code in the project file tree.

This means that the less relevant files always appear in the Explorer, and I have to scroll down, down, down to get the relevant files. That's a frustratingly cumbersome workflow.

I can collapse the folder. But VSCode never persists the expanded vs collapsed state of Explorer folders. The state resets at every launch.

I've tried setting various VSCode settings recommended online, but none appear to have an effect. Honestly, the design is questionable. Most are limited to always-expand vs always-collapse logic, but that's not what I want.

I want every folder expanded by default, *unless* I have manually elected to collapse it, in which case, I want that remembered until the very day that I delete my project's VSCode cache.
Repository: pytorch
Issue: "bmm_sparse_cuda" not implemented for 'BFloat16'
Labels: module: sparse,triaged,module: bfloat16

### 🚀 The feature, motivation and pitch

When I am performing a sparse-dense matrix multiplication in BFloat16, I got this error message:
```
RuntimeError: "bmm_sparse_cuda" not implemented for 'BFloat16'
```

Would there be any supports of the half precision calculation for Sparse Tensors in the future?

### Alternatives

_No response_

### Additional context

_No response_

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip
Repository: PowerToys
Issue:  Please add a function that allows you to reprogram certain keys only for certain programs
Labels: Needs-Triage

### Description of the new feature / enhancement

In certain programs (for me, Siemens NX, for example), numbers must be entered with a period instead of a comma, regardless of the locale. It would be helpful here to only output the comma on the numeric keypad as a point in certain programs.

### Scenario when this would be used?

Using english Excel / Siemens Nx with german or other keyboard layout

### Supporting information

The Tool called Axel's Punkt can be found under 
https://psplm24.de/nx-downloads/dezimaltrennzeichen-in-nx-aendern/
The original link is dead.
[AxelsPunkt.zip](https://github.com/user-attachments/files/17023410/AxelsPunkt.zip)
Repository: godot
Issue: Particle velocity is not initialized to zero when new particles start
Labels: bug,needs testing,topic:particles

### Tested versions

- v4.2.2.stable.mono.official [15073afe3]
- v4.3.stable.mono.official [77dcf97d8]

### System information

Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4080 (NVIDIA; 32.0.15.5599) - AMD Ryzen 9 7950X3D 16-Core Processor (32 Threads)

### Issue description

Assume a very simple particle shader like this:

```glsl
shader_type particles;

void start() {
	TRANSFORM = mat4(vec4(1., 0.,0.,0.),vec4(0.,1.,0.,0.), vec4(0.,0.,1.,0.), vec4(float(INDEX),0.,0.,1.));
	VELOCITY = vec3(0,5,0);
}
```

This will make the particles line up in a row and fall down with 5 px per second. Now when I comment out the `VELOCITY` line, I would expect newly spawned particles to no longer fall down. However, newly spawned particles keep the velocity until I reload the scene.


https://github.com/user-attachments/assets/b4bde8ac-6373-4e87-bd9d-a8d60360884b

I would expect the particles to be initialized with a zero velocity on start.  This also affects visual shaders but I assume fixing the underlying issue will fix both text-based and visual shaders.

### Steps to reproduce

- Create a GPUParticles2D node.
- Create a particle shader script with the contents above.
- Repeat the steps from the video.


### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: Native crash in integration tests
Labels: bug,freeze-slow-crash-leak,linux,integration-test-failure

https://dev.azure.com/vscode/VSCode/_build/results?buildId=131793&view=logs&j=a8a6689c-5a84-59c0-482a-7dd9f21eb2d8&t=914c026e-c786-5738-7483-d51207ed28a1&l=3971

[crash-dump-linux-x64-integration-1.zip](https://github.com/user-attachments/files/17024161/crash-dump-linux-x64-integration-1.zip)
Repository: angular
Issue: `hostDirectives` should auto-resolve double matching
Labels: area: core,core: host directives

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

core

### Description

I have been using `hostDirectives` extensively for past several months and `NG0309: Directives can only match an element once.` error is the bane of my existence and a huge burden on Directive Composition API.

I have heard an argument from the Angular team that order of execution matters in case multiple directives have host binding to the same property. I don't believe this reasoning makes any sense when it comes to directives because it's literally impossible to maintain anyway and even if it was — it's a terrible practice to rely on `<div dirA dirB>` behaving differently than `<div dirB dirA>`.

Consider this situation:
All my `buttons` have a host directive that applies some visual rules — `appearance`.
All my `dropdown items` have the same host directive.

Now imagine I have an element, say a `sidebar item`, that can be both a `dropdown item` and a `button` and needs some code from both of those directives. If I add both `button` and `dropdown item` to host directives of `sidebar item` I get `appearance` double matched.

Collapsed sidebar shows items in dropdown:
![image](https://github.com/user-attachments/assets/1d5898e4-02af-41df-8172-10b01ceaa6fa)

Expanded sidebar shows them outside of dropdown as regular buttons:
![image](https://github.com/user-attachments/assets/0ac3c86f-62d5-4831-98ae-dca5327b85ff)

I tried to make this example as simple and transparent as possible to illustrate the issue, please do not take it at face value. In reality this cases are much more complex, but they boil down to this:

**We need to be able to declare host directives freely without having to worry about combining our directives further down the line and finding out some particular combinations cause errors due to nested host directives structure.**

There's an added complexity here because host directive declarations can expose different inputs/outputs, so the real discussion here should be how to handle those best. But the core idea that it shouldn't throw for multiple matches is absolutely clear, unless I'm missing something which I'm sure I'm not but if you have a good reasoning for it — please bring it up.

### Proposed solution

Once a directive is already matched on an element, ignore all subsequent matches like providers do when they are seen multiple times in `providers` arrays of multiple directives on the same element.

### Alternatives considered

None possible
Repository: PowerToys
Issue: Adding a sticky note inside a folder
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Some time I like to leave a message for myself regarding a folder documents which i dont use often, but are super valueable
I would love to have a sticky note thats not always active on my desktop

### Scenario when this would be used?

can be used to put up a reminder for to-do, notes, attention, 

### Supporting information

https://www.youtube.com/watch?v=qmSS9iv6wIQ