sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Inductor Graph Partitioning For Cudagraphs
Labels: triaged,module: cuda graphs,oncall: pt2

### 🚀 The feature, motivation and pitch

CUDAGraphs has limitations on what it can support. We fallback for:
- unsupported operators: operators which trigger d->h, h->d, or which have syncs. 
- cpu compute - although we have have a [pass to move compute to cuda](https://github.com/pytorch/pytorch/blob/ee0034978029100e5224b8a43cf0ef82136a244f/torch/_inductor/fx_passes/post_grad.py#L118C5-L118C30)
- mutation - although we support many cases of it (see https://github.com/pytorch/pytorch/issues/121861)

We also force re-recording for changing float and int inputs.  

Failing to cudagraph has been an issue for a while, but we now we have two new forcing functions. [Compiled Autograd](https://github.com/pytorch/pytorch/pull/125382/) has cpu inputs. We about to emit dynamic [code for float inputs](https://github.com/pytorch/pytorch/pull/125325). Both would play poorly with cudagraphs today.	CompiledAutograd also the difficulty that it will combine all of the backwards into one graph. If you had multiple graphs in the backward, some of which you were cudagraphing and some which you were not, now you will skip the whole backward.

Arbitrary cudagraph partitioning is not straightforward. Anytime you partition as :

Cudagraph1 -> FallbackGraph1 -> Cudagraph2 

Partitioning will split memory between cudagraph and fallback regions. It will incur a copy cost and memory duplication for all of the outputs of fallback graphs into cudagraphs. And it will stop potential cross-graph optimizations like fusion, which doesn't apply as much for the cpu->cuda case. The original "cudagraphs" backend [partitioned](https://github.com/pytorch/pytorch/blob/a0265a446e3797ef8e295cbf88bb281b7335b881/torch/_dynamo/backends/cudagraphs.py#L134-L136) around all mutations but it actually made things slower.

I think we can start incrementally and with simple heuristics for partitioning and expand. As a first pass, it might make sense just to partition a prologue for cpu tensors and float inputs. We could also expand the pass to move constructors on cpu to cuda to also work on inputs to the graph. 

One tricky thing to handle here will be updating all of the metadata we pass to inductor for each of the compilations. 

### Alternatives

_No response_

### Additional context

_No response_

cc @mcarilli @ezyang @peterbell10 @msaroufim @bdhirsh @anijain2305 @chauhang @xmfan @BoyuanFeng
Repository: vscode
Issue: Post exit update attempt abends if another user has VSCode open on the same machine.
Labels: bug,install-update,windows

Type: <b>Bug</b>

Under Windows 10, if user A opens vscode, switches to user B, opens vscode and closes vscode while an update to vscode is pending, the update process for user B reports obscure errors rather than simply identifying that another user (user A in this case) has vscode locked, and as such an update isn't possible at this time (or alternatively, just silently quiting).

VS Code version: Code 1.89.0 (b58957e67ee1e712cebf466b995adf4c5307b2bd, 2024-05-01T02:09:22.859Z)
OS version: Windows_NT x64 10.0.19045
Modes:


<!-- generated by issue reporter -->
Repository: ant-design
Issue: MenuItem title stop working when it has children.
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/menu-item-title-6glrvk?file=%2Fsrc%2FApp.tsx)

### Steps to reproduce

Create a MenuItem array, assign title property to all top level items, then some add children, some doesn't add children.

### What is expected?

Menu item title should show a string when mouse hover.

### What is actually happening?

It only shows when there's no children

| Environment | Info |
| --- | --- |
| antd | 5.16.5 |
| React | 4.4.4 |
| System | Win11 |
| Browser | Edge & Chrome |

---
https://codesandbox.io/p/sandbox/menu-item-title-6glrvk?file=%2Fsrc%2FApp.tsx

Above example will show details.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: go
Issue: proposal: regexp: the regexp package should support context
Labels: Proposal

### Go version

latest

### Output of `go env` in your module/workspace:

```shell
N/A
```


### What did you do?

N/A

### What did you see happen?

Regexp did not cancel early

### What did you expect to see?

It would be sensible to have a long running regexp match operation be cancellable with the context package.

I know this package was created before the `context` package was, but this might be a useful addition for a future extension of this package or golang2.x

Cheers
Repository: react
Issue: [React 19] custom element property vs. attribute behavior deviates from RFC discussion and proposal doc
Labels: React 19

## Summary

Hey folks! Not sure if the decisions here changed and I missed it, but it looks like the current React 19 beta impl for react props -> web component props/attrs has changed from what was originally [discussed](https://docs.google.com/document/d/1wwL_YZ5TnYorEEr2Lkeh9rgbnsynDXXI7tCejVcpE6I/edit#heading=h.86shuzhenihc) by @josepharhar. The tl;dr:

Unlike Preact, "complex values" were originally going to only be assigned to properties (if/when they exist). If the property does not exist, no value would be assigned. Instead, [only functions and Symbols are omitted from setting as attributes](https://github.com/facebook/react/blob/main/packages/react-dom-bindings/src/client/DOMPropertyOperations.js#L111-L114).

Not only does this result in likely undesired behavior (e.g. `anattr="[object Object]"`), it can also result in runtime errors that are potentially difficult to debug, e.g.:
```tsx
<my-wc iThoughtThisWasAProp={[aSymbol]}><my-wc> // This will crash
```

It looks like the originally planned logic could be introduced [in this general vicinity](https://github.com/facebook/react/blob/main/packages/react-dom-bindings/src/client/DOMPropertyOperations.js#L224-L227). Not sure if this is a bug, a feature request, or just a discussion as to why the change in plans, but just wanted to surface for visibility, just in case. Also, happy to cobble together a codesandbox or similar if that would be helpful!

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->
Repository: material-ui
Issue: [joy-ui][Modal] Is it expected for actions to be presented inverted?
Labels: good first issue,component: dialog,package: joy-ui

### Steps to reproduce

Link to live example: https://codesandbox.io/p/sandbox/lucid-tereshkova-hyfyys?file=%2Fsrc%2FDemo.tsx%3A44%2C52

Steps:
1. Click in the button to open the modal
2. Press <kbd>Tab</kbd> to navigate between the actions

![Kooha-2024-05-09-19-59-37](https://github.com/mui/material-ui/assets/42154031/07aa898f-536d-48a9-a88e-6b49db691208)



### Current behavior

The options are presented inverted relative to how they were defined in the code.

### Expected behavior

I don't know if this is expected but pressing <kbd>Tab</kbd> should move the focus forward. For instance, with the focus in "Archive", the next focusable element is the "Discard notes" button. The Material Design [modal](https://next.mui.com/material-ui/react-dialog/#form-dialogs) behaves like that.

If it's a bug, I think it's just the case of aligning the buttons with `justify-content: flex-end` instead of `flex-direction: row-reverse`.

### Context

_No response_

### 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>


**Search keywords**: joy modal actions
Repository: rust
Issue: It is unclear what combination of CPU features is safe.
Labels: T-compiler,A-docs,C-discussion,A-target-feature

### Location

https://doc.rust-lang.org/rustc/targets/known-issues.html

### Summary

The linked page says:

> Most target-feature problems arise, when mixing code that have the target-feature enabled with code that have it disabled. If you want to avoid undefined behavior, it is recommended to build all code (including the standard library and imported crates) with a common set of target-features.

> By default, compiling your code with the -C target-feature flag will not recompile the entire standard library and/or imported crates with matching target features. Therefore, target features are generally considered as unsafe. Using #[target_feature] on individual functions makes the function unsafe.

Since this guide only provides examples of what's _not_ okay (and calls them out explicitly as incomplete), and doesn't provide any guarantees about what _is_ okay, a strict reading suggests that it's basically never okay to use target features at all (unless you are an expert on all the possible variations of your platform's ABI). A normal user who is not an expert has no way of knowing that any given feature is okay to enable so if they see these docs, they will have to be conservative and enable nothing.

I think this is an oversight, because I can't imagine that e.g. it's unacceptable/UB to enable mainstream SIMD features like AVX .
Repository: rust
Issue: Tracking issue for invalid_reference_casting
Labels: C-tracking-issue

This is a tracking issue for the lint `invalid_reference_casting`, which was uplifted from Clippy's `cast_ref_to_mut` lint in https://github.com/rust-lang/rust/pull/111567.

This lint is deny-by-default, i.e. `#![deny(invalid_reference_casting)]`.

### Status

This lint was uplifted directly from Clippy, but shortly after that a bug in the lint was reported: https://github.com/rust-lang/rust/issues/124685. Currently we are working on eliminating all forms of this issue.

### Steps

- [ ] @saethlin is doing some investigation into how this lint is tripped across the ecosystem by crawling crater results.

### Open Questions

The lint currently hunts for an expression that represents the backing allocation, then if it encounters a pattern known to produce false positives, we punt on reporting that case. Should we invert the logic and be silent by default instead?

### Implementation history
https://github.com/rust-lang/rust/pull/111567
https://github.com/rust-lang/rust/pull/124761
https://github.com/rust-lang/rust/pull/124908
https://github.com/rust-lang/rust/pull/124978
Repository: flutter
Issue: Could `flutter_test` replace `integration_test`
Labels: a: tests,c: proposal,f: integration_test,P3,team-framework,triaged-framework

@goderbauer @jonahwilliams @johnmccutchan and @matanlurey [met today](https://github.com/flutter/flutter/issues/148028#issuecomment-2103678217) to discuss Flutter testing.

One of the topics that came up, but we _don't_ plan to act on in the near term, is the differences between `flutter_test` and `integration_test`: both of them run in the same process (and isolate) of the running app, compared to an external test through `flutter_driver`, and what would it take for `flutter_test` to just subsume `integration_test`.

A non-exhaustive list might include:

- `flutter_test` would need to formally support running on a device[^1]
- Plugins and platform views would need to be enabled (versus be stubs)
- Test results would need to be reported[^1]
- Re-building something like an APK continuously sucks when iterating, so supporting something like hot restart

The general feel is that _most_ of these changes are tooling related, but of course devil is in the details.

It's also worth mentioning this effort would have to come after we decide that `flutter_driver` should be the "external" testing story (right now both `flutter_driver` _and_ `integration_test` attempt to be our _external_ testing story).

[^1]: It works today if you run `flutter run test/path_to_test.dart` but there are no test results reported
Repository: pytorch
Issue: dynamo_export fails to produce a graph from nn.GLU : no tensor operations were found 
Labels: module: onnx,triaged

### 🐛 Describe the bug

Here's a simple repro. Legacy export works, dynamo_export fails:
```
import torch

model = torch.nn.GLU().eval().cuda()
sample_input = (torch.randn(8, 4).cuda(),)

# This works fine                                                                                                           
torch.onnx.export(model, sample_input, "glu_legacy.onnx")

# The following error is produced by dynamo_export:                                                                         
# AssertionError: Failed to produce a graph during tracing as no tensor operations were found.                              

options = torch.onnx.ExportOptions(dynamic_shapes=True)

out = torch.onnx.dynamo_export(model,
                               *sample_input,
                               export_options=options
                               )
out.save("glu.onnx")



### Versions

PyTorch nightly 05/09
Repository: rust
Issue: The structure definition of dllimport seems to lack information and is not enough to generate an undecorated lib.
Labels: A-linkage,A-LLVM,O-windows,T-compiler,C-bug

Where rust calls llvm, the symbolname is left blank, which makes the structure definition of dllimport seem to lack information and is not enough to generate an undecorated lib.
<img width="638" alt="FBCB13F97186228859BF21CB085FD4BA" src="https://github.com/rust-lang/rust/assets/83765419/c0b17d29-78e3-4d8c-a4d8-ca354558ed63">

![{D68F8C74-9B96-A55C-E70C-ECE8D5F008CB}](https://github.com/rust-lang/rust/assets/83765419/004db7a8-9144-4708-a76b-42c7dc89d6c5)

![712E7975E74D9587542E2CE1F801611A](https://github.com/rust-lang/rust/assets/83765419/a7a99bf8-65a2-4cf2-abee-d65aecf6b6c7)
![9704252B8B4EA78E8088CAA9F83B871F](https://github.com/rust-lang/rust/assets/83765419/2223d06a-a711-4239-afa1-342fd0212219)
Repository: pytorch
Issue: Support for third-party use of pipeline
Labels: oncall: distributed,triaged,module: PrivateUse1

### 🚀 The feature, motivation and pitch

I'm working on a 3rd party pipline feature, but currently it only supports cuda and cpu. hopefully pipline will support 3rd party.

### Alternatives

_No response_

### Additional context

The methods in torch/distributed/pipeline/sync/stream.py are limited to cuda and cpu use only, hopefully they can be expanded for third parties

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @chauhang @d4l3k @NmomoN @mengpenghui @fwenguang @cdzhan @1274085042 @PHLens
Repository: angular
Issue: Issue in scrolling in menu and sub menu in sidebar in docs
Labels: P3,area: docs-infra

### Describe the problem that you experienced

When scroll in menu using mobile view, the scroll is disabled 

### Enter the URL of the topic with the problem

https://angular.dev/guide/components

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

Fix scroll 
![Screenshot_2024-05-10-06-14-41-277_com android chrome](https://github.com/angular/angular/assets/55943011/c5ac1e81-0bea-4f6d-ba21-66931bb5abb4)
issue 

### Describe what you want to experience that would fix the problem

Fix scrolling in mega menus 

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

_No response_

### If the problem is browser-specific, please specify the device, OS, browser, and version

Redmi note 12 pro, chrome browser 

### Provide any additional information here in as much as detail as you can

_No response_
Repository: kubernetes
Issue: [Flaking Test][sig-storage] should block a second pod from using an in-use ReadWriteOncePod volume on the same node
Labels: sig/storage,kind/flake,triage/accepted

### Which jobs are flaking?

- e2e-kops-aws-cni-cilium-eni
- ci-kubernetes-kind-e2e-parallel-1-29
- pull-kubernetes-e2e-kind

### Which tests are flaking?

Kubernetes e2e suite: [It] [sig-storage] CSI Volumes [Driver: csi-hostpath] [Testpattern: Dynamic PV (default fs)] read-write-once-pod [MinimumKubeletVersion:1.27] should block a second pod from using an in-use ReadWriteOncePod volume on the same node

### Since when has it been flaking?

Unclear. It appears to be for a while but I haven't been able to find an issue already filed.

https://storage.googleapis.com/k8s-triage/index.html?date=2024-05-09&test=should%20block%20a%20second%20pod%20from%20using%20an%20in-use%20ReadWriteOncePod

### Testgrid link

https://testgrid.k8s.io/presubmits-kubernetes-blocking#pull-kubernetes-e2e-kind

### Reason for failure (if possible)

```
[FAILED] failed to wait for FailedMount event for pod2: got error while getting events: client rate limiter Wait returned an error: context deadline exceeded
In [It] at: k8s.io/kubernetes/test/e2e/storage/testsuites/readwriteoncepod.go:233
```

```
[FAILED] failed to wait for FailedMount event for pod2: got error while getting events: client rate limiter Wait returned an error: rate: Wait(n=1) would exceed context deadline
```

### Anything else we need to know?

https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/124683/pull-kubernetes-e2e-kind/1788664943130710016

### Relevant SIG(s)

/sig storage
Repository: puppeteer
Issue: [Feature]:  when I want to generate a pdf with 2 per sheet each, I don't find the corresponding api in "page.pdf (options?: PDFOptions)". 
Labels: feature,P3

### Feature description

Hello dear author, when I want to generate a pdf with 2 per sheet each, I don't find the corresponding api in "page.pdf (options?: PDFOptions)". Can you support this function? Thank you very much.
![screen](https://github.com/puppeteer/puppeteer/assets/8838858/de5f0c4b-2b15-4c05-8fea-45a7a5777cd4)
Repository: vscode
Issue: remote extension host terminated unexpectedly
Labels: under-discussion,remote

Type: <b>Bug</b>

1. Upgrade from 1.84.2 to 1.89.0
2. Install the Microsoft remote Development extension
3. Connect to linux system
4. Error appears, according to remote agent log it produces an segmentation fault. See attached logfile.


VS Code version: Code 1.89.0 (b58957e67ee1e712cebf466b995adf4c5307b2bd, 2024-05-01T02:09:22.859Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Connection to 'SSH: 172.22.60.112' could not be established  Canceled

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (12 x 2904)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<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_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|31.76GB (16.45GB free)|
|Process Argv|--crash-reporter-id 818bd2ed-537b-4deb-b60c-980a17668484|
|Screen Reader|no|
|VM|0%|

Connection to 'SSH: 172.22.60.112' could not be established  Canceled
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
tftest:31042121
vstes516:30244333
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
showvideoc:31016891
dsvsc021:30996838
0ee40948:31013168
a69g1124:31038041
dvdeprecationcf:31040882
dwnewjupytercf:31039676

```

</details>

<!-- generated by issue reporter -->
[remoteagent.log](https://github.com/microsoft/vscode/files/15270825/remoteagent.log)
Repository: terminal
Issue: Restart-connection on an active terminal does not terminate original process
Labels: Issue-Bug,Area-TerminalConnection,Product-Terminal

### Windows Terminal version

1.19.11213.0

### Windows build number

10.0.22631.3447

### Other Software

_No response_

### Steps to reproduce

* Open Windows terminal
* Open Process Explorer and find the `WindowsTerminal.exe` process in the tree
* Observe that there is one `OpenConsole.exe` and a shell process e.g. `pwsh.exe`
* Run the "Restart connection" command
* Observe that there are now _two_ `OpenConsole.exe` and `pwsh.exe` (or whatever was running before), and there is no way to interact with the original processes (that I am aware of)

### Expected Behavior

Running "Restart connection" terminates the shell in the current tab before launching a new one (or after, I don't care).

### Actual Behavior

The original shell process remains and is not accessible any more.
Repository: kubernetes
Issue: InPlacePodVerticalScaling does not meet the requirement of qosClass being equal to Guaranteed after shrinking the memory
Labels: kind/bug,sig/node,triage/accepted

### What happened?

InPlacePodVerticalScaling does not meet the requirement of qosClass being equal to Guaranteed after shrinking the memory
![image](https://github.com/kubernetes/kubernetes/assets/13641341/0c5d19fb-b124-4cbf-a520-b574d3fe0656)


### What did you expect to happen?

InPlacePodVerticalScaling maintains the same qosclass type of Pod before and after scaling

### How can we reproduce it (as minimally and precisely as possible)?

After enabling the InPlacePodVerticalScaling feature, the patch modifies the request and limit of the container's resource to a value smaller than usage

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.1", GitCommit:"3ddd0f45aa91e2f30c70734b175631bec5b5825a", GitTreeState:"clean", BuildDate:"2022-05-24T12:17:11Z", GoVersion:"go1.18.3", Compiler:"gc", Platform:"darwin/amd64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"29", GitVersion:"v1.29.2", GitCommit:"4b8e819355d791d96b7e9d9efe4cbafae2311c88", GitTreeState:"clean", BuildDate:"2024-02-14T22:24:00Z", GoVersion:"go1.21.7", Compiler:"gc", Platform:"linux/amd64"}
</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>