sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Color issues
Labels: Needs-Triage,Product-CropAndLock

### Description of the new feature / enhancement

파워토이의 "자르기 및 잠금" (Snip and Lock) 기능을 사용하고 있습니다. 이 기능은 화면을 자르고 나서 다른 작업을 하거나 동영상을 따로 볼 수 있는 유용한 도구입니다. 그러나, 이 기능을 사용한 후 자른 화면의 윈도우 테두리 색상이 윈도우 테마에서 지정한 어두운 색상과 다르게 너무 밝은 색으로 나타나는 문제가 발생하고 있습니다.

현재 윈도우 테마에서는 어두운 색상을 설정해두었지만, "자르기 및 잠금" 기능을 사용하면 자른 화면의 테두리 색상이 밝은 흰색으로 표시됩니다. 이 부분을 사용자가 지정한 색상으로 조정할 수 없거나, 윈도우 테마와 일치하도록 자동으로 맞춰지지 않아 불편을 겪고 있습니다.

이 문제를 해결하거나, 사용자 지정 색상에 맞게 테두리 색상이 변경될 수 있는 방법이 있다면 안내해 주시면 감사하겠습니다.

I am using the "Snip and Lock" feature of PowerToys. This feature is a useful tool for cropping parts of the screen and continuing other tasks or watching videos separately. However, after using this feature, I encountered an issue where the window border color of the cropped screen appears in a very bright color, which does not match the dark color set in my Windows theme.

I have set a dark color in the Windows theme, but after using the "Snip and Lock" feature, the border color of the cropped screen appears as a bright white color. I am unable to adjust this to the color I have set, and the color does not automatically match my Windows theme, causing some inconvenience.

I would appreciate it if there is a way to resolve this issue or adjust the border color to match the user-defined theme color.

### Scenario when this would be used?

파워토이의 "자르기 및 잠금" (Snip and Lock) 기능을 사용하고 있습니다. 이 기능은 화면을 자르고 나서 다른 작업을 하거나 동영상을 따로 볼 수 있는 유용한 도구입니다. 그러나, 이 기능을 사용한 후 자른 화면의 윈도우 테두리 색상이 윈도우 테마에서 지정한 어두운 색상과 다르게 너무 밝은 색으로 나타나는 문제가 발생하고 있습니다.

현재 윈도우 테마에서는 어두운 색상을 설정해두었지만, "자르기 및 잠금" 기능을 사용하면 자른 화면의 테두리 색상이 밝은 흰색으로 표시됩니다. 이 부분을 사용자가 지정한 색상으로 조정할 수 없거나, 윈도우 테마와 일치하도록 자동으로 맞춰지지 않아 불편을 겪고 있습니다.

이 문제를 해결하거나, 사용자 지정 색상에 맞게 테두리 색상이 변경될 수 있는 방법이 있다면 안내해 주시면 감사하겠습니다.

I am using the "Snip and Lock" feature of PowerToys. This feature is a useful tool for cropping parts of the screen and continuing other tasks or watching videos separately. However, after using this feature, I encountered an issue where the window border color of the cropped screen appears in a very bright color, which does not match the dark color set in my Windows theme.

I have set a dark color in the Windows theme, but after using the "Snip and Lock" feature, the border color of the cropped screen appears as a bright white color. I am unable to adjust this to the color I have set, and the color does not automatically match my Windows theme, causing some inconvenience.

I would appreciate it if there is a way to resolve this issue or adjust the border color to match the user-defined theme color.

### Supporting information

_No response_
Repository: rust
Issue: Forbid disabling SSE on x86 targets that have SSE in their "baseline"
Labels: O-x86_64,T-compiler,C-discussion,A-target-feature,O-x86_32

Passing `-Ctarget-feature=-sse` on an x86-64 target currently produces an ugly [LLVM error](https://rust.godbolt.org/z/3j8rnfrzP).
Doing the same on a x86-32 target leads to [unsound floating-point behavior](https://github.com/rust-lang/rust/issues/114479).

Therefore, I think we should deprecate and eventually fully forbid toggling the `sse`/`sse2` target features on x86 targets, except for those targets that do not have these features to begin with (e.g. `i586-unknown-linux-gnu`).

I am implementing some machinery [here](https://github.com/rust-lang/rust/pull/133099) that could help with that, but properly implementing this will be tricky since one can also [use `-Ctarget-cpu`](https://rust.godbolt.org/z/vaGscs6q1) to disable these target features.

Once this is implemented, we have some options for improving the Rust ABI on these targets as well:
- on x86-32, we could use SSE registers to return float values, instead of `PassMode::Indirect`
- on all x86 targets, we could pass SIMD vectors of up to 128 bits in registers rather than indirectly

[Here](https://github.com/rust-lang/rust/issues/114479#issuecomment-2082686372), compiler team triage decided "Current Tier 1 x86 targets require SSE-based floats at minimum". The concrete proposal above got MCP'd in https://github.com/rust-lang/compiler-team/issues/808.

### Open questions

How do we best implement this? It's non trivial since `-Ctarget-cpu` can alter the `sse`/`sse2` feature gates, so our usual approach of just checking which target features got toggled with `-Ctarget-feature` does not work.

To make things worse, the way we control whether `sse`/`sse2` is available in the "basline" is via the `base.cpu` field, not via the explicit list of target features, so if we want to do things "only if the baseline has SSE", that's non-trivial to implement. Maybe we should just add a `bool` field to the target spec that directly controls "use SSE registers for Rust ABI" or "requires SSE registers" or so?

Cc @bjorn3 @workingjubilee @Amanieu
Repository: godot
Issue: Shader failing to compile on exported projects in Android web
Labels: bug,platform:web,platform:android,needs testing,topic:shaders

### Tested versions

Found this bug on projects built and exported using Godot v4.3.stable.official [77dcf97d8]

### System information

Android Web Browser (trying to run exported Godot project)

> **Note:** I first had this issue reported on a Samsung phone. I was able to reproduce it and copy the error log on my Amazon Fire HD 10 using the Kiwi browser.

### Issue description

I have a game that runs fine on desktop web browsers. But i'm running into an issue on Android web browsers. I have a TextureRect that uses a shader to display the main game world. The shader fails to compile and so the TextureRect is just black on Android web browsers. ~~You should be able to see the issue on the game here: https://ramblingstranger.itch.io/quantum-rift~~

***Edit:** I've figured out a workaround for my game for now, so you shouldn't actually see any issues at the link above. You can still see the issue in the MRP linked below.*

### MRP and steps to reproduce

I've also created an MRP. The MRP has two TextureRects. The one without a shader displays fine (on the left), but the one with a shader doesn't display (on the right). You can find the MRP here:
* https://github.com/ramblingstranger/shader-issue-mrp
* https://ramblingstranger.github.io/shader-issue-mrp/

In the MRP, the shader that i am using on the TextureRect is just this:
```glsl
shader_type canvas_item;

uniform sampler2D image;

void fragment()
{
	vec4 pixel = texture(image, UV);

	// This line causes the problem
	vec4[1] pixels = {pixel};

	COLOR = pixels[0];
}
```

> **Note:** The issue goes away if i change the fragment function to this:
> ```glsl
> void fragment()
> {
> 	vec4 pixel = texture(image, UV);
> 	COLOR = pixel;
> }
> ```

I used the Kiwi browser to access a dev console on Android and found the following error:
```
USER ERROR: CanvasShaderGLES3: Fragment shader compilation failed:
0:163 S0032: no default precision defined for variable 'vec4[1]'
   at: _display_error_with_code (drivers/gles3/shader_gles3.cpp:254)
USER ERROR: Method/function failed.
   at: _compile_specialization (drivers/gles3/shader_gles3.cpp:396)
USER WARNING: shader failed to compile, unable to bind shader.
   at: _version_bind_sahder (./drivers/gles3/shader_gles3.h:222)
```

The dev console also spits out the shader that failed to compile. It appears to be the GLSL version of the Godot shader shown above. The part that directly corresponds to the shader i wrote is:
```glsl
{
	vec4 m_pixel=texture(m_image, uv);
	vec4 m_pixels[1]=vec4[1](m_pixel);
	color=m_pixels[0];
}
```
Repository: ollama
Issue: goroutine 7 [running]
Labels: bug,needs more info

### What is the issue?

Hello.

I am testing with olama. Using olama, the embedded model and LLM model are on gpu. As soon as you enter the question, the embedded and LLM models are sequentially performed.
And since we built a web server using streamlit, we have to handle a lot of question inputs. We ran the olama server by adding an option to quickly process a large number of requests using olama. The commands used to run the server are as follows. CUDA_VISIBLE_DEVICE=1 OLAMA_GPU_OVERHEAD=500000000 OLAMA_NUM_PARALLEL=11 OLAMA_KEEP_ALIVE=-1 olama service

Run the streamlit app and access the web server to input and answer questions well. However, at an unspecified time, olama outputs the following message.
The first picture is ollama 0.4.2, and the second picture is a message picture that occurred when using ollama 0.4.6.
In 0.4.2, the answer is not answered only when the error message has occurred, and the next question is generated again. However, after the error message in 0.4.6, the olama lm model is deallocated from gpu memory and the olama server is also stopped. For reference, the same phenomenon as 0.4.6 occurs in all 0.4.3 to 0.4.5.

![image](https://github.com/user-attachments/assets/9a9c44bb-49fc-4273-9ea2-79ac30e84cff)

![image](https://github.com/user-attachments/assets/62c1c181-87c0-4302-ad3b-e3b0e79dd74b)


### OS

Docker

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.4.6, 0.4.2
Repository: PowerToys
Issue: Dynamically resize window based on current focus
Labels: Idea-New PowerToy,Product-Window Manager,Needs-Triage

### Description of the new feature / enhancement

I often use two browser windows side-by-side on a widescreen monitor. I would like to see a feature that lets me define a resizing behavior for the window currently in focus. The adjoining window would shrink accordingly.

Settings To Consider:
- Scaling Direction to scale (up, down, left, right)
- Scaling Length (percentage? points?)
- Activation / Trigger (focus or mouse hover)
- Transition Speed
- Apply to Adjoining (yes/no)
- Apply to All (affecting all windows on the screen)

Note: Multiple profiles might be required.

How To Enable:
Enabled via keyboard shortcut.

Example:
I have 2x windows grouped together side-by-side. I activate the feature using a shortcut. The window currently in focus becomes the "master" and scales outward to 66% screen width (based on my settings). Adjoining windows scale inward at the adjoining edge, keepign the full window in view; any other edges remain static. When the adjoining window comes into focus, it reverts back to its original size, or scales out to 66% screen width if the Apply to Adjoining setting is enabled.

### Scenario when this would be used?

Example Scenarios:
- Side-by-side browser windows that alternate in width to give a wider viewport
- Tiled shells / terminals that auto-expand on focus
- Word documents kept open side-by-side to transfer content or because you have multiple projects and keep them all on a specific virtual desktop. (auto-expanding would display more ribbon options!)

### Supporting information

No additional info available.
Repository: kubernetes
Issue: informer.AddEventHandler: handle.HasSynced always returns false after panic
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

I was testing something roughly like this:

```golang
informer := NewSharedInformer(source, &v1.Pod{}, 1*time.Second)
go informer.RunWithContext(ctx)
require.Eventually(t, informer.HasSynced, time.Minute, time.Millisecond, "informer has synced")

handler := ResourceEventHandlerFuncs{
			AddFunc: func(obj any) {
				panic("fake panic")
			},
		}

handle, err := informer.AddEventHandlerWithContext(ctx, handler, HandlerOptions{})
require.NoError(t, err)
require.Eventually(t, handle.HasSynced, time.Minute, time.Millisecond, "handler has synced")
```

This times out waiting for the handler to sync.

### What did you expect to happen?

`handle.HasSynced` = `ResourceEventHandlerRegistration.HasSynced` should return true eventually.

### How can we reproduce it (as minimally and precisely as possible)?

I'll have a full reproducer in one of my PRs soon.

### Anything else we need to know?

/sig api-machinery


### Kubernetes version

master ~= 1.32
Repository: vscode
Issue: SCM Graph - Add horizontal scrollbar for source control graph
Labels: bug,ux,scm

<!-- ⚠️⚠️ 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. -->
Add horizontal scrollbar to source control graph in the source control panel. It should probably appear automatically if source control graph content doesn't fit into window, like it does in text editors. `shift+scroll` for horizontal scrolling would also be nice. I checked out source control settings but couldn't find any mention of horizontal scrolling. I also haven't found a similar feature request.

Maybe it won't be useful 99% of the time, but once in a while you get assigned to one of *those* projects...
![Image](https://github.com/user-attachments/assets/802ef20f-cea2-4206-a3eb-1beeab4c0c07)
Repository: ant-design
Issue: Form.Item 错误提示信息中新增的additionalDom 未作为参数传给_internalItemRender，导致pro-components中的错误信息跳动
Labels: unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/objective-aj-dhwfyt)

### Steps to reproduce

清空第一个input的数据

### What is expected?

可以将additionalDom 变量传入_internalItemRender 这样 pro-components可以直接使用它

### What is actually happening?

错误信息跳动了

| Environment | Info |
| --- | --- |
| antd | 5.22.2 |
| React | 18.2.0 |
| System | windows |
| Browser | chrome版本 113.0.5672.127（正式版本） （64 位） |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: VSCode freezing during search
Labels: bug,search

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

Version: 1.95.3 (user setup)
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045

Steps to Reproduce:

Scenario 1:
![Image](https://github.com/user-attachments/assets/066e64b5-873d-4808-b298-905b2d62cc12)

Scenario 2:
![Image](https://github.com/user-attachments/assets/3fece497-ecc7-4054-b86a-fd2111b85a1c)
The path in files.includes can be changed to an absolute path. 
![Image](https://github.com/user-attachments/assets/191396fd-3324-4a3e-9862-8b2bb94e0f94)

1. Open the vscode source code project.
2. Open the settings.json file.
3. Search`\((.*\n.*)*\);`and select the regular button.
4. The vscode freezes and a dialog is displayed.
![Image](https://github.com/user-attachments/assets/2468b048-1068-418d-a00d-f58b1a275381)
Repository: ollama
Issue: Add a CORS permissions model into the Ollama UI ("Allow example.com to use Ollama? [Yes] [No]")
Labels: feature request

Lots of AI apps out there solve access to LLM in a few different ways:

- Directly use a hosted model and foot the bill for the user
- Ask the user to provide their own hosted model API key (😬)
- Let the user host the app themselves, providing the API key this way
- Connect with a local model provider like Ollama, but this has several issues today[^1]

I think Ollama is in wide enough circulation that it could create a permissions standard around local model access from the browser. An initial draft of this could be very simple:

The first time a request comes in with an `Origin` value that's never been seen before, hold the request and ask the user with a system notification: "Allow example.com to use Ollama?" If the user chooses to allow, the domain gets added to an allow list, which is used to send a valid CORS header to the incoming request. If the user chooses to deny, add the domain to a deny list which just means the CORS header will not be sent. If the user makes no choice, then time out the request and ask again next time.

This can still be combined with the existing `OLLAMA_ORIGINS` setting so if something is in there it's automatically allowed (except for `*`).

[^1]: The first issue is that the user must run terminal commands to enable CORS. The second one is that unless they use `*` then turning on access for one app will remove access for another (unless they know how to read and combine the list of domains). And finally the third one is that the user will be lazy and pick `*` and now any site in the world can use their local model.
Repository: tauri
Issue: [feat] feature request: allow config open new window (target=blank) behavior when build webview window
Labels: type: feature request

### Describe the problem

Currently, the Tauri application only supports configuring the behavior of opening new windows (target="_blank") using the shell plugin, which defaults to opening new windows in the default browser. It would be highly beneficial to have additional configuration options that allow developers to:

- Open new windows using a Tauri window.
- Open new windows within the current window.

To achieve this currently, we need to inject JavaScript and monitor click events. This approach is not very stable and may cause unexpected behavior by polluting the front-end page

**Rationale**
Providing these configuration options would enhance the flexibility and usability of Tauri applications, allowing developers to better control the user experience and behavior of their app. (some security software will prevent pop up default browser)


Related discussion:
https://github.com/tauri-apps/tauri/discussions/11809
https://github.com/tauri-apps/tauri/issues/1657




### Describe the solution you'd like

To achieve this currently, we need to inject JavaScript and monitor click events. This approach is not very stable and may cause unexpected behavior by polluting the front-end page

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: tailwindcss
Issue: V4 Minification Issue with ::after
Labels: needs reproduction,v4

In v4 beta 1

I had this... 

```CSS
.btn-menu::after {
    @apply absolute -bottom-1.5 block h-0.5 w-0 bg-neutral-200 dark:bg-neutral-700 transition-all content-[''];
}
```

When I compile the npm run build using laravel and vite...
```
import { defineConfig } from 'vite';
import laravel from 'laravel-vite-plugin';

export default defineConfig({
    plugins: [
        laravel({
            input: [
                'resources/css/styles.css',
                'resources/js/custom.js',
                'resources/css/admin.css',
                'resources/js/admin.js'],
            refresh: true,
        }),
    ],
});
```

I get this error:
```
vite v5.4.9 building for production...
✓ 27 modules transformed.
rendering chunks (1)...warnings when minifying css:
▲ [WARNING] Unexpected ")" [css-syntax-error]

    <stdin>:2:62793:
      2 │ ...ion:absolute}.btn-menu:after:is(){background-color:var(--color-n...
        ╵                                    ^
```

This was fine with v3, any idea what I'm doing wrong?
Repository: rust
Issue: Missed optimization in sum of remainders
Labels: A-LLVM,T-compiler,C-optimization

I tried these codes:
```rust
const N: usize = 100000;
#[unsafe(no_mangle)]
fn foo0(n: usize) -> usize {
    // assert!(n > 0);
    if n == 0 {
        return n;
    }
    let s = (0..N).map(|i| i % n).sum();
    s
}
```

```rust
const N: usize = 100000;
#[unsafe(no_mangle)]
fn foo1(n: usize) -> usize {
    // assert!(n > 0);
    if n == 0 {
        return n;
    }
    let mut s = 0;
    let (q, r) = (N / n, N % n);
    if q > 0 {
        s += q * (n - 1) * n / 2;
    }
    if r > 0 {
        s += (r - 1) * r / 2;
    }
    s
}
```
I expected the loop in `foo0` to be optimized away to a result similar to `foo1`.
Repository: PowerToys
Issue: QuickAccent - Toolbar overflow
Labels: Idea-Enhancement,Needs-Triage,Product-Quick Accent

### Description of the new feature / enhancement

![Image](https://github.com/user-attachments/assets/83bda8ef-3e06-4516-9ae1-0d1bb156f229)

In quick accent, when using windows with 125% scaling the toolbar for the character `e` (that has a lot of options when selecting it) the bar goes overboard and I cannot see all the options.

Make it possible for the toolbar to wrap into multiple lines so that we can navigate it (maybe even using up and down arrows).

### Scenario when this would be used?

When the toolbar overflows

### Supporting information

_No response_
Repository: pytorch
Issue: [typing] add `nn.Module` overload type hint to `torch.compile`.
Labels: module: nn,module: typing,triaged

### 🚀 The feature, motivation and pitch

`torch.compile` can be applied to `nn.Module` instances, but [its current type hints do not reflect it](https://github.com/pytorch/pytorch/blob/3c63e76b03737085e2eb2e7fb7163d7ba16986ba/torch/__init__.py#L2364-L2387), which causes all sorts of typing errors:

```python
from typing import reveal_type

import torch

m = torch.nn.Linear(3, 4)
m_compiled = torch.compile(m)
reveal_type(m_compiled)  # Callable[..., Any]
module_instance: torch.nn.Module = m_compiled  # ❌ incompatible type
m_compiled.parameters()  # ❌ unknown attribute
```

Typing `torch.compile` precisely is challenging, due to lack of some features in the typing system like intersection types (https://github.com/python/typing/issues/213). In principle, there should be an overload of the form

```python
@overload
def compile[M: Module](module: M, ...) -> M & OptimizedModule
```

Due to the lack of intersection types, I would propose to annotate as `M`, since users might want to call methods defined on `M`, which raise `unknown attribute` messages currently.

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @ezyang @malfet @xuzhao9 @gramster
Repository: godot
Issue: _get and _set are not called for real properties
Labels: topic:core,topic:gdscript,documentation

### Tested versions

-Reproducible in Godot v4.3.stable, v4.2.stable, 4.0.3.stable, 4.0.stable

### System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - NVIDIA GeForce GTX 1080 Ti (NVIDIA; 31.0.15.3713) - 12th Gen Intel(R) Core(TM) i5-12400F (12 Threads)

### Issue description

When reading or writing real members defined in the class, `_get` and `_set` are ignored, they are only called for custom properties that are returned via `_get_property_list`. The documentation and meaningful special values like `null` suggest that this is not desired behavior.

### Steps to reproduce

```gdscript
extends Control

var num := 5

func _get(property: StringName) -> Variant:
	if (property == "num"):
		return 6
	return null

func _ready() -> void:
	assert(num == 6, "_get is not working on real properties")
```

### Minimal reproduction project (MRP)

[get-bug_repro.zip](https://github.com/user-attachments/files/17958071/get-bug_repro.zip)