sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Font Height is different than it should be
Labels: font-rendering,under-discussion,confirmation-pending

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.93.1
- OS Version: Windows 10 19045.4894

Steps to Reproduce:

I wanted to apply the Jetbrains Fleet editor appearance into VSCode, so i started by:
1. Noting the default font settings from Jetbrains Fleet:
   **Font:** Jetbrains Mono
   **Font Size:** 13.0
   **Line height:** 1.7

2. Converting it to settings.json for VSCode:
```
"editor.fontFamily": "Jetbrains Mono",
"editor.lineHeight": 1.7,
"editor.fontSize": 13,
```

But then the font height (not the line height) was lower compared to Jetbrains Fleet editor. Like its compressed. Heres a comparison:
Left is VSCode, right is Fleet.
![image](https://github.com/user-attachments/assets/ffc7e32d-7ebf-4ff5-afd0-63f384e48626)
Repository: deno
Issue: Full management of versions à la `nvm` with offline/cache capabilities and wildcards
Labels: cli,suggestion

# Observation 

Deno added cool ways to upgrade like installing without `--version` or `deno upgrade [rc|lts]`.

But still it could be better. Versions are too precise, and you can't just ask for `1.46`, neither ask for `1.46.*` nor `~1.46`.

Also, it would be good to have a full listing of the versions available and list the RCs, and LTSs in a `nvm list-remote` fashion.

Cherry on top would be offline resolution of the version asked if the list of tag is fresh, let's say a day. Similar to `deno run -r, --reload`, a reload option would refresh the cache.

# Subcommands suggestion

```bash
deno ls-remote, list-remote [lts|*wildcard*] # What is available online
deno list [lts|*wildcard*] # offline list. A `-r, --remote` could make the `ls-remote` useless
deno upgrade [lts] # Already exists, but needs *wildcards* 
deno prune [one-version|*wildcard*] [-a, --all-unused, -d --dangling] [-o, --outdated] # outdated will remove all past versions, so if 1.46.3 is the current, 1.46.{0,1,2} will be deleted
```

See past issues:
- https://github.com/denoland/deno/issues/25035
- https://github.com/denoland/deno/issues/18440
- https://github.com/denoland/deno/issues/18406
Repository: PowerToys
Issue: Unable to open Settings or Quick Access
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

General, Settings

### Steps to reproduce

Single or double click system tray icon OR right click system tray icon and select Quick Access or Settings
[PowerToysReport_2024-09-19-16-47-59.zip](https://github.com/user-attachments/files/17067989/PowerToysReport_2024-09-19-16-47-59.zip)

I have:
- Uninstalled PowerToys
- Tried different versions
- Tried different sources
- Tried local vs. machine-wide installs

I have been using PowerToys on this machine (work issued) since approximately v0.59. At some point this issue began and has persisted. At some point, I noticed Dotnet 8 was a dependency but was not being installed. I have manually installed Dotnet 8.

I am able to open certain modules by utilizing their hotkeys.

### ✔️ Expected Behavior

Quick Access to open or Settings menu to open

### ❌ Actual Behavior

Nothing

### Other Software

_No response_
Repository: rust
Issue: `Range<usize>::next` should fully MIR-inline
Labels: T-compiler,A-MIR,A-mir-opt-inlining,C-optimization

If you compile this to optimized MIR:
```rust
// @compile-flags: -O -C debuginfo=0 --emit=mir -Z inline-mir-threshold=9999 -Z inline-mir-hint-threshold=9999
use std::ops::Range;
#[no_mangle]
pub fn demo(num: &mut Range<usize>) -> Option<usize> {
    num.next()
}
```
<https://rust.godbolt.org/z/zsh6b6Y8n>

You'll see that it still contains a call to `forward_unchecked`:
```rust
    bb1: {
        _3 = copy ((*_1).0: usize);
        StorageLive(_4);
        _4 = <usize as Step>::forward_unchecked(copy _3, const 1_usize) -> [return: bb2, unwind continue];
    }
```

That's pretty unfortunate, because `forward_unchecked(a, 1)` is just `AddUnchecked(a, 1)`, a single MIR operator.
Repository: ollama
Issue: Fetch model by hash
Labels: feature request

An endpoint or a CLI command to fetch an ollama "model" by hash (e.g. as found in `manifests/registry.ollama.ai/library/llama3.1/latest`) instead of by a human-assigned tag would help e.g. with offline usage of ollama (downloading models upfront in a sandbox and exposed to ollama in a read-only form)

(not a duplicate of https://github.com/ollama/ollama/issues/2003)
Repository: rust
Issue: Inefficient codegen in builder pattern with existed copyable base value
Labels: A-LLVM,P-medium,T-compiler,C-bug,regression-untriaged

First found in https://github.com/rust-lang/rust/issues/128081#issuecomment-2249215141

In a builder pattern code, when building with existed copyable base value, codegen isn't efficient like partial copy.
This can be reproduced on both argument value and constant value.

Full copy and patial copy:
C version: https://godbolt.org/z/z3fWsKhqE
Rust version: https://godbolt.org/z/MeGf8E5Gd

Existed value and non existed value:
C version: https://godbolt.org/z/9z3x3Kv5c
Rust version: https://godbolt.org/z/vWEaEfd3e

Real use case examaple in rust: https://godbolt.org/z/3q9jn5c1o
Repository: material-ui
Issue: CSS Vars Theme not applying correct styles when using nested/forced color schemes
Labels: bug 🐛,package: material-ui,customization: theme

### Steps to reproduce

Link to live example: 
- Github: https://github.com/rossipedia/mui-css-vars
- Stackblitz: https://stackblitz.com/~/rossipedia/mui-css-vars

Steps:
Use the toggle button group to switch between light and dark mode

### Current behavior

The button labeled "LIGHT" switches its text color from black to white.

### Expected behavior

The "LIGHT" button should not change its text color when switching themes.

### Context

The [docs](https://mui.com/material-ui/customization/css-theme-variables/configuration/#forcing-a-specific-color-scheme) say you should be able to force a specific color scheme by applying the configured selector to a parent element:

> To force a specific color scheme for some part of your application, set the selector to the component or HTML element directly.

### Your environment

Browser: Arc (Chromium)

<img width="396" alt="image" src="https://github.com/user-attachments/assets/9fb64864-c1c7-413f-a9dc-5af430e690bf">


<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
System:
    OS: macOS 15.0
  Binaries:
    Node: 22.8.0 - ~/.local/state/fnm_multishells/34387_1726794020155/bin/node
    npm: 10.8.2 - ~/.local/state/fnm_multishells/34387_1726794020155/bin/npm
    pnpm: 9.6.0 - ~/.local/state/fnm_multishells/34387_1726794020155/bin/pnpm
  Browsers:
    Chrome: 128.0.6613.138
    Edge: 129.0.2792.52
    Safari: 18.0
  npmPackages:
    @emotion/react: ^11.13.3 => 11.13.3
    @emotion/styled: ^11.13.0 => 11.13.0
    @mui/material: 6.1.1 => 6.1.1
    @types/react: ^18.3.8 => 18.3.8
    react: ^18.3.1 => 18.3.1
    react-dom: ^18.3.1 => 18.3.1
    typescript: ^5.6.2 => 5.6.2
```
</details>


**Search keywords**: theme cssvars
Repository: PowerToys
Issue: FancyZones not working with Chrome 128.0.6613.138
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Drag Chrome Windows with Shift key.
No FancyZones appears and cannot snap Chrome Windows

### ✔️ Expected Behavior

Drag Chrome Windows with Shift key.
FancyZones appears and snap Chrome Windows

### ❌ Actual Behavior

Drag Chrome Windows with Shift key.
No FancyZones appears and cannot snap Chrome Windows
I can snap other applications, ex Oultook, Teams with FancyZones.

### Other Software

WIndows 11 23H2
Repository: ollama
Issue: `temperature` for reader-lm should be 0
Labels: model request

[reader-lm](https://ollama.com/library/reader-lm) converts HTML to Markdown but with the default temperature, it hallucinates content: https://github.com/ollama/ollama/issues/6875.  Setting `temperature` to zero appears to resolve this.  This would be nice to have in the model config in the ollama library.
Repository: ollama
Issue: an unknown error was encountered while running the model
Labels: bug

### What is the issue?

API returns error message which does not tell what is wrong.

Reproduce:

install model llava:13b-v1.5-q4_0

save this file:
[req-data.txt](https://github.com/user-attachments/files/17068575/req-data.txt)

run this command:
```curl -d "`cat req-data.txt`" http://localhost:11434/api/generate```

API responds with:
{"error":"an unknown error was encountered while running the model "}


### OS

Linux

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.3.10
Repository: godot
Issue: GPUParticles2D issue
Labels: needs testing,topic:particles

### Tested versions

Godot Engine v4.3.stable.official.77dcf97d8

### System information

Windows 10 OpenGL API 3.3.0 - Build 31.0.101.4887 - Compatibility - Using Device: Intel - Intel(R) UHD Graphics

### Issue description

If you set Emitting to true and One shot to true then this will set the emitter running and then sets the Emitting to false when it's finished.  This results in the particle emitter not running when the emitter's scene is instantiated into the game

### Steps to reproduce

1. Create a scene with a GPUEmitter2D
2. Set the Emitter to true and One shot to true
3. Instantiate the explosion scene into the main game

### Minimal reproduction project (MRP)

NA
Repository: ant-design
Issue: change the locale of ConfigProvider will make the children components totally rerender
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-bdjzlp-guzng3?file=demo.tsx)

### Steps to reproduce

change the locale of ConfigProvider between undefined and other languages

### What is expected?

don't cause the children components totally rerender

### What is actually happening?

 the children components totally rerender

| Environment | Info |
| --- | --- |
| antd | 5.20.6 |
| React | 18.3.1 |
| System | windows 11 |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->


![demo3](https://github.com/user-attachments/assets/25dd531b-14e7-4b70-b081-9f7b4d57cbc4)

antd's default language is English, so I set the locale to undefined when the language change to English, then cause this problem
Repository: rust
Issue: Is "must_use" really needed for Option::insert ?
Labels: T-lang,T-libs-api,C-discussion

Related to https://github.com/rust-lang/rust/pull/87196

I personally think `insert` is a more succinct and readable way than ` = Some(x)` and this seems should be a style preference and don't get why it's marked as `must_use`.
what's more weird is `Option::replace` is not marked as `must use`, so the syntax is kind of inconsistent to me.
Repository: ui
Issue: [feat]: Swiper Slider Component
Labels: area: request

### Feature description

Wanted to have optimized Swiper Slider component to be useful and also a good performance on mobile because I've experience some performance issue on Swiper/React on mobile devices

### Affected component/components

_No response_

### Additional Context

Additional details here...

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: deno
Issue: require('.')  does not work
Labels: bug,node compat

deno version: 2.0.0-rc.4
when using prisma client, a error throws: `error: Could not load '.' `
`require('.')`  should work as `require('./index.js')`
Repository: pytorch
Issue: Composite Compliance Tensor ut check fails in privateuse1 device
Labels: needs reproduction,triaged,module: PrivateUse1

### 🐛 Describe the bug

I perform Composite Compliance Tensor ut check on privateuse1 device and it fails and return unknown format. I find that this tensor will be constructed in python_variable.cpp THPVariable_make_subclass. Here the tensor can not be constructed based on device.

### Versions

pytorch  2.1+ 

cc @NmomoN @mengpenghui @fwenguang @cdzhan @1274085042 @PHLens
Repository: rust
Issue: `Send` bound of trait object make unexpected async block is not general enough error
Labels: A-diagnostics,A-trait-system,C-bug,A-async-await

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=4f2133cbf38d27366a8edd106b5485e5

I expected to see this happen: Same as below, compile pass:
https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=69e324c356bd126e575a971a7cbbf2fa

Instead, this happened:
```
error: implementation of `From` is not general enough
  --> src/lib.rs:44:9
   |
44 | /         Box::pin(async move {
45 | |             let response = self.send_request(request).await;
46 | |             match response {
47 | |                 Ok(response) => todo!(),
...  |
51 | |             }
52 | |         })
   | |__________^ implementation of `From` is not general enough
   |
   = note: `Box<(dyn std::error::Error + Send + Sync + 'static)>` must implement `From<Box<(dyn std::error::Error + Send + Sync + '0)>>`, for any lifetime `'0`...
   = note: ...but it actually implements `From<Box<(dyn std::error::Error + Send + Sync + 'static)>>`

error: could not compile `playground` (lib) due to 1 previous error; 1 warning emitted
```
Repository: deno
Issue: `using` in a `for... of` loop fails to call `Symbol.dispose` method (+ same problem for `async` versions)
Labels: bug,upstream,swc

Version: Deno 1.46.3

I initially thought this was a bug with TS, but compiling TS via the playground and running it in Chrome works correctly, as does running it in Bun.

Using `using` within a `for... of` loop fails to call the `Symbol.dispose` method. The same problem occurs when using awaiting using using `await using` using `Symbol.asyncDispose`:

```ts
class Disposable {
    disposed = false;

    [Symbol.dispose]() {
        this.disposed = true
    }
}

const disposables = [new Disposable()]

for (using _ of disposables) {/* ... */}

if (disposables[0]!.disposed) {
    console.log("✅ dispose ok")
} else {
    console.error("💥 failed to dispose")
}

class AsyncDisposable {
    disposed = false;

    [Symbol.asyncDispose]() {
        this.disposed = true
    }
}

const asyncDisposables = [new AsyncDisposable()]

for (await using _ of asyncDisposables) {/* ... */}

if (asyncDisposables[0]!.disposed) {
    console.log("✅ async dispose ok")
} else {
    console.error("💥 failed to async dispose")
}
```

Keywords: using, using using, using await using, awaiting using await using
Repository: pytorch
Issue: [channels_last] Segmentation fault with aten.convolution
Labels: high priority,module: crash,module: cpu,module: convolution,triaged,oncall: cpu inductor

### 🐛 Describe the bug

Segmentation fault is observed with aten.convolution for inputs in channels_last format. This is observed with both eager and compile mode.

The example works fine if channels_last format is not enabled.

### Error logs

```
Internal Error: Received signal - Segmentation fault
Segmentation fault (core dumped)
```

### Minified repro

```
import torch

def compute(input, input2):
    clone = torch.ops.aten.clone.default(input2, memory_format = torch.channels_last)
    convolution = torch.ops.aten.convolution.default(clone, input, None, [2, 13], [1, 14], [1, 1], False, [0, 0], 67)
    convolution_backward = torch.ops.aten.convolution_backward.default(convolution, clone, input, [0], [2, 13], [1, 14], [1, 1], False, [0, 0], 67, [True, True, False])
    print(convolution_backward)

input = torch.randn(134, 67, 2, 1)
input2 = torch.randn(18, 4489, 23, 12)
input = input.contiguous(memory_format=torch.channels_last)

compute(input, input2)
```

### Versions

```
PyTorch version: 2.4.0a0+git9cc5232
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.4 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: 14.0.5
CMake version: version 3.28.3
Libc version: glibc-2.35

Python version: 3.10.12 (main, Sep 11 2024, 15:47:36) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-5.15.0-119-generic-x86_64-with-glibc2.35
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
```

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10 @chauhang @penguinwu
Repository: excalidraw
Issue: No Text Preview while writing 
Labels: bug

No doubt the the excalidraw platform is great , but make the writing preview on for black color as it is the most used and the classic color to write  , while typing i cannot see what i am typing or if i make typo then  the only way to know and correct it is to see that after writing , this happens every often , just make the text preview aa blac in color while writing in real time for black color
Repository: transformers
Issue: Kolmogorov–Arnold Transformer
Labels: New model,Feature request

### Model description

The Kolmogorov–Arnold Transformer (KAT) replaces the standard MLP layers in transformers with Kolmogorov-Arnold Network (KAN) layers, improving the model's expressiveness and overall performance. 

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

The code is at https://github.com/Adamdad/kat and paper at https://arxiv.org/abs/2409.10594
Repository: ollama
Issue: "/show parameters" command causes crashes when running Qwen 2.5 models, on version 0.3.11
Labels: bug

### What is the issue?

This only happens after changing the parameters through /set parameter command.
Here's an example:
PS H:\ztmp> ollama run qwen2.5
>>> /show parameters
No parameters were specified for this model.
>>> /set parameter top_k 1
Set parameter 'top_k' to '1'
>>> /show parameters
error: couldn't get model
Error: something went wrong, please see the ollama server logs for details
PS H:\ztmp>

This is on windows 11.

Here's the error message from the ollama serve terminal tab:
2024/09/20 08:47:43 [Recovery] 2024/09/20 - 08:47:43 panic recovered:
assignment to entry in nil map
runtime/map_faststr.go:205 (0x7a93ba)
github.com/ollama/ollama/server/routes.go:807 (0x12cc57e)
github.com/ollama/ollama/server/routes.go:732 (0x12cb497)
github.com/gin-gonic/gin@v1.10.0/context.go:185 (0x1287cca)
github.com/ollama/ollama/server/routes.go:1076 (0x12d0c14)
github.com/gin-gonic/gin@v1.10.0/context.go:185 (0x1295d39)
github.com/gin-gonic/gin@v1.10.0/recovery.go:102 (0x1295d27)
github.com/gin-gonic/gin@v1.10.0/context.go:185 (0x1294e64)
github.com/gin-gonic/gin@v1.10.0/logger.go:249 (0x1294e4b)
github.com/gin-gonic/gin@v1.10.0/context.go:185 (0x1294291)
github.com/gin-gonic/gin@v1.10.0/gin.go:633 (0x1293d00)
github.com/gin-gonic/gin@v1.10.0/gin.go:589 (0x1293831)
net/http/server.go:2688 (0xafaecc)
net/http/server.go:3142 (0xafc6cd)
net/http/server.go:2044 (0xaf79c7)
runtime/asm_amd64.s:1695 (0x8026a0)

### OS

Windows

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.3.11
Repository: rust
Issue: `#[rustc_default_body_unstable]` silently ignores `implied_by` and `soft`
Labels: A-attributes,T-compiler,C-bug

`#[rustc_default_body_unstable]` is treated the same as `#[unstable]` by `parse_unstability` in `rustc_attr`, so it accepts the same flags. However, the stability annotator in `rustc_passes` doesn't collect implications from it and `eval_default_body_stability` in `rustc_middle` doesn't check feature-gate implications. Likewise, it accepts `soft` but `default_body_is_unstable` in `rustc_hir_analysis` ignores it.

I think I can fix this (I don't imagine it's high-priority) but I'd like to check first whether it's intentionally not handled. Currently I don't think anything in `library/` or `src/` uses or acknowledges `#[rustc_default_body_unstable]`/`rustc_attr::DefaultBodyStability`.
Repository: godot
Issue: Unnecessary "Viewport Texture must be set to use it." errors while trying to set said ViewportTexture
Labels: bug,topic:core,topic:editor

### Tested versions

- Reproducible in 4.3.stable
- Reproducible in 4.4.dev2 and `master` (0a4aedb36065f66fc7e99cb2e6de3e55242f9dfb), i.e. both before and after #97029

### System information

Fedora Linux 40 (KDE Plasma) - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 7600M XT (RADV NAVI33) - AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16 Threads)

### Issue description

While testing the MRP from #96941 which uses ViewportTextures, I noticed some cases which don't seem to be well handled yet, even after #97029 (cc @Hilderin).

![image](https://github.com/user-attachments/assets/8651cb2f-287e-459d-a797-6bb466091bc6)

In the "Test 0/MeshInstance3D", for the Surface Material Override > Albedo > Texture, if you assign "New ViewportTexture", it spams the error 3 times, and the dialog that normally shows to let you select a SubViewport flashes and disappears right away.
```
ERROR: Viewport Texture must be set to use it.
   at: _err_print_viewport_not_set (./scene/main/viewport.cpp:171)
ERROR: Viewport Texture must be set to use it.
   at: _err_print_viewport_not_set (./scene/main/viewport.cpp:171)
ERROR: Viewport Texture must be set to use it.
   at: _err_print_viewport_not_set (./scene/main/viewport.cpp:171)
```

In the "Test 1/MeshInstance3D", for the Surface Material Override > Shader Parameters > Texture, if you assign "New ViewportTexture", it prints the error *once*, but properly shows the SubViewport selection dialog, which works fine to pick a SubViewport.

On the other hand for that MRP, #97029 did solve two occurrences of the error when opening the scene (visible in 4.3.stable or 4.4.dev2, but not in latest `master`).

### Steps to reproduce

See above.

### Minimal reproduction project (MRP)

https://github.com/rakkarage/testtextureshaderparameter

Zipped version in case that repo gets updated or removed: 
[testtextureshaderparameter.zip](https://github.com/user-attachments/files/17072306/testtextureshaderparameter.zip)