sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/cgo: generated code uses aliases even in modules using Go older than 1.9
Labels: help wanted,NeedsFix,compiler/runtime,BugReport

### Go version

go version devel go1.23-722d59436b Thu May 16 02:00:26 2024 +0000 linux/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/dominikh/.cache/go-build'
GOENV='/home/dominikh/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/dominikh/prj/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/dominikh/prj'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/home/dominikh/prj/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/dominikh/prj/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.23-722d59436b Thu May 16 02:00:26 2024 +0000'
GODEBUG=''
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/tmp/foo/go.mod'
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 -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1611460511=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

Try to `go build`

```
-- foo.go --
package pkg

// #include <stdlib.h>
import "C"

func foo() {
	C.malloc(0)
}
-- go.mod --
module example.com

go 1.0
```

### What did you see happen?

```
# example.com
$WORK/b001/_cgo_gotypes.go:23:6: type alias requires go1.9 or later (-lang was set to go1; check go.mod)
```

### What did you expect to see?

No failure.

I'm mostly filing this for the sake of documentation, as it's probably not worth fixing. I don't think it negatively impacts any real projects. Any 1.0 module can upgrade to 1.9 (or 1.21, for that matter) without risking backwards incompatible changes. Additionally, any code base targeting a Go version older than 1.9 is unlikely to be a Go module in the first place.
Repository: create-react-app
Issue: Contribution Inquiry!
Labels: needs triage

Hi  Paul!

I'm interested in contributing to your repository CREATE-REACT-APP. Can I start working on it?

Thanks,
Julieth B
Repository: ant-design
Issue: Badge 徽标数 设置了color时 count为0时 本该消失，但仍显示小红点
Labels: help wanted,Inactive,unconfirmed

### Reproduction link

[https://codepen.io/kongdemin/pen/QWRdRKW?editors=1010](https://codepen.io/kongdemin/pen/QWRdRKW?editors=1010)

### Steps to reproduce

<Badge count={0} />
<Badge color="red" count={0} />

### What is expected?

设置color后，为0时消失

### What is actually happening?

设置color后，为0时消失

| Environment | Info |
| --- | --- |
| antd | 5.17.4 |
| React | 18 |
| System | mac |
| Browser | 谷歌 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: When inputting Japanese characters using TextField and confirming, the characters are duplicated.
Labels: a: text input,platform-mac,a: internationalization,a: desktop,has reproducible steps,P2,team-text-input,triaged-text-input,found in release: 3.22,found in release: 3.23

### Steps to reproduce

When using TextField to input Japanese, part of the characters after conversion are duplicated. For example, entering "日本語を入力します" (inputting Japanese) and confirming with the Enter key results in "日本語を入力します入力します" (inputting Japanese inputting Japanese) with part of the text duplicated.

1. Open a Flutter app containing a TextField widget.
2. Focus on the TextField and input "日本語を入力します" (inputting Japanese).
3. Convert the input to kanji.
4. Confirm the input by pressing the Enter key.

Flutter Version: 3.22.1
Platform: macOS
Development Environment: macOS Sonoma

### Expected results

After confirmation, the TextField should display the input without any duplication.

### Actual results

After confirmation, part of the input is duplicated in the TextField.

### Code sample

...
@override
Widget build(BuildContext context) {
  return TextField();
}

### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>

https://github.com/flutter/flutter/assets/83323382/0fea9dba-1913-481d-b20b-bca663b846db
Repository: ant-design
Issue: Colorpicker dragging too many times will be banned
Labels: Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/react-18-v56q5o?file=%2Fsrc%2FApp.js%3A7%2C43)

### Steps to reproduce

Drag the color panel for 10s continuously, let go, and drag again, you can see that the mouse pointer displays disabled, and you cannot drag at this time.

### What is expected?

Can drag and drop normally no matter how it is operated

### What is actually happening?

Drag the color panel for 10s continuously, let go, and drag again, you can see that the mouse pointer displays disabled, and you cannot drag at this time.

| Environment | Info |
| --- | --- |
| antd | 5.17.4 |
| React | 18.2.0 |
| System | windows10 |
| Browser | Edge 125.0.2535.67  |

---
But i can't irreproducible in M2 MacOS.

You can see



<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: AnimationTree fails resolving track on node with unique name (%)
Labels: bug,needs testing,topic:animation

### Tested versions

4.3.dev.custom build master today

### System information

window10 gd4.3.dev.custom build

### Issue description

 scene\animation\animation_mixer.cpp:663 - AnimationMixer: 'anim/unarmed-swim-idle', couldn't resolve track:  '%GeneralSkeleton:RightUpperLeg'. This warning can be disabled in Project Settings. (User)
 
 
![image](https://github.com/godotengine/godot/assets/33251075/7d1ad54a-c707-4936-a06c-093a40eb6776)
![image](https://github.com/godotengine/godot/assets/33251075/99b6530d-6946-4a30-ade7-b305f1bda451)

To make this node reusable by multiple different model scenes, I made it a separate scene and set an empty skeleton and animationplayer with %naming, the animationplayer loads external animation lib so it can be used for animation tree node editing

However, this would trigger an error and it takes a long time to load every time.


### Steps to reproduce

create A scene import the glb with animation player,and create a animationtree for it.then save the animation tree as a branch scene.

### Minimal reproduction project (MRP)

1.open player/roles/male_warrior/MaleWarrior.tscn
remove animationtree node
reinstance a RoleAnimationTree scene on it .and see the error

2.open assets/models/male_warrior/male_warrior.glb
select load pose to use external animlib
and select assets/anim.res, see another error(can not pick bindbones animlib.Even man.glb and male_warrior.glb its the same bone map)
Repository: node
Issue: `DOMException`s do not work with `v8.serialize()`
Labels: v8 module,web-standards

### Version

v22.1.0

### Platform

`Linux ether-laptop 6.5.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 26 11:23:57 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux`

### Subsystem

`node:v8`

### What steps will reproduce the bug?

```js
import {serialize, deserialize} from 'node:v8';

const error = AbortSignal.abort().reason;
console.log(error instanceof DOMException); 
// true
console.log(error);
// DOMException [AbortError]: This operation was aborted
//     at new DOMException (node:internal/per_context/domexception:53:5)
//     at AbortSignal.abort (node:internal/abort_controller:205:14)
//     at ...

const clonedError = deserialize(serialize(error));
console.log(clonedError instanceof DOMException); 
// false
console.log(clonedError);
// {}
```

### How often does it reproduce? Is there a required condition?

Always.

### What is the expected behavior? Why is that the expected behavior?

A `DOMException` should be serializable/deserializable like other error instances.

### What do you see instead?

Serializing/deserializing with v8 turns it into an empty plain object.

### Additional information

Related: `structuredClone(domException)` returns an empty plain object, which is probably the same bug. This might be related to #49181.
Repository: flutter
Issue: Return back data from screens if not popped with Navigator.pop(context)
Labels: c: new feature,framework,f: routes,c: proposal,P3,team-framework,triaged-framework

### Use case

Currently, our Flutter application requires that data be returned from a screen using Navigator.pop(context, result). However, there are scenarios where a screen might not be popped using this method, and we still need to return data. This enhancement request is to enable screens to return data even if they are not popped using Navigator.pop(context).


### Proposal

Preserving the data to a global state it can be accessed from the previous screen. Considering improved flexibility in handling screen navigation and data return.
 - a user navigated to screen A to B
 - An external event (e.g. a user-initiated navigation by system nav bar) closes Screen B.
 - Screen B should be able to return data to the previous screen 

**I don't know whether it can be done by PopScope.**
Repository: next.js
Issue: Forms example does not work with useActionState
Labels: examples

### Verify canary release

- [ ] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Node.js v22.0.0

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:17:33 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6031
  Available memory (MB): 36864
  Available CPU cores: 14
Binaries:
  Node: 22.0.0
  npm: 10.5.1
  Yarn: N/A
  pnpm: 9.1.2
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which example does this report relate to?

next-forms

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

The doc says to run `pnpm create next-app --example next-forms next-forms-app`, which downloads the code, but it doesn't use the next canary package, which means it doesn't use the react 19 package. When the user goes to run the project, they will get an issue with the react useActionState hook not being available.

I see there is an issue that changed the example to use useActionState, but it may be unclear to the user if they aren't aware they need to be on canary versions of next and react.

### Expected Behavior

I would expect the example to run/work after running the create command.

### To Reproduce

run the pnpm create command from the forms example.
Repository: go
Issue: cmd/go: cgo functions rewritten only with -gcflags=-L
Labels: NeedsInvestigation,BugReport

### Go version

tip

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

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/iant/.cache/go-build'
GOENV='/home/iant/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/iant/gopath/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/iant/gopath'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org'
GOROOT='/home/iant/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/home/iant/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='devel go1.23-377646589d Fri May 24 22:23:55 2024 +0000'
GODEBUG=''
GOTELEMETRY='on'
GOTELEMETRYDIR='/home/iant/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
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 -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3319284758=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

Build this package:

```Go
package p

import "C"

func F() *C.char {
	s, err := C.CString("hi")
	if err != nil {
		println(err)
	}
	return s
}
```

### What did you see happen?

With no `-gcflags` option:

```
# command-line-arguments
$WORK/b001/_cgo_gotypes.go:75:6: _Cfunc_CString redeclared in this block
	$WORK/b001/_cgo_gotypes.go:53:6: other declaration of _Cfunc_CString
foo.go:6:12: undefined: _C2func_CString
```

With `-gcflags=-L`:

```
# command-line-arguments
$WORK/b001/_cgo_gotypes.go:75:6: C.CString redeclared in this block
	$WORK/b001/_cgo_gotypes.go:53:6: other declaration of C.CString
foo.go:6:12: undefined: C.CString
```

### What did you expect to see?

I don't expect `-gcflags=L` to change the function name reported by the compiler.  The `-L` option is documented as "Show complete file path in error messages."  Why should that change the function name?

This turns out to happen because of some code in cmd/go/internal/work/shell.go.  That code looks for lines that match the regexp `\[[^\[\]]+\.(cgo1|cover)\.go:[0-9]+(:[0-9]+)?\]`.  With `-gcflags=-L`, the compiler emits lines like

```
./foo.go:6:12[/tmp/go-build1291356211/b001/foo.cgo1.go:9:28]: undefined: _C2func_CString
```

That matches the regexp.  In that case cmd/go strips the line in square brackets, and then translates `_C2func_` to `C.`.  That was introduced in https://go.dev/cl/7231075 for the Go 1.1 release.  From looking at the source code, it does appear that at that time the compiler always printed the original file name in square brackets if a `//line` directive had been used.  Today that only happens if the `-L` option has been used.
Repository: create-react-app
Issue: Heroku Error: R14 (Memory quota exceeded) - Create React App
Labels: needs triage

I have a created a app with create-react-app, however when I deploy the app on Heroku I keep getting memory leaks. For reference am using the below. Link to my app is below. Any idea what is going on?

https://github.com/andrewaclark248/SafeTexting

client/package.json
```
  "scripts": {
    "start": "react-dotenv && react-scripts start",
    "build": "react-dotenv && react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject",
    "deploy": "npx serve -s build"
  },

```

package.json
```
  "scripts": {
    "start": "cd client && npm run start",
    "install": "cd client && npm i",
    "build": "cd client && npm run build",
    "install:build": "npm run install && npm run build",
    "deploy": "npm run install:build && cd client && npm run deploy"
  },

```

Procfile
`web: npm run deploy`
Repository: react
Issue: [Compiler Bug]: healthcheck vs eslint
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [X] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [X] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

n/a

### Repro steps

I've ran the healthcheck against my app which states that 72 out of 80 components have been compiled. The documentation states the higher the better. I don't have any eslint violations (there were 2 but those have been fixed). The app is working with some good improvements, so thanks!

```
% npx react-compiler-healthcheck@latest

Successfully compiled 72 out of 80 components.
StrictMode usage found.
Found no usage of incompatible libraries.
```

So how do i find the remaining components? Should there not be a minimum of 8 eslint violations or is that not how it works? What's the recommended approach to getting all 80 optimised?

### How often does this bug happen?

Every time

### What version of React are you using?

19.0.0-rc-38e3b23483-20240529
Repository: vscode
Issue: after resolving merge conflict the control does not automatically move to next conflict
Labels: feature-request,merge-editor

Type: <b>Bug</b>

after resolving merge conflict the control does not automatically move to next conflict
`"merge-conflict.autoNavigateNextConflict.enabled": true,` is present in the settings.

VS Code version: Code - Insiders 1.90.0-insider (ca688da9fb6dad00996cee7d5342490daa7bb1fb, 2024-05-31T01:05:41.342Z)
OS version: Windows_NT x64 10.0.22621
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (8 x 2112)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.82GB (5.45GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (23)</summary>

Extension|Author (truncated)|Version
---|---|---
ng-template|Ang|18.0.0
vscode-markdownlint|Dav|0.55.0
vscode-eslint|dba|2.4.4
githistory|don|0.6.20
gitlens|eam|15.0.4
EditorConfig|Edi|0.16.4
prettier-vscode|esb|10.4.0
output-colorizer|IBM|0.1.2
git-graph|mhu|1.30.0
mongodb-vscode|mon|1.6.0
vscode-scss|mrm|0.10.0
vscode-dotnet-runtime|ms-|2.0.5
live-server|ms-|0.4.13
vscode-typescript-next|ms-|5.5.20240505
angular-console|nrw|18.21.4
vscode-xml|red|0.27.2024053103
vscode-yaml|red|1.14.0
sonarlint-vscode|Son|4.5.1
code-spell-checker|str|3.0.1
vscode-stylelint|sty|1.4.0
vscodeintellicode|Vis|1.3.1
vscodeintellicode-completions|Vis|2.0.0
vscode-java-debug|vsc|0.57.0


</details>
<!-- generated by issue reporter -->
Repository: next.js
Issue: Failed to reload dynamic routes: Error: Catch-all must be the last part of the URL.
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://github.com/ashly-dxb/next-app

### To Reproduce

1. Next.js app is running perfectly on :  **http://localhost:3000**
2. Create a route.js file  as shown here  **.\pages\api\auth\[...nextauth]\route.js**
3. File content should be:     **export { GET, POST } from "../../../../auth";**
4. The App stops with an error message on the screen: **Internal Server Error**

### Current vs. Expected behavior

It should not make any errors as described already.

### Provide environment information

```bash
package.json file:

"dependencies": {
    "@fortawesome/fontawesome-svg-core": "^6.5.2",
    "@fortawesome/free-solid-svg-icons": "^6.5.2",
    "@fortawesome/react-fontawesome": "^0.2.1",
    "axios": "^1.7.2",
    "bcryptjs": "^2.4.3",
    "cookies-next": "^4.2.1",
    "dotenv": "^16.4.5",
    "jsonwebtoken": "^9.0.2",
    "moment": "^2.30.1",
    "mongoose": "^8.4.0",
    "next": "^14.2.3",
    "next-auth": "^5.0.0-beta.18",
    "nodemailer": "^6.9.13",
    "react": "^18.3.1",
    "react-bootstrap-icons": "^1.11.4",
    "react-dom": "^18.3.1",
    "universal-cookie": "^7.1.4"
  },
```


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

Not sure, create-next-app

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

next dev (local)

### Additional context

_No response_
Repository: kubernetes
Issue: node: e2e: simplify usage of the sample-device-plugin
Labels: area/test,area/kubelet,sig/node,triage/accepted

we currently [use two different versions](https://github.com/kubernetes/kubernetes/pull/117908/commits/356f2deb12403e563a9ecfb400d97f2f5ead35d6#r1620471275) of sample-device-plugin in the node e2e tests.
The reason for this is historical: in https://github.com/kubernetes/kubernetes/pull/115107 we added support to control the registration process to be able to test device failure handling in the application code. Because the invasive changes, we are using two instances of sample device plugins to avoid any chance of unwanted regressions.

In #117908 we are starting to clean up all of this streamlining the handling of sample-device-plugin, which was (apparently?) unnecessarily different than else. The next and final step is to use a single version of sample device plugin for everything. This simple cleanup mostly require careful testing to avoid the aforementioned risk of regressions.
Repository: excalidraw
Issue: Vue3 how use this
Labels: support

Vue3 how use this
Repository: flutter
Issue: Add SliverSizeTransition
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

### Use case

To animate size of sliver widgets.

### Proposal

Add `SliverSizeTransition` widget
Repository: next.js
Issue: static-export get searchParams is empty
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/github/Statfine/Next.js-static-export/main

### To Reproduce

```
export default function About({ searchParams}: { searchParams: { id: string } }) {
  console.log('searchParams====>', searchParams)
  return (
    <>
      <h1>About</h1>
      <div>
        Back to <Link href="/">Home</Link>
      </div>
    </>
  );
}
```

1. It is correct that the development environment gets the id from the route /about?id=123
2. npm run build
3. cd out & http-server ./ -p 8080
4. open page localhost:8080/about?id=123 bug console searchParams====> {}

 able to simulate the scenario above by change https://github.com/vercel/next.js/tree/canary/examples/with-static-export

### Current vs. Expected behavior

The packaged page returns the same as the development environment

### Provide environment information

```bash
Binaries:
  Node: 20.0.0
  Yarn: 1.22.11
Relevant Packages:
  next: 15.0.0-rc.0
  eslint-config-next: 15.0.0-rc.0
  react: 19.0.0-rc-f994737d14-20240522
  react-dom: 19.0.0-rc-f994737d14-20240522
  typescript: ^5
Next.js Config:{
  output: 'export',
  experimental: {
    reactCompiler: true,
  },
}
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

_No response_
Repository: rust
Issue: Using `-C lto=thin` and `-C no-prepopulate-passes` at the same time for windows target , report link error: undefined symbol
Labels: A-linkage,T-compiler,O-windows-gnu,C-bug

We compile `hello.rs` for `x86_64-pc-windows-gnullvm` then there is a link error: undefined symbol
`rustc -C lto=thin -C no-prepopulate-passes --target=x86_64-pc-windows-gnullvm hello.rs`
```rust
fn main() {
    println!("Hello world!");
}
```
The rustc version is `rustc 1.80.0-nightly (867900499 2024-05-23)`
The link error reproduces for target `x86_64-pc-windows-gnu` and `x86_64-pc-windows-gnullvm`
It seems that `-C no-prepopulate-passes` isn't compatible with `-Clto`.
Maybe we should report error that `-C no-prepopulate-passes isn't compatible with -Clto`?
Repository: PowerToys
Issue: Mouse without borders
Labels: Idea-Enhancement,Needs-Triage,Product-Mouse Without Borders

### Description of the new feature / enhancement

This is more of improve, I have two windows device one is pc which i use when im at home and another is my work laptop. So with the mouse without borders it works fine with minor tweaks, it will be good. For example, with mouse without border and i could listen to the audio that is playing in the second device. It will be new kvm but only for windows

### Scenario when this would be used?

As a cybersecurity student, i really use the new kvm since it will be easy for me and other professional to multitask

### Supporting information

It just an idea, Please think about it. Thank you