sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [AOTI] AttributeError: 'ShapeAsConstantBuffer' object has no attribute 'dtype'
Labels: triaged,oncall: pt2,module: aotinductor

### 🐛 Describe the bug

comment out the line below:

[pytorch/test/inductor/test_aot_inductor.py](https://github.com/pytorch/pytorch/blob/57a9a64e10b84fa8d932482ae9417aa3fc3fbf44/test/inductor/test_aot_inductor.py#L2312)

Line 2312 in [57a9a64](https://github.com/pytorch/pytorch/commit/57a9a64e10b84fa8d932482ae9417aa3fc3fbf44)

 "test_index_put_with_none_index": fail_stack_allocation(is_skip=True), 
and run the following command:

```
python test/inductor/test_aot_inductor.py -k AOTInductorTestABICompatibleCpuWithStackAllocationAndMinimalArrayRefInterface.test_dynamic_scalar_abi_compatible_cpu_with_stack_allocation_and_minimal_arrayref_interface

```
error:
```
 File "/home/yingzhaoseattle/pytorch/torch/_inductor/codegen/cpp_wrapper_cpu.py", line 910, in generate
    self.write_wrapper_decl()
  File "/home/yingzhaoseattle/pytorch/torch/_inductor/codegen/cpp_wrapper_cpu.py", line 401, in write_wrapper_decl
    output_arrayref_types = ", ".join(
                            ^^^^^^^^^^
  File "/home/yingzhaoseattle/pytorch/torch/_inductor/codegen/cpp_wrapper_cpu.py", line 402, in <genexpr>
    f"ArrayRefTensor<{DTYPE_TO_CPP[x.get_dtype()]}>"
                                   ^^^^^^^^^^^^^
  File "/home/yingzhaoseattle/pytorch/torch/_inductor/ir.py", line 318, in get_dtype
    return self.dtype
           ^^^^^^^^^^
AttributeError: 'ShapeAsConstantBuffer' object has no attribute 'dtype'
To execute this test, run the following from the base repo dir:
     python test/inductor/test_aot_inductor.py -k AOTInductorTestABICompatibleCpuWithStackAllocationAndMinimalArrayRefInterface.test_dynamic_scalar_abi_compatible_cpu_with_stack_allocation_and_minimal_arrayref_interface
```

### Versions

PyTorch version: 2.5.0a0+git00f675b
Is debug build: False
CUDA used to build PyTorch: 12.0
ROCM used to build PyTorch: N/A

OS: CentOS Stream 9 (x86_64)
GCC version: (GCC) 11.4.1 20231218 (Red Hat 11.4.1-3)
Clang version: Could not collect
CMake version: version 3.26.5
Libc version: glibc-2.34
```[tasklist]
### Tasks
```


cc @ezyang @anijain2305 @chauhang @penguinwu @desertfire @chenyang78
Repository: ollama
Issue: openchat 8b
Labels: model request

openchat/openchat-3.6-8b-20240522
https://huggingface.co/openchat/openchat_3.5
Repository: pytorch
Issue: RVV support in PyTorch
Labels: module: performance,module: cpu,triaged,enhancement

### 🚀 The feature, motivation and pitch

# RVV support in PyTorch

We conducted performance tests on the RISC-V platform, comparing the performance of various models on `aarch64` and `riscv64` machines. We observed significantly slower performance on riscv64 machines for models such as `MobileNet_v2`, `YOLOv3`, and `VGG16`. We want to add support for the RISC-V Vector ISA extension in PyTorch to optimize kernel implementations, enhance model execution speed, and also QNNPACK support for RISC-V.

Upon analyzing performance issues, we found no optimizations for the RISC-V architecture in PyTorch. After some attempts #127867, we believe that adding RVV support could provide poor man's improvements on hardware with V extension support.  Although there have been previous efforts in this #43359, they did not progress further. I plan to work on this but am unsure how to collaborate with the community.

### Alternatives

#### Pitch

Many other software, such as OpenBLAS, OpenCV, and SLEEF, have successfully integrated RVV support for performance enhancements. I have already create a PR #127867 for `DepthwiseConvKernel`, which observed significant performance improvements when inferring with `MobileNet_v2`. With input data dimensions of `[1, 3, 224, 224]`, we saw a threefold performance increase. We hope to achieve performance parity with ARM machines by continue optimizing for the RISC-V architecture.

#### Solution

The main focus is optimize kernels with RVV. Based on initial work, it does not negatively impact the original PyTorch build. Future efforts can extend RVV support to these modules.

**Kernels**

- DepthwiseConvKernel
- int4mm_kernel
- int8mm_kernel
- BlasKernel
- ...

**Vec**

- intrinsics.h
- vec_base.h
- ...

**QNNPACK**

- q8vadd
- q8conv
- q8gemm
- q8dwconv
- u8rmax
- u8clamp
- q8gavgpool
- q8avgpool
- sgemm
- u8maxpool
- x8zip
- requantization
- ...

**CI**

- Build tests on riscv64
- ...

#### Seeking advice

We are a small team from the Institute of Software, Chinese Academy of Sciences, attempt to improve PyTorch support on RISC-V. We plan to work on the aspects mentioned above but are unsure how to engage with the community since there are no maintainers listed for RISC-V specific areas. Future improvements will cross multiple modules, so how should we get maintainer reviews? Any advice from the PyTorch community on this topic will be appreciated.

Additionally, should I write an RFC for this purpose?


### Additional context


We used QEMU and CanMV-K230 (with RVV 1.0) for functionality and performance testing as described above.

```[tasklist]
### Tasks
```


cc @msaroufim @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10
Repository: PowerToys
Issue: Shortcut Palette 
Labels: Needs-Triage

### Description of the new feature / enhancement

I'd really love to see this feature. It might be like, press a certain key (e..g. Cmd) and see a Shortcut Cheat Sheet of the currently focused application.  

### Scenario when this would be used?

Currently trying to get away from using the mouse so much and increase productivity by using just keyboard and shortcuts. Trying to memorize the shortcuts ain't that easy. 

### Supporting information

Idea is coming from CheatSheet. 
Really love when using a mac (https://cheatsheet-mac.en.softonic.com/mac?ex=RAMP-2046.0).
Repository: ollama
Issue: Support OPTIONS with OpenAI endpoints
Labels: feature request,api

![微信截图_20240626152830](https://github.com/ollama/ollama/assets/129468439/23e316b8-cb87-4783-81af-96b94690a61a)
Repository: pytorch
Issue: Libtorch 2.3.1 requires Glibc_2.28 and can't be used on ubuntu 18.
Labels: module: binaries,module: docs,module: cpp,triaged,module: intel

### 🐛 Describe the bug

I'm not sure if it's expected or not, but it seems that the prebuild abi libtorch requires glibc>=2.28 to use. However according to the [support linux distribution](https://pytorch.org/get-started/locally/#supported-linux-distributions), the minima requirement for glibc is 2.17.

libtorch link: https://download.pytorch.org/libtorch/cpu/libtorch-cxx11-abi-shared-with-deps-2.3.1%2Bcpu.zip

ldd output for abi's `libtorch_cpu`:
```bash
ldd libtorch_cpu.so
./libtorch_cpu.so: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by ./libtorch_cpu.so)
./libtorch_cpu.so: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by ./libtorch_cpu.so)
        linux-vdso.so.1 (0x00007ffee0b88000)
        libc10.so => not found
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f0a068e2000)
        libgcc_s.so.1 => /root/miniconda3/lib/libgcc_s.so.1 (0x00007f0a1e91b000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f0a066de000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f0a064bf000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f0a06121000)
        libgomp-98b21ff3.so.1 => not found
        libstdc++.so.6 => /root/miniconda3/lib/libstdc++.so.6 (0x00007f0a05f3e000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f0a05b4d000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f0a1e717000)
```

In the meantime, it seems that the non-abi version's libtorch_cpu.so doesn't require Glibc >= 2.28, below is the `ldd`  output for non-abi libtorch_cpu.so

```bash
linux-vdso.so.1 (0x00007ffc78bef000)
        librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f7e3d0fa000)
        libgcc_s.so.1 => /root/miniconda3/lib/libgcc_s.so.1 (0x00007f7e54b73000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f7e3cef6000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f7e3ccd7000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f7e3c939000)
        libstdc++.so.6 => /root/miniconda3/lib/libstdc++.so.6 (0x00007f7e3c756000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f7e3c365000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f7e5496f000)
```




### Versions

2.3.1

cc @seemethere @malfet @osalpekar @atalman @svekars @brycebortree @jbschlosser @frank-wei @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10
Repository: vscode
Issue: Missing theme variables for test coverage highlight background
Labels: feature-request,testing

<!-- ⚠️⚠️ 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
- Yes
<!-- 🪓 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.90.2
- OS Version: Win 11

Steps to Reproduce:

1. Have a repository with a written Jest tests that doesn't cover 100% of the code.
2. Run `npx jest --coverage`
3. Run command `Jest: Toggle Coverage`
4. Highlighted uncovered code cannot be themed.

When you turn on test coverage, this is the row highlights you'll get for the rows with uncovered tests (dark red and sand color):
![image](https://github.com/microsoft/vscode/assets/1387798/d9d5512d-4f23-41ee-a442-d505ef058653)
![image](https://github.com/microsoft/vscode/assets/1387798/e266f376-dd38-4c02-b7cf-05ba49efdadf)

As a VS Code theme maintainer, I want to set the custom color for these highlights. I followed the [documentation for testing colors](https://code.visualstudio.com/api/references/theme-color#testing-colors). However, none of the available variables seem to take effect. I suppose the variables for these highlights are not yet available.
![image](https://github.com/microsoft/vscode/assets/1387798/adea7c6d-8084-4bb2-9fb9-45d6aff59a1b)
![image](https://github.com/microsoft/vscode/assets/1387798/9731246c-bcd3-4b28-a072-33029d8c8b34)
Repository: vscode
Issue: jsx auto indentation not corrent
Labels: bug,editor-autoindent

https://github.com/microsoft/vscode/assets/41773861/cc499f00-1402-40b5-940e-ad897d033e6f

@hediet @aiday-mar

## Expect

after press enter, the indent should align to the start of `onClick`

```
Version: 1.90.2 (Universal)
Commit: 5437499feb04f7a586f677b155b039bc2b3669eb
Date: 2024-06-18T22:37:41.291Z
Electron: 29.4.0
ElectronBuildId: 9728852
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.5.0
```
Repository: godot
Issue: If Prefer native menu is enabled after displaying a popupmenu at least once, it displays in odd location
Labels: bug,topic:porting,topic:gui

### Tested versions

- Reproducible in v4.3.beta2.official [b75f0485b]
Feature "Prefer Native Menu" on PopupMenu is not available on the latest version of 4.2.2

### System information

Windows 10 - v4.3.beta2.official [b75f0485b]

### Issue description

After displaying a PopupMenu at least once, if the option "Prefer Native Menu" in it's property list is enabled, displaying the popup menu again will reveal it in an odd location
![Godot_v4 3-beta2_win64_6gsPbSoEfc](https://github.com/godotengine/godot/assets/51516412/98ad0b35-ba09-41c3-8dfd-ed208dd3ce8c)


### Steps to reproduce

1. Create PopupMenu node
2. Add an item or two to the item list
3. trigger the PopupMenu
4. Enable the "Prefer Native Menu" property in the node's property list
5. Retrigger the PopupMenu

### Minimal reproduction project (MRP)

[bug-report.zip](https://github.com/user-attachments/files/15984393/bug-report.zip)
I've included this project in two other bug reports I've posted recently - If you're coming from/going to one of the other two this is a part of, rest assured you don't need to redownload the project for each report. They are the exact same file.
Repository: godot
Issue: Linking a PopupMenu to a StatusIndicator forces the PopupMenu to use the Prefer Native Menu option
Labels: bug,topic:porting,topic:gui

### Tested versions

- Reproducible in v4.3.beta2.official [b75f0485b]
StatusIndicator and the "Prefer Native Menu" option on PopupMenu are not available on the latest version of 4.2.2

### System information

Windows 10 - v4.3.beta2.official [b75f0485b]

### Issue description

When linking a PopupMenu to a StatusIndicator, the PopupMenu is forced to use the "Prefer Native Window" option regardless of how the PopupMenu was triggered

### Steps to reproduce

1. Create PopupMenu and StatusIndicator nodes
2. Link PopupMenu to StatusIndicator node
3. Add an item to the item list
4. Trigger the PopupMenu outside of the StatusIndicator node (e.g. with .popup())

### Minimal reproduction project (MRP)

[bug-report.zip](https://github.com/user-attachments/files/15984393/bug-report.zip)
I've included this project in two other bug reports I've posted recently - If you're coming from/going to one of the other two this is a part of, rest assured you don't need to redownload the project for each report. They are the exact same file.
Repository: flutter
Issue: [go_router] In TabBarView with StatefulShellBranch, content remains Blank when swiping to switch between tabs
Labels: package,has reproducible steps,P2,p: go_router,team-go_router,triaged-go_router,found in release: 3.22,found in release: 3.23

### What package does this bug report belong to?

go_router

### What target platforms are you seeing this bug on?

Android, iOS

### Have you already upgraded your packages?

Yes

### Dependency versions

<details><summary>pubspec.lock</summary>

```lock
 go_router: ^14.2.0
```

</details>


### Steps to reproduce

1. Clone [flutter/packages](https://github.com/flutter/packages) and run `custom_stateful_shell_route` for example.
2. Swipe the TabBarView to switch between tabs.

example file:
https://github.com/flutter/packages/blob/main/packages/go_router/example/lib/others/custom_stateful_shell_route.dart

### Expected results

Screen B2 of Tab 2 to be displayed even if the Tab is switched by swiping.

### Actual results

Swiping does not display the contents of the TabBarView, but a blank space.


### Code sample

<details open><summary>Code sample</summary>

It can be reproduced with the example code in flutter/packages.
https://github.com/flutter/packages/blob/main/packages/go_router/example/lib/others/custom_stateful_shell_route.dart

</details>


### Screenshots or Videos

<details open>
<summary>Screenshots / Video demonstration</summary>


https://github.com/flutter/flutter/assets/8737743/a0c91f4d-96b6-4ae6-bb63-ebe417ac7073



</details>


### Logs

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


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.22.0, on macOS 14.5 23F79 darwin-arm64, locale en-JP)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.90.2)
[✓] Connected device (6 available)
    ! Error: Browsing on the local area network for iPhone. Ensure the device is unlocked and attached with a cable or associated with
      the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources

• No issues found!
```

</details>
Repository: TypeScript
Issue: C extends A but C does not extend A | B
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

union extends

### 🕗 Version & Regression Information

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

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.5.2#code/C4TwDgpgBAglC8UDeUCGAuKBGANFARpgM7ABOAlgHYDmAvlAD7JqYBMUehUJFNtA3AFgAUKEhQAQgmYYorPAGNiZKtSgCRY6AGFpKWVkZzOy3mo3DN4aAHUA9qQDWRADwAVKBAAewCJQAmRLDS2gB80m5CotZQACJ2EEQAcnbA9k7unj5+gcFMUohhEfxAA

### 💻 Code

```ts
type A = { a: 1, b: string} | { a: 2 , b: string};
type B = { a: 2, c: string };
type C = { a: 1 | 2, b: string };

type Works<T extends A = C> = T;
type DoesNotWork<T extends A | B = C> = T;
```


### 🙁 Actual behavior

An error tells that C does not extend A | B

### 🙂 Expected behavior

No error since C extends A and therefore extends A | B

### Additional information about the issue

_No response_
Repository: storybook
Issue: [Bug]: "Source" and "Canvas" display only "type: code" after updating to v8
Labels: bug,react,block: source,sev:S2

### Describe the bug

After updating to Storybook v8, the code blocks under the canvas displays different code then previously when you click the "Show code" button.

Storybook 7
<img width="660" alt="Screenshot 2024-06-26 at 11 22 54" src="https://github.com/storybookjs/storybook/assets/18709268/a7dc0374-918e-46f2-a819-a6895767fe00">

Storybook 8
<img width="706" alt="Screenshot 2024-06-26 at 11 23 02" src="https://github.com/storybookjs/storybook/assets/18709268/f893b012-10a1-4cb1-ba45-5554f6c0ce4a">

I'm using CSF with MDX

```typescript
// toggle.stories.tsx

import type { Meta, StoryObj } from '@storybook/react';
import { Toggle } from './toggle';

const meta: Meta<typeof Toggle> = {
    component: Toggle,
    title: 'Inputs/Toggle',
    args: {
        'data-test-id': 'toggle',
        isChecked: true,
        isDisabled: false,
        size: 'medium',
    },
};

export default meta;
type Story = StoryObj<typeof Toggle>;

export const Basic: Story = {};
``` 

```mdx
{/* toggle.mdx */}

import { Canvas, Meta } from '@storybook/blocks';
import * as ToggleStories from './toggle.stories';

<Meta of={ToggleStories} />

<Canvas of={ToggleStories.Basic} />
``` 

This issue occurs with every story where I use MDX. When there is a `render` function in the story object, it outputs the entire story object instead of displaying only the JSX output as it did previously.

Storybook 7
<img width="655" alt="Screenshot 2024-06-26 at 11 33 52" src="https://github.com/storybookjs/storybook/assets/18709268/1a7bf844-7d08-4605-b471-5d812da34444">

Storybook 8
<img width="702" alt="Screenshot 2024-06-26 at 11 33 35" src="https://github.com/storybookjs/storybook/assets/18709268/4b031b44-2da9-48cf-bfb5-68928589c368">



### Reproduction link

https://stackblitz.com/edit/github-cyjyvh?file=src%2Fstories%2FButton.mdx

### Reproduction steps

I was able to reproduce it partly.

- Comment out the `Canvas` block int the **Button.mdx** file and observe the different value rendered in the `Canvas` block.

### System

```bash
System:
    OS: Windows 10 10.0.19045
    CPU: (24) x64 12th Gen Intel(R) Core(TM) i9-12900
  Binaries:
    Node: 21.1.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 4.3.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD <----- active
    npm: 10.2.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 126.0.6478.57
    Edge: Chromium (125.0.2535.92)
  npmPackages:
    eslint-plugin-storybook: 0.8.0 => 0.8.0
```


### Additional context

_No response_
Repository: next.js
Issue: [Testing with Playwright/MSW]: TypeError: _msw.MockedRequest is not a constructor
Labels: bug,Testing

### Link to the code that reproduces this issue

https://github.com/trm217/reproduction-nextjs-playwright-msw-issue

### To Reproduce

1. Install dependencies using `pnpm i`
2. Build the app using `pnpm build`
3. Execute the playwright test using `pnpm exec playwright test`. 

### Current vs. Expected behavior

I would expect the error `TypeError: _msw.MockedRequest is not a constructor` not to be thrown, as it doesn't allow using the testmode feature at all.

The error occurs when ever the import path given in [this example](https://github.com/vercel/next.js/blob/canary/packages/next/src/experimental/testmode/playwright/README.md) is used ([this file](https://github.com/trm217/reproduction-nextjs-playwright-msw-issue/blob/97b07e23321f6c263adc2591ddca2f10ea4077bc/tests/example.spec.ts#L5) in the reproduction).

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
Binaries:
  Node: 21.2.0
  npm: 10.2.3
  Yarn: 1.22.22
  pnpm: 9.1.0
Relevant Packages:
  next: 14.2.4 // Latest available version is detected (14.2.4).
  eslint-config-next: 14.2.4
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.2
Next.js Config:
  output: N/A
```


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

Testing

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

Other (Deployed)

### Additional context

_No response_
Repository: material-ui
Issue: [material-ui][Autocomplete] label cut off when the option list is displayed above.
Labels: bug 🐛,design: material,package: material-ui,component: autocomplete,RFC

### What's the problem?

- label cut when option list show upper side

[screen-capture (30).webm](https://github.com/mui/material-ui/assets/83221063/82ae59cc-f90f-464a-8757-d82bc9431015)


### What are the requirements?

_No response_

### What are our options?

_No response_

### Proposed solution

_No response_

### Resources and benchmarks

_No response_

**Search keywords**:
Repository: vscode
Issue: Accessible Hover View/Help contains yellow rectangles for certain whitespace characters like &nbsp, &emsp etc.
Labels: bug,verification-found,editor-hover

- Install the GitLens extension
- Hover on an editor line, some decorative text should appear to the right showing the last person who edited the line, the moment when it was edited and the commit message
- Hover on that text, an editor hover should appear
- Focus on a hover part of the editor hover
- Make the accessible hover view appear
- Notice that the accessible hover view contains yellow rectangles corresponding to the whitespace characters like &nbsp &emsp etc 🐛 

https://github.com/microsoft/vscode/assets/61460952/e4940367-93ad-4647-80e8-e6d80a74497b
Repository: godot
Issue: You cannot multi-select and multi-edit in the remote scene view
Labels: enhancement,topic:editor

### Tested versions

4.2.2.stable

### System information

Godot v4.2.2.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 Laptop GPU (NVIDIA; 31.0.15.4633) - AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16 Threads)

### Issue description

You cannot multi-select and multi-edit in the remote view. It only let's you select a single node at a time. 

I would expect to be able to select multiple nodes of the same type and edit them all in one go like I can in the scene view.

Not sure if this should be logged as a proposal? I would expect it to work, so it felt more like a bug.

### Steps to reproduce

Run a scene with multiple nodes. You cannot Ctrl/Shit select multiple nodes in the remote view.

### Minimal reproduction project (MRP)

NA