sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Build opencv.js can not use
Labels: bug,category: javascript (js)

### System Information

OpenCV version: 4.8.0
Operating System / Platform: Ubuntu 20.04
Compiler & compiler version: emsdk

### Detailed description

The build fininsh opencv.js can not use
the cv is a Promise, is different from the release
and event u use cv = await cv
and then to using other function in opencv it report error as the cv.Mat is not a function in opencv.js
![image](https://github.com/opencv/opencv/assets/30902531/2decc2a1-d502-484a-8dae-a2516ddb84cc)


### Steps to reproduce

to build the opencv.js like the [doc](https://docs.opencv.org/4.x/d4/da1/tutorial_js_setup.html) and then using it in html like this 
···
<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8" />
    <title>Hello OpenCV.js</title>
    <!-- 使用js版的opencv -->
    <script
      async
      src="opencv.js"
      onload="onOpenCvReady()"
      type="text/javascript"
    ></script>
	
  </head>
  <body>
    <h2>Hello OpenCV.js</h2>
    <p id="status">OpenCV.js is loading...</p>
	<canvas id='result'></canvas>
    <button onclick='btnclick()'>测试</button>
    <img id='img0' src='./0.jpg'/> 
    <script type="text/javascript">
      async function onOpenCvReady() {
        document.getElementById("status").innerHTML = "OpenCV.js is ready.";
		cv = await cv;
		let mat = new cv.Mat()
      }
	   
	   
	   
		function btnclick() {
			console.log('xxxx');
			console.log(cv);
			
			var img1 = cv.imread('img0');
			
		}   
     
    </script>
  </body>
</html>

···
and then it report the error like this
···
opencv.js:30  Uncaught TypeError: cv.matFromImageData is not a function
    at Module.imread (opencv.js:30:10470629)
    at btnclick (old.html:35:18)
    at HTMLButtonElement.onclick (old.html:18:34)
···


and my build opencv.js is here 
[opencv.zip](https://github.com/opencv/opencv/files/14354911/opencv.zip)


### 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: vscode
Issue: Option to auto-expand groups in variables panel while debugging
Labels: feature-request,debug

When debugging, the current behavior is that all groups (nodes) in the variables panel are collapsed, possibly with the exception of the first (usually the one titled 'local').

Unfortunately, there are often many 'Block' groups, representing code scopes that aren't technically "local" but are still very near and relevant, like conditionals, loop bodies, function closures, etc. Each of these 'block' groups often only contains a few variables.

Since the information about the content of each group is hidden by default, it makes it difficult to find a particular variable, often forcing the user to use a kind of 'trial-and-error' to expand each group in turn:

![Screenshot_1](https://github.com/microsoft/vscode/assets/8589488/5fdbf6b5-39bb-437e-afd7-36eb5a29bf29)

In the above example, there is no easy way, say, to locate the "Block" group containing `var5`, other than going through each group, by trial and error, and expanding each in turn. There is no indication that can help knowing that some group contains this particular variable.

This has been like this [for many years](https://github.com/microsoft/vscode/issues/93230). It makes the debugging experience more tedious and frustrating, but it doesn't seem like there has been much recent effort to improve on it (last relevant issues are several years old). Maybe people have possibly given up, somehow accepting it as an integral part of the VSCode debugging experience?

Another frustrating behavior is that within a single debugging session, often the UI will "forget" the expansion state of one or more groups and have it collapsed again, when a new breakpoint is reached, forcing the user to again try to "guess" (sometimes by trial and error) the group that contained the variable they were interested in (my experience is from TypeScript debugging, but it is likely relevant to many other languages).

Since there has been so much effort, over the years, to improve the UI experience in much less important or critical areas, I wonder if there's any chance this can be improved by simply providing an option to, say auto-expand all "block" groups? Or provide a button to "expand all" groups, or all groups of a particular type or reasonably near scope?

In general, is there any hope that this aspect of the debugging experience, especially the variables panel, would be improved any time soon?
Repository: PowerToys
Issue: Added PowerToys Run's theme color to follow the taskbar color
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

The current theme only supports light and dark mode, and can not be associated with taskbar colors in Windows. Do a uniform color display!! Otherwise, the taskbar color is red, and the color of PowerToys Run is black. Very unfriendly

### Scenario when this would be used?

When switching PowerToys Run themes, there are now only light and dark modes. Please support following taskbar colors. Thank you

### Supporting information

_No response_
Repository: kubernetes
Issue: force-delete pod execute prestop hook
Labels: kind/bug,sig/node,priority/important-longterm,triage/accepted

### What happened?

as the pr https://github.com/kubernetes/kubernetes/pull/49449 said：Do not try to run preStopHook when the gracePeriod is 0 。 When we execute a force delete pod, it will not execute a pre-stop hook。But this pr https://github.com/kubernetes/kubernetes/pull/115835 Disrupted this behavior。It will execute a pre-stop hook when force delete。







### What did you expect to happen?

https://github.com/kubernetes/kubernetes/pull/49449
https://github.com/kubernetes/kubernetes/pull/115835

The behavior of the above two PR is conflicting. I don't know which approach meets expectations



### How can we reproduce it (as minimally and precisely as possible)?

1 use this yaml apply pod：
```
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: nginx-daemonset
spec:
  selector:
    matchLabels:
      app: nginx
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx-container
        image: hub.easystack.io/captain/nginx:1.21
        volumeMounts:
        - name: root-volume
          mountPath: /root/
        lifecycle:
          preStop:
            exec:
              command: ["/bin/sh", "-c", "echo 'hello world' > /root/tempfile && sleep 5"]
      volumes:
      - name: root-volume
        hostPath:
          path: /root/
```

2  force delete one pod：
kubectl delete po nginx-daemonset-pml7f --force

You can see the result of the pre-stop execution


### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
server Version: v1.28.2
# paste output here
```

</details>


### Cloud provider

<details>
..
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here
Linux node-1.domain.tld 4.18.0-372.19.1.es8_8.x86_64 #1 SMP Tue Jan 2 14:54:00 CST 2024 x86_64 x86_64 x86_64 GNU/Linux

# 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: neovim
Issue: Strange behavior with :terminal resizing
Labels: bug,status:blocked-external,terminal

### Problem

Resizing a terminal buffer alters lines in unexpected ways. This occurs when resizing a terminal via a split or when resizing the entire terminal

See video demo, below:

https://github.com/neovim/neovim/assets/10103049/af03f6ec-ddcd-415d-acce-b47eda25913b

### Steps to reproduce

- Install Neovim nightly (NVIM v0.10.0-dev-2396+gb4c013c27-dirty, in my case)
- Call `nvim -u NONE`
- Run `:terminal`
- Print something with long lines and then resize the terminal

### Expected behavior

Resizing would work without causing blank space which permanently alters the lines

### Neovim version (nvim -v)

v0.10.0-dev-2396+gb4c013c27-dirty

### Vim (not Nvim) behaves the same?

yes, vim 9.1

### Operating system/version

CentOS Linux 7 (Core)

### Terminal name/version

gnome or Alacritty (both have the issue)

### $TERM environment variable

xterm-256color

### Installation

build from repo
Repository: godot
Issue: Polyphonic audio stream not playing correctly when compiling with MSVC.
Labels: bug,platform:windows,topic:buildsystem,topic:audio

### Tested versions

Reproducible in: builds on Windows using MSVC
Not reproducible in: builds on Windows using mingw

### System information

Godot v4.2.1.stable (b09f793f5) - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (NVIDIA; 31.0.15.2824) - Intel(R) Core(TM) i9-14900KF (32 Threads)

### Issue description

For a racing simulation I've created a script that will use a polyphonic AudioStreamPlayer3D that will play one or two looping samples concurrently, mixing their volumes and pitches to emulate in this case an engine sound that changes with RPM.

This works just fine on release builds of Godot on Windows, but when I compile my own build from source (using MSVC) the sound plays incorrectly.

### Steps to reproduce

Open the sample project in the Godot editor and make sure the world.tscn is open. In the scene tree there is a single child called "Stream" and if you select that, in the inspector there is a slider called RPM that you can change to adjust the engine RPM. Up to 2200 RPM it plays only one sample, above it starts mixing in the second. You should clearly hear an engine revving as you move the slider.

If you use a release build, you will hear it. If you build it yourself on Windows using MSVC, it does not change when moving the slider.

### Minimal reproduction project (MRP)

[audiostream-polyphonic.zip](https://github.com/godotengine/godot/files/14356504/audiostream-polyphonic.zip)
Repository: rust
Issue: unconditional_panic (index out of bounds) should work on simd vectors like normal array
Labels: A-diagnostics,T-compiler

### Code

```Rust
#![feature(portable_simd)]

fn main() {
    let array = std::simd::u8x64::splat(0);

    // This panics instead of a compiler error but if the array was defined like this
    // let array = [0; 64];
    // It would be a compiler error
    // I think simd vector should have the same behavior as the array
    // Because the simd vector is a fixed size array
    let index = array[69];

    println!("array {}", index);
}
```


### Current output

```Shell
The code compiles successfully.
```


### Desired output

```Shell
error: this operation will panic at runtime
  --> src\main.rs:11:17
   |
11 |     let index = array[69];
   |                 ^^^^^^^^^ index out of bounds: the length is 64 but the index is 69
   |
   = note: `#[deny(unconditional_panic)]` on by default

error: could not compile `example` (bin "example") due to 1 previous error
```


### Rationale and extra context

_No response_

### Other cases

_No response_

### Rust Version

```Shell
$ rustc --version --verbose
rustc 1.78.0-nightly (bb594538f 2024-02-20)
binary: rustc
commit-hash: bb594538fc6e84213a6b8d5e165442570aa48923
commit-date: 2024-02-20
host: x86_64-pc-windows-msvc
release: 1.78.0-nightly
LLVM version: 18.1.0
```


### Anything else?

_No response_
Repository: rust
Issue: suggestion to lint unnecessary ﻿`&mut` usage
Labels: A-lints,T-compiler,C-feature-request

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
use std::collections::HashMap;

fn f(map: &mut HashMap<i32, i32>) {
    let _ = map.get(&0);
}
```

I expected to see this happen: note that the `﻿&mut` is unnecessary in this function, as it serves solely as an immutable reference.

Instead, this happened: nothing happened and it compiled successfully.

### 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.78.0-nightly (bb594538f 2024-02-20)
binary: rustc
commit-hash: bb594538fc6e84213a6b8d5e165442570aa48923
commit-date: 2024-02-20
host: aarch64-apple-darwin
release: 1.78.0-nightly
LLVM version: 18.1.0
```
Repository: PowerToys
Issue: Can't expand/collapse PDF bookmarks or open thumbnail tab in sidebar
Labels: Issue-Bug,Needs-Triage,Product-Peek

### Microsoft PowerToys version

0.78.0

### Installation method

WinGet

### Running as admin

No

### Area(s) with issue?

Peek

### Steps to reproduce

Peek a PDF, click `Contents` button to show sidebar and click any thing in sidebar.


https://github.com/microsoft/PowerToys/assets/8749411/ece1ace6-36fa-45e0-8d6e-aaf9536f7b13



### ✔️ Expected Behavior

Clicks will work.

### ❌ Actual Behavior

Sidebar will hide when clicking item in sidebar.

### Other Software

_No response_
Repository: rust
Issue: `Condvar::wait_while` documentation is inaccurate
Labels: A-docs,T-libs

The implementation checks the condition first, while the documentation states that it enters the wait immediately:

doc
> Blocks the current thread until this condition variable receives a notification and the provided condition is false.

code
```rs
        while condition(&mut *guard) {
            guard = self.wait(guard)?;
        }
        Ok(guard)
```
Repository: go
Issue: runtime: traceback: unexpected SPWRITE function msancall/asancall
Labels: help wanted,NeedsFix,compiler/runtime

### Go version

1.21, 1.22, gotip

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN='/home/mauri870/gopath/bin'
GOCACHE='/home/mauri870/.cache/go-build'
GOENV='/home/mauri870/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/mauri870/gopath/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/mauri870/gopath'
GOPRIVATE=''
GOPROXY='direct'
GOROOT='/home/mauri870/git/go'
GOSUMDB='off'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/mauri870/git/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.23-1a8ee033f8 Tue Feb 20 22:55:07 2024 +0000'
GCCGO='/usr/bin/gccgo'
GOAMD64='v1'
AR='ar'
CC='clang-17'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
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 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build273665276=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

```bash
export CC=clang
go test -run ^TestDebugCallGC$ runtime -v -asan -count 10
go test -run ^TestDebugCallGC$ runtime -v -msan -count 10
```

### What did you see happen?

Crash when running runtime tests with -asan or -msan.

```
traceback: unexpected SPWRITE function msancall
fatal error: traceback                                                                               
```

### What did you expect to see?

Either src/runtime/debug_test.go tests to pass, or skip these  with `&& linux && !race && !msan && !asan)`
Repository: TypeScript
Issue: Wrong `super` in class element decorator
Labels: Needs Investigation

### 🔎 Search Terms

super decorators

### 🕗 Version & Regression Information

- This is the behavior in every version I tried


### ⏯ Playground Link

https://www.typescriptlang.org/play?target=99#code/MYGwhgzhAECC0FMAeAXBA7AJjUkYG9owAKAfQEYAuI9ATwBppSAmasOgSmkOAHt0IvEAgB0IXgHNiAIggBXAA4IATiLDSuAX2jb8AKGjQAZr17Eu+w4eEoiRtMugBeaOecA+bpoDcBq7ihoACFuPytoAAF5JVUwY2doaWlfcM09MLsHcxSdPTS9dAQAdzhzERMzDm8gA

### 💻 Code

I'm targeting ESNext

```ts
class A extends class { a(_1: any, _2: any) { console.log("super.a") } } {
  foo() {
    let after = () => {};
    class B {
      @super.a f = "";
    }

    after();
  }
}

new A().foo();
```


### 🙁 Actual behavior

Running the output throws `super.a is not a function`

### 🙂 Expected behavior

The output code should log "super.a"

### Additional information about the issue

_No response_
Repository: TypeScript
Issue: Control flow analysis gets confused by decorators
Labels: Needs Investigation

### 🔎 Search Terms

decorators super control flow

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

https://www.typescriptlang.org/play?target=99#code/HYUw7gBAxgNghgZwRAghEAPALiYATZWRZAbwjgAoBKCEgXwgZICgJoB7YBLAJwFcoWdj2q1WbCAj4AHECKoBuZuLYwQWcgDMcPJROjwkEAEJj9bAAIU42uRAC8kmXIB0cADQQKAfQCMn7wAmGnsAPlo6Gk0HCAAiWL0JOmV9Gx1qROS6IA

### 💻 Code

```ts
new class A extends class { a() {} } {
  constructor() {
    super();

    let after;
    class B {
      @(after = super.a, (_1, _2) => {}) f = "";
    }

    after();
  }
}
```


### 🙁 Actual behavior

TS complains that:
- I'm accessing `super.a` before calling `super()`
- I'm calling `after` before initializing it

### 🙂 Expected behavior

That code should be fine

### Additional information about the issue

_No response_
Repository: vscode
Issue: Making refactors is stressful because I don't know when they will or will not show the refactor preview
Labels: polish,editor-code-actions

Testing https://github.com/microsoft/vscode/issues/205853

The refactor preview is very cool, but it seems like not all actions under "Refactor..." use the preview. If I'm uncertain of the refactor I'm making I don't want it to start changing files on disk right away. It would help me gain confidence in the "Refactor..." actions if I knew in advance that the action was going to have a preview.
Repository: go
Issue: runtime: clarify statement on g object memory lifetime
Labels: Documentation,help wanted,NeedsDecision,compiler/runtime

### What is the URL of the page with the issue?

https://github.com/golang/go/blob/master/src/runtime/HACKING.md

### What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/121.0.0.0 Safari/537.36

### Screenshot

<img width="1387" alt="Screen Shot 2024-02-21 at 8 54 11 PM" src="https://github.com/golang/go/assets/37536298/0f1d78d7-d905-4b11-9457-900b921529f3">


### What did you do?

read docs

### What did you see happen?

All g, m, and p objects are heap allocated, but are never freed, so their memory remains type stable. As a result, the runtime can avoid write barriers in the depths of the scheduler.

### What did you expect to see?

The statement "g objects are heap allocated, but are never freed, so their memory remains type stable" can be misleading. It may imply that the entire memory occupied by a goroutine, including its stack, remains allocated indefinitely.

To address this, proposes the following changes:

**Update the documentation:**

- Clarify that the statement refers to the g object itself, not the goroutine's stack memory.

- Explain that while the g object is never explicitly freed, its stack memory is eventually reclaimed by the garbage collector.


https://github.com/golang/go/blob/d4112310a4d3b1981d77226a3d52a8b566b0c0bc/src/runtime/proc.go#L4185
Repository: PowerToys
Issue: [keyboard manager] map "alt+j" to send "alt+left" not work
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.70.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

1. sometimes back from system hibernate then the settings of " "alt+j" to send "alt+left" not work. 
2. sometimes no work for no reason.
by the way, other maping works fine;  and i change to "all apps" for tests.

### ✔️ Expected Behavior

press  "alt+j" to send "alt+left" 

### ❌ Actual Behavior

nothing happen.

### Other Software

no
Repository: flutter
Issue: [shared_preferences] Windows and Linux don't support multiple isolates/engines correctly
Labels: platform-windows,platform-linux,p: shared_preferences,package,a: desktop,team-ecosystem,P3,triaged-ecosystem

### Steps to reproduce

1. A engine:
prefs.setBool('EnabledSmartRecognizeGraph', !widget.allowRecognize);
2. B engine:
prefs.setString(_kVoipRecordFilePathKey, jsonEncode(dic));
3. A engine:
prefs.reload();


### Expected results

The prefs contain data written in the above two times simultaneously.

### Actual results

prefs exclusively has the data written from the A engine.

The reason for this issue lies in the implementation of the .reload method, which follows the chain of _store.getAll() -> getAllWithParameters -> _readPreferences. There is a problem with this implementation that causes reload to always read data from the cache instead of the updated JSON file.

Here's the relevant code snippet:
Future<Map<String, Object>> _readPreferences() async {  
    return _cachedPreferences ?? await _reload();  
}

### Code sample

<details open><summary>Code sample</summary>

```dart
SharedPreferences prefs = await SharedPreferences.getInstance();
prefs.setBool('EnabledSmartRecognizeGraph', !widget.allowRecognize); // A engine
prefs.setString(_kVoipRecordFilePathKey, jsonEncode(dic)); // B engine
prefs.reload();
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
error
```

</details>
Repository: stable-diffusion-webui
Issue: [Apple Silicon installation]: Add this to the installation guide
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 ?

Hi there. Apple does not run CUDA, so the export torch cuda test is obviously not needed. 

### Proposed workflow

You might wanna tell people to run export COMMANDLINE_ARGS="--skip-torch-cuda-test" prior to running the webui.sh script.

### Additional information

_No response_
Repository: create-react-app
Issue: Why react app keep calling ws/info and ws/iframe.html ?
Labels: needs triage

I have setup new project using create-react-app, and saw my scripts inside index.html are called multiple time
Repository: ant-design
Issue: pagination点击下一页后按下Enter键页数会加二
Labels: Inactive,unconfirmed

### Reproduction link

[https://ant-design.gitee.io/components/pagination-cn](https://ant-design.gitee.io/components/pagination-cn)

### Steps to reproduce

1. pagination组件官网demo，点击下一页
2. 按下Enter键

### What is expected?

页数加一

### What is actually happening?

页数加二

| Environment | Info |
| --- | --- |
| antd | 5.14.1 |
| React | ^18.2.0 |
| System | Windows11 |
| Browser | Edge121.0.2277.128 |

---
[rc-pagination#562](https://github.com/react-component/pagination/pull/562)
当点击下一页后按下enter键，预期是出现页数加一，但实际按下enter键除了会触发键盘事件还会默认触发元素的点击事件，所以会出现页数加二的情况，反之点击上一页然后按下enter键也是如此，页数会减二而不是预期的减一，最直接的解决办法是event.preventDefault阻止默认事件即可，但是也会想到即使不写键盘事件，点击下一页，此时元素已经获取到焦点，此时按下enter键也会默认触发元素的点击事件，达到页数加一的效果，那么写键盘事件是否是冗余代码？翻看了业内比较知名的mui与element-plus，似乎他们并没有专门关照enter键盘事件

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->