sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [material-ui][Tooltip] Stays visible on scroll
Labels: bug 🐛,component: tooltip,package: material-ui,regression

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/s/mui-tooltip-scroll-bug-88jrqh

Steps:

1. hover over one of the test items
2. scroll up or down


### Current behavior 😯

The tooltip remains visible until scrolling has stopped

### Expected behavior 🤔

The tooltip should close when the user scrolls

### Context 🔦

We have a data table with tooltips, and scrolling in the table causes weird interactions with the tooltip. The tooltip will remain visible on an element out of view when the user is scrolling.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 13.4
  Binaries:
    Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.16.0/bin/yarn
    npm: 8.19.4 - ~/.nvm/versions/node/v16.16.0/bin/npm
  Browsers:
    Chrome: 115.0.5790.170
    Edge: Not Found
    Safari: 16.5
  npmPackages:
    @emotion/react: 11.10.4 => 11.10.4 
    @emotion/styled: 11.10.4 => 11.10.4 
    @mui/base:  5.0.0-beta.7 
    @mui/core-downloads-tracker:  5.14.0 
    @mui/icons-material: ^5.8.2 => 5.11.9 
    @mui/material: ^5.14.0 => 5.14.0 
    @mui/private-theming:  5.13.7 
    @mui/styled-engine:  5.13.2 
    @mui/styles: ^5.11.11 => 5.11.11 
    @mui/system:  5.14.0 
    @mui/types:  7.2.4 
    @mui/utils:  5.13.7 
    @types/react: 18.0.28 => 18.0.28 
    react: 18.2.0 => 18.2.0 
    react-dom: 18.2.0 => 18.2.0 
    typescript: 4.7.4 => 4.7.4 

```
</details>
Repository: next.js
Issue: Locale paths are using root pages
Labels: bug

### 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 PREEMPT_DYNAMIC Thu, 03 Aug 2023 16:02:01 +0000
    Binaries:
      Node: 20.5.0
      npm: 9.8.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.14-canary.0
      eslint-config-next: 13.4.13
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Internationalization (i18n)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/chardon55/next-test1

### To Reproduce

1. Run a Next.js project in App router architecture **with i18n on**
2. Access a locale path (e.g., "http://127.0.0.1:3000/en")
3. See the rendered page

![en](https://github.com/vercel/next.js/assets/44740171/91960111-3d7b-4180-8f70-668e933b7b89)

![fr](https://github.com/vercel/next.js/assets/44740171/f0afd8c6-3694-4172-bd4e-f67632c6c36e)


### Describe the Bug

When you access a locale path ("/en", "/fr"), if the locale is the default locale, it redirects to the root page (the real "/"). For non-default locales, it usually becomes 404.

### Expected Behavior

In the previous versions (e.g., 13.4.12), accessing a locale page uses the page in the corresponding "[locale]" directory, instead of in the root directory.

### Which browser are you using? (if relevant)

Chrome 115.0.5790.170 & Firefox 116.0.2

### How are you deploying your application? (if relevant)

next start (using yarn)
Repository: go
Issue: x/tools/gopls: show fmt.Stringer representation of a const on mouse over 
Labels: FeatureRequest,gopls,Tools

### What did you do?
Moused over `Meters` or any of the other consts. 
```go
package si

type Distance int64

const (
      Nanometers  = 1
      Micrometers = 1000 * Nanometers
      Millimeters = 1000 * Micrometers
      Meters      = 1000 * Millimeters
)

// String pretty formats the units to a reasonable human readable representation i.e. "100m", "500nm", 
func (v Velocity) String() string {
      return formatWithBase(v, baseNano, 'm')
}
```



### What did you expect to see?
What I want is what is currently done today with the time.Duration type:
![image](https://github.com/golang/go/assets/121810678/14debf00-a328-485d-83cf-735115d4c299)

I understand this implies a HUGE change to gopls, since it would mean somehow running arbitrary code. This carries some worrysome implications:
- Security risk
- How to implement this without exploding gopls binary size
- Recursive risk

I'd understand if this cannot be done today, however I want to start the discussion since this would be a large quality of life improvement for me since I regularly work with SI unit consts to define program behaviour.

I'd also like to refer you all the TinyGo `interp` package which safely evaluates Go code on initialization: https://github.com/tinygo-org/tinygo/tree/release/interp.

### What did you see instead?
Got very long numbers which are not immediately interpretable, much less when defining other more complex consts with the Distance type.
![image](https://github.com/golang/go/assets/121810678/f6b6fca2-e19b-4622-9e58-2e8fc4b42fb4)
Repository: opencv
Issue: cv::compare() and cv::cuda::compare() might give different result
Labels: bug,category: gpu/cuda (contrib)

### System Information

OpenCV 4.8.0
Windows 7 64b
latest Visual Studio 2019

### Detailed description

When using a non-integer threshold with an integer matrix, the internal rounding of the threshold differs between cv::compare() and cv::cuda::compare(), leading to different results.

An easy workaround is to manually rounding the threshold to the desired edge (floor(), ceil(), round()...) before calling compare(), but it is less handy for the generic case where the threshold can be the result of an algorithm, and the input matrix has no specific depth.
I have tracked it down because it was the root of strange differences between CPU and (supposedly equivalent) GPU code.

Changing the rounding behaviour of `cv::compare()` or `cv::cuda::compare()` to make them match might be a breaking change for existing code.

Perhaps only extra documentation is needed here.

### Steps to reproduce

```
    cv::Mat m1_cpu(1, 1, CV_16U);
    cv::Mat m2_cpu(1, 1, CV_8U);
    cv::Mat m3_cpu(1, 1, CV_8U);
    cv::cuda::GpuMat m1_gpu(1, 1, CV_16U);
    cv::cuda::GpuMat m2_gpu(1, 1, CV_8U);
    m1_cpu = cv::Scalar::all(11);
    m1_gpu.upload(m1_cpu);
    cv::compare(m1_cpu, cv::Scalar::all(10.6), m2_cpu, cv::CMP_GT);
    cv::cuda::compare(m1_gpu, cv::Scalar::all(10.6), m2_gpu, cv::CMP_GT);
    m2_gpu.download(m3_cpu);
    const double n = cv::norm(m2_cpu, m3_cpu, cv::NORM_INF);
    CV_Assert(fabs(n)<1e-6);
```

### Issue submission checklist

- [X] I report the issue, it's not a question
- [ ] 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: Focusing another window while dragging a file from the FileExplorer causes a TreeError
Labels: bug,file-explorer

<!-- ⚠️⚠️ 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. -->
- VS Code Version: 1.81.0
- OS Version: Windows_NT x64 10.0.19044

Steps to Reproduce:

1. Start dragging a file in the file explorer
2. Focus another window, either by pressing Alt+Tab or hovering over an application icon in the Windows taskbar
3. Focus back on VSCode and release the file in the file explorer again
4. An error window showing `TreeError [FileExplorer] Data tree node not found: ExplorerItem: test.txt` pops up
Repository: pytorch
Issue: [ux] Suppot torch.tensor(set([1,2,3]))
Labels: triaged,needs research,topic: new features,module: python frontend

### 🚀 The feature, motivation and pitch

If it's easy to do, it would save a few keystrokes ( + maybe same for `dict_keys` and `dict_values`) and maybe some copies and python objects on the heap for large inputs:
```python
import torch

torch.tensor(list(set([1,2,3])))
# tensor([1, 2, 3])

torch.tensor(set([1,2,3]))
# RuntimeError: Could not infer dtype of set

# torch.tensor(set([1,2,3]), dtype = torch.int64)
# TypeError: an integer is required (got type set)

# torch.tensor({1 : 'a', 2 : 'b', 3 : 'c'}.keys())
# RuntimeError: Could not infer dtype of dict_keys


# torch.tensor({1 : 'a', 2 : 'b', 3 : 'c'}.keys(), dtype = torch.int64)
# TypeError: an integer is required (got type dict_keys)
```

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD
Repository: go
Issue: testing: report non-zero exit status in -json output
Labels: Proposal,Proposal-Accepted

<!--
Our proposal process is documented here:
https://go.dev/s/proposal-process
-->

I have the following test file `sample_test.go`:
```go
package main

import (
	"os"
	"testing"
)

func Test(t *testing.T) {
	t.Run("1", func(t *testing.T) {
		t.Run("1.1", func(t *testing.T) {
			os.Exit(2)
                         // os.Exit(0)
		})
	})
}
```

If I use go test on that file, I get the exit code in the output as expected:

```console
$ go test -json -test.paniconexit0 -test.run Test .      
{"Time":"2023-08-08T16:09:56.448232+02:00","Action":"start","Package":"awesomeProject3"}
{"Time":"2023-08-08T16:09:56.611997+02:00","Action":"run","Package":"awesomeProject3","Test":"Test"}
{"Time":"2023-08-08T16:09:56.612096+02:00","Action":"output","Package":"awesomeProject3","Test":"Test","Output":"=== RUN   Test\n"}
{"Time":"2023-08-08T16:09:56.612131+02:00","Action":"run","Package":"awesomeProject3","Test":"Test/1"}
{"Time":"2023-08-08T16:09:56.612133+02:00","Action":"output","Package":"awesomeProject3","Test":"Test/1","Output":"=== RUN   Test/1\n"}
{"Time":"2023-08-08T16:09:56.612136+02:00","Action":"run","Package":"awesomeProject3","Test":"Test/1/1.1"}
{"Time":"2023-08-08T16:09:56.612138+02:00","Action":"output","Package":"awesomeProject3","Test":"Test/1/1.1","Output":"=== RUN   Test/1/1.1\n"}
{"Time":"2023-08-08T16:09:56.61243+02:00","Action":"output","Package":"awesomeProject3","Test":"Test/1/1.1","Output":"exit status 2\n"}
{"Time":"2023-08-08T16:09:56.612473+02:00","Action":"output","Package":"awesomeProject3","Output":"FAIL\tawesomeProject3\t0.164s\n"}
{"Time":"2023-08-08T16:09:56.612476+02:00","Action":"fail","Package":"awesomeProject3","Elapsed":0.164}
```

If I use go test2json instead, I will get no exit code in the output at all.
```console
$ go test -c -o awesomeProject3 ./...
$ go tool test2json -t ./awesomeProject3 -test.v -test.run Test       
{"Time":"2023-08-08T16:12:00.158467+02:00","Action":"start"}
{"Time":"2023-08-08T16:12:00.47165+02:00","Action":"run","Test":"Test"}
{"Time":"2023-08-08T16:12:00.471757+02:00","Action":"output","Test":"Test","Output":"=== RUN   Test\n"}
{"Time":"2023-08-08T16:12:00.471767+02:00","Action":"run","Test":"Test/1"}
{"Time":"2023-08-08T16:12:00.47177+02:00","Action":"output","Test":"Test/1","Output":"=== RUN   Test/1\n"}
{"Time":"2023-08-08T16:12:00.471773+02:00","Action":"run","Test":"Test/1/1.1"}
{"Time":"2023-08-08T16:12:00.471775+02:00","Action":"output","Test":"Test/1/1.1","Output":"=== RUN   Test/1/1.1\n"}
{"Time":"2023-08-08T16:12:00.472018+02:00","Action":"fail","Test":"Test/1/1.1","Elapsed":0.314}
```

Try the same commands with the zero exit code and you will see a detailed panic message in both cases.

----
1. Consider panicking on any non-zero exit code as well.
2. Consider showing the non-zero exit code in the text2json output as well.
Repository: rust
Issue: rustdoc: broken_intra_doc_links lint triggered by item behind feature gate
Labels: T-rustdoc,C-feature-request

```rust
#[cfg(feature = "notset")]
pub struct BehindFeature;

/// Frobs a blorb.
/// 
/// See also [`BehindFeature`].
pub struct Hello;
```

Causes this warning:

```
warning: unresolved link to `BehindFeature`
 --> src/main.rs:6:16
  |
6 | /// See also [`BehindFeature`].
  |                ^^^^^^^^^^^^^ no item named `BehindFeature` in scope
  |
  = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]`
  = note: `#[warn(rustdoc::broken_intra_doc_links)]` on by default

warning: `testcrate` (bin "testcrate" doc) generated 1 warning
```

(and, of course, `cargo doc --all-features` doesn't, and reveals that the link is not broken.)

Is it feasible to make this lint notice that the link is to an item behind a feature gate? And, either include that in the warning, or even elide the lint altogether? Happy to do the legwork if the rustdoc maintainers think it is feasible.

I think the compiler is doing something similar when it reports "found an item that was configured out" in errors, eg:

```
error[E0432]: unresolved import `super::BehindFeature`
  --> src/differentcodetoabove.rs:18:13
   |
18 |         use super::BehindFeature;
   |             ^^^^^^^^^^^^^^^^^^^^ no `BehindFeature` in the root
   |
note: found an item that was configured out
  --> src/differentcodetoabove.rs:2:12
   |
2  | pub struct BehindFeature;
   |            ^^^^^^^^^^^^^
   = note: the item is gated behind the `notset` feature
```
Repository: go
Issue: proposal: x/mobile: add a way to specify IPHONEOS_DEPLOYMENT_TARGET for maccatalyst
Labels: Proposal,mobile,OS-iOS

Currently if you specify the flag `-iosversion` if affects both the ios and maccatalyst frameworks. However, I need target 11.0 for ios and 13.1 for maccatalyst, because maccatalyst requires 13.1, but I don't want to raise the version for ios and lose users.

I need a way to specify different versions for the different platforms.

It may be worth it to provide a way to specify our own build config files. I believe I would be able to set `IPHONEOS_DEPLOYMENT_TARGET[sdk=macosx*]=13.1` on a build config, though that doesn't work as an env variable.
Repository: PowerToys
Issue: Can't start MWB service
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.72.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

1 - I set up host and everything ok! Set to use as service. Everything OK!
2 - I set up client and everything ok! Works as expected!
3 - I set to use as service in client machine (so I can use in lock screen) and the first time I put option on, it after a second puts it again in off. If I try again, MWB stops working. If I restart PowerToys, it starts working, but service is off...

### ✔️ Expected Behavior

When I start service, it would work normnally...

### ❌ Actual Behavior

When I set to use as service in client machine (so I can use in lock screen):
a) the first time I put option on, it after a second puts automatticly it again in off
b) If I try again, MWB stops working. If I restart PowerToys, it starts working, but service is off...

### Other Software

_No response_
Repository: stable-diffusion-webui
Issue: [Bug]: Don't start in RX 7600 (Linux)
Labels: bug-report,platform:amd

### Is there an existing issue for this?

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

### What happened?

Without set HSA_OVERRIDE_GFX_VERSION=11.0.0, this program doesn't start on my RX 7600.

I could solve this adding this variable, then I suggest to add this in webui.sh

### Steps to reproduce the problem

bash webui.sh

### What should have happened?

Missing setting HSA_OVERRIDE_GFX_VERSION=11.0.0 in source code conditionals of webui.sh.

### Version or Commit where the problem happens

1.5.1

### What Python version are you running on ?

Python 3.10.x

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

Linux

### What device are you running WebUI on?

AMD GPUs (RX 6000 above)

### Cross attention optimization

Automatic

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

Google Chrome

### Command Line Arguments

```Shell
`HSA_OVERRIDE_GFX_VERSION=11.0.0 bash webui.sh` to solve this problem.
```


### List of extensions

None

### Console logs

```Shell
Irrelevant information, because I solved the problem with the environment variable that they forgot to export in the code.
```


### Additional information

I think this bug report didn't need so many fields.
Repository: deno
Issue: Include "Deny permissions" for Deno Worker
Labels: bug

It would be beneficial to include a "Deny Permission" option for Deno Workers, extending the current permission controls and enhancing security.

Reflecting on the conversations within issues #18804 and #4867, it's apparent that more nuanced handling of permissions has been a topic of interest. Perhaps the existing WorkerOptions could be extended to include a deny field, for example :
```ts
export interface WorkerOptions {
  type?: "classic" | "module";
  name?: string;
  deno?: {
    includeNamespace?: boolean;
    permissions?: {
      read?: boolean | string[] | "inherit";
      //...
      deny?: {
        read?: boolean | string[] | "inherit";
        //...
      } | "inherit";
    } | "inherit";
  };
}
```
Repository: storybook
Issue: [Documentation]: Angular Translations - ngx-translate integration (solution provided in ticket)
Labels: documentation,needs triage

### Describe the problem

I see there's documentation for [setting up React translations](https://storybook.js.org/recipes/react-i18next#1-expose-i18next-to-storybook), but no documentation for setting up Angular translations - eg, with `ngx-translate`.

I saw the `ngx-translate` integration question raised on [this issue thread](https://github.com/storybookjs/storybook/issues/6541).

However, I couldn't get any of these solutions to work.

I reproduced the issue [in this repo](https://github.com/CMadden8/storybooktest/tree/main/org) with the most minimal code I could think of. Granted, this is an NX repo - but the NX team reckon this is a Storybook issue.

You would need `nx console` installed on the IDE, and would need to run `storybook` and then `my-app`. There is only one story in the `libs/my-app` lib.

I followed [this example](https://dsebastien.medium.com/using-ngx-translate-in-storybook-stories-3f4228f80e02) from the issue thread I linked above. This worked to get Storybook looking for the translation files. But it can't find the assets (you will see this reported in the console and the network tab), as it seems they're not being included in the build. 

I tried adding the asset paths to the Storybook config [here](https://github.com/CMadden8/storybooktest/blob/main/org/libs/my-app/ui/project.json).

However, it seems to have no effect.

I'm guessing there's a simple solution to this, but I'm just missing the key element - how do you add the assets to the Storybook build? If this can be solved, then the rest of the `ngx-translate` integration appears to work, and is straightforward. I think it would be worth documenting the correct approach if this final puzzle can be solved, as `ngx-translate` is used in almost every Angular app I've worked on.





### Additional context

_No response_
Repository: pytorch
Issue: Optimizers should use learning rates passed as tensors directly
Labels: module: optimizer,triaged,actionable,module: dynamic shapes

### 🚀 The feature, motivation and pitch

If you pass a tensor as the learning rate when constructing an optimizer, it works, but internally it does an item() on every step, which breaks graph capture and triggers synchronization warnings if you have them enabled.

It would be nice if the optimizers (maybe just the fused versions?) directly used the tensor, because then you could adjust learning rate every step while using CUDA graphs.  I wind up forcing graph rebuilds every 1000 steps or so when I want to dynamically change learning rates.

### Alternatives

_No response_

### Additional context

_No response_

cc @vincentqb @jbschlosser @albanD @janeyx99 @crcrpar @ezyang
Repository: vscode
Issue: explorer.excludeGitIgnore stops at the first .gitgnore file it finds instead of walking up the tree to the git repo root
Labels: bug,help wanted,file-explorer


Type: <b>Bug</b>

Repro recipe:
```
mkdir vscode-gitignore && cd vscode-gitignore && git init && echo 'test-directory/' > .gitignore && mkdir .vscode && echo '{ "explorer.excludeGitIgnore": true }' > .vscode/settings.json && mkdir -p subdir/test-directory && touch subdir/.gitignore && cd subdir && git status &&  /Applications/Visual\ Studio\ Code.app/Contents/MacOS/Electron --disable-extensions .
```

Expected: `test-directory` is hidden from file explorer since it's missing from the `git status` output.

Observed: `test-directory` is present in the file explorer.

I believe this is happening because VSCode is finding & using `subdir/.gitignore` without consideration of the top-level `.gitignore` file in the parent directory. Since `git ignore` considers all `.gitignore` files in the repo between the destination and the root, IWBN for `excludeGitIgnore` to do the same.

(the practical effect of this is having to duplicate entries from the root .gitignore file into descendant .gitignore files to get VSCode to ignore them)

VS Code version: Code 1.81.0 (Universal) (6445d93c81ebe42c4cbd7a60712e0b17d9463e97, 2023-08-02T12:40:02.782Z)
OS version: Darwin arm64 22.6.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (10 x 24)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|4, 3, 3|
|Memory (System)|32.00GB (1.01GB free)|
|Process Argv|--crash-reporter-id 238d4d83-8b5b-4545-8c62-9914465be0f0|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
pythonvs932:30410667
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
pynewext54:30695312
azure-dev_surveyone:30548225
vsccc:30803844
3biah626:30602489
89544117:30613380
showlangstatbar:30737416
vsctsb:30748421
03d35959:30757346
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
gsofa:30804715
pythonnosmt12:30797651
pythonidxpt:30805730
pythonnoceb:30805159
e537b577:30795824
dsvsc013:30795093
dsvsc014:30804076

```

</details>

<!-- generated by issue reporter -->