sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: Data Race in BFMatcher::knnMatch Function
Labels: bug,category: features2d

### System Information

OpenCV 4.8.0/4.8.1
onetbb 2021.10.0
Arch Linux
GCC 13.2.1 20230801

### Detailed description

Hi all,

A data race occurs when I call BFMatcher::knnMatch several times in succession.

I built onetbb and opencv with thread sanitizer, from which the attached stack trace origins.
[Stacktrace.txt](https://github.com/opencv/opencv/files/13333746/Stacktrace.txt)

The data race occurs sporadic, I can reproduce the result when running the attached main in a loop and using stress to strain the system. The data race occurs about once in 15 iterations.
Without debug symbols and thread sanitizer the data race occurs every time.


### Steps to reproduce

```cpp
#include <opencv2/features2d.hpp>
#include <vector>

int main(int argc, char *argv[])
{
    auto test = cv::BFMatcher::create();
    cv::Mat descriptors1 = cv::Mat::eye(3, 3, CV_32F);
    cv::Mat descriptors2(3, 3, CV_32F);
    descriptors2.at<float>(0, 0) = 0;
    descriptors2.at<float>(0, 1) = 1;
    descriptors2.at<float>(0, 2) = 0;
    descriptors2.at<float>(1, 0) = 0;
    descriptors2.at<float>(1, 1) = 0;
    descriptors2.at<float>(1, 2) = 1;
    descriptors2.at<float>(2, 0) = -1;
    descriptors2.at<float>(2, 1) = 0;
    descriptors2.at<float>(2, 2) = 0;
    std::vector<std::vector<cv::DMatch>> matches;
    test->knnMatch(descriptors2, descriptors1, matches, 125);
    test->knnMatch(descriptors2, descriptors1, matches, 125);
}
```

### 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: go
Issue: x/crypto/ssh: race in ListenUnix() causes forwarded socket to be rejected after client requests it
Labels: Security,help wanted,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

Not applicable.  Affects x/crypto version v0.15.0

### Does this issue reproduce with the latest release?

Yes


### What operating system and processor architecture are you using (`go env`)?

Not applicable

### What did you do?

In ListenUnix():

https://github.com/golang/crypto/blob/1cf1811d7195fe9bb436a00e335567575fac9b07/ssh/streamlocal.go#L40

it sends the message to request remote forwarding of Unix domain sockets before it is prepared to receive forwards, which it sets later: https://github.com/golang/crypto/blob/1cf1811d7195fe9bb436a00e335567575fac9b07/ssh/streamlocal.go#L47

This sets up a race between the server forwarding a connection and the client being prepared to receive it.  The client should set itself to receive the forward _before_ sending the request (and if the request fails, clean up) to avoid a race condition.  I see this in unit testing where a test SSH server can very quickly respond to a request to forward sockets, but in principal it could happen in a live system too.

A similar issue affects TCP sockets.

### What did you expect to see?

1. the SSH server accepts the message to begin forwarding Unix sockets
2. the SSH server opens a channel back to the client to forward the socket
3. the client accepts the channel


### What did you see instead?


1. the SSH server accepts the message to begin forwarding Unix sockets
2. the SSH server opens a channel to forward the socket back to the client
3. occasionally, the SSH client rejects the channel with "administratively prohibited (no forward for address)", even though it is the address the client just requested.
Repository: vscode
Issue: Support fontFamily per token type
Labels: feature-request,editor-rendering

```json
"editor.fontFamily": {
   "default": "'Cascadia Code', Consolas, 'Courier New', monospace",
   "comment": "...",
   "string": "...",
   "inlineSuggestion": "...",
}
```

FYI @joaomoreno 

Related #36512
Repository: stable-diffusion-webui
Issue: [Bug]: Bad UI in stable diffusion
Labels: bug-report

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

I installed the system according to the instructions of AUTOMATIC1111/stable-diffusion-webui, but when I opened the browser and typed http://127.0.0.1:7860/, the page displayed was confusing, the UI was bad.
However, the basic function is normal, generating pictures based on prompt.
screenshot:
![Screenshot (1)](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/149995879/6cdb4531-cd59-482e-88ee-9aa5c36c58ad)

![Screenshot (2)](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/149995879/d855d5f8-999c-4c52-9b5f-14f72c0cbc6e)

![Screenshot (3)](https://github.com/AUTOMATIC1111/stable-diffusion-webui/assets/149995879/d89ff611-186d-482b-bc6f-465d3055a171)


### Steps to reproduce the problem

1.Install AUTOMATIC1111/stable-diffusion-webui
2.Open a browser (Google or edge) and type “[http://127.0.0.1:7860/”](http://127.0.0.1:7860/%E2%80%9D)
3.The cluttered interface is displayed

### What should have happened?

A normal web page, like the screenshot on the website
https://github.com/AUTOMATIC1111/stable-diffusion-webui/blob/master/screenshot.png

### Sysinfo

windows laptop

### What browsers do you use to access the UI ?

Google Chrome, Microsoft Edge

### Console logs

```Shell
venv "D:\user\new\SD\stable-diffusion-webui\venv\Scripts\Python.exe"
Python 3.10.6 (tags/v3.10.6:9c7b4bd, Aug  1 2022, 21:53:49) [MSC v.1932 64 bit (AMD64)]
Version: v1.6.0-2-g4afaaf8a
Commit hash: 4afaaf8a020c1df457bcf7250cb1c7f609699fa7
Installing requirements
Launching Web UI with arguments:
no module 'xformers'. Processing without...
no module 'xformers'. Processing without...
No module 'xformers'. Proceeding without it.
Loading weights [cc6cb27103] from D:\user\new\SD\stable-diffusion-webui\models\Stable-diffusion\model.ckpt
Running on local URL:  http://127.0.0.1:7860

To create a public link, set `share=True` in `launch()`.
Startup time: 55.0s (prepare environment: 39.0s, import torch: 5.3s, import gradio: 3.3s, setup paths: 2.7s, initialize shared: 0.3s, other imports: 2.4s, setup codeformer: 0.2s, load scripts: 0.9s, create ui: 0.5s, gradio launch: 0.3s).
Creating model from config: D:\user\new\SD\stable-diffusion-webui\configs\v1-inference.yaml
Applying attention optimization: Doggettx... done.
Model loaded in 26.1s (load weights from disk: 12.3s, load config: 0.1s, create model: 1.2s, apply weights to model: 11.2s, apply half(): 0.3s, load VAE: 0.1s, calculate empty prompt: 0.7s).
```


### Additional information

tryed in every  browser even in incognito dosent changed ,tryed reinstalling result was same .images are generating but when it should generate 4 diffrent images it only generate 1 image and repeat it 4 times
Repository: godot
Issue: Multiple Errors on Opening or Creating Projects
Labels: bug,topic:rendering

### Godot version

v4.1.3.stable.mono.official [f06b6836a]

### System information

Godot v4.1.3.stable.mono - Windows 10.0.19045 - Vulkan (Compatibility) - Intel(R) HD Graphics 400 () - Intel(R) Atom(TM) x5-Z8350  CPU @ 1.44GHz (4 Threads)

### Issue description

I am using the OpenGL rendering driver (with a .bat file launching Godot with the flag --rendering-driver opengl3; unsure why it is saying Vulkan (Compatibility) above...) and have just noticed I am receiving the errors below in the command prompt upon either creating a new project, or opening an existing one (even if it's a blank project). These errors also sometimes display in the editor output, though not always.  _Maybe due to the completion order of async calls while loading the editor, and the output pane initializing? If so, you may not need to launch the same way/use the OpenGL renderer for the errors to occur, it just makes sure they are displayed..._

`ERROR: Condition "!texture_allocs_cache.has(p_id)" is true.
   at: texture_free_data (drivers/gles3/storage/utilities.h:111)
ERROR: Cubemap Arrays are not supported in the GL Compatibility backend.
   at: (drivers/gles3/storage/texture_storage.cpp:763)
ERROR: Attempting to use an uninitialized RID
   at: (./core/templates/rid_owner.h:199)
ERROR: Condition "!t" is true.
   at: texture_free (drivers/gles3/storage/texture_storage.cpp:705)`

I have yet to notice any effect caused by these errors, but when I googled the RID uninitialized error, I came across issue #74757. I'm not sure if it's exactly related, so I don't know if these issues should be merged (he is using Ubuntu with version 4 non-mono, with a different error stack trace to compensate), but I wanted to chime in with a proper format and hopefully include everything that is relevant.

### Steps to reproduce

1. Open Godot with the OpenGL Rendering driver utilizing a Windows batch file and the --rendering-driver opengl3 flag set. (unknown if necessary)
2. Either create a new project, or open an existing project.

### Minimal reproduction project

Not sure if it's needed, but just in case my system somehow creates projects differently(?) I have attached an empty project created using my system.
[GodotErrorMRP.zip](https://github.com/godotengine/godot/files/13333614/GodotErrorMRP.zip)
Repository: ant-design
Issue: table拖拽排序列表时出现拖拽闪动
Labels: Inactive,unconfirmed

### Reproduction link

[https://stackblitz.com/edit/react-jzzv12?file=demo.tsx](https://stackblitz.com/edit/react-jzzv12?file=demo.tsx)

### Steps to reproduce

重现步骤：
1. 在table上添加
scroll={{
            x: 'max-content',
}}
2. 鼠标点住一行向下拖不要松

### What is expected?

当拖到最后一行时页面不闪动

### What is actually happening?

拖到最后一行页面闪动

| Environment | Info |
| --- | --- |
| antd | 5.11.1 |
| React | 18.2.01/17.02 |
| System | mac |
| Browser | chrome版本119.0.6045.123 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Quitting .NET editor prints error: `ERROR: Condition "!EditorSettings::get_singleton() || !EditorSettings::get_singleton()->has_setting(p_setting)" is true. Returning: Variant()`
Labels: bug,topic:editor,topic:dotnet

### Godot version

v4.1.3.stable.mono.official [f06b6836a]

### System information

Godot v4.1.3.stable.mono - Windows 10.0.19045 - Vulkan (Compatibility) - Intel(R) HD Graphics 400 () - Intel(R) Atom(TM) x5-Z8350  CPU @ 1.44GHz (4 Threads)

### Issue description

While creating issue #84838 I was testing different projects, and to do so I used the Quit to Project List in the Project menu of the editor. Upon looking through the log in the command prompt (I used a windows batch file to launch Godot with the OpenGL renderer), I noticed the errors below. Other than the error messages I have not noticed any ill effects, though I haven't tested thoroughly.
`ERROR: Condition "!EditorSettings::get_singleton() || !EditorSettings::get_singleton()->has_setting(p_setting)" is true. Returning: Variant()
   at: _EDITOR_GET (editor/editor_settings.cpp:1127)
ERROR: 1 RID allocations of type 'N5GLES37TextureE' were leaked at exit.`

### Steps to reproduce

1. Open Godot using the console (e.g. the Godot console exe, a batch file as I have done above, command prompt, etc.)
2. Create or open any project.
3. Click Project -> Quit to Project List from the file menu
4. Error message appears in the console window that opened Godot

### Minimal reproduction project

N/A
Repository: PowerToys
Issue: Support netowrk proxy settings for auto update downloading
Labels: Area-Setup/Install,Area-Runner,Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

I am going to update the PowerToys by clicking update button, but something went wrong when download the install files because of my network problem. I need to setup HTTP proxy for updating.

### Scenario when this would be used?

In the settings panel, when need proxy network to download install files.

### Supporting information

It could be HTTP(s) proxy, Socks 4/5 proxy with url and port.


See `https://learn.microsoft.com/en-us/dotnet/api/system.net.webproxy`
Repository: ant-design
Issue: TimePicker.RangePicker设置defaultValue后再次选择开始时间时赋值错误
Labels: Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/embed/fan-wei-xuan-ze-qi-antd-5-11-0-forked-vyxmvj?fontsize=14&hidenavigation=1&theme=dark)

### Steps to reproduce

如复现demo所示给TimePicker.RangePicker设置defaultValue值为[dayjs("00:00:00", "HH:mm:ss"),dayjs("00:00:00", "HH:mm:ss")]时，再次点击设置开始时间，点击确定后赋值得却是结束时间


### What is expected?

正常赋值到开始时间输入框内

### What is actually happening?

赋值到结束时间输入框内

| Environment | Info |
| --- | --- |
| antd | 5.11.1 |
| React | 18.2.0 |
| System | windows11 |
| Browser | Chrome 119.0.6045.106（正式版本）（64 位） |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: node
Issue: Unhandled rejection event in web streams when stream error is piped
Labels: web streams

### Version

21.1.0

### Platform

Linux kunigunde 6.5.9-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 26 Oct 2023 00:52:20 +0000 x86_64 GNU/Linux

### Subsystem

streams/web

### What steps will reproduce the bug?

Run the following code:

```javascript
import { ReadableStream } from "stream/web";

process.on('unhandledRejection', (err) => {
	console.log(`Unhandled rejection: ${err.message}`);
});

const stream1 = new ReadableStream({
	start(controller) {
		controller.error(new Error('Test'));
	},
});

const stream2 = new TransformStream();

stream1.pipeTo(stream2.writable);

try {
	await stream2.readable.getReader().read();
} catch (err) {
	console.log(`Caught error: ${err.message}`);
}
```

### How often does it reproduce? Is there a required condition?

With the given code example, it happens every time.

It does _not_ happen in the following situations:
* Reading from `stream1` directly rather than piping it to `stream2`
* Reading from `stream2` but not `catch`ing the error but letting the app crash instead

### What is the expected behavior? Why is that the expected behavior?

No `unhandledRejection` event should be triggered, since the exception is actually handled.

### What do you see instead?

An `unhandledRejection` event is triggered. The output of the sample script is:
```
Caught error: Test
Unhandled rejection: Test
```

### Workaround

I’m not sure if this has any unintended side effects, but catching the rejection by the promise returned by `pipeTo()` seems to solve the problem:
```javascript
stream1.pipeTo(stream2.writable).catch(() => {});
```
Repository: next.js
Issue: default.js fallback file renders without CSS modules
Labels: bug

### Link to the code that reproduces this issue

https://github.com/graddaniel/broken-style-at-default

### To Reproduce

1. `yarn run dev`
2. navigate to http://localhost:3002/someroute - should render fine
3. navigate to http://localhost:3002/someroute/asd - someroute's children fallback is no longer styled (font is black instead of green)

### Current vs. Expected behavior

Current:
When a route, which uses a `default.js` file with CSS modules for `children` fallback is rendered, the styling is missing. The class name is set properly, but it's definition is missing in the browser.

Expected:
When a route, which uses a `default.js` file with CSS modules for `children` fallback is rendered it is correctly styled according to classes in imported CSS modules.

Additional info:
Tailwind styling renders correctly.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #98~20.04.1-Ubuntu SMP Mon Oct 9 16:43:45 UTC 2023
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.0.3-canary.5
  eslint-config-next: 14.0.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

I have generated the application according to the installation guide and added a minimalistic sample of the issue.

installation guide: https://nextjs.org/docs/getting-started/installation

![bug2](https://github.com/vercel/next.js/assets/48184737/aa0fc3e4-de9c-4c71-b4d3-281edb1f5a43)
![bug3](https://github.com/vercel/next.js/assets/48184737/b50bf889-c91a-4739-bc9e-ced521f46d94)
Repository: next.js
Issue: Next.js 14 build hangs forever with ace-code-editorjs while it works fine with Next.Js 13
Labels: bug

### Link to the code that reproduces this issue

https://github.com/ats1999/nextjs-14-build-hangs

### To Reproduce

1. git clone https://github.com/ats1999/nextjs-14-build-hangs.git
2. cd nextjs-14-build-hangs
3. npm i
4. npm run build

You'll get to see that nextjs build will hang forever.

### Current vs. Expected behavior

Currently, i am expecting that it should build nextjs but it is hanging forever.



### Verify canary release

- [x] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:04:44 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T8103
Binaries:
  Node: 18.16.1
  npm: 9.5.1
  Yarn: N/A
  pnpm: 8.6.5
Relevant Packages:
  next: 14.0.2
  eslint-config-next: 14.0.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

The build is hanging with the next 14.0.2 and upper versions but it's working fine with 13.x.x.

I haven’t checked all versions, but the above two versions have been checked.

The build is hanging on the local machine as well as vercel deployment

Although, npm run dev is working fine.

You can just remove `<Editor id="editor" />` from `app/page.tsx` and the build will work fine. 

Why is this happening? This is not happening while local development, but occurs only when i am running `npm run build`
Repository: vscode
Issue: `explorer.fileNesting.expand` ignored for items with `capture` and wildcard usage
Labels: bug,file-explorer,file-nesting

<!-- ⚠️⚠️ 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.84.2 (user setup)
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:51:52.184Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Windows_NT x64 10.0.19045

Steps to Reproduce:

1. Settings.json:
    ```json
    "explorer.fileNesting.enabled": true,
    "explorer.fileNesting.patterns": {
        "*.ts": "$(capture).js, $(capture).d.ts.map, $(capture).*.ts, $(capture)_*.js, $(capture)_*.ts"
    },
    "explorer.fileNesting.expand": false,
    ```
2. Files: `environment.ts` and `environment.development.ts`
3. Make sure `environment.ts` is unexpanded
4. Unfocus VSCode window
5. Refocus VSCode window
6. `environment.ts` gets expanded automatically.
Repository: go
Issue: proposal: slices: add Cut, CutPrefix and CutSuffix
Labels: Proposal

The strings and bytes packages have Cut, CutPrefix, and CutSuffix.

I propose adding the following functions to the slices package:

```go
func Cut[S ~[]E, E comparable](s S, sep ...E) (before, after S, found bool)
func CutPrefix[S ~[]E, E comparable](s S, prefix ...E) (after S, found bool)
func CutSuffix[S ~[]E, E comparable](s S, suffix ...E) (before S, found bool)
```

For ergonomics, I chose to make sep/prefix/suffix variadic, since most uses I can think of (e.g., simple parsers) would generally have one, or a few elements at most.
Repository: material-ui
Issue: [icons] Missing "Area Chart" icon
Labels: external dependency,package: icons

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example:

As you can see there is an icon called "Area Chart"
https://fonts.google.com/icons?icon.set=Material+Icons&selected=Material+Icons+Outlined:area_chart:&icon.query=area+chart

This doe not exist on the mui.com icons demo (or in the package):
https://mui.com/material-ui/material-icons/?query=area


### Current behavior 😯

It appears some icons are missing - even thought mui.com says:
"@mui/icons-material includes the 2,100+ official Material Icons"

### Expected behavior 🤔

_No response_

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```

  System:
    OS: macOS 14.1
  Binaries:
    Node: 20.5.1 - ~/.local/share/asdf/installs/nodejs/20.5.1/bin/node
    Yarn: Not Found
    npm: 9.8.0 - ~/.local/share/asdf/plugins/nodejs/shims/npm
  Browsers:
    Chrome: 119.0.6045.123
    Edge: Not Found
    Safari: 17.1
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1 
    @emotion/styled: ^11.11.0 => 11.11.0 
    @mui/base:  5.0.0-beta.23 
    @mui/core-downloads-tracker:  5.14.17 
    @mui/icons-material: ^5.14.16 => 5.14.16 
    @mui/material: ^5.14.17 => 5.14.17 
    @mui/private-theming:  5.14.17 
    @mui/styled-engine:  5.14.17 
    @mui/system:  5.14.17 
    @mui/types:  7.2.8 
    @mui/utils:  5.14.17 
    @types/react: ^18.2.15 => 18.2.36 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: ^5.0.2 => 5.2.2 
```
</details>
Repository: vscode
Issue: Explore quick fixes and command decoration being attached to the previous command (with help of sticky scroll)
Labels: feature-request,terminal-shell-integration,terminal-sticky-scroll
Repository: vscode
Issue: Rethink how z-index is assigned within the editor
Labels: feature-request,editor-sticky-scroll,editor-widgets

We are currently running into a problem where sticky scroll currently appears below the inline chat zone-widget and below the PR comments. A proposal has been made to increase the z-index to 11 in https://github.com/microsoft/vscode/issues/174134, but it appears this can cause issues (see issue for more details). We have come to a point where we may have to rethink how z-indices are assigned within the editor (perhaps automatically). The following are the constraints to respect: 

(1) nothing from within the editor should be above widget outside the editor 
(2) sticky scroll should be the top-most widget within the editor

Perhaps the editor can offer to z-index contexts for important widgets (sticky scroll) and other widgets (the rest). 

cc @jrieken