sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: https://github.com/kubernetes/kubernetes/issues/129593
Labels: kind/failing-test,sig/architecture,needs-triage

### Which jobs are failing?

master-informing
- ec2-master-scale-performance

### Which tests are failing?

ClusterLoaderV2.load overall (/home/prow/go/src/k8s.io/perf-tests/clusterloader2/testing/load/config.yaml)
ClusterLoaderV2.load: [step: 29] gathering measurements [01] - APIResponsivenessPrometheusSimple
ClusterLoaderV2.load: [step: 29] gathering measurements [07] - APIAvailability


### Since when has it been failing?

Continuous fail since 2 Jan until now (13 Jan)
[2025-01-03 07:03:16 +0000 UTC](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-kops-aws-scale-amazonvpc-using-cl2/1875075116421877760)
[2025-01-04 07:02:14 +0000 UTC](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-kops-aws-scale-amazonvpc-using-cl2/1875437256194396160)
[2025-01-08 07:02:13 +0000 UTC](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-kops-aws-scale-amazonvpc-using-cl2/1876886807254142976)
[2025-01-13 07:03:04 +0000 UTC](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-kops-aws-scale-amazonvpc-using-cl2/1878698764034641920)

![Image](https://github.com/user-attachments/assets/7caad7c8-c0bb-4c23-9b2b-e2f277865b67)

### Testgrid link

https://testgrid.k8s.io/sig-release-master-informing#ec2-master-scale-performance

### Reason for failure (if possible)

`{ Failure :0
[measurement call APIResponsivenessPrometheus - APIResponsivenessPrometheusSimple error: top latency metric: there should be no high-latency requests, but: [got: &{Resource:secrets Subresource: Verb:DELETE Scope:resource Latency:perc50: 25.95124ms, perc90: 46.712232ms, perc99: 3.770032761s Count:16151 SlowCount:478}; expected perc99 <= 1s got: &{Resource:configmaps Subresource: Verb:GET Scope:resource Latency:perc50: 25.439364ms, perc90: 45.790856ms, perc99: 3.403321481s Count:579 SlowCount:8}; expected perc99 <= 1s got: &{Resource:leases Subresource: Verb:PUT Scope:resource Latency:perc50: 25.681733ms, perc90: 46.22712ms, perc99: 2.928246732s Count:2734799 SlowCount:44167}; expected perc99 <= 1s got: &{Resource:pods Subresource:binding Verb:POST Scope:resource Latency:perc50: 25.594763ms, perc90: 46.070573ms, perc99: 2.366918654s Count:182655 SlowCount:2645}; expected perc99 <= 1s got: &{Resource:deployments Subresource: Verb:POST Scope:resource Latency:perc50: 25.563803ms, perc90: 46.014846ms, perc99: 1.562933373s Count:16609 SlowCount:228}; expected perc99 <= 1s]]
:0}`

`{ Failure :0
[measurement call APIAvailability - APIAvailability error: API availability: SLO not fulfilled (expected >= 99.50, got: 98.93)]
:0}`

### Anything else we need to know?

N/A

### Relevant SIG(s)

/sig architecture
/sig scheduling
Repository: react-native
Issue: TextInput onKeyPress fires after the onChange
Labels: Component: TextInput,Needs: Repro,Newer Patch Available,Needs: Attention

### Description

According to the [docs](https://reactnative.dev/docs/textinput#:~:text=Fires%20before%20onChange%20callbacks.)  the keyPress event should fire before the change event. That does not seem to be the case though, I've run into this on a physical device in a project (doesn't use expo) I can't share and also reproduced this on a online playground for react native with expo.

In the video you can see that the `console.log` in the onChange callback happens before the `cosnole.log` in the `onKeyPress` callback:

https://github.com/user-attachments/assets/6e5b8cd5-6452-42a7-b315-54c911933a14

### Steps to reproduce

1. Add the onKeyPress and onChange callbacks to a TextInput
2. Trigger both events by pressing any key on a keyboard
3. see that onChange triggers first

### React Native Version

tested on 0.74.5 and 0.76.6

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
info Fetching system and libraries information...
System:
  OS: Linux 5.10 Manjaro Linux
  CPU: (8) x64 Intel(R) Core(TM) i7-10610U CPU @ 1.80GHz
  Memory: 18.82 GB / 30.99 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.18.2
    path: /usr/local/bin/node
  Yarn:
    version: 1.22.22
    path: /usr/local/bin/yarn
  npm:
    version: 9.8.1
    path: /usr/local/bin/npm
  Watchman: Not Found
SDKs:
  Android SDK: Not Found
IDEs:
  Android Studio: AI-241.18034.62.2411.12169540
Languages:
  Java: Not Found
  Ruby:
    version: 2.6.8
    path: /home/owner/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.74.5
    wanted: 0.74.5
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: false
  newArchEnabled: false
```

### Stacktrace or Logs

```text
no logs to show
```

### Reproducer

https://snack.expo.dev/@ncpa/rn-bug

### Screenshots and Videos

_No response_
Repository: godot
Issue: The Toggle Scripts Panel keyboard shortcut in the script editor is responding to the wrong key in brazilian abnt2 keyboards.
Labels: discussion,topic:editor,topic:input

### Tested versions

- Reproducible in: v4.3.stable.official [77dcf97d8]
- I haven't tested, but I remember this happening for as long as I can remember, I just didn't reported until now.

### System information

Godot v4.3.stable - Windows 10.0.19044 - GLES3 (Compatibility) - ANGLE (NVIDIA, NVIDIA GeForce GTX 1050 Ti (0x00001C82) Direct3D11 vs_5_0 ps_5_0, D3D11-31.0.15.4617) - Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz (8 Threads)

### Issue description

The keyboard shortcut for "toggle scripts panel" is ctrl+backslash.

![Image](https://github.com/user-attachments/assets/37ec389b-372d-4293-82ed-cc6cb70e3079)

But when using a default brazilian abnt2 keyboard, I have to press the "]" key, wich is in the same position as the "#" key in an ISO keyboard. Bellow you can see the abnt2 layout.

![Image](https://github.com/user-attachments/assets/a94ee75a-d7f9-425f-a0a8-d3194a166a5f)

I think this should probably be because sortcut is using physical key code instead of non physical (layout dependent) key code.

### Steps to reproduce

- plug in an abnt2 keyboard
- open a script
- press ctrl+backslash (the backslash printed in the keyboard, that is, the key to the right of the left shift)
- nothing happens
- press ctrl+right_square_bracket
- the scripts panel will hide

### Minimal reproduction project (MRP)

Not needed. any new empty project will do.
Repository: svelte
Issue: :has with sibling selector shows as unused when styling svg elements
Labels: css

### Describe the bug

When trying to style elements based on siblings in :has selector is falsy reported as unused. When i wrap it in global it works.
When trying to style html elements in the same way it works without issues.

### Reproduction

- With "~" sibling selector: https://svelte.dev/playground/hello-world#H4sIAAAAAAAAA22QwU7DMBBEf2VZDm1RRJpKXFwnEjf-AXNInW1jyTiRvS2NrPDtyEmqgsTRM7Nvdh3R1Z-EAt_I2g6-Om8bWFNjmJoNZng0lgKK94g89CmXBMxuU699_xwuZDlphzrQf7ruHJPjgAJl0N70XCmn2BJDikMJq6l3tVdO5veEk-FymqLxkWrdQrTkTtwKKLZjBmZMlmKpjdeWQF9LhdHAU7IVgh5KhcVWIfhS4UtSbB1CqdBTozCvlnFPmudHzFPNhP0D3W1vuN0vXJqR-bKik21RzX8Y01Hjg8zbYrmCB0tTwQwVbR3W36l2E-cdFB-NtQI8NfukjPfwkpj9gz3T4st8xmKGTFdGwf5M48f4A7HHHojRAQAA
- With "+" sibling selector: https://svelte.dev/playground/hello-world#H4sIAAAAAAAAA22QwU7DMBBEf8Ush7YQkaYSF9eJxI1_wBxSZ9tYWpzI3pZGVv4dOUlVkDh6ZvbNriO4-gtBwjsSdeK789SINTaWsdlABkdLGEB-ROChT7kkQHabeuv7l3BB4qQd6oD_6aZzjI4DSFDBeNtzpZ1mQhYpLkqxmnpXe-1Ufk84FS6nKRofsTatiITuxK0UxXbMhB2TpVkZ6w2hMNdSQ7TiKdkahBlKDcVWg_ClhtekUB1CqcFjoyGvlnGPhudHzFPNhP0D3W1vuN0vXJpR-bKiU21RzX8Y01Hjg8rbYrmCB8KpYIbKtg7r51S7ifMOmo-WSAqPzT4p4z28JGb_QGdcfJXPWMiA8cog2Z9x_Bx_AMd0wwzRAQAA
- With :global:  https://svelte.dev/playground/hello-world#H4sIAAAAAAAAA21QzU7DMAx-lWAO26Ci7SQuWTqJG-9AOHSpt0YyaZV4Y1XUd0dpOw0kjv5-bUdw9ReChHck6sR356kRa2wsY7OBDI6WMID8iMBDn3QJgOzmeuv7l3BB4oQd6oD_4aZzjI4DSFDBeNvzXjvNhCySXFRiNfWudtqp_K5wKlxOkzQ-Ym1aEQndiVspymLMhB0TpVkZ6w2hMNdKQ7TiKdEahBkqDWWhQfhKw2tCqA6h0uCx0ZDvF7tHw_MQ81Qzxf4J3Ra3uO2vuORR-bKiU225n38Y01Hjg8rbcrmCB8KpYA6VJ-oONa1lW4f1c6rfbOK8jOajJZLCY7NLyHh3LYqZP9AZF17lcz5kwHhlkOzPOH6OP9ySgvHaAQAA

### Logs

_No response_

### System Info

```shell
System:
    OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
    Memory: 18.77 GB / 31.11 GB
    Container: Yes
    Shell: 5.2.21 - /bin/bash
  Binaries:
    Node: 18.20.3 - ~/.nvm/versions/node/v18.20.3/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v18.20.3/bin/yarn
    npm: 10.7.0 - ~/.nvm/versions/node/v18.20.3/bin/npm
    pnpm: 9.4.0 - ~/.nvm/versions/node/v18.20.3/bin/pnpm
    bun: 1.1.34 - ~/.bun/bin/bun
  Browsers:
    Chrome: 131.0.6778.264
  npmPackages:
    svelte: 5.17.3 => 5.17.3
```


### Severity

annoyance
Repository: godot
Issue: Animation Performance Problems
Labels: confirmed,topic:animation,performance

### Tested versions

Reproduced 4.4 Dev 7, 4.3 Stable
Not Reproduced 3.6 Stable

### System information

Windows 11, i3 10105f

### Issue description

I've noticed that Animation Tree and Animation Player seem to have a Ludicrously high cost

For Reference, in my game to have 60 FPS, I can have ~100 AI characters with active animation players and trees, but 3-4 times as many with them disabled.
Each of the AI's is dynamically typed GDScript, that isn't even all that optimized, gathering data of their environment and communicating with each other, moving around with Godot's physics and navigation calculations running in the background of all of that.

The GPU is not the limitation, given it's taking only a couple of milliseconds per frame to render and changing GPU taxing settings does nothing

### Steps to reproduce

Open MRP, Observe poor performance, go to the instance, and set process mode of the animation tree and player to disabled, Observe Massive Improvement

Note: The MRP went a bit extreme (some 2.4k instances) to tank the performance even harder for those more powerful systems out there (It's a slide show on mine in the editor with animations activated in the instances)

### Minimal reproduction project (MRP)

[Animation.zip](https://github.com/user-attachments/files/18397920/Animation.zip)
Repository: rust
Issue: Add mpsc select
Labels: T-libs-api,C-feature-request

Rust has nice implementations of channels, but is missing an implementation of `select` (i.e. wait on multiple channels), which severely limits their usefulness.

The usual solution is to give up on `std::sync::mpsc::channel` entirely and use [`crossbeam-channel`](https://docs.rs/crossbeam/latest/crossbeam/channel/index.html) instead. That's rather unfortunate - it's like providing a file API, but there's no write functionality so you have to use a third party crate for all file operations instead.

Years ago there was an unstable implementation, but [it was removed in 2019](https://github.com/rust-lang/rust/pull/60921) without ever being stabilised (the implementation was apparently unsafe and had other issues - see #27800).

However since 2022, `std::sync::mpsc::channel` has been implemented in terms of `crossbeam-channel`, which makes it even more weird that you still have to use `crossbeam-channel`, and also presumably means that importing `crossbeam-channel`'s `select` implementation is much easier.

Could we do that?

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"krishpranav"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: next.js
Issue: Turbopack - Module not found: Can't resolve './foo!=!./foo'
Labels: Turbopack

### Link to the code that reproduces this issue

https://github.com/jantimon/reproduction-nextjs-inline-match-resource

### To Reproduce

1. `npm run dev --turbopack`
2. See the error: `Module not found: Can't resolve './foo!=!./foo'`

### Current vs. Expected behavior

# Next.js 15.1.4 `!=!` Support

Inline match resource query `!=!` is not supported by TurboPack

| Command               | Status |
|-----------------------|--------|
| npm run dev              | ✅     |
| npm run build            | ✅     |
| npm run dev --turbopack  | ❌     |

As turbo-pack does not support `!=!` in the path, it will throw an error when running `yarn dev --turbopack`:

```
 ⨯ ./app/page.tsx:3:1
Module not found: Can't resolve './foo!=!./foo'
  1 | import Image from "next/image";
  2 |
> 3 | import foo from "./foo!=!./foo";
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  4 |
  5 |
  6 | export default function Home() {
```

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
  Available memory (MB): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: 9.6.0
Relevant Packages:
  next: 15.1.4 // Latest available version is detected (15.1.4).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
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 dev (local)

### Additional context

We are trying to add TurboPack compatibility for [next-yak](https://github.com/DigitecGalaxus/next-yak)

> 🦀 Zero-runtime CSS-in-JS powered by Rust. Write styled-components syntax, get build-time CSS extraction and full RSC compatibility 

next-yak transpiles tsx code to css

So our loader generates css from `button.tsx` although the file has a `.tsx` extension 

`webpack` has a great feature for this case: "inline match resource queries"

Will you add inline match resource queries to turbopack or is there another way to migrate next-yak to TurboPack?
Repository: PowerToys
Issue: PowerToys.Run will not launch
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

WinGet, GitHub

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

[PowerToysReport_2025-01-13-09-51-28.zip](https://github.com/user-attachments/files/18398279/PowerToysReport_2025-01-13-09-51-28.zip)

I've recently updated to Windows 11 24H2 and recently PowerToys.Run has stopped launching. 

### ✔️ Expected Behavior

PowerToys.Run to launch as usual.

### ❌ Actual Behavior

Nothing

### Other Software

_No response_
Repository: tauri
Issue: [bug] I am using show_menu_on_left_click, but the following warning keeps appearing: tauri::tauri_utils::config::TrayIconConfig::menu_on_left_click: Use show_menu_on_left_click instead.
Labels: type: bug,status: needs triage

### Describe the bug

```json
{
  "build": {
    "beforeBuildCommand": "yarn build",
    "beforeDevCommand": "yarn dev",
    "frontendDist": "../out",
    "devUrl": "http://localhost:3000"
  },
  "bundle": {
    "active": true,
    "category": "DeveloperTool",
    "icon": ["icons/icon.icns", "icons/icon.png"],
    "macOS": {
      "dmg": {
        "background": "./imgs/image.png",
        "windowSize": {
          "width": 700,
          "height": 400
        }
      },
      "entitlements": "./entitlements.plist",
      "signingIdentity": "Developer ID Application"
    },
    "createUpdaterArtifacts": true
  },
  "productName": "Jiffy",
  "mainBinaryName": "jiffy",
  "version": "1.0.1",
  "identifier": "com.jiffy.dev",
  "plugins": {
    "updater": {
      "pubkey": "",
      "endpoints": [""]
    }
  },
  "app": {
    "macOSPrivateApi": true,
    "windows": [
      {
        "label": "main"
      },
      {
        "label": "list"
      }
    ],
    "security": {
      "csp": null
    },
    "trayIcon": {
      "id": "tray_list",
      "iconPath": "icons/tray_icon.png",
      "iconAsTemplate": true,
      "showMenuOnLeftClick": true
    }
  }
}
```
This is our tauri.conf.json file.
I am using show_menu_on_left_click, but the following warning keeps appearing:
`tauri::tauri_utils::config::TrayIconConfig::menu_on_left_click: Use show_menu_on_left_click instead.`
How to solve it?

![CleanShot 2025-01-14 at 00 10 48@2x](https://github.com/user-attachments/assets/f74c2b8f-9962-4c97-9efc-d97eacbdbbe4)

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
Error `tauri.conf.json` error on `app > trayIcon`: {"id":"tray_list","iconPath":"icons/tray_icon.png","iconAsTemplate":true,"showMenuOnLeftClick":true} is not valid under any of the schemas listed in the 'anyOf' keyword
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: tauri
Issue: [feat] Add features to individually enable mobile support
Labels: type: feature request

### Describe the problem

I've recently migrated a project that we have to Tauri v2 and noticed that many dependencies were showing up in our `Cargo.lock` file that are related to mobile targets (I noticed this especially with the `swift` and `objc2-` crates). Internally we are trying to review more and more dependencies of our projects to reduce the chance of supply chain attacks and make a contribution to the security of the general ecosystem.

I know that unused dependencies won't be included in the final executable (e.g. of our strictly desktop related app), but it would help our reviewing efforts a lot if unneeded dependencies would not show up in the `Cargo.lock` file.

### Describe the solution you'd like

Following the approach used by many other crates, it would be great to see new features added (maybe called `iOS` and `Android` for mobile targets, other targets could maybe follow in the future) to configure which target platforms are enabled. That would allow us to reduce the number of dependencies showing up in the `Cargo.lock` file, reducing the clutter, communicating clearly which deps are required, and also making it easier to review code to guarantee supply chain safety.

The current behavior can be kept by adding these target features to the default set of features that is enabled when adding Tauri to a project.

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: godot
Issue: Environment "Glow" should be put before the "Tonemap"
Labels: enhancement,discussion,topic:rendering,topic:editor,topic:3d,topic:vfx

### Tested versions

Tested on a Godot 4.4 nightly build I downloaded yesterday (Jan 12 2025)

### System information

Godot v4.4.dev (5b52b4b5c) - Windows 11 (build 22631) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3050 Laptop GPU (NVIDIA; 32.0.15.6109) - 11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz (12 threads)

### Issue description

I saw the AgX PR(https://github.com/godotengine/godot/pull/87260) has been merged, so I decided to download Godot for the first time and take a look. I downloaded this demo scene: https://github.com/perfoon/Abandoned-Spaceship-Godot-Demo

Here is what I see:

![Image](https://github.com/user-attachments/assets/a3d3a1be-47ed-4212-8c26-99db95009ed2)

It looks to me that the "Glow" effect is being put _after_ the Image Formation (or view transform or tonemap), while it should be put to _before_. A rule of thumb is that any processing that can generate Open Domain (higher than 1.0) values need to be put to pre-formation (or pre-tonemapping), this is why the entire Blender compositor is before the view transform. Godot is not putting the Image formation/view transform/tone mapping at the end of these processings, which causes this problem. I feel the need to report this. You might also want to check whether there are other similar issues with other settings apart from fixing this.

### Steps to reproduce

1. Open this demo project: https://github.com/perfoon/Abandoned-Spaceship-Godot-Demo
2. Select the WorldEnvironment, in the inspector, change the "Tonemap" setting to AgX
3. See how a clipping issue that shouldn't be there when AgX is enabled remains
4. Disable the "Glow", see how the issue disappears.

### Minimal reproduction project (MRP)

N/A
Repository: go
Issue: x/tools/gopls: out-of-bounds slice panic in bug in frob.(*reader).bytes
Labels: NeedsInvestigation,gopls,Tools,gopls/telemetry-wins,BugReport

```
#!stacks
"runtime.goPanicSliceAcap" && "frob.(*reader).bytes"
```
Issue created by [stacks](https://pkg.go.dev/golang.org/x/tools/gopls/internal/telemetry/cmd/stacks).

```go

func (r *reader) bytes(n int) []byte {
	v := r.data[:n]
	r.data = r.data[n:] // <--- panic
	return v
}
```

This stack `MZjt-Q` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2025-01-10.json):

- `crash/crash`
- [`runtime.gopanic:+69`](https://cs.opensource.google/go/go/+/go1.23.3:src/runtime/panic.go;l=804)
- [`golang.org/x/tools/gopls/internal/cache.assert:=10`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/cache/debug.go;l=10)
- [`golang.org/x/tools/gopls/internal/cache.(*packageHandleBuilder).evaluatePackageHandle.func1:+2`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/cache/check.go;l=1074)
- [`runtime.gopanic:+50`](https://cs.opensource.google/go/go/+/go1.23.3:src/runtime/panic.go;l=785)
- [`runtime.goPanicSliceAcap:+2`](https://cs.opensource.google/go/go/+/go1.23.3:src/runtime/panic.go;l=141)
- `golang.org/x/tools/gopls/internal/util/frob.(*reader).bytes:=392`
- [`golang.org/x/tools/gopls/internal/util/frob.(*frob).Decode:+6`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/util/frob/frob.go;l=248)
- `golang.org/x/tools/gopls/internal/util/frob.Codec[...].Decode:=53`
- [`golang.org/x/tools/gopls/internal/cache/typerefs.decode:+2`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/cache/typerefs/refs.go;l=805)
- `golang.org/x/tools/gopls/internal/cache/typerefs.Decode:=42`
- [`golang.org/x/tools/gopls/internal/cache.(*Snapshot).typerefs:+12`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/cache/check.go;l=1274)
- [`golang.org/x/tools/gopls/internal/cache.(*packageHandleBuilder).evaluatePackageHandle:+53`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/cache/check.go;l=1120)
- [`golang.org/x/tools/gopls/internal/cache.(*Snapshot).getPackageHandles.func2.1:+8`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/cache/check.go;l=896)
- [`golang.org/x/sync/errgroup.(*Group).Go.func1:+3`](https://cs.opensource.google/go/x/sync/+/v0.9.0:errgroup/errgroup.go;l=78)
- `runtime.goexit:+0`
```
golang.org/x/tools/gopls@v0.17.1 go1.23.3 linux/amd64 vscode (1)
```