sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: Ollama stops giving outputs after a few runs
Labels: bug

### What is the issue?

I've been trying to run "smallthinker" and "llama3.2:1b", but after around 30 runs, the models stop giving outputs. However, ollama is running with 100% CPU in the background on my Mac. 

### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

0.5.7
Repository: go
Issue: maps: make Equal O(1) for pointer-identical maps
Labels: Performance,NeedsInvestigation,LibraryProposal

### Go version

go1.23

### Output of `go env` in your module/workspace:

```shell
GOARCH=amd64
GOOS=linux
```

### What did you do?

Ran this benchmark:
```
var m = func() map[int]string {
	m := make(map[int]string)
	for i := range 1000000 {
		m[i] = strconv.Itoa(i)
	}
	return m
}()

func Benchmark(b *testing.B) {
	for range b.N {
		maps.Equal(m, m)
	}
}
```

### What did you see happen?

```
Benchmark-32    	      75	  15531818 ns/op
```

### What did you expect to see?

```
Benchmark-32    	1000000000	         0.1882 ns/op
```

As a trivial test, Equal could use unsafe to check whether the map pointers are identical.
In which case, the maps are equal.

Unfortunately, we need to skip this optimization if the key and value types could possibly contain floating point values, which violate the reflexive property of equality for NaNs.
Repository: next.js
Issue: Error when using namespace/compound components in React Server Component
Labels: linear: next,Module Resolution

### Link to the code that reproduces this issue

https://github.com/DanielGiljam/nextjs-rsc-jsx-issue

### To Reproduce

1. Start the application in development (next dev)

3. See the error

    ```
    React.jsx: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.
    ```

### Current vs. Expected behavior

Current behavior: you get the error described above.

Expected behavior: namespace/compound components would work like they do in client components.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 23.3.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.14.2
Relevant Packages:
  next: 15.2.0-canary.19 // Latest available version is detected (15.2.0-canary.19).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

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

Module Resolution, Not sure

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

next dev (local), next build (local)

### Additional context

_No response_
Repository: godot
Issue: Typed Dictionary cannot use subclass of type in key with Invalid index type for a base type
Labels: discussion,topic:gdscript,documentation

### Tested versions

v4.4.beta1.official [d33da79d3]

### System information

Godot v4.4.beta1 - Windows 10 (build 19045) - Multi-window, 3 monitors - Vulkan (Forward+) - dedicated GeForce GTX 1050 - Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 threads)

### Issue description

A typed Dictionary with index of type X cannot use a variable of type Y (that extends X) in keys.



### Steps to reproduce

1) Create a base class
2) Create another class that extends first class
3) Create a typed dictionary. Use the base class as the key type
4) Create a variable of the subtype
5) attempt to use that variable as a key in dictionary

Expected: can use any subclass of index type as a key

What happens: Parser Error: Invalid index type "(subclass name)" for a base of type "Dictionary[(base type), String]"

### Minimal reproduction project (MRP)

[mpr-typed-dictionary-subclass-index.zip](https://github.com/user-attachments/files/18509677/mpr-typed-dictionary-subclass-index.zip)
Repository: pytorch
Issue: DISABLED test_view_of_slice_cuda (__main__.TestUnbackedSymintsCUDA)
Labels: module: rocm,triaged,skipped

Platforms: rocm

This test was disabled because it is failing on main branch ([recent examples](https://torch-ci.com/failure?failureCaptures=%5B%22inductor%2Ftest_unbacked_symints.py%3A%3ATestUnbackedSymintsCUDA%3A%3Atest_view_of_slice_cuda%22%5D)).

This seems to be an mi300-specific failure.

cc @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd
Repository: PowerToys
Issue: Stop to work
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

My laptop just stop to connect to my computer. I try to restart, uninstall and reinstall and still not work.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: opencv
Issue: 16-bit APNG Reading and Writing Problems
Labels: bug,category: imgcodecs

### System Information

OpenCV version: 4.12.0-dev

### Detailed description

The `imreadanimation` function currently fails to properly read specific 16-bit APNG files, including those with 2 channels (grayscale + alpha). Sample images for testing can be found in the APNGKit repository:
[033.png](https://github.com/onevcat/APNGKit/blob/master/Tests/APNGKitTests/Resources/SpecTesting/033.png)
[034.png](https://github.com/onevcat/APNGKit/blob/master/Tests/APNGKitTests/Resources/SpecTesting/034.png)
[035.png](https://github.com/onevcat/APNGKit/blob/master/Tests/APNGKitTests/Resources/SpecTesting/035.png)

A possible solution could be to read 2-channel APNG images as 4-channel images, similar to how imread (as far as I know) processes 2-channel standard PNGs as 4-channel images.

Additionally, the `imwriteanimation` function currently converts 16-bit frames to 8-bit before saving. Would it be feasible to support saving 16-bit APNGs if there is a real need for it? (I did not find any 16-bit APNG files except for the mentioned test files.)

I am planning to work on this issue, and any feedback would be helpful.

### Steps to reproduce

```
import cv2 as cv
import numpy as np

animation = cv.Animation()
filename = "034.png"
success, animation = cv.imreadanimation(filename)
cv.imshow("Frame", animation.frames[0])
cv.waitKey()
```

also take a look on related [test code](https://github.com/opencv/opencv/blob/4.x/modules/imgcodecs/test/test_animation.cpp#L363-L406)

### Issue submission checklist

- [x] I report the issue, it's not a question
- [ ] 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: create DISABLED issues for specific runner labels
Labels: module: ci,triaged

### 🚀 The feature, motivation and pitch

ROCm CI runners are a mix of MI200 and MI300 systems.  At the time of writing this issue, the MI200 runners are used pre-merge and the MI300 runners are only used post-merge.  

- rocm / linux-focal-rocm6.3-py3.10 / test (default, 1, 6, linux.rocm.gpu.mi300.2) [post-merge]
- rocm / linux-focal-rocm6.3-py3.10 / test (default, 1, 6, linux.rocm.gpu.2) [pre-merge]

Other HW vendors might also support different runner labels for the same flows.

We are seeing tests getting DISABLED as flaky because they pass on mi200 pre-merge then fail on mi300 post-merge.  Unfortunately, the DISABLED issues are disabling both mi200 and mi300 runner labels for the same flows which means we are losing the mi200 signal unnecessarily.

Is it possible to create DISABLED issues that can also specify the runner label?

### Alternatives

_No response_

### Additional context

_No response_

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: vscode
Issue: terminal is not working 
Labels: info-needed


Type: <b>Bug</b>

terminal is not working and i have windows 10 installed but vs code running 8 version

VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 6.0.6002
Modes:

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

|Item|Value|
|---|---|
|CPUs|Intel(R) Celeron(R) CPU  N3060  @ 1.60GHz (2 x 1600)|
|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: disabled_off<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|3.83GB (0.34GB free)|
|Process Argv|--crash-reporter-id fb6c5a50-8a7a-4cc7-8401-bc15b680d067|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (10)</summary>

Extension|Author (truncated)|Version
---|---|---
bracket-pair-color-dlw|Bra|0.0.6
npm-intellisense|chr|1.4.5
path-intellisense|chr|2.10.0
vscode-eslint|dba|3.0.13
prettier-vscode|esb|11.0.0
auto-rename-tag|for|0.1.10
powershell|ms-|2025.0.0
LiveServer|rit|5.7.9
es7-react-js-snippets|rod|1.9.3
JavaScriptSnippets|xab|1.8.0


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

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
newcmakeconfigv2:31071590
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
9064b325:31222308
copilot_t_ci:31222730

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: hint_range emit wrong error
Labels: bug,confirmed,topic:shaders

### Tested versions

- Reproducible in v4.3.stable.mono.official [77dcf97d8]

### System information

Apple M1 Pro, Sequoia 15.2

### Issue description

hint_range with a non literal value produce the error:  `Expected an integer constant after!.`

hint_range works with floats but does not work with constants, so the error should most likely be `Expected a literal after`.

### Steps to reproduce

In any shader, add a line:

```glsl
uniform float foo : hint_range(1.1, PI) = 0.0;
```
However if you just specify a float, it compiles with no errors:

```glsl
uniform float foo : hint_range(1.1, 2.2) = 0.0;
```

### Minimal reproduction project (MRP)

It is easily reproducible. Let me know if it is absolutely necessery.
Repository: rust
Issue: Tracking Issue for `atomic_try_update`
Labels: T-libs-api,C-tracking-issue


Feature gate: `#![feature(atomic_try_update)]`

This is a tracking issue for an infallible version of `AtomicT::fetch_update` as well as a new name for the existing fallible version.

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
impl AtomicT {
    // same as `fetch_update`
    pub fn try_update(
        &self,
        set_order: Ordering,
        fetch_order: Ordering,
        f: impl FnMut(T) -> Option<T>,
    ) -> Result<T, T>;

    pub fn update(
        &self,
        set_order: Ordering,
        fetch_order: Ordering,
        f: impl FnMut(T) -> T,
    ) -> T;
}
```

### Steps / History

- [x] ACP: https://github.com/rust-lang/libs-team/issues/490
- [x] Design requested by t-libs-api in https://github.com/rust-lang/rust/pull/133829#issuecomment-2590524152
- [ ] Implementation: #133829
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR



### Unresolved Questions


- https://github.com/rust-lang/rust/pull/133829#issuecomment-2600217185

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: ollama
Issue: Add support for the AI HAT+
Labels: feature request

Add support for the new AI HAT+ that can be added on to Raspberry Pi 5 [info here](https://www.raspberrypi.com/products/ai-hat/) to enable speedups.
Repository: PowerToys
Issue: Hotkey to Refresh Connections in Mouse Without Borders
Labels: Needs-Triage

### Description of the new feature / enhancement

It would be useful to have a Hotkey command to refresh connections in Mouse Without Borders. I have noticed that when my laptop connects or disconnects from the VPN I need for work, MWB loses connection to it and I have to go into the settings to hit the Refresh Connections button. It happens frequently enough that the extra steps add up to a lot of time.

### Scenario when this would be used?

I have noticed that when my laptop connects or disconnects from the VPN I need for work, MWB loses connection to it and I have to go into the settings to hit the Refresh Connections button. It happens frequently enough that the extra steps add up to a lot of time. The Mouse Without Borders functionality works well in both the VPN connected or disconnected states, but the systems lose connection with each other when switching between them (including if there is any disruption and it automatically reconnects.)

### Supporting information

I haven't experimented with other VPN clients, but with the Cisco AnyConnect client, I have this behavior. I suspect it will happen with other VPN clients as well.
Repository: godot
Issue: Visual shader editor stuck in pan mode
Labels: bug,topic:editor,topic:input

### Tested versions

Godot v4.3.stable 
v4.4.beta1.official [d33da79d3]

### System information

Fedora Linux 41 (KDE Plasma) - Wayland - Vulkan

### Issue description

If you pan with Space + left mouse button while mouse is over a interactive control you get stuck in pan mode.
You can get back to the normal state by pressing space again. 

https://github.com/user-attachments/assets/bb987a8e-a35b-45f5-bd4a-afa978f8d067


### Steps to reproduce

Create a visual shader
Add some node with controls that can be interacted with
Place mouse cursor over the control
Use Space + left mouse button to pan


### Minimal reproduction project (MRP)

[shader.zip](https://github.com/user-attachments/files/18510225/shader.zip)
Repository: godot
Issue: Wayland Cursor custom image doesn't update when using Image instead of Texture2D
Labels: bug,platform:linuxbsd,topic:porting,topic:input

### Tested versions

- v4.4.beta.gentoo [4ce466d7f]

### System information

Linux Gentoo using Wayland

### Issue description

When using the Wayland DisplayServer you can only update the custom mouse cursor once if you are using Image instead of Texture2D resources and the images have the same hotspot.

The function `Input.set_custom_mouse_cursor` claims that it is okay to use either an Image or a Texture2D as a custom cursor image. The caching code in `DisplayServerWayland::cursor_set_custom_image` checks for cursor reuse using "get_rid()" on the provided resource. Since an Image does not have a RID, any image will always enter the branch `// We have a cached cursor. Nice.`.

Bug is visible since #96647 was fixed, although the underlying bug was already older than that.

### Workarounds
* Use Texture2D instead of image resources - may cause undesired overhead to convert back to image
* Reset the cursor in between - may cause cursor flickering
* Move the hotspot locations to force a cache miss - unwanted extra work to make images suitable with different hotspots

### Steps to reproduce

* Force editor and game to use the Wayland display server
* Make sure the referenced `img1` and `img2` are imported as Image and not as Texture.

```gdscript
Input.set_custom_mouse_cursor(img1, Input.CURSOR_ARROW)
# Correctly shows img1 as the cursor
Input.set_custom_mouse_cursor(img2, Input.CURSOR_ARROW)
# Still shows img1 as the cursor
```

### Minimal reproduction project (MRP)

[wayland-cursor-reproducer.zip](https://github.com/user-attachments/files/18510307/wayland-cursor-reproducer.zip)
Repository: neovim
Issue: More structured health checks
Labels: checkhealth

### Problem

Neovim provides a `:checkhealth` feature for plugins and Neovim itself to show "self-diagnostics". This allows users to
1. quickly see detectable problems and misconfigurations ("runtime is missing", "parsers are broken", "server not executable", "TERM misconfigured")
2. information about the internal state (loaded treesitter parsers, active and inactive LSP configurations)

While this information is very useful for bug reports and understanding why your Neovim behaves as it does, the increasing amount of information (especially around (nvim-)treesitter and LSP) makes it increasingly hard to navigate. So we need to add ways of structuring and navigating this information.


### Expected behavior

There are several (independent) improvements that can be made, roughly in order of ascending complexity:

* [ ] Add a table of contents (`gO`, already supported for `help` buffers, which `checkhealth` inherits from).
* [ ] Add section navigation via `]]` (which would also be useful for `help` buffers)
* [ ] Add color to section headers (white/green for "all clear" or info only, orange if the section contains a warning, red if the section contains an error)
* [ ] Add folding to sections (foldtext should be section header, colored as above). This is a bit controversial but a net win if
   - `foldenable` is respected (so people can opt out of all folding);
   - sections are either all folded or not folded by default;
   - folding is not enabled if only a single section is shown (e.g., `:check lsp`).
* [ ]  Only show the most important, actionable, health checks by default and reserve the full information for an "extended view" that can be toggled by either pressing, say, `D` in a `checkhealth` buffer or calling `:checkhealth!`.
(This could be implemented by adding a flag to `vim.health.info` to indicate that the message should only be shown in extended mode. Bonus points for evaluating this lazily -- "Treesitter parsers", I'm thinking of you!)
Repository: go
Issue: runtime: SIGBUS in go/types in TestVet
Labels: NeedsInvestigation,compiler/runtime

```
#!watchflakes
default <- pkg == "cmd/vet" && test == "TestVet/method"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8725028079657686513)):

    === RUN   TestVet/method
    === PAUSE TestVet/method
    === CONT  TestVet/method
        vet_test.go:195: error check failed: 
            Unmatched Errors:
            unexpected fault address 0x10769e80
            fatal error: fault
            [signal SIGBUS: bus error code=0x2 addr=0x10769e80 pc=0x10769e80]
            goroutine 1 gp=0xc000002380 m=2 mp=0xc00004c808 [running]:
            runtime.throw({0x10663d90?, 0x28?})
    ...
            	../../runtime/proc.go:435 +0xce fp=0xc000043f38 sp=0xc000043f18 pc=0x1038d26e
            runtime.gcBgMarkWorker(0xc0000ca620)
            	../../runtime/mgc.go:1423 +0xe9 fp=0xc000043fc8 sp=0xc000043f38 pc=0x10339389
            runtime.gcBgMarkStartWorkers.gowrap1()
            	../../runtime/mgc.go:1339 +0x25 fp=0xc000043fe0 sp=0xc000043fc8 pc=0x10339265
            runtime.goexit({})
            	../../runtime/asm_amd64.s:1700 +0x1 fp=0xc000043fe8 sp=0xc000043fe0 pc=0x10394601
            created by runtime.gcBgMarkStartWorkers in goroutine 1
            	../../runtime/mgc.go:1339 +0x105
    --- FAIL: TestVet/method (4.09s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: Cupertino navbars apply too much top padding within a sheet
Labels: a: fidelity,f: cupertino,P2,team-design,triaged-design

When using a navbar within a CupertinoSheetRoute, the navbar applies unnecessary safe area padding at the top. Ideally the safe area padding would be reduced either by default or easily done manually.

| Expected | Actual |
| --- | --- |
| <img width="206" alt="Image" src="https://github.com/user-attachments/assets/c5711111-ca66-4f70-b6af-d0bdc1fa545d" /> | <img width="200" alt="Image" src="https://github.com/user-attachments/assets/237459e7-ae05-426c-ad3f-0a711caf630c" /> |




See comments [here](https://github.com/flutter/flutter/pull/157568#issuecomment-2592535332) and [here](https://github.com/flutter/flutter/pull/157568#issuecomment-2590955571).
Repository: flutter
Issue: [SwiftPM] Improve error message if app needs to raise its minimum deployment
Labels: platform-ios,tool,P3,team-ios,triaged-ios

### Background
Swift Package Manager strictly enforces a package's platform requirements. For example, if your Flutter iOS app has a minimum deployment of iOS 12.0 and it depends on a plugin that requires iOS 15.0, you'll get an error like:

```
Failed to build iOS app
Target Integrity (Xcode): The package product 'my-plugin' requires minimum platform version 15.0 for the iOS platform, but this target supports 12.0
```

### Solution

We should improve this error message. For example:

```
Failed to build iOS app
The plugin 'my_plugin' requires iOS 15.0, but this app supports 12.0.

To use 'my_plugin', update your app's minimum deployment to 15.0:

1. Open `ios/Runner.xcworkspace` using Xcode
2. Open Runner target > Build Settings > Minimum Deployments
3. Set iOS to `15.0.`
```
Repository: tauri
Issue: [feat] Improve mobile app version management
Labels: type: feature request

### Describe the problem

For iOS, Tauri synchronizes both `CFBundleVersion` and `CFBundleShortVersionString` with the version property in `tauri.conf.json`. A similiar issue exists for Android builds.

This means we cannot distinguish between the _user-facing_ version visible in stores and the _developer-facing_ build version. [Expo](https://docs.expo.dev/build-reference/app-versions/) for React Native handles this well by defining the following configuration properties:

| Property    | Description |
| -------- | ------- |
| `version` | The user-facing version visible in stores. On Android, it represents `versionName` name in android/app/build.gradle. On iOS, it represents `CFBundleShortVersionString` in Info.plist. |
| `android.versionCode` | The developer-facing build version for Android. It represents `versionCode` in android/app/build.gradle. |
| `ios.buildNumber` | The developer-facing build version for iOS. It represents `CFBundleVersion` in Info.plist. |

### Describe the solution you'd like

Implement a similiar approach in `tauri.config.json` for defining the _developer-facing_ build version for Android/iOS.

### Alternatives considered

N/A

### Additional context

#10944.