sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Code duplication in `foldingModel.ts`
Labels: debt,perf-bloat

Running `npx jscpd . -c ./.jscpd.json` over our sources with `.jscpd.json` containing:

```json
{
	"ignore": [
		"**/*.svg",
		"**/node_modules/**",
		"**/.git/**",
		"**/fixtures/**",
		"**/*.test.ts",
		"**/*.integrationTest.ts",
		"**/keybinding/test/**",
		"**/browser/keyboardLayouts/**",
		"**/out/**",
		"test/**",
		"extensions/**"
	],
	"reporters": ["console"],
	"minLines": 30
  }
```

Revealed:

```
Clone found (typescript):
 - src/vs/editor/contrib/folding/browser/foldingModel.ts [257:7 - 306:2] (49 lines, 543 tokens)
   src/vs/workbench/contrib/notebook/browser/viewModel/foldingModel.ts [87:2 - 136:20]
```
Repository: next.js
Issue: req.url not reliable in getServerSideProps on Vercel
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://github.com/ValentinH/getserversideprops-req-url

### To Reproduce

When using `req.url` from the  `getServerSideProps` context in an internationalised app (using [sub-path routing](https://nextjs.org/docs/pages/building-your-application/routing/internationalization#sub-path-routing)) deployed on Vercel, the locale is not included. However, there is one specific case where it is included and this is not consistent: when using dynamic segments.

1. https://getserversideprops-req-url.vercel.app/fr => `req.url: '/'` ✅ 
1. https://getserversideprops-req-url.vercel.app/fr/simple-page => `req.url: '/simple-page'` ✅
1. https://getserversideprops-req-url.vercel.app/fr/simple-nested/example => `req.url: '/simple-nested/example'` ✅
1. https://getserversideprops-req-url.vercel.app/fr/1 => `req.url: '/fr/1'` ❌


### Current vs. Expected behavior

`req.url` should never contain the locale prefix even if the route uses dynamic segments.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: 8.14.2
Relevant Packages:
  next: 14.1.1-canary.20 // Latest available version is detected (14.1.1-canary.20).
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Data fetching (gS(S)P, getInitialProps)

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

### Additional context

Using `resolvedUrl` from the `getServerSideProps` context is working fine.
Running the app in production mode (`next build && next start`), it's fine. This only happens when deployed on Vercel 🤔 
Maybe the answer to this is just "don't use req.url, it's unreliable" but it could be clearer in the docs.
Repository: vscode
Issue: "Open editors" should be able to sort in order of most recently viewed
Labels: feature-request,file-explorer

Currently VS Code (while editing a Dart project with Dart-Code) shows the open tabs in a list at top right, called "OPEN EDITORS". This is sorted in the same order as the open tabs.

It would be really awesome if there were an option button at the top left of this list that allowed the user to sort in different orders, specifically adding the ability for the user to view the tabs in order of most recently viewed, so that the most recently viewed editor is at the top of the list.

This would help a lot when a lot of tabs are open, and you can't remember which file you made an edit in a few tab switches ago.
Repository: pytorch
Issue: ValueError when setting tensor type to match MPS tensor type
Labels: triaged,module: mps

### 🐛 Describe the bug

There seems to be an inconsistency in type conversion behavior in PyTorch when using the Metal Performance Shaders (MPS) backend, as compared to CUDA and CPU backends. When attempting to set a tensor's type to match that of another tensor already on the MPS device, a ValueError is raised.

To reproduce the bug, the following code works as expected on CUDA and CPU devices:

```
import torch
a = torch.FloatTensor([1, 2, 3]).to(torch.device("cuda"))
b = torch.FloatTensor([4, 5, 6])
b.type(a.type())
```


However, when running similar code using the MPS device, it results in a ValueError:
```
import torch
a = torch.FloatTensor([1, 2, 3]).to(torch.device("mps"))
b = torch.FloatTensor([4, 5, 6])
b.type(a.type()) 
```

its error message received is as follows:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ValueError: invalid type: 'torch.mps.FloatTensor'


Expected behavior:
The type conversion should occur without raising an exception, similar to the behavior when using CUDA or CPU devices.




### Versions

PyTorch version: 2.1.2
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 14.3 (x86_64)
GCC version: Could not collect
Clang version: 15.0.0 (clang-1500.1.0.2.5)
CMake version: version 3.28.1
Libc version: N/A

Python version: 3.9.18 (main, Sep 11 2023, 08:38:23)  [Clang 14.0.6 ] (64-bit runtime)
Python platform: macOS-10.16-x86_64-i386-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz

Versions of relevant libraries:
[pip3] numpy==1.26.2
[pip3] onnx==1.15.0
[pip3] onnxruntime==1.16.3
[pip3] onnxscript==0.1.0.dev20240123
[pip3] torch==2.1.2
[pip3] torchaudio==2.1.2
[pip3] torchvision==0.16.2
[conda] numpy                     1.26.2                   pypi_0    pypi
[conda] torch                     2.1.2                    pypi_0    pypi
[conda] torchaudio                2.1.2                    pypi_0    pypi
[conda] torchvision               0.16.2                   pypi_0    pypi


cc @kulinseth @albanD @malfet @DenisVieriu97 @razarmehr
Repository: vscode
Issue: command actions (copy, paste, etc.) do no work on macOS
Labels: bug,webview

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: Version: 1.85.2 (Universal)
- OS Version: Darwin arm64 23.1.0

Steps to Reproduce:

1. [Install plugin](https://marketplace.visualstudio.com/items?itemName=bpmn-io.vs-code-bpmn-io)
2. Create a file with the extension .bpmn
3. Create a Task
4. Double click on the task (contenteditable)
5. Type text
6. ctrl+a or command+a does not work on macOs
6. ctrl+c or command+c does not work on macOs
6. ctrl+v or command+v does not work on macOs

See also the extension issue: https://github.com/bpmn-io/vs-code-bpmn-io/issues/92

Further relevant information:

- It works on windows
- It works on macOs in the browser
- This bug is only showing up for the combination macOS and vscode
- When typing inside a contenteditable area only the key up is recognized by the [key binding service](https://code.visualstudio.com/docs/getstarted/keybindings#_troubleshooting-keybindings)
Repository: godot
Issue: TileMap hangs on loading .tscn 
Labels: bug,needs testing,topic:2d,performance

### Tested versions

v4.2.stable

### System information

Apple M1 OS version: 14.3 (23D56)

### Issue description

I cannot load a tilemap almost 90% of the time. It can be either load and hang on adding properties on tileset or it will just not load or draw. TileMap is not that big ~200 tiles

### Steps to reproduce

Load project, load tilemap or edit tileset to some extent.

### Minimal reproduction project (MRP)

Project:

https://drive.google.com/drive/folders/1sLW4mquZPlHM91fCnOAgSpswB_qFb_mt?usp=sharing
Repository: go
Issue: cmd/compile/internal/types2, go/types: don't panic when calling under/underlying
Labels: NeedsInvestigation,compiler/runtime

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.21.6 darwin/arm64
</pre>

### Does this issue reproduce with the latest release?

yes

### 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='/Users/phaul/Library/Caches/go-build'
GOENV='/Users/phaul/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/phaul/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/phaul/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/phaul/.asdf/installs/golang/1.21.6/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/Users/phaul/.asdf/installs/golang/1.21.6/go/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.21.6'
GCCGO='gccgo'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/7f/z0kc3pxd6wz4540t2drzzlwm0000gn/T/go-build2303253187=/tmp/go-build -gno-record-gcc-switches -fno-common'
GOROOT/bin/go version: go version go1.21.6 darwin/arm64
GOROOT/bin/go tool compile -V: compile version go1.21.6
uname -v: Darwin Kernel Version 23.3.0: Wed Dec 20 21:33:31 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T8112
ProductName:		macOS
ProductVersion:		14.3
BuildVersion:		23D56
lldb --version: lldb-1500.0.200.58
Apple Swift version 5.9.2 (swiftlang-5.9.2.2.56 clang-1500.1.0.2.5)
</pre></details>

### What did you do?

The following code snippet panics the compiler:

<pre>
package main

type X Int

const (
  Invalid = X(iota)
  Call
  Int
)

func main () {

}
</pre>


### What did you expect to see?

Some errors reported

### What did you see instead?

<pre>
phaul@192 ~ % go build x.go
# command-line-arguments
<unknown line number>: internal compiler error: panic: nil underlying

Please file a bug report including a short program that triggers the error.
https://go.dev/issue/new
</pre>
Repository: deno
Issue: Test runner prints random 'output' and 'output end' between tests
Labels: bug,testing

Version: Deno 1.40.2

I'm pretty sure the tests aren't logging anything, because it only seems to happen when I run multiple test files with `--parallel`. If I either remove that flag or run only a single file. I'm not seeing any `------- output -------` messages logged.

<img width="918" alt="image" src="https://github.com/denoland/deno/assets/2737650/48e973e1-023b-4b49-9898-750a1920bf7e">

This screenshot was taken from [this GitHub Actions run](https://github.com/rendajs/Renda/actions/runs/7678123003/job/20927644574).
Repository: vscode
Issue: Quick open: Questionable focus related code with a `setTimeout`
Labels: debt,quick-pick

There is a `setTimeout` involved with changing `focus` which in general is questionable and has caused https://github.com/microsoft/vscode/issues/203111

https://github.com/microsoft/vscode/blob/1a37acbdf9c83ad21f68a48562346980a31ffa1b/src/vs/platform/quickinput/browser/quickInputController.ts#L184-L192

The code was introduced from 

https://github.com/microsoft/vscode/commit/fa155b782696c4d36eb2cdc10a36a1f29435f22d#diff-78408a8bfbdf8f8ae5c9671f4eb3be0d2b48dede183abaa6963a1264322877d8R112-R117
Repository: storybook
Issue: [Bug]: Storybook does not clean up url query params on component switch
Labels: bug,core,sev:S3

### Describe the bug

If one component sets some query params it does not clear them when switching between components. This causes odd side effects for me when having interaction tests and then want to switch between stories.


### To Reproduce

Create a component which uses a function like this:

```ts
export const router = {
  pushQuery: (queryParam: string) => {
    let newUrl = window.location.protocol + '//' + window.location.host + window.location.pathname;
    if (queryParam) {
      newUrl += `?${queryParam}`;
    }
    window.history.pushState({ path: newUrl }, '', newUrl);
  }
};
```

Then create two stories which would consume the query params and behave differently based on the params. Then you will see once a story has set a param it will be carried over to the next component. 

e.g. both components rely on the query param userId, fo instance to know what message to display. 

### System

```bash
Environment Info:

  System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (4) x64 Intel(R) Core(TM) i5-6600K CPU @ 3.50GHz
  Binaries:
    Node: 16.16.0 - /opt/nvm/versions/node/v16.16.0/bin/node
    npm: 8.11.0 - /opt/nvm/versions/node/v16.16.0/bin/npm
  Browsers:
    Chrome: 115.0.5790.98
  npmPackages:
    @storybook/addon-actions: ^7.4.0 => 7.4.0 
    @storybook/addon-essentials: ^7.4.0 => 7.4.0 
    @storybook/addon-interactions: ^7.4.2 => 7.4.2 
    @storybook/addon-links: ^7.4.0 => 7.4.0 
    @storybook/addon-mdx-gfm: ^7.4.0 => 7.4.0 
    @storybook/addons: ^7.4.0 => 7.4.0 
    @storybook/blocks: ^7.4.0 => 7.4.0 
    @storybook/jest: ^0.2.2 => 0.2.2 
    @storybook/react: ^7.4.0 => 7.4.0 
    @storybook/react-vite: ^7.4.0 => 7.4.0 
    @storybook/testing-library: ^0.2.1 => 0.2.1 
```
Repository: next.js
Issue: with mobx bug
Labels: examples

### Verify canary release

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

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 20.6.0
  npm: N/A
  Yarn: N/A
  pnpm: 8.11.0
Relevant Packages:
  next: 14.1.1-canary.20 // Latest available version is detected (14.1.1-canary.20).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A
```


### Which example does this report relate to?

with-mobx

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

Chrome 120.0.6099.225

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

_No response_

### Describe the Bug

When changing query parameters, multiple renderings occur, when the mobx state is hydrated

### Expected Behavior

hydration does not cause additional app renderings

### To Reproduce

link reproduce - https://codesandbox.io/p/github/realing29/next_mobx_ssr_hydration_bug/main?file=%2Fcomponents%2FStoreProvider.js%3A25%2C39
When changing the route from 1 to 2, more than 20 renderings occurred
![image](https://github.com/vercel/next.js/assets/36142237/8eeac531-4b7a-48a4-a567-2e13b1271742)

video
https://github.com/vercel/next.js/assets/36142237/87252a43-3e56-43b2-b8d6-b5a7115c9856

the current solution is to replace the initialize Store function with:

```jsx
function initializeStore(initialData = null) {
  const _store = store ?? new Store();

  const isFirstRenderRef = useRef(true);
  if (isFirstRenderRef.current) {
    _store.hydrate(initialData);
  }

  useEffect(() => {
    if (!isFirstRenderRef.current) {
      if (initialData) {
        _store.hydrate(initialData);
      }
    } else {
      isFirstRenderRef.current = false;
    }
  }, [_store, initialData]);


  if (typeof window === "undefined") return _store;

  if (!store) store = _store;
  return _store;
}
```
Repository: material-ui
Issue: [material-ui][TextField] Filled TextField Label has insufficient colour contrast when focused
Labels: design: material,component: text field,package: material-ui,design: material you

### Steps to reproduce

Link to live example: 
https://mui.com/material-ui/react-text-field/#basic-textfield

EDIT: Optionally, if testing the focus state of the Text Field is difficult, we can also use the one as the Select component here: https://mui.com/material-ui/react-select/#filled-and-standard-variants

Steps:
1. Focus on the Filled TextField
2. Check the input with any accessibility tools (I used both [Colour Contrast Analyzer](https://www.tpgi.com/color-contrast-checker/) and [Accessibility Insights for Web](https://accessibilityinsights.io/docs/web/overview/)


### Current behavior

![image](https://github.com/mui/material-ui/assets/58952185/4262728c-c774-49e7-9da8-8dc8d4976f18)

![image](https://github.com/mui/material-ui/assets/58952185/f55b2d8e-c3d1-4088-aa80-b60cbf3693bd)


### Expected behavior

Colour contrast passes accessibility tests.

### Context

The label on the default primary filled variant of the text field doesn't pass WCAG for the color contrast when the input is focused.
I'm not sure what's the best way to address this issue. We can either change the grey background for the filled variant of TextField or change the label colour when focused (it's set to the primary one now. If it's set to primary dark, it passes the tests).

### 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**: Filled TextField Label has insufficient colour contrast when focused
Repository: transformers
Issue: Adding CrossMAE
Labels: New model

### Model description

Hey,
the recently released [CrossMAE](https://crossmae.github.io/) seems like it would be a nice addition to transformers.

Basically the model improves MAE by using Cross-Attention instead of Self-Attention on the tokens and thereby decreasing the needed FLOPS quite significantly. At the same time it seems to be able to keep the performance of MAE or even improve it a bit.

Maybe there are already plans of integrating it @NielsRogge ?

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

Project Page: https://crossmae.github.io/
GitHub Repo: https://github.com/TonyLianLong/CrossMAE
Paper: https://arxiv.org/pdf/2401.14391.pdf
Repository: ant-design
Issue: Add `metadata` prop to FileUpload type
Labels: Inactive,unconfirmed

### What problem does this feature solve?

We need a way to store arbitrary metadata as part of the file object, but the FileUpload type does not provide a prop for this. This adds an optional prop to allow devs to append and associate additional file data to a file object inside the file list of the Upload component.

### What does the proposed API look like?

```diff
diff --git a/node_modules/antd/es/upload/interface.d.ts b/node_modules/antd/es/upload/interface.d.ts
index b6032f3..4253b44 100644
--- a/node_modules/antd/es/upload/interface.d.ts
+++ b/node_modules/antd/es/upload/interface.d.ts
@@ -27,6 +27,7 @@ export interface UploadFile<T = any> extends ProgressAriaProps {
     type?: string;
     xhr?: T;
     preview?: string;
+    metadata?: any;
 }
 export interface InternalUploadFile<T = any> extends UploadFile<T> {
     originFileObj: RcFile;
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: ERR Assertion Failed: Error: Assertion Failed
Labels: bug,diff-editor

Version: 1.86.0-insider
Commit: 5d344004f839677def958534b58e854a9ae26fd0
Date: 2024-01-26T23:09:31.910Z
Electron: 27.2.3
ElectronBuildId: 26495564
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.3.0

```
ERR Assertion Failed: Error: Assertion Failed
    at I (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12:8729)
    at new r (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:693:52594)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:693:46574
    at Array.map (<anonymous>)
    at P (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:693:46512)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:693:49514
    at w (vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:85:11238)
    at vscode-file://vscode-app/Applications/Visual%20Studio%20Code%20-%20Insiders.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:693:49509
```
Repository: storybook
Issue: [Bug]: HMR issues on renaming stories
Labels: bug,sev:S2

### Describe the bug

originally filed [here](https://github.com/storybookjs/storybook/discussions/25687#discussioncomment-8245240)

**Project:** MealDrop
**Version:** 8.0.0-alpha.14
**Bug/feedback:**

When renaming the story file of which you are visiting, a lot of weird things happen, it's best described in a video:

https://github.com/storybookjs/storybook/assets/1671563/540e03b8-82bf-4893-a0e3-adfe8058cf3f

The issues which happen are:
1 - The story of which you renamed somehow changes order and goes to the bottom of the list (there is no storySort being used)
2 - An `importers[path] is not a function` error is flashed in the screen:
<img width="349" alt="image" src="https://github.com/storybookjs/storybook/assets/1671563/5c5dc9c3-40c1-4252-a6fb-da45a5f9768f">

3 - The UI goes into a funky state where there's some sort of negative margin and the toolbar is unreachable (until you close the addon panel, which is not really closed)

### To Reproduce

1. Go to https://github.com/yannbf/mealdrop/tree/storybook/8.0.0
2. Visit a story
3. Rename its story file to something else (e.g. add an A at the end)

### System

_No response_

### Additional context

_No response_
Repository: PowerToys
Issue: After exchang alt and ctrl,  use alt + tab open the app switcher, when keep alt & tab down use left or right, ensue every keymap crash
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.77.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

![image](https://github.com/microsoft/PowerToys/assets/5457239/453f5126-d770-4960-8cbb-0be6fa2bb46e)

1. use alt + tab open window switcher
2. keep alt + tab key down
3. press down left or right
4. the window switcher disapper and keyborad Manager doesn't work

but i found a repair method

1. ctrl + alt + del 
2. esc

then keyboard manage works again






### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_