sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [Chip] Does not focus on when navigating with arrows on with Safari 16.3 (18614.4.6.1.6)
Labels: component: chip,component: autocomplete,browser: Safari

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: [Mui-focused](https://mui.com/material-ui/react-autocomplete/#multiple-values)

Steps:

1. Select the "Multiple values" example 
2. Add a few movies to the list 






### Current behavior 😯

The chips don't change colours when you navigate using arrows like it does in Chromium

### Expected behavior 🤔

The chips should switch to the colours defined in https://github.com/mui/material-ui/pull/35502/files#diff-8f415fe330d102624dbf0dbb137ff10972d0d336ecc89df39355d291f7cc2b02R183 which works on Chromium

### Context 🔦

_No response_

### Your environment 🌎


```yaml
Packages.json: 
    "@mui/lab": "5.0.0-alpha.121",
    "@mui/material": "5.11.11",
    "@mui/styled-engine": "5.11.11",
```

```
 System:
    OS: macOS 13.2.1
  Binaries:
    Node: 19.7.0 - /private/var/folders/jy/hc1n_qhd0sb1tbbm5z945v500000gn/T/xfs-c1d0b0ec/node
    Yarn: 4.0.0-rc.39 - /private/var/folders/jy/hc1n_qhd0sb1tbbm5z945v500000gn/T/xfs-c1d0b0ec/yarn
  Browsers:
    Chrome: Chromium: 110.0.5481.177 (Official Build) (arm64)]
    Safari: 16.3

```
Repository: godot
Issue: Can't copy text from editor help
Labels: bug,topic:editor,usability,topic:gui

### Godot version

4.0 rc6

### System information

Windows 10 x64

### Issue description

You can select text in editor help, but it can't be copied. Ctrl+C does not change clipboard.

### Steps to reproduce

1. F1
2. Enter
3. Select text
4. Ctrl+C
5. Ctrl+V somewhere

### Minimal reproduction project

N/A
Repository: storybook
Issue: [Feature Request]: Support for TS 4.9 <typeof meta> syntax on html-vite framework
Labels: feature request,html

### Is your feature request related to a problem? Please describe

The types for `Meta` and `StoryObj` on the `html` framework do not support this syntax:

```ts
// ./Button.story.ts
import type { Meta, StoryObj } from '@storybook/html';
import { createButton, type ButtonProps } from './Button';

const meta = {
  title: 'Component',
  render: args => createButton(args),
  //                           ^- Argument of type '({ variant }: ButtonProps) => HTMLButtonElement' is not assignable to parameter of type 'ButtonProps'.ts(2345)
} satisfies Meta<typeof createButton>;

type Story = StoryObj<typeof meta>;

export default meta;

export const Default: Story = {
  args: {
    variant: 'primary',
//  ^- Type '{ variant: string; }' is not assignable to type 'Partial<{ title: string; render: (args: ({ variant }: ButtonProps) => HTMLButtonElement) => HTMLButtonElement; }>'.
  }
}
```

```ts
// ./Button.ts
export type ButtonProps = {
  variant: 'primary' | 'secondary';
}

export function createButton({ variant }: ButtonProps) {
  return `<button class="${variant}">...</button>`;
}
```

The implementation that works is to use the `ButtonProps` type instead of the `typeof createButton` annotation.

```ts
// ./Button.story.ts
import type { Meta, StoryObj } from '@storybook/html';
import { createButton, type ButtonProps } from './Button';

const meta = {
  title: 'Component',
  render: args => createButton(args),
} satisfies Meta<ButtonProps>;

type Story = StoryObj<ButtonProps>;

export default meta;

export const Default: Story = {
  args: {
    variant: 'primary',
  }
}
```


### Describe the solution you'd like

I would like that the `Meta` and `StoryObj` types from the `html` framework could infer the types from the `createButton` function so that it would comply with the implementation in the docs for React and other frameworks.

### Describe alternatives you've considered

_No response_

### Are you able to assist to bring the feature to reality?

no

### Additional context

Cc: @kasperpeulen
Repository: rust
Issue: Floating point remainder in `no_std` causes linker error
Labels: A-linkage,T-compiler,C-bug,A-floating-point,S-needs-repro

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
#![no_std]
#![no_main]

fn identity(x: f64) {
    // turn off constant folding
    x
}

#[no_mangle]
pub extern "C" fn foo() {
    1.0 % identity(2.0)
}
```

I expected to see this happen: should either compile and link correctly, or give a compiler error (something like "fmod not supported in `no_std`, please use the `libm` crate")

Instead, this happened: the code compiles, but when linking into other programs (in my case a C program), the linker reports "unresolved external symbol `fmod` referenced in function foo".

I'm currently using `libm` directly as a workaround.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.69.0-nightly (d962ea578 2023-02-26)
binary: rustc
commit-hash: d962ea57899d64dc8a57040142c6b498a57c8064
commit-date: 2023-02-26
host: x86_64-pc-windows-msvc
release: 1.69.0-nightly
LLVM version: 15.0.7
```
Repository: next.js
Issue: [NEXT-707] Next.js 13.2.1: Custom TypeScript ESLint setup fails ‘next build’
Labels: bug,linear: next

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.2.0: Fri Nov 11 02:03:51 PST 2022; root:xnu-8792.61.2~4/RELEASE_ARM64_T6000
Binaries:
  Node: 18.13.0
  npm: 8.19.3
  Yarn: 1.22.19
  pnpm: 7.26.0
Relevant packages:
  next: 13.2.1
  eslint-config-next: 13.2.1
  react: 18.2.0
  react-dom: 18.2.0
```

### Which area(s) of Next.js are affected? (leave empty if unsure)

ESLint (eslint-config-next)

### Link to the code that reproduces this issue

https://github.com/christianvuerings/next13.2-custom-eslint-repro

### To Reproduce

1. Run `npx create-next-app@latest --typescript`
2. Call project next13.2-custom-eslint-repro
3. `Would you like to use ESLint with this project?`: Yes
4. Add `  "plugins": [“company”]` to `.eslintrc.json`
5. Add `"eslint-plugin-company”: "file:eslint-plugin-company”,` to `package.json`
6. Install `@esbuild-kit/cjs-loader` and `@typescript-eslint/utils`
7. Add your first custom rule
8. Run `npm run build`

### Describe the Bug

Next.js build fails with the following exception:

```
$ npm run build
uncaughtException TypeError: Unexpected response from worker: undefined
    at ChildProcessWorker._onMessage (/Users/christian/code/next13.2-custom-eslint-repro/node_modules/next/dist/compiled/jest-worker/index.js:1:12492)
    at ChildProcess.emit (node:events:513:28)
    at ChildProcess.emit (node:domain:489:12)
    at emit (node:internal/child_process:937:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
info  - Linting and checking validity of types .
```

Example failure: https://github.com/christianvuerings/next13.2-custom-eslint-repro/actions/runs/4293648834/jobs/7481595628

### Expected Behavior

Next.js build succeeds

### Other notes

* `npm run lint` passes
* `npx eslint .` passes 
* Issue started with [v13.1.7-canary.0](https://github.com/vercel/next.js/releases/tag/v13.1.7-canary.0), [v13.1.6](https://github.com/vercel/next.js/releases/tag/v13.1.6) works fine
* Issue also happens on latest canary: [v13.2.2-canary.3](https://github.com/vercel/next.js/releases/tag/v13.2.2-canary.3)
* Workaround: run `next build --no-lint` instead of `next build` & run `next lint` step separately

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

<sub>[NEXT-707](https://linear.app/vercel/issue/NEXT-707/nextjs-1321-custom-typescript-eslint-setup-fails-next-build)</sub>
Repository: stable-diffusion-webui
Issue: [Bug]: git -C error
Labels: bug-report

### Is there an existing issue for this?

- [x] I have searched the existing issues and checked the recent builds/commits

### What happened?

When I install the webui with command `./webui.sh`, the output is

```
Installing gfpgan
Installing clip
Installing open_clip
Cloning Stable Diffusion into repositories/stable-diffusion-stability-ai...
Traceback (most recent call last):
  File "/home/xxx/stable-diffusion-webui/launch.py", line 360, in <module>
    prepare_environment()
  File "/home/xxx/stable-diffusion-webui/launch.py", line 300, in prepare_environment
    git_clone(stable_diffusion_repo, repo_dir('stable-diffusion-stability-ai'), "Stable Diffusion", stable_diffusion_commit_hash)
  File "/home/xxx/stable-diffusion-webui/launch.py", line 162, in git_clone
    run(f'"{git}" -C "{dir}" checkout {commithash}', None, "Couldn't checkout {name}'s hash: {commithash}")
  File "/home/xxx/stable-diffusion-webui/launch.py", line 105, in run
    raise RuntimeError(message)
RuntimeError: Couldn't checkout {name}'s hash: {commithash}.
Command: "git" -C "repositories/stable-diffusion-stability-ai" checkout 47b6b607fdd31875c9279cd2f4f16b92e4ea958e
Error code: 129
stdout: <empty>
stderr: Unknown option: -C
usage: git [--version] [--help] [-c name=value]
           [--exec-path[=<path>]] [--html-path] [--man-path] [--info-path]
           [-p|--paginate|--no-pager] [--no-replace-objects] [--bare]
           [--git-dir=<path>] [--work-tree=<path>] [--namespace=<name>]
           <command> [<args>]
```

I edit the `launch.py`, replace `-C` with `--exec-path` and it's ok.

### Steps to reproduce the problem

No

### What should have happened?

Just replace the `-C` with `--exec-path`

### Commit where the problem happens

0cc0ee1

### What platforms do you use to access the UI ?

Linux

### What browsers do you use to access the UI ?

_No response_

### Command Line Arguments

```Shell
No
```


### List of extensions

No

### Console logs

```Shell
No
```


### Additional information

_No response_
Repository: vscode
Issue: Provide option to disable drag and drop in Editor
Labels: feature-request,workbench-dnd,workbench-editors

<!-- ⚠️⚠️ 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. -->
Sometimes users could drop a file in the editor unintentionally. Could we have an option to disable drag-and-drop in the editor, in parity with File Explorer (e.g., there is an option to disable drag-and-drop for file explorer: `explorer.enableDragAndDrop`)?
Repository: rust
Issue: Reorganize config.toml.example so that unsupported options don't come first in the list
Labels: C-enhancement,T-bootstrap,A-contributor-roadblock

e.g. https://github.com/rust-lang/rust/blob/5157d938c49af1248a21e7ed2fbc5c6f71963276/config.toml.example#L389-L395
Repository: vscode
Issue: Finalize `tooltip` API for `QuickPickItem`s
Labels: feature-request,api,quick-pick,api-finalization

Last iteration we introduced tooltips for quickpickitems into Core and as a proposed API:
https://github.com/microsoft/vscode/issues/174473

The shape of which looks like this:
```ts
        export interface QuickPickItem {
		tooltip?: string | MarkdownString;
	}
```

The ask was from Jupyter Notebooks extension who show a ⚠️ in their quick pick items when _something_ isn't quite as we expect. A `tooltip` is one way to allow them to show additional information that might not be critical, but is available.
Repository: rust
Issue: Invalid missing documentation for reexported item
Labels: T-rustdoc,C-bug

Example:

```rust
mod priv_mod {
    pub struct Foo;
}

#[doc(hidden)]
pub use priv_mod::Foo;
```

With this code, we get:

```
error: missing documentation for a struct
```

Whereas we shouldn't since `Foo` is hidden.
Repository: next.js
Issue: Dynamic importing named exports seems to remove displayName of react component
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:42:11 PST 2023; root:xnu-8792.81.3~2/RELEASE_X86_64
Binaries:
  Node: 18.12.1
  npm: 8.19.2
  Yarn: N/A
  pnpm: 7.15.0
Relevant packages:
  next: 13.2.2-canary.3
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
```

### Which area(s) of Next.js are affected? (leave empty if unsure)

Dynamic imports (next/dynamic)

### Link to the code that reproduces this issue

https://stackblitz.com/edit/vercel-next-js-mdahey?file=pages/index.tsx

### To Reproduce

In [stackblitz](https://stackblitz.com/edit/vercel-next-js-mdahey?file=pages/index.tsx) check `ExampleDynamic.displayName` value is undefined, when `Example.name` value is 'Example'.

### Describe the Bug

I'm using [swiper](https://www.npmjs.com/package/swiper) in my Next.js project and tried to dynamic import two named exported components like below.

```
const SwiperWrapper = dynamic(
  () => import('swiper/react').then(mod => mod.Swiper),
  { ssr: false },
);

const SwiperSlide = dynamic(
  () => import('swiper/react').then(mod => mod.SwiperSlide),
  { ssr: false },
);
```

Above code doesn't make any runtime error, but causes swiper module's malfunction. Because `SwiperSlide` component has explicit 
 displayName 'SwiperSlide'

<img width="300" alt="스크린샷 2023-03-01 오전 12 57 17" src="https://user-images.githubusercontent.com/22445243/221907878-c38784d7-31fe-45d2-bba7-40fbcce3f326.png">

and swiper use it to retrieve valid child elements with same displayName (in result can't get any element since displayName is missing).

<img width="500" alt="스크린샷 2023-03-01 오전 12 59 29" src="https://user-images.githubusercontent.com/22445243/221908697-23578404-5efd-4060-bb47-331d7208829f.png">

It turns out when I import `SwiperSlide` component with dynamic import, displayName property is wiped out and replace to `undefined`. It's reasonable displayName is undefined when dynamic imported component is still loading, but displayName is not assigned even after loaded. I tested this situation with `React.lazy` and this bug also happens on Reacy.lazy too.

By seeing `React.lazy`'s action I'm not sure this is a bug or intended action, but I think explicitly mentioned displayName property shouldn't be removed neither we use dynamic import nor React.lazy. It would be happy if this issue is fixed for Next.js dynamic import.

### Expected Behavior

displayName property remains when using dynamic import.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: terminal
Issue: Bug with "Open windows from a previous session" and defaults profile run as admin
Labels: Help Wanted,Issue-Bug,Area-UserInterface,Product-Terminal,Priority-2

### Windows Terminal version

1.16.10261.0

### Windows build number

10.0.19045.2604

### Other Software

_No response_

### Steps to reproduce

Set "When Terminal Starts" to "open windows from a previous session"
Set Defaults to run this profile as administrator

### Expected Behavior

When opening terminal from start menu it opens as administrator with saved tabs

### Actual Behavior

Terminal opens with default profile and new window with previous tabs.
This happens even with saved tab being the startup default
Repository: pytorch
Issue: `copy.deepcopy` does not copy gradients of nn.Parameter
Labels: module: bc-breaking,module: autograd,module: nn,triaged,topic: bc breaking

Deep copy now copies the .grad field for tensors, but it does not work for Parameter

```
import torch
import copy

c = torch.nn.Linear(1, 10)

c.weight.grad = torch.rand((10, 1))

print(c.weight.grad)
d = copy.deepcopy(c)
print(d.weight.grad)
```
Tested with version 1.13.1. Running the code from @albanD gives the expected result. It would be great if we could find a way to copy an entire (larger) model including its gradients without having to copy every one by hand.

_Originally posted by @jhuebotter in https://github.com/pytorch/pytorch/issues/3307#issuecomment-1425753484_
            

cc @ezyang @gchanan @albanD @zou3519 @gqchen @pearu @nikitaved @Lezcano @Varal7 @mruberry @jbschlosser @walterddr @mikaylagawarecki @saketh-are
Repository: pytorch
Issue: Multiheadattention module doesn't implement the function about kdim and vdim
Labels: module: nn,triaged

### 🐛 Describe the bug

![a](https://user-images.githubusercontent.com/104755879/221919054-ff045a9b-7937-407a-831c-2767f39534bb.png)
The function just implements kdim=vdim=embed_dim.

### Versions

The code on GitHub

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @drisspg
Repository: storybook
Issue: [DX] Favor `.tsx` extension in Vite/React/TS framework
Labels: help wanted,maintenance,cli

### Describe the bug

This is not a code bug but an misalignment in developer expectations.

The Vite/React/TS framework uses `.ts` extensions for Stories and configuration. However, `.tsx` is required when adding React components (decorators and templates).

On the story page, the Vite provided error is misleading (screenshot attached): `Failed to find dynamically imported module: **/MyComponent.stories.ts`

![image](https://user-images.githubusercontent.com/658360/221935127-4142e26a-7829-4f06-b821-cda997f2bfba.png)

This is a little confusing because a file by that name exists (on the user filesystem). The file just failed to build the included JSX.

The correct error can be seen in both console and and docs page:
`[plugin:vite:esbuld] Transform failed…`
![image](https://user-images.githubusercontent.com/658360/221935648-8bfe1f9a-4c80-41a8-8463-9e8d3d6ea22f.png)

Documentation does not assist here because it is based on the Webpack experience, which is much more permissive. Docs suggest that `.tsx` or `.ts` are suitable.

<img width="451" alt="image" src="https://user-images.githubusercontent.com/658360/221936326-8037326f-8a5b-4cc7-9ff4-2272c61b77d9.png">


### To Reproduce

- `npx storybook@next repro`
  - resolved as: `storybook@7.0.0-beta.55`
- framework: `TS/React/Vite`
- node: `16.13.2`
- Add any decorator or `render` field to a story

If the file extensions aren't changed to `.tsx`, they produce these errors:

![image](https://user-images.githubusercontent.com/658360/221937463-523eb95d-19eb-4e55-85eb-0c707889d10e.png)
![image](https://user-images.githubusercontent.com/658360/221937521-f044ecd0-97c9-4726-a15b-97f5cc8fb6fd.png)
![image](https://user-images.githubusercontent.com/658360/221937581-bda76337-a08c-4c50-8da3-91706fa743a5.png)


### System

_No response_

### Additional context

I spoke with the Storybook team in internal Chromatic chat.
The favored solution there is to use use `.tsx` files in this sandbox, even though the extension is extraneous for the CSF3 examples.
Repository: deno
Issue: `npm:wrangler` throws `Found argument '--no-warnings' which wasn't expected`
Labels: bug,node compat

The following error is thrown when running `deno run -A npm:wrangler publish worker.js`

```bash
error: Found argument '--no-warnings' which wasn't expected, or isn't valid in this context

        Did you mean '--no-config'?

        If you tried to supply `--no-warnings` as a value rather than a flag, use `-- --no-warnings`

USAGE:
    deno run --allow-all --unstable --no-config <SCRIPT_ARG>...

For more information try --help
```

Where `worker.js` can be just an empty file. 

`--no-warnings` is [a CLI flag for Node](https://nodejs.org/api/cli.html#--no-warnings), but this error can be reproduced in Deno with:

```ts
import { spawn } from "node:child_process";
import process from "node:process";

spawn(
  process.execPath,
  [
    "--no-warnings",
  ],
  {
    stdio: ["inherit", "inherit", "inherit", "ipc"],
  },
);

```
It is a simplification of [the code used in the package](https://github.com/cloudflare/workers-sdk/blob/0ed6712c7a1b8f2017d1574594405c3c7cbda2da/packages/wrangler/bin/wrangler.js#L58). I am not sure how `process.execPath` is implemented for Deno, but the [Node docs](https://nodejs.org/api/process.html#processexecpath) say: `The process.execPath property returns the absolute pathname of the executable that started the Node.js process.` Only in this case that would be the `deno` executable, which does not know a `--no-warnings` flag.

Source (Discord): https://discord.com/channels/684898665143206084/684898665151594506/1080156118208233522

```bash
deno --version

deno 1.31.1 (release, x86_64-unknown-linux-gnu)
v8 11.0.226.13
typescript 4.9.4
```
Repository: flutter
Issue: [Impeller] Shell unit-tests must have an Impeller backend.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

I think shell tests in general aren't executed for impeller.  I tried to get this test running by setting `Settings.enable_impeller`.  The encode image calls would fail then because `ShellTestPlatformView::GetImpellerContext()` returns nullptr.  I tried making `ShellTestPlatformView::GetImpellerContext()` return a mock context but `SnapshotControllerImpeller::DoMakeRasterSnapshot()` would still fail because `GetDelegate().GetSurface()` is nullptr.  I think a deeper dive will have to be done to get these tests running for impeller.
Repository: pytorch
Issue: dist.barrier() should be able to go through custom backend
Labels: oncall: distributed

### 🚀 The feature, motivation and pitch

With https://github.com/pytorch/pytorch/pull/95072, users can now create a gloo backend for cpu tensors and a custom backend for cuda tensors. However, in such a use case, `dist.barrier()` will always go to gloo due to the following code block in https://github.com/pytorch/pytorch/blob/master/torch/csrc/distributed/c10d/ProcessGroup.cpp: 
```
virtual c10::intrusive_ptr<Work> barrier(
      const BarrierOptions& opts = BarrierOptions()) {
    static at::Tensor tensor;
    // TODO: if nccl was specified then use it
    if (backendType_ == c10d::ProcessGroup::BackendType::NCCL) {
      // set cuda tensor
      tensor = at::empty(
          {1},
          at::TensorOptions().device(at::DeviceType::CUDA).dtype(at::kByte));
    } else {
      // Default to using cpu implementation
      tensor = at::empty(
          {1},
          at::TensorOptions().device(at::DeviceType::CPU).dtype(at::kByte));
    }
```
Custom backends such as SMDDP (https://docs.aws.amazon.com/sagemaker/latest/dg/data-parallel-modify-sdp-pt.html) require `dist.barrier()` to go through SMDDP barrier() because of certain cuda stream semantics -- when a barrier is called, all previous collective communication operations must finish, and frameworks such as DeepSpeed rely on this semantic.

We should allow a way for `dist.barrier()` to go through custom backends. Possibilities are:
1. Add a `device` option in `dist.barrier()`. E.g. `dist.barrier(device='cuda')`
2. When we register custom backends, add a parameter there to signal that the custom backend supports cuda tensor, so the check `backendType_ == c10d::ProcessGroup::BackendType::NCCL` can become `is_cuda_backend(backendType_)`
3. There might be more solutions

Urgency wise, we need a solution before the 2.0 release.

P.S. We don't have the same problem when mapping a custom backend, say SMDDP, to both cpu and cuda devices.

Tagging @H-Huang for visibility and technical inputs. 
Also tagging custom backend developers @indhub @0x6b64 @Arjunbala 

### Alternatives

_No response_

### Additional context

_No response_

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu