sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: [Color Picker] Window size issue
Labels: Issue-Bug,Area-User Interface,Severity-Regression,Needs-Triage,Product-Color Picker

### Microsoft PowerToys version

0.79.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

ColorPicker

### Steps to reproduce

Use a hotkey to open and pick a colour

### ✔️ Expected Behavior

Window size for the editor should be the same as it always was which fits the contents

![2024-03-12_972](https://github.com/microsoft/PowerToys/assets/17172994/d55517b7-712b-4a99-9b6e-e2c993e19550)


### ❌ Actual Behavior

After the initial use of the new UI, the size has changed and the window is now 3x the size it was. This takes up way too much space and for a window that uses 1/3 of that space. (not a fan of the new look either)

![2024-03-12_971](https://github.com/microsoft/PowerToys/assets/17172994/c2158e9a-3204-4cdd-ae12-c3222e17aaf7)

### Other Software

_No response_
Repository: material-ui
Issue: [material-ui][Chip] Disable blur() event on escape key should be opt-in
Labels: new feature,waiting for 👍,component: chip,package: material-ui

Hi! 👋 
      
Firstly, thanks for your work on this project! 🙂

Today I used [patch-package](https://github.com/ds300/patch-package) to patch `@mui/material@5.15.12` for the project I'm working on.

<!-- 🔺️🔺️🔺️ PLEASE REPLACE THIS BLOCK with a description of your problem, and any other relevant context 🔺️🔺️🔺️ -->

Here is the diff that solved my problem:

```diff
diff --git a/node_modules/@mui/material/Chip/Chip.js b/node_modules/@mui/material/Chip/Chip.js
index 5f9d12e..f0110dd 100644
--- a/node_modules/@mui/material/Chip/Chip.js
+++ b/node_modules/@mui/material/Chip/Chip.js
@@ -330,7 +330,7 @@ const Chip = /*#__PURE__*/React.forwardRef(function Chip(inProps, ref) {
       if (onDelete && isDeleteKeyboardEvent(event)) {
         onDelete(event);
       } else if (event.key === 'Escape' && chipRef.current) {
-        chipRef.current.blur();
+        // Commented out by httpete with patch-package chipRef.current.blur();
       }
     }
     if (onKeyUp) {
```

<em>This issue body was [partially generated by patch-package](https://github.com/ds300/patch-package/issues/296).</em>


**Search keywords**:
Repository: ant-design
Issue: Menu-只展开当前父级菜单 demo openKeys 处理错误
Labels: Inactive,unconfirmed

### Reproduction link

[https://ant-design.antgroup.com/components/menu-cn#menu-demo-sider-current](https://ant-design.antgroup.com/components/menu-cn#menu-demo-sider-current)

### Steps to reproduce

1. 点击 Navigation Two
2. 点击 Submenu
3. 再次点击 Submenu

### What is expected?

当再次点击 Submenu 后，Navigation Two 被收起了

### What is actually happening?

Navigation Two 不应该被收起

| Environment | Info |
| --- | --- |
| antd | 5.15.2 |
| React | latest |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->


这个问题是上次 https://github.com/ant-design/ant-design/issues/44221 改动导致的
Repository: vscode
Issue: Same crash when deleteing files thru vscode's explorer, like #91902
Labels: freeze-slow-crash-leak,windows,under-discussion

<!-- ⚠️⚠️ 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

<!-- 🪓 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.87.2 (user setup)
Commit: 863d2581ecda6849923a2118d93a088b0745d9d6
Date: 2024-03-08T15:20:17.278Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Windows_NT x64 10.0.19041 

Steps to Reproduce:

1. e.g i put vs/base/common folder in a project and just want to delete some unused files like "performance.js" and "performance.d.ts"
2. then it exit, unexpected.

i follow the steps here https://github.com/Microsoft/vscode/wiki/Native-Crash-Issues and crash report is here uploaded. hope it may help.

[crash.zip](https://github.com/microsoft/vscode/files/14582348/crash.zip)
Repository: ollama
Issue: Support ChatGLM3
Labels: model request

When I load the local ChatGLM3-6b model, I receive an error message，When I load the local ChatGLM3-6b model, I receive an error message. Can we support the following？
Repository: flutter
Issue: [Impeller] blur coverage computations are still incorrect.
Labels: P2,e: impeller,team-engine,triaged-engine

Perhaps we're not expanding the bounds enough? Look at the bottom of the screen


https://github.com/flutter/flutter/assets/8975114/c5f0a7bf-62bd-4e43-842b-849f96ccaa55




Example app:

```dart
import 'dart:ui';

import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: MyHomePage(title: 'Scrolling ios blur 3.19.1'),
    );
  }
}

class MyHomePage extends StatelessWidget {
  const MyHomePage({
    super.key,
    required this.title,
  });

  final String title;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      extendBody: true,
      extendBodyBehindAppBar: true,
      appBar: AppBar(
        backgroundColor: Theme.of(context).colorScheme.inversePrimary,
        title: Text(title),
      ),
      body: ListView.separated(
        itemCount: 20,
        itemBuilder: (_, i) => ImageFiltered(
            imageFilter: ImageFilter.blur(sigmaX: 25, sigmaY: 25),
            child: Image.network(
              'https://cdn.pixabay.com/photo/2018/03/31/19/29/schnitzel-3279045_1280.jpg',
              height: 200,
              fit: BoxFit.cover,
            ),
        ),
        separatorBuilder: (_, __) => const SizedBox(height: 80),
      ),
    );
  }
}
```
Repository: deno
Issue: Must wait for `Deno.Listener.accept` to reject after calling `Deno.Listener.close`
Labels: docs,ext/net

I've just discovered that after a call to `Deno.Listener.close`, if I attempt to call `Deno.listen` on the same port, I get `AddrInUse` error, and the best way I found to avoid this is to wait for any `Deno.Listener.accept` calls (or `Deno.Listener[Symbol.asyncIterator]`).

<details>
<summary>Example server code</summary>

```typescript
const server = Deno.listen({ port: 10000 });
server.accept().catch(() => {});
server.close();
Deno.listen({ port: 10000 }); //< AddrInUse
```
</details>

The only information I managed to find was on `Deno.Listener.close` which said 
>Any pending accept promises will be rejected with errors.

With the lack of documentation on the functions in question, I'm not able to determine if this is desired behaviour or not, so I've assumed it is. 

Is it possible to either:
* Change `Deno.Listener.close` to actually close the socket
* Change `Deno.listen` to wait for sockets that have been requested to close before opening
* Add/change documentation to explain this requirement, on one or more of these functions
Repository: vscode
Issue: Clicking on an output and using Up/Down arrows scrolls through cells of another notebook
Labels: bug,notebook

Have two or more notebooks open side by side
* Select a cell of notebook 1
* Set focus to an output of a cell in another notebook
    * Verify the new nb is selected (cell will be highlighted)
* Use up/down arrows
* Watch how cells in notebook 1  are highlighted instead of the nb that contains the output..
Repository: vscode
Issue: [Bug] MacOS: Multiline edit not functional in Safari, works well in Chrome
Labels: bug,editor-multicursor,safari

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 
- OS Version: 

Steps to Reproduce:

1. Print a few lines of code in Monaco editor in browser and press Option+Command+Up Arrow or Option+Command+Down Arrow
2. This should place multiline cursor and works well in Chrome, but not in Safari.
Repository: pytorch
Issue: Can’t save SparseTensor for custom device
Labels: module: sparse,triaged

### 🐛 Describe the bug

Our backend has support to create SparseTensor, but we find that SparseTensor in PrivateUse1 can not be saved directly, like:
```
import torch
a = torch.tensor([[0, 2.], [3, 0]]).to_sparse().to("privateuseone")
torch.save(a)
```
It will raise error `TypeError: can't convert Sparse layout tensor to numpy. Use Tensor.dense() first.`
I found that the following code was causing the problem:
https://github.com/pytorch/pytorch/blob/e99fa0042cd3dcd2eded24585d59c53f2da9d9f5/torch/_tensor.py#L262-L273
SparseTensor doesn't have storage, so above code will be running. And ` self.cpu().numpy()` will failed in  
https://github.com/pytorch/pytorch/blob/e99fa0042cd3dcd2eded24585d59c53f2da9d9f5/torch/csrc/utils/tensor_numpy.cpp#L133-L138

I think here are two ways to solve this problem, maybe you have other advice?
https://github.com/pytorch/pytorch/blob/e99fa0042cd3dcd2eded24585d59c53f2da9d9f5/torch/_tensor.py#L263-L264
1. Delete the branch judgment in the _tensor.py and let PrivateUse1 goto the follow branchs like other devices
2. Add is_sparse, is_neg, to the branch judgment for PrivateUse1, because `numpy()` cannot handle these tensors

### Versions

torch/main

cc @alexsamardzic @nikitaved @pearu @cpuhrsch @amjames @bhosmer @jcaip
Repository: PowerToys
Issue: PowerToys Run is flashing white when typing w/ dark mode
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage

### Microsoft PowerToys version

0.79.0

### Installation method

WinGet

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

1. Open PowerToys Run
2. Type something that return result

https://github.com/microsoft/PowerToys/assets/75104667/1cd4c28d-5722-414d-a18e-a1e384947332


3. PowerToys will flash w/ white background





### ✔️ Expected Behavior

PowerToys Run should not flash or flash w/ dark background (Assuming that you set a Dark Theme)

### ❌ Actual Behavior

PowerToys flash w/ white background causing user's eye to blind for a short period of time

### Other Software

_No response_
Repository: vscode
Issue: Test API: test run profiles - workspace folder scope?
Labels: under-discussion,testing

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Unless I've missed something in the API, I'm wondering if test run profiles should have an optional "workspace folders scope" out-of-the-box? 
i.e. an array of workspace folders that the run profile will execute against.

Something like this:
```typescript
const workspaceFolderScopeArray = ["workspace folder 1", "workspace folder 2"];
const runProfile = ctrl.createRunProfile("my run profile", profileKind, workspaceFolderScopeArray, 
  async (request: vscode.TestRunRequest) => { 
     // vscode will PRE-FILTER request.tests to only include test uris are within workspaceFolderScopeArray
    await myRunHandler(request);
});
```

Use cases (all multi-root):
- A test extension has a standard run profile. When the user clicks the run all tests button with the standard run profile the test extension author has to assume that the profile will work against all workspace folders, some of which may error out.
- A test extension allows a user to provide their own customised version of a runner, e.g. command line arguments or a custom script, via `settings.json`. The extension will convert this into a run profile, but only the user knows which workspace folders that custom run profile will work with.
- The user may wish to limit certain run profiles to certain workspace folders for their own (unknown) reasons.

Current state:
- The extension developer can provide the ability for a user to specify via extension-specific `settings.json` settings which workspace folders scope they want the runProfile to execute against.
- The extension developer can then implement something themselves to filter the tests that are run to the required workspace folders scope.
- However, the extension developer _cannot_ stop the UI from providing "Execute run profile" on workspace folders that should never use that run profile. They can only stop tests from being run.

So it's really only a UI concern, but I'm just wondering if it's a _common enough use case_ that the test filtering/UI update should be provided out-of-the-box by `vscode.TestRunProfile`?
Because run profiles are at the vscode instance-level, it does create some interesting side-effects if the user cannot scope the run profiles to certain workspace folders. 

My question is - should the ability to scope the run profiles to certain workspace folders be implemented by the extension developer or provided out of the box?
Repository: angular
Issue: Add observed property to OutputEmitterRef
Labels: feature,area: core,core: inputs / outputs

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

With the `@Output` decorator, I used to check the `observed` of the `EventEmitter` (because it inherits `Subject`) to enable/disable some features.

For example, `<lu-select (clueChange)="..." />` would display a search bar in `LuSelect` component but `<lu-select />` would not.

This solution seems elegant as it avoid an additional input that would lead to unwanted cases:

- Both `<lu-select enableClue (clueChange)="..." />` and `<lu-select />` would work
- `<lu-select (clueChange)="..." />` would be useless because the search bar is not disabled because `enableClue = false`
- `<lu-select enableClue />` would be useless because the search bar is displayed, but nobody listen to its value

### Proposed solution

Add a `getter`property `observed` in [OutputEmitterRef](https://angular.dev/api/core/OutputEmitterRef)

([in this file](https://github.com/angular/angular/blob/edc1740d7e7f0296c719c7176c24031f55ae1487/packages/core/src/authoring/output/output_emitter_ref.ts#L33))

```ts
export class OutputEmitterRef<T> implements OutputRef<T> {
  private listeners: Array<(value: T) => void>|null = null;

  get observed(): boolean {
    return !!this.listeners?.length;
  }

  //...
}
```

### Alternatives considered

Replace existing usages of `emitter.observed` by inputs.
Repository: storybook
Issue: [Bug]: `composeStory` does not override parameters
Labels: bug,documentation,sev:S2,portable stories,test utilities

### Describe the bug

According to the documentation, `composeStory` can be used to override story parameters during unit testing. Sadly, it is not the case.

```ts
const UnitTestButton = composeStory(Primary, MetaButton, {
  parameters: {
    layout: 'full', // initial value : 'centered'
    foo: 'baz'
  }
});

// UnitTestButton.parameters.layout === 'centered'
```

### To Reproduce

https://stackblitz.com/edit/github-b6bbz5?file=package.json,src%2Fstories%2FButton.spec.tsx,src%2Fstories%2FButton.stories.ts,package-lock.json&preset=node

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.18.0 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.3 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.1.0-alpha.1 => 8.1.0-alpha.1 
    @storybook/addon-interactions: ^8.1.0-alpha.1 => 8.1.0-alpha.1 
    @storybook/addon-links: ^8.1.0-alpha.1 => 8.1.0-alpha.1 
    @storybook/addon-onboarding: ^8.1.0-alpha.1 => 8.1.0-alpha.1 
    @storybook/blocks: ^8.1.0-alpha.1 => 8.1.0-alpha.1 
    @storybook/react: ^8.1.0-alpha.1 => 8.1.0-alpha.1 
    @storybook/react-vite: ^8.1.0-alpha.1 => 8.1.0-alpha.1 
    @storybook/test: ^8.1.0-alpha.1 => 8.1.0-alpha.1 
    storybook: ^8.1.0-alpha.1 => 8.1.0-alpha.1
```


### Additional context

_No response_
Repository: godot
Issue: Opening window-node makes me lose -10fps in compability mode
Labels: bug,enhancement,topic:rendering,performance

### Tested versions

Reproducible in godot 4.0-4.3 dev4

### System information

Windows 11, Compatibility mode

### Issue description

I try to target my game for older devices or laptops without dGPU. 

My game opens another window with the window-node (embedded subwindows are off.) Without opening another window the game runs smoothly 60fps. With window the game fps drops to 50fps.

This is without opening window:
![image](https://github.com/godotengine/godot/assets/81559157/1c23c268-c999-4596-99fa-a72f2f5ccae9)

And this is with window opened:
![image](https://github.com/godotengine/godot/assets/81559157/9fa6c9c2-8a0a-40d8-8d7c-667a7f421db7)

The code for the opening window is here:
```
extends Control

const CONTROL_PANEL: PackedScene = preload("res://window.tscn")
func _ready():
	var _scene = CONTROL_PANEL.instantiate()
	
	_scene.title = "Control panel"
	self.add_child(_scene)
```
Without vsync, my fps is around 1400 but will cause a lot of stuttering (Even if I cap fps to 60.

This is only reproducible in compatibility mode. Forward+ won't make this. I'm running this with intel 12th igpu for testing purposes. Somehow my RTX 3060 can handle the 2 windows. 

This problem makes my game not suitable for older laptops even if it's a very simple game.




### Steps to reproduce

Run with igpu and make project compatibility mode. 
1. Make the main scene and window scene (Just Godot sprite in both).

Main scene: 
```
const CONTROL_PANEL: PackedScene = preload("res://window.tscn")
func _ready():
	var _scene = CONTROL_PANEL.instantiate()
	
	_scene.title = "Control panel"
	self.add_child(_scene)
```


### Minimal reproduction project (MRP)

[MRP.zip](https://github.com/godotengine/godot/files/14585751/MRP.zip)
Repository: PowerToys
Issue: Use Chords in the Send Action Shortcut
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

The recent addition of chords in the keyboard manager section is great! I think it would also make sense to have an option for the send action to also be a chord. But im not sure if I understand the use case of this stuff properly. 

### Scenario when this would be used?

I have in mind using it for Excel which has a lot of Alt + H, and then a long list of options throughout the ribbon. As seen below:
![image](https://github.com/microsoft/PowerToys/assets/163288015/3a5854a2-ada6-4db0-bf36-aad325b6f9ef)


### Supporting information

I've wanted a way to be able to remap complicated excel shortcuts that have chords for a long time. I would imagine others would have similar use cases. 

thank you for everything you do. Power Toys is an unbelievable project!
Repository: ant-design
Issue: Slider 滑动输入条配置完大小颜色，初始化之后hover上去会抖动
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-ri1rum?file=demo.tsx,index.css)

### Steps to reproduce

设置纯黑色滑块
``` tsx
    <ConfigProvider
      theme={{
        components: {
          Slider: {
            handleSize: 16,
            handleActiveColor: '#000',
            handleColor: '#000',
            trackBg: '#000',
            trackHoverBg: '#000',
          },
        },
      }}
    >
      <Slider tooltip={{ formatter: null }} />
    </ConfigProvider>
```
然后把滑块after也设置为黑色
``` css
.ant-slider .ant-slider-handle::after {
  background-color: #000;
}
```

### What is expected?

没有轻微抖动

### What is actually happening?

初始化之后hover上去有轻微抖动

| Environment | Info |
| --- | --- |
| antd | 5.15.1 |
| React | react |
| System | macOS 14.3 |
| Browser | 版本 122.0.6261.112 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: excalidraw
Issue: New Slides are empty
Labels: E+/presentations

Hi there,

I just created some new slides, but they appear empty within the slides overview and when running presentation mode :-(

<img width="2051" alt="Bildschirmfoto 2024-03-13 um 11 10 58" src="https://github.com/excalidraw/excalidraw/assets/219704/96234838-eb7c-460c-bb6f-2a15c4bce121">
Repository: storybook
Issue: [Bug]: Vue3-vite autodocs with docgen 'vue-component-meta' does no longer work with `defineSlots`
Labels: bug,vue3,sev:S3,docgen

### Describe the bug

When using the new `vue-component-meta` to generate the docs page of a story it will break when you do that with a component that uses `defineSlots`.  

In the reproduction I created two stories, ButtonSlots and Button. The one which has slots shows these docs:
![image](https://github.com/storybookjs/storybook/assets/5757159/891430b9-350f-42b4-a8bf-c612a2eb7033)
Notice it is missing meta information such as doc comments and default values. It will only show what you are using in the stories or defining in `args`/`argTypes` it seems.

The one without defineSlots looks like this:
![image](https://github.com/storybookjs/storybook/assets/5757159/61b58e01-3ed2-476c-a5f8-baac35c02151)

**Also secondary issue**: HMR will not work for regenerating these autodocs. Only a hard restart of the server will generate updated autodocs, which does not result in a very good DX. If you want to reproduce the issue beware of this :)

### To Reproduce

https://stackblitz.com/edit/github-admhcw?file=src%2Fstories%2FButton2.vue

### System

_No response_

### Additional context

_No response_