sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: associative scan is incorrect for certain shapes/kwargs
Labels: high priority,triaged,oncall: pt2,module: higher order operators

I got this repro from noticing some test failures locally (details here: https://github.com/pytorch/pytorch/pull/136670#issuecomment-2412515964)
```
import torch
from torch._higher_order_ops.associative_scan import associative_scan

def f(a):
    return associative_scan(lambda x, y: x + y, a, dim=1, reverse=True, combine_mode="generic")

a = torch.arange(18, dtype=torch.float32, device='cuda').reshape(2, 9)

# I got this output from running with `_fake_associative_scan` defined here:
# https://github.com/pytorch/pytorch/blob/main/test/functorch/test_control_flow.py#L1579
expected_out = torch.tensor([
    [ 36.,  36.,  35.,  33.,  30.,  26.,  21.,  15.,   8.],
    [117., 108.,  98.,  87.,  75.,  62.,  48.,  33.,  17.],
], dtype=torch.float32, device='cuda')

out = f(a)
print(torch.allclose(out, expected_out))
# output is:
# tensor([[ 36.,  15.,  35.,   0.,  30.,   0.,  21.,   0.,   8.],
          [117.,  33.,  98.,  36.,  75.,  33.,  48.,  26.,  17.]],
         device='cuda:0')
```

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @chauhang @penguinwu @ydwu4 @yf225
Repository: rust
Issue: Tracking Issue for `const_eq_ignore_ascii_case`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(const_eq_ignore_ascii_case)]`

This is a tracking issue for const `eq_ignore_ascii_case` on `[u8]` and `str`.

<!--
Include a short description of the feature.
-->

### Public API

```rust
impl [u8] {
    pub const fn eq_ignore_ascii_case(&self, other: &[u8]) -> bool;
}
impl str {
    pub const fn eq_ignore_ascii_case(&self, other: &str) -> bool;
}
```

### Steps / History

- [x] Implementation: #131721
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

### Unresolved Questions

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: rust
Issue: `--extern mycrate=path/to/my/crate/with/random.suffix` fails with "file name should be lib*.rlib or lib*.so"
Labels: T-compiler,C-bug,A-crates,A-rust-for-linux,E-needs-design

macro.rs:
```rust
extern crate proc_macro;
use proc_macro::TokenStream;

#[proc_macro_attribute]
pub fn your_macro(_attr: TokenStream, item: TokenStream) -> TokenStream {
    // Macro implementation
    item
}
```

main.rs:
```rust
extern crate macros;

#[macros::your_macro]
fn main() {
    println!("Hello, world!");
}
```

This works:
```shell
rustc --crate-type proc-macro macros.rs -o libmacros.dylib
rustc main.rs --extern macros=libmacros.dylib
```

This doesn't:
```shell
rustc --crate-type proc-macro macros.rs -o libmacros.so
rustc main.rs --extern macros=libmacros.so
```

```
error: extern location for macros is of an unknown type: libmacros.so
 --> main.rs:4:1
  |
4 | extern crate macros;
  | ^^^^^^^^^^^^^^^^^^^^

error: file name should be lib*.rlib or lib*.dylib
 --> main.rs:4:1
  |
4 | extern crate macros;
  | ^^^^^^^^^^^^^^^^^^^^

error[E0463]: can't find crate for `macros`
 --> main.rs:4:1
  |
4 | extern crate macros;
  | ^^^^^^^^^^^^^^^^^^^^ can't find crate

error: aborting due to 3 previous errors

For more information about this error, try `rustc --explain E0463`.
```

This has come up in Rust-For-Linux where we'd like to always use the .so suffix, but this causes the build to fail on macOS. If we change the suffix to .dylib, it works on macOS, but not Linux.
Repository: go
Issue: cmd/compile: inlining of range funcs should be more aggressive
Labels: Performance,NeedsInvestigation,compiler/runtime

Consider the following program:

```
package pkg

import (
	"iter"
)

func trivialIterator() iter.Seq[int] {
	return func(yield func(int) bool) {
		yield(0)
	}
}

func consumer() {
	for range trivialIterator() {
		foo()
		foo()
	}
}

//go:noinline
func foo() {}
```

Building it with `GOEXPERIMENT=newinliner` with `go1.24-cbdb3545ad` reports:

```
./foo.go:8:9: can inline trivialIterator.func1 with cost 60 as: func(func(int) bool) { yield(0) }
./foo.go:7:6: can inline trivialIterator with cost 17 as: func() iter.Seq[int] { return func literal }
./foo.go:21:6: cannot inline foo: marked go:noinline
./foo.go:13:6: cannot inline consumer: function too complex: cost 175 exceeds budget 160
./foo.go:14:2: cannot inline consumer-range1: function too complex: cost 190 exceeds budget 160
./foo.go:14:27: inlining call to trivialIterator with score -23
./foo.go:8:9: can inline consumer.trivialIterator.func1 with cost 60 as: func(func(int) bool) { yield(0) }
./foo.go:14:2: inlining call to consumer.trivialIterator.func1 with score 60
./foo.go:8:14: yield does not escape
./foo.go:8:9: func literal escapes to heap:
./foo.go:8:9:   flow: ~r0 = &{storage for func literal}:
./foo.go:8:9:     from func literal (spill) at ./foo.go:8:9
./foo.go:8:9:     from return func literal (return) at ./foo.go:8:2
./foo.go:8:9: func literal escapes to heap
./foo.go:8:14: yield does not escape
./foo.go:14:2: consumer capturing by ref: #state1 (addr=false assign=true width=8)
./foo.go:14:2: func literal does not escape
./foo.go:14:27: func literal does not escape
```

Note that despite the utter trivialness of the loop body (`consumer-range1`), it cannot be inlined.

I think that inlining of range bodies deserves a special case and that the cost of the synthetic function is unimportant. If this were a "normal" loop, the body would inherently be part of the `consumer` function, no matter how complex it'd be. If we know that `yield` is only called in a single place syntactically, then we should be able to unconditionally inline the range func and produce code no more complex than for a normal loop (excluding the state tracking for range funcs, but that's fixed overhead).

I'm sure I'm missing something.

(The bot will find many related issues, but I don't think any of them directly mention this general case.)
Repository: flutter
Issue: Flutter Windows native implementation should bring any way to draw the system's button while customizing title bar to keep features like "snap layouts"
Labels: c: new feature,platform-windows,c: proposal,a: desktop,P3,team-windows,triaged-windows

### Use case

Flutter Windows native implementation should bring any way to draw the system's button while customizing title bar to keep features like "snap layouts"

There is some packages in pub.dev that helps customizing title bar by "disabling" the system's one, but this disables native features like [Windows 11 snap layouts](https://learn.microsoft.com/en-us/windows/apps/desktop/modernize/ui/apply-snap-layout-menu) and there is no way to render that.

### Proposal

Create an API to let the system draw the native buttons when "frameless" mode from window_manager package or bitsdojo_window_windows native hack to runner's main.cpp, keeping features like "snap layouts".
Repository: godot
Issue: AnimationNodeTransition transition_to_self doesnt fade when transitioning to self.
Labels: bug,topic:animation

### Tested versions

- reproducible in godot v4.3 (stable)

### System information

Windows 10 - Godot 4.3 (Stable) - Vulkan Forward+

### Issue description

When you make a transition node in an AnimationTree and set it to transition to self it does not fade, instead simply starting the animation over entirely unless you create a duplicate animation input.

This could be how its intended but feels wrong that when i want to fade an animation to itself on a AnimationTransitionNode i have to make a copy if that animation. 

### Steps to reproduce

Create a new AnimationTree, create an AnimationNodeTransition and set to transition to self. Give it an Xfade. Have it transition to self while game is running. instead of fading to self it will simply restart the animation.

### Minimal reproduction project (MRP)

[animationtransitionnode.zip](https://github.com/user-attachments/files/17371131/animationtransitionnode.zip)
Repository: svelte
Issue: False positive `ownership_invalid_binding`?
Labels: bug,awaiting submitter

### Describe the bug

I'm getting the following message, telling me to consider `bind:` between the two components. However, I am, in fact, binding between the two.

![CleanShot 2024-10-14 at 22 02 50@2x](https://github.com/user-attachments/assets/a6735923-5c19-4b8f-917f-237953016c6c)


### Reproduction

https://svelte.dev/playground/c27c1016f1f2423489568d9fb2271921?version=5.2.5


### Logs

```shell
[svelte] ownership_invalid_bindingsrc/lib/calendar-with-select.svelte passed a value to node_modules/.pnpm/bits-ui@1.0.0-next.17_svelte@5.0.0-next.265/node_modules/bits-ui/dist/bits/calendar/components/calendar.svelte with `bind:`, but the value is owned by node_modules/.pnpm/bits-ui@1.0.0-next.17_svelte@5.0.0-next.265/node_modules/bits-ui/dist/bits/calendar/components/calendar.svelte. Consider creating a binding between node_modules/.pnpm/bits-ui@1.0.0-next.17_svelte@5.0.0-next.265/node_modules/bits-ui/dist/bits/calendar/components/calendar.svelte and src/lib/calendar-with-select.svelte
```


### System Info

```shell
System:
    OS: macOS 15.0
    CPU: (12) arm64 Apple M2 Max
    Memory: 92.23 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.15.1 - ~/.nvm/versions/node/v20.15.1/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v20.15.1/bin/npm
    pnpm: 9.6.0 - ~/Library/pnpm/pnpm
    bun: 1.0.25 - ~/.bun/bin/bun
  Browsers:
    Edge: 129.0.2792.89
    Safari: 18.0
  npmPackages:
    svelte: ^5.0.0-next.1 => 5.0.0-next.265
```


### Severity

annoyance
Repository: ant-design
Issue: Tree显示icon后未对齐且多行文本和图标未在同一行
Labels: Inactive,improvement

### Reproduction link

[https://ant.design/components/tree-cn#tree-demo-line](https://ant.design/components/tree-cn#tree-demo-line)

### Steps to reproduce
总之就是看起来好乱

![image](https://github.com/user-attachments/assets/6aa5e6a1-f33b-48a3-b33f-df798157d056)

![image](https://github.com/user-attachments/assets/ea6210dd-7727-4535-84e6-b17f7c4ec3ca)


### What is expected?

对齐

### What is actually happening?

未对齐

| Environment | Info |
| --- | --- |
| antd | 5.21.4 |
| React | 18.3.1 |
| System | windows 11 |
| Browser | chrome latest |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: StateError: Bad state: No running isolate (inspector is not set).
Labels: c: crash,dependency: dart,P2,team-tool,triaged-tool,dependency:dart-triaged

First appeared in 3.23.0

Appears to be exclusive to `flutter run --machine --start-paused -d chrome`.

Affects ~1.3% of clients that have reported a crash on 3.24.3 (which has a crash rate of ~1%)

Stack trace as of 3.24.3:

```
StateError: Bad state: No running isolate (inspector is not set).
at ChromeProxyService.inspector(chrome_proxy_service.dart:78)
at _waitForResumeEventToRunMain.<anonymous closure>(dwds_vm_client.dart:308)
at _rootRunUnary(zone.dart:1415)
at _CustomZone.runUnary(zone.dart:1308)
at _CustomZone.runUnaryGuarded(zone.dart:1217)
at _BufferingStreamSubscription._sendData(stream_impl.dart:365)
at _DelayedData.perform(stream_impl.dart:541)
at _PendingEvents.handleNext(stream_impl.dart:646)
at _PendingEvents.schedule.<anonymous closure>(stream_impl.dart:617)
at StackZoneSpecification._run(stack_zone_specification.dart:207)
at StackZoneSpecification._registerCallback.<anonymous closure>(stack_zone_specification.dart:114)
at _rootRun(zone.dart:1391)
at _CustomZone.run(zone.dart:1301)
at _CustomZone.runGuarded(zone.dart:1209)
at _CustomZone.bindCallbackGuarded.<anonymous closure>(zone.dart:1249)
at StackZoneSpecification._run(stack_zone_specification.dart:207)
at StackZoneSpecification._registerCallback.<anonymous closure>(stack_zone_specification.dart:114)
at _rootRun(zone.dart:1399)
at _CustomZone.run(zone.dart:1301)
at _CustomZone.runGuarded(zone.dart:1209)
at _CustomZone.bindCallbackGuarded.<anonymous closure>(zone.dart:1249)
at _microtaskLoop(schedule_microtask.dart:40)
at _startMicrotaskLoop(schedule_microtask.dart:49)
at _runPendingImmediateCallback(isolate_patch.dart:118)
at _RawReceivePort._handleMessage(isolate_patch.dart:185)
```

Potentially relevant files:
* https://github.com/dart-lang/webdev/blob/main/dwds/lib/src/dwds_vm_client.dart
* https://github.com/dart-lang/webdev/blob/main/dwds/lib/src/services/chrome_proxy_service.dart
Repository: deno
Issue: [Bug] fs.exists, Deno.readTextFile, Deno.writeTextFile Fail to Work on Memory Disk
Labels: bug,windows,ext/fs

Version: Deno 2.0.0
OS: Windows 10 x86_64

```txt
deno 2.0.0 (stable, release, x86_64-pc-windows-msvc)
v8 12.9.202.13-rusty
typescript 5.6.2
```

## Intro

I use a memory disk created by [ImDisk](https://sourceforge.net/projects/imdisk-toolkit/). Its setup is as follows. However, some Deno file system APIs fail to work on it.

![image](https://github.com/user-attachments/assets/3a84d4c5-db91-4d46-88e7-78d99c3e18bb)

## Reproduce the Issue

Here are the steps.

### Create a test file

```sh
cd /d y:\
echo test > a.txt
```

### Create a test typescript file

```typescript
import { exists } from "https://deno.land/std/fs/mod.ts";

Deno.readTextFile("y:\\a.txt")
  .then((x) => console.log(x))
  .catch((e) => console.error(e));
Deno.writeTextFile("y:\\test.txt", "test")
  .then((x) => console.log(x))
  .catch((e) => console.error(e));
exists("y:\\a.txt")
  .then((x) => console.log(x))
  .catch((e) => console.error(e));
```

### Execute the typescript file

The error message is as follows.

```txt
Error: Incorrect function. (os error 1): readfile 'y:\a.txt'
    at Object.readTextFile (ext:deno_fs/30_fs.js:777:24)
    at file:///C:/test.ts:3:6 {
  code: "EISDIR"
}
Error: Incorrect function. (os error 1): writefile 'y:\test.txt'
    at writeFile (ext:deno_fs/30_fs.js:835:13)
    at Object.writeTextFile (ext:deno_fs/30_fs.js:877:12)
    at file:///C:/test.ts:6:6 {
  code: "EISDIR"
}
Error: Incorrect function. (os error 1): stat 'y:\a.txt'
    at async Object.stat (ext:deno_fs/30_fs.js:407:15)
    at async exists (https://deno.land/std@0.224.0/fs/exists.ts:112:18) {
  code: "EISDIR"
}
```

## Summary

The impacted file system APIs are not restricted to the ones in the test. There might be more of them.

Actually, not all file system APIs fail. E.g. `Deno.copyFile`, `Deno.remove` work well. I guess because they leverage OS native API.
Repository: TypeScript
Issue: Using types from private class properties results in `any` types in `.d.ts` files
Labels: Bug

### 🔎 Search Terms

class private any index access

### 🕗 Version & Regression Information

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

### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/KYDwDg9gTgLgBAYwDYEMDOa4DEITgbwCg4S4woBLANxRmDgH1yIxhYBPALjjRkoDsA5nAC8cAOTiA3MVIII-XlACuCGNAAUKKIO44IAbXFMoLNjHbiAugEoCskgF9CzoA

### 💻 Code

```ts
export class Foo {
    private _property: string = '';
    constructor(arg: Foo['_property']) {
    }
}

```


### 🙁 Actual behavior

Generated `.d.ts` is:
```ts
export declare class Foo {
    private _property;
    constructor(arg: Foo['_property']);
}
```

### 🙂 Expected behavior

Generated `.d.ts` is:
```ts
export declare class Foo {
    private _property: string;
    constructor(arg: Foo['_property']);
}
// or
export declare class Foo {
    private _property;
    constructor(arg: string);
}
// or
/* Typescript Errors on the code to tell you it's going to generate an `any` */
```

### Additional information about the issue

This behaviour is problematic because it creates a desync between consumers of `.ts` files and consumers of `.d.ts` files for the same code.

For example:
```ts
new Foo(1);
```

If the `Foo` type comes from the `.ts` file, then TS will error on this code as it can see that the argument type is `string`.
OTOH if the `Foo` type comes from the `.d.ts` file, then TS will **_NOT_** error on this code as it sees the argument type as `any`.

---

We have just uncovered this at Canva.
A user reported an error showing up in their IDE against our `master` branch (i.e. code that has passed CI as typechecked).
The code is structured such that the file with the error (A) is in a separate project to the file declaring the class (B).
This means that we have the exact scenario above where (A) consumes (B)'s `.d.ts` during our CLI builds, but (A) consume's (B)'s `.ts` within the IDE.

This pattern of declaring a type based on a private property's type is quite pervasive across our codebase and it's surprising that this is the first problem that's been actively revealed.
Repository: rust
Issue: Elided lifetime changes in `rust_2018_idioms` lint is very noisy and results in dramatically degraded APIs for Bevy
Labels: A-lints,T-lang,C-discussion,L-elided_lifetimes_in_paths,A-edition-2018,I-lang-radar

# Problem

With the upcoming release of Rust 2024 edition, we're concerned that `rust_2018_idioms` will be deny by default.

*[Editorial comment (TC): This is not an edition item for Rust 2024, and the edition is not accepting any new items, so we can say definitely that this will not be tied to the release of Rust 2024.  See [here](https://github.com/rust-lang/rust/issues/131725#issuecomment-2416993025).]*

We investigated what these changes will entail for Bevy in https://github.com/bevyengine/bevy/pull/15916, and the impact is quite severe. Our primary user-facing system and query APIs are littered with meaningless lifetimes.

This is a much worse experience with no upside for us, and Bevy and its entire ecosystem will have to manually allow this lint on every project.

## Proposed solution

We would appreciate if the elided lifetimes lint could be split out from the rest of the `rust_2018_idioms` linting, which we generally liked the effect of.

Ideally this would be off by default as well, to avoid needing to teach new users to turn it off as a critical part of project setup.
Repository: rust
Issue: Tracking Issue for bootstrap spurious rebuilds
Labels: E-hard,T-bootstrap,C-bug,C-tracking-issue,E-needs-investigation

This is a tracking issue for collecting spurious rebuild issues in bootstrap. Spurious rebuilds refer to rebuilds that seem unnecessary, e.g. if running `./x test run-make` twice in a row without modifying any sources rebuilds cargo. Note that is this not *always* the case, e.g. at the time when this issue was created, `mir-opt` tests build a special std with `mir-opt` `RUSTFLAGS`, which will need to be rebuilt if trying to go to stage2 because a stage2 rustc will expect a stage1 "standard" std build without `mir-opt` `RUSTFLAGS` (there are other solutions to that, not in the scope of this issue).

## Categories

NOTE: There is only currently one category of spurious rebuilds that I am acutely aware of, it's entirely possible to have other classes of causes for spurious rebuilds.

### Differing `RUSTFLAGS`

While some of these issues are closed, the fixes are usually stopgap solutions.

- [ ] #131636
- [x] #131437
- [x] #130108
    - Remark: this is `RUSTFLAGS` too via `cargo.configure_linker`.
- [x] #126464
- [x] #123177

### Preventing spurious rebuilds due to differing `RUSTFLAGS`

To solve the class of spurious rebuilds due to differing `RUSTFLAGS`, we will need to properly handle them. Specifically, we need to (https://github.com/rust-lang/rust/issues/131636#issuecomment-2412844566):

- Centralize `RUSTFLAGS` handling to forbid naive "conditional" `RUSTFLAGS`.
- Conditional `RUSTFLAGS` should be propagated to bootstrap shims using environment variable (something like `IMPLICIT_RUSTFLAGS`) so they can't invalidate the build cache.
- Ensure bootstrap should never set any conditional rustflag explicitly on cargo.

### Discussion

https://rust-lang.zulipchat.com/#narrow/stream/326414-t-infra.2Fbootstrap/topic/Mechanism.20for.20better.20RUSTFLAGS.20handling
Repository: PowerToys
Issue: KeyboardManagerEngine can't run.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

When running for long periods of time, the keyboardManagerEngine will be killed

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: next.js
Issue: NextJs requests custom route when using `navigator.clipboard.writeText`
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://github.com/cuongle-hdwebsoft/nextjs-bug

### To Reproduce

1. Start the application in development mode
2. Go to homepage http://localhost:8080/
3. Click the button `Click me`, and wait until it alerts `Copy clipboard successfully`
4. Open server log in the terminal, it will appear `==> This route is called`

### Current vs. Expected behavior

Current behavior:
- When I use `navigator.clipboard.writeText` to copy the text, it always request API to my custom route

Expected behavior:
- It should not request API when using `navigator.clipboard.writeText`

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Mon Aug 12 20:51:54 PDT 2024; root:xnu-11215.1.10~2/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.22
  pnpm: 9.12.0
Relevant Packages:
  next: 14.2.15 // Latest available version is detected (14.2.15).
  eslint-config-next: 14.2.15
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


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

create-next-app

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

next dev (local)

### Additional context

_No response_
Repository: PowerToys
Issue: Adding the mouse highlighter mode command to the quick access menu
Labels: Needs-Triage

### Description of the new feature / enhancement

In the quick access menu, could we not add the possibility to activate or deactivate the mouse highlighter mode.
This could look like a checkbox.
This use would be identical to the activation keyboard shortcut.

If we use the highlighter from time to time, the keyboard shortcut is forgotten and the action on the quick access menu solves this problem.

![Image](https://github.com/user-attachments/assets/454e8c13-a53a-445f-a6f8-40042ace086b)


### Scenario when this would be used?

If we use the highlighter from time to time, the keyboard shortcut is forgotten and the action on the quick access menu solves this problem.

### Supporting information

_No response_
Repository: vscode
Issue: No activated agent with id in remote window
Labels: bug,remote,confirmation-pending,chat

<!-- ⚠️⚠️ 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. -->
Version: 1.94.2
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0

Steps to Reproduce:

1. I have a Copilot running on the remote extension host process, in remote window.
2. The chat participant is contributed by the local extension.