sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/compile: add string constants to DWARF
Labels: NeedsInvestigation,FeatureRequest,compiler/runtime

### Go version

go version go1.22.3 linux/amd64

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

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/.cache/go-build'
GOENV='/home/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.22.3'
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/user/1000/go-build3235747414=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

I tried to view the value of different types of const values with dlv.
**Code:**

> package main
> 
> import "fmt"
> 
> const myValueStr = "try"
> const myValueInt = 12
> const myValueFloat = 1.2
> 
> func main() {
> 	fmt.Println(myValueStr, myValueInt, myValueFloat)
> }




### What did you see happen?

I obtain a different behavior depending of the type of the constant.

**Debug:**

> dlv exec main
> (dlv) print main.constValueInt
> 12
> (dlv) print main.constValueStr
> **Command failed: could not find symbol value for main**
> (dlv) print main.constValueFloat
> **Command failed: could not find symbol value for main**


**Analyze:**

> objdump -W main | grep -i constV
>     <2547>   DW_AT_name        : main.constValueInt

By analyzing Go ompiler code, we can see into src/cmd/compile/internal/gc/obj.go:163 that's the func dumpGlobalConst exports only integer const "for now" (ie. comment line 172).

### What did you expect to see?

I expect to see all const values.

**Debug:**

> dlv exec main
> (dlv) print main.constValueInt
> 12
> (dlv) print main.constValueStr
> **"try"**
> (dlv) print main.constValueFloat
> **1.2**


**Analyze:**
> objdump -W main | grep -i constV
>     <2547>   DW_AT_name        : main.constValueInt
>     **<2547>   DW_AT_name        : main.constValueStr**
>     **<2547>   DW_AT_name        : main.constValueFloat**
Repository: bitcoin
Issue: build: use UCRT runtime for Windows (release) binaries
Labels: Windows,Build system

Switching to the modern runtime would be good, because the old runtime is missing features, which has meant writing workarounds for Windows in our code: i.e #29014/#29357.

[Mingw-w64 12.0.0 has been released](https://sourceforge.net/p/mingw-w64/mailman/message/58776404/), which now defaults to the `UCRT` runtime, over `MSVCRT`. See https://github.com/mingw-w64/mingw-w64/blob/master/mingw-w64-doc/howto-build/ucrt-vs-msvcrt.txt for more details. This makes using it somewhat easier, because we can just use `12.0.0` verbatim, rather than having to configure an older mingw-w64 for the newer runtime.

- [x] Upstream mingw-w64 12.0.0 into Guix: See https://git.savannah.gnu.org/cgit/guix.git/commit/?id=17188be0f723e00377b21b767f5447d7938a116e.
- [x] Update Guix time-machine here: #30452.
- [ ] Add CI to cover new runtime.
- [ ] Drop MSVCRT workarounds.
- [ ] Any other documentation / Windows release build configuration updates.
- [ ] A symbol-check that the new runtime is indeed being used.
Repository: vscode
Issue: Reconsider fixing #200693
Labels: diff-editor,under-discussion


Type: <b>Bug</b>

I have encountered the same problem and it took quite some time for me to find the #200693 issue.
Unfortunatly `"diffEditor.useInlineViewWhenSpaceIsLimited": false` didn't fix the problem as I have `"diffEditor.renderSideBySide": false` set.
If possible, please reconsider fixing #200693.

VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:16:23.416Z)
OS version: Linux x64 6.5.0-28-generic
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 5800U with Radeon Graphics (16 x 3984)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<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: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|1, 1, 1|
|Memory (System)|30.66GB (7.87GB free)|
|Process Argv|--crash-reporter-id 6b23b007-5059-4e42-a35f-0e85619d093a|
|Screen Reader|yes|
|VM|0%|
|DESKTOP_SESSION|ubuntu-xorg|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|ubuntu-xorg|
|XDG_SESSION_TYPE|x11|
</details><details><summary>Extensions (12)</summary>

Extension|Author (truncated)|Version
---|---|---
gitlens|eam|15.0.4
vscode-pull-request-github|Git|0.88.1
labeled-bookmarks|koa|1.1.11
remote-ssh|ms-|0.110.1
remote-ssh-edit|ms-|0.86.0
remote-explorer|ms-|0.4.3
vscode-pbkit|pbk|0.0.7
rust-analyzer|rus|0.3.1975
crates|ser|0.6.6
even-better-toml|tam|0.19.2
errorlens|use|3.18.0
vscode-lldb|vad|1.10.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30995554
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
chatpanelt:31048053
dsvsc021:30996838
01bff139:31013167
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecationcf:31061161
pythonprt:31056678
dwnewjupytercf:31046870
26j00206:31048877

```

</details>

<!-- generated by issue reporter -->
Repository: ollama
Issue: Custom-llama issue
Labels: bug

### What is the issue?

Hello,

I have a problem, or I misunderstood something. If I put several SYSTEM tags in my custom-llama3 file, only the last one is taken.

How can I give him more information?

Example I would like
SYSTEM You are a helpful AI assistant named Droid
but also that they can know the location of the smoking area in my building, or that to contact the Sales department they must contact 00*******?

thank you in advance for your help and sorry if my question is stupid.

### OS

Windows

### GPU

Other

### CPU

Intel

### Ollama version

 0.1.39
Repository: ollama
Issue: OLLAMA_MODELS not applied on initial start or on restart after upgrade on macOS
Labels: feature request

The addition of OLLAMA_MODELS is much appreciated, since it allows specifying a different location, such as an external disk, where more space might be available.

One issue, however, is if we put specify OLLAMA_MODELS in our .zshrc, for example, the .zshrc file isn't read when Ollama starts initially or when Ollama restarts after an update. 

Perhaps I'm missing something?

Otherwise, it would be great to make this something that can be configured/set directly in Ollama instead of needing to quit Ollama, open a Terminal (so that .zshrc is read) and start Ollama from the Terminal so that the OLLAMA_MODELS directory is set instead of using the default.
Repository: flutter
Issue: Multiple sub-page of a navigation controller have a FlutterNativeView with the same registration type, e.g. B->C,C page pops back to B, crash.
Labels: platform-ios,engine,a: platform-views,has reproducible steps,P2,c: fatal crash,team-ios,triaged-ios,found in release: 3.22,found in release: 3.23

### Steps to reproduce

When I use multi-engine mode
A navigation stack with multiple sub-surfaces all have a FlutterNativeView with the same registration type, e.g. B->C, C page pops back to B, crash.
When I use single engine mode then everything is fine

### Expected results

no crash

### Actual results

crash

Thread 1: signal SIGABRT
![image](https://github.com/flutter/flutter/assets/6309671/2c17272f-b74f-47d8-8764-c93ded151fe0)


### Code sample

<details open><summary>Code sample</summary>

```swift
if !singleEngine {// wait “https://github.com/flutter/flutter/issues/127168”
            let groupOptions = FlutterEngineGroupOptions()
            groupOptions.entrypoint = entrypoint
            groupOptions.initialRoute = initRoute
            groupOptions.entrypointArgs = [FlutterEngineBinding.deviceInfo()]
            groupOptions.libraryURI = nil
            engine = FlutterContainerManager.shared.group.makeEngine(with: groupOptions)
        }else{
            engine.run(withEntrypoint: entrypoint, libraryURI: nil, initialRoute: initRoute, entrypointArgs: [FlutterEngineBinding.deviceInfo()])
        }
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
flutter doctor   
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.1, on macOS 14.4.1 23E224 darwin-arm64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0-rc4)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.2)
[✓] VS Code (version 1.89.1)
[✓] Connected device (4 available)
```

</details>

I found version：3.16.5,3.19.5 also have this crash
Repository: vscode
Issue: Add `go to the first occurence` and `go to the last occurence` in floating find widget
Labels: feature-request,editor-find

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Many times I want to go to the first one that was found.
But if there are a dozen results, I have to click many times.
Repository: rust
Issue: compiletest: warn if we see a `// @<directive-name>`
Labels: A-testsuite,T-bootstrap,E-medium,C-bug,A-compiletest

Realized in https://github.com/rust-lang/rust/pull/125808#discussion_r1622294753.

A test writer might accidentally write

```rs
// @ignore-cross-compile
```

which is parsed as a normal comment not a compiletest directive because compiletest directives require that the line starts with `//@`.

This typo is hard to spot: both by PR authors and the reviewers. It might not fail in PR CI -- it might not even fail in full build CI, but then explode when the conditions are just right.

We should detect these and issue at least warnings from compiletest to help test writers realize the problem.
Repository: PowerToys
Issue: AI in Run
Labels: Product-PowerToys Run,Needs-Triage,Run-Plugin

### Description of the new feature / enhancement

Should work kind of like advanced paste but you don't have to copy anything and can just ask it to create something.
Could be a separate shortcut, could be right in run plugin accessible by a prefix.

After generation there could be a little prompt to press something to copy or directly paste the result.

### Scenario when this would be used?

Writing code, docs whatever.

### Supporting information

_No response_
Repository: neovim
Issue: rpc fail invalid header line "contents.py"`
Labels: bug,needs:repro,lsp

### Problem

I get 
```
Error executing luv callback:
...ers/ekarni/Neovim/share/nvim/runtime/lua/vim/lsp/rpc.lua:265: ...ers/ekarni/Neovim/share/nvim/runtime/lua/vim/lsp/rpc.lua:51: invalid header line "contents.py"
stack traceback:
	[C]: in function 'parse_chunk'
	...ers/ekarni/Neovim/share/nvim/runtime/lua/vim/lsp/rpc.lua:265: in function <...ers/ekarni/Neovim/share/nvim/runtime/lua/vim/lsp/rpc.lua:251>
```

from time to time. 

I also get can't `resume dead coroutine` afterwards. 




### Steps to reproduce

It happens when I use my own version of pylsp, but only sometimes. On clean restart, selecting workspace directory , and workspace symbols. 

### Expected behavior

clear

### Neovim version (nvim -v)

NVIM v0.10.0-dev-3122+ga0a189a8e

### Vim (not Nvim) behaves the same?

unk

### Operating system/version

windows

### Terminal name/version

nvim-qt

### $TERM environment variable

unk

### Installation

nightly
Repository: deno
Issue: Support Tanstack Start (tanstack.com)
Labels: bug,node compat

Version: Deno 1.44.0

Repro:

Clone https://github.com/tanstack/tanstack.com
pnpm i   (using pnpm v 8.10.2) 
DENO_FUTURE=1 deno task dev

Error:

```sh
➜ DENO_FUTURE=1 deno task dev
Task dev vinxi dev
vinxi v0.3.11
vinxi starting dev server

 ERROR  Cannot read properties of undefined (reading 'env')                                                                                                                                      2:23:41 PM

  at Object.plugins (app.config.timestamp_1717158220687.js:14:32)
  at Object.plugins (node_modules/.pnpm/zod@3.22.4/node_modules/zod/lib/index.mjs:3193:40)
  at Object.plugins (node_modules/.pnpm/@tanstack+start@1.34.2_@opentelemetry+api@1.8.0_react-dom@18.3.1_react@18.3.1_typescript@5.3.3_vite@5.1.4/node_modules/@tanstack/start/dist/esm/config/index.js:152:59)
  at Object.plugins (node_modules/.pnpm/@tanstack+start@1.34.2_@opentelemetry+api@1.8.0_react-dom@18.3.1_react@18.3.1_typescript@5.3.3_vite@5.1.4/node_modules/@tanstack/start/dist/esm/config/index.js:211:45)
  at createViteHandler (node_modules/.pnpm/vinxi@0.3.11_@opentelemetry+api@1.8.0/node_modules/vinxi/lib/dev-server.js:58:31)
  at async Object.handler (node_modules/.pnpm/vinxi@0.3.11_@opentelemetry+api@1.8.0/node_modules/vinxi/lib/router-modes.js:147:27)
  at async Promise.all (index 1)
  at async createDevServer (node_modules/.pnpm/vinxi@0.3.11_@opentelemetry+api@1.8.0/node_modules/vinxi/lib/dev-server.js:155:5)
  at async Object.run (node_modules/.pnpm/vinxi@0.3.11_@opentelemetry+api@1.8.0/node_modules/vinxi/bin/cli.mjs:182:17)
  at async runCommand (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:316:16) 



 ERROR  Cannot read properties of undefined (reading 'env')    
```


Seems like it's breaking at:

`authToken: process.env.SENTRY_AUTH_TOKEN,`

But it works fine with `pnpm run dev`
Repository: next.js
Issue: 'next/dynamic' - SSR does not seem to work for dynamically imported components. 
Labels: bug,Lazy Loading,Performance

### Link to the code that reproduces this issue

https://github.com/welschmoor/dynamicimortsbug

### To Reproduce
Go to this deployed version and follow instructions:
https://dynamicimortsbug.vercel.app/


### Current vs. Expected behavior

About 2 months ago everything was working fine. Then I assume because of some version bump it no longer is.

The issue is this one: If I use dynamic imports inside a server component, then it has no effect and I get the whole javascript of all dynamic components is shipped to the browser. This is not the bug, this was always the case for app router. Now, if I use 'use client' in an intermediary file where I import 'next/dynamic', then dynamic imports work almost as intended, where only if some condition is true that code for the components is imported. This keeps bundle size small. However, upon navigating to a route which has dynamic imports, I have no SSR. Dynamic components seem to be client only. So if I navigate to say /about page, I first see the footer (!!!) and then the dynamic imports are loaded and cause a huge layoutshift.

 { ssr: true } as an option to dynamic imports has no effect. About 2 months ago it worked fine, I did not have this layoutshift and the bundle size was small, so it used to work as intended. I don't remember which version I was on back then, might have even been next v13.

### Provide environment information

```bash
Happens on both Mac and Linux
```


### Which area(s) are affected? (Select all that apply)

Lazy Loading, Performance

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

My project's build fails with 15.0.0-canary.2 or the RC versions, hence 14.2.3 was used with React 18.3.0. The provided repo however is a clean create-next-app that I ran today 20240531.
Repository: deno
Issue: Allow classes with `fetch` method for `deno serve`.
Labels: suggestion,serve

I have been testing the new `deno serve` command (really cool!) but noticed that it doesn't work with methods. 
For example, the following code:

```js
const foo = new class {
  fetch(request: Request) {
    return new Response("Hello, world!");
  }
}

export default foo;
```

returns this error:

```
error: deno serve requires export default { fetch } in the main module, did you mean to run "deno run"?
```

but this one (without classes) works fine:

```js
const foo = {
  fetch(request: Request) {
    return new Response("Hello, world!");
  }
}

export default foo;
```

Supporting class methods would be nice.
Repository: godot
Issue: USER ERROR: BUG: Unreferenced static string to 0: Physics2DConstraintSolveIslands
Labels: bug,platform:android,topic:physics,topic:2d

### Tested versions

4.3 dev6

### System information

android 11 api 30

### Issue description

USER ERROR: BUG: Unreferenced static string to 0: Physics2DConstraintSolveIslands
   at: unref (core/string/string_name.cpp:127)
USER ERROR: BUG: Unreferenced static string to 0: Physics2DConstraintSetup
   at: unref (core/string/string_name.cpp:127)
FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x7b4a7b00cc)


### Steps to reproduce

There is no problem under Windows, but it appears under Android. I am using C #, which seems to be unable to debug under Android, and I am not sure where the problem lies

### Minimal reproduction project (MRP)

not have
Repository: go
Issue: crypto/tls: darwin race builders failing on BenchmarkHandshakeServer/ECDHE-X25519-ECDSA-P256
Labels: NeedsInvestigation

The darwin race builder has been failing for some time with errors or this form:

```
=== RUN   BenchmarkHandshakeServer/ECDHE-P256-RSA
BenchmarkHandshakeServer/ECDHE-P256-RSA
    handshake_server_test.go:1346: #4: read tcp 127.0.0.1:62314->127.0.0.1:62310: use of closed network connection
        Read 0, wanted 51, got , wanted 140303000101160303002800000000000000005df832a2c7d4ac17570d9fc1962a774871f425eccda764cb20ea6acc31f0cb8b
    handshake_server_test.go:1349: #4: mismatch on read: got:000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000 want:140303000101160303002800000000000000005df832a2c7d4ac17570d9fc1962a774871f425eccda764cb20ea6acc31f0cb8b
```

Representative logs:

 https://build.golang.org/log/a53a964e3bc25c4d3b3e4883e320e9f8b060f41b
 https://ci.chromium.org/ui/p/golang/builders/ci/gotip-darwin-amd64-race/b8746453827322458849/overview

I can reproduce on a gomote, e.g. 

```
$ export MOTE=thanm-gotip-darwin-amd64-race-0
$  gomote run $MOTE go/bin/go test -count=1 -bench=BenchmarkHandshakeServer crypto/tls
```

It looks as though this started at [CL 586655](https://go.dev/cl/586655) from inspecting the builder logs.

CC @FiloSottile @rolandshoemaker
Repository: kubernetes
Issue: jwt: should we allow assertion of non-Kubernetes API server audiences?
Labels: sig/auth,lifecycle/frozen,triage/accepted

A webhook token authenticator can assert which `audiences` a token is valid for:

https://github.com/kubernetes/kubernetes/blob/6d0aab2e38364d9d8e050b5f3a120a36ee588389/staging/src/k8s.io/api/authentication/v1/types.go#L91-L102

The empty list of `audiences` means "valid against the audience of the Kubernetes API server."

A JWT authenticator is unable to express this.  Instead, it can only express that "if you see any audience from this list, consider that equivalent to the audience of the Kubernetes API server."

```yaml
apiVersion: apiserver.config.k8s.io/v1beta1
kind: AuthenticationConfiguration
jwt:
- issuer:
    url: ...
    audiences:
    - audience1
    - audience2
    audienceMatchPolicy: MatchAny
  claimValidationRules: ...
...
```

For example, in the above config, `audience1` and `audience2` are considered equivalent to the API server audience (regardless of what the actual value of the API server audience is).

This means that if some "server" with audience `foo` wants to use the token review API for token verification, the "client" can only use either Kube SA tokens or tokens from a webhook authenticator to authenticate against that "server."  The workaround for the server would be to directly verify the token itself, but that would mean it would need to effectively implement the entire JWT authenticator logic itself.

One possible approach would be to allow for the use of a CEL expression to determine the `audiences`:

```yaml
apiVersion: apiserver.config.k8s.io/v1beta1
kind: AuthenticationConfiguration
jwt:
- issuer:
    url: ...
    audiences: null # must be empty
    audienceMatchPolicy: MatchViaCEL # allows the use of the audiencesExpression field
    # CEL expression that returns empty string array to mean
    # valid against the audience of the Kubernetes API server.
    # Otherwise the returned string array list is used to perform
    # an audience intersection check exactly as how it is performed
    # for the webhook token authenticator.
    audiencesExpression: "..."
  claimValidationRules: ...
...
```

/sig auth
/triage accepted

@aramase @liggitt
Repository: terminal
Issue: Windows Terminal crashes when combining duplicateTab with moveTab in multipleActions
Labels: Issue-Bug,Area-UserInterface,Severity-Crash,Product-Terminal

### Windows Terminal version

1.21.1272.0

### Windows build number

Microsoft Windows [Version 10.0.22631.3593]

### Other Software

_No response_

### Steps to reproduce

1. Include this snippet in your `settings.json`:
```json
{
    "command":
    {
        "action": "multipleActions",
        "actions":
        [
            {
                "action": "duplicateTab"
            },
            {
                "action": "moveTab",
                "window": "new"
            }
        ]
    },
    "keys": "ctrl+shift+f12"
},
```
2. Open Windows Terminal
3. Press Ctrl+Shift+F12
4. See it crash.

### Expected Behavior

I was hoping to create a new entry with `multipleActions` to 1. duplicate the current tab into a new tab, 2. move it to its own window. @zadjii-msft had proposed this great workaround as a way to clone the current tab into a new window, in https://github.com/microsoft/terminal/issues/14350#issuecomment-1304809041.

### Actual Behavior

Windows Terminal crashes.

Noting that using `multipleActions` with just the `duplicateTab` action works, but it only duplicates the tab.
Similarly, referencing *just* the `moveTab` action works.
Combining them both in `multipleActions` causes Terminal to crash.

There was a similar bug where manipulating tabs as part of `multipleActions` was causing issues:
https://github.com/microsoft/terminal/issues/11107
And there was a fix to the way Windows Terminal handled tab movement in `multipleActions`.
https://github.com/microsoft/terminal/pull/11144

Maybe a similar problem still exists when creating a new tab as part of `multipleActions`.