sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: stable-diffusion-webui
Issue: [Bug]: Archlinux cannot install 
Labels: asking-for-help-with-local-system-issues

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

When I try to install it I got this error : 
`rocBLAS error: Cannot read /home/ht/stable-diffusion-webui/venv/lib/python3.11/site-packages/torch/lib/rocblas/library/TensileLibrary.dat: No such file or directory
/dev/fd/63: line 241:  5167 Aborted                 (core dumped) "${python_cmd}" "${LAUNCH_SCRIPT}" "$@"
`

### Steps to reproduce the problem

1. Go to .... 
2. Press ....
3. ...


### What should have happened?

the above line explains all

### Version or Commit where the problem happens

1.4.1

### What Python version are you running on ?

Python 3.11.x (above, no supported yet)

### What platforms do you use to access the UI ?

Linux

### What device are you running WebUI on?

AMD GPUs (RX 5000 below)

### Cross attention optimization

Automatic

### What browsers do you use to access the UI ?

Brave

### Command Line Arguments

```Shell
No
```


### List of extensions

No

### Console logs

```Shell
`rocBLAS error: Cannot read /home/ht/stable-diffusion-webui/venv/lib/python3.11/site-packages/torch/lib/rocblas/library/TensileLibrary.dat: No such file or directory
/dev/fd/63: line 241:  5167 Aborted                 (core dumped) "${python_cmd}" "${LAUNCH_SCRIPT}" "$@"
`
```


### Additional information

_No response_
Repository: axios
Issue: The axios always try ipv6 first when send request to http://localhost:8800，even if I set family to 4
Labels: priority::medium

### Describe the bug

The axios always try ipv6 first when send request to http://localhost:8800，even if I set family to 4.

My server does not listen to ipv6 by default.
So, this issue will cause a long initial connection time(about 300ms).

### To Reproduce

1. start a http server that does not listen on ipv6:
this is a poco http server for c++
```c++
  Poco::Net::HTTPServerParams *params = new Poco::Net::HTTPServerParams;
  params->setMaxQueued(100);
  params->setMaxThreads(16);

  Poco::Net::ServerSocket socket(Poco::Net::SocketAddress("localhost", port_));
  Poco::Net::HTTPServer server(new RequestHandlerFactory(), socket, params);
  server.start();
```
2. send any request to the server use localhost:
```ts
const axios_instance = axios.create({
  baseURL: 'http://localhost:8800',
  family: 4,
  timeout: 1000,
});

axios_instance.post("/project/-/open", {
      path: path
});
```
3. check the initial connection from DevTools
4. capture the tcp traffic:
use localhost
![image](https://github.com/axios/axios/assets/31911231/61389e68-268b-4dc1-a566-c707c2212c78)
use 127.0.0.1
![image](https://github.com/axios/axios/assets/31911231/b035428a-1f5a-451a-abec-5c6f2ac3c020)



### Code snippet

_No response_

### Expected behavior

send request to localhost over ipv4 only(or first) when set the family to 4.

### Axios Version

1.4.0

### Adapter Version

XHR/HTTP

### Browser

Webview2(Edge)

### Browser Version

_No response_

### Node.js Version

v18.15.0

### OS

windows11

### Additional Library Versions

_No response_

### Additional context/Screenshots

_No response_
Repository: opencv
Issue: Negative_Test/Rect_Test/*.Overflows fails for float and double with ENABLE_FAST_MATH option
Labels: bug,optimization,category: core

### System Information

OpenCV: current 4.x (4.8.0-dev)
Platform: Ubuntu 18.04, GCC 7.5
Hardware: Core i5 2500k (no avx2 and no avx512)

### Detailed description

Looks like over-optimization in the test body itself. Detailed investigation is required.

### Steps to reproduce

```
cmake -DENABLE_FAST_MATH=1 ../opencv
make -j4
./bin/opencv_test_core --gtest_filter=Negative_Test/Rect_Test/1.Overflows*
```

### 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: opencv
Issue: Core_QR_Solver.accuracy64f test failed with ENABLE_FAST_MATH option
Labels: bug,optimization,category: core

### System Information

OpenCV: current 4.x (4.8.0-dev)
Platform: Ubuntu 18.04, GCC 7.5
Hardware: Core i5 2500k (no avx2 and no avx512)

### Detailed description

Accuracy test fails.

### Steps to reproduce

```
cmake -DENABLE_FAST_MATH=1 ../opencv
make -j4
./bin/opencv_test_core --gtest_filter=Core_QR_Solver.accuracy64f
```

### 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: Allow contributing to the context menu in the TreeView's empty space 
Labels: feature-request,tree-views

<!-- ⚠️⚠️ 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. -->
We can contribute to the context menu of a tree view item using `view/item/context`. However, there is no way to do it for the empty space under all nodes (as in the Explorer). This could be useful to put commands that initialize or add nodes.

![image](https://github.com/microsoft/vscode/assets/12927950/e5da4afa-321d-436a-a0c3-1f7f55a1f142)

Under `NyuziProcessor` nodes we cannot right click to add more projects for example...
Repository: next.js
Issue: Docs: cms-agilitycms
Labels: good first issue,examples

### What is the improvement or update you wish to see?

The documentation for AgilityCMS urgently requires comprehensive enhancements. The existing materials impede developers' experiences by necessitating conjectures about the correct steps - this viewpoint comes from a user familiar with the AgilityCMS system. There is an evident disparity between the terminology used in the official documents and that on the AgilityCMS platform itself. This could potentially deter new developers, causing them to abandon their efforts prematurely. Although I've strictly adhered to the NextJS example code and diligently followed the provided tutorial (to the best of my ability given the circumstances), I cannot get this example to work. There is no feedback that even suggests how to fix the error (and I'm guessing even if I fix the "HeroPost" problem, I anticipate more errors to come...) 

Far too complicated. Not a positive developer experience. 

### Is there any context that might help us understand?

Error:
```
Agility CMS => Fetching sitemap for getAgilityPaths...
Agility CMS => Getting page props for '/'...
- error Error: Could not find a component with the name HeroPost. Tried searching:
        /xxxxx/components/hero-post.tsx',
        /xxxxx/lib/components/hero-post.tsx',
        /xxxxx/components/HeroPost.tsx',
        /xxxxx/lib/components/HeroPost.tsx'.
```
....it's literally right there under `xxxxx/components/hero-post.tsx`? 

### Does the docs page already exist? Please link to it.

https://github.com/vercel/next.js/blob/canary/examples/cms-agilitycms/README.md
Repository: PowerToys
Issue: Wrong result order in powertoys run
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.71.0

### Installation method

GitHub, PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

1. On a machine with [Process Explorer](https://learn.microsoft.com/en-us/sysinternals/downloads/process-explorer) along with [TortoiseSVN](https://tortoisesvn.net/) and/or [TortoiseGit](https://tortoisegit.org/) installed.
2. Search for "procex" in powertoys run
3. all TortoiseSVN/Git shortcuts shows up first, followed by procexp64.exe at the bottom of the list

![image](https://github.com/microsoft/PowerToys/assets/139963448/0f1ae393-ee90-47f8-aad8-0eeedfaa022c)

I think the issue is that tortoise executable ends with *Proc.exe. 
Even if "*proc.exe" is a valid result for "procex" querry, I think "procexp64.exe" should be the first result because it is closer to what I typed (litteral match, no missing character).
I was unabled to reproduce it with simple text files though.

Similarily, by typing "proce", the first results are the ones that resemble the less with what I typed (many missing characters)
![image](https://github.com/microsoft/PowerToys/assets/139963448/6e8b3f60-014e-4730-94a5-0d774423873a)


### ✔️ Expected Behavior

procexp.exe or procexp64.exe shows at the top of list

or more genereally : 
The result that resembles my querry the most shows at the top of the list

### ❌ Actual Behavior

all TortoiseSVN/Git shortcuts shows up first, followed by procexp.exe at the bottom of the list

or more genereally : 
The result that resembles my querry the most shows at the bottom of the list

### Other Software

_No response_
Repository: terminal
Issue: the Terminal's system menu (alt+space) doesn't have keyboard accelerators
Labels: Help Wanted,Issue-Bug,Product-Terminal,Area-Windowing

### Windows Terminal version

-

### Windows build number

-

### Other Software

-

### Steps to reproduce

run it

### Expected Behavior

I intentionally categorize this as a bug, not as a feature request. 
Windows has had comprehensive keyboard navigation for more than two decades. 
I do not know what happened, but recently everything is gone. 
Open a context menu, no shortcuts. They take longer to appear, do fancy animations or whatever, but they are unusable without the mouse. 
Same deal with this disaster here.
Try to use it without a mouse. Try to use *all* of it without a mouse and you will understand. 

conhost: alt-space, `Properties` and `P` is underlined. It has a shortcut. 
wt: alt-space, there is a `Settings` entry, but no shortcut. Why. 

conhost: ctrl-tab, cycle through various settings tabs, as fast as the keyboard can send keypresses. 
wt: we use tab. It changes the focus of the item selected. Tab to go down to the list of categories. Categories do not change: one must press return. _Okay_. Startup, press down, press enter, see "Interaction" tab. Press down, press enter, see "Appearance" tab. ... Where did the focus just go? Oh look, at the _bottom of the window_ a new button has appeared. Now you have to hold up to get focus back where it should have been. _Okay_.  Press enter on "Color schemes". Now focus has gone _in_ the tab contents? Why? Escape does not go up the hierarchy. Did 4 shift-tab to get back at the list.
'Actions'. Moving focus up-down shows the pencil button, but there is no way to actually activate it. You _have_ to use the mouse button. I mashed my entire keyboard. Nothing at all happened. The only two keys that do something are 'up' and 'down'.
No idea why we must, but we click the mouse. It's like I'm playing diablo all over again. 

conhost: alt-space, p, ctrl-tab (as needed), press a letter/digit or alt+letter/digit and you've accessed or changed any available setting immediately. _Any_ configuration option available to the user is 4(min) 8(max) keypresses away. 

I'm not gonna sugarcoat it.
Your efforts and the sheer amount of work you have put are both astounding
But you are focusing so hard on features and fanciness that you've completely ignored _usability_
Keyboard navigation is _not_ something you can tack-on after the fact. Yes, I see the Actions list. That, is not keyboard navigation. 
Thank you for your time.

### Actual Behavior

Impossible to use without a mouse.
Repository: react
Issue: Bug: undefined behavior with input checkbox onChange not triggered
Labels: Type: Bug,Component: DOM

Hello,

I have also discovered a bug where when we do `e.preventDefault()` on an `onClick()` function, inputs will not be updated correctly

Link to code example:


Here is a demo https://codesandbox.io/s/vigorous-albattani-g3hv29

Has you can see in the demo, when the state is `true` the checkbox is not checked


## The current behavior

The checkbox is not checked when we have a  `e.preventDefault()` even if the state is `true`

## The expected behavior

The checkbox should have the value of the checked props

## Notes

- I've also created some unit test for checkbox in #27127 
- Related to #27016
Repository: storybook
Issue: [Bug]: Addon controls always shows "-" when `control: false` instead of value set
Labels: bug,needs triage

### Describe the bug

When I set a prop to not controllable through the option `control: false` in `argTypes` it doesn't display the value set in the `arg` parameter.

I expected to see the value passed to the component in order to be able to understand in storybook the props necessary to achieve the result displayed there.

![image](https://github.com/storybookjs/storybook/assets/71693205/155cc1e0-a9af-49e2-b50d-debc478da1a6)


### To Reproduce

https://stackblitz.com/edit/storybook-react-template-wlwehw-anxeh4

### System

```shell
Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
  Binaries:
    Node: 16.20.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 9.4.2 - /usr/local/bin/npm
  npmPackages:
    @storybook/addon-essentials: 7.1.0 => 7.1.0 
    @storybook/preset-create-react-app: 7.1.0 => 7.1.0 
    @storybook/react: 7.1.0 => 7.1.0 
    @storybook/react-webpack5: ^7.1.0 => 7.1.0 
    @storybook/theming: 7.1.0 => 7.1.0
```


### Additional context

_No response_
Repository: next.js
Issue: Build stuck when using ace-builds and ace-builds/webpack-resolver
Labels: bug,linear: next

### 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: #1 SMP Tue Jun 27 22:28:01 UTC 2023
    Binaries:
      Node: 16.14.2
      npm: 8.5.0
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.10
      eslint-config-next: 13.4.10
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: export
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/modest-hawking-c5mzf9?file=%2Fcomponents%2Fcode-editor.jsx%3A47%2C32

### To Reproduce

Run `npm run build`, the build stage stucks in the optimization phase.

### Describe the Bug

Using the `ace-builds` package results in a stuck build, I'm suspecting that the `ace-builds/webpack-resolver` is causing this issue with NextJS, removing that line of code makes the build succeeds normally.



### Expected Behavior

The build should not get stuck because of the esm or webpack resolvers in ace

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

<sub>[NEXT-1467](https://linear.app/vercel/issue/NEXT-1467/build-stuck-when-using-ace-builds-and-ace-esm-resolver)</sub>
Repository: PowerToys
Issue: Return of the old functionality
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Add setting for disable the "- Shortcut" text for shortcuts.

### Scenario when this would be used?

Saves a lot of time.

### Supporting information

_No response_
Repository: pytorch
Issue: DISABLED test_conv_with_as_strided_dynamic_shapes_cuda (__main__.DynamicShapesCudaTests)
Labels: module: rocm,triaged,module: flaky-tests,skipped

Platforms: rocm

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/failure/test_conv_with_as_strided_dynamic_shapes_cuda) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/15120975791).

Over the past 72 hours, it has flakily failed in 6 workflow(s).

**Debugging instructions (after clicking on the recent samples link):**
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Grep for `test_conv_with_as_strided_dynamic_shapes_cuda`


Test file path: `inductor/test_torchinductor_dynamic_shapes.py`

ResponseTimeoutError: Response timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/inductor/test_torchinductor_dynamic_shapes.py -1 (connected: true, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang
Repository: godot
Issue: Unexpected "Indent" in class body when the real problem is different, and in another line.
Labels: bug,topic:gdscript,usability

### Godot version

v4.1.1.stable.official.bd6af8e0e

### System information

Windows 10.0.19045 - Vulkan (Compatibility) - GeForce GT 540M- Intel Core i7-2670QM CPU @ 2.20GHz (8 Threads)

### Issue description

Writing something after func definition, for example:

![image](https://github.com/godotengine/godot/assets/84321760/d361ccc1-4a6b-4880-9aaa-060f3cb6895c)

Causes an "Unexpected Indent in class body" error to appear one line below, as shown.

This message does not inform the user about the real problem in their code, and makes them look for a problem in a perfectly correct line below instead, confusing them and making debugging unnecessarily harder and longer.

### Steps to reproduce

Copy and paste this code, or write a similar one in the editor, then observe the bug:

```gdscript
extends Node


func _ready():K
	var rng = RandomNumberGenerator.new()


	rng.randomize()
	print(rng.seed)
```

### Minimal reproduction project

N/A
Repository: tensorflow
Issue: Random predictions with intel-tensorflow when OMP_THREAD_LIMIT is set
Labels: stat:awaiting tensorflower,type:bug,subtype:cpu-intel,TF 2.13

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

The problem arises when using *intel-tensorflow*

### Source

binary

### TensorFlow version

unknown, 2.13.0 (package intel_tensorflow-2.13.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl)

### Custom code

No

### OS platform and distribution

Linux Ubuntu 20.04

### Python version

3.8, 3.9, 3.10, 3.11

### Current behavior?

This problem only happens when using the *intel-tensorflow* package which uses the mkl library. When the environment variable OMP_THREAD_LIMIT is set, the predictions of some standard models become random when running on cpu.

During the run, a warning from OMP is shown:
```
OMP: Warning #96: Cannot form a team with 36 threads, using 12 instead.
OMP: Hint Consider unsetting KMP_DEVICE_THREAD_LIMIT (KMP_ALL_THREADS), KMP_TEAMS_THREAD_LIMIT, and OMP_THREAD_LIMIT (if any are set).
```
This warning suggests to unset the variable _OMP_THREAD_LIMIT_ but I think a randomness/instability in the prediction of models needs more than a warning with a "Hint".

To reproduce the problem:
* Create an environment with *intel-tensorflow* installed
* Copy the code in the following section into a file *test_script.py*
* Run the following commands:
  * `python test_script.py`
  * `OMP_THREAD_LIMIT=2 python test_script.py`  (edited)

### Standalone code to reproduce the issue

```python
import tensorflow as tf


if __name__ == "__main__":
    with tf.device("/cpu:0"):
        model = tf.keras.applications.efficientnet.EfficientNetB0()
        img = tf.ones((1, 224, 224, 3))
        pred = model(img)

        print(f"Result: {pred[0, :5]}")
```


### Relevant log output

```shell
# Run without OMP_THREAD_LIMIT
...
Result: [0.00066389 0.00075261 0.00108045 0.00210853 0.00316559]

# Run with OMP_THREAD_LIMIT
...
OMP: Warning #96: Cannot form a team with 6 threads, using 2 instead.
OMP: Hint Consider unsetting KMP_DEVICE_THREAD_LIMIT (KMP_ALL_THREADS), KMP_TEAMS_THREAD_LIMIT, and OMP_THREAD_LIMIT (if any are set).
Result: [0.00030835 0.00062532 0.00057299 0.00088017 0.00140722]
```
Repository: next.js
Issue: Full reload of page with multiple root layouts files
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Hi Team, 

As mentioned in the docs that,

Navigating across multiple root layouts will cause a full page load (as opposed to a client-side navigation). For example, navigating from /cart that uses app/(shop)/layout.js to /blog that uses app/(marketing)/layout.js will cause a full page load. This only applies to multiple root layouts.

Link: https://nextjs.org/docs/app/api-reference/file-conventions/layout

I have tried this out by keeping multiple layout files for each of the routes, but the page dosent seems to have full reload on navigation.

Kindly help us out here if I am missing something.

Thanks,
Rahul Nag
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

NA

### To Reproduce

Hi Team, 

As mentioned in the docs that,

Navigating across multiple root layouts will cause a full page load (as opposed to a client-side navigation). For example, navigating from /cart that uses app/(shop)/layout.js to /blog that uses app/(marketing)/layout.js will cause a full page load. This only applies to multiple root layouts.

Link: https://nextjs.org/docs/app/api-reference/file-conventions/layout

I have tried this out by keeping multiple layout files for each of the routes, but the page dosent seems to have full reload on navigation.

Kindly help us out here if I am missing something.

Thanks,
Rahul Nag

### Describe the Bug

Hi Team, 

As mentioned in the docs that,

Navigating across multiple root layouts will cause a full page load (as opposed to a client-side navigation). For example, navigating from /cart that uses app/(shop)/layout.js to /blog that uses app/(marketing)/layout.js will cause a full page load. This only applies to multiple root layouts.

Link: https://nextjs.org/docs/app/api-reference/file-conventions/layout

I have tried this out by keeping multiple layout files for each of the routes, but the page dosent seems to have full reload on navigation.

Kindly help us out here if I am missing something.

Thanks,
Rahul Nag

### Expected Behavior

It dosent reload the full page

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: pytorch
Issue: Efficient BMM for sparse-dense tensors
Labels: module: sparse,triaged,topic: new features

### 🚀 The feature, motivation and pitch

Hi,
I want to perform a sparse-dense BMM and compute gradients for the sparse matrix. Is there an operation in torch which does it efficiently? According to [this table](https://pytorch.org/docs/stable/sparse.html#supported-operations), `torch.bmm` computes only the dense gradients. Also, it's limited to the COO layout.

### Alternatives

_No response_

### Additional context

_No response_

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer