sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/go: "RLock …: Function not implemented" when the main module is in a filesystem that does not support locking
Labels: NeedsFix,modules

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.1 android/arm64
</pre>

### Does this issue reproduce with the latest release?
No


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/data/data/com.termux/files/home/.cache/go-build"
GOENV="/data/data/com.termux/files/home/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="android"
GOINSECURE=""
GOMODCACHE="/data/data/com.termux/files/home/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="android"
GOPATH="/data/data/com.termux/files/home/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/data/data/com.termux/files/usr/lib/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/data/data/com.termux/files/usr/lib/go/pkg/tool/android_arm64"
GOVCS=""
GOVERSION="go1.17.1"
GCCGO="gccgo"
AR="ar"
CC="aarch64-linux-android-clang"
CXX="aarch64-linux-android-clang++"
CGO_ENABLED="1"
GOMOD="/storage/8D8B-150E/Go/secure-api/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/data/data/com.termux/files/usr/tmp/go-build380772883=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
I tired to create a module for my new golang project using ```go mod init github.com/ayush/secure-api```


### What did you expect to see?
I expected of successfully creation of module for my project.


### What did you see instead?

Error I got:
```go: RLock /storage/8D8B-150E/Go/secure-api/go.mod: function not implemented```
Repository: PowerToys
Issue: [Keyboard Manager]:  'Remap a key' Dialog is not getting closed using 'ESC' key.
Labels: Issue-Bug,Area-Accessibility,A11yE+D,A11ySev3,A11yWCAG

### Microsoft PowerToys version

0.45.0

### Running as admin

- [ ] Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

**Steps to reproduce**
Test Environment:
OS: Windows 11 Version Dev
App version: 0.45.0
App name: PowerToys
Screen Reader: Narrator
Tool: Accessibility Insight for Windows

**Repro Steps:**
1.	Launch 'PowerToys' application.
2.	In General tab, navigate to 'Keyboard Manager’ button and activate.
3.	Navigate to ‘Remap a key’ and activate it using enter/Space key.
4.	Now, Remap a key dialog box will appear.
5.      Press 'ESC' key and Observe the issue.

**Note :**
Same issue repro with Remap a shortcut.

**User Impact:** -> Priority 2
Keyboard user will face issue while navigating the app.

**Guidelines Reference:**-
https://www.w3.org/TR/WCAG21/#multiple-ways

**Attachments:** 

https://user-images.githubusercontent.com/91203131/134474753-5428fedf-1739-4be2-8409-30a8c794797c.mp4

![PowerToys - 'Remap a key' Dialog is not getting closed using 'ESC' key](https://user-images.githubusercontent.com/91203131/134474186-2a591ab2-d80d-4a24-bbf4-7f7aa53feabc.png)

![PowerToys - 'Remap a Shortcut' Dialog is not getting closed using 'ESC' key](https://user-images.githubusercontent.com/91203131/134474591-7a1742bb-126f-4196-b905-0febf0d22b28.png)

### ✔️ Expected Behavior

When 'Esc' key pressed the 'Remap a key' dialog should get closed.

### ❌ Actual Behavior

When 'Esc' key pressed on the 'Remap a key' dialog is not getting closed.

### Other Software

_No response_
Repository: vscode
Issue: Balanced bracket delete
Labels: feature-request,editor-bracket-matching

Feature request for deleting brackets at once. 

Before:
```
const x = ("hello world")|;
```

After invoking the command "Delete bracket" befor `|`:
```
const x = "hello world"|;
```
Repository: flutter
Issue: App gets stuck after changing from stateless to stateful and trying to hot restart.
Labels: framework,t: hot reload,a: debugging,P2,team-framework,triaged-framework

As the title says now since the update to flutter 2.5 whenever a mistake is made in the code that is not indicated in the editor with a red mark, the application crashes completely instead of showing you the exception in console as it has always done . That is very annoying because you always have to hit the play button until the application gets good and thus be able to do a hot restart or you have to stop it completely and start it again.

For instance, every time I change a StatelessWidget for a StatefulWidget and save my application it crashes because it tries to do the hot reload, and I have to hit the play button until it finally lets me restart the app. If I didn't restart it like this, I would have to stop it and restart completely because it won't let me continue. This is something very annoying that did not happen before, so it would be good if you did something about it, because obviously I already know that if I have changed a StatelessWidget for a StatefulWidget that can cause me problems and I have to restart but anyway it is not necessary to stop all my application but to indicate it to me by console as it has always done and so I fix it before continuing again, since now when it stops it makes you waste a lot of time ...
Repository: TypeScript
Issue: [4.3, 4.4] Inline filtering mapped type conditional with `infer` fails
Labels: Bug,Needs Investigation,Rescheduled

# Bug Report

As of TypeScript 4.3, when inlining a mapped type on the left-hand side of `extends` in a conditional type, TypeScript incorrectly evaluates the condition when the right-hand side contains another mapped type with `infer` and renders the false condition. When declaring the mapped type explicitly rather than inline, the ternary is correctly evaluated.

This is pretty hard to cover in words, so please check playground link for reproduction.

The language version can be changed to 4.2 to see it working correctly.

### 🔎 Search Terms

typescript infer inline mapped type never generic inference

### 🕗 Version & Regression Information

- This changed between versions 4.2 and 4.3

### ⏯ Playground Link

Change TS language to 4.2 to see the code functioning correctly, and 4.3 or 4.4 to see failure.

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.4.2#code/C4TwDgpgBAIhBmBLAdhAJgaQiAzgHgBUA+KAXigG8BYAKCigG0MoUoBrbAe3igIF0AXLXr0cwAE4oA5lAgAPYBGRocUZgH4oqAG4RxUIXRHIArgFsARntkKlKtVE07rh+swC+tWqEhrknAHdkLFxCEnI4JFRMbHxiG0VlVWojegYAfRZkdi4efgEs+GsAVWEoTyNNUqMC53EAbi8aAHpm3gALRFUfaC6oYHboeQBDAGNgKBxhs2hh1QADDH8gkJx5gBooCxMJlAAbFAgFyMOY0OJ5rLEIYbQobig0CFG94clkGUQJuahhyYgwG9hop+uAIN4wVAAGLDRAHD5LQLBWJhMiUMpMLI5EAPfJlUQSaQJOyqDRaCC6fSuYzmKz6eSJexkuoGMoeYlJdGpRiZVgcHF5QSFEplCr0KplWoUvSNGi0FCKcTwMbQKGvKTJMpsZbINXDKQARgKFk4nD2N2QWp1eqkACZjabzcNLUYGHICmJ3lIhSazRaoAAfLQmPZ7QNQEzKBCnWUVCG+E7RABqwwOaGBiE4yNwaMT6FWeBtOCI8egiKCRbR5ez+CLJZoPWhsPhUmrlfIMLh0mrBbrtCAA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type DefinedKeys<T> = {
  [K in keyof T]:
    string extends K ? never :
    number extends K ? never :
  K }

type KnownKeys<T> = DefinedKeys<T> extends {
    [_ in keyof T]: infer U
  }
  ? U
  : never;

// This type is the exact same as `KnownKeys`, but inlines `DefinedKeys<T>` instead of declaring it as a separate type
type FailingKnownKeys<T> = {
  [K in keyof T]:
    string extends K ? never :
    number extends K ? never :
  K } extends {
    [_ in keyof T]: infer U
  }
  ? U
  : never;

interface Flags {
  knownFlag1: boolean
  knownFlag2: boolean
  [x: string]: boolean | null | undefined;
}

type DefinedValidationKeys = DefinedKeys<Flags>
type KnownFlags = KnownKeys<Flags>
type FailingKnownFlags = FailingKnownKeys<Flags>
```

### 🙁 Actual behavior

In the above code sample, the type `FailingKnownFlags` is `never` (the false branch of the ternary of `FailingKnownKeys<T>`), while `KnownFlags` correctly is `{knownFlag1: boolean, knownFlag2: boolean}`

### 🙂 Expected behavior

```
KnownKeys<T> === FailingKnownKeys<T>
```

They are the same declaration, just one being inline and the other with an explicitly extracted type.
Repository: pytorch
Issue: [docs] Better explain signature of toch.randn
Labels: module: docs,triaged

Currently it's `torch.randn(*size, *, out=None, dtype=None, layout=torch.strided, device=None, requires_grad=False) → Tensor`

In regular Python, calling it with randn((3, 4, 5)) would produce `size` tuple with a single element.

It should be more clear that all three syntaxes are equivalent:
```python
torch.randn( 3, 4, 5 )
torch.randn( size = (3, 4, 5) )
torch.randn( (3, 4, 5) )
```

Probably there is the same problem about other rand functions

cc @brianjo @mruberry
Repository: godot
Issue: [GodotPhysics] Ragdoll / PhysicalBone don't work on scaled models with Godot Physics
Labels: bug,confirmed,topic:physics,topic:3d

### Godot version

3.3.2.Stable

### System information

Windows 10, GLES3, GTX 980Ti

### Issue description

When using Godot Physics with Ragdolls / Physical bones on a model that's scaled, it immediately clears the scale back to 1.0 when starting the simulation, this is not an issue with Bullet.
In this scene the leg is scaled to 0.25, 0.25, 0.25.

Godot Physics:
![slTdyN6Qrr](https://user-images.githubusercontent.com/4955051/134511680-daf233fb-330f-48dc-b7a8-6c1a04816abb.gif)

Bullet:
![ZAtQKwBk5a](https://user-images.githubusercontent.com/4955051/134511914-a38d5c2c-f565-449a-ac19-51f2a0cd17b2.gif)


### Steps to reproduce

Open attached project and run the scene. Press space bar to start the simulation.

### Minimal reproduction project

[RagdollGodoPhysicsIssues.zip](https://github.com/godotengine/godot/files/7217843/RagdollGodoPhysicsIssues.zip)
Repository: godot
Issue: Ragdoll / Physical bone doesn't work with overlapping collision shapes on Godot Physics
Labels: bug,topic:physics,topic:3d

### Godot version

3.3.2.Stable

### System information

Windows 10, GLES3, GTX 980Ti

### Issue description

When setting up a ragdoll the collision shapes will often have some overlap at joints. This seems to work fine in Bullet, but in Godot Physics it causes a lot of jittering.

Godot Physics:
![7ddO4amjx0](https://user-images.githubusercontent.com/4955051/134514903-38501397-389e-4354-a615-18bd8d7dee83.gif)

Bullet:
![FwpBcHZeVg](https://user-images.githubusercontent.com/4955051/134515382-e95bd8d5-a055-4260-8a11-5bae6e0e477c.gif)

Now possibly this is expected and it's just a miracle that it works in Bullet, but if that's the case maybe it should specify in the manual that the collision shapes should not intersect? It is difficult to make a Ragdoll that covers a character well without intersecting the colliders.

### Steps to reproduce

Open the attached project and run it and press space bar to start the simulation

### Minimal reproduction project

[RagdollGodoPhysicsIssues2.zip](https://github.com/godotengine/godot/files/7217976/RagdollGodoPhysicsIssues2.zip)
Repository: storybook
Issue: Add AbortController support to long-running interaction events
Labels: feature request,addon: interactions

> As a user I want to be able to navigate through stories by keyboard (even when stories have long-running interactions), so that I can quickly browse through a Storybook.

For specific interactions that can be long running, e.g. `userEvent.type` with a `delay`, add `AbortController` support so that Storybook core can try to abort the play function instead of having to resort to a full page refresh #16142

=> Do this inside `testing-library`
Repository: storybook
Issue: Patch `userEvent.type` to stop typing if the target element has lost focus
Labels: bug,good first issue,help wanted,addon: interactions

> As a user, if I happen to click outside of the focused element as `userEvent.type` is executing, I want the typing to stop, so that it does not trigger random keyboard shortcuts in the Storybook UI

We should patch `userEvent.type` to check for focus before it fires a keyboard event, and to stop execution via an exception, in the case that the focus has changed.

We should probably also contribute this back to TestingLibrary

=> "In testing-library, empty the event queue when a blur or focus event is received" - @ghengeveld 

┆Issue is synchronized with this [Asana task](https://app.asana.com/0/1200510412866230/1201047348863322) by [Unito](https://www.unito.io)
Repository: pytorch
Issue: TorchScript can't handle super() in subclass of nn.Sequential
Labels: oncall: jit

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->
I'm trying to export a PyTorch model using TorchScript.
This model uses nn.Sequential modules that forward() an input List[Tensor] to output List[Tensor] (the nn.Sequential modules have been properly constructed with nn.Module's that input and output List[Tensor]).
However I gather we have a known JIT compiler issue relating to this situation as follows: https://github.com/pytorch/pytorch/issues/52588
Therefore following the workaround suggested by [ansley](https://github.com/ansley) I subclassed nn.Sequential and redefined forward() to accept/return a List[Tensor]
However I'm running into a second issue relating to calling super() in my subclass which looks like follows:-

	class SequentialWithListTensor(nn.Sequential):
		def __init__(self, *initList):
			super().__init__(*initList)

		def forward(self, x:List[torch.Tensor])->List[torch.Tensor]:
			result = torch.jit.annotate(List[torch.Tensor], [])
			result = super()(x)
			return result


## To Reproduce

Steps to reproduce the behavior:

1. Invoke TorchScript JIT compiler on above model

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->
Upon invoking torch.jit.script(), I get following error:-

	RuntimeError:
	cannot call a value of type 'Tensor':
	  File "ritm_interactive_segmentation\isegm\model\modeling\hrnet_ocr.py", line 171
		def forward(self, x:List[torch.Tensor])->List[torch.Tensor]:
			result = torch.jit.annotate(List[torch.Tensor], [])
			result = super()(x)
					 ~~~~~ <--- HERE
			return result

It just seems like super() is not properly defined in the subclass of nn.Sequential (the JIT compiler apparently does the default type inference to "Tensor"?).
## Expected behavior

<!-- A clear and concise description of what you expected to happen. -->
super() call in subclass should return correct reference to base class object (as seen by TorchScript compiler)

## Environment
	Collecting environment information...
	PyTorch version: 1.9.0+cpu
	Is debug build: False
	CUDA used to build PyTorch: Could not collect
	ROCM used to build PyTorch: N/A

	OS: Microsoft Windows 10 Enterprise
	GCC version: Could not collect
	Clang version: Could not collect
	CMake version: version 3.21.1
	Libc version: N/A

	Python version: 3.9 (64-bit runtime)
	Python platform: Windows-10-10.0.18363-SP0
	Is CUDA available: False
	CUDA runtime version: Could not collect
	GPU models and configuration: GPU 0: GeForce RTX 2070 with Max-Q Design
	Nvidia driver version: 456.87
	cuDNN version: Could not collect
	HIP runtime version: N/A
	MIOpen runtime version: N/A

	Versions of relevant libraries:
	[pip3] numpy==1.21.1
	[pip3] torch==1.9.0
	[pip3] torchvision==0.10.0
	[conda] Could not collect

## Additional context

<!-- Add any other context about the problem here. -->
Repository: godot
Issue: PhysicalBones are not alligned with skeleton when created
Labels: bug,topic:core,topic:editor,topic:3d

### Godot version

3.3.2.Stable

### System information

Windows 10, GLES3, GTX 980Ti

### Issue description

PhysicalBones are not alligned with skeleton when created.

![CgQ8xXDJKb](https://user-images.githubusercontent.com/4955051/134522685-c609650e-3963-4b15-8a1d-f780140babb8.gif)


### Steps to reproduce

Open attached project and open a new inherited scene of leg.glb. Select the skeleton and select Skeleton -> Create Physical Skeleton

### Minimal reproduction project

[RagdollGodoPhysicsIssues2.zip](https://github.com/godotengine/godot/files/7218337/RagdollGodoPhysicsIssues2.zip)
Repository: flutter
Issue: [camera] Video recording - initial lag/freeze on first record
Labels: platform-ios,a: quality,p: camera,package,has reproducible steps,P2,found in release: 2.5,found in release: 2.6,team-ios,triaged-ios

Flutter 2.2.3 • channel stable
camera: 0.9.2+2
device: iPhone 12 Pro Max iOS 14.8

When using the official camera example I am experiencing around 500ms of lag on first record after running the app. This results in a recording that has blank black frames in the beginning, or a frozen frame. I have experienced this in the official camera example and my own implementations in both debug and release builds.

prepareForVideoRecording() is being called and awaited prior to startVideoRecording

The lag and frame freeze is included in the final recorded video file which is the main issue. In this screen recording of the official example, you can see:
- I click button to begin recording, which results in major UI lag
- recording completes and saves, the preview in bottom right has a bunch of blank black frames in the beginning

https://user-images.githubusercontent.com/33461698/134526462-d3bdda34-3b36-4775-a818-8ae41c3b091d.MP4
Repository: terminal
Issue: Terminal crashes taking all processes attached with it if it loses gpu context
Labels: Resolution-Fix-Committed,Resolution-External,Issue-Bug,Severity-Crash,Product-Terminal,Tracking-External

### Windows Terminal version (or Windows build number)

Windows 11 10.0.22458.0, Terminal Preview 1.11.2421.0

### Other Software

AMD GPU Drivers, possibly others but dont have any to test

### Steps to reproduce

https://aka.ms/AAdvrbk is the Feedback Link pointing to the issue

Have Terminal doing things in the background involving a process that constantly writes to the terminal, like rclone or something else with verbose output
Trigger a gpu driver crash and let it recover


### Expected Behavior

Terminal to survive gpu context loss at least in a minimal way allowing the user to stop work safely and recover if necessary 

### Actual Behavior

Terminal will appear after recovery with a  frame and nothing but white as the window contents followed shortly by crashing completely. Any running processes in the terminal windows will die shortly after
Repository: PowerToys
Issue: FZ Crashing when moving windows between zones - redemp
Labels: Issue-Bug,Product-FancyZones,Severity-High

### Microsoft PowerToys version

0.45

### Running as admin

- [X] Yes

### Area(s) with issue?

FancyZones, FancyZones Editor

### Steps to reproduce

move a window into a fancy zone I created

### ✔️ Expected Behavior

I was expecting the window to snap in place

### ❌ Actual Behavior

windows error pop-up "fancy zones has crashed" 

when I restart the computer, all of my established fancy zones are gone. I reset them after that, and then when I move a few things into zones, it then crashes again.

I uninstalled completely, removed all temp files, etc... and re-installed, also tried on new windows install and the same issue occurred 

### Other Software

_No response_
Repository: rust
Issue: Adding a needless .into should produce a better error.
Labels: A-diagnostics,T-compiler

Suggested from [this question](https://stackoverflow.com/q/69303389/124486) on SO.

This code,

```rust
seq += rhs.into();
```

Will produce this error,

```rust
error[E0283]: type annotations needed
  --> src/sequence.rs:50:5
   |
19 | seq += rhs.into();
   |     ^^ ---------- this method call resolves to `T`
   |     |
   |     cannot infer type for type parameter `T`
   |
   = note: cannot satisfy `_: Into<u64>`
   = note: required because of the requirements on the impl of `AddAssign<_>` for `Sequence`
```

This can lead you down a rabbit hole. The right answer is far more simple: **remove the `.into()`**

```
seq += rhs;
```
I would like error to say (copied from SO),

> You have a double Into indirection. Since your type already implements `AddAssign<T> where T: Into<u64>`, then there is no need to add `.into()` to your right-hand member.

That's ideal. Alternatively it could just work. (I'm still kind of confused why it doesn't), but the solution is far easier and nicer than either,

    seq += u64::from(rhs);
    Into<u64>::into(rhs);

Lastly, providing the above syntax which is more complex but would otherwise solve the problem would be nice too.
Repository: rust
Issue: Unsatisfied HRTBs cause the compiler to suggest adding impossible bounds
Labels: A-diagnostics,T-compiler,D-incorrect,A-higher-ranked

Given the following code ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=978d9446191f7e77f30d41eea92ffcd0)):

```rust
trait Foo<'a> {}
impl<'a, T: 'a> Foo<'a> for T {}

trait Bar: for<'a> Foo<'a> {}
impl<T> Bar for T {}
```

The current output is:

```
error[E0311]: the parameter type `T` may not live long enough
 --> src/lib.rs:5:9
  |
5 | impl<T> Bar for T {}
  |      -  ^^^ ...so that the type `T` will meet its required lifetime bounds...
  |      |
  |      help: consider adding an explicit lifetime bound...: `T: 'a`
  |
note: ...that is required by this bound
 --> src/lib.rs:4:12
  |
4 | trait Bar: for<'a> Foo<'a> {}
  |            ^^^^^^^^^^^^^^^
```

Ideally there would be a way to say that `Bar` requires `Self` to implement `Foo<'a>` for any `'a` such that `Self: 'a`, however this is not possible. This case of the error can be fixed by additionally requiring `T: for<'a> Foo<'a>` when implementing `Bar`, however this will just shift the problem to whoever tries to use `Bar`. 

Anyway the help message is just wrong because `T` can't be restrained by `'a`, and trying `for<'a> T: 'a` just generates another identical error (which again suggest to bound `T` by `'a`). 

The suggestion also led me to write something like this ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=328332f623d0aa0a9d42c84a6f1fdeb6)):

```rust
trait Foo where for<'a> Self: 'a {}
```

On nightly and stable 1.54 (and older) the error message is pretty much the same the one already posted, the only difference with the other snippet is that I haven't found any workaround to make this compile.

Interestingly on stable 1.55 and beta it ICE, so it's technically a regression from stable to stable, however it's already fixed, so I don't think it's a big deal.