sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: Support cursorline_hl_group for diagnostic signs
Labels: enhancement,highlight,diagnostic

### Problem

Currently, for `vim.diagnostic` we may configure `numhl` and `linehl` properties. These configuration values are "forwarded" to `nvim_buf_set_extmark()`'s `number_hl_group` and `line_hl_group` options. However, `cursorline_hl_group` is a valid option to `nvim_buf_set_extmark` as well, and is necessary to get a coherent cursorline extending through the signcolumn. 

Below is a picture of the problem: (We desire for the background of the sign to take on the CursorLineSign background as well.

<img width="342" alt="Screenshot 2024-09-01 at 1 37 58 PM" src="https://github.com/user-attachments/assets/ede5b398-2d77-45ec-b3d2-08a43b89cd24"> 

### Expected behavior

Proposed solution: we add `culhl` configuration property for `vim.diagnostic.config({})`, mapping diagnostic severity to the highlight group used for the sign when the cursorline is on the line. Just like `numhl` and `linehl`, we forward this value to `cursorline_hl_group` option of `nvim_buf_set_extmark()` here:

https://github.com/neovim/neovim/blob/master/runtime/lua/vim/diagnostic.lua#L1455-L1461

My personal opinion is this is a small, low-cost change that does not add complexity to the codebase. Please consider!

Gitsigns.nvim added support for culhl, so this is the last frontier for me to get that nice coherent cursorline :]
Repository: godot
Issue: Newly instantiated PointLight2D nodes set to Mix blend mode only render on sprites present in scene at spawn time.
Labels: bug,topic:rendering,topic:2d

### Tested versions

- Reproducible in both versions I tried: 4.2.1 and 4.3stable.

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2080 (NVIDIA; 32.0.15.5599) - Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 Threads)

### Issue description

A newly instantiated PointLight2D node using Mix blend mode will only render on CanvasItem textures that are present in the scene at the time of its spawn. Either instantiating a pre-saved scene with a point light or creating PointLight2D.new() both deliver similar results.

Changing the light blend mode to Add fixes the issue, PointLight2D's will now render on every sprite, but using Add blend mode piles up brightness in an undesirable way for my project.

I created a test project in both Godot 4.2 and 4.3 with the same result. I instantiate moving sprites one at a time with normal-mapped CanvasItem textures. After each sprite a new PointLight2D is created and tied to its position. (I've tried creating a single scene with both sprite and point light inside which causes the same issue.)

The first sprite to spawn will only render lights that have been created after it. It renders all future lights, while the last sprite will render only the single light created just after it.
![2dLightTest](https://github.com/user-attachments/assets/717a936c-5bc7-41b8-a151-8be67084d10a)

### Steps to reproduce

- Create a CanvasModulate node set to black.
- Instantiate one or more Sprite2Ds with a normal map set in its CanvasItem texture.
- Instantiate a new PointLight2D, add a texture and set blend mode to Mix.
- Instantiate one or more new Sprite2Ds.
- The second set of Sprite2Ds do not accept light from the PointLight2Ds created before them.

### Minimal reproduction project (MRP)

[LightTest.zip](https://github.com/user-attachments/files/16830492/LightTest.zip)
Repository: PowerToys
Issue: Allow us to uninstall unused feature and redownload them when we need them
Labels: Needs-Triage

### Description of the new feature / enhancement

I love all the features, but I don't use them very often, so I usually disable them. The issue is that the software has become quite large (almost 1GB). My ambitious feature request is to allow users to delete unused features. If we want to re-enable them later, we could download a specific package. Thank you, team!

### Scenario when this would be used?

In laptops with limited storage. Mine have soldered internal storage :) Ngl, it is currently the second largest app in me.

### Supporting information

![image](https://github.com/user-attachments/assets/882880b9-1db9-4058-89f5-8844d65f2612)
Repository: godot
Issue: If a modifier key like ^ ´ or ¨ is active (even if it hit before launching Godot) physical keycode output gets corrupted
Labels: bug,topic:input

### Tested versions

- Reproducible in 4.3

### System information

Windows 11 - Godot 4.3 stable

### Issue description

Keyboards in some regions have keys that when pressed do nothing until you press a second key.
As an example hitting "¨" and then "A" results in "Ä". ^ + A = Â etc.

"event.get_physical_keycode()" is applying said modifiers to all of it's output, if one is currently active.

Here's my test script:
```gdscript
extends Node

func _ready() -> void:
	var actions: = InputMap.get_actions()
	for action in actions:
		var events: Array[InputEvent] = InputMap.action_get_events(action)
		for event in events:
			if (event is InputEventKey):
				var keycode : Key = event.get_physical_keycode()
				var physical_label: = DisplayServer.keyboard_get_label_from_physical(keycode)
				var key_name: = OS.get_keycode_string(physical_label)
				print(key_name)
```


It normally prints:
```
key_name: A
key_name: B
key_name: C
key_name: D
key_name: E
key_name: F
key_name: G
```

But if I hit ¨ key before launching the project:
```
key_name: Ä
key_name: ¨
key_name: ¨
key_name: ¨
key_name: Ë
key_name: ¨
key_name: ¨
```

To clarify: That's the entire script. No _input() is involved at all.

### Steps to reproduce

Have keyboard with a modifier key like ¨, ´ or ^.

1. Hit said key once.
2. Launch the project.

### Minimal reproduction project (MRP)

[umlaut-caret-bug-test.zip](https://github.com/user-attachments/files/16830764/umlaut-caret-bug-test.zip)
Repository: go
Issue: cmd/go: standard library tests fail with GO111MODULE=auto
Labels: GoCommand

### Go version

go version go1.22.6 darwin/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE='auto'
GOARCH='amd64'
GOBIN=''
GOCACHE='/tmp/.gocache'
GOENV='/Users/rittneje/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/rittneje/go/pkg/mod'
GONOPROXY='[REDACTED]'
GONOSUMDB='[REDACTED]'
GOOS='darwin'
GOPATH='/Users/rittneje/go'
GOPRIVATE='[REDACTED]'
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/rittneje/go1.22.6'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/Users/rittneje/go1.22.6/pkg/tool/darwin_amd64'
GOVCS='[REDACTED]'
GOVERSION='go1.22.6'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD=''
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/kf/kr7_s3xx0l12zbj3jrn082hmzy5gvy/T/go-build1131392119=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

go test net/http -v -run=^TestReadResponseErrors$

### What did you see happen?

> === RUN   TestReadResponseErrors
    response_test.go:944: status "200 OK" "Content-Length:\r\nContent-Length:\r\n\r\nGophers\r\n": unexpected success; want error with substring "invalid empty Content-Length"
--- FAIL: TestReadResponseErrors (0.00s)
FAIL
FAIL	net/http	0.636s
FAIL

### What did you expect to see?

> === RUN   TestReadResponseErrors
--- PASS: TestReadResponseErrors (0.00s)
PASS
ok  	net/http	0.278s

This is because `GODEBUG` is not getting the expected default value due to `GO111MODULE=auto`.

Explicitly running `GO111MODULE=on go test net/http -v -run=^TestReadResponseErrors$` causes it to pass.
Repository: vscode
Issue: Emmet Wrap with fragments do not work at all
Labels: bug,emmet,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**/No
<!-- 🪓 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.92.2 (Universal)
- OS Version: macOS Sequoia 15.1 Developer Beta

Steps to Reproduce:

1. Create a markup element
2. Make sure you're selecting an element
3. Use the "Emmet: Wrap with Abbreviation"


https://github.com/user-attachments/assets/52080ea9-c229-407d-a310-30106abc78a0
Repository: pytorch
Issue: DISABLED test_randint_randomness_for_large_range (__main__.TestCuda)
Labels: module: cuda,triaged,module: flaky-tests,skipped

Platforms: linux

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

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

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



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

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 1027, in test_randint_randomness_for_large_range
    assert abs(run(torch.device("cuda")) - run(torch.device("cpu"))) < 10_000
  File "/var/lib/jenkins/workspace/test/test_cuda.py", line 1024, in run
    return torch.stack([t1, t2]).unique().shape[0]
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_tensor.py", line 991, in unique
    return torch.unique(
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_jit_internal.py", line 624, in fn
    return if_false(*args, **kwargs)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_jit_internal.py", line 624, in fn
    return if_false(*args, **kwargs)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/functional.py", line 1075, in _return_output
    output, _, _ = _unique_impl(input, sorted, return_inverse, return_counts, dim)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/functional.py", line 968, in _unique_impl
    output, inverse_indices, counts = torch._unique2(
RuntimeError: Host and device pointer dont match with cudaHostRegister. Please dont use this feature by setting PYTORCH_CUDA_ALLOC_CONF=use_cuda_host_register:False (default)

To execute this test, run the following from the base repo dir:
    python test/test_cuda.py TestCuda.test_randint_randomness_for_large_range

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

</details>


Test file path: `test_cuda.py`

cc @ptrblck @msaroufim @clee2000
Repository: pytorch
Issue: DISABLED test_randint_cuda_dynamic_shapes_cuda_wrapper (__main__.DynamicShapesCudaWrapperCudaTests)
Labels: triaged,module: flaky-tests,skipped,oncall: pt2,module: inductor

Platforms: linux

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

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

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



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

```
Traceback (most recent call last):
  File "/opt/conda/envs/py_3.10/lib/python3.10/contextlib.py", line 79, in inner
    return func(*args, **kwds)
  File "/var/lib/jenkins/workspace/test/inductor/test_cuda_cpp_wrapper.py", line 113, in fn
    _, code = test_torchinductor.run_and_get_cpp_code(
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/_inductor/utils.py", line 1917, in run_and_get_cpp_code
    result = fn(*args, **kwargs)
  File "/var/lib/jenkins/workspace/test/inductor/test_torchinductor.py", line 11370, in new_test
    return value(self)
  File "/var/lib/jenkins/workspace/test/inductor/test_torchinductor.py", line 8118, in test_randint
    self.assertEqual(c0, c1)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 3885, in assertEqual
    raise error_metas.pop()[0].to_error(
AssertionError: Tensor-likes are not close!

Mismatched elements: 1598 / 1600 (99.9%)
Greatest absolute difference: 3.37277889251709 at index (28, 17) (up to 1e-05 allowed)
Greatest relative difference: 1.423457129854089e+38 at index (28, 17) (up to 1.3e-06 allowed)

To execute this test, run the following from the base repo dir:
    python test/inductor/test_cuda_cpp_wrapper.py DynamicShapesCudaWrapperCudaTests.test_randint_cuda_dynamic_shapes_cuda_wrapper

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

</details>


Test file path: `inductor/test_cuda_cpp_wrapper.py`

cc @clee2000 @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: tensorflow
Issue: `np.cumprod` on ndarray with type `tensorflow.python.framework.dtypes.bfloat16.as_numpy_dtype` can cause `segmentfault
Labels: stat:awaiting tensorflower,type:support,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

tf-nightly 2.18.0.dev20240828

### Custom code

Yes

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

I encountered an `segmentfault issue` in TensorFlow when I used API `np.cumprod` on ndarray with type `tensorflow.python.framework.dtypes.bfloat16.as_numpy_dtype` .  I have confirmed that the code would crash on `tf-nightly-2.18.0.dev20240817` and `tf-nightly-2.18.0.dev20240828` (nightly-build)

### Standalone code to reproduce the issue

```shell
import numpy as np
from tensorflow.python.framework import dtypes


def numpy_reverse(x, axis):
    length = len(x.shape)
    if axis < 0:
        axis = length + axis
    ix = [slice(None, None, -1) if i == axis else slice(None) for i in range(length)]
    return x[tuple(ix)]


axis = 0
x = np.zeros([595]).astype(dtypes.bfloat16.as_numpy_dtype) # crash
# x = np.zeros([595]).astype(float) # works well
length = len(x.shape)
x = numpy_reverse(x, axis=0)
ix_head = [slice(0, 1) if i == axis else slice(None) for i in range(length)]
ix_init = [slice(0, -1) if i == axis else slice(None) for i in range(length)]
init = np.ones_like(x[tuple(ix_head)])
np_out = np.concatenate([init, np.cumprod(x[tuple(ix_init)], axis)], axis=axis)
```


### Relevant log output

```shell
Segmentation fault (core dumped)
```
Repository: stable-diffusion-webui
Issue: [Feature Request]: Keep original file name for img-img
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

There doesn't seem to be an option to save img-img generations with its original file name, this is pretty annoying when you're working with 100's of files and you need them to be named just like the original (e.g game textures), takes a lot of extra time to go into the output folder and rename them.

For batch processing you do have this option, which is great, however sometimes i want to just write individual prompts, though i'm less likely to want to do it because the tediousness of changing filenames all the time.

### Proposed workflow

checkbox

### Additional information

_No response_
Repository: kubernetes
Issue: Panic when comparing two interface.
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

When I used ArgoCD, I found [this line](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apimachinery/pkg/util/strategicpatch/patch.go#L955) will result in panic if two compared values are `map[string]interface`. The call was initiated from [here](https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apimachinery/pkg/util/strategicpatch/patch.go#L2105). If the passed in entry does not follow the schema, it may result the two compared values are `map[string]interface` and will raise panic.

### What did you expect to happen?

From the function `CreateThreeWayMergePatch`'s comments, it should either return the error said the input does not follow the schema or do the comparison. Panic should not be raised. I proposed reflect.DeepEqual could be used instead of "=="

### How can we reproduce it (as minimally and precisely as possible)?

If the struct does not follow the schema and give one field as map[string]interface instead of string, and calling `CreateThreeWayMergePatch`, the panic will be raised.

### Anything else we need to know?

I could raise PR if it does make sense.

### Kubernetes version

1.29.5

### Cloud provider

N/A

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: flutter
Issue: Add preventGestureDelay Option to flutter_webview Plugin
Labels: p: webview,package,c: proposal,team-ecosystem,P2,triaged-ecosystem

### Use case

Problem Description: The problem I'm facing is a noticeable delay in touch interactions within the flutter_webview plugin. This delay, which typically occurs between tapping a button and being able to scroll or perform another action, degrades the user experience by making the app feel unresponsive. This issue is particularly problematic in web-based mobile applications where immediate feedback from touch interactions is crucial.

Relation to a Problem: The issue is tied to Flutter’s DelayingGestureRecognizer, which introduces a delay to differentiate between single and double taps. While this may be useful in certain contexts, it hinders the fluidity of interactions in a WebView, where immediate touch response is often more important. This is especially frustrating in applications that require quick, responsive interactions, like scrolling immediately after tapping a button.

Alternative Solutions Considered: I have considered using alternative packages like flutter_inappwebview, which offers a preventGestureDelay option that effectively eliminates this delay. However, this package hasn't been maintained for several months, leading to concerns about long-term support and compatibility. Additionally, the flutter_webview plugin is the official and more stable option, making it the preferred choice for many developers, including myself.

### Proposal

Feature Request: I propose adding a preventGestureDelay option to the flutter_webview plugin. This option should allow developers to toggle the prevention of gesture delays, specifically addressing the delay caused by the DelayingGestureRecognizer. This will enable WebView to respond to touch interactions, such as taps and scrolls, immediately, improving the overall user experience.

Why This Should Be Provided by Flutter: Given that flutter_webview is the official WebView plugin for Flutter, it is crucial for it to support common use cases that demand responsive touch interactions. This feature would enhance the plugin's utility and ensure it meets the needs of modern mobile applications that require quick, fluid touch gestures. While this could potentially be implemented in a third-party package, having it as part of the official plugin ensures better integration, maintenance, and stability across Flutter projects.
Repository: ui
Issue: [bug]: Error: You forgot to add 'mini-css-extract-plugin' plugin (i.e. `{ plugins: [new MiniCssExtractPlugin()] }`), 
Labels: bug

### Describe the bug

When creating a new project with the CLI (without an existing Next.js project) using pnpm I get this error.

### Affected component/components

-

### How to reproduce

- Empty directory
- pnpm dlx shadcn@latest init
- pnpm dlx shadcn@latest add button
- Render a button on app/page.tsx
- pnpm run dev

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
Error: You forgot to add 'mini-css-extract-plugin' plugin (i.e. `{ plugins: [new MiniCssExtractPlugin()] }`), please read https://github.com/webpack-contrib/mini-css-extract-plugin#getting-started

Import trace for requested module:
./app/globals.css
```


### System Info

```bash
MacOS, Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: deno
Issue: line numbers don't match source code in chrome://inspect performance tab
Labels: bug

Version: Deno 1.46.2
Chrome 128.0.6613.114

I'm using the --inspect-wait flag to profile some Deno code. To reproduce:

```
git clone git@github.com:skybrian/repeat-test.git
cd repeat-test
git checkout 389357e1b3e2546dbefc6b9d9984760509b13ee2
deno --inspect-wait performance/profile_take_chars.ts
```

The profile runs automatically after the inspector connects and the flame graph appears after a second or two, but when I look at individual functions in the call graph, the line numbers are off. For example, there are two prune() functions that are reported to be at lines 66 and 263 of pick_tree.ts, but in [the pick_tree source code](https://github.com/skybrian/repeat-test/blob/main/src/pick_tree.ts), these functions are actually at 111-136 and 342-365.

Presumably the code is being transformed in some way before it's run? It would be nice if that transformation preserved newlines so that the line numbers match.