sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Code bug in call_prepare_scriptable_func_impl function.
Labels: oncall: jit

### 🐛 Describe the bug

I'm not sure if this is a BUG or not, but I read the source code and it seems that this function adds an unnecessary loop. `torch/jit/_script.py` has a function called `call_prepare_scriptable_func_impl`. There's a piece of code that looks like this:
```python
    new_obj_dict = {}

    for name, sub_module in obj.__dict__.items():
        if name == "_modules":
            for k, v in sub_module.items():
                sub_module[k] = call_prepare_scriptable_func_impl(v, memo)
            new_obj_dict[name] = sub_module
        elif isinstance(sub_module, torch.nn.Module) and not isinstance(
            sub_module, ScriptModule
        ):
            new_obj_dict[name] = call_prepare_scriptable_func_impl(sub_module, memo)
        else:
            new_obj_dict[name] = sub_module

    for k, v in new_obj_dict.items():
        obj.__dict__[name] = v
```

The first loop I can understand is to use recursion to facilitate all member variables of the class to be converted to script and member variables of subclasses. Where `name` is a variable in the first loop. But in the second loop, it keeps assigning a different `v` to `obj.__dict__[name]`. `obj` doesn't change at the end of the loop, because `name` is a variable from the first loop. It seems that this code just takes the value loop of `obj.__dict__[name]` and assigns it to some strange variables and then reassigns the original value, so obj doesn't change anything.


### Versions

2.3.1 and github main codebase also.

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel
Repository: vscode
Issue: Menus disappear when Android Chrome virtual keyboard present
Labels: bug,web,android

<!-- ⚠️⚠️ 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.91.1
- OS Version: Android version 14
- Chrome Version: 126.0.6478.186

Steps to Reproduce:

1. Open any web version of VS Code ([vscode.dev](https://vscode.dev/) or [codespaces](https://github.com/codespaces)) in an Android Chrome web browser. (I can also reproduce it in Firefox!)
2. Trigger the virtual keyboard to appear. Opening a text file would do it. Focusing the search input field does it too.
3. Try to open a menu via the hamburger button on the top left or the ellipsis button on the top right. The menu will briefly appear and the keyboard will lower, then immediately the menu will disappear again and the keyboard will raise again.

https://github.com/user-attachments/assets/e53a2d7c-5864-4c12-be35-c8f14e10f697
Repository: material-ui
Issue: [material-ui][Autocomplete] Make multiple selected values available to FormData
Labels: new feature,waiting for 👍,package: material-ui,component: autocomplete

### Summary

When using `<Autocomplete>` for multiple values, the selected options should be made available like a native `<select>` through [FormData](https://developer.mozilla.org/en-US/docs/Web/API/FormData). At the moment the input element passed to `renderInput` contains an empty string, when accessed through FormData (if you use a `TextField`), since it acts more as a visual and not a semantic container.

Side note: in the single value select case this works already through the `TextField`, which then contains the selected value.

### Examples

We built a quick example of what we would like:
```typescript
import { Autocomplete, Button, TextField } from '@mui/material'
import * as React from 'react'
import { Form, type ActionFunctionArgs } from 'react-router-dom'

const someOptions = [
  { label: 'Option1' },
  { label: 'Option2' },
  { label: 'Option3' },
]

export function AutoCompleteDemo() {
  return (
    <Form method="POST" action="/example">
      <Autocomplete
        options={someOptions}
        getOptionLabel={(option) => option.label}
        multiple
        renderInput={(params) => (
          <TextField
            {...params}
            required
            name="example"
            variant="outlined"
            label="Example"
          />
        )}
      />
      <Button type="submit">Submit</Button>
    </Form>
  )
}

export async function AutoCompleDemoAction(args: ActionFunctionArgs) {
  const formdata = await args.request.formData()
  // formdata.example should contain all selected values as a list
  console.log(formdata)
  return true
}
```

![image](https://github.com/user-attachments/assets/158ee08f-2934-4501-be89-3e1d0b030d58)

But as you can see, we get an empty string:

![image](https://github.com/user-attachments/assets/d17b334b-060e-4fe1-970b-5d87544d6332)

(And we were so far unable to fit a `<Select>` into the `renderInput` position, see also the Motivation segment.

### Motivation

Using `<Autocomplete>` with [`<Form>` from React Router](https://reactrouter.com/en/main/components/form) requires additional code/custom components to make the selected option(s) available during form submission. It would be more elegant and semantically correct if you could just access the selected values through FormData – just like you already can with an `<Autocomplete>` for a single value.

And it doesn't seem to be really possible to feed a `<Select>` to `<Autocomplete>` (through `renderOption` for the `<MenuItem>`s and `renderInput` for the `<Select>`).

If it helps with the priority: we are a paying customer with the order ID 84512.

**Search keywords**: material ui, MUI, Autocomplete, FormData
Repository: storybook
Issue: [Bug]: Docs page renders the Toast multiple times
Labels: bug,needs triage

### Describe the bug

Docs page is rendering the component ToastContainer **multiple times**. More exactly there will be one for each story section that appears in the docs page. 

![image](https://github.com/user-attachments/assets/6c8b2c42-4eb1-4bfc-8646-77cd5dab75f0)



### Reproduction link

https://osstotalsoft.github.io/rocket-ui-ts/?path=/docs/components-feedback-toast--docs

### Reproduction steps

**1.** Go to the docs page of our Toast component: https://osstotalsoft.github.io/rocket-ui-ts/?path=/docs/components-feedback-toast--docs 
**2.** Click the button Info Toast, or any other type of toasts.
**3.** Close the toast that appeared on the screen.
**4.** Realize that under the first toast will be another one and another one and so on. More exactly there will be one for each story section that appears in the docs page.
**5.** Alternatively, inspect the Document and get the number of toasts `document.getElementsByClassName('Toastify').length`
**6.** Our components solution is open source and the code can be found at: https://github.com/osstotalsoft/rocket-ui-ts

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22631
    CPU: (20) x64 Intel(R) Core(TM) i9-10900 CPU @ 2.80GHz
  Binaries:
    Node: 20.15.1 
    Yarn: 4.3.1 
    npm: 9.5.1 
  Browsers:
    Edge: Chromium (126.0.2592.102)
```


### Additional context

Storybook configuration:
:pencil: main.js:                https://github.com/osstotalsoft/rocket-ui-ts/blob/master/.storybook/main.ts
:pencil: preview.tsx          https://github.com/osstotalsoft/rocket-ui-ts/blob/master/.storybook/preview.tsx
:pencil: Toast.stories.tsx   https://github.com/osstotalsoft/rocket-ui-ts/blob/master/src/stories/feedback/Toast/Toast.stories.tsx

:disappointed: **What's happening**: In my Toast.stories.tsx file, I am exporting 3 stories, which will appear in the docs page plus the presenting section which is by default the first story. So, in this case, 4 _ToastContainers_ are rendered.

:smiley: **Expected behavior**: When I open a Toast, only one _ToastContainer_ should be rendered.

PS: We use the toast from **'react-tostify'**

Thank you for your help! :tulip:
Repository: puppeteer
Issue: [Bug]: Embedded video thumbnails not appearing in full page screenshots
Labels: bug,upstream,confirmed,P3

### Minimal, reproducible example

```TypeScript
import puppeteer from 'puppeteer';

const browser = await puppeteer.launch({ 
    executablePath: '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome',
    headless: true, // Run in headful mode
    args: ['--disable-features=site-per-process'],
  });

  //Go to any webpage with a video at the bottom/not at the top
  await page.goto('https://jobbuddytech.com', { waitUntil: 'networkidle0' });
  const screenshotBuffer = await page.screenshot({ fullPage: true });

  //Embedded thumbnail video not appearing
```


### Background

I'm trying to take full page screenshots of websites. I want the screenshot to be as visually similar to what a user would see as possible. I am having trouble getting embedded video thumbnails to appear in the screenshot as they appear to the user. Usually it's just a blank box when using the fullPage: true option for the screenshot method (as above).

I've tried all kinds of awaits, but they don't make a difference. The only things I found to work were to programatically scroll, take screenshots, and stitch them back together. This results in some problems where sticky elements exist. And I've tried setting the viewport to the document.body.scrollHeight and doing a full page screenshot. This creates some strange looking screenshots in some of my examples (too long, repeated elements etc)

Please advise if there's a solution to this.

### Expectation

 I would expect the embedded video thumbnail to appear in screenshots as it does it a user viewing with a browser.

### Reality

Where the embedded video thumbnail should be, is just blank

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22.13.1

### Node version

20

### Package manager

npm

### Package manager version

10.2.4

### Operating system

macOS
Repository: godot
Issue: Incorrect shading on normal mapped models with skeleton when using compatibility renderer
Labels: bug,topic:rendering,regression,topic:3d

### Tested versions

-Reproducible in 4.2.2, 4.3beta3. -Not reproducible in 4.1.1, 4.1.3

### System information

Godot v4.2.2.stable - Windows 10.0.26100 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 Ti (NVIDIA; 32.0.15.6070) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)

### Issue description

When viewing a normal mapped model using the compatibility renderer, shading appears inverted in places.
Issue is apparent both on windows and when exported for android.
Issue does not occur when using Mobile or Forward+ renderer (nor in gles2 or gles3 for Godot 3).
Issue does not occur in 4.1.3, 4.1.1, or 3.5.3.

My uneducated guess is that there's a missing or superfluous negative in the normal map code.

Miscelaneous information;
Model is ~6k polys, rigged and animated .glb. Only has diffuse and normal map. Textures tested at various resolutions.
Created in blender.

This is my first post, please let me know if the formatting or information is wrong.

![whyiscompatibilitylikethis2a](https://github.com/user-attachments/assets/50e94a5f-f4b2-450b-ab5d-48365868a6e6)


### Steps to reproduce

open a normal mapped model with skeleton while using the compatibility renderer in Godot 4.2.2 / 4.3beta3

### Minimal reproduction project (MRP)

[test-normalbug.zip](https://github.com/user-attachments/files/16282972/test-normalbug.zip)
Repository: deno
Issue: deno publish failed with error: error[excluded-module] when export casing differs from file casing
Labels: bug,publish

Version: Deno 1.45.2

I have 37 generated project to publish, so they have all the same shape.

some of them failed with error :
```bash
Checking for slow types in the public API...
error[excluded-module]: module in package's module graph was excluded from publishing
 --> /dev/react-icons-gi/ico/Gi3dGlasses.ts
  = hint: remove the module from 'exclude' and/or 'publish.exclude' in the config file or use 'publish.exclude' with a negative glob to unexclude from gitignore

  info: excluded modules referenced via a package export will error at runtime due to not existing in the package
  docs: https://jsr.io/go/excluded-module

error[excluded-module]: module in package's module graph was excluded from publishing
 --> /dev/react-icons-gi/ico/Gi3dHammer.ts
  = hint: remove the module from 'exclude' and/or 'publish.exclude' in the config file or use 'publish.exclude' with a negative glob to unexclude from gitignore

  info: excluded modules referenced via a package export will error at runtime due to not existing in the package
  docs: https://jsr.io/go/excluded-module
```

The error message is not relevant, I had only exclude my .github folder, and the error is the same without any exclude.

error sample:
https://github.com/UrielCh/react-icons-gi/actions/runs/9988509932/job/27605141756

similar project without the error:
https://github.com/UrielCh/react-icons-ai/actions/runs/9988506667/job/27605128093


all those project will be published [here](https://jsr.io/@preact-icons)
Repository: next.js
Issue: Global error not working if triggered in sub-path in version 13.5.5
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://github.com/TitusEfferian/next-13-3-5-error-repro/blob/main/src/app/TestLayoutChild.tsx

### To Reproduce

1. Clone the repository: https://github.com/TitusEfferian/next-13-3-5-error-repro
2. Run `npm install`
3. Run `npm run build`
4. Run `npm run start`
5. Go to `http://localhost:3000/another_path`
6. Click the trigger error button

### Current vs. Expected behavior

**Current Behavior**

It's not handled by the global error; instead, it is rendered by the default error UI from Next.js.

**Expected Behavior**

Handled by the global error if the error comes from a sub-path.

Actually, if the error is triggered on the root page, it works as expected, but if it's triggered by another path, it's not working.

I also checked with the later version `14.2.5`, and it works in that version.


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:14:38 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 18.19.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.2.5 // Latest available version is detected (14.2.5).
  eslint-config-next: 13.5.5
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure, create-next-app

### Which stage(s) are affected? (Select all that apply)

next build (local), next start (local)

### Additional context

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Update gradio
Labels: enhancement

### Is there an existing issue for this?

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

### What would your feature do ?

not limit version of gradio

### Proposed workflow

1. requirements.txt gradio
2. any other limit version of pip libs


### Additional information

_No response_
Repository: material-ui
Issue: [material-ui][Dialog] Keyboard scrolling doesn't work in fullscreen mode
Labels: bug 🐛,component: dialog,package: material-ui

### Steps to reproduce

Link to live example: https://stackblitz.com/edit/react-mn6y3k-zhswqk?file=Demo.tsx

This applies to Dialog components with scroll='body'

Steps:
1. Open the dialog with `fullScreen=true`
2. Try to scroll using the keyboard. 


### Current behavior

You cannot scroll using the keyboard until you manually focus on the Dialog contents using a click or a tab.

### Expected behavior

I would expect to be able to scroll using the keyboard straight away, as it is when `fullScreen=false`

### Context

Trying to create an accessible full screen Dialog component

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 14.1
  Binaries:
    Node: 22.4.1 - /opt/homebrew/bin/node
    npm: 10.8.1 - /opt/homebrew/bin/npm
    pnpm: Not Found
  Browsers:
    Chrome: 126.0.6478.182
    Edge: Not Found
    Safari: 17.1
  npmPackages:
    @emotion/react: ^11.11.0 => 11.11.1
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.28
    @mui/core-downloads-tracker:  5.15.1
    @mui/icons-material: ^5.14.20 => 5.15.1
    @mui/material: ^5.14.20 => 5.15.1
    @mui/private-theming:  5.15.1
    @mui/styled-engine:  5.15.1
    @mui/system:  5.15.1
    @mui/types:  7.2.11
    @mui/utils:  5.15.1
    @mui/x-date-pickers: ^5.0.20 => 5.0.20
    @types/react: ^18.2.75 => 18.2.75
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^5.4.5 => 5.4.5
```
</details>


**Search keywords**: fullscreen dialog keyboard scroll
Repository: vscode
Issue: In code-server, disconnected processes eventually block forever on stdout/stderr PTY buffer
Labels: bug,linux,terminal-process

<!-- ⚠️⚠️ 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.91.1
- OS Version: Ubuntu 22.04

Steps to Reproduce:

1. Run code-server with default flags and default configuration.
2. In an Integrated Terminal window, run `while true; do date; done`, and close the browser window, keeping the command still running.
3. After about 30 seconds, without reopening the browser window, notice that the `date` process is hung. You can verify it by checking its PID (e.g. through ps) and confirm that the process is not exiting instantaneously. You can also check that something like `echo "Hello" >/proc/$pid/fd/1` will block.

More context:

I am filing this as a bug because this is surprising behavior, but one can also argue for this to be a feature request. In code-server mode, it can be common to launch a long-running job in the terminal and then close the browser window, expecting the user to return to the session later. This works in most cases and users are able to find their long-running jobs have been running upon reconnecting to the session. However, when jobs send a lot of data to stdout/stderr, they are blocked on IO to the PTY, and it becomes unclear why the job is not making progress ([example](https://github.com/nextflow-io/nextflow/discussions/5144#discussioncomment-10082244)). The expected behavior would be that any data sent to stdout/stderr will be processed as in a scrollback buffer, but it looks like this is not the case.
Repository: PowerToys
Issue: Double-click in blank area of the file explorer to go to upper folder (parent directory)
Labels: Needs-Triage

### Description of the new feature / enhancement

To click on a blank space of the file explorer to jump into the parent directory (upper folder level)

### Scenario when this would be used?

Every single time we navigate through the files with the mouse, we don't need to take our hand off the mouse to go to the keyboard to press the alt + arrow up or bother ourselves looking at the tab to click on the previous directory, or move the mouse to the icon for going one level up.

It is handy when we can double-click in our current mouse position or just with a little move go to a blank space, and that's it: no thinking is required or extra effort.

### Supporting information

_No response_
Repository: node
Issue: Start adding .asc signature files for tar files to validate signature
Labels: feature request

### What is the problem this feature will solve?

Right now, node uses SHA256 checksums to verify published artifacts like tars. Signatures offer stronger security. Some packages already do this like Yarn: https://github.com/yarnpkg/yarn/releases/tag/v1.22.17

### What is the feature you are proposing to solve the problem?

Start adding .asc signature files in index (e.g. https://nodejs.org/download/release/v16.20.2/) 



### What alternatives have you considered?

_No response_
Repository: vscode
Issue: editorIndentGuide.activeBackground is being cut by preprocessor directives
Labels: bug,editor-indent-guides

Line coloring enabled by `editorIndentGuide.activeBackground` loses its continuity when there are preprocessor directives along the way. In C/C++ codebases where preprocessor flags are used often, this feature loses its usability.

Yes, it's possible that preprocessor directive might be expanded into something that really breaks the current scope and defines a newer, but I think this happens less often enough to assume by default it's not the case.  


<!-- ⚠️⚠️ 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: Version: 1.91.1 Commit: f1e16e1e6214d7c44d078b1f0607b2388f
- OS Version: Darwin arm64

Steps to Reproduce:

![image](https://github.com/user-attachments/assets/e9050521-48b6-4da4-a5bf-d6735899012f)

Expected behavior:
Red line should have continued between and after the `#ifdef` scope.