sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [Tabs] Scrollable Tabs render an absolute-positioned div that blocks pointer events
Labels: component: tabs,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://mui.com/material-ui/react-tabs/#scrollable-tabs

Steps:
1. Use the <Tabs /> Component with the variant "scrollable".
2. The first child inside the div with the class "MuiTabs-root" will be the following div:

```html
<div class="MuiTabs-scrollableX MuiTabs-hideScrollbar" style="width: 99px; height: 99px; position: absolute; top: -9999px; overflow: scroll;"></div>
```


### Current behavior 😯

The above mentioned div gets rendered.

### Expected behavior 🤔

If this div is rendered by mistake, it should not be rendered.
If this div has a purpose to be rendered, it should be considered to have pointer-events: none.

### Context 🔦

When rendering multiple Tabs on the same page, if the page height get bigger than 9999px, the div:
```html
<div class="MuiTabs-scrollableX MuiTabs-hideScrollbar" style="width: 99px; height: 99px; position: absolute; top: -9999px; overflow: scroll;"></div>
```
rendered by the Tab on the bottom of the page starts to block pointer events for element on the top of the page.

In the following screenshot, the div from the card on the bottom of the page affects the card on the top of the page:
<img width="1512" alt="image" src="https://user-images.githubusercontent.com/59069354/233724806-9ad835cb-7c9c-4313-8ab6-b98ad2d51f6b.png">


### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>

Browser used:
  Chrome

System:
    OS: Linux 5.15 Debian GNU/Linux 10 (buster) 10 (buster)
  Binaries:
    Node: 16.13.2 - /usr/local/bin/node
    Yarn: 1.22.15 - /usr/local/bin/yarn
    npm: 8.1.2 - /usr/local/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    @emotion/react: ^11.10.5 => 11.10.5
    @emotion/styled: ^11.10.5 => 11.10.5
    @mui/base:  5.0.0-alpha.126
    @mui/core-downloads-tracker:  5.12.1
    @mui/material: ^5.11.1 => 5.12.1
    @mui/private-theming:  5.12.0
    @mui/styled-engine:  5.12.0
    @mui/system:  5.12.1
    @mui/types:  7.2.4
    @mui/utils:  5.12.0
    @types/react: 18.0.26 => 18.0.26
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 4.9.4 => 4.9.4
Repository: flutter
Issue: ☂️  Rework `Slider` & `RangeSlider` widgets
Labels: framework,f: material design,P2,team-design,triaged-design

## ☂️  Umbrella of Slider and RangeSlider issues

Rework the `Slider` & `RangeSlider` widgets to address most if not all issues listed below.  

------------------------------

## `Slider`

### Callback issues
- [x] https://github.com/flutter/flutter/issues/128433
- [x] https://github.com/flutter/flutter/issues/123315
- [ ] https://github.com/flutter/flutter/issues/120596
- [ ] https://github.com/flutter/flutter/issues/112290
- [ ] https://github.com/flutter/flutter/issues/74312
- [x] https://github.com/flutter/flutter/issues/66341
- [ ] https://github.com/flutter/flutter/issues/63293

### Value indicator
- [x] https://github.com/flutter/flutter/issues/123313
- [ ] https://github.com/flutter/flutter/issues/122793
- [x] https://github.com/flutter/flutter/issues/113538
- [ ] https://github.com/flutter/flutter/issues/73787
- [ ] https://github.com/flutter/flutter/issues/39510

### Thumb
- [ ] https://github.com/flutter/flutter/issues/113781
- [x] https://github.com/flutter/flutter/issues/62567

### Performance 
- [ ] https://github.com/flutter/flutter/issues/98770
- [ ] https://github.com/flutter/flutter/issues/51715

### Slider error issues
- [ ] https://github.com/flutter/flutter/issues/97292

### New feature  and Proposals
- [ ] https://github.com/flutter/flutter/issues/63330
- [ ] https://github.com/flutter/flutter/issues/62214
- [ ] https://github.com/flutter/flutter/issues/34704
- [x] https://github.com/flutter/flutter/issues/32768

### Accessibility 
- [ ] https://github.com/flutter/flutter/issues/114225

### Documentation
- [ ] https://github.com/flutter/flutter/issues/74098

### Tests
- [x] https://github.com/flutter/flutter/issues/34251

## `RangeSlider`

### Value indicator 
- [ ]  https://github.com/flutter/flutter/issues/76466

### New features  and Proposals
- [ ] https://github.com/flutter/flutter/issues/62486
- [ ] https://github.com/flutter/flutter/issues/53958
- [ ] https://github.com/flutter/flutter/issues/33795
- [ ] https://github.com/flutter/flutter/issues/126746

### Functionality 
- [ ] https://github.com/flutter/flutter/issues/51620
- [x] https://github.com/flutter/flutter/issues/126648


### Accessibility 
- [ ] https://github.com/flutter/flutter/issues/32229



## Slider Updates Project
https://github.com/orgs/flutter/projects/44/views/2
Repository: storybook
Issue: [Bug]: Story docs block does not recover from errors thrown in React
Labels: bug,help wanted,addon: docs,sev:S3

If you add a `throw new Error('bla')` to a component rendered in a docs block, it will error but once you fix the issue, it won't recover:


https://user-images.githubusercontent.com/1671563/233017345-63c314cb-f951-49a6-8990-95bc3286f794.mov

_Originally posted by @yannbf in https://github.com/storybookjs/storybook/issues/21440#issuecomment-1514347004_
Repository: vscode
Issue: Quick pick label tooltips
Labels: bug,quick-pick

<!-- ⚠️⚠️ 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.77.3
- OS Version: Ubuntu 18.04

Steps to Reproduce:

1. Open the command palette
2. Find an entry that is longer than the width of the quick pick
3. Discover that there is no way to see the full text of the entry

Tooltips for quick pick descriptions were added in response to https://github.com/microsoft/vscode/issues/101874. However, it was pointed out in https://github.com/microsoft/vscode/issues/101874#issuecomment-655369751 that a solution is needed for the labels as well (as only labels are used in the command palette), but that comment appears to have been disregarded in the resolution to that issue.
Repository: godot
Issue: Particle3D scale does not work in billboard mode.
Labels: discussion,topic:rendering,usability,topic:3d,topic:particles

### Godot version

Godot_v4.1-dev1

### System information

Ubuntu 22.04, RTX3060ti

### Issue description

Particle3D scale does not work in billboard mode.

### Steps to reproduce

Add 3D particles, enable billboard particle.

### Minimal reproduction project

[Particles test.zip](https://github.com/godotengine/godot/files/11299596/Particles.test.zip)
Repository: pytorch
Issue: Deformable Convolution export to onnx
Labels: module: onnx,triaged

### Deformable Convs in onnx export

Dear Torch Team,

Is there a possibilty that the torch.onnx.export() function gets updated so that it support the deformable convolution layer that is now supported in the latest opset (version 19) of ONNX.
I believe that adding support for deformable convolutions in torch.onnx.export() would greatly enhance the functionality and versatility of the export possibilities.

Nick
Repository: godot
Issue: Error message from AnimationTree with root bone
Labels: bug,needs testing,topic:animation

### Godot version

4.0.2

### System information

Windows 11

### Issue description

I'm randomly getting error messages, usually when saving the project but also at other times, that say the following:

`Found invalid node path 'Armature/Skeleton3D:mixamorig10_Root' on node 'PlayerTest/Player/AnimationTree'`

The node has the bone listed above as its root_motion_track. The AnimationTree is working fine, including root motion.

The message seems to come from the function `SceneTreeDock::_update_node_path`. It looks like it's trying to treat a bone path as a node?


### Steps to reproduce

Create scene with Skeleton3D, AnimationPlayer and AnimationTree.
Set the AnimationTree's player to the AnimationPlayer.
Create a bone in the skeleton and set it as the AnimationTree root_motion_track.

The message usually seems to happen when saving files in the editor.


### Minimal reproduction project

N/A
Repository: next.js
Issue: Special characters in CWD cause 404s for both dev and build/start
Labels: Upstream,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: #41~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Mar 31 16:00:14 UTC 2
    Binaries:
      Node: 19.7.0
      npm: 9.5.0
      Yarn: N/A
      pnpm: 8.3.1
    Relevant packages:
      next: 13.3.1-canary.19
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Operating System (Windows, MacOS, Linux)

### Link to the code that reproduces this issue

https://github.com/emivespa/next.js-48699-repro
### To Reproduce

```bash
mkdir percent%sign
cd percent%sign

npx create-next-app@latest --example reproduction-template reproduction-app
cd reproduction-app

npm i next@canary
npm run dev # And go to localhost:3000
npm run build && npm run start # Same bug.
```

### Describe the Bug

When the Next server runs from a CWD path with special characters, everything but '/' 404s.

There are no warnings when running in an "unsafe" CWD.

### Expected Behavior

I expected the app to work normally, but maybe a warning would suffice.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

next dev, next start
Repository: stable-diffusion-webui
Issue: [Bug]: txt2img not generating - stuck at 0%
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?

When attempting to generate a txt2img prompt, the progress bar never appears - it simply turns gray after displaying "waiting" for a brief moment. The "Interrupt" and "Pause" keys are also unresponsive.

If it doesn't do that, it displays "In queue..." endlessly

### Steps to reproduce the problem

Launch the webui-user.bat with the parameters provided


### What should have happened?

Images should have been generated

### Commit where the problem happens

latest

### What platforms do you use to access the UI ?

Windows

### What browsers do you use to access the UI ?

Mozilla Firefox

### Command Line Arguments

```Shell
--skip-torch-cuda-test --precision full --no-half
```


### List of extensions

No

### Console logs

```Shell
venv "H:\ai\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)]
Commit hash: 22bcc7be428c94e9408f589966c2040187245d81
Installing requirements for Web UI
Launching Web UI with arguments: --skip-torch-cuda-test --precision full --no-half
Warning: caught exception 'Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from http://www.nvidia.com/Download/index.aspx', memory monitor disabled
No module 'xformers'. Proceeding without it.
Loading weights [fe4efff1e1] from H:\ai\stable-diffusion-webui\models\Stable-diffusion\sd-v1-4.ckpt
Creating model from config: H:\ai\stable-diffusion-webui\configs\v1-inference.yaml
LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.
Applying cross attention optimization (InvokeAI).
Textual inversion embeddings loaded(0):
Model loaded in 182.2s (load weights from disk: 175.6s, create model: 3.6s, apply weights to model: 2.8s, load textual inversion embeddings: 0.1s).
Running on local URL:  http://127.0.0.1:7860

To create a public link, set `share=True` in `launch()`.
Startup time: 226.4s (import torch: 17.0s, import gradio: 6.9s, import ldm: 2.3s, other imports: 11.3s, setup codeformer: 0.3s, load scripts: 3.2s, load SD checkpoint: 182.5s, create ui: 2.3s, gradio launch: 0.4s).
```


### Additional information

The H:\ directory that the repository is located on is an external drive.

AMDx64
Repository: next.js
Issue: Next AppDir Dynamic Routes prerenders depending on order of code
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: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.14.0
      npm: 9.3.1
      Yarn: 1.22.19
      pnpm: 7.27.0
    Relevant packages:
      next: 13.3.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

https://github.com/khuezy/next-route

### To Reproduce

# Reproduction

1. `npm install`
2. `npm run build`
3. Note that the build fails

See file: `app/(group)/api/hello/route.tsx`
```typescript
// Since this is before accessing the Request object,
// Next will try to prerender this...
await someAsyncFunc();

// But I expect this GET to be dynamically rendered
// since I'm using the Request object.
// If I  move this block above the await above, it works.
const { searchParams } = new URL(req.url);
const title = searchParams?.get("title") || "";
```

4. Move the `await someAsyncFunc();` line below the searchParams like:

```typescript
// Since the reference to the Request object is first,
// Next build does not prerender this route
const { searchParams } = new URL(req.url);
const title = searchParams?.get("title") || "";

// build doesn't error b/c this is a dynamic route, as expected
await someAsyncFunc();
```

5. `npm run build`
6. Note the build is succesful b/c it treats /api/hello as dynamic


### Describe the Bug

According to the app dir [Docs](https://beta.nextjs.org/docs/routing/route-handlers):

```
Route handlers are evaluated dynamically when:

Using the Request object with the GET method.
```

But if you have code in your `GET` handler before using the Request object, `next build` will try to preprocess the handler.

### Expected Behavior

Next build should treat the `GET` handler as dynamic if it uses the Request object.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: go
Issue: crypto/tls: centralize alert sending
Labels: NeedsInvestigation

Currently we send TLS alerts all over the place, decoupling the process for other error handling, this results in inconsistencies about when and where we send alerts that can be quite confusing (including sometimes just not sending expected alerts at all).

Ideally we should centralize alert transmission in one (or two) places: Conn.Read and Conn.Write. Alerts can then be derived from errors (or a field we set on the connection?) allowing us to consistently handle them.

cc @FiloSottile
Repository: opencv
Issue: Photo linearResponse does not support images with channels != 3
Labels: bug,feature,category: photo

### System Information

OpenCV version: 4.6.0
file: modules/photo/src/hdr_common.cpp

![图片](https://user-images.githubusercontent.com/49955157/233753479-23eca2a6-17a0-4e3d-8504-102edbdd0e5a.png)

The function can not work if  channels is not 3

### Detailed description

OpenCV version: 4.6.0
file: modules/photo/src/hdr_common.cpp

![图片](https://user-images.githubusercontent.com/49955157/233753479-23eca2a6-17a0-4e3d-8504-102edbdd0e5a.png)

The function can not work if  channels is not 3

### Steps to reproduce

bug at file: modules/photo/src/hdr_common.cpp
![图片](https://user-images.githubusercontent.com/49955157/233753479-23eca2a6-17a0-4e3d-8504-102edbdd0e5a.png)

if i call linearResponse(4)  or linearResponse(1)

![图片](https://user-images.githubusercontent.com/49955157/233753695-8d5a97d5-96da-49d9-b335-cb96f6d5e986.png)


### 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
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: next.js
Issue: Next's `fetch` wrapper adds unexpected headers (specifically, `accept-language`)
Labels: bug,Pages Router

### 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.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 20.0.0
      npm: 9.6.4
      Yarn: N/A
      pnpm: 8.3.1
    Relevant packages:
      next: 13.3.1-canary.19
      eslint-config-next: 13.3.1
      react: 18.2.0
      react-dom: 18.2.0
```


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

Data fetching (gS(S)P, getInitialProps)

### Link to the code that reproduces this issue

see below

### To Reproduce

Make a `PROPFIND` request to Apple's iCal endpoint, like so:

```ts
const result = await fetch("https://caldav.icloud.com/.well-known/caldav", {
    method: "PROPFIND",
    headers: {
      Authorization: "Basic xxxyyyzzz=", // iCloud user:pass
    },
  })
```

### Describe the Bug

It looks like the `fetch` provided by Next adds some headers by default, specifically:
* `accept-language: *`
* `sec-fetch-mode: cors`

In particular, the presence of `accept-language` causes the CalDAV server to 500 on me. 

Until I intercepted network traffic to examine the contents of the `fetch` request, I wasn't aware that these extra headers were being added:

![image](https://user-images.githubusercontent.com/3246342/233754132-44cba268-8bd7-4f3a-8477-22b9c566e440.png)


When I manually forced it to use `node-fetch`, I observed the headers in question weren't added:

![image](https://user-images.githubusercontent.com/3246342/233754146-a1194211-b8f7-4d08-b882-632604843ccd.png)

I'm not sure if this is an upstream issue, but it threw me for a loop :) 

I can workaround it using the provided version of `fetch` if I add `"accept-language": undefined` to the `headers` object (despite TS griping that `undefined` isn't an acceptable param; it works fine!)

### Expected Behavior

No new headers are added to `fetch` requests.

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

n/a

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

next dev
Repository: TypeScript
Issue: "Overriding" JSDoc at re-exports mostly only results in propagation of added "@deprecated" JSDoc tag
Labels: Needs More Info

# Bug Report

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

JSDoc, \@deprecated, override, re-export.

Related on Stack Overflow: [How can I make VS Code recognize an overridden JSDoc for a re-export?](https://stackoverflow.com/a/75999518/11107541).

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->

I tried this with TypeScript 5.0.4 and 4.6.4. I tried 4.6.4 because I noticed that https://github.com/microsoft/TypeScript/pull/47293 happened just a bit before the release of 4.6. I witnessed the same behaviour for both versions I tried. I have described that behaviour below.

### 💻 Code

<!-- Please post the relevant code sample here as well-->

exporter.js:

```js
/**
 * JSDoc from original export.
 * A thing that is definitely not deprecated.
 */
export const thing = 123;
```

reexporter.js:

```js
export {
   /**
    * JSDoc from re-export.
    * A thing that is deprecated.
    * @deprecated reasons.
    */
   thing
} from "./exporter";
```

importer.js:

```js
// ✅ means   expected behaviour
// ❌ means unexpected behaviour

import {
   thing            // ✅ not crossed out.  ✅ hover info: "JSDoc from original export. A thing that is definitely not deprecated."
   as originalThing // ✅ not crossed out.  ✅ hover info: "JSDoc from original export. A thing that is definitely not deprecated."
} from "./exporter"

import {
   thing              // ✅ crossed out.  ✅ hover info: "JSDoc from re-export. A thing that is deprecated. @deprecated — reasons." off. even this comment is crossed out.
   as reexportedThing // ✅ crossed out.  ❌ hover info: "JSDoc from original export. A thing that is definitely not deprecated."
} from "./reexporter";
reexportedThing();    // ✅ crossed out.  ❌ hover info: "JSDoc from original export. A thing that is definitely not deprecated."

import {
   thing // ✅ crossed out.  ❌ hover info: "JSDoc from original export. A thing that is definitely not deprecated."
} from "./reexporter"
thing(); // ✅ crossed out.  ❌ hover info: "JSDoc from original export. A thing that is definitely not deprecated."
```

### 🙁 Actual behavior

see the above code.

### 🙂 Expected behavior

see the above code. Everywhere with a "❌", I expected to see the overridden JSDoc in the VS Code hover info backed by tsserver.