sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Unknown C++ exception from OpenCV code from python using QR Detect
Labels: bug,category: objdetect

### System Information

OpenCV version: 4.10.0.82
Operating System / Platform: Windows 10 Version 22H2 (OS Build 19045.5247)
Python 3.9.13

Reproduced in Docker Image as well:
OpenCV version: 4.10.0.84
Operating System / Platform: Ubuntu 24.04.1
Python: 3.12.3

### Detailed description

Particular images are hanging on the call to detect and decode for the QR Code Detector. They run for about 10 minutes and then provide the error: `cv2.error: Unknown C++ exception from OpenCV code` . WIthin the Docker Image described above they run for the same amount of time until throwing a Segmentation Fault. Alternatively, when these images are run through the same call on OpenCV Aruco QR Detector the errors are not encountered. In some cases we have observed that subtle changes to the images will lead to successful runs. Images are attached here.
![053E9D618F012E84FB3029EB83D6246F-sample](https://github.com/user-attachments/assets/e8835270-bbf6-40d2-a263-bab4c34f6349)
![sample_000003](https://github.com/user-attachments/assets/45a5b34d-acd5-43b2-b4fe-66c3fe182bb7)


### Steps to reproduce

```python
qcd = cv2.QRCodeDetector()
img = cv2.imread("Path/To/Image")
retval, decoded_info, points, straight_qrcode = qcd.detectAndDecodeMulti(img)
```

### 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: godot
Issue: Text servers can't be built as extensions
Labels: bug,discussion,topic:buildsystem,topic:gdextension

### Tested versions

4.4.dev [6395450b10d73bc3515763c7bbd1b2f5b7425d10]

### System information

Windows 11

### Issue description

While working on https://github.com/godotengine/godot/pull/100562 I was attempting to confirm the compilation as an extension would work but ran into unrelated problems, two primary ones currently:
* The builsystem fails due to:
```
ImportError: cannot import name 'Ansi' from partially initialized module 'methods' (most likely due to a circular import) (modules\text_server_fb\gdextension_build\methods.py):
  File "modules\text_server_fb\gdextension_build\SConstruct", line 7:
    import methods
  File "modules\text_server_fb\gdextension_build\methods.py", line 6:
    from methods import Ansi
```
  This should be easy to fix by renaming `modules\text_server_fb\gdextension_build\methods.py` to something specific.
* The compilation itself fails due to missing thorvg files, this would likely be due to the SCons file not being up-to-date with changes to the svg module

I can look into fixing the specifics but we should probably evaluate if we want to maintain this functionality as buildable, drop it entirely, or just leave it

### Steps to reproduce

Try to build the extension version of either text server module

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: CavasItem's clip only mode on skewed styleboxes fails to clear.
Labels: bug,topic:rendering,topic:2d

### Tested versions

- Reproducible in: 4.3.stable

### System information

Godot v4.3.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1660 Ti (NVIDIA; 32.0.15.6636) - AMD Ryzen 7 4800H with Radeon Graphics (16 Threads)

### Issue description

![Image](https://github.com/user-attachments/assets/41164166-eda6-4038-a3df-a00eee271200)
![Image](https://github.com/user-attachments/assets/a11a5781-1922-4cc1-8e94-096bc97231e6)

As you can see, the portions of the stylebox outside the bounding box are not being cleared; artifacts of previous frames persist. 

### Steps to reproduce

Create a panel with a flat stylebox. 
Skew the stylebox. 
Put any visible child inside the panel. 

### Minimal reproduction project (MRP)

[panel.zip](https://github.com/user-attachments/files/18186026/panel.zip)
Repository: PowerToys
Issue: Add automatic rename mode when creating a new file type in New+
Labels: Idea-Enhancement,Needs-Triage,Product-New+

### Description of the new feature / enhancement

In **New+**, When a new file type is created from the template, it should _automatically_ enter "**rename** mode" to allow users to immediately rename the file from its default template name. This feature is similar to the Windows built-in behavior and would streamline workflows by eliminating unnecessary steps, such as navigating to the file and manually triggering rename.

### Scenario when this would be used?

This feature would be particularly helpful when users create multiple files in quick succession. Often, new files are named generically (e.g., "New File (1)"), with respect to the template name, and users must manually rename them later. By entering rename mode automatically, users can:
- Avoid creating duplicate, undescriptive filenames.
- Save time by renaming files immediately upon creation.

This is especially beneficial for power users managing large projects with frequent file additions.

### Supporting information

_No response_
Repository: godot
Issue: Stream sync play and seek is setting wrong position on certain cases
Labels: bug,topic:audio,regression

### Tested versions

- Reproducible in: 4.3.stable and later
- Not reproducible in: 4.2.stable and earlier

### System information

Godot v4.3.stable - Windows 10.0.19045 - GLES3 (Compatibility) - Intel(R) HD Graphics 5500 (Intel Corporation; 20.19.15.5107) - Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz (4 Threads)

### Issue description

If you have multiple streams on AudioStreamSynchronized with different lengths, start and seek methods will unsync the sound when position set is higher than one of the stream's length.

There's an opened [PR](https://github.com/godotengine/godot/pull/100534) to fix it.

### Steps to reproduce

- Add a AudioStreamSynchronized to an AudioPlayer
- Add a stream with a length of 16 seconds
- Add another stream with a length of 32 seconds
- Call audio_player.play(20) or audio_player.seek(20)

### Minimal reproduction project (MRP)

You can reproduce this issue [here](https://github.com/adriano-sudario/godot_streams_issues_mrp) with detailed informations running the scene _res://bugs/stream_sync_play_and_seek_not_setting_position_right_sometimes.tscn_
Repository: go
Issue: runtime: use runtime.AddCleanup in the standard library
Labels: NeedsFix,compiler/runtime

AddCleanup has been added to the runtime (#67535). We should use runtime.AddCleanup instead of runtime.SetFinalizer in the standard library wherever it is possible.

@mknyszek
Repository: flutter
Issue: Question for the engine team about making copyPixelBuffer/textureFrameAvailable more explicit about call patterns
Labels: engine,P3,team-engine,triaged-engine

From https://github.com/flutter/packages/pull/7466#discussion_r1871942627:

"I think the next step is to file an issue to explore with the engine team whether making the copyPixelBuffer/textureFrameAvailable more explicit about call patterns (e.g., saying that calls will not be more frequent than ~the screen refresh rate) is something the engine team is comfortable with, so we know whether or not we need to build limiting logic at the plugin level."

In #7466 there is little issue that it assumes that `copyPixelBuffer` will not be called more often than screen refresh rate. It is not very critical for functionality but it would not be optimal if that did not hold. Current implementation holds this assumption but that is not documented.
Repository: ollama
Issue: Setup window scaling is bigger than expected.
Labels: bug

### What is the issue?

It's probably not causing any problems during usage but this kinda bothers me on each update. The setup window, text and buttons are larger than expected. I'm currently on `0.5.4` but same exists on previus versions. I have dual monitor setup. Both 1080p and never used scaling (on default %100). The size difference is pretty obvious in eye but here is a screenshot:

![image](https://github.com/user-attachments/assets/0b2913c4-87af-4465-bb89-c384cfa15e07)
Right window for reference. All setup programs I have ever seen is in size of it.

### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.5.4
Repository: godot
Issue: [GDScript] Cannot declare variable in lambda with the same name as parent scope
Labels: discussion,topic:gdscript

### Tested versions

Godot v4.3.stable - Windows 10.0.26100 - Vulkan (Forward+) - integrated Intel(R) Iris(R) Xe Graphics (Intel Corporation; 31.0.101.5595) - 13th Gen Intel(R) Core(TM) i5-1340P (16 Threads)

### System information

N/A

### Issue description

When creating a GDScript function containing a lambda in it, both with the same variable name, this will result in a compile error.

### Steps to reproduce

Create the following script below. It will result in the following error:

```
Parse Error: There is already a variable named "result" declared in this scope.
```

### Minimal reproduction project (MRP)

```gdscript
func test() -> void:
	var result := []
	var lambda := func () -> void:
		var result := []
```
Repository: transformers
Issue: InternVL is ExecuTorch Compatible
Labels: Feature request,ExecuTorch

### Feature request


### Feature request

Enable OpenGVLab/InternVL2-1B to ["Export to ExecuTorch"](https://github.com/huggingface/transformers/issues/32253) workflow


### Motivation

See details in #32253

### Your contribution

model enablement
Repository: ant-design
Issue: Slider: allow "included=true" to begin from a specified value
Labels: unconfirmed

### What problem does this feature solve?

Currently `included=true` always starts from left-most (right-most if reversed) edge. Currently there is no way to start the track fill to begin from a middle of the range. For example if you have a range from -10 to 10 and the default value is 0 then you may want to include the track starting from zero and going toward the node.

### What does the proposed API look like?
```react-js
<Slider
  min={-10}
  max={10}
  defaultValue={0}
  included={true}
  includedStart={0}    <-- This is the proposal
  />
```
<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: angular
Issue: Angular router leaks components and their DOM Elements
Labels: memory leak,area: router

### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

No

### Description

Every time we navigate to a component and route away asynchronously, the Angular router is leaking the component.
This is causing severe memory issues in production code.

Steps to reproduce:
1. `git clone git@github.com:arobinson/angular-router-leak.git`
2. `pnpm install`
3. `ng serve`
4. Open http://localhost:4200/homepage in Google Chrome (or Microsoft Edge)
5. Open the chrome developer tools
6. Open the "Memory" tab
7. Take a heap snapshot
8. Filter for "andrew", verify nothing is found
9. Close the chrome developer tools
10. Click "Launch Standalone"
11. Click "Close" (it will navigate after a 2 second delay)
12. Repeat steps 10 & 11 a few times
13. Reopen the chrome developer tools
14. Open the "Memory" tab
15. Take a heap snapshot
16. Filter for "andrew", notice that the DOM element has been orphaned and will not be Garbage Collected. 

For larger components this ends up leaking over 50MB of RAM per navigation in our application.

![Image](https://github.com/user-attachments/assets/088b0baf-d795-410b-8766-efd829680f94)

Now see that somehow the problem is different with a synchronous navigation:
1. Reload the browser to clear the memory
2. Open dev tools
3. Click "Launch Standalone" again
4. This time click "Close Synchronously"
5. Repeat steps 3 & 4 a few times
15. Take a heap snapshot
16. Filter for "andrew", notice that only the last DOM element that was routed to is detached. So there is still a memory issue, but thankfully it does not grow every time we route.
![Image](https://github.com/user-attachments/assets/586b16a5-2339-438e-8d32-9977eb49d55f)


### Please provide a link to a minimal reproduction of the bug

https://github.com/arobinson/angular-router-leak

### Please provide the exception or error you saw

```true
Detached / Leaked DOM elements and their components
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 18.2.1
Node: 22.11.0
Package Manager: pnpm 9.9.0
OS: darwin arm64

Angular: 18.2.2
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1900.3
@angular-devkit/build-angular   18.2.1
@angular-devkit/core            19.0.3
@angular-devkit/schematics      19.0.3
@angular/cli                    18.2.1
@schematics/angular             19.0.3
rxjs                            7.8.1
typescript                      5.5.2
zone.js                         0.14.10
```

### Anything else?

_No response_
Repository: go
Issue: x/pkgsite: code example format request returns HTTP 405 method not allowed error
Labels: help wanted,NeedsInvestigation,pkgsite

<!--
Please answer these questions before submitting your issue. Thanks!

If you would like to have your package removed, please file an issue at https://golang.org/s/pkgsite-package-removal.
-->
 
### What is the URL of the page with the issue?
 https://pkg.go.dev/net/url#Values.Encode (click the "Format" button)
 
 
### What is your user agent?
 Chrome on Windows
<!-- 
You can find your user agent here:
https://www.whatismybrowser.com/detect/what-is-my-user-agent
-->
 
 
 
### Screenshot
 
<!--
Please paste a screenshot of the page.
-->
 
<img width="1912" alt="image" src="https://github.com/user-attachments/assets/64eb69b9-a154-4cc5-a0e7-5a39913cc755" />

 
 
### What did you do?
 
<!--
If possible, provide a recipe for reproducing the error.
-->
 Clicked the Format button for the code example
 
 
### What did you expect to see?
 Formatted code
 
 
### What did you see instead?
An HTTP 405 error response
Repository: vscode
Issue: Selected tab underline thickness is hard to see
Labels: feature-request,workbench-tabs

<!-- ⚠️⚠️ 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 would like there to be a way to customize the active tab underline thickness. The current 1px thickness is difficult to notice. I think 4px makes sense.

## Existing tab UI

It's hard to tell which tab is selected, especially in light themes where a thin dark line isn't generally noticeable.

![Image](https://github.com/user-attachments/assets/57a34cb1-eda7-4b78-a8b6-cec2d4e5b23f)

## Tab UI suggestion

There's plenty of room to add a 4px line, which fits with the [WCAG focus](https://www.w3.org/WAI/WCAG21/Understanding/focus-visible) suggestion of using color the size of twice the perimeter of the shape being outlined. This is both easy to see and aesthetically pleasing, in my opinion. This isn't the same thing as component focus, but if it's good enough for focus, I think it should be good enough for active state.

![Image](https://github.com/user-attachments/assets/60ef8177-2a34-4034-b82b-817ecbadfe8c)

## Other small underlines

The top/bottom docked activity bar has the same issue

![Image](https://github.com/user-attachments/assets/d164f3c3-91a9-4080-bf40-dd7f477099ba)

As do the tabs in the panel and in the terminal

![Image](https://github.com/user-attachments/assets/1d75756d-a990-4269-855a-af308a50a1eb)

![Image](https://github.com/user-attachments/assets/e934feec-9d48-4434-8dd0-3a2b9c26006c)


## Other programs

WebStorm uses a 4px border which is easy to see.

![Image](https://github.com/user-attachments/assets/9ae34c3d-2ad5-4d1a-9cb5-ef04b178bc1f)


## Other GitHub issues

A similar previous request was locked (due to inactivity?) https://github.com/microsoft/vscode/issues/130394
Repository: godot
Issue: Alt-tabbing doesn't switch focus to different window
Labels: bug,topic:editor,needs testing

### Tested versions

4.4 dev6

### System information

Godot v4.4.dev6 - Windows 10.0.19045 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated AMD Radeon RX 580 2048SP (Advanced Micro Devices, Inc.; 31.0.21921.1000) - Intel(R) Core(TM) i5-7500 CPU @ 3.40GHz (4 threads)

### Issue description

When switching from script editor to undocked shader editor, pressing common shortcuts (undo, copy & paste) are still performed in the script editor. This is because alt-tabbing doesn't switch focus to shader editor, I need to click on the shader editor to completely switch the focus. Alt-tabbing just brings up the shader editor without switching the focus to it.

This isn't an issue when switching from shader editor to script editor.

### Steps to reproduce

open script editor and undock shader editor. write something in script editor, switch to shader editor and press ctrl+a. everything in script editor should be selected.

### Minimal reproduction project (MRP)

new project
Repository: rust
Issue: Equality constraints break type resolution
Labels: C-bug,T-types,needs-triage

<!--
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.
-->

Imagine a trait for serialization (AsRaw). I'm trying to make a trait for wrappers that serialize into the same encoding as their inner type. I tried this:

```rust
trait AsRaw {
    type Raw;
}

trait WrapperTrait: AsRaw {
    type Inner: AsRaw<Raw = Self::Raw>;
}

#[repr(u32)]
enum Foo {
    Bar = 1,
    Baz = 2,
}

impl AsRaw for Foo {
    type Raw = u32;
}

fn noop1<P: WrapperTrait>(x: <P::Inner as AsRaw>::Raw) -> <P as AsRaw>::Raw {
    x
}

fn noop2<P: WrapperTrait<Inner = Foo>>(x: <P::Inner as AsRaw>::Raw) -> <P as AsRaw>::Raw {
    // ERROR: mismatched types
    x
}

fn noop3<P: WrapperTrait<Inner = Foo>>(x: <P::Inner as AsRaw>::Raw) -> <P as AsRaw>::Raw {
    noop1::<P>(x)
}
```

For some reason, `noop2()` fails to compile, even though `noop1()` (a strictly more general function) compiles successfully. Furthermore, `noop3()` (which has the same exact signature as `noop2()`) compiles successfully, taking advantage of `noop1()`.

Providing a specific value for an associated type seems to cause the compiler to "forget" certain bounds on the associated type, at least while checking type equality.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: aarch64-apple-darwin
release: 1.83.0
LLVM version: 19.1.1
```

Nightly has the same behavior.

Error message:

```
$ RUST_BACKTRACE=1 cargo build                                                                              02:53:57 PM
   Compiling equality-bug v0.1.0 (/Users/jacobgreenfield/Downloads/equality-bug)
error[E0308]: mismatched types
  --> src/main.rs:25:5
   |
23 | fn noop2<P: WrapperTrait<Inner = Foo>>(x: <P::Inner as AsRaw>::Raw) -> <P as AsRaw>::Raw {
   |                                                                        ----------------- expected `<P as AsRaw>::Raw` because of return type
24 |     // ERROR: mismatched types
25 |     x
   |     ^ expected associated type, found `u32`
   |
   = note: expected associated type `<P as AsRaw>::Raw`
                         found type `u32`
   = help: consider constraining the associated type `<P as AsRaw>::Raw` to `u32` or calling a method that returns `<P as AsRaw>::Raw`
   = note: for more information, visit https://doc.rust-lang.org/book/ch19-03-advanced-traits.html

For more information about this error, try `rustc --explain E0308`.
error: could not compile `equality-bug` (bin "equality-bug") due to 1 previous error
```
Repository: ui
Issue: [feat]: Switch to `gap-XX` instead of `space-y-XX`
Labels: area: request

### Feature description

Tailwind `gap-XX` is the proper way to space elements within `flex` or `grid` elements. 

We should refactor the codebase and switch every `space-x-XXX` or `space-y-XXX` to `gap-XXX` when appropriate. 

### Affected component/components

_No response_

### Additional Context

The downside of using `space-y-XX` is that it's hard for the user to override if changed needed for a single child.

It will require the `!important` flag to override the complex styling applied to the children by the `space-y` utils.

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: kubernetes
Issue: Missing imports using register-gen since v0.32.0
Labels: sig/api-machinery,kind/regression,triage/accepted

I tried the register-gen and the imports `k8s.io/apimachinery/pkg/runtime` and `k8s.io/apimachinery/pkg/runtime/schema` are missing with the version 0.32.0.
This is due to the dependency `k8s.io/gengo/v2` being updated after the merge if this PR: https://github.com/kubernetes/gengo/pull/277. The field `FormatOnly` is set to true, so the insertion/deletion of imports is disabled.

I could provide a fix for this issue. I am just not sure if it should be fixed directly in register-gen (by adding the imports in the code generator), or if that change should be reverted in the `k8s.io/gengo/v2` project.
Repository: go
Issue: testing/synctest: "all goroutines in bubble are blocked" should list blocked goroutines
Labels: NeedsInvestigation

When all the goroutines in a synctest bubble are durably blocked and no progress can be made, synctest.Run panics. This is essentially a more limited version of the runtime's fatal error "all goroutines are asleep - deadlock!".

Currently, when this panic occurs in a test, by default you see a stack trace for the goroutine which called synctest.Run, but not for any other goroutines. This isn't especially useful. You can set GOTRACEBACK=all to see more stacks, but you shouldn't have to.

I think that ideally in this case you'd get stack traces for all goroutines in the bubble causing the panic, but not for anything else.

I'm not sure yet what the right way to implement this is: Should the panic from synctest.Run contain the relevant stack traces? Should synctest.Run print the stacks itself before panicing? Should the testing package detect the synctest.Run panic and handle printing the relevant stacks itself?
Repository: vscode
Issue: Expanding references in quick chat should grow picker
Labels: bug,quick-chat

https://github.com/user-attachments/assets/aad8fac3-f497-4e67-9c54-f43afe7bb8df

originally internally reported by @bpasero
Repository: vscode
Issue: Sticky scroll lines in the diff editor don't fully extend horizontally
Labels: under-discussion,editor-sticky-scroll

repro:
- open diff editor to check changes for a commit
- scroll one of the diff lines to a point where it is at the top of the viewport (where the sticky elements would be)
- 🐛 see the diff peeking through between the sticky line and scroll bar

![Image](https://github.com/user-attachments/assets/2bd61b2e-6a9b-481b-97a3-d1bf549f8b77)
Repository: flutter
Issue: PR opened pre-monorepo merge but rebased to AFTER it scheduling the wrong presubmit builds
Labels: team-infra,monorepo

https://github.com/flutter/flutter/pull/160482

It's also scheduling framework builds immediately.