sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: JIT will affect the gradient computation of forward mode
Labels: oncall: jit

### 🐛 Describe the bug

JIT will affect the gradient computation of forward mode for some API

For example, if we directly call `jit_fn` with forward mode, it will output the correct gradient:

```py
import torch

def fn(input, target):
    weight = None
    reduction = "mean"
    return torch.nn.functional.multilabel_soft_margin_loss(input, target, weight=weight, reduction=reduction, )

input = torch.tensor([[1., 1.]], dtype=torch.float32)
target = torch.tensor([[2., 2.]], dtype=torch.float32)

inputs1 = (input.clone().requires_grad_(), target.clone().requires_grad_())
inputs2 = (input.clone().requires_grad_(), target.clone().requires_grad_())

jit_fn = torch.jit.trace(fn, (input, target))
print(torch.autograd.functional.jacobian(jit_fn, inputs2, vectorize=True, strategy='forward-mode'))
# [tensor([[-0.6345, -0.6345]], grad_fn=<ReshapeAliasBackward0>), tensor([[-0.5000, -0.5000]], grad_fn=<ReshapeAliasBackward0>)
```

However, if we call `jit_fn(*inputs1)` before the gradient computation in forward mode with `inputs2`, the gradient will be all 0, which is wrong

```py
import torch

def fn(input, target):
    weight = None
    reduction = "mean"
    return torch.nn.functional.multilabel_soft_margin_loss(input, target, weight=weight, reduction=reduction, )

input = torch.tensor([[1., 1.]], dtype=torch.float32)
target = torch.tensor([[2., 2.]], dtype=torch.float32)

inputs1 = (input.clone().requires_grad_(), target.clone().requires_grad_())
inputs2 = (input.clone().requires_grad_(), target.clone().requires_grad_())


jit_fn = torch.jit.trace(fn, (input, target))
jit_fn(*inputs1)
print(torch.autograd.functional.jacobian(jit_fn, inputs2, vectorize=True, strategy='forward-mode'))
# [tensor([[0., 0.]]), tensor([[0., 0.]])]
```

Interestingly, this cannot affect the gradient computation in reverse mode.

Many APIs suffer from this problem, like `lp_pool1d`


### Versions

pytorch: 1.12.1
Repository: vscode
Issue: completion on breakpoint remove all items
Labels: feature-request,debug

Type: <b>Bug</b>/<b>Feature request</b>

when create an expression for a breakpoint looks like it does not handle correctly the world split. 
I can explain it only by images, on my code If I try to complete a word it gives a lot of result:
![image](https://user-images.githubusercontent.com/22457168/189027616-c3a92ab9-3053-4a84-aaf7-a48793453f18.png)
But if the same word is after a logical operator the result are much less:
![image](https://user-images.githubusercontent.com/22457168/189027777-932cb10e-8005-4802-a595-f3f406d5355c.png)


VS Code version: Code 1.71.0 (784b0177c56c607789f9638da7b6bf3230d47a8c, 2022-09-01T07:36:10.600Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx   (8 x 1996)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|undefined|
|Memory (System)|6.90GB (0.98GB free)|
|Process Argv|--crash-reporter-id 16bc8c7e-027f-4165-8229-92f97b9f44b4|
|Screen Reader|no|
|VM|67%|
</details><details><summary>Extensions (23)</summary>

Extension|Author (truncated)|Version
---|---|---
harbour|ape|1.0.4
regexper-unofficial|ape|0.0.3
doxdocgen|csc|1.4.0
typescript-notebook|don|2.0.6
vscode-npm-script|eg2|0.3.28
better-cpp-syntax|jef|1.15.19
vscode-language-pack-it|MS-|1.71.9070919
csharp|ms-|1.25.0
python|ms-|2022.14.0
vscode-pylance|ms-|2022.9.10
jupyter|ms-|2022.8.1002431955
jupyter-keymap|ms-|1.0.0
jupyter-renderers|ms-|1.0.9
remote-containers|ms-|0.251.0
remote-ssh|ms-|0.84.0
cmake-tools|ms-|1.12.26
cpptools|ms-|1.12.4
cpptools-extension-pack|ms-|1.3.0
hexeditor|ms-|1.9.8
notepadplusplus-keybindings|ms-|1.0.7
vscode-yaml|red|1.10.1
LiveServer|rit|5.7.9
cmake|twx|0.0.17

(2 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30557514
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
pylanb8912:30545647
vsclangdc:30486549
c4g48928:30535728
hb751961:30553087
dsvsc012cf:30540253
azure-dev_surveyone:30548225
i497e931:30553904

```

</details>

<!-- generated by issue reporter -->oard because it was too large to send. Please paste.
Repository: vscode
Issue: GitHub - can't fork a fork
Labels: bug,github

- Open my codespace which is on https://github.com/mdehling/stable-diffusion
- Try to push a commit on the notebook branch (is there a command to fork manually because I didn't remember that I have to try to push to get the fork prompt to show up?)
- Get an error:
<img width="578" alt="image" src="https://user-images.githubusercontent.com/323878/189030915-a5cc419d-84c8-4549-9ce1-15309ce9b1db.png">

Because upstream was already set to the real upstream

```
$ git remote -v
origin  https://github.com/mdehling/stable-diffusion (fetch)
origin  https://github.com/mdehling/stable-diffusion (push)
upstream        https://github.com/joaomoreno/stable-diffusion.git (fetch)
upstream        https://github.com/joaomoreno/stable-diffusion.git (push)
```
Repository: flutter
Issue: iPad safari font loading issue
Labels: engine,a: fidelity,a: typography,platform-web,e: web_html,has reproducible steps,P2,found in release: 3.3,found in release: 3.4,team-web,triaged-web

## Details
1. Please open following url in desktop chrome browser and iPad safari browser:
https://sta-portal.gymismo.com/#/
2. I have observed that font is not loading in iPad. I have tested in physical device with master channel.

Target Platform: Web
Target OS version/browser: Safari
Devices: iPad 8th Generation

Desktop Screenshot:
<img width="1792" alt="Desktop" src="https://user-images.githubusercontent.com/77234816/189057484-e089fd7a-2fa5-477a-99e9-c84e66126234.png">


iPad Screenshot:
![iPad](https://user-images.githubusercontent.com/77234816/189057504-a3c22b59-d19a-4ddc-b044-68438138c075.PNG)
Repository: stable-diffusion-webui
Issue: [Feature Request] Ability to see completed images before batch is fully finished running (reload button)
Labels: enhancement

The one thing I miss about the "other" webui is the Reload button on the txt2img and img2img screens. Clicking Reload while a batch is running loads any already completed images into the interface so you can browse them while the rest of the batch completes.

Please consider implementing a Reload button. Thanks!
Repository: ant-design
Issue: autocomplete set InputNumber children,it will be error when I input anything
Labels: 🐛 Bug,help wanted,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/bu-qu-fen-da-xiao-xie-antd-4-23-0-forked-nv86yp?file=/demo.js)

### Steps to reproduce

1. open https://codesandbox.io/s/bu-qu-fen-da-xiao-xie-antd-4-23-0-forked-nv86yp?file=/demo.js
2. input anything in InputNumber
3. error 🥵

### What is expected?

I want to input something and select options

### What is actually happening?

if I input , having error in console

| Environment | Info |
| --- | --- |
| antd | 4.23.0 |
| React | 16.14.0 |
| System | mac os monterey 12.2.1 |
| Browser | 104.0.5112.101 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: Make a Draggable drag cancelable
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

It would be nice when it's possible to cancel a drag programmatically. Currently it's possible to cancel a drag in flutter, but the `_DragAvatar` that would allow for this is not exposed (see image).

## Use Case
An application that ends the drag as soon as you reach the boundary.

## Proposal

Either expose the `_dragAvatar` API or returns a boolean within the `DragUpdateCallback` which you can use to stop dragging.

<img width="641" alt="image" src="https://user-images.githubusercontent.com/25419507/189066570-485440b5-8864-4266-b6dc-e14accc51e4e.png">
Repository: opencv
Issue: Segfault on `imshow` when setting a `matplotlib` backend beforehand
Labels: bug,category: highgui-gui,category: 3rdparty

The python repository issue-template mentioned that issues that have to be fixed in C++ as well should be reported here.
Although the example is purely python. The example relies on `matplotlib` and may not be caused by `opencv` directly, but the segfault happens when calling a `opencv` function, so I'm reporting it here.

##### System information (version)
- OpenCV => `4.6.0-4` ([this](https://github.com/archlinux/svntogit-packages/blob/packages/opencv/trunk/PKGBUILD) is the package I'm using, it looks like it's using gcc, but I honestly can't tell)
- Python-OpenCV => `4.6.0.66`
- Operating System / Platform => Arch Linux `5.19.7-arch1-1 #1 SMP PREEMPT_DYNAMIC x86_64 GNU/Linux`
- Compiler => `gcc (GCC) 12.2.0` (see note above)

##### Detailed description

When importing `matplotlib.pyplot` and then setting a backend for `matplotlib` before using `opencv` the first call to `imshow` causes a segmentation fault.

##### Steps to reproduce

1. Set up a python environment using Python `3.9.13` with the following packages:
```
cycler          0.11.0
fonttools       4.37.1
gobject         0.1.0
kiwisolver      1.4.4
matplotlib      3.5.3
numpy           1.23.2
opencv-python   4.6.0.66
packaging       21.3
Pillow          9.2.0
pip             22.2.2
pycairo         1.21.0
PyGObject       3.42.2
pyparsing       3.0.9
PyQt5-Qt5       5.15.2
PyQt5-sip       12.11.0
pyrealsense2    2.51.1.4348
python-dateutil 2.8.2
scipy           1.9.1
setuptools      60.2.0
six             1.16.0
wheel           0.37.1
```

2. Prepare a python script like this:
```py
import matplotlib as mpl
import cv2

# swapping the order of thsese also resolves the issue
from matplotlib import pyplot as plt # removing this import resoves the issue
mpl.use('GTK3Agg') # remvoing this also resovle the issue

def test():
    webcam = cv2.VideoCapture(0)

    try:
        while True:
            ret, frame = webcam.read()

            # segfault happens on the first call to `imshow`
            cv2.imshow('frame', frame)
            if cv2.waitKey(1) & 0xFF == ord('q'):
                break
    finally:
        webcam.release()
        cv2.destroyAllWindows()


test()
```
3. Running the script.

##### 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: rust
Issue: Missed enum layout optimization with a NonZeroU64 + more space in an enum
Labels: T-compiler,A-layout

The `Provenance` type defined here is [24 bytes in size](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=7a3f56a0785aa4888ca3109fa5831a41):
```rust
use std::num::NonZeroU64;

pub enum Provenance {
    Concrete {
        alloc_id: NonZeroU64,
        sb: NonZeroU64,
    },
    Wildcard,
    None,
}
```
However, it should be possible to encode `Provenance` in 16 bytes: e.g. `(0usize, 0suize)` could encode `None` and `(0usize, 1usize)` could encode `Wildcard`.

In Miri, a [slight variant of this](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=7a3f56a0785aa4888ca3109fa5831a41) would help reduce the size of a fairly common type from 32 bytes to 24 bytes.

Unfortunately even https://github.com/rust-lang/rust/pull/94075 does not help here. The entire concept of reading a single field to determine the discriminant is not flexible enough to represent this layout.
Repository: PowerToys
Issue: Colorpicker color changes on hover (Not as spec'd by UX concept)
Labels: Issue-Bug,Area-User Interface,Priority-3,Product-Color Picker

### Microsoft PowerToys version

0.61.0

### Running as admin

- [X] Yes

### Area(s) with issue?

ColorPicker

### Steps to reproduce

To reproduce, start the colorpicker ( win shift c)
pick a color (midtones show it best)
Have our mouse outside of the selected color
![image](https://user-images.githubusercontent.com/62603552/189092973-5ca5bdf1-bfa0-4920-8013-b7b0662a087b.png)

Hover over it with your mouse; the color changes
![image](https://user-images.githubusercontent.com/62603552/189093103-789ba900-1d21-47ab-bde2-8f1c281c6d18.png)

Hover over any other color; that color changes too
![image](https://user-images.githubusercontent.com/62603552/189093337-25a01b27-2fe0-4ae6-8146-5d058f516003.png)


### ✔️ Expected Behavior

Expected behavior is to show the actual color, as per [Niels Laute's UX concept](https://medium.com/@Niels9001/a-fluent-color-meter-for-powertoys-20407ededf0c) : 

![image](https://miro.medium.com/max/700/1*G2rC8YO9cLRLSc124YTD8Q.gif)


### ❌ Actual Behavior

Usage for this colorpicker is to be able to choose exactly the color you want; it can be confusing when that color changes when you hoover over it; especially when looking/hovering for 'a matching colors'

In the screenshots above; the first (middle) color is HEX: 0ab6a8 , When you hover over it, it is HEX: 109a8e  
The left color is HEX: 0effeb , when you hover over it it is HEX: 13d4c4

This sounds like nitpicking, but when trying to find specific colors, it is frustrating to see the color change when you select it. did you select the correct color?

If you must have something to show as a selector, use an outline, or a background change, like in the sidebar with picked colors.

### Other Software

_No response_
Repository: godot
Issue: Changing the order of a Control node during TreeExiting results in errors and strange behaviour
Labels: bug,confirmed,topic:gui

### Godot version

4.0.dev 9142904c2

### System information

Win 11, RTX 3060

### Issue description

If a script changes the order of a control node within it's siblings during the TreeExiting event, many errors are thrown continuously whenever the mouse cursor hovers over the deleted control.
This also results in strange behaviour - for example, nodes above the deleted one no longer receive input.

The actual errors:
`E 0:00:02:0210   Node::can_process: Condition "!is_inside_tree()" is true. Returning: false
  <C++ Source>   scene\main\node.cpp:686 @ Node::can_process()`
`E 0:00:02:0228   CanvasItem::get_global_transform: Condition "!is_inside_tree()" is true. Returning: get_transform()
  <C++ Source>   scene\main\canvas_item.cpp:172 @ CanvasItem::get_global_transform()`

Please note that I've only tested this in C#, but it's most likely not C# specific.

### Steps to reproduce

1. Subscribe to the TreeExiting event/signal in a way that adds or deletes a node ahead of the current one in the scene hierarchy (so that the index of the current node changes).
2. Delete the node that you subscribed to.

### Minimal reproduction project

[DeleteTest.zip](https://github.com/godotengine/godot/files/9526479/DeleteTest.zip)

Click on the button, then hover over the label. Errors show up.
Repository: rust
Issue: Tracking issue for future-incompatibility lint `mem_uninitialized`
Labels: A-lints,T-libs-api,T-compiler,C-future-incompatibility,C-tracking-issue,S-tracking-unimplemented

> [!IMPORTANT]
> This lint has not been implemented yet! See #100342.

This is the **summary issue** for the `mem_uninitialized`
future-compatibility warning and other related errors. The goal of
this page is describe why this change was made and how you can fix
code that is affected by it. It also provides a place to ask questions
or register a complaint if you feel the change should not be made. For
more information on the policy around future-compatibility warnings,
see our [breaking change policy guidelines][guidelines].

[guidelines]: https://github.com/rust-lang/rfcs/blob/master/text/1122-language-semver.md

#### What is the warning for?

This warning will trigger whenever `std::mem::uninitialized` is used, unless the type returned consists of only raw pointers, integers, and floats.

As an example, `uninitialized::<[char; 64]>` will trigger the warning, but `uninitialized::<[u8; 64]>` will not. Additionally, in generic methods, `uninitialized::<T>` will trigger the warning, even though T might be a `[u8; 64]` when it is used.

To fix the warning, use [`std::mem::MaybeUninit`](https://doc.rust-lang.org/std/mem/union.MaybeUninit.html), and only `assume_init` once the value is fully initialized. Note that even though we do not warn for uninitialized integers here, it is still undefined behavior to create uninitialized integers.

The change to warn here was made in order to get notified when their dependencies inappropriately use `mem::uninitialized`, which can lead to runtime panics depending on the type (as tracked in https://github.com/rust-lang/rust/issues/66151). Using a lint here is less surprising than a runtime panic, and allows people to get notification of code that may break at runtime, earlier.

#### When will this warning become a hard error?

Unlike other future-compat warnings, this is never intended to be a hard error, it is purely to warn users about dangerous uses of `mem::uninitialized` in their dependency tree.
Repository: TypeScript
Issue: Type inference destructure object
Labels: Bug

# Bug Report

Typescript seems to not be able to infer correctly a rest object type.

I've found a workaround for it by nesting the value (in playground)

### 🔎 Search Terms

Destructuring

### 🕗 Version & Regression Information

Tested in 4.5.5, 4.8.2 and next (time of writing = v4.9.0-dev.20220908)

### ⏯ Playground Link

[Playground](https://www.typescriptlang.org/play?ts=4.8.2#code/JYWwDg9gTgLgBAJQKYEMDGMA0cDecBSAygBoCiANkiEgHYwDCENAzjFAK4bRwC+cAZlAgg4AciioMogFDSYATzBI4ANRTl2ygLy44Aej1wAKgAtgzOGCFLYwJBeYmI7cgBM4AI2XqA7inkWwCzArsowJsquKDAozEhYcDAQnt4elInJEjShUIkRcADmUChgJtJwcADWSPIAXHCsUEEFANzlcGgQ5ND1jc1tFQBu6pr1NOwgXlBtPG3SSAAekLCJisoA4sWlACLRKITxRmsAPO1GcIswtK4WyJ1Qrsd9NAXY7DSVNBA+NAB8cDo7tBHs9XnAaEhBkgoP8DMYzBYJFZ7LQYBZLsU4FEYnloh0UDQUnB2HF3D4IoSsjlmnllJQCtcBNwUHBhhokNJ-joABTSblqdlwABkxgAlMLcO16dd6kQyJRqHRGCw2JwklBjgLNBKjL9pDxRQBtAC6cwUSjgAAVrMxjudLtdbkh7iC2M03h8vj8uYhncCnm6XtgIVCYT6cO02ZpmPVNiUTLsYgcYEclHbfjM5noAFTw8xYiD2GiieA+aCVODZvTSToquCMcBMVEAuB2i4LK7ZJ0ugNNIPEz3fP6-bk4KP2Hj1a0QMC23XirT-cfMAB0IBK3NHcGl2Xq9BJSRAABkkAzstgV5erDOLAaAf9jvvWMIT2f3DhLyvr7O+HpfqL2gqIDgJA0CwPAiDIKg6CYNguCQLhAA9OBSCgIQoFkRZlngc1lAAdXLFAhHeVw4x2PZk1TJBTgqe0O0dX0e1BD1PiHH0gQeXt3XBSFoV+bA4VMfMkQkOI6HRDtMWxFlwjxNACSJEkkDJCk4CpaEaXCOlT0ZfhmVZEYOXDdoczgAA5ewrncaTK2rIZDPqLVlBFIwpR03cCBICgqFRZVGjVaBNUMnU9R4E1ZFwuACKgSoiOcbJp1nNsHS7Rj-WYgdWO9FsONdPswRDPjjPs9kYyiwjiOyMiEwow4Tl1TNZGkUyhIsVxCwsMsYosKsayYVhypiuKSIbSAIToFtkvo1Lcq4-t3iy4dR2XSdBtiyrXESud-3vAzSrXDctx3Vw9wPF93NcbBx14BcHyfQ9X0ZD9L3HX9-yAA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type Value = { // This properties should be always inside the dataset, to be able to render the graph
  key: string;
  color: string;
  value: number;
};

export type GraphDataSetType<
  T extends Record<string, unknown> = Record<string, never> // This represents extra data that can be used when rendering the legend for a value
> = (
(Value & T) & {
  legend: JSXElementConstructor<Value & T>
})[];

type Props<T extends Record<string, unknown> = Record<string, never>> = {
  values: GraphDataSetType<T>;
};

/* This doesn't work */
const Component = <T extends Record<string, unknown>>({values}: Props<T>) => values.map(({ legend: CustomLegend, ...props }) => <CustomLegend {...props} />)
                                                                                                                              // ^ Error
```

### 🙁 Actual behavior

Throws an error 
```
Type 'Omit<Value & T & { legend: JSXElementConstructor<Value & T>; }, "legend">' is not assignable to type 'IntrinsicAttributes & Value & T'.
  Type 'Omit<Value & T & { legend: JSXElementConstructor<Value & T>; }, "legend">' is missing the following properties from type 'Value': key, color, value
```

### 🙂 Expected behavior

Expect to not throw an error as ``` Omit<Value & T & { legend: ... }, "legend" }> === Value & T```
Repository: next.js
Issue: modularize_imports  issue for re-export from node_modules
Labels: bug,SWC

### Verify canary release

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

### Provide environment information

mac os/next 12.2.5

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

chrome

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

_No response_

### Describe the Bug

next 12.2.5 follow this feature. https://github.com/vercel/next.js/pull/38583
mostly this feature works fine, except another sense has an issue here

for example 

```tsx
     '@mui/material': {
        transform: '@mui/material/{{member}}',
        preventFullImport: true,
      },
```

consider below sense:
1. import {alpha} from `@mui/material`
2. the `alpha` is re-exported from `@mui/material`
```ts
export {
 alpha
} from '@mui/system';
```

3. in fact the `alpha` is really existed in `@mui/system`
4. but in the `next` it will transform to `@mui/material/alpha`, this is wrong, it should ignore `@mui/material/alpha` because we won't configure the `modularizeImports`



### Expected Behavior

 in fact the `alpha` is really existed in `@mui/system`
but in the `next` it will transform to `@mui/material/alpha`, this is wrong, it should ignore `@mui/material/alpha` because we won't configure the `modularizeImports`


### Link to reproduction

https://github.com/tianyingchun/next-issue

### To Reproduce

1. yarn 
2. yarn dev
3.  see console
4.  related feature: https://github.com/vercel/next.js/pull/38583
<img width="708" alt="image" src="https://user-images.githubusercontent.com/2833251/189121026-3c26aa4e-9153-4f24-8b36-55d2f4db2c1a.png">