sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: DISABLED test_attn_cuda (__main__.TestMin)
Labels: triaged,module: flaky-tests,skipped,module: functorch

Platforms: linux, win, windows

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_attn_cuda&suite=TestMin) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8828175188).

Over the past 3 hours, it has been determined flaky in 4 workflow(s) with 4 failures and 4 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_attn_cuda`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


cc @zou3519 @Chillee @samdow @soumith
Repository: pytorch
Issue: DISABLED test_variant_consistency_jit_linalg_lu_cuda_float32 (__main__.TestJitCUDA)
Labels: triaged,module: flaky-tests,skipped,module: unknown

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_variant_consistency_jit_linalg_lu_cuda_float32&suite=TestJitCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8828175049).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 failures and 1 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_variant_consistency_jit_linalg_lu_cuda_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
Repository: pytorch
Issue: NVFuser `FusionRootMappingMultipleBroadcast_CUDA` raises exception on sm_80+ 
Labels: module: cuda,module: ci,triaged,module: nvfuser

### 🐛 Describe the bug

See here for example (only change that test is compiled with sm_86 and run on A10G )
https://github.com/pytorch/pytorch/actions/runs/3222501479/jobs/5272211415

```
[ RUN      ] NVFuserTest.FusionRootMappingMultipleBroadcast_CUDA
unknown file: Failure
C++ exception with description "Should not be mappable: iS0{i0} of T0_l[ iS0{i0} ] and iS1{i0} of T1_l[ iS1{i0}, bS2{1} ]
Exception raised from checkIdMapped at /home/nshulga/git/pytorch/pytorch/torch/csrc/jit/codegen/cuda/test/test_gpu.cpp:3084 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0x6b (0x7f63622479bb in /home/nshulga/git/pytorch/pytorch/build/lib/libc10.so)
frame #1: c10::detail::torchCheckFail(char const*, char const*, unsigned int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) + 0xbf (0x7f63622428bf in /home/nshulga/git/pytorch/pytorch/build/lib/libc10.so)
frame #2: <unknown function> + 0x621c5c (0x55d14faf4c5c in ./bin/test_jit)
frame #3: torch::jit::NVFuserTest_FusionRootMappingMultipleBroadcast_CUDA_Test::TestBody() + 0x2f3 (0x55d14faf5cc3 in ./bin/test_jit)
frame #4: void testing::internal::HandleExceptionsInMethodIfSupported<testing::Test, void>(testing::Test*, void (testing::Test::*)(), char const*) + 0x4a (0x55d14fc118aa in ./bin/test_jit)
frame #5: <unknown function> + 0x72b85f (0x55d14fbfe85f in ./bin/test_jit)
frame #6: <unknown function> + 0x72bb42 (0x55d14fbfeb42 in ./bin/test_jit)
frame #7: <unknown function> + 0x72c3b5 (0x55d14fbff3b5 in ./bin/test_jit)
frame #8: testing::internal::UnitTestImpl::RunAllTests() + 0xe2f (0x55d14fc0a6df in ./bin/test_jit)
frame #9: testing::UnitTest::Run() + 0x98 (0x55d14fc0aad8 in ./bin/test_jit)
frame #10: main + 0xfb (0x55d14f7043cb in ./bin/test_jit)
frame #11: __libc_start_main + 0xe7 (0x7f63612c0c87 in /lib/x86_64-linux-gnu/libc.so.6)
frame #12: _start + 0x2a (0x55d14f75e79a in ./bin/test_jit)
" thrown in the test body.
[  FAILED  ] NVFuserTest.FusionRootMappingMultipleBroadcast_CUDA (1 ms)
```

### Versions

CI

cc @ngimel @seemethere @pytorch/pytorch-dev-infra
Repository: pytorch
Issue: Autograd doc does not mention torch.autograd.set_grad_enabled
Labels: module: docs,module: autograd,triaged,actionable

### 📚 The doc issue

[Autograd doc](https://pytorch.org/docs/stable/notes/autograd.html#locally-disable-grad-doc) does not mention `torch.autograd.set_grad_enabled`.

### Suggest a potential alternative/fix

Add reference to [`torch.autograd.set_grad_enabled`](https://pytorch.org/docs/stable/generated/torch.autograd.set_grad_enabled.html) used as function for disabling autograd in current thread.

cc @svekars @holly1238 @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: terminal
Issue: Multiline Paste Warning should be Editable
Labels: Help Wanted,Area-UserInterface,Product-Terminal,Issue-Task

# Description of the new feature/enhancement
![image](https://user-images.githubusercontent.com/28855373/195186047-bb5df9eb-2030-4eb8-bf9d-2f946943b44e.png)

Teams and other programs often add Headers or additional text to the Copy/Paste. I propose we make the MultiLine Warning dialog editable so we can modify the contents prior to confirming the paste.

# Proposed technical implementation details (optional)

I propose one of two solutions.
1. Add an Edit button to allow us to edit the contents of the paste. 
2. Convert the text to a Textbox so we can Edit prior to confirming.

I am thinking a button can go right here.
![image](https://user-images.githubusercontent.com/28855373/195186813-82c3e93a-97fe-4853-b527-612b6de081b9.png)
Repository: svelte
Issue: Compiler warnings on trying to set styles and classes on <svelte:body />
Labels: feature request,compiler

### Describe the problem

For the time being while features like changing `<body>` class (#3105) and styles

```
<svelte:body style="max-width: 50em; margin: auto;" />
```

are not supported, would be nice if the Svelte compiler showed a warning when people try to do this.

### Describe the proposed solution

Red squiggly lines below and a tooltip saying 

> The <svelte:body> element _only_ allows listening for events that fire on `document.body`. It does not support modifying `document.body`.

 on hovering lines like:

```
<svelte:body style="max-width: 50em; margin: auto;" />

<svelte:body class:foo={is_bar} />
```

### Alternatives considered

Current state of no compiler warning requires people to search GitHub.

### Importance

nice to have
Repository: angular
Issue: Language Service: Automatic Import Improvements
Labels: feature,area: language-service,feature: under consideration

I recently implemented auto-imports in the language service in https://github.com/angular/angular/pull/47088. This feature includes the scaffolding for a large number of possible improvements, tracked below. We should prioritize some of these to make the experience as excellent as possible.

- ✅ *(15.0.0)* **Automatic Quickfix Imports**: Suggest imports as a quick fix for unknown standalone components.
- ✅ *(15.0.0)* **NgModule support**: Support importing to and from NgModules, in addition to standalone components.
- ✅ *(15.1.0)* **Multi-suggestions**: If more than one directive has this selector, give the user a choice. 
- ✅ *(15.2.0)* **Pipes**: Support pipes as well as directives.
- 🗓️ **Declaration Files**: Suggest directives from .d.ts files, including imports with `@` specifiers.
- 🗓️ **Builtin Directives**: We should suggest first-party Angular directives and pipes when appropriate.

_✅ Complete |  🚧 In Progress |  🗓️ Planned_

**Collected PRs Relevant to this Hotlist**
Language Service: #47181, #47088, #47787, #47938, #48074, #48354
Compiler: #47180, #47166, #47561, #47631, #48090
Repository: godot
Issue: Collision category in CharacterBody3D, CharacterBody2D, SoftBody3D is not inside CollisionObject3D section.
Labels: bug,topic:editor,topic:physics

### Godot version

(mono) 4.0 b1, b2

### System information

Windows 10, Nvidia GTX 1660Ti, Vulkan

### Issue description

The Collision dropdown of CharacterBody3D, SoftBody3D (this doesn't have CollisionObject3D section at all so not sure how it should be here),  CharacterBody2D in the Inspector is not inside CollisionObject3D section.
Some other nodes such as Area3D, RigidBody3D, VehicleBody3D, StaticBody3D, AnimatableBody3D, RigidBody2D, AnimatableBody2D do have CollisionObject3D/2D section and Collision dropdown is inside it.

In the picture I show you one of the examples.

![obrazek](https://user-images.githubusercontent.com/33526847/195195606-1eef3908-f650-4910-9140-a306d4785ab4.png)

Note:
As mentioned above I'm not sure about SoftBody3D as it does not have the CollisionObject section at all but all the other nodes have it.

### Steps to reproduce

Check the body nodes in the Inspector.

### Minimal reproduction project

-
Repository: go
Issue: cmd/go: add a flag to use stdin as a cancellation side-channel
Labels: Proposal,Proposal-Accepted,GoCommand

The `go` command executes a lot of subprocesses as it runs, including:
- the Go compiler and linker, and in cgo-enabled builds the C compiler and linker,
- version-control tools to download modules that aren't available from a proxy,
- the `vet` tool to analyze programs,
- test binaries built for packages under `go test` and `go test -fuzz=.`, and
- binaries executed by `go run` (#54868 notwithstanding).

Some clients of the `go` command end up starting a command, letting it run a while, and then wanting to cancel its execution. For example, `gopls` may start running `go list` to evaluate a program being edited, but then cancel that command due to another edit to the files in the user's workspace or a failure in some other concurrent processing that renders the `go list` result irrelevant.

If the `go` process itself is forcibly terminated using `os.Kill` (via either `(*os.Process).Kill` or `exec.CommandContext`), its subprocesses may continue to execute for an arbitrarily long time, leaking resources and (on Windows, at least) potentially preventing cleanup of temporary files and directories.

On Unix platforms, we can instead request a clean shutdown using `os.Interrupt`. (The `go` command may or may not respond appropriately to that signal today, but in principle it _can_ and that's what matters in terms of the public-facing API.) However, `os.Interrupt` does not work on Windows, and per discussion on #6720 and #46345 we don't know of a general way to make it work. (At the very least, it would require `os/exec` to make invasive and likely-incompatible assumptions about consoles and process groups.)

Since `os.Kill` leaks resources and `os.Interrupt` isn't always available, we need some other way to request cancellation of a running `go` command.

Fortunately, we have a way out: as far as I am aware, every platform that supports `os/exec` in Go also supports inter-process pipes, and `cmd/go` to my knowledge does not use `stdin` for anything today.

----

I propose that we add a new flag to the `go` command, `-stdin=keepalive`, that will cause it to read from (and discard bytes from) `stdin` until EOF, then make a best effort to cancel all subprocesses, clean up, and exit as soon as possible.

The choice of `-stdin=keepalive` leaves open the possibility of using `stdin` in other ways in the future, while being clear about both its role (“keepalive”) and mechanism (“stdin”).

(CC @golang/tools-team)
Repository: go
Issue: math/big: new examples that fail the checks in TestFloat64SpecialCases
Labels: help wanted,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?
go version go1.19.2 linux/amd64

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

```
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/adam/.cache/go-build"
GOENV="/home/adam/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/adam/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/adam/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/tmp/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/tmp/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.2"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/tmp/go/src/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2907961955=/tmp/go-build -gno-record-gcc-switches"
```

### What did you do?

I have found a few edge cases that fail the `TestFloat64SpecialCases` test.

To reproduce:

Add the following edge cases to `float64inputs` in [ratconv_test.go](https://github.com/golang/go/blob/master/src/math/big/ratconv_test.go) and run the `TestFloat64SpecialCases` test:

- `"170141183460469231731687303715884105728p-48317"`,
- `"0000000000000000000000000000031768211457p-9818716"`,
- `"00000000000000000000000000000000000000000000000000000000001662320182p-801401"`,
- `"818p-8818873"`,

The stack trace will be:

```
--- FAIL: TestFloat64SpecialCases (1.08s)
    ratconv_test.go:589: Rat.SetString("170141183460469231731687303715884105728p-48317").Float64().exact = true, want false
    ratconv_test.go:589: Rat.SetString("0000000000000000000000000000031768211457p-9818716").Float64().exact = true, want false
    ratconv_test.go:589: Rat.SetString("00000000000000000000000000000000000000000000000000000000001662320182p-801401").Float64().exact = true, want false
    ratconv_test.go:589: Rat.SetString("818p-8818873").Float64().exact = true, want false
```




### What did you expect to see?



### What did you see instead?
Repository: pytorch
Issue: DISABLED test_variant_consistency_jit_linalg_lu_factor_cuda_complex64 (__main__.TestJitCUDA)
Labels: triaged,module: flaky-tests,skipped,module: unknown

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_variant_consistency_jit_linalg_lu_factor_cuda_complex64&suite=TestJitCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8829357726).

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 2 failures and 2 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_variant_consistency_jit_linalg_lu_factor_cuda_complex64`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.
Repository: pytorch
Issue: DISABLED test_vmapjvpvjp_linalg_lu_cuda_float32 (__main__.TestOperatorsCUDA)
Labels: triaged,module: flaky-tests,skipped,module: functorch

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_vmapjvpvjp_linalg_lu_cuda_float32&suite=TestOperatorsCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8828597209).

Over the past 3 hours, it has been determined flaky in 5 workflow(s) with 5 failures and 5 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_vmapjvpvjp_linalg_lu_cuda_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


cc @zou3519 @Chillee @samdow @soumith
Repository: pytorch
Issue: DISABLED test_reentrant_parent_error_on_cpu_cuda (__main__.TestAutogradDeviceTypeCUDA)
Labels: module: autograd,triaged,module: flaky-tests,skipped

Platforms: win, windows, rocm



This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_reentrant_parent_error_on_cpu_cuda&suite=TestAutogradDeviceTypeCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8829817384).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 failures and 1 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_reentrant_parent_error_on_cpu_cuda`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: godot
Issue: was RenderingServer.black_bars_set_margins removed intentionally in Godot 4.0 beta 2
Labels: discussion,topic:rendering

### Godot version

4.0 beta 2

### System information

Windows 10

### Issue description

was RenderingServer.black_bars_set_margins removed intentionally?

### Steps to reproduce

try running a project with code

### Minimal reproduction project

_No response_
Repository: opencv
Issue: AffineFeature Mask
Labels: bug

### System Information

OpenCV python version: 4.6.0
Operating System / Platform: macOS Monterey 12.6
Python version: 3.9.13

### Detailed description

I am used to use mask feature detector in OpenCV and it works fine for all except AffineFeature, i.e. once I determine a mask for AffineFeature with any backbone, I see detected points in the area with 0 label in mask.

### Steps to reproduce

```python
import cv2 as cv
import numpy as np

I = cv.imread(any image, 0)
MASK = np.zeros_like(I, np.uint8)
MASK[:250, :250] = 1

affinefeature = cv.AffineFeature_create(cv.SIFT_create())
kp, desc = affinefeature.detectAndCompute(I, mask=MASK)
cv.drawKeypoints(I, kp, None, color=-1, flags=2)
# NOTE: based on the defined MASK, we should not have any ASIFT points outside of the MASK (0->250 and 0->250), but there are points there.
```

### 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: godot
Issue: Error is shown when i add skeletonIK nodes to a skeleton from an imported mesh.
Labels: bug,topic:import,topic:animation

### Godot version

3.5.1 rc2

### System information

Macos Monterey

### Issue description

I get this error when I'm using inverse kinematics. the error does not stop the game from running and it does not show any impact on the game. it just pops up in the output whenever i start or stop the game from running. This occurs both on GLES2 and GLES3. I also suspect the cause is because i did clear inheritance after importing the model.

E 0:00:07.256   build_chain: Condition "p_task->root_bone >= ee->tip_bone" is true. Returned: false
  <C++ Source>  scene/animation/skeleton_ik.cpp:77 @ build_chain()


### Steps to reproduce

Import a rigged 3D model and attach a skeletonIK node to the Skeleton.

### Minimal reproduction project

_No response_
Repository: godot
Issue: Improve external animation signaling in the editor
Labels: enhancement,topic:editor,usability,topic:animation

### Godot version

4.0.beta.2

### System information

Windows 11, NVIDIA 3050, Intel i7 11th gen

### Issue description

The add track button is missing on models imported from external applications (specifically blender) even after the .glb file is saved as a scene in a .tscn file 
![image](https://user-images.githubusercontent.com/77935781/195238069-69319e39-ebd4-4da9-aec1-ac7531374d52.png)


### Steps to reproduce

1.) Create a model with rigged animations in blender
2.) import into godot
3.) attempt to add a track to the animationPlayer

### Minimal reproduction project

[IssueProject.zip](https://github.com/godotengine/godot/files/9761071/IssueProject.zip)
Repository: stable-diffusion-webui
Issue: keep original png file's chunks(text information) while img2img processing
Labels: enhancement

**Is your feature request related to a problem? Please describe.**
After processing images in img2img tabs, original text information(prompts and parameters) which saved in png file as chunks is replaced with new text information. If we forget which file is original, it's too hard to reproduce images.

**Describe the solution you'd like**
If a original image is png file and it has text information, keep it and append new text information. In case of it has already appended information, handle it like original information and append new information.
ex>
[original information - prompts and parameters]
Modified at [datetime], [img2img process prompts and parameters]
Modified at [datetime], [img2img process prompts and parameters]


**Describe alternatives you've considered**
Or just put original image file names in chunk information if the name is available .
ex>
original image : [filename]
Modified at [datetime]
[img2img process prompts and parameters]

**Additional context**
Add any other context or screenshots about the feature request here.
Repository: pytorch
Issue: DISABLED test_vmapjvpall_linalg_lu_cuda_float32 (__main__.TestOperatorsCUDA)
Labels: triaged,module: flaky-tests,skipped,module: functorch

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_vmapjvpall_linalg_lu_cuda_float32&suite=TestOperatorsCUDA) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/8836194077).

Over the past 3 hours, it has been determined flaky in 1 workflow(s) with 1 failures and 1 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT BE ALARMED IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_vmapjvpall_linalg_lu_cuda_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


cc @zou3519 @Chillee @samdow @soumith