sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: Crash with 0x80000003
Labels: platform/windows,crash :boom:,bug :beetle:,blocked/need-repro,34-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

34.0.1

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

Windows

### Operating System Version

Windows 11 Professionnel

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

My app generated with electron dont crash, or crash with a more specific error message.

### Actual Behavior

My app generated with electron crash.

### Testcase Gist URL

_No response_

### Additional Information

This is the linked crash report : [677bf7cc-40e6-4a67-95ef-d8d0f8ee7cb5.dmp](https://github.com/user-attachments/files/18575807/677bf7cc-40e6-4a67-95ef-d8d0f8ee7cb5.dmp)

The bug is also in 34.0.0. I saw it in different computers. I saw it in dev mode, and also in production.

The crash seems to happen when the rendererProcess has one or more webRTC connexion, and we both spam channel activation/deactivation in both end. For example these channels can be micro or camera.

This is the line causing the bug : 

![Image](https://github.com/user-attachments/assets/03261bf9-6f8a-435e-b0e3-baf87f1c5b96)
Repository: rust
Issue: Tracking issue for release notes of #135439: Make `-O` mean `OptLevel::Aggressive`
Labels: T-compiler,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #135439.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Compiler
- [Make `-O` mean opt-level 3 instead of 2 to match Cargo's defaults](https://github.com/rust-lang/rust/pull/135439)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @clubby789 -- origin issue/PR authors and assignees for starting to draft text
Repository: vscode
Issue: Detects changes but values are not updated
Labels: bug

Testing #238896

Repro:

1. Open Powershell (v5) in VS Code 
2. Run `set SOMETHING=1`

This triggers the `onDidChangeTerminalShellIntegration` but the `env` field does not have the new `SOMETHING` variable in it.


```
> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.26100.2161
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.26100.2161
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

> set SOMETHING=1
```
Repository: rust
Issue: NaNs are quieted on Emscripten
Labels: T-compiler,C-bug,A-floating-point,A-ABI,needs-triage,I-miscompile,O-emscripten,E-needs-investigation

`tests/ui/abi/numbers-arithmetic/return-float.rs` currently fails under `wasm32-unknown-emscripten`:

```
---- [ui] tests/ui/abi/numbers-arithmetic/return-float.rs stdout ----

error: test run failed!
status: exit status: 101
command: cd "/home/purplesyringa/rust/build/x86_64-unknown-linux-gnu/test/ui/abi/numbers-arithmetic/return-float" && RUSTC="/home/purplesyringa/rust/build/x86_64-unknown-linux-gnu/stage1/bin/rustc" RUST_TEST_THREADS="8" "node" "/home/purplesyringa/rust/build/x86_64-unknown-linux-gnu/test/ui/abi/numbers-arithmetic/return-float/a.js"
stdout: none
--- stderr -------------------------------

thread 'main' panicked at /home/purplesyringa/rust/tests/ui/abi/numbers-arithmetic/return-float.rs:25:13:
assertion `left == right` failed
  left: 2144687445
 right: 2140493141
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
------------------------------------------
```

This reproduces on 66d6064f9eb888018775e08f84747ee6f39ba28e on Node v23.6.0. WASI is fine, and I think it uses Node during tests too, so probably not a Node bug.

@rustbot label +A-ABI +A-floating-point +I-miscompile +O-emscripten +T-compiler +E-needs-investigation
Repository: ui
Issue: [bug]: Incorrect Import Path for Utility Function in Sidebar Component
Labels: bug

### Describe the bug

In the `Sidebar` component, the import statement for the `cn` utility function is written as:  

```tsx
import { cn } from "@/components/lib/utils"
```  

However, the correct import path should be:  

```tsx
import { cn } from "@/lib/utils"
```  

This issue arises from an incorrect reference to the `utils` file location in the import statement. Updating the import path to the correct one will resolve this issue.

### Affected component/components

Sidebar

### How to reproduce

1. Go to https://ui.shadcn.com/docs/components/sidebar
2. Scroll down to Installation
3. Select "Manual"
4. See error

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash

```

### System Info

```bash
Browser
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: transformers
Issue: Mangled tokenization with Llama 3.1 for string sequences containing<space>'m
Labels: bug

We observed that trying to tokenize/detokenize strings containing the sequence `<space>'m` would not give back the initial string, but would "eat" the leading whitespace.

For example, the string "for 'manual'" will be transformed into "for'manual'"

Investigating further, we also observed issue with strings containing `<space>'s`, making us think the issue may be related to trying to handle sequences such as "I'm".

### System Info

transformers==4.46.2

### Who can help?

I guess it's for @ArthurZucker and @itazap 

### Information

- [ ] The official example scripts
- [x] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [x] My own task or dataset (give details below)

### Reproduction

Running:

```python
from transformers import AutoTokenizer

prompt = """for 'manual'"""

tokenizer = AutoTokenizer.from_pretrained("meta-llama/Meta-Llama-3.1-8B-Instruct")
tokenizer.batch_decode(tokenizer([prompt])["input_ids"], skip_special_tokens=True)[0]
```

prints

```
"for'manual'"
```

(missing whitespace before the leading ')

### Expected behavior

It should output the following

```
"for'manual'"
```
Repository: react
Issue: Why does DevTools need permission to write to the clipboard?
Labels: Component: Developer Tools

React DevTools is asking for permission to read the clipboard.

Why?

![Image](https://github.com/user-attachments/assets/026238d9-d6db-4aaf-8b1e-44e949409b99)
Repository: react
Issue: [React 19] HMR Bugs
Labels: React 19



### 1st issue: The error gets shown right before the HMR reloads (not updates) the page after changes are made.

![Image](https://github.com/user-attachments/assets/a1bc7ead-6c64-46f7-9ae0-fff59c06051f)

### 2nd issue: HMR reloads the page instead of updating trivial components (App).

**./package.json:**

```
{
  "name": "chat-contests",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {
    "dev": "npx webpack serve",
    "build": "npx webpack"
  },
  "author": "",
  "license": "ISC",
  "description": "",
  "devDependencies": {
    "@babel/core": "^7.26.0",
    "@babel/preset-env": "^7.26.0",
    "@babel/preset-react": "^7.26.3",
    "babel-loader": "^9.2.1",
    "css-loader": "^7.1.2",
    "html-webpack-plugin": "^5.6.3",
    "style-loader": "^4.0.0",
    "webpack": "^5.97.1",
    "webpack-cli": "^6.0.1",
    "webpack-dev-server": "^5.2.0"
  },
  "dependencies": {
    "@reduxjs/toolkit": "^2.5.0",
    "axios": "^1.7.9",
    "react": "^19.0.0",
    "react-dom": "^19.0.0",
    "react-redux": "^9.2.0"
  }
}
```

**./src/index.js**:

In the logs there's only the "HOT AVAILABLE" message. For some reason HMR doesn't accept my module.

```
import React from 'react';
import { createRoot } from 'react-dom/client';
import App from './App';

const app = createRoot(
    document.getElementById('app')
);

const render = () => app.render(<App />);

if (module.hot) {
    console.error('HOT AVAILABLE');
    
    module.hot.accept('./App', () => {
        console.error('HOT ACCEPTED');

        const NextApp = require('./App').default;
        
        console.error('HOT APP LOADED');
        
        app.render(<NextApp />);
    });
} else {
    console.error('NOT HOT');

    render();
}
```

**./src/App.js:**

```
import React from 'react';

const App = () => {
    return (
        <div>Hello World!!10!</div>
    );
};

export default App;
```

**./webpack.config.js:**

```
const path = require('path');
const HtmlWebpackPlugin = require('html-webpack-plugin');

module.exports = {
    mode: 'development',
    entry: './src/index.js',
    output: {
        path: path.resolve(__dirname, 'dist'),
        filename: 'bundle.[contenthash].js',
        clean: true
    },
    devServer: {
        static: {
            directory: './dist',
            publicPath: '/apps/chat-contests/dev'
        },
        port: 1010,
        hot: true,
        allowedHosts: 'all',
        client: {
            webSocketURL: {
                protocol: 'wss',
                port: 443,
                hostname: 'my-hostname.com',
                pathname: '/chat-contests-ws'
            }
        }
    },
    module: {
        rules: [{
            test: /\.jsx?$/,
            exclude: /node_modules/,
            use: 'babel-loader'
        }, {
            test: /\.css$/,
            use: [ 'style-loader', 'css-loader' ]
        }]
    },
    resolve: {
        extensions: [ '.js', '.jsx' ]
    },
    plugins: [
        new HtmlWebpackPlugin({
            template: './public/index.html'
        })
    ]
};
```
Repository: PowerToys
Issue: new+ takes over the "new folder" buttons...
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

New+

### Steps to reproduce

After activating New+, If I'm in a dialog box that offers a "New Folder" button,  or in Windows Explorer, clicking the "New folder" button now simply opens a new  Explorer window at the New+ template folder location.


### ✔️ Expected Behavior

I only expected this to affect the right click menu.

### ❌ Actual Behavior

If you click a "new folder" button in Explorer while New+ is running, instead of the standard windows action of creating a new folder in the current folder, a new Explorer window gets opened and the dialog box does nothing.

### Other Software

_No response_
Repository: kubernetes
Issue: [CLE] Add integration test for third party strategy
Labels: sig/api-machinery,triage/accepted

https://github.com/kubernetes/kubernetes/blob/master/test/integration/apiserver/coordinated_leader_election_test.go#L214-L222 only tests for OldestEmulationVersion. This strategy could be a third party strategy https://github.com/kubernetes/kubernetes/blob/master/pkg/controlplane/controller/leaderelection/leaderelection_controller_test.go#L316, we should add an integration test to ensure that this works.

/cc @henrywu573
/triage accepted
/sig api-machinery
/assign
Repository: vscode
Issue: replace `isFile`, `isDirectory` on proposed terminal completion provider with `kind`
Labels: bug,terminal-suggest

revert this hack

https://github.com/microsoft/vscode/pull/238900

cc @Tyriar
Repository: vscode
Issue: Trust dialog disappears when clicking links
Labels: feature-request,dialogs

Testing #238847

When I click on any link from the Trust dialog that opens the browser, the dialog is dismissed (assume Cancel). I then have to go to the Extensions View and click on Install again to bring up the dialog.  

I'm a little mixed on this behavior. I would prefer the dialog to stay open so that if I want to click on multiple links to learn more then I don't have to keep going back to the Extensions View and clicking Install again.  At the same time, I don't want a modal dialog.

Can we keep the same dialog but just not close it when going to the browser?
Repository: ui
Issue: [bug]: Cannot read properties of undefined (reading 'resolvedPaths')
Labels: bug

### Describe the bug

![Image](https://github.com/user-attachments/assets/b49f5f3e-d96a-4340-b633-fa458ab8695c)

### Affected component/components

Almost all components

### How to reproduce
Any npx shadcn@latest add causes this issue
```
Run the npx shadcn@latest add calendar
```

### System Info

```bash
Windows 11
```
Repository: vscode
Issue: Should the unverified link go to a different docs page?
Labels: info-needed

Testing #238847

When an extension is unverified, the link currently goes to a page meant for extension authors telling them how to become verified: https://code.visualstudio.com/api/working-with-extensions/publishing-extension#verify-a-publisher

However, the dialog is intended for end users, not publishers. Suggest that the unverified link goes here: 
https://code.visualstudio.com/docs/editor/extension-runtime-security#_determine-extension-reliability. This tells the user more about extension reliability including verified publishers.
Repository: TypeScript
Issue: Not possible to use const string as enum value
Labels: Duplicate

### 🔎 Search Terms

enum const string computed value 18033

### 🕗 Version & Regression Information

I tried 2 TS versions, reproducible with both:
- 5.6.2
- 5.7.3

### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/MYewdgzgLgBCAOUCW4BMMC8MDkDluwG4AoUSWPFMAZkx0vGuxgEMIYzoTiBTAD3ggATrB5gArgFsYAFR7QAohOkBvYjBgB5RFQCMdXDvC7sAGnVajYdFgbXTMAPSOYAHncwwIGDyFDh7AAWvjwW2vg0dHbUDs5uHlAQABS6ABwADNTUAJQ+fsIwwUKhAL5AA

### 💻 Code

```ts
const option2 = 'option2';
const option3 = 'option3' as const;

export enum TestEnum {
  Option1 = 'option1',
  Option2 = option2, // <<< no errors here
  Option3 = option3, // <<< ts(18033) error here
}
```


### 🙁 Actual behavior

Blocked by `ts(18033)` error

### 🙂 Expected behavior

No `ts(18033)` error

### Additional information about the issue

When string variable created `as const` it's impossible to use it as an enum value because of `ts(18033)` error.
As far as I'm aware this behaviour should've been implemented as part of this issue https://github.com/microsoft/TypeScript/issues/40793
Repository: godot
Issue: 4.4 Beta 1 - Animation Sub-Properties Create Wrong Key Type
Labels: bug,topic:editor,topic:animation

### Tested versions

4.4.beta1

### System information

Godot v4.4.beta1 - Windows 11 (build 22631) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Laptop GPU (NVIDIA; 31.0.15.4633) - AMD Ryzen 7 5800H with Radeon Graphics (16 threads)

### Issue description

I noticed that 4.4 Beta 1 introduced individual property selection for animations, which is great.
It's bugged however.
Picking the Y value for Position when adding a track still creates a Vector2 key.

![Image](https://github.com/user-attachments/assets/f1b0513a-3cfe-403e-a477-0d15d0fd7e44)

The key also shows up as a red X in the timeline when a value is assigned to it.

![Image](https://github.com/user-attachments/assets/acfc1b99-dddb-4639-81a1-1d5619f47f9d)

### Steps to reproduce

1 - Create an animation
2 - Add a track for a property like Position's Y

### Minimal reproduction project (MRP)

[AnimationBug.zip](https://github.com/user-attachments/files/18576945/AnimationBug.zip)
Repository: neovim
Issue: 'background' detection not working on Windows Terminal
Labels: platform:windows,tui,terminal,events

### Problem

`background` option is not set automatically on Windows Terminal.
As far as I investigated the `TermResponse` autocommand is not getting called with `OSC 11` events.

I have tried to log all `TermResponse` events:

```lua
vim.api.nvim_create_autocmd('TermResponse', {
  callback = function(args)
    print(vim.inspect(args))
  end
})
```

But apparently `OSC 11` is not being trigged, even if I run `:= io.stdout:write('\027]11;?\007')`.


### Steps to reproduce

- Select a light theme on Windows Terminal
- Run `nvim --clean`

### Expected behavior

`background` option should be set to `light` automatically when the terminal is using a `light` theme.

### Nvim version (nvim -v)

NVIM v0.11.0-dev-1417+g487c48ec86

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

no, VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Dec 22 2024 22:14:21)

### Operating system/version

Windows

### Terminal name/version

Windows Terminal 1.21.3231.0

### $TERM environment variable

empty

### Installation

chocolatey
Repository: vscode
Issue: How to reset or revoke Trusted Publishers?
Labels: feature-request,extensions

Testing #238847

Is there a way to reset or untrust an existing trusted publisher? I can't find any commands in the Command Palette...

The scenario is that I accidentally clicked on "Trust" or that I learned later that a publisher is not to be trusted, so I want the ability to revoke this trust.
Repository: rust
Issue: Lifetime generics on Generic Const Items should not affect if const is checked for evaluatability
Labels: C-bug,T-types,F-generic_const_items

> There's a difference between `const _: () = panic!();` and `const _<'a>: () = panic!();`: The former is a pre-mono error, the latter is a post-mono error.

This seems inconsistent, and pretty bad. But luckily something we can change before stabilizing generic consts :)

I think we should probably change the code introduced in https://github.com/rust-lang/rust/pull/121387 to instead call `requires_monomorphization` instead of `is_empty` on the generics.

It should also preferably check for impossible predicates in the same way we do for `-Clink-dead-code`/`-Zcollect-mono-items=eager`, since we must avoid monomorphizing consts with impossible (possibly trivial) preds. You could probably turn that into an ICE today.

_Originally posted by @compiler-errors in https://github.com/rust-lang/rust/pull/136168#pullrequestreview-2576994338_
Repository: vscode
Issue: Make the splitter/sash size configurable
Labels: feature-request,layout

<!-- ⚠️⚠️ 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. -->
The width for splitters and sash handles (for things like the left edge of the search box) is only 2px wide. I constantly find this hard to hover on and grab (big screen, sensitive mouse, old hands). Why not make it configurable? You _can_ configure a sash size like this:

```json
{
	"workbench.sash.size": 8
}
```

But it only takes effect once you've managed to hover over the splitter. I want to make the hover target bigger.
Repository: vscode
Issue: Filtering seems to give up after a lot of results
Labels: output

Testing #238846

Searching the pty host channel with trace logs for terminal, notice the overview ruler stops showing results and the filter stops working from then on:

<img width="1172" alt="Image" src="https://github.com/user-attachments/assets/1fc992eb-fb3f-4d79-b945-a5d35f6ee7fd" />

With Terminal highlighted, you can see more matches in the overview ruler:

<img width="1172" alt="Image" src="https://github.com/user-attachments/assets/0a022b8b-7fa1-46ef-a842-4ccc98733883" />
Repository: vscode
Issue: Filtering of output channels should run asynchronously and avoid locking up the renderer
Labels: output

Testing #238846

Filtering to a lot of content will lock up the renderer process. In a log with ~11000 lines it blocked the renderer for around 0.5s:

<img width="719" alt="Image" src="https://github.com/user-attachments/assets/24351126-45b5-47e4-bef0-b6ad21a14280" />

Can we do this processing async using something like this so the renderer doesn't lock up?

https://github.com/microsoft/vscode/blob/8081bc3f04fb46dcf8755937107ecfc31f6ed96e/src/vs/editor/browser/gpu/taskQueue.ts#L115-L135

Based on the numbers above I would guess an output channel of 110000 lines (which isn't unreasonable imo) would block the renderer for around 5 seconds.
Repository: kubernetes
Issue: Basing removed APIs on git tag always causes verify failures when the tag is changed to beta
Labels: sig/api-machinery,sig/testing,sig/release,triage/accepted

This follows up on https://github.com/kubernetes/kubernetes/issues/128616#issuecomment-2465832999.

Per @liggitt's comment

> the reason we fail on beta and not alpha is that master transitions to 1.$next.0-alpha.0 as soon as we make a release branch and rc.0 for the current minor

When we transition from `1.$x.0-alpha.0` to `1.$x.0-beta.0`, the alpha flag is changed and certain resource are [dropped](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/server/deleted_kinds.go#L139), causing an OpenAPI diff.

I have a sample PR to force the beta tag to see the OpenAPI diff: https://github.com/kubernetes/kubernetes/pull/129863#issuecomment-2619604117. 

At the moment, we can't preemptively remove these "removed" APIs from the OpenAPI as the tag as not transitioned to beta. So we have a chicken egg problem that bumping the tag will cause CI failures because of removed types and we cannot preemptively remove the types because the tag is not bumped. 

Can we rely on something other than the git tag alpha/beta/etc for determining what APIs to serve? Perhaps a constant in a file?

cc @aojea @BenTheElder @liggitt @deads2k
Repository: vscode
Issue: Editor GPU: Filtering in compound log shows stale content frequently
Labels: editor-gpu

Testing #238846

Playing around with the log categories and the filter text I hit this pretty easily:

<img width="744" alt="Image" src="https://github.com/user-attachments/assets/ca5b54ce-899e-4e95-a25c-85550d3fb160" />

<img width="744" alt="Image" src="https://github.com/user-attachments/assets/9d871377-9846-44ec-b9f3-975005e71c43" />

Output filtering just works in such a way that makes this bug happen often, the text at the bottom isn't actually there but it's still hanging around in the GPU buffer.
Repository: ant-design
Issue: Space.Compact Bug
Labels: unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-7cs4n9)

### Steps to reproduce

Use space.compact with input and button

### What is expected?

The button is the same height as the input

### What is actually happening?

the height of the button is less than the height of the input

| Environment | Info |
| --- | --- |
| antd | 5.23.3 |
| React | v19   Vite |
| System | Kubuntu 24.04.1 LTS |
| Browser | Google Chrome Version 132.0.6834.83 (Official Build) (64-bit) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->