sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: Documentation of toast component for manual installation is wrong
Labels: bug

### Describe the bug

If you go to the official documentation: https://ui.shadcn.com/docs/components/toast

And select manual installation, the three snippets of code that you are supposed to copy and paste into your project are the same one. I guess it was a mistake when creating the page.

Could you please fix this and put the correct code for every file?

Thanks

### Affected component/components

Toast

### How to reproduce

If you go to the official documentation: https://ui.shadcn.com/docs/components/toast

And select manual installation, the three snippets of code that you are supposed to copy and paste into your project are the same one. I guess it was a mistake when creating the page.


### Codesandbox/StackBlitz link

_No response_

### Logs

```bash

```

### System Info

```bash
All machines, since it is the official website :)
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: ollama
Issue: deepseek-r1 `qwen` variants use a new pre-tokenizer, which is not implemented in the llama.cpp version used
Labels: bug

### What is the issue?

The newly supported `deepseek-r1` model variants that have `distill-qwen` in the name use a new pre-tokenizer. Support for this has been added to the latest llama.cpp (not sure if the release version or just the latest commit on the main branch). 

The backend llama.cpp that Ollama uses should be updated to support this, since the `default` pre-tokenizer is very different than the bespoke version. 

### OS

Linux, macOS, Windows, Docker, WSL2

### GPU

_No response_

### CPU

_No response_

### Ollama version

0.5.7
Repository: pytorch
Issue: torch.backends.cudnn.flags use error when test
Labels: module: cudnn,module: convolution,triaged

### 🐛 Describe the bug

https://github.com/pytorch/pytorch/blob/main/test/nn/test_convolution.py#L3311

There is a problem with the use of cudnn.flags() here. The original purpose was to test the accuracy of allow_tf32 when it was turned on and off, but the call to cudnn.flags() causes allow_tf32 to always be True.

```python
    @onlyCUDA
    @tf32_on_and_off(0.005)
    def test_ConvTranspose2d_size_1_kernel(self, device):
        x_cpu = torch.randn(2, 3, 5, 5)
        conv_cpu = torch.nn.ConvTranspose2d(3, 3, kernel_size=1)
        y_cpu = conv_cpu(x_cpu)
        y = torch.rand_like(y_cpu)
        y_cpu.backward(y)

        with cudnn.flags(enabled=False):
            conv_cuda = torch.nn.ConvTranspose2d(3, 3, kernel_size=1).to(device)
            conv_cuda.bias.data.copy_(conv_cpu.bias.data)
            conv_cuda.weight.data.copy_(conv_cpu.weight.data)
            y_cuda = conv_cuda(x_cpu.to(device))
            y_cuda.backward(y.to(device))

        self.assertEqual(y_cpu, y_cuda, atol=1e-5, rtol=0, exact_device=False)

```

### Versions

Regardless of the environment

cc @csarofeen @ptrblck @xwang233 @eqy
Repository: ui
Issue: [bug]: Checkbox
Labels: bug

### Describe the bug

When using the [Tasks demo page](https://ui.shadcn.com/examples/tasks) with Firefox 134.0.2 on Windows 11, the checkbox move when you click on it.

See the video below:

https://github.com/user-attachments/assets/704cd821-0be9-4322-b2cf-35ce163a2ce7

The problem only reproduces on Firefox.


### Affected component/components

Checkbox

### How to reproduce

1. Go to [Tasks demo page](https://ui.shadcn.com/examples/tasks)
2. Click on any checkbox on the first column
3. Observe the checkbox moving up and down

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash

```

### System Info

```bash
Firefox 134.0.2 on Windows 11
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: storybook
Issue: [Bug]: can't get scss to load despite storybook does not crash
Labels: bug,needs triage

### Describe the bug

I can't get the storybook to show scss styling, I've tried everything (with and without @storybook/preset-scss), but it still doesn't show styling coming from scss files - it does work with inline styling. 

Storybook doesn't complain. Most webpackFinal config options without @storybook/preset-scss resulted with a storybook error, complaining about scss characters.

I have a react app, with webpack5, using scss&css.


```
"@storybook/addon-essentials": "^8.5.0",
"@storybook/addon-interactions": "^8.5.0",
"@storybook/addon-onboarding": "^8.5.0",
"@storybook/addon-webpack5-compiler-swc": "^2.0.0",
"@storybook/blocks": "^8.5.0",
"@storybook/preset-scss": "^1.0.3",
"@storybook/react": "^8.5.0",
"@storybook/react-webpack5": "^8.5.0",
    
"style-loader": "4.0.0",
"sass": "^1.81.0",
"sass-loader": "^16.0.4",
"css-loader": "6.11.0",
```

main.ts
```
const config: StorybookConfig = {
  addons: [
    '@storybook/addon-webpack5-compiler-swc',
    '@storybook/addon-onboarding',
    '@storybook/addon-essentials',
    '@chromatic-com/storybook',
    '@storybook/addon-interactions',
    '@storybook/preset-scss',
  ],
  core: {
    builder: 'webpack5',
  },
  framework: {
    name: '@storybook/react-webpack5',
    options: {},
  },
  stories: [
    '../src/**/*.mdx',
    '../src/**/*.stories.@(js|jsx|mjs|ts|tsx)',
    '../src/browser/storybook-utils/**/*.stories.@(js|jsx|mjs|ts|tsx)',
  ],
  webpackFinal: async (config) => {
    config.module.rules.push({
      test: /\.scss$/,
      use: [
        'style-loader',
        {
          loader: 'css-loader',
          options: {
            importLoaders: 1, // Ensure sass-loader runs before css-loader
          },
        },
        'sass-loader',
      ],
      include: path.resolve(path.dirname(import.meta.url), '../'),
    });

    if (config.resolve) {
      config.resolve.plugins = [
        ...(config.resolve.plugins || []),
        new TsconfigPathsPlugin({
          extensions: config.resolve.extensions,
        }),
      ];
    }
    return config;
  },
};
export default config;
```

```
import './ModalContainerHeader.scss';

...

<div className="ModalContainerHeader">
      <div className="testOne" style={{ color: 'red' }}>
        Test
      </div>
      <div className="testTwo">Test</div>
    </div>
```

```
.ModalContainerHeader {
  .testTwo {
    color: red;
  }
```

<img width="122" alt="Image" src="https://github.com/user-attachments/assets/36977036-52ed-4086-861b-f7462750fd32" />

<img width="408" alt="Image" src="https://github.com/user-attachments/assets/1f1b3d4c-3a55-49f1-9521-14adb084b481" />

any ideas what to do?

### Reproduction link

can't share sorry

### Reproduction steps

_No response_

### System

```bash
worked ok
```

### Additional context

_No response_
Repository: neovim
Issue: gF should recognize more file/line/column patterns and seek to column
Labels: jumps-navigation,editor

### Problem

Right now the [gF](https://neovim.io/doc/user/editing.html#gF) feature seems to only support a limited set of patterns. In particular, it doesn't seem to work with python's backtrace format:

```
Traceback (most recent call last):
  File "/path/to/file.py", line 123, in <module>
```

It also seems to completely ignore column info since gF on `file:123:12:` (eg as emitted by modern gcc and clang) seeks to the 123rd line but not the 12th column.

One of the things I miss most from vscode is that I can run a command in the terminal and just cmd-click in the output when it is referring to a file and go right where I need to go. 

### Expected behavior

The vscode terminal's logic to detect file/line/column seems to work fairly well in practice, so it may be a good source of inspiration. It looks like [this](https://github.com/microsoft/vscode/blob/ce2c2f3c79a32b9917e32c61e058392dc5a1b6aa/src/vs/workbench/contrib/terminalContrib/links/browser/terminalLinkParsing.ts#L64-L126) is list of 3 regexes that they use, along with examples patterns that they are trying to match.

Once you have the parser able to recognize columns, it would be nice if `gF` automatically went to the right column as well.

Maybe this should be a new ticket, but it would be really nice if the built-in `:terminal` was automatically enhanced to recognize these patterns and A) apply a highlight group, possibly only when the cursor or mouse is over one (bonus points if the highlight group was only applied when the file exists!), and B) consider a default mapping on `<LeftMouse>` or `<C-LeftMouse>` to go to the file.

Another nice feature would be something to send the matching locations to the quickfix list. I have tried `:cgetbuffer` from the terminal and it does not work well, at least with the default `errorformat`. Among other issues, I wasn't able to make one that would match file:line:column in the middle of a line and not treat anything before the file as part of the message rather than the file. It would be especially cool if there was support for only sending the output from the last command to quickfix using OSC codes from the prompt to delimit command boundaries (at least kitty and vscode support the [OSC 133](https://gitlab.freedesktop.org/Per_Bothner/specifications/blob/master/proposals/semantic-prompts.md) A/B/C/D sequence for this which is also useful for #9209). This would let you run your build in a terminal and still get all the niceties like live progress reporting and colorful output, while still being able to use the quickfix list as if you used `:make`
Repository: material-ui
Issue: [docs] Tabs need two clicks to work on Firefox
Labels: docs,component: tabs,status: waiting for author,support: docs-feedback

### Related page

https://mui.com/material-ui/react-tabs/

### Kind of issue

Broken demo

### Issue description

For some examples It needs to click twice to change the tab. That's happening to the firefox browser in chromium based browsers looks fine. 

### Context

Open the tabs demo documentation in Firefox. I'm on macOS. Going to click to change the tabs, and I'm doing a click on a different tab and looks like clicked, does an effect, stays to the current tab, click again, going to the tab that I clicked. After refresh, it worked, but I cannot consider a cache issue since it was the first time that I visited the page from this browser. 

**Search keywords**: tabs, double click
Repository: vscode
Issue: HTML can't wite any more code Visual Studio Code
Labels: info-needed


Type: <b>Bug</b>

I have issue with Visual Studio Code. All of a sudden , i can't write code anymore. let me explain: when i try to mwrite code, it keeps inserting closing tag and i can no longer open any tags. The closing tags appear for all tags like DIV, MAIN, BODY. However ,i've checked my code many times, and it's perfectly fine. I also tried with other project , and i'm experiencing the same problem. I need to solve this issue because i work with VSC. Thank You!

VS Code version: Code 1.96.2 (Universal) (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Darwin arm64 23.6.0
Modes:

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

|Item|Value|
|---|---|
|CPUs|Apple M3 (8 x 2400)|
|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>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|5, 12, 7|
|Memory (System)|16.00GB (3.14GB free)|
|Process Argv|--crash-reporter-id 8d604037-1790-40a6-96c0-15e093dc2ea9|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
newcmakeconfigv2:31071590
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730

```

</details>

<!-- generated by issue reporter -->
Repository: ant-design
Issue: AutoComplete customize input size
Labels: improvement

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/customize-input-component-antd-5-23-2-forked-grw9hy?file=%2Fdemo.tsx)

### Steps to reproduce

Switch between small, middle and large

### What is expected?

AutoComplete wrapper should size to custom Input's height

### What is actually happening?

* When size prop is set only on the custom Input, AutoComplete wrapper itself keeps fixed height. 
* When size prop is set on both Input and AutoComplete,then it works almost as it should, except at large size AutoComplete height is larger the Input's, also it shows the warning in console: Warning: [antd: AutoComplete] You need to control style self instead of setting `size` when using customize input. 

| Environment | Info |
| --- | --- |
| antd | 5.23.2 |
| React | 18 |
| System | Windows |
| Browser | Firefox |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: storybook
Issue: [Bug]: “The current testing environment is not configured to support act” errors when changing between component docs pages
Labels: bug,react,needs triage,upgrade:8.5

### Describe the bug

When switching between component docs pages you get bunch of
```
The current testing environment is not configured to support act(...)
```
and occasionally
```
An update to ZoomElement inside a test was not wrapped in act(...).
```
errors in browser console.

### Reproduction link

https://stackblitz.com/edit/github-qczcaoih?file=package.json&preset=node

### Reproduction steps

1. Navigate to Button docs page
2. While on Button docs page, navigate to Header or Page docs page.
3. Check browser console for errors.



### System

```bash
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.6.0-alpha.1 => 8.6.0-alpha.1 
    @storybook/addon-interactions: ^8.6.0-alpha.1 => 8.6.0-alpha.1 
    @storybook/addon-onboarding: ^8.6.0-alpha.1 => 8.6.0-alpha.1 
    @storybook/addon-webpack5-compiler-swc: ^2.0.0 => 2.0.0 
    @storybook/blocks: ^8.6.0-alpha.1 => 8.6.0-alpha.1 
    @storybook/react: ^8.6.0-alpha.1 => 8.6.0-alpha.1 
    @storybook/react-webpack5: ^8.6.0-alpha.1 => 8.6.0-alpha.1 
    @storybook/test: ^8.6.0-alpha.1 => 8.6.0-alpha.1 
    storybook: ^8.6.0-alpha.1 => 8.6.0-alpha.1
```

### Additional context

React version: 19
Brower: Chrome, Firefox
Repository: rust
Issue: compiletest: investigate if it's possible to do run-time capability detection against *target*
Labels: E-hard,C-enhancement,A-cross,T-compiler,T-bootstrap,A-compiletest,E-needs-design

Some tests are conditioned on *capabilities*, which are most accurately detected at run-time *against* the **target** under cross-compilation scenarios (compared to having to maintain allowlists or denylists of targets). However, implementing this is non-trivial:

- You have to build *and* run the capability run-time test as an executable on the **target**, *not* the **host**. This may involve having to work with custom test runners (e.g. `wasmtime`) or remote-test-server.
- The *target* may not support std!
Repository: flutter
Issue: [ Web ] Flutter web Autofill doesn't work when browser password manager is protected with Windows Hello
Labels: a: text input,platform-windows,platform-web,has reproducible steps,browser: chrome-desktop,team-web,fyi-text-input,found in release: 3.27,found in release: 3.28

### Steps to reproduce

- Create a basic login form with a login and password fields, with autofill
- Activate Windows Hello protection on browser (in Chrome : password manager -> settings -> Activate Windows Hello)
- First run on browser -> save credentials
- Restart your web app
- Use this second run to use the saved credentials, with autofill

### Expected results

The selected credentials should fill the login/password form fields

### Actual results

- [x] if the browser uses its own password manager directly, the autofill works perfectly (tested with Chrome, Mozilla Firefox)
- [ ] if the browser uses Windows Hello to protect the password manager, the fields are not filled after Windows validation (tested only with Chrome, because I didnt success to make Mozilla Firefox ask for Windows Hello confirmation)

### Code sample

<details open><summary>Code sample</summary>

```dart
      Form(
        child: AutofillGroup(
          child: Column(
            mainAxisSize: MainAxisSize.min,
            children: [
              //...
              TextField(
                  autofillHints: const [AutofillHints.username],
                  controller: loginCtrl,
              ),
              TextField(
                  autofillHints: const [AutofillHints.password],
                  obscureText: true,
                  controller: pwdCtrl,
              ),
```

</details>
Repository: kubernetes
Issue: Pass ctx to the remaining WaitForXXX methods in test/integration/util/util.go
Labels: sig/scheduling,kind/feature,needs-triage

### What would you like to be added?

Pass ctx to the remaining WaitForXXX methods in test/integration/util/util.go

### Why is this needed?

We should use existing test context consistently.
Repository: react
Issue: Bug: onChange Not Triggering for range input After Dynamic Updates
Labels: Status: Unconfirmed

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

## Description

When using range input in React, the onChange event does not trigger properly under certain dynamic updates to its step and max attributes. Specifically, if the step and max values are updated dynamically, and the range input value is reset to 0, subsequent user interactions with the range slider fail to trigger the onChange event as expected. This behavior does not occur in a pure JavaScript implementation.

**React version:** 19.0.0  

## Steps To Reproduce  

1. Open the StackBlitz example: [React example](https://stackblitz.com/edit/vitejs-vite-srhuep2z?file=src%2FApp.jsx)  
2. Click the middle of the range input, changing its value to `500`.  
3. Click the **"Change to step 0.5 max 1"** button, observe that the range input is set to `0` (expected behavior).  
4. Click the **"Change to step 500 max 1000"** button, observe that the range input is set back to `0`. Then click the middle of the range input.  

## The current behavior  

After completing step 4, the value of the range input remains at 0, even though the user clicks on the middle of the range slider. The onChange event is not triggered, and the value does not update.

## The expected behavior  

After completing step 4, the value of the range input should update to 500 when the user clicks on the middle of the range slider. The onChange event should be triggered correctly, reflecting the value change.

## Link to code example  

- [React implementation reproducing the issue](https://stackblitz.com/edit/vitejs-vite-srhuep2z?file=src%2FApp.jsx)
- [Pure JavaScript implementation without the issue](https://codepen.io/wrxue/pen/emOPrbL)  

---

https://github.com/user-attachments/assets/0d471278-8b12-499d-8b86-819d03a17d2f
Repository: react
Issue: [DevTools Bug]:  [DevTools Bug] Cannot reorder children for node "0" because no matching node was found in the Store.
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://www.autotrack.nl/aanbod

### Repro steps

1. Start profiling in chrome
2. Click on any filter
3. Uncaught Error: Cannot reorder children for node "0" because no matching node was found in the Store.
Dismiss
The error was thrown at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1175534
    at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1140783)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1142390
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1552529)

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

6.0.1-c7c68ef842

### Error message (automated)

Cannot reorder children for node "0" because no matching node was found in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1175534
    at v.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1140783)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1142390
    at bridgeListener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:1:1552529)
```

### Error component stack (automated)

```text

```

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot reorder children for node  because no matching node was found in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
Repository: kubernetes
Issue: Replace reflect.DeepEqual with cmp.Diff in pkg/scheduler tests
Labels: sig/scheduling,kind/feature,needs-triage

### What would you like to be added?

In some tests, `reflect.DeepEqual` is used to compare expected and actual values. It should be replaced to `cmp.Diff` if possible.

### Why is this needed?

According to the [SIG Scheduling guidelines](https://github.com/kubernetes/community/blob/master/sig-scheduling/CONTRIBUTING.md#technical-and-style-guidelines), `cmp.Diff` should be used instead of `reflect.DeepEqual`.
Repository: PowerToys
Issue: Error after enabling high contrast(accesibility panel)  from default unlock window
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.0.0

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

General

### Steps to reproduce

lock pc and enable high contrast throw accessibility panel

[2025-01-23.txt](https://github.com/user-attachments/files/18519748/2025-01-23.txt)

### ✔️ Expected Behavior

No errors on this behavior

### ❌ Actual Behavior

Error window displayed

### Other Software

_No response_