sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Some CSSProperties are interpreted as objects, when they should be enums/strings
Labels: bug,needs triage

### Describe the bug

Some types from `CSSProperties` are interpreted as objects in the controls, when they should be string-like.

I understand why this issue happens, but since this is applied to many CSS properties, I don't want to override the controls every time (especially manually setting the options).


### To Reproduce

Add a prop that uses `(string & {})`in addition to other specified string. Example:

```
alignItems: CSSProperties['alignItems']
```
Compare this to a property that does not have `(string & {})`:
```
direction: CSSProperties['flexDirection']
```
![image](https://github.com/storybookjs/storybook/assets/1438972/faecc5dd-cd25-4e4b-abcd-da880c646930)


### System

```shell
Storybook 7.0.10
Environment Info:

  System:
    OS: macOS 13.3.1
    CPU: (8) arm64 Apple M1
  Binaries:
    Node: 18.16.0 - /usr/local/bin/node
    Yarn: 3.6.0 - /usr/local/bin/yarn
    npm: 9.5.1 - /usr/local/bin/npm
  Browsers:
    Safari: 16.4
```


### Additional context

Info on why `(string & {})` is used https://stackoverflow.com/questions/61047551/typescript-union-of-string-and-string-literals

[Example typed CSS property](https://github.com/frenic/csstype/blob/46694defae2cf3386218d0000490b0d0ac385aa6/index.d.ts#L18464)
Repository: electron
Issue: [Feature Request]: Add onClose event for BrowserWindow previewFile API
Labels: enhancement :sparkles:,component/BrowserWindow

### 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 feature request that matches the one I want to file, without success.

### Problem Description

In macOS, I use electron `previewFile` api to preview image, it will open a quick look window which it's good.

But I also want to detect quick look window has manully closed for my business logic, I try to find out electron documentation but can't find any callback events for quick look window.

### Proposed Solution

Add a `onClose` callback for quick look window, it will triggered when quick look window closed.

### Alternatives Considered

or is there any other way can detect quick look window closed?

### Additional Information

_No response_
Repository: next.js
Issue: Client components not interactive
Labels: Upstream,bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.1.0: Sun Oct  9 20:15:09 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T6000
    Binaries:
      Node: 17.1.0
      npm: 8.1.2
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant Packages:
      next: 13.4.19
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/AaronVr/nextjs-client-component-bug

### To Reproduce

1. Start with the base Next.js project with default settings
2. Create a new file called `app/counter.tsx`
3. Create the following client component within `app/counter.tsx`:
```
'use client'
 
import { useEffect, useState } from 'react'
 
export default function Counter() {
  const [count, setCount] = useState(0)

  useEffect(() => {
    console.log('In use effect.')
  }, [])
 
  return (
    <div>
      <p>You clicked {count} times</p>
      <button onClick={() => {console.log(count); setCount(count + 1);}}>Click me</button>
    </div>
  )
}
```
4. Create the following server component in `app/page.tsx`:
```
import Counter from "./counter";

/** Add your relevant code here for the issue to reproduce */
export default function Home() {
  return <main>
    <Counter/>
  </main>
}
```
5. Execute `npm run dev` and open in browser. 
6. Look at the browser console: the `useEffect` did not print anything to the console.
7. Click the 'Click me' button to increment the counter. 
8. The counter does not increment.

### Describe the Bug

When creating the following client component:
```
'use client'
 
import { useEffect, useState } from 'react'
 
export default function Counter() {
  const [count, setCount] = useState(0)

  useEffect(() => {
    console.log('In use effect.')
  }, [])
 
  return (
    <div>
      <p>You clicked {count} times</p>
      <button onClick={() => {console.log(count); setCount(count + 1);}}>Click me</button>
    </div>
  )
}
```
React hooks do not seem to work and the button's `onClick` function does not work.

### Expected Behavior

When creating a client component as described above, the useEffect function should be called and the onClick function should call the provided handler function.

### Which browser are you using? (if relevant)

Safari 16.1 (18614.2.9.1.12)

### How are you deploying your application? (if relevant)

_No response_
Repository: material-ui
Issue: [website] Dark mode toggle doesn't affect [data-mui-color-scheme]
Labels: bug 🐛,website

The dark mode toggle in the components docs does not change the value of the `data-mui-color-scheme` attribute on the `<html>` element. This causes the Tailwind demos to be styled incorrectly.

See https://mui.com/base-ui/react-input/#basics: switch to Tailwind CSS and change the display mode.

<img width="645" alt="image" src="https://github.com/mui/material-ui/assets/4696105/aed8b32f-e431-45f9-8f09-707b8db283d5">
Repository: pytorch
Issue: Doc is unclear on how to install pytorch with Cuda via pip
Labels: triaged,topic: docs

### 📚 The doc issue

![image](https://github.com/pytorch/pytorch/assets/35759490/17b506aa-ff3a-40cf-baac-63bb66c486ac)

I've been looking on how to install torch with CUDA via pip for almost one day and the doc is absolutely not helping on how to do so.

### Suggest a potential alternative/fix

Explain clearly how to install pytorch using pip with CUDA or not.

```
To install pytorch with CUDA using pip, you first need to install CUDA on your system if it is compatible with it and then install pytorch with the following command in your shell:

`pip install ...........`
```
Repository: flutter
Issue: DropdownMenu is very slow when using large lists
Labels: c: new feature,f: material design,a: quality,c: proposal,perf: speed,P3,team-design,triaged-design

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

When using large lists of options in the `DropdownMenu`, the UI starts to slow down terribly, loading the list itself is very slow.
Unable to use.
We need to add something like virtualization so that only those options that should be visible at the moment are drawn.

### Proposal

Add virualization to the options list.
Repository: pytorch
Issue: [LibTorch/iOS] Building with METAL support script is freezing
Labels: triaged,oncall: mobile,module: ios

### 🐛 Describe the bug

I am trying to build the library to support METAL on iOS, I am executing this command after cloning the repo:

`IOS_ARCH=arm64 USE_PYTORCH_METAL=1 ./scripts/build_ios.sh`

However, it just freezes here at 86%:

```
Consolidate compiler generated dependencies of target torch_cpu
[ 86%] Building CXX object caffe2/CMakeFiles/torch_cpu.dir/__/aten/src/ATen/native/cpu/ReduceOpsKernel.cpp.DEFAULT.cpp.o
```

### Versions

LibTorch-Lite (1.13.0.1):
LibTorch-Lite/Core (= 1.13.0.1)
LibTorch-Lite/Core (1.13.0.1):
LibTorch-Lite/Torch
LibTorch-Lite/Torch (1.13.0.1)

cc @kulinseth @albanD @malfet @DenisVieriu97 @razarmehr @abhudev
Repository: pytorch
Issue: [FakeTensor] `to` doesn't error with `allow_non_fake_inputs=False`
Labels: triaged,module: fakeTensor

### 🐛 Describe the bug

```python
import torch
from torch._subclasses.fake_tensor import FakeTensorMode

number = 0.5
const = torch.tensor(number)

with FakeTensorMode(allow_non_fake_inputs=False):
    x = const.sin()  # Fails as expected `Please convert all Tensors to FakeTensors first or instantiate FakeTensorMode with 'allow_non_fake_inputs'.`

    x = const.to(torch.float)  # This passes
    print(x)  # tensor(0.5)
    x = const.to(torch.int)  # This passes
    print(x)  # FakeTensor(..., size=(), dtype=torch.int32)
```

cc: @zou3519 

### Versions

main
Repository: flutter
Issue: Checkbox doesn't render properly with ContinuousRectangleBorder
Labels: f: material design,a: quality,has reproducible steps,P2,team-design,triaged-design,found in release: 3.13,found in release: 3.14

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

1. Pass `shape: ContinuousRectangleBorder(…)` in a `Checkbox` widget.
2. Set `Checkbox.value` to false.

### Expected results

The checkbox should render a clean ContinuousRectangleBorder (squircle) outline.

### Actual results

The outline looks bad. It seems to be rendering the expected squircle overlapped with a `RoundedRectangleBorder`.

When `Checkbox.value` is set to true, the shape is rendered properly.

### Code sample

https://dartpad.dev/23adc23f66e7df9bd5133bfa80f3014f?channel=master

<details><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() => runApp(const AppBarApp());

class AppBarApp extends StatelessWidget {
  const AppBarApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Center(
          child: Checkbox(
            shape: ContinuousRectangleBorder(
                borderRadius: BorderRadius.circular(24)),
            value: false,
            onChanged: (_) {},
          ),
        ),
      ),
    );
  }
}
```

</details>


### Screenshot

![image](https://github.com/flutter/flutter/assets/1006207/15edf0fb-44a1-4ca4-b8e3-b1f36417198d)

Left: unchecked, right: checked
Repository: next.js
Issue: Pages render without static props on client-side navigation with `skipMiddlewareUrlNormalize` option
Labels: bug,Navigation,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:05 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.20.2
      npm: 8.19.4
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/victorandree/next-static-props-middleware-url

### To Reproduce

1. Create a new Next app with the Pages router
2. Create a page that uses `getStaticProps` to get static props
3. Configure `{ trailingSlash: true, skipMiddlewareUrlNormalize: true }`
4. Create an empty middleware function in `middleware.ts`
5. Navigate to the static page using client-side navigation

### Describe the Bug

If you navigate to a page that uses `getStaticProps` using client-side navigation (e.g. by clicking a link), the component renders without these static props, if you have middleware and Next.js is configured with ``{ trailingSlash: true, skipMiddlewareUrlNormalize: true }`.

Note:

- This behavior was probably introduced somewhere between 13.4.2 and 13.4.16.
- If you use `trailingSlash: false`, I'm not seeing this issue.

### Expected Behavior

The page should render with the statically defined properties.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: storybook
Issue: [Bug] Svelte component documentation isn't added to autodocs documentation
Labels: bug,svelte,needs triage

### Describe the bug

Following the [official svelte component documentation guidelines](https://svelte.dev/docs/faq#how-do-i-document-my-components) doesn't result in the autodocs generated page having documentation for the component.

### Steps to reproduce the behavior

1. Create a svelte component
2. Document it in the [officially recommended format](https://svelte.dev/docs/faq#how-do-i-document-my-components)
3. enable autodocs
4. run storybook and look at the generated autodocs for it. Note that the component description is not present.

### Expected behavior

The same markdown documentation used for the officially recommended method of documenting a component should also be provided to the autodocs for any svelte stories.

### Screenshots and/or logs

Example of the commented documentation working within VSCode:
![image](https://github.com/storybookjs/addon-svelte-csf/assets/9017393/4b00e781-2351-4add-a763-7a281da1bc76)

Example of the autodoc-generated documentation _not_ containing that same information:

![image](https://github.com/storybookjs/addon-svelte-csf/assets/9017393/e88b83c8-3ae4-451d-ad59-dd0f86ae97c8)


### Environment

 - OS: Mac OS
 - Node.js version: v20.5.0
 - NPM version: 9.8.0
 - Browser (if applicable): N/A
 - Browser version (if applicable): N/A
 - Device (if applicable): N/A

### Additional context

This issue, along with storybookjs/addon-svelte-csf#122 would go a long way towards improving the storybook docs experience for Svelte.
Repository: material-ui
Issue: [system] Doesn't throw type error when setting state classes in `styleOverrides`
Labels: typescript,package: system

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/s/nervous-currying-86srm3?file=/index.js

Steps: 

1. While setting styleOverrides for state classes like `expanded` , `disabled` etc... , right now below image is what seen in console... which is fine. But typescript doesn't throw any error while setting `state classes` in `styleOverrides`, which is bit confusing
2. I think erroring in types when users set `state classes` in `styleOverrides` provides better `DX`.

<img width="484" alt="Screenshot 2023-08-21 at 5 37 19 PM" src="https://github.com/mui/material-ui/assets/60743144/22999f3b-fc19-4dff-ba21-2b7865257f5a">




### Current behavior 😯

Doesn't throw any type error when setting state classes

### Expected behavior 🤔

Should throw type error when setting state classes

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: vscode
Issue: [folding] Folding is clickable on the whole foldable region in the gutter
Labels: feature-request,editor-folding

This is an extension to https://github.com/microsoft/vscode/issues/60670. It would be great to be able to click on the whole gutter line to fold. Example from Fleet: 



https://github.com/microsoft/vscode/assets/16353531/56920085-5316-467f-a009-80be027d60ed
Repository: PowerToys
Issue: 使用PowerToys桌面图标变成白纸图标
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.72.0

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

General

### Steps to reproduce

打开应用之后，桌面图标就变成白纸图标，原来图标不见，需要刷新才能恢复原来的图标
<img width="114" alt="image" src="https://github.com/microsoft/PowerToys/assets/55046358/7c8535bf-2b30-40d0-8021-ed635b1a2ceb">


### ✔️ Expected Behavior

打开应用之后图标正常显示

### ❌ Actual Behavior

打开应用之后，桌面图标就变成白纸图标，原来图标不见，需要刷新才能恢复原来的图标
<img width="114" alt="image" src="https://github.com/microsoft/PowerToys/assets/55046358/7c8535bf-2b30-40d0-8021-ed635b1a2ceb">
[PowerToysReport_2023-08-21-20-54-34.zip](https://github.com/microsoft/PowerToys/files/12396131/PowerToysReport_2023-08-21-20-54-34.zip)


### Other Software

_No response_
Repository: pytorch
Issue: [feature request] Support native ONNX export of FFT-related ops in opset17 (with `inverse=True`, it also includes inverse DFT)
Labels: module: onnx,triaged

### 🚀 The feature

Seems that more FFT-related ops are now supported by ONNX opset17 and onnxruntime:
- https://github.com/onnx/onnx/blob/main/docs/Operators.md#dft

It would be good to have torch.fft.rfft and friends to be natively exported without having to construct the basis manually.

I think this would also be import to torchaudio community

Also related: https://github.com/pytorch/pytorch/issues/107446

### Motivation, pitch

N/A

### Alternatives

_No response_

### Additional context

_No response_
Repository: pytorch
Issue: Select on a coalesced COO tensor returns COO tensor with coalesce flag set to False.
Labels: module: sparse,feature,triaged

## Issue description

As in the title. The result of `select` ought to be always coalesced when its input tensor is a coalesced COO tensor because the ordering of indices in the select result is the same as in the input tensor indices.

## Code example

```python
>>> a = torch.tensor([[0, 1, 2], [3, 4, 5], [5, 6, 7]]).to_sparse()
>>> a.is_coalesced()
True
>>> a.select(0, 0)
tensor(indices=tensor([[1, 2]]),
       values=tensor([1, 2]),
       size=(3,), nnz=2, layout=torch.sparse_coo)
>>> a.select(0, 0).is_coalesced()
False
```

The expected result is `True`.

## System Info

- PyTorch version: main

cc @alexsamardzic @nikitaved @cpuhrsch @amjames @bhosmer
Repository: next.js
Issue: remove warning/allow to pass named, re-exported assets (png, svg, ...) to client components
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
    Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.19
      pnpm: 7.1.0
    Relevant Packages:
      next: 13.4.20-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/solitary-sun-kv223y?file=/app/page.tsx:3,1

### To Reproduce

Open the sandbox example. See the `dev`-terminal output. 

### Describe the Bug

I get a warning:
`Warning: Only plain objects can be passed to Client Components from Server Components. Module objects are not supported.`

### Expected Behavior

No warning, since it works, the image is correctly rendered.

I do understand why the message comes, but can we make an exception for that case? It would be nice if you could export the assets named, so its easier to see usage, refactor and be able to change extension without having to rename the (direct) imports everywhere.

Note: I can only re-export using full-export and alias: `* as alias from "./asset-url.xyz"`. Typically when importing, I don't need full import, but can use the default. Maybe its just a matter of typing to allow me re-export without full-export, which then should prevent the warning?

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: go
Issue: runtime: failures with `fatal error: traceback did not unwind completely` on `openbsd/arm64`
Labels: help wanted,OS-OpenBSD,NeedsInvestigation,arch-arm64,compiler/runtime

```
#!watchflakes
post <- goos == "openbsd" && goarch == "arm64" && log ~ `fatal error: traceback did not unwind completely`
```

(Pulled out from https://github.com/golang/go/issues/55167#issuecomment-1686446766, https://github.com/golang/go/issues/62105#issuecomment-1682814478, and https://github.com/golang/go/issues/62101#issuecomment-1682814436.)
Repository: vscode
Issue: terminal.integrated.environmentChangesIndicator is no longer accurate
Labels: debt,terminal-env-collection

This setting's `"on"` is the same as `"warnonly"`, we probably don't need this setting at all anymore.
Repository: godot
Issue: UI: "Reparent to New Node" behavior is unpredictable when using custom Anchor Points
Labels: bug,topic:editor,topic:gui

### Godot version

v4.1.1.stable.official [bd6af8e0e]

### System information

macOS 13.4.1

### Issue description

When using the function "Reparent to New Node" with custom Anchor Points, the behavior is unpredictable and/or time consuming.

Coming from Figma / Sketch / Illustrator, I see this command as a "Group" command, meaning the node(s) I'm selecting first should be used as a reference for the size / position of the new node being created. However, when using this command with custom Anchor Points, it completely mess up the size / position / anchor data of the objects(s) you want to nest inside a new node.

### Steps to reproduce

- Create a new User Interface Scene
- Add a new Panel Node
- Resize the Panel Node to make it much larger than default (i.e: 1000 x 500)
- Move the Panel Node to another position than 0, 0
- In the Anchor Menu (far right in the top toolbar), click on the dropdown menu and select "Set to Current Ratio"
- Right-click on the Panel Node in the Scene panel and select Reparent to New Node
- Choose a Control Node and click Create
- Notice how the Panel Node's Size, Position and Anchor are now messed up

### Minimal reproduction project

Or try reparenting the Panel node inside this project:

[Reparent-to-New-Node-Bug.zip](https://github.com/godotengine/godot/files/12398286/Reparent-to-New-Node-Bug.zip)
Repository: PowerToys
Issue: FancyZones - Span 3 columns 
Labels: Idea-Enhancement,FancyZones-Dragging&UI,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

FancyZones allows spanning 2 columns of zones if you drag near the boundary of 2 zones.  (you can also span 2 rows)



### Scenario when this would be used?

I have three columns of zones (3 monitors) and would like to span 3 columns.  Doesn't seem to be a way to do this.

### Supporting information

Some people have more than 2 monitors, or 3 zone columns defined for 2 monitors.
Repository: neovim
Issue: TUI: Support 'guifont' in terminals that recognise OSC 50 (XTerm Set Font)
Labels: enhancement,tui

### Problem

As far as i understand, `'guifont'` option does not work in terminals at all. But we can make it work by using XTerm's `OSC 50` that allows program to set terminal font! This would be useful for, for example, switching ligature sets on fonts depending on filetype. Or just changing font just for Neovim in general.

### Expected behavior

Neovim should recognise XTerm's `OSC 50` and use it for setting `'guifont'`. Checking whether the requested font actually exists may be a problem, but i'm not sure if Neovim GUI's check for that.