sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [Flutter] Make the framework aware of which view has focus and publish changes through the platform dispatcher. 
Labels: c: new feature,framework,c: proposal,f: focus,P3,team-framework,triaged-framework

### Use case

https://github.com/flutter/flutter/pull/143259 introduced handlers for Apps to respond to platform focus changes. We now need a mechanism to track which view currently has focus and notify the engine when focus shifts so the platform focus can be adjusted accordingly.

### Proposal

My initial suggestion is to implement a simple view focus tracker utility. This would keep track of the currently focused view and inform the engine whenever focus changes through `PlatformDispatcher.requestViewFocusChange` calls. 

A naive POC that works when there is only a single view in the app: https://github.com/tugorez/flutter/commit/5d302b86f1f9e85721db186e6868737aa60cc9d5
Repository: flutter
Issue: Upgrade remaining chromium bots in each pool to macOS 14.5
Labels: team-infra,P2,triaged-infra

### Type of Request

infra task

### Infrastructure Environment

Devicelab

### What is happening?

Prerequisites

- [ ] https://github.com/flutter/flutter/issues/148887 has been landed for 1-2 releases
- [ ] Ensure no open issues in https://github.com/flutter/flutter/issues/148882
- [x] https://github.com/flutter/flutter/issues/149830

---

Upgrade all remaining bots to macOS 14.5 per arch per pool

- [ ] [Try pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=os&c=status&d=asc&f=device_os%3Anone&f=pool%3Aluci.flutter.try&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Try pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=os&c=status&d=asc&f=device_os%3Anone&f=pool%3Aluci.flutter.try&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)
- [ ] [Staging pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=os&c=status&d=asc&f=device_os%3Anone&f=pool%3Aluci.flutter.staging&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Staging pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=os&c=status&d=asc&f=device_os%3Anone&f=pool%3Aluci.flutter.staging&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)
- [ ] [Prod pool - arm64 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=os&c=status&d=asc&f=device_os%3Anone&f=pool%3Aluci.flutter.prod&f=cpu%3Aarm&f=os%3AMac&k=os&s=id)
- [ ] [Prod pool - x86 bots](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=os&c=status&d=asc&f=device_os%3Anone&f=pool%3Aluci.flutter.prod&f=cpu%3Ax86&f=os%3AMac&k=os&s=id)

When ready to upgrade, file an issue with a list of explicit bots listed by name to upgrade. See b/326078082 as example. Include request to ensure the Flutter Devicelab cert is installed as well after reimage in the issue.

### Steps to reproduce

_No response_

### Expected results

_No response_
Repository: vscode
Issue: Cannot read properties of undefined (reading 'getViewLineMinColumn')
Labels: bug,error-telemetry

```javascript
TypeError: Cannot read properties of undefined (reading 'getViewLineMinColumn')
at b.getViewLineMinColumn in src/vs/editor/common/viewModel/viewModelLines.ts:735:62
at m.getLineMinColumn in src/vs/editor/common/viewModel/viewModelImpl.ts:681:22
at p.update in src/vs/editor/common/viewModel/viewModelImpl.ts:1166:126
at m.setViewport in src/vs/editor/common/viewModel/viewModelImpl.ts:657:23
at Object.renderText in src/vs/editor/browser/view.ts:486:29
at Object.renderText in src/vs/editor/browser/view.ts:426:23
at <anonymous> in src/vs/editor/browser/view.ts:743:47
at func in src/vs/editor/browser/view.ts:676:10
at safeInvokeNoArg in src/vs/editor/browser/view.ts:743:15
at R.ee [as d] in src/vs/editor/browser/view.ts:726:10
at R.execute in src/vs/base/browser/dom.ts:325:9
at dt in src/vs/base/browser/dom.ts:366:8
at animationFrameRunner in src/vs/base/browser/dom.ts:384:45
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=dc96b837cf6bb4af9cd736aa3af08cf8279f7685&bH=6979a0a4-9d64-5063-ddce-8b1faed98b7f)
Repository: rust
Issue: Tracking Issue for externally implementable items
Labels: T-lang,C-tracking-issue,B-experimental,F-extern_item_impls

This is a tracking issue for the lang **experiment** on externally implementable items.  This currently covers these proposals:

- https://github.com/rust-lang/rfcs/pull/3632
- https://github.com/rust-lang/rfcs/pull/3635
- https://github.com/rust-lang/rfcs/pull/3645
- https://github.com/rust-lang/rfcs/pull/2492

The feature gate for the issue is `#![feature(extern_item_impls)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.  They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.  A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.  Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

- [x] Get alternate proposals.
  - [x] Original proposal from @m-ou-se. https://github.com/rust-lang/rfcs/pull/3632
  - [x] Alternative proposal from @m-ou-se. https://github.com/rust-lang/rfcs/pull/3635
  - [x] Alternative proposal from @Amanieu. https://github.com/rust-lang/rfcs/pull/3645
  - [x] Alternative proposal from @tmandry. https://github.com/rust-lang/rfcs/pull/3632#issuecomment-2125972702
- [x] Pick a design for the experiment.
  - Using attributes rather than new syntax: https://github.com/rust-lang/rust/issues/125418#issuecomment-2360542039
- [x] Submit project goal: https://github.com/rust-lang/rust-project-goals/pull/198
  - [ ] Approval
- [ ] Implement the experiment.
   - [x] First fix attributes so we can do name resolution in them: https://github.com/rust-lang/compiler-team/issues/796
   - [ ] Implement externally implementable items using attributes. (In progress!)
- [ ] Verify proposals are consistent with:
  - https://github.com/rust-lang/rfcs/pull/3484
- [ ] Write/update RFC based on experiment.
- [ ] Accept an RFC.
- [ ] Add documentation to the [dev guide][].
    - See the [instructions][doc-guide].
- [ ] Add documentation to the [reference][].
    - See the [instructions][reference-instructions].
- [ ] Add formatting for new syntax to the [style guide][].
    - See the [nightly style procedure][].

[dev guide]: https://github.com/rust-lang/rustc-dev-guide
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly style procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md
[reference]: https://github.com/rust-lang/reference
[reference-instructions]: https://github.com/rust-lang/reference/blob/master/CONTRIBUTING.md
[style guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions

- Which exact alternative or alternatives should we adopt?

### Related

- https://github.com/rust-lang/rfcs/pull/3632
- https://github.com/rust-lang/rfcs/pull/3635
- https://github.com/rust-lang/rfcs/pull/3645
- https://github.com/rust-lang/rfcs/pull/2492

### Implementation history

TODO.

cc @m-ou-se @Amanieu @tmandry @joshtriplett
Repository: flutter
Issue: Upgrade 50% of bots in dart-internal to macOS 14.5
Labels: team-release

### Type of Request

infra task

### Infrastructure Environment

Devicelab

### What is happening?

Prerequisites
- [x] https://github.com/flutter/flutter/issues/148871
- [x] https://github.com/flutter/flutter/issues/148873
- [x] https://github.com/flutter/flutter/issues/148879
- [x] https://github.com/flutter/flutter/issues/148891 has been landed for 1-2 releases
- [ ] https://github.com/flutter/flutter/issues/148887
- [ ] Ensure no open issues in https://github.com/flutter/flutter/issues/148882

--- 
Upgrade 50% of bots per arch in `luci.dart-internal.flutter` to macOS 14.5.

- [ ] [arm64 bots](https://chrome-swarming.appspot.com/botlist?c=id&c=task&c=cpu&c=os&c=status&d=asc&f=pool%3Aluci.dart-internal.flutter&f=os%3AMac&f=cpu%3Aarm&k=cpu&s=id)
- [ ] [x86 bots](https://chrome-swarming.appspot.com/botlist?c=id&c=task&c=cpu&c=os&c=status&d=asc&f=pool%3Aluci.dart-internal.flutter&f=os%3AMac&f=cpu%3Ax86&k=cpu&s=id)

When ready to upgrade, file an issue with a list of explicit bots listed by name to upgrade. See b/326078082 as example. Include request to ensure the Flutter Devicelab cert is installed as well after reimage in the issue.

### Steps to reproduce

_No response_

### Expected results

_No response_
Repository: flutter
Issue: ☂️ Tracking issue for any infra or test failures with Xcode 16 and iOS 18 Simulators
Labels: P2,team-ios,triaged-ios

## Test failures:

### flutter/flutter

- [x] https://github.com/flutter/flutter/issues/151553
  - [x] https://github.com/flutter/flutter/pull/153116
- [x] https://github.com/flutter/flutter/issues/152983 
  - This will not require a cherry-pick since the PR that caused it is only in master https://github.com/flutter/flutter/pull/152347

### flutter/packages

- [x] https://github.com/flutter/flutter/issues/150391
- [x] https://github.com/flutter/flutter/issues/150448
- [x] https://github.com/flutter/flutter/issues/150943
- [x] https://github.com/flutter/flutter/issues/151467
- [x] https://github.com/flutter/flutter/issues/150220
- [x] https://github.com/flutter/flutter/issues/152970
- [ ] ~~https://github.com/flutter/flutter/issues/153578~~
  - Issue also exists on macOS 13 and Xcode 15, so not specific to Xcode 16, and therefore not a blocker.

### flutter/engine

- [x] https://github.com/flutter/flutter/issues/152990
  - This will not require a cherry-pick since the failing test only exists on main https://github.com/flutter/engine/pull/54119


## Infra Issues:

- [ ]
Repository: flutter
Issue: Run all flutter/flutter macOS tests using Xcode 16 and iOS 18 simulator
Labels: P2,team-ios,triaged-ios

## Prerequisites

- [ ]  Xcode 16 is available in [CIPD](https://chrome-infra-packages.appspot.com/p/infra_internal/ios/xcode)
- [ ]  https://github.com/flutter/flutter/issues/148881 (assuming Xcode 16 requires macOS 14.5)
  - If Xcode 16 requires a higher macOS version, bots will need to be upgraded to new required version before doing 
- [ ]  https://github.com/flutter/flutter/issues/148891 (assuming Xcode 16 requires macOS 14.5)
  - If Xcode 16 requires a higher macOS version, bots will need to be upgraded to new required version before doing 

## Instructions to run via led
[Update to latest depot_tools](https://chromium.googlesource.com/chromium/tools/depot_tools/+/HEAD/README.md#updating) by running gclient:

To run manual led test on a Mac-14 staging bot:

1. `led get-builder "luci.flutter.staging:Mac channels_integration_test" > properties.json`
2. Replace `"sdk_version": "15a240d"` with new Xcode build version (case sensitive with CIPD version)
3. `cat properties.json | led edit -d os=Mac-14 | led edit-recipes-bundle | led launch`

❗ File issues for tests that fail and add links to the issues in https://github.com/flutter/flutter/issues/148898. This is important so we can track any fixes that need to be cherrypicked to beta/stable and so steps that are steps are not completed before issues are resolved.

## Instructions to run via PR

If you run via PR, you can make a PR that changes the .ci.yaml to use the new Xcode build version and run exclusively on macOS 14. Note that not all tests run in presubmit, so you'll likely need to do some of them via `led` or edit the .ci.yaml to run the tests in presubmit.

https://github.com/flutter/flutter/blob/master/.ci.yaml

```diff
$flutter/osx_sdk : >-
        {
-          "sdk_version": "15a240d"
+          "sdk_version": "[insert new CIPD case-sensitive Xcode build version]"
        }
        
- os: Mac-13|Mac-14
+ os: Mac-14

- ["device_os=iOS-17","os=Mac-13|Mac-14", "cpu=x86"]
+ ["device_os=iOS-17","os=Mac-14", "cpu=x86"]
```

❗ File issues for tests that fail and add links to the issues in https://github.com/flutter/flutter/issues/148898. This is important so we can track any fixes that need to be cherrypicked to beta/stable and so steps that are steps are not completed before issues are resolved.
Repository: flutter
Issue: Run all flutter/packages macOS tests using Xcode 16 and iOS 18 simulator
Labels: P2,team-ios,triaged-ios

## Prerequisites

- [ ] Xcode 16 is available in [CIPD](https://chrome-infra-packages.appspot.com/p/infra_internal/ios/xcode)
- [ ] https://github.com/flutter/flutter/issues/148891 (assuming Xcode 16 requires macOS 14.5)
  - If Xcode 16 requires a higher macOS version, bots will need to be upgraded to new required version before doing this

## Instructions

Make a PR that changes the .ci.yaml to use the new Xcode build version and run exclusively on macOS 14. Note that not all tests run in presubmit, so you'll likely need to do some of them via led or edit the .ci.yaml to run the tests in presubmit.

https://github.com/flutter/packages/blob/main/.ci.yaml

```diff
$flutter/osx_sdk : >-
        {
-          "sdk_version": "15a240d"
+          "sdk_version": "[insert new CIPD case-sensitive Xcode build version]"
        }
        
- os: Mac-13|Mac-14
+ os: Mac-14
```

https://github.com/flutter/packages/blob/main/.ci/scripts/create_simulator.sh
```diff
- readonly OS=com.apple.CoreSimulator.SimRuntime.iOS-17-0
+ readonly OS=com.apple.CoreSimulator.SimRuntime.iOS-18-0
```

https://github.com/flutter/packages/blob/main/.ci/targets/ios_platform_tests.yaml
```diff
- args: ["native-test", "--ios", "--ios-destination", "platform=iOS Simulator,name=Flutter-iPhone,OS=17.0"]
+ args: ["native-test", "--ios", "--ios-destination", "platform=iOS Simulator,name=Flutter-iPhone,OS=18.0"]
```

https://github.com/flutter/packages/blob/main/packages/pigeon/tool/shared/test_suites.dart
```diff
-  const String deviceRuntime = 'com.apple.CoreSimulator.SimRuntime.iOS-17-0';
-  const String deviceOS = '17.0';
+  const String deviceRuntime = 'com.apple.CoreSimulator.SimRuntime.iOS-18-0';
+  const String deviceOS = '18.0';
```

To run tests using `led`, such as for tests that don't run in presubmit, you can use a command like the following to test against the PR:

1. `led get-builder "luci.flutter.staging:Mac_arm64 ios_platform_tests_shard_3 stable" > properties.json`
2. Replace `"sdk_version": "15a240d"` with new Xcode build version (case sensitive with CIPD version)
3. `cat properties.json | led edit -d os=Mac-14 | led edit -pa git_ref='refs/pull/[insert PR id]/head' | led edit -pa git_url='https://github.com/flutter/packages | led edit-recipes-bundle | led launch`

❗ **File issues for tests that fail and add links to the issues in https://github.com/flutter/flutter/issues/148898**. This is important so we can track any fixes that need to be cherrypicked to beta/stable and so steps that are steps are not completed before issues are resolved.
Repository: godot
Issue: get_system_dir does not return correct media folders in Android
Labels: platform:android,topic:porting

### Tested versions

Tested on 4.2.2

### System information

Tested on Android 11 and Android 14

### Issue description

Calling OS::get_system_dir(dir = SystemDir::SYSTEM_DIR_PICTURES,  shared_storage = false) on Android returns the following path:
/storage/emulated/0/Android/data/org.godotengine.gamename/files/Pictures

This is not a very useful location, as files stored in this location are not visible in the phone's gallery and are in general not accessible for the user.

If instead a path on media is used, the pictures are available in the gallery and are accessible to the user. I am currently hardcoding the following path and it works correctly:
/storage/emulated/0/Android/media/org.godotengine.gamename/gamename

I'm don't have much knowledge in Android, but I think this should be the path returned by the get_system_dir function.

### Steps to reproduce

Print the returned value of OS::get_system_dir(SYSTEM_DIR_PICTURES) in an Android phone.

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: Power Toy Run - Just curser on the screen and not results
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.81.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

use shortcut to open, just see larger curser no box, and when I type I see no results

### ✔️ Expected Behavior

To see the box and results for what I type

### ❌ Actual Behavior

use shortcut to open, just see larger curser no box, and when I type I see no results

### Other Software

N/A
Repository: flutter
Issue: Resolve issue with Android code provided on 'Writing custom platform-specific code' page
Labels: platform-android,P2,team-android,triaged-android

Page URL: https://docs.flutter.dev/platform-integration/platform-channels
Page source: https://github.com/flutter/website/tree/master/src/docs/development/platform-integration/platform-channels.md

Description of issue:

Currently, this code is not working anymore for Android (Java or Kotlin) as mostly there is no more method `onCreate` is there, and the `MainActivity` type has been changed to use 

```
import io.flutter.embedding.android.FlutterActivity;
import io.flutter.embedding.engine.FlutterEngine;
```

instead of 
`import io.flutter.app.FlutterActivity;`

And I got an error for `getFlutterView() is not defined`
Any Suggestion?
Repository: flutter
Issue: Run all flutter/engine macOS tests using Xcode 16 and iOS 18 simulator
Labels: P2,team-ios,triaged-ios

## Prerequisites

- [ ] Xcode 16 is available in [CIPD](https://chrome-infra-packages.appspot.com/p/infra_internal/ios/xcode)
- [ ] https://github.com/flutter/flutter/issues/148891 (assuming Xcode 16 requires macOS 14.5)
  - If Xcode 16 requires a higher macOS version, bots will need to be upgraded to new required version before doing this

## Instructions

Make a PR that changes the .ci.yaml to use the new Xcode build version and run exclusively on macOS 14. Note that not all tests run in presubmit, so you'll likely need to do some of them via led or edit the .ci.yaml to run the tests in presubmit.

https://github.com/flutter/engine/blob/main/.ci.yaml

```diff
$flutter/osx_sdk : >-
        {
-          "sdk_version": "15a240d"
+          "sdk_version": "[insert new CIPD case-sensitive Xcode build version]"
        }
        
- os: Mac-13|Mac-14
+ os: Mac-14
```

https://github.com/flutter/engine/blob/main/ci/builders/local_engine.json
https://github.com/flutter/engine/blob/main/ci/builders/mac_android_aot_engine.json
https://github.com/flutter/engine/blob/main/ci/builders/mac_host_engine.json
https://github.com/flutter/engine/blob/main/ci/builders/mac_ios_engine.json
https://github.com/flutter/engine/blob/main/ci/builders/mac_unopt_debug_no_rbe.json
```diff
$flutter/osx_sdk : >-
        {
-          "sdk_version": "15a240d"
+          "sdk_version": "[insert new CIPD case-sensitive Xcode build version]"
        }
        
- os=Mac-13|Mac-14
+ os=Mac-14
```

https://github.com/flutter/engine/blob/main/ci/builders/mac_unopt.json
```diff
$flutter/osx_sdk : >-
        {
          "runtime_versions": [
-               "ios-17-0_15a240d"
+               "ios-18-0_[insert new CIPD case-sensitive Xcode build version]"
          ],
-          "sdk_version": "15a240d"
+          "sdk_version": "[insert new CIPD case-sensitive Xcode build version]"
        }
        
- os=Mac-13|Mac-14
+ os=Mac-14
```

https://github.com/flutter/engine/blob/main/testing/scenario_app/run_ios_tests.sh
```diff
- readonly OS_RUNTIME=com.apple.CoreSimulator.SimRuntime.iOS-17-0
- readonly OS="17.0"
+ readonly OS_RUNTIME=com.apple.CoreSimulator.SimRuntime.iOS-18-0
+ readonly OS="18.0"
```

In addition, golden files will need to be updated. See https://github.com/flutter/engine/pull/49833 as example


❗ **File issues for tests that fail and add links to the issues in https://github.com/flutter/flutter/issues/148898**. This is important so we can track any fixes that need to be cherrypicked to beta/stable and so steps that are steps are not completed before issues are resolved.
Repository: flutter
Issue: Update .ci.yaml in flutter/flutter to use Xcode 16 and macOS 14
Labels: P2,team-ios,triaged-ios

Prerequisites

- [ ] https://github.com/flutter/flutter/issues/148899
- [ ] https://github.com/flutter/flutter/issues/148888 (assuming Xcode 16 requires macOS 14.5)
  - If Xcode 16 requires a higher macOS version, bots will need to be upgraded to new required version before doing 
- [ ] https://github.com/flutter/flutter/issues/148892 (assuming Xcode 16 requires macOS 14.5)
  - If Xcode 16 requires a higher macOS version, bots will need to be upgraded to new required version before doing 
- [ ] Ensure no open issues in https://github.com/flutter/flutter/issues/148898 under flutter/flutter

--- 

https://github.com/flutter/flutter/blob/master/.ci.yaml
```diff
$flutter/osx_sdk : >-
        {
-          "sdk_version": "15a240d"
+          "sdk_version": "[insert new CIPD case-sensitive Xcode build version]"
        }
        
- os: Mac-13|Mac-14
+ os: Mac-14

- ["device_os=iOS-17","os=Mac-13|Mac-14", "cpu=x86"]
+ ["device_os=iOS-17","os=Mac-14", "cpu=x86"]
```
Repository: pytorch
Issue: function signature for multiprocessing.spawn is multiprocessing.spawn.spawn
Labels: oncall: distributed,triaged

### 📚 The doc issue

Today the doc for multiprocessing.spawn has the function signature as `multiprocessing.spawn.spawn()`, which is wrong. This is because the actual `spawn` method is written in the file `spawn.py` and got re-exposed in `multiprocessing`. Now the function name `spawn` shadows the module name `spawn` (because of file `spawn.py`) and Sphinx is confused.

### Suggest a potential alternative/fix

_No response_

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @chauhang @d4l3k
Repository: electron
Issue: [Bug]: GNU/Linux/Fedora/KDE: file selection dialog doesn't work
Labels: platform/linux,bug :beetle:,has-repro-gist,29-x-y,30-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

29.4.0

### What operating system are you using?

Other Linux

### Operating System Version

Fedora 38

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

The file(s) highlighted in a file selection dialog should be communicated to the application.

### Actual Behavior

The file(s) marked in a file selection dialog are not communicated to the application.

### Testcase Gist URL

_No response_

### Additional Information

When under GNU/Linux/Fedora/KDE, for example, "electron https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file" is executed and the file selection dialog is started, the file selection is not reported back to the application. When the file selection dialog is confirmed, it appears as if no file has been selected. This prevents, for example, files from being selected or saved in "Signal Desktop".

Used software versions:
KDE Plasma: 5.27.11
KDE Frameworks: 5.115.0
Qt: 5.15.12

Some analyses on this issue were conducted under "https://bugzilla.suse.com/show_bug.cgi?id=1224940".
Repository: terminal
Issue: The "Move pane, tab index..." and "Resize pane..." commands should be nested in the palette
Labels: Issue-Bug,Product-Terminal,Area-CmdPal

If you just type "pane" in the cmdpal, there's entirely too many entries. Too. Much. Let's just nest them.