sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: The feature gate csiMigrationRBD should be CSIMigrationRBD
Labels: kind/bug,sig/storage,lifecycle/frozen,needs-triage

### What happened?

I'm trying CSI RBD migration feature in 1.23. 
Found if set --feature-gates=CSIMigrationRBD=true to kube-controller-manager  or CSIMigrationRBD: true to kubelet config. 
Error  "unrecognized feature gate: CSIMigrationRBD" showed up.

Need to set to --feature-gates=csiMigrationRBD=true.

It is "CSIMigrationRBD" in [feature-gates](https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/) and in [1.23 release page](https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.23.md#feature)

Looks like shall update to CSIMigrationRBD in this line.
https://github.com/kubernetes/kubernetes/blob/935052185ccb3a9dc5d2f33a893df2c8e9eeb890/pkg/features/kube_features.go#L342


### What did you expect to happen?

CSIMigrationRBD shall work.

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

1. Adding the feature flag to the kube-controller-manager --feature-gates=CSIMigrationRBD=true
2. Adding the feature flag to the kubelet config: featureGates: CSIMigrationRBD: true
3. Restart kubelet

### Anything else we need to know?

_No response_

### Kubernetes version

1.23.1

### Cloud provider

vcenter

### 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 and version (if applicable)

<details>

</details>


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

<details>

</details>
Repository: flutter
Issue: Allow Customization of splash and overlay color in PopupMenuItem.
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

Hi guys!
My client asks me to change splash/overlay color of exact item in a menu.

`PopupMenuItem` contains `InkWell` inside. Please make the settings of the internal `InkWell` outside to the `PopupMenuItem` properties so I can customize menu entry's `InkWell`.

Thanks.
Repository: godot
Issue: Vulkan: SSIL does not force the editor to redraw for one frame as it should
Labels: bug,enhancement,topic:rendering,topic:editor,topic:3d

*Related to https://github.com/godotengine/godot/issues/54892.*

### Godot version

4.0.dev (b6b81e800)

### System information

Fedora 34, GeForce GTX 1080 (NVIDIA 495.46)

### Issue description

SSIL does not force the editor to redraw for one frame. However, it should do that since SSIL operates with a one-frame delay. This also breaks SSIL rendering after resizing the project window when low-processor mode is enabled in the Project Settings.

This does not occur for more than one frame if **Update Continuously** is enabled in the Editor Settings (or if low-processor mode is disabled in the Project Settings).

***Epilepsy warning:** video below contains some flashing when the window is resized.*

https://user-images.githubusercontent.com/180032/149147667-bf901d63-5d79-45da-8dbd-f6d6722d3fb0.mp4




### Steps to reproduce

- Add some MeshInstance3Ds and a DirectionalLight3D so you can see light bounce around once SSIL is enabled.
- Add a WorldEnvironment node with a new Environment resource.
- Enable SSIL in the Environment resource.
- Resize the editor window. Observe that SSIL will stop working until you move the camera in the 3D editor.

### Minimal reproduction project

[test_ssil_3.zip](https://github.com/godotengine/godot/files/7854794/test_ssil_3.zip)
Repository: pytorch
Issue: support setting `keepdim` without setting `dim`
Labels: triaged,module: python array api

The [array API specification stipulates](https://data-apis.org/array-api/latest/API_specification/utility_functions.html#all-x-axis-none-keepdims-false) that only the first argument in `all` is positional only. The other two, `dim` and `keepdim` need to be independently usable.

```python
>>> t = torch.full((2, 3), True)
>>> torch.all(t)
tensor(True)
>>> torch.all(t, dim=1)
tensor([True, True])
>>> torch.all(t, dim=1, keepdims=True)
tensor([[True],
        [True]])
>>> torch.all(t, keepdims=True)
TypeError: all() received an invalid combination of arguments - got (Tensor, keepdims=bool), but expected one of:
 * (Tensor input, *, Tensor out)
 * (Tensor input, int dim, bool keepdim, *, Tensor out)
 * (Tensor input, name dim, bool keepdim, *, Tensor out)
```

The same applies to the following other ops:

- `any`
- `max`
- `mean`
- `prod`
- `std`
- `sum`
- `var`

This issue is related to #70914, which likely uses the same underlying functionality to parse inputs.

cc @mruberry @rgommers @pmeier @asmeurer @leofang @AnirudhDagar @asi1024 @emcastillo @kmaehashi
Repository: pytorch
Issue: axis to dim remapping is not working for flip and roll
Labels: triaged,module: python array api

Although not documented, the Python interface of PyTorch ops internally maps `axis` keywords to `dim` for `numpy` and in turn also for array API compliance:

```python
>>> t = torch.empty(1, 2, 1, 3)
>>> t.squeeze(dim=2).shape
torch.Size([1, 2, 3])
>>> t.squeeze(axis=2).shape
torch.Size([1, 2, 3])
```

This mapping does not work for the following ops:

| op     | array API parameter | PyTorch parameter |
|--------| --- | --- |
| `flip` | [`axis`](https://data-apis.org/array-api/latest/API_specification/manipulation_functions.html#id3) | [`dims`](https://pytorch.org/docs/master/generated/torch.flip.html) |
| `roll` | [`axis`](https://data-apis.org/array-api/latest/API_specification/manipulation_functions.html#roll-x-shift-axis-none) | [`dims`](https://pytorch.org/docs/master/generated/torch.roll.html) |

cc @mruberry @rgommers @pmeier @asmeurer @leofang @AnirudhDagar @asi1024 @emcastillo @kmaehashi
Repository: flutter
Issue: ☂️ Rewrite RefreshIndicator to increase fidelity
Labels: platform-android,framework,f: material design,a: fidelity,P3,team-design,triaged-design

RefreshIndicator implementation should be rewritten, in particular to align with Android's logic, but there are also other issues which are listed below.

Use these sources to rewrite the RefreshIndicator and tune its fidelity

* [Android RefreshIndicator analogue](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:swiperefreshlayout/swiperefreshlayout/src/main/java/androidx/swiperefreshlayout/widget/SwipeRefreshLayout.java;l=1136?q=swiperefreshlayout.java)
* [Android RefreshProgressIndicator analogue](https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:swiperefreshlayout/swiperefreshlayout/src/main/java/androidx/swiperefreshlayout/widget/CircularProgressDrawable.java;l=1?q=CircularProgressDrawable.java)

The comparison app https://github.com/nt4f04uNd/refresh_indicator_overlay can be used to check the results

Known issues that should be addressed are:
* https://github.com/flutter/flutter/issues/94933
* https://github.com/flutter/flutter/issues/6052
* https://github.com/flutter/flutter/issues/94595
* `_kDragContainerExtentPercentage` (the fraction of vieport the indicator will move from the user's drag) should probably be 0.5, if it will remain after fixing https://github.com/flutter/flutter/issues/94595
* Any extra friction that is applied to scroll physics affects the extent the RefreshIndicator will use, this can be avoided by using drag delta directly.
* There should be an arrowhead animation before going indeterminate
* Indicator should allow being dragged again when it is cancelled, currently you have to wait until the animation ends
Repository: pytorch
Issue: Lack of type check in `nn.functional` APIs
Labels: module: nn,triaged,enhancement

### 🐛 Describe the bug

Some `nn.functional` APIs like `torch.nn.functional.relu` and `torch.nn.functional.max_pool1d` do not check the type of argument. For example, `torch.nn.functional.relu(input, inplace=False)`. `inplace` is a bool argument but it can be fed a string value

```python
torch.nn.functional.relu(a, "aaaa")
# succeed
```

Another example

```python
tensor = torch.rand([2, 2])
torch.nn.functional.max_pool1d(tensor, 1, return_indices="aaa")
# succeed
```

where the type of `return_indices` is bool

### Versions

pytorch: 1.10.1

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345
Repository: PowerToys
Issue: Always On Top keeps windows on top even if switched off again
Labels: Issue-Bug,Product-Always On Top,Status-Reproducible

### Microsoft PowerToys version

0.53.1

### Running as admin

- [ ] Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce

Enable AOT, add some windows on top.
Disable AOT, 
go back to work

### ✔️ Expected Behavior

Ex-on-top windows behave like all other open windows and disappear behind currently active window

### ❌ Actual Behavior

ex on-top windows keep staying in front of current active window, have to move it to other screen.
I have to apply a work-around: I then have to re-enable AOT, find all windows that are been set to be on top and then I have to switch it off for each, and then disable AOT again.

### Other Software

_No response_
Repository: bitcoin
Issue: net: signed-integer-overflow in LocalServiceInfo
Labels: Bug,P2P

`LocalServiceInfo` is defined as:
https://github.com/bitcoin/bitcoin/blob/16781e1bc9f8ffc721ebea73434e0066957bc959/src/net.h#L228-L231
`nScore` is of type int which is signed and is 4 bytes wide on my machine (clang-12). `nScore` is incremented by `SeenLocal` during the version handshake here:
https://github.com/bitcoin/bitcoin/blob/16781e1bc9f8ffc721ebea73434e0066957bc959/src/net_processing.cpp#L2603-L2606
So I believe this UB is peer-triggerable (I don't think the compiler can detect this), but I don't think it's a big deal unless there's a node out there compiled with UBSAN or ftrapv. It seems like `nScore` can just be changed to int64_t.
Repository: opencv
Issue: Video Writer taking too long to write a single frame
Labels: question (invalid tracker),incomplete

Hi, M using cv2.videowriter to write frames to a MP4 cobtainer, each out.write(frame) taking about 0.37sec  to process. 
Is this the expected behavior to take this long?? 
Using
- OpenCV => 4.2
-platform - debian
Repository: react
Issue: [DevTools Bug]: Devtools script served over insecure connection causing issues with local https server.
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://github.com/malewis5/payment-sandbox

### Repro steps

Hi React Team,
I am trying to use the devtools to debug in Safari. I'm working with Apple Pay so I'm using ngrok to create a secure tunnel. When I visit the ngrok domain Safari throws a warning stating: 
```[blocked] The page at https://revcommerce.ngrok.io/ was not allowed to run insecure content from http://192.168.132.58:8097/.```

Repro steps: 
1. Clone and install dependencies.
2. Run using ngrok or other method for https.
3. Visit the page using **Safari**.
4. Inspect the page and you'll see the warning.

Thank you guys.

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: pytorch
Issue: Move torch::deploy tests to their own workflow job
Labels: high priority,triaged,module: deploy

Right now, the torch::deploy tests piggyback off some random linux gpu job. This is confusing (one linux gpu job is different from all the others) and breaks sometimes. @malfet suggested we split this into its own job that just runs deploy test, to make thing s clearer. https://github.com/pytorch/pytorch/pull/70203 is a good blueprint.

cc @ezyang @gchanan @zou3519 @wconstab
Repository: pytorch
Issue: 1.10.11 fails to compile libtorch_cpu with -fopenmp
Labels: module: build,triaged,module: undefined reference

### 🐛 Describe the bug

When compiling 1.10.1 with GCC 11.2.0, it goes through, but it seems that in some point the `-fopenmp` is missing, so libtorch_cpu.so ends up without the right symbols.

```  File "/dev/shm/strube1/juwelsbooster/PyTorch/1.10.1/gcccoremkl-11.2.0-2021.4.0-CUDA-11.5/pytorch/test/run_test.py", line 15, in <module>
    import torch
  File "/tmp/eb-sggdkfuw/tmp_f29p14f/lib/python3.9/site-packages/torch/__init__.py", line 197, in <module>
    from torch._C import *  # noqa: F403
ImportError: /tmp/eb-sggdkfuw/tmp_f29p14f/lib/python3.9/site-packages/torch/lib/libtorch_cpu.so: undefined symbol: __kmpc_global_thread_num
  >> command completed: exit 1, ran in 00h00m01s
```

On `build.ninja` I see 

```
LANGUAGE_COMPILE_FLAGS = -O2 -ftree-vectorize -march=native -fno-math-errno -fopenmp -fPIC -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREA\
DPOOL -fopenmp -DNDEBUG -DUSE_KINETO -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DSYMBOLICATE_MOBILE_DEBUG_HANDLE -DEDGE_PROFILER\
_USE_KINETO -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknow\
n-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict\
-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -W\
no-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-\
math -Werror=format -Werror=cast-function-type -Wno-stringop-overflow -DHAVE_AVX512_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION -O3 -DNDEBUG -DNDEBUG
```

So it's there.

I don't know where else to look for to make sure it gets it. 

### Versions

1.10.1

cc @malfet @seemethere
Repository: rust
Issue: Indefinitely hangs on hidden "overflow evaluating the requirement" errors when the complexity is too high.
Labels: T-compiler,C-bug,I-hang

### Minimal Example

#### main.rs
```Rust
use std::pin::Pin;
use futures::Future;

trait MyTrait {
    type Value;
    type Future;
}

impl<S> MyTrait for &S where S: MyTrait {}

struct MyStruct<S>;

impl MyTrait for MyStruct<dyn MyTrait<
    Value = usize,
    Future = Pin<Box<dyn Future<Output = Option<usize>>>>,
>>
    where Self::Future: 'static
{
    type Value = usize;
    type Future = Pin<Box<dyn Future<Output = Option<Self::Value>>>>;
}

fn main() {}
```

#### Cargo.toml
```Rust
[package]
name = "rust-playground"
version = "0.1.0"
edition = "2021"

[dependencies]
futures = "0.3.14"
```

### Meta
`rustc --version --verbose`:
```
rustc 1.59.0-nightly (0fb1c371d 2021-12-06)
binary: rustc
commit-hash: 0fb1c371d4a14f9ce7a721d8aea683a6e6774f6c
commit-date: 2021-12-06
host: aarch64-apple-darwin
release: 1.59.0-nightly
LLVM version: 13.0.0
```

### Error output

It doesn't produce error output, the compiler hangs indefinitely. However, simplifying the example in any way seems to uncover a bunch of "overflow evaluating the requirement" errors. For example, by commenting out the first implementation of the trait, one of the errors is:

```
error[E0275]: overflow evaluating the requirement `<MyStruct<(dyn MyTrait<Value = usize, Future = Pin<Box<(dyn futures::Future<Output = Option<usize>> + 'static)>>> + 'static)> as MyTrait>::Future == _`
  --> src/main.rs:13:1
   |
13 | / impl MyTrait for MyStruct<dyn MyTrait<
14 | |     Value = usize,
15 | |     Future = Pin<Box<dyn Future<Output = Option<usize>>>>,
16 | | >>
...  |
20 | |     type Future = Pin<Box<dyn Future<Output = Option<Self::Value>>>>;
21 | | }
   | |_^
   |
note: required because of the requirements on the impl of `MyTrait` for `MyStruct<(dyn MyTrait<Value = usize, Future = Pin<Box<(dyn futures::Future<Output = Option<usize>> + 'static)>>> + 'static)>`
  --> src/main.rs:13:6
   |
13 |   impl MyTrait for MyStruct<dyn MyTrait<
   |  ______^^^^^^^_____^
14 | |     Value = usize,
15 | |     Future = Pin<Box<dyn Future<Output = Option<usize>>>>,
16 | | >>
   | |__^
```
Repository: flutter
Issue: Remove retry logic from flutter/plugin FTL tooling
Labels: team,p: tooling,package,team-ecosystem,P3,triaged-ecosystem

See https://github.com/flutter/flutter/issues/95063 for background. Once we understand and have addressed the source of the FTL flake (in particular the random "timeout" results), we should eliminate the retry logic so that we're not masking flake and making test runs longer.
Repository: go
Issue: encoding/asn1: Marshal rejects encoding *T even if T is encodeable
Labels: NeedsInvestigation

https://go.dev/play/p/Aj7m_EiK1EX

```go
package main

import (
	"encoding/asn1"
	"fmt"
)

func main() {
	b, e := asn1.Marshal(struct{}{})
	fmt.Printf("%x, %s\n", b, e)
	b, e = asn1.Marshal(&struct{}{})
	fmt.Printf("%x, %s\n", b, e)
}
```

### What did you expect to see?

Equal values for both prints.

### What did you see instead?

```
3000, %!s(<nil>)
, asn1: structure error: unknown Go type: *struct {}
```

Ideally, Marshal (and arguably Unmarshal) should recurse through pointers as they do interfaces. Of course, encoding/asn1 is... not really the best ASN.1 library, so maybe we should put a comment on it saying to use crypto/cryptobytes and call it a day.
Repository: go
Issue: cmd/fix: timeout in TestRewrite on netbsd builders
Labels: OS-NetBSD,NeedsInvestigation

```
goroutine 30 [syscall]:
syscall.Syscall6(0x4286, 0x8493abc, 0x0, 0x84ba4b0, 0x0, 0x0, 0x0)
	/tmp/workdir/go/src/syscall/asm_unix_386.s:43 +0x5 fp=0x8493a68 sp=0x8493a64 pc=0x80afb25
syscall.wait4(0x4286, 0x8493abc, 0x0, 0x84ba4b0)
	/tmp/workdir/go/src/syscall/zsyscall_netbsd_386.go:34 +0x5b fp=0x8493aa0 sp=0x8493a68 pc=0x80ae63b
syscall.Wait4(0x4286, 0x8493ae0, 0x0, 0x84ba4b0)
	/tmp/workdir/go/src/syscall/syscall_bsd.go:144 +0x3b fp=0x8493ac4 sp=0x8493aa0 pc=0x80ae3fb
os.(*Process).wait(0x84b49f0)
	/tmp/workdir/go/src/os/exec_unix.go:43 +0x82 fp=0x8493af8 sp=0x8493ac4 pc=0x80c45a2
os.(*Process).Wait(...)
	/tmp/workdir/go/src/os/exec.go:132
os/exec.(*Cmd).Wait(0x84c6580)
	/tmp/workdir/go/src/os/exec/exec.go:507 +0x4d fp=0x8493b3c sp=0x8493af8 pc=0x812cbfd
os/exec.(*Cmd).Run(0x84c6580)
	/tmp/workdir/go/src/os/exec/exec.go:341 +0x43 fp=0x8493b4c sp=0x8493b3c pc=0x812bfe3
cmd/fix.typecheck.func1(0x84e2080, 0x8493dc4)
	/tmp/workdir/go/src/cmd/fix/typecheck.go:174 +0x38c fp=0x8493c78 sp=0x8493b4c pc=0x8176bcc
cmd/fix.typecheck(0x8493dc4, 0x84e2080)
	/tmp/workdir/go/src/cmd/fix/typecheck.go:207 +0x13b fp=0x8493d6c sp=0x8493c78 pc=0x8175d7b
cmd/fix.typefix(0x84e2080, 0x81bc910)
	/tmp/workdir/go/src/cmd/fix/cftype.go:43 +0xa1 fp=0x8493e9c sp=0x8493d6c pc=0x816f7a1
cmd/fix.eglfixDisp(0x84e2080)
	/tmp/workdir/go/src/cmd/fix/egltype.go:30 +0x25 fp=0x8493eac sp=0x8493e9c pc=0x8170945
cmd/fix.parseFixPrint(0x851f860, 0x81bc914, {0x84b0c78, 0x13}, {0x84e40c0, 0x3d}, 0x1)
	/tmp/workdir/go/src/cmd/fix/main_test.go:66 +0x339 fp=0x8493f38 sp=0x8493eac pc=0x817d129
cmd/fix.TestRewrite.func1(0x851f860)
	/tmp/workdir/go/src/cmd/fix/main_test.go:122 +0x2e4 fp=0x8493f9c sp=0x8493f38 pc=0x817d704
testing.tRunner(0x851f860, 0x840c678)
	/tmp/workdir/go/src/testing/testing.go:1440 +0x10d fp=0x8493fe4 sp=0x8493f9c pc=0x80ff98d
testing.(*T).Run.func1()
	/tmp/workdir/go/src/testing/testing.go:1487 +0x28 fp=0x8493ff0 sp=0x8493fe4 pc=0x8100768
runtime.goexit()
	/tmp/workdir/go/src/runtime/asm_386.s:1311 +0x1 fp=0x8493ff4 sp=0x8493ff0 pc=0x80a72b1
created by testing.(*T).Run
	/tmp/workdir/go/src/testing/testing.go:1487 +0x36e
```

`greplogs --dashboard -md -l -e '(?ms)panic: test timed out.*^cmd/fix\.TestRewrite'`

[2022-01-12T16:50:38-83bfdb6/netbsd-386-9_0-n2](https://build.golang.org/log/4b89c1c3924622b542b1d02328b7223ede23227d)
[2021-10-22T00:57:18-9ff91b9/netbsd-arm-bsiegert](https://build.golang.org/log/73a84fec9a58f4da36103a74a2232d630b7f25d9)
[2021-04-08T02:17:20-a8e5553/netbsd-386-9_0](https://build.golang.org/log/d573accc40f86748b9b36928eb64f6c2ff3743c9)
[2020-10-26T17:26:23-a5088e7/freebsd-amd64-race](https://build.golang.org/log/2d3ea23e6e04c1bdf851d1309a12536299ba4ae7)
Repository: TypeScript
Issue: Bad parsing behaviour for generic arrow type arguments in class heritage / JSX open element
Labels: Bug,Help Wanted

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

shift left
type arguments
<<

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is a crash
- This changed between versions ______ and _______
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about ____ Generics _____
- I was unable to test this on prior versions because _______

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.6.0-dev.20220112#code/PTAEDkHtQBwQwE4GcCmoUIZBA6AUABQDGANnEkugB4AuKAdgCaUBmBAlADyicAqAfASoAuUL3agAvPzEyA3gF92AbjycAwpAC2MSPQY1ufQSLETps0MH6q8IUAAVEqdJmz5iZCtTpNWHTmMhUXEpGQFQRRU1TR09A0CBYLMwy2tlIA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
// No parse error.
(class extends f()< <T>(x: T) => T> {});
<Component< <T>(x: T) => T> />;

// Parse error.
(class extends f()<<T>(x: T) => T> {});
<Component<<T>(x: T) => T> />;
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->
Parsing error.

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->
No parse error. They are equivalent.

### Additional Info

Found this issue when working on a similar fix to Babel (https://github.com/babel/babel/pull/14145). This issue is a follow-up to #23996. /cc @Kingwl since you have fixed that issue.