sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Code are constantly freezes
Labels: bug,editor-edit-context


Type: <b>Bug</b>

When I'm trying to type in the code area itself and any popups (Auto complete, Copilot, code line information) will stop updating for a few seconds and is constantly happening. Scrolling will partially show the top and bottom of the area until all of it unfreezes again. This started happening with 1.95.2 I believe.

VS Code version: Code 1.95.3 (f1a4fb101478ce6ec82fe9627c43efbf9e98c813, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.26100
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 2600 Six-Core Processor             (12 x 3394)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.93GB (11.80GB free)|
|Process Argv|D:\\Joshs PC\\Games\\Servers\\Minecraft\\1.20.6 Paper - NeonCraftCity\\plugins\\Denizen\\scripts\\serverOther.dsc --crash-reporter-id 0ea9fbe9-16bc-407b-a35e-44a995b881ff|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (22)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-css-formatter|aes|1.0.2
vscode-m3u|af4|1.0.0
spellright|ban|3.0.140
denizenscript|den|1.4.7
copilot|Git|1.248.0
copilot-chat|Git|0.23.2024102903
vscode-autohotkey-plus-plus|mar|6.4.1
rainbow-csv|mec|3.13.0
vscode-html-format|moh|0.1.6
csharp|ms-|2.55.29
vscode-dotnet-runtime|ms-|2.2.3
debugpy|ms-|2024.12.0
python|ms-|2024.20.0
vscode-pylance|ms-|2024.12.1
remote-wsl|ms-|0.88.5
powershell|ms-|2024.4.0
vsliveshare|ms-|1.0.5941
indent-rainbow|ode|8.3.1
LiveServer|rit|5.7.9
HOCON|sab|0.0.1
vscode-gradle|vsc|3.16.4
volar|Vue|2.1.10


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530

```

</details>

<!-- generated by issue reporter -->
Repository: storybook
Issue: [Bug]: Svelte 5 decorator giving type error
Labels: bug,svelte

### Describe the bug

The decorator option gives a type error on the imported component:
`Svelte: Type Component<Props, {}, ''> has no properties in common with type SvelteStoryResult<Component<Props, {}, ''>>`

### Reproduction link

https://stackblitz.com/edit/github-h1zsrmcf?file=src%2Fstories%2FButton.stories.ts

### Reproduction steps

1. Go to the above link
2. Wait a bit for the scripts to run
3. Look at the error on line 18
### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22621
    CPU: (6) x64 Intel(R) Core(TM) i5-9600KF CPU @ 3.70GHz
  Binaries:
    Node: 22.11.0 - C:\Program Files\nodejs\node.EXE
    npm: 10.9.1 - ~\AppData\Roaming\npm\npm.CMD <----- active
  Browsers:
    Edge: Chromium (127.0.2651.74)
  npmPackages:
    @storybook/addon-a11y: ^8.4.7 => 8.4.7
    @storybook/addon-essentials: ^8.4.7 => 8.4.7
    @storybook/addon-interactions: ^8.4.7 => 8.4.7
    @storybook/addon-svelte-csf: ^5.0.0-next.13 => 5.0.0-next.13
    @storybook/blocks: ^8.4.7 => 8.4.7
    @storybook/svelte: ^8.4.7 => 8.4.7
    @storybook/sveltekit: ^8.4.7 => 8.4.7
    @storybook/test: ^8.4.7 => 8.4.7
    chromatic: ^11.20.0 => 11.20.0
    eslint-plugin-storybook: ^0.11.1 => 0.11.1
    storybook: ^8.4.7 => 8.4.7
```

### Additional context

_No response_
Repository: rust
Issue: Unsafe Loop when using mem::transmute & Unpreventable Due to a Macro
Labels: A-lints,T-compiler,S-needs-repro,S-needs-info

### Code

```Rust
#[macro_export]
macro_rules! vpr_as_m128i {
    ($n64:expr, $idx:expr) => {
        unsafe {
            std::mem::transmute::<u128, std::arch::x86_64::__m128i>($[$idx as usize])
        }
    }
}
```

### Current output

```Shell
// With 'Unsafe' Keyword
unnecessary `unsafe` block
`#[warn(unused_unsafe)]` on by default
Error originated from macro call here
because it's nested under this `unsafe` block
unnecessary `unsafe` block
unnecessary `unsafe` block
Error originated from macro call here
because it's nested under this `unsafe` block

// When Removing the 'Unsafe' Keyword
call to unsafe function `std::intrinsics::transmute` is unsafe and requires unsafe function or block
consult the function's documentation for information on how to avoid undefined behavior.
```

### Desired output

```Shell
No warning when adding unsafe since transmuting memory goes out of the bounds of the borrow checker.
```

### Rationale and extra context

The problem occurs when using a macro, normally the issue could be avoided by using the recommended `#[warn(unused_unsafe)]` procedural macro. However, when adding the attribute, it specifies issue https://github.com/rust-lang/rust/issues/15701:

```
attributes on expressions are experimental
see issue #15701 <https://github.com/rust-lang/rust/issues/15701> for more informationrustc[Click](rust-analyzer-diagnostics-view:/diagnostic message [1]?1#file:///home/will/Documents/Projects/p64/p64-core/src/rsp.rs)
```

The proposed fix is either to recognise that `mem::transmute` requires unsafe due to the borrow checker's absence or allow the `#[warn(unused_unsafe)]` procedural macro to be allowed to be specified with macros. I would prefer the former over the latter.

### Other cases

```Rust

```

### Rust Version

```Shell
$ rustc --version --verbose
rustc 1.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-unknown-linux-gnu
release: 1.82.0
LLVM version: 19.1.1
```

### Anything else?

_No response_
Repository: vscode
Issue: Bring detached tabs into focus when any other window from that project comes into focus.
Labels: feature-request,workbench-auxwindow

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

When clicking the window, or taskbar of a detached window (tabs dragged or moved to another screen) that are part of an active project, bring all other linked windows to front.

We already open and close detached windows together with the main window, and when opening, they open and all come to the front.
I just am asking for this to be the case with all types of project interaction on different windows.

I program my unity games on 4 screens, and I would love to not have to click on all 4 taskbar tabs to bring each detached window up 500 times a day.
Repository: neovim
Issue: `executable()` is slow on WSL
Labels: bug,performance,defaults,platform:wsl

### Problem

Neovim's `vim._defaults.lua` executes a call to `executable()` to check for the presence of `rg` and sets it as `'grepprg'`. When `rg` is not found, this process is slow and introduces unnecessary overhead during startup. Users do not expect such a heavy check in the default configuration.

This `executable()` check can cause a delay of 50–200 milli seconds, further exacerbating the performance issue. 

### Steps to reproduce

Uninstall ripgrep.
Install Neovim.
Start Neovim with nvim --clean --startuptime foo.txt.

Observe the execution delay caused by the executable check in `vim._defaults.lua`.
For example, try to delete below lines.

```
--- Default options
do
  --- Default 'grepprg' to ripgrep if available.
  if vim.fn.executable('rg') == 1 then
    -- Use -uu to make ripgrep not check ignore files/skip dot-files
    vim.o.grepprg = 'rg --vimgrep -uu '
    vim.o.grepformat = '%f:%l:%c:%m'
  end
end
```

### Expected behavior

Neovim should avoid calling executable to check for the presence of `rg` during startup. When `rg` is not found, the `executable()` check triggers an exhaustive path search, which significantly increases the startup time. Removing this check entirely would lead to improved performance, as users can configure `'grepprg'` manually if needed.

The performance cost of `executable()` is a well-known problem, and calling it during startup should be avoided unless absolutely necessary.

### Nvim version (nvim -v)

v0.11.0-dev-b1c907f

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

no

### Operating system/version

Ubuntu 24.04.1 LTS

### Terminal name/version

WezTerm

### $TERM environment variable

xterm-256color

### Installation

build from repo
Repository: create-react-app
Issue: Is there anyway to improve create-react-app performance? 
Labels: needs triage

Lately, the performance of my React application has been really slow. I want to use Vite.js to improve the performance, but I don't like having additional files. Is there a way to improve the performance of a Create React App project without switching
Repository: pytorch
Issue: Proposal for Official Cross-Platform Support for 3D Gaussian Splatting
Labels: module: nn,triaged,needs research

### 🚀 The feature, motivation and pitch

3D Gaussian Splatting is widely applied in the fields of computer vision and computer graphics due to its efficiency and flexibility. However, the currently popular implementations primarily rely on NVIDIA’s CUDA, which limits their usability on other platforms, such as MacBooks with Apple Silicon. To make this technique more accessible and platform-agnostic, we suggest implementing an official PyTorch-based 3D Gaussian Splatting (3DGS) framework. By leveraging PyTorch’s backend, this implementation could support multiple hardware platforms, including CUDA for NVIDIA GPUs, Metal for MacBooks, and potentially other accelerators, thereby broadening its applicability across diverse systems and user bases.

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: react
Issue: Bug:  React class is too slower then react hooks
Labels: Status: Unconfirmed

React version:18.2.66

## Steps To Reproduce
I write this code to test react hooks and react class for test performance, but i find react class is too slower then react hooks.
```tsx
export let TestHook = () => {
    const _this = useRef({} as any).current;
    if (!_this.inited) {
        _this.states = new Array(50000);
        _this.inited = true;
    }
    for (let i = 0; i < 50000; i++) {
        _this.states[i] = (useState(i));
    }

    let updateState = () => {
        _this.states.forEach(([state, setState]: any) => {
            setState(state + 1);
        });
    }
    useEffect(() => {
        const intervalId = setInterval(updateState, 100);
        return () => clearInterval(intervalId);
    }, []);

    return (
        <div className={style.hook}>
            {_this.states.map(([state]: any) => (
                <span >{state}</span>
            ))}
        </div>
    );
};
```

```tsx
export class TestClass extends Component<any, any> {
    state: any = {}
    constructor(prop: any) {
        super(prop);
        for (let i = 0; i < 50000; i++) {
            this.state[i] = i;
        }
    }
    componentDidMount() {
        setInterval(() => {
            let s = this.state;
            for (let k in s) {
                this.setState({ [k]: s[k] + 1 });
            }
        }, 100)
    }
    render() {
        return (
            <div className={style.class}>
                {Object.keys(this.state).map((k) => (
                    <span>{this.state[k]}</span>
                ))}
            </div>
        )
    }
}
```
Repository: PowerToys
Issue: Key mapping issue
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.86.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Whatever keys I have mapped don't work until the PowerToys are in focus. It means when I'm in the PowerToys app, then only keys work properly. If I close it, then the keys don't work.

### ✔️ Expected Behavior

The keys should work properly without even opening the apps. And anywhere they should work. 

### ❌ Actual Behavior

Key mapping only works if I open PowerToys, and inside the app only it works, not even outside it's working.

### Other Software

_No response_
Repository: yt-dlp
Issue: Support --audio-format m4b
Labels: enhancement,triage

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm requesting a feature unrelated to a specific site
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Provide a description that is worded well enough to be understood

This is exactly the same thing as `m4a`, so no major changes are required. The only reason why it would be useful is so that `%(ext)s` will result in a proper file extension.

`m4b` usually serves only informative purpose, as it implies an audio book with chapters (which `yt-dlp` already handles perfectly well for this use case), and `m4a` could be whatever. 

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: godot
Issue: RichTextLabel (RTL): Adding text with add_text() does not update the .text property
Labels: discussion,documentation,topic:gui

### Tested versions

v4.4.dev5.official [9e6098432]
v4.4.dev6.official [1f47e4c4e]

### System information

Godot v4.4.dev5 - Windows 10 NVIDIA GeForce RTX 4060 Ti

### Issue description

Text added with add_text() is not added to the .text property of the RichRextLabel.

### Steps to reproduce

1. Create an RTL instance.
2. Use the add_text() function of it.
3. Check what is inside the .text property.




### Minimal reproduction project (MRP)

```
extends Control

func _ready() -> void:
	var rtl : RichTextLabel = RichTextLabel.new()

	rtl.text = 'Hello World'
	print(rtl.text) # output is "Hello World"

	rtl.add_text('I want to add this text but it does not work!')

	print(rtl.text) # output is still "Hello World"

```
Repository: PowerToys
Issue: 창 이동
Labels: Issue-Bug,FancyZones-Dragging&UI,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

Microsoft Store

### Running as admin

None

### Area(s) with issue?

FancyZones

### Steps to reproduce

주식차트창에서 일부 차트만 따로 빼서 지정레이아웃으로 옮길때 쉬프트키를 누르고 마우스커서로 이동을 해도 레이아웃 지정칸영역이 활성화가 안됩니다. 스샷은 첨부가 어렵고 자세한 내용은 위의 설명 그대로입니다.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: go
Issue: go/parser: (*ast.File).Decls is empty after bailout
Labels: NeedsDecision

Currently when `parser.ParseFile` is executed without `parser.AllErrors` the parsing is stopped, but the `(*ast.File).Decls` field is not populated with the parsed (valid and invalid) declarations:

Reproducer:

```go
func TestEarlyBailout(t *testing.T) {
	const src = `package test
func test() {
	validCode()
}

func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
func parseError() { var a }
`

	fset := token.NewFileSet()
	f, _ := ParseFile(fset, "test.go", src, SkipObjectResolution)
	if len(f.Decls) == 0 {
		t.Fatal("no decls found") // fails
	}
}
```

I think that we should return at least a partial AST in this case, or we should document this behavior.

CC @adonovan @griesemer
Repository: go
Issue: go/parser: scanner errors do not cause a bailout
Labels: NeedsInvestigation

While investigating #70725, i noticed that, errors from the scanner are passed directly to `p.errors`:

https://github.com/golang/go/blob/8c3e391573403cf1cf85b3256e99d0c0b7d79b3a/src/go/parser/parser.go#L69-L71

Per the docs i would assume that the parsing should stop after 10 error (including scanner errors):

https://github.com/golang/go/blob/8c3e391573403cf1cf85b3256e99d0c0b7d79b3a/src/go/parser/interface.go#L57

It should probably call the `p.errors` instead: 

https://github.com/golang/go/blob/8c3e391573403cf1cf85b3256e99d0c0b7d79b3a/src/go/parser/parser.go#L260-L281

CC @griesemer @adonovan
Repository: PowerToys
Issue: PowerToys Run doesn't reindex unless closed and reopened
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

I'm using Windows 11 latest version and PowerToys latest version. I forgot how I installed PowerToys and if it's running as admin or not, it's been very long ago and those details aren't relevant to the question anyway.

Steps to reproduce:

1. download and install [beekeeper studio latest version from github](https://github.com/beekeeper-studio/beekeeper-studio/releases/tag/v4.6.8)
2. Try to run beekeeper studio via PowerToys run, Powertoys won't find beekeeper
3. Restart your PC, or shut down and boot the PC again, the issue will presist
4. If you quit PowerToys and start it again, only then the issue would be fixed.

It would be nice to have a button called re-index so that you show the user what's being indexed and allow him to perform the action.
Repository: PowerToys
Issue: 双屏下，键盘管理器中重新映射键盘键失效
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Under dual displays, remapping keyboard keys in the keyboard manager is ineffective and no longer works.There is no problem with a single display screen.I am using an external wired monitor

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: PowerToys
Issue: Left ctrl <-> alt keys remapping interferes with getting Polish-specific letters
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.86

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Switch LEFT CTRL with LEFT ALT and vice versa

### ✔️ Expected Behavior

LEFT ALT key used with C, V, X etc. will work as LEFT CTRL before change. LEFT CTRL key will work (among the other things) as a modifier to get polish keys on my keyboard. RIGHT ALT & RIGHT CTRL function will not change.

### ❌ Actual Behavior

After remapping neither LEFT CTRL nor RIGHT ALT work as modifiers to achieve polish letters (ą, ł, ż etc.), so wnen I press RIGHT ALT + A or LEFT CTRL + A I should get "ą" and I get "a"

### Other Software

_No response_
Repository: next.js
Issue: `The Next.js plugin was not detected` reporting when using flat config
Labels: Linting,linear: next

### Link to the code that reproduces this issue

https://github.com/mrskiro/next-cannot-find-plugin-in-flat

### To Reproduce

1. npm install
2. npm run lint

### Current vs. Expected behavior

When running next lint, it retrieves the ESLint configuration file and checks whether the Next.js plugin is being used.

https://github.com/vercel/next.js/blob/f348241e25767e1e08909de19cdab032d63e369b/packages/next/src/lib/eslint/runLintCheck.ts#L203-L214

At this step, the [calculateConfigForFile](https://eslint.org/docs/latest/integrate/nodejs-api#-eslintcalculateconfigforfilefilepath) API is called with the path to the configuration file. However, the result of this API reflects the linting configuration for the specified file path. For example, if the configuration file is a `.mjs` file, and the `@next/next` plugin does not include .mjs in its files property, the warning
`The Next.js plugin was not detected in your ESLint configuration. See https://nextjs.org/docs/app/api-reference/config/eslint#migrating-existing-config`
will be reported.

I followed the instructions in the comment below to configure flat config. In my project, `.mjs` files are used only for configuration purposes, so I have not included .mjs in the files property of `@next/next`.
https://github.com/vercel/next.js/issues/71763#issuecomment-2476838298

### Provide environment information

```bash
npx next info                         

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Nov 14 18:19:02 PST 2024; root:xnu-11215.41.3~13/RELEASE_ARM64_T8132
  Available memory (MB): 24576
  Available CPU cores: 10
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: 1.22.22
  pnpm: 9.14.4
Relevant Packages:
  next: 15.0.4-canary.47 // Latest available version is detected (15.0.4-canary.47).
  eslint-config-next: 15.0.4
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Linting

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

Other (Deployed)

### Additional context

1. make `@next/eslint-plugin-next` also provide `files` and include config file extension
2. search for files that must be present in nextjs (probably more complicated)
3. Stop using eslint.calculateConfigForFile and search from `fs` etc.

Will gladly submit a PR. I look forward to your opinion!
Repository: godot
Issue: UV Map corruption on GLB import
Labels: bug,topic:import

### Tested versions

Godot 4.3


### System information

Forward+, Windows 10, I3 4190

### Issue description

When importing GLB models into Godot, textures seem stretched or corrupted.

Model in Blender(imported GLB)
![Image](https://github.com/user-attachments/assets/62092cac-6c9a-4aff-97e9-32fb554169c1)

Model in Godot Editor
![Image](https://github.com/user-attachments/assets/22ab68bb-f045-4f94-85f3-47220bdd0865)

btw materials aren`t corrupted:
![Image](https://github.com/user-attachments/assets/7359a797-58d5-42aa-a60b-6d384f5e43af)
![Image](https://github.com/user-attachments/assets/6df8bb12-d52f-4685-9740-e63e3c232da5)
![Image](https://github.com/user-attachments/assets/5acfb1f2-d928-4201-9431-dbd504aa2650)


### Steps to reproduce

Import model into the editor and see corruption of UV

[axe.zip](https://github.com/user-attachments/files/18052186/axe.zip)


### Minimal reproduction project (MRP)

N/A