sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: It's not possible to set any Terminal Profile
Labels: bug,confirmed,terminal-profiles

<!-- ⚠️⚠️ 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.92.0 (user setup)
Commit: b1c0a14de1414fcdaa400695b4db1c0799bc3124
Date: 2024-07-31T23:26:45.634Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

- OS Version: 
Windows 11 23H2. build 22631.3880

Steps to Reproduce:

1. open ` code --disable-extensions --user-data-dir <test_dir>`
2. Follow the terminal profiles doc, and add a profile:
https://code.visualstudio.com/docs/terminal/profiles#_configuring-profiles  
3. e.g.:
```json
{
    "terminal.integrated.profiles.windows": {
        "test": {
            "source": "PowerShell",
            "args": ["-NoProfile"]
        }
    },
    "terminal.integrated.defaultProfile.windows": "test"
}
```
vscode warns on `"terminal.integrated.defaultProfile.windows": "test"`  
Message in my system:  
```
Value is not accepted. Valid values: null, "PowerShell", "Windows PowerShell", "Git Bash", "Command Prompt", "Cygwin", "bash (MSYS2)", "JavaScript Debug Terminal"
```

The only, somewhat, related bug was alread fixed and closed:
https://github.com/microsoft/vscode/issues/161219
Repository: rust
Issue: Incorrect reporting of asm labels in Nightly
Labels: A-lints,A-diagnostics,T-compiler,C-bug,L-binary_asm_labels,D-imprecise-spans


Updating from 1.80.x-nightly to 1.82.x-nightly introduced a new compiler error in one of my inline assembly blocks falsely reporting that an `int 0x13` shouldn't include numerical labels. 


I tried this code:

```rust
    pub fn read(&self, disk: u16) {
        let packet_address = self as *const Self as u16;
        let status: u16;

        unsafe {
            core::arch::asm!("
                push si
                mov si, {packet:x}
                mov ax, 0x4200
                int 0x13
                jc 1f
                mov {status:x}, 0
                jmp 2f
                1:
                mov {status:x}, 1
                2:
                pop si
            ",
                in("dx") disk,
                packet = in(reg) packet_address,
                status = out(reg) status,
            );
        };

        // If the interrupt failed, we want to abort and tell the user
        if status == 1 {
            fail(b'D');
        }
    }
```

Compiler output:
```
error: avoid using labels containing only the digits `0` and `1` in inline assembly
  --> bootloader/stage-bootsector/src/disk.rs:38:23
   |
38 |                   int 0x13
   |  _______________________^
39 | |                 jc 1f
40 | |                 mov {status:x}, 0
   | |___________________________^ use a different label that doesn't start with `0` or `1`
   |
   = help: start numbering with `2` instead
   = note: an LLVM bug makes these labels ambiguous with a binary literal number on x86
   = note: see <https://github.com/llvm/llvm-project/issues/99547> for more information
   = note: `#[deny(binary_asm_labels)]` on by default
```

### Meta

`rustc --version --verbose`:
```
rustc 1.82.0-nightly (64ebd39da 2024-08-03)
```

*No backtrace was provided even when setting RUST_BACKTRACE=1*

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"asquared31415"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: vscode
Issue: Ability to change cursor height.
Labels: feature-request,editor-rendering

<!-- ⚠️⚠️ 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. -->

I know that this issue has been created twice already (#100492 and #27931), but we are still looking for this feature, that sublime text already had for YEARS
Repository: tauri
Issue: v2 requiring an instance of App, AppHandle or Window to get access to path functions like home_dir()
Labels: type: documentation,help wanted

in v1, all you needed was to import and you had access to paths:
```rust
use tauri::api::path::home_dir;

#[tauri::command]
fn getPath() -> Result<PathBuf> {
   home_dir()
```

but now in v2, you need an instance of AppHandle:
```rust
use tauri::Manager;

#[tauri::command]
fn getPath(app: tauri::AppHandle) -> Result<PathBuf> {
   app.path().home_dir()
```

is this intended?
also there's no documentation I could find on v2 usage of paths
Repository: godot
Issue: Editor becomes unresponsive on macOS when launched from JetBrains Rider
Labels: bug,platform:macos,topic:editor,topic:thirdparty,regression,performance

### Tested versions

Reproducible in: 
- 4.3 RC 2 Mono

Not reproducible in:
- 4.3 RC 1
- 4.3 Beta 2
- 4.2

### System information

Godot v4.3.rc2.mono - macOS 14.5.0 - Vulkan (Forward+) - integrated Apple M1 Pro - Apple M1 Pro (10 Threads)

### Issue description

When the editor has been open for some amount of time, it becomes unresponsive. This sometimes occurs when alt-tabbing into the editor window, and sometimes occurs when performing an action from the editor (such as building the C# assembly, saving project settings, or resetting an exported property in the inspector, to name a few examples I have experienced firsthand).

### Steps to reproduce

1. Open a C# project in Godot 4.3 RC 2 Mono on macOS.
2. Work on the project as normal, spending large amounts of time with the editor open in the background while using an external IDE to edit C# code.
3. Eventually, the editor will become unresponsive, necessitating a Force Quit.

### Minimal reproduction project (MRP)

N/A
Repository: tauri
Issue: [bug] Characters ignored in <input> field when using single key shortcuts (Linux)
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

When registering single-key keyboard shortcuts eg. 
```rust
Menu::new()
     .add_item(CustomMenuItem::new("albums", "Go to Albums").accelerator("A"))
     .add_item(CustomMenuItem::new("library", "Go to Library").accelerator("L"))
     .add_item(CustomMenuItem::new("queue", "Toggle Queue").accelerator("Q"))
```
, the letters won't work in an `<input>` field because the shortcut is triggered instead. This occurs on Linux but not on macOS. Haven't tested on Windows. 

### Reproduction

Repro repo here: https://github.com/basharovV/tauri-linux-input-shortcut-repro

### Expected behavior

When typing in an <input> field, all single-key shortcuts should be ignored until the focus is released. This is the behaviour on macOS

### Full `tauri info` output

```text
[✔] Environment
    - OS: Ubuntu 22.04 X64
    ✔ webkit2gtk-4.0: 2.44.2
    ✔ rsvg2: 2.52.5
    ✔ rustc: 1.80.0 (051478957 2024-07-21)
    ✔ cargo: 1.80.0 (376290515 2024-07-16)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-unknown-linux-gnu (default)
    - node: 18.20.4
    - npm: 10.7.0

[-] Packages
    - tauri [RUST]: 1.7.1
    - tauri-build [RUST]: 1.5.3
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.6.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../build
    - devPath: http://localhost:1420/
    - framework: Svelte
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Story Indexer doesn't support `type: docs`
Labels: bug,needs triage

### Describe the bug

If a story indexer returns `type: docs`, then this is ignored and it is added as `type: story`, see 
https://github.com/storybookjs/storybook/blob/b94ead30bd1798648bc674bce61ba841508b6bbc/code/core/src/core-server/utils/StoryIndexGenerator.ts#L369

### Reproduction link

https://github.com/tobiasdiez/storybook-vue-addon/pull/118 (see code)

### Reproduction steps

_No response_

### System

```bash
Latest storybook
```


### Additional context

_No response_
Repository: pytorch
Issue: Reducing jagged tensor using unbind results in error in torch.compile
Labels: triaged,module: nestedtensor,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

I am trying to understand why adding torch.compile to the following code (for a simple batch-wise multiplication and reduction sum of nested jagged tensors) results in the following error. Basically, I don't understand what this error means, how it affects the performance/accuracy of results, and also I could not find any documentation of it online.

```python
import torch
import torch.nested as nested

x = (torch.arange(20).reshape((5,4)) * 1.).requires_grad_()
y = (torch.arange(12).reshape((3,4)) * 10.).requires_grad_()
n = nested.as_nested_tensor([x, y], layout=torch.jagged)
w = torch.tensor([10., 100.], dtype=torch.float).reshape(2,1,1).requires_grad_()

def redmul(n, w):
    nw = nested.as_nested_tensor([dense * w[idx] for idx, dense in enumerate(n.unbind())], layout=torch.jagged)
    loss = 0.
    for dense in nw.unbind():
        loss = loss + dense.sum()
    return loss

mul = torch.compile(redmul) ### No error without compile
loss = mul(n, w)
loss.backward()
```

Error:
```
W0804 22:05:35.902000 3221626 torch/fx/experimental/symbolic_shapes.py:5189] [0/0] failed during evaluate_expr(u0, hint=None, expect_rational=True, size_oblivious=False, forcing_spec=False
E0804 22:05:35.903000 3221626 torch/fx/experimental/recording.py:298] [0/0] failed while running evaluate_expr(*(u0, None), **{'fx_node': False})
W0804 22:05:36.037000 3221626 torch/_dynamo/exc.py:270] [0/0_1] Backend compiler failed with a fake tensor exception at 
W0804 22:05:36.037000 3221626 torch/_dynamo/exc.py:270] [0/0_1]   File "/tmp/ipykernel_3221626/2352441899.py", line 4, in redmul
W0804 22:05:36.037000 3221626 torch/_dynamo/exc.py:270] [0/0_1]     nw = nested.as_nested_tensor([dense * w[idx] for idx, dense in enumerate(n.unbind())], layout=torch.jagged)
W0804 22:05:36.037000 3221626 torch/_dynamo/exc.py:270] [0/0_1] Adding a graph break.
```

### Versions

Latest nightly pytorch from conda:
```
libjpeg-turbo             2.0.0                h9bf148f_0    pytorch-nightly
pytorch                   2.5.0.dev20240803 py3.10_cuda12.1_cudnn9.1.0_0    pytorch-nightly
pytorch-cuda              12.1                 ha16c6d3_6    pytorch-nightly
pytorch-mutex             1.0                        cuda    pytorch-nightly
torchaudio                2.4.0.dev20240803     py310_cu121    pytorch-nightly
torchtriton               3.0.0+dedb7bdf33           py310    pytorch-nightly
torchvision               0.20.0.dev20240803     py310_cu121    pytorch-nightly
```

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ @ezyang @chauhang @penguinwu
Repository: opencv
Issue: pyrDown is not consistent between different ROIs
Labels: bug,category: imgproc

### System Information

OpenCV version: 4.10 and below

### Detailed description

Running `pyrDown` on a ROI of an image should produce the same result as running `pyrDown` on a full image and then taking the corresponding ROI of the result.
This assumption is not correct for result borders but only if `BORDER_ISOLATED` flag is enabled.

Here's the code showing that this assumption is broken. This can possibly be caused by a size of a destination image which is `x/2+1` for each dimension.

### Steps to reproduce

```
    Mat src(16, 16, CV_16UC3, Scalar(0, 0, 0));
    {
        int swidth = src.cols;
        int sheight = src.rows;
        int cn = src.channels();
        int count = 0;
        for (int y = 0; y < sheight; y++)
        {
            ushort *src_c = src.ptr<ushort>(y);
            for (int x = 0; x < swidth * cn; x++)
            {
                src_c[x] = (count++) % 10;
            }
        }
    }
    Mat dst(src.cols / 2 + 1, src.rows / 2 + 1, CV_16UC3, Scalar(0,0,0));
    pyrDown(src, dst, Size(dst.cols, dst.rows));

    Mat srcp = src(Rect(0, 0, 14, 14));
    Mat dstp(srcp.cols / 2 + 1, srcp.rows / 2 + 1, CV_16UC3, Scalar(0,0,0));
    pyrDown(srcp, dstp, Size(dstp.cols, dstp.rows));

    std::cout << "dst diff" << std::endl << dst(Rect(Point(), dstp.size())) - dstp << std::endl;
```
Expected output: all zeros
Actual output:
```
[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0;
 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 1, 0;
 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1;
 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0;
 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 1, 1;
 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0;
 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1, 1, 0;
 0, 1, 1, 1, 1, 0, 0, 0, 1, 0, 0, 0, 1, 1, 1, 0, 0, 0, 1, 1, 0, 1, 1, 0]
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: pytorch
Issue: DISABLED test_device_mode_ops_sparse_mm_reduce_cpu_float64 (__main__.TestDeviceUtilsCPU)
Labels: triaged,module: flaky-tests,skipped,module: unknown

Platforms: asan, linux, mac, macos, win, windows

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_device_mode_ops_sparse_mm_reduce_cpu_float64&suite=TestDeviceUtilsCPU&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/28323231518).

Over the past 3 hours, it has been determined flaky in 66 workflow(s) with 198 failures and 66 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_device_mode_ops_sparse_mm_reduce_cpu_float64`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/Users/ec2-user/runner/_work/pytorch/pytorch/test/test_utils.py", line 1164, in test_device_mode_ops
    for sample in samples:
  File "/Users/ec2-user/runner/_work/_temp/conda_environment_10238467895/lib/python3.9/site-packages/torch/testing/_internal/common_utils.py", line 388, in __next__
    input_idx, input_val = next(self.child_iter)
  File "/Users/ec2-user/runner/_work/_temp/conda_environment_10238467895/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 36, in generator_context
    response = gen.send(None)
  File "/Users/ec2-user/runner/_work/_temp/conda_environment_10238467895/lib/python3.9/site-packages/torch/testing/_internal/common_methods_invocations.py", line 1228, in sample_inputs_sparse_mm_reduce
    torch.eye(m, m)
RuntimeError: Please register PrivateUse1HooksInterface by `RegisterPrivateUse1HooksInterface` first.

To execute this test, run the following from the base repo dir:
    python test/test_utils.py -k TestDeviceUtilsCPU.test_device_mode_ops_sparse_mm_reduce_cpu_float64

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_utils.py`

cc @clee2000
Repository: PowerToys
Issue: Make Installer Existing-Installed-Version-Location-Aware
Labels: Area-Setup/Install,Needs-Triage

### Description of the new feature / enhancement

When you install PT, and you already have an existing installation in place, the installer should lookup the existing installed path. It should then show that path in the installer dialog, and perhaps inquire if you wish to upgrade that install. 

### Scenario when this would be used?

Every installation of the application.

### Supporting information

I have a current installation of PT v80.1.0 located in D:\Program Files\Utilities\PowerToys. I just started the installer for the current v83.0 build (x64, machine wide), and it gave the default installation location vs my existing location.
Repository: go
Issue: proposal: x/net/http2/h2c: allow to disable http upgrade in h2c
Labels: Proposal

### Proposal Details

## changes

I add an option `DisableH2CUpgrade` to allow server to ignore the upgrading headers from the clients, it satisfies the bahavior mentioned in [rfc7230 section 6.7 ](https://datatracker.ietf.org/doc/html/rfc7230#section-6.7)

> A server MAY ignore a received Upgrade
   header field if it wishes to continue using the current protocol on
   that connection.

So after the change, if `DisableH2CUpgrade` is specified, the server will use http/2 to serve http/2 requests while using http1.1 for http1.1 requests.

## motivation

The [H2C smuggle](https://www.assetnote.io/resources/research/h2c-smuggling-in-the-wild) is verbose for a server behind some proxies. As the proxy is not controlled by the service maintainers, and it does need h2c for faster internal communication among servers, the `prior knowledge` way is enough in such scenarios.

This PR supports this feature by adding a new option, which is backward compatible as well.
Repository: rust
Issue: Should IoSliceMut::advance() be used when impl std::io::Read::read_vectored()?
Labels: T-libs-api,A-docs,T-libs,A-io,C-discussion

As of [io_slice_advance](https://github.com/rust-lang/rust/issues/62726) is stable since 1.81, the following asserting may won't work if the users use IoSliceMut::advance in their impl of `Read` trait.
```rust
fn what_to_read<R>(reader: R)
where
    R: Read,
{
    let mut b1 = [0u8; 16];
    let mut b2 = [0u8; 32];

    let mut iov = [IoSliceMut::new(&mut b1), IoSliceMut::new(&mut b2)];
    let nr = reader.read_vectored(&mut iov).unwrap();

    if nr > 0 {
        assert_eq!(b1[0], iov[0][0]);
    }
    if nr >= b1.len() {
        assert_eq!(iov[0].len(), b1.len());
    }
}
```

It is unclear that whether the returned size of `read_vectored` is the real read data size, or the valid buffer size in the passed `&mut [IoSliceMut<'_>]`.
Please clarify that so `Read` implementations can do the correct thing.
Repository: PowerToys
Issue: Rebound key not repeating when I hold it down
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.83.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Rebind Delete key to Pause key, hold down Pause - it will only delete a single character, then do nothing.

### ✔️ Expected Behavior

Pressing down the rebound Pause key should keep on deleting characters.

### ❌ Actual Behavior

Only a single character is deleted, then nothing else happens.

### Other Software

_No response_
Repository: create-react-app
Issue: React Application Embedded Script
Labels: needs triage

Hello Team, 

I want create a react application in embedded so we can use in other directly in other proejcts when call this script
Repository: next.js
Issue: with-msw example doesn't work. 
Labels: examples

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 8
Binaries:
  Node: 20.16.0
  npm: 10.8.1
  Yarn: 1.22.22
  pnpm: 9.6.0
Relevant Packages:
  next: 15.0.0-canary.102 // Latest available version is detected (15.0.0-canary.102).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 4.9.5
Next.js Config:
  output: N/A
```


### Which example does this report relate to?

with-msw

### What browser are you using? (if relevant)

N/A

### How are you deploying your application? (if relevant)

npm run dev

### Describe the Bug

Running the `with-msw` example as is , using node 20.16 will show this error: 

```
    at async DevServer.handleRequest (/Users/dwjohns5/git-workspace/with-msw-app-2/node_modules/next/dist/server/dev/next-dev-server.js:336:24) {
  page: '/',
  [cause]: Error: getaddrinfo ENOTFOUND my.backend
      at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:120:26) {
    errno: -3008,
    code: 'ENOTFOUND',
    syscall: 'getaddrinfo',
    hostname: 'my.backend'
  }
```


This issue here https://github.com/vercel/next.js/issues/56608 appears to be refer to the same issue, and it mentions that it's an issue with Next now using native fetch and MSW having an issue with it. 

I updated to msw@2.3.5 and the issue still exists. (see: https://github.com/dwjohnston/with-msw-repro/commit/3d959bea37baec2500e089cd24e1c161331cabcc) 


It's worth mentioning this open issue here: https://github.com/mswjs/msw/issues/1340





### Expected Behavior


At the very least the with-msw example should show _some_ kind of instance of MSW working, and the documentation provide all the caveats and scenarios where it won't work. 

### To Reproduce

```
nvm use 20 
npx create-next-app --example with-msw with-msw-app
cd with-msw-app
npm run dev 
```

Access application at localhost:3000 and observe server rendering fail.
Repository: ollama
Issue: How to fix the default settings of the model?
Labels: bug

### What is the issue?

I found that the template for 'yi: 9b-v1.5-q8-0' is missing and different from the 'yi: 9b' template
Where should the fix be carried out?

![image](https://github.com/user-attachments/assets/90bd2fc8-b4c7-40b2-92c9-fbf9c9a08298)
![image](https://github.com/user-attachments/assets/5cec12cd-8f25-45be-8990-3eabda9c95d8)
![image](https://github.com/user-attachments/assets/1b6eeec8-dc74-4dff-8df5-bedb6ce85fde)


### OS

Windows

### GPU

AMD

### CPU

AMD

### Ollama version

0.3.2