dragon-fly

> @glopal @lowang-bh Do you have any terminal related settings configured? I have no special settings about terminal, all is the default.

> When you see a terminal tab with the warning icon, and hover over it, VS Code will show what environment variables are updated and options to investigate the details...

> > When you see a terminal tab with the warning icon, and hover over it, VS Code will show what environment variables are updated and options to investigate the...

> I downgraded vscode to 1.79 and the extension runs the PATH export as expected. So it's either a bug in vscode 1.80, or an interoperability issue with the latest...

in the scenario which switching go version works well, we can see the vscode's terminal runs this command.

> https://blog.csdn.net/weixin_42873928/article/details/129957307 Not works for me.

The latest release of v2.10.1 ```go testing.tRunner.func1.2({0x1020a40a0, 0x10327ada8}) /usr/local/go/src/testing/testing.go:1526 +0x1c8 testing.tRunner.func1() /usr/local/go/src/testing/testing.go:1529 +0x364 panic({0x1020a40a0, 0x10327ada8}) /usr/local/go/src/runtime/panic.go:884 +0x1f4 github.com/agiledragon/gomonkey/v2.modifyBinary(0x101aedcd0, {0x1400051e900, 0x18, 0x102050240?}) /Users/wlh/go/src/github.com/volcano-sh/volcano/vendor/github.com/agiledragon/gomonkey/v2/modify_binary_darwin.go:9 +0xa0 github.com/agiledragon/gomonkey/v2.replace(0x101aedcd0, 0x101fc8ae0?) /Users/wlh/go/src/github.com/volcano-sh/volcano/vendor/github.com/agiledragon/gomonkey/v2/patch.go:269 +0x88 github.com/agiledragon/gomonkey/v2.(*Patches).ApplyCore(0x140002df930, {0x101fc8ae0?, 0x14000518ca0?,...

> I am suggesting running your unit test in docker images so the problem would not occur again. It works fine for me with the image`golang:1.20`. I am using M1....

/lgtm

/lgtm