sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Relay compiler configuration "exclude" option is not respected
Labels: bug,Turbopack

### Link to the code that reproduces this issue

https://github.com/mjfaga/nextjs-relay-swc-excludes

### To Reproduce

Install dependencies and build:
```shell
yarn install
yarn build
```

### Current vs. Expected behavior

# Current Behavior

When adding a library (in the MVP, `@stigg/react-sdk`) that uses GraphQL under the hood, the relay compiler breaks consumption of that library and the app no longer properly builds.

```
 ± yarn build
yarn run v1.22.21
$ relay-compiler --validate && next build
[INFO] Querying files to compile...
[INFO] [default] compiling...
[INFO] [default] compiled documents: 0 reader, 0 normalization, 0 operation text
[INFO] Compilation completed.
[INFO] Done.
  ▲ Next.js 14.2.8

   Creating an optimized production build ...
Failed to compile.

./node_modules/@stigg/js-client-sdk/dist/index.js
Module not found: Can't resolve '/Users/markfaga/projects/nextjs-relay-swc-excludes/./__generated__/SlimSubscriptionFragmentV2.graphql.ts'

https://nextjs.org/docs/messages/module-not-found

Import trace for requested module:
./node_modules/@stigg/react-sdk/dist/react-sdk.esm.js
./src/app/page.tsx
```

# Expected Behavior

No errors because node_modules is excluded from being targeted during relay GraphQL compilation (see below for additional context).

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020
  Available memory (MB): 98304
  Available CPU cores: 12
Binaries:
  Node: 22.7.0
  npm: 10.8.2
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.2.8 // Latest available version is detected (14.2.8).
  eslint-config-next: 14.2.8
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.2
Next.js Config:
  output: N/A
```


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

Turbopack

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

next build (local)

### Additional context

The current [SWC relay compiler implementation](https://github.com/vercel/next.js/blob/canary/turbopack/crates/turbopack-ecmascript-plugins/src/transform/relay.rs#L20-L24) only supports 3 key options:
* `src`
* `language`
* `artifact_directory`

`exclude` is another critical option that is not currently supported. In the direct relay implementation, this is optional BUT ships with a default value of `["**/node_modules/**", "**/mocks/**", "**/generated/**"]` to ensure things like packages in node_modules aren't targeted when they also happen to use GraphQL under the hood. In these cases, node_module source is recompiled, breaking those libraries.
Repository: ollama
Issue: Talking to  Mistral-Nemo via OpenAI tool calling - fails
Labels: bug,needs more info

### What is the issue?

With this curl command:

```
curl http://localhost:11434/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{"model":"mistral-nemo:12b-instruct-2407-fp16",
  "messages": [
    {
      "role": "user",
      "content": "What is the weather like in Boston?"
    }
  ],
  "tools": [
    {
      "type": "function",
      "function": {
        "name": "get_current_weather",
        "description": "Get the current weather in a given location",
        "parameters": {
          "type": "object",
          "properties": {
            "location": {
              "type": "string",
              "description": "The city and state, e.g. San Francisco, CA"
            },
            "unit": {
              "type": "string",
              "enum": ["celsius", "fahrenheit"]
            }
          },
          "required": ["location"]
        }
      }
    }
  ],
  "tool_choice": "auto"
}' | json_pp
```

we should be able to execute an OpenAI API compatible tool use call against `mistral-nemo`.

But I get this result:

```
{
   "choices" : [
      {
         "finish_reason" : "stop",
         "index" : 0,
         "message" : {
            "content" : "Glad to help! In which unit would you like the temperature?",
            "role" : "assistant"
         }
      }
   ],
   "created" : 1725905432,
   "id" : "chatcmpl-677",
   "model" : "mistral-nemo:12b-instruct-2407-fp16",
   "object" : "chat.completion",
   "system_fingerprint" : "fp_ollama",
   "usage" : {
      "completion_tokens" : 15,
      "prompt_tokens" : 95,
      "total_tokens" : 110
   }
}
```

Is there a missing config or something similar like that?
Thanks.


### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

0.3.9
Repository: pytorch
Issue: add torch.linalg stubs
Labels: triaged,module: linear algebra

### 🚀 The feature, motivation and pitch

torch.linalg doesn't seem to have any stubs, just docstrings.
My IDE just marks everything as "Any", which is not very helpful.
Adding the interface for these functions would make my life much better.

### Alternatives

_No response_

### Additional context

_No response_

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano
Repository: deno
Issue: `npx <bin-name>` doesn't work after `deno install` on Windows
Labels: bug,windows,install

```jsonc
// package.json
{
  "dependencies": {
    "typescript": "^5.6.2"
  }
}
```

```shellsession
> deno install
> npx tsc --init
Need to install the following packages:
tsc@2.0.4
Ok to proceed? (y)
```

This was done in powershell.
Repository: TypeScript
Issue: Template Literal Types derived from the type keys cannot be used as Indexed Access Types in generic contexts
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

template literal, indexed access, keyof, key of

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about indexed access.

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.6.1-rc#code/PTAEBUE8AcFMGdQHcCWAXAFqAdgVwLawBOKAxqANayTwB0AUGjLKAIKgC8oA2gIwC6AbkbNQAIU6he3ISLigAwpIDePKpABcOAgCNi-Lb1ABfYU3kARFaAAMhk8Pog2AGxcB7JLAAmoFNm9YAA8fUABDUlIERHMEBljXDy9fLm5Wbht+ABo2bgByGzzs3Lx8PSJi9IADABJlUvLjKuKxDJb8wvaG-RzW2vrdYibihTac0YKi8e5uiun+2eGcizHQFcn+WWcLFHgwt09Q-0CQ3wio+BjmOjkWHb2D5Mk07ng0EmwAc3a3j+-p37+f5rV7vIHFFazCHcBaDIjDWS3UAAOXcaFY2AAkpdcLAADzgUDBNCwAKIdw6ABWsFIaAAfJJwDC6up3AAzCDDMyibHwXEEolBElk0AU6m0hlcJn9VkcwkAMlAAApAV9QAAfbRlYga0A6FCffxoXU6dzuFywMLYXV4Ny63ABWBs-w+ACUXKRCnc+GgETQvP5hOJpO85KpNPpjOZygAokFSC5cIE8bKIDl4JAyua6VygA

### 💻 Code

```ts
// Types with numeric keys.
type A = [1];
type B = 1[];
type C = { [key: number]: 1 };
type D = { 0: 1 };

// Allowed indexed access types.
type Allowed = [A[0], A['0'], A[number], A[`${number}`], B[0], B['0'], B[number], B[`${number}`], C[0], C['0'], C[number], C[`${number}`], D[0], D['0']];
// Disallowed indexed access types.
type Disallowed = [A[string], B[string], C[string], D[string], D[number], D[`${number}`]];

type NotAnIssue<T extends object> = T[`${keyof T}`];
type Issue<T extends object> = T[`${keyof T & (string | number | bigint | boolean | null | undefined)}`];
type CompactIssue<T extends object> = T[`${Exclude<keyof T, symbol>}`];
```

### 🙁 Actual behavior

The template type literal generated from `keyof T` cannot be used as an indexed access type for `T`.

### 🙂 Expected behavior

The template type literal generated from `keyof T` or its restriction can be used as an indexed access type for `T`, since it is restricted to be a stringified version of the key type, which should behave exactly the same as the key type in this context.

### Additional information about the issue

All object types with numeric keys can be accessed with the string version of that key. However, the compiler does not acknowledge this fact in the case of generics with proper restrictions on the type.

Using `` `${keyof T}` `` directly is prohibited because template literal types cannot be constructed from `symbol` types. However, if the type is restricted to the allowed `string | number | bigint | boolean | null | undefined`, TypeScript is still refusing to use `keyof T` for indexed access.

The issue does not happen with definite (non-generic) types and the issue also does not occur if `` `${Exclude<keyof T, symbol>}` `` is replaced with `Exclude<keyof T, symbol>` (which is still a problem for other use cases).
Repository: terminal
Issue: sixel unexpected background fill
Labels: Area-VT,Issue-Bug,Product-Terminal,In-PR

### Windows Terminal version

1.22.2362.0

### Windows build number

10.0.26040.0

### Other Software

My own sixel renderer that I just implemented.  I don't doubt that it could be something I'm doing, but the symptom doesn't match my read on the sixel stream.  This is a link to the function that does all of the sixel stream rendering:
https://github.com/JohnMcPMS/winget-cli/blob/f5f2a9497b561d2b724cbf754d89490b71a391c8/src/AppInstallerCLICore/Sixel.cpp#L156

### Steps to reproduce

This file contains a sixel stream that produces the issue: [sixel.txt](https://github.com/user-attachments/files/16935110/sixel.txt)

`cat sixel.txt` reproduces the issue.

### Expected Behavior

Only pixels within the bounds of the sixel would change.

### Actual Behavior

When I don't enable transparency in the sixel (send `0` for `P2` in the control string), some arbitrary number of cell height rows are filled with an arbitrary color.  The conditions only seem to change based on the dimensions of the sixel image, not the color palette that it contains.  This feels very much like an issue with reading uninitialized or unowned memory.

![image](https://github.com/user-attachments/assets/1f6756c7-f5d2-476e-8499-517de1bd74fe)
*Contains a selection behind the color band to indicate that it is on the sixel plane.*
Repository: flutter
Issue: SubmenuButton submenus close automatically only on first activation [Android]
Labels: platform-android,framework,f: material design,has reproducible steps,P1,customer: quake (g3),team-android,found in release: 3.24,found in release: 3.25

### Steps to reproduce

Create a SubmenuButton with a children menu items
```
  
                      SubmenuButton(
                        leadingIcon: Icon(Symbols.design_services),
                        menuChildren: [
                          MenuItemButton(
                            onPressed: () => print('Pressed'),
                            child: Text('My submenu item'),
                          ),
                        ],
                        child: Text('My submenu'),
                      ),
```

Tap on the Submenu button, and the `My submenu item` will flash open and close immediately. The submenu appears on tap down, and disappears on tap release. This only happens the first time. Any subsequent activations work fine.

### Expected results

Tapping on the submenu will show the children and not disappear.

### Actual results

Tapping on the submenu shows and hides the submenu on tap release.

### Code sample

<details open><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: MenuAnchor(
            builder: (context, controller, child) => TextButton(
              onPressed: () {
                controller.isOpen ? controller.close() : controller.open();
              },
              child: Text('Press here'),
            ),
            menuChildren: [
              SubmenuButton(menuChildren: [
                MenuItemButton(
                  onPressed: () {},
                  child: Text('Menu item'),
                ),
              ], child: Text('Submenu')),
            ],
          ),
        ),
      ),
    );
  }
}
```

</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
[Paste your output here]
```

</details>
Repository: vscode
Issue: When opening from elevated commandline returns error code 19
Labels: freeze-slow-crash-leak,windows,electron,workbench-run-as-admin

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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: 1.93.0 System Setup
- OS Version: Windows 23H2

Steps to Reproduce:

1. Open VS Code using the command `code .` on an elevated cmd.exe

This error shows up on one machine, works fine on another machine. The issue exists even after reinstalling OS:

[Window Title]
Visual Studio Code

[Main Instruction]
The window terminated unexpectedly (reason: 'launch-failed', code: '18')

[Content]
We are sorry for the inconvenience. You can reopen the window to continue where you left off.

[ ] Don't restore editors  [Reopen] [Close]
Repository: go
Issue: net/http: TestClientWriteShutdown/h1 failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net/http" && test == "TestClientWriteShutdown/h1"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8737264146446772337)):

    === RUN   TestClientWriteShutdown/h1
    === PAUSE TestClientWriteShutdown/h1
    === CONT  TestClientWriteShutdown/h1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: cmd/go: TestScript/telemetry failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript/telemetry"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8737264145430408049)):

    === RUN   TestScript/telemetry
    === PAUSE TestScript/telemetry
    === CONT  TestScript/telemetry
        script_test.go:135: 2024-09-09T14:45:39Z
        script_test.go:137: $WORK=/opt/golang/swarm/.swarming/w/ir/x/t/cmd-go-test-3295567942/tmpdir3648051217/telemetry1615998762
        script_test.go:159: 
            PATH=/opt/golang/swarm/.swarming/w/ir/x/t/cmd-go-test-3295567942/tmpdir3648051217/testbin:/opt/golang/swarm/.swarming/w/ir/x/w/goroot/bin:/opt/golang/swarm/.swarming/w/ir/x/w/goroot/bin:/opt/golang/swarm/.swarming/w/ir/x/w/goroot/bin:/opt/golang/swarm/.swarming/w/ir/cache/tools/bin:/opt/golang/swarm/.swarming/w/ir/bbagent_utility_packages:/opt/golang/swarm/.swarming/w/ir/bbagent_utility_packages/bin:/opt/golang/swarm/.swarming/w/ir/cipd_bin_packages:/opt/golang/swarm/.swarming/w/ir/cipd_bin_packages/bin:/opt/golang/swarm/.swarming/w/ir/cache/cipd_client:/opt/golang/swarm/.swarming/w/ir/cache/cipd_client/bin:/opt/golang/swarm/.swarming/cipd_cache/bin:/usr/sbin:/usr/bin
            HOME=/no-home
            CCACHE_DISABLE=1
            GOARCH=amd64
    ...
            [stderr]
            go: GOTELEMETRYDIR cannot be modified
            [exit status 1]
            > stderr '^go: GOTELEMETRYDIR cannot be modified$'
            matched: go: GOTELEMETRYDIR cannot be modified
            # Test issue #69269: 'go telemetry off' should not increment counters.
            # Establish that previous commands did write telemetry files. (0.000s)
            > exists $userconfig/go/telemetry/local
        script_test.go:159: FAIL: testdata/script/telemetry.txt:55: exists /opt/golang/swarm/.swarming/w/ir/x/t/cmd-go-test-3295567942/tmpdir3648051217/telemetry1615998762/userconfig/.config/go/telemetry/local: stat /opt/golang/swarm/.swarming/w/ir/x/t/cmd-go-test-3295567942/tmpdir3648051217/telemetry1615998762/userconfig/.config/go/telemetry/local: no such file or directory
    --- FAIL: TestScript/telemetry (2.85s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: reduce torch.compile default logs
Labels: module: logging,triaged,oncall: pt2,module: inductor

### 🐛 Describe the bug

Got these logs by default while running torch.compile: https://gist.github.com/jerryzh168/68f3a0b53908df9ae7e767cb20734eec while running this test: https://gist.github.com/jerryzh168/c2d4ce9c95d25b037a4c636a05f84fb7

### Versions

main

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: neovim
Issue: Nread causes E676: No matching autocommands for buftype=acwrite buffer
Labels: bug,bug-vim,netrw

### Problem

Using `:Nread scp ..` twice causes the error "E676: No matching autocommands for buftype=acwrite buffer" when writing the file that was open before execuing Nread. 

Seems that Nread/netrw is changing the other buffer's buftype?

### Steps to reproduce

I only know how to reproduce using scp/ssh. Assuming you already have an SSH server running:
`nvim --clean`
Open any random file. e.g. `:e ~/.gitconfig`
`:Nread scp://127.0.0.1//`
`C-^`
`:Nread scp://127.0.0.1//`
`C-^`
`:w`

### Expected behavior

Not getting an error

### Neovim version (nvim -v)

0.10.1

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

N/A Reproduced on two different distributions

### Terminal name/version

N/A

### $TERM environment variable

N/A

### Installation

Build from repo
Repository: rust
Issue: Using `GetFileInformationByName` in Windows for file stat/metadata operations
Labels: I-slow,O-windows,T-libs,C-optimization,A-filesystem

Continuing discussion from https://github.com/rust-lang/rust/pull/128256...

Currently, window's fs.rs uses the `GetFileInformationByHandle` api which requires opening and closing a file handle. A new API will be available in future builds of Windows (from documentation it should be around 24H2/26052) called `GetFileInformationByName` which does not require opening a file handle. This reduces 2-3 syscalls in this code path which can have a reasonable performance gain.

There are a few design considerations however,

- Not all file-system drivers support this API, for example FAT32
- Backwards compatibility stops at 1709, i.e. (basically this feature would be `#[cfg(not(target_vendor = "win7")`] )

Currently, this change would support tier-1 support for https://github.com/rust-lang/rust/issues/121478 since it includes all the fields needed in one call. In addition to removing the additional syscall for handling reparse points.

## Prior Art:
- https://github.com/libuv/libuv/pull/4327
- https://github.com/python/cpython/commit/0f175766e27642108c65bba04bbd54dcf8799b0e

## Links:
- GetInformationByHandle - https://learn.microsoft.com/windows/win32/api/winbase/nf-winbase-getfileinformationbyname
- Blog post - https://blogs.windows.com/windows-insider/2024/02/08/announcing-windows-11-insider-preview-build-26052-canary-and-dev-channels/

cc: @ChrisDenton
Repository: flutter
Issue: `flutter test -d` should give a warning/error
Labels: a: tests,c: new feature,tool,P2,team-tool,triaged-tool

### Use case

I often mistakenly run things like `flutter test -d chrome`[^1], with the expectation that my test platform will be Chrome. Instead of erroring or telling me what I did wrong, the tests will be executed with the default platform without a problem. I'll admit that this has tricked me into thinking that my tests passed on Chrome before...

[^1]: That's the correct flag for `flutter run`, but for `flutter test` it should be `--platform=chrome`.

### Proposal

Instead, if `flutter test` receives an invalid `-d` flag, it should output a suggestion to try the `--platform` flag. I'd also argue that it shouldn't run the tests at all in that scenario.
Repository: PowerToys
Issue: Failed to load PowerToys.ImageResizerExt.dll
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

Failed to load PowerToys.ImageResizerExt.dll

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

General, Always on Top, Command not found

### Steps to reproduce

Failed to load PowerToys.ImageResizerExt.dll
[PowerToysReport_2024-09-10-04-34-12.zip](https://github.com/user-attachments/files/16936381/PowerToysReport_2024-09-10-04-34-12.zip)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: go
Issue: x/tools/gopls: crash in Hover (telemetry)
Labels: NeedsInvestigation,gopls,Tools,gopls/telemetry-wins

```
#!stacks
"runtime.sigpanic" && ("golang.hover:+170" || "golang.hover:+209")
```

This stack `zUGLQA` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2024-09-07.json):
```go
if def, ok := pkg.TypesInfo().Defs[ident]; ok && ident.Pos() == def.Pos() {
```
Looks like `Defs[ident]=nil` is an actual map entry.

`crash/crash`
[`runtime.gopanic:+69`](https://cs.opensource.google/go/x/go/+/go1.23.0:../../../../Users/adonovan/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.0.darwin-arm64/src/runtime/panic.go;l=804)
`runtime.panicmem:=262`
[`runtime.sigpanic:+19`](https://cs.opensource.google/go/x/go/+/go1.23.0:../../../../Users/adonovan/go/pkg/mod/golang.org/toolchain@v0.0.1-go1.23.0.darwin-arm64/src/runtime/signal_unix.go;l=900)
[`golang.org/x/tools/gopls/internal/golang.hover:+170`](https://cs.opensource.google/go/x/tools/+/gopls/v0.16.1:gopls/internal/golang/hover.go;l=304)
[`golang.org/x/tools/gopls/internal/golang.Hover:+4`](https://cs.opensource.google/go/x/tools/+/gopls/v0.16.1:gopls/internal/golang/hover.go;l=109)
[`golang.org/x/tools/gopls/internal/server.(*server).Hover:+30`](https://cs.opensource.google/go/x/tools/+/gopls/v0.16.1:gopls/internal/server/hover.go;l=51)
[`golang.org/x/tools/gopls/internal/protocol.serverDispatch:+335`](https://cs.opensource.google/go/x/tools/+/gopls/v0.16.1:gopls/internal/protocol/tsserver.go;l=503)
[`golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.ServerHandler.func3:+5`](https://cs.opensource.google/go/x/tools/+/gopls/v0.16.1:gopls/internal/protocol/protocol.go;l=160)
[`golang.org/x/tools/gopls/internal/lsprpc.(*streamServer).ServeStream.handshaker.func4:+52`](https://cs.opensource.google/go/x/tools/+/gopls/v0.16.1:gopls/internal/lsprpc/lsprpc.go;l=509)
[`golang.org/x/tools/gopls/internal/protocol.Handlers.MustReplyHandler.func1:+2`](https://cs.opensource.google/go/x/tools/+/gopls/v0.16.1:../../../../Users/adonovan/go/pkg/mod/golang.org/x/tools@v0.22.1-0.20240628205440-9c895dd76b34/internal/jsonrpc2/handler.go;l=35)
[`golang.org/x/tools/gopls/internal/protocol.Handlers.AsyncHandler.func2.2:+3`](https://cs.opensource.google/go/x/tools/+/gopls/v0.16.1:../../../../Users/adonovan/go/pkg/mod/golang.org/x/tools@v0.22.1-0.20240628205440-9c895dd76b34/internal/jsonrpc2/handler.go;l=103)
`runtime.goexit:+0`
```
golang.org/x/tools/gopls@v0.16.1 go1.23.0 darwin/amd64 vscode (1)
```

Issue created by golang.org/x/tools/gopls/internal/telemetry/cmd/stacks.
Dups: ylB3Iw x2v5eg