sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: No possibility to define chip in onDelete handler
Labels: component: chip,enhancement

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Steps: 

1. Add onDelete handler to the Chip component. 
2. Add `data-index` or `id` property to the component
3. Click delete button to raise an event


### Current behavior 😯

1. Setting `data-index` or `id` doesn't affect any changes, they cannot be read from event.target or event.currentTarget

### Expected behavior 🤔

I can get an `id` or `dataset` property passed to the component from event

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 13.2.1
  Binaries:
    Node: 18.15.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 9.5.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 112.0.5615.49
    Edge: Not Found
    Firefox: 111.0.1
    Safari: 16.3
  npmPackages:
    @emotion/react: ^11.10.4 => 11.10.4 
    @emotion/styled: ^11.10.4 => 11.10.4 
    @mui/base:  5.0.0-alpha.102 
    @mui/core-downloads-tracker:  5.10.10 
    @mui/icons-material: ^5.10.9 => 5.11.0 
    @mui/material: ^5.10.10 => 5.10.10 
    @mui/private-theming:  5.11.13 
    @mui/styled-engine:  5.11.11 
    @mui/system: ^5.11.14 => 5.11.14 
    @mui/types:  7.2.3 
    @mui/utils:  5.11.13 
    @types/react: ^18.0.25 => 18.0.26 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    typescript: ^4.8.4 => 4.8.4 

```
</details>
Repository: storybook
Issue: [Feature Request]: Watch mode for manager.ts
Labels: feature request,ui

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

Not a problem, necessarily. I would just love to be able to see theme changes live, rather than needing to restart my server constantly.

### Describe the solution you'd like

Just like the docs themselves, I would like for the theming functions to have a watch mode built into them. There's already an established naming convention for the manager, so with my limited knowledge of the code base I wouldn't imagine this to be a difficult thing to acheive.

### Describe alternatives you've considered

ctrl + c

npm run storybook

over

and over

and over again

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

yes, I can

### Additional context

When i say I can assist, I mean I could potentially assist. I've not looked at this code base before, so I'm sure there are others who are better equipped to handle this. But if no one picks it up, I'll gladly look into it.
Repository: storybook
Issue: [Bug]: Storybook status page shows `react-vite` templates under the Preact category
Labels: bug,build

### Describe the bug

<img width="1385" alt="image" src="https://user-images.githubusercontent.com/112161/230627376-e96e53b3-5aaa-425e-929e-1e854045c136.png">

`react-vite` TS and JS templates should be shown under the React category instead.

### To Reproduce

Open https://storybook.js.org/status/#preact and note the last two entries containing `react` instead of `preact` for the `vite` builder.

### System

_No response_

### Additional context

_No response_
Repository: next.js
Issue: Given setup for JEST breaks loading SVG with custom loaders 
Labels: bug,Testing

### 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: #76~20.04.1-Ubuntu SMP Mon Mar 20 15:54:19 UTC 2023
    Binaries:
      Node: 18.0.0
      npm: 8.6.0
      Yarn: N/A
      pnpm: 7.0.1
    Relevant packages:
      next: 13.2.4
      eslint-config-next: 13.2.4
      react: 18.2.0
      react-dom: 18.2.0
```


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

Jest (next/jest)

### Link to the code that reproduces this issue

https://github.com/pkawula/next-jest-bug

### To Reproduce

Clone the repo and install dependencies

then just run `npm t`

### Describe the Bug

Since Next provides base setup for testing in jest, you cannot use different loader for SVG in test components.
The `nextJs` function includes config for `svg`:
```
...
moduleNameMapper: {
...
// Keep .svg to it's own rule to make overriding easy
 "^.+\\.(svg)$": require.resolve(`./__mocks__/fileMock.js`),
 ...
```

I have written a custom transformer to simply transform SVG Components, but it does not work because the svg files are mapped to objects.
I cannot override this rule because it is not allowing me to access the file details which is possible using transform.


### Expected Behavior

I would like an option to disable default moduleNameMapper ruleset added by Next or to delete one to avoid conflicting moduleMapper with transform.

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

_No response_

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

_No response_
Repository: pytorch
Issue: Wrong illustration in README.md
Labels: module: docs,triaged

### 📚 The doc issue

The last frame of the illustration is wrong:

![wrong illustration](https://github.com/pytorch/pytorch/raw/390c51bf87a5e9958f0190c0226493dc4dcdd61e/docs/source/_static/img/dynamic_graph.gif)


### Suggest a potential alternative/fix

The correct illustration should look like this:

![correct illustration](https://user-images.githubusercontent.com/8487114/230635413-925f0858-7166-4557-bb46-484be4b8f1f2.png)


cc @svekars @carljparker
Repository: next.js
Issue: [NEXT-1138] Dynamic root optional catch all routes receive ['index'] when routing to the homepage - as opposed to an empty array
Labels: bug,linear: next

### 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: #202210290932~1669062050~22.04~d94609a SMP PREEMPT_DYNAMIC Mon N
    Binaries:
      Node: 18.15.0
      npm: 9.5.0
      Yarn: 1.22.19
      pnpm: 7.25.0
    Relevant packages:
      next: 13.3.1-canary.1
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
```


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

_No response_

### Link to the code that reproduces this issue

https://github.com/LiamMartens/nextjs13-appdir-homepage-link-index-path

### To Reproduce

This issue only appears on Vercel - not in development or when using `yarn build + yarn start`
A deployed version of the sample repo can be found here

To see the issue:
- Go to [https://nextjs13-appdir-homepage-link-index-path.vercel.app/](https://nextjs13-appdir-homepage-link-index-path.vercel.app/)
- Use one of the links to navigate to a secondary page (page 1 or page 2 ; doesn't matter)
- Once navigated use the homepage link to navigate back to the root of the optional catch all
- You will see a 404 and you will notice the `PATH` receives `['index']` as a parameter - as can be seen displayed on the page

### Describe the Bug

Routing to the index of an optional catch all using a `next/link` results in the param `['index']` being sent as opposed to an empty array

### Expected Behavior

The catch all parameter should be an empty array

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

_No response_

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

_No response_

<sub>[NEXT-1138](https://linear.app/vercel/issue/NEXT-1138/dynamic-root-catch-all-routes-receive-[index]-when-routing-to-the)</sub>
Repository: flutter
Issue: [pigeon] Java and Swift generators swap code and message in exceptions
Labels: platform-android,platform-ios,package,team-ecosystem,p: pigeon,P2,p: requires breaking change,triaged-ecosystem

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Steps to Reproduce

<!-- Please include full steps to reproduce so that we can reproduce the problem. -->

1. Use Pigeon's java generator with `--java_out`
2. Throw an exception in Java/Kotlin code
3. Catch it in dart code
 
**Expected results:** `code` should be the name of the class and `message` the `.toString()`

**Actual results:** They are inverted

The bug is right here https://github.com/flutter/packages/blob/main/packages/pigeon/lib/java_generator.dart#L803-L810 . The `if` part is correct, the `else` is not.
Repository: go
Issue: x/build: use LLD linker on linux-amd64-clang builder?
Labels: Builders,NeedsInvestigation

The LLD linker is widely used by users. Occasionally there are some subtle differences in behavior between the C linkers (BFD, Gold, LLD), that cause issues for us (e.g. we may have assumptions based on the BFD linker's specific behavior (e.g. #59466), or we may uncover a bug in the C linker itself.)

As far as I can tell, we don't have much LLD coverage on the builders. I think it is probably good to have one. The `linux-amd64-clang` builder already uses LLVM based C compiler. So it may be a good fit. (gcc+lld is possible but probably not a popular configuration.)

Thoughts? Thanks.

cc @prattmic (was chatting with Michael about this the other day)
Repository: vscode
Issue: [Linux Mint] Program icon doesn't match Linux Mint theme
Labels: bug,help wanted,linux

Hello,

I'm writing regarding [this issue](https://www.reddit.com/r/linuxmint/comments/10sgvh5/visual_studio_code_no_mint_icon_if_installing_the/).

The problem is that VSCode doesn't recognise Mint's theme and instead displays the default icon.

I tried the solution proposed [here](https://www.reddit.com/r/linuxmint/comments/10sgvh5/comment/j7csakq/?utm_source=share&utm_medium=web2x&context=3) but it works only temporarily, because VSCode will automatically restore its default icon with every update.

Please let me know if you need more information.

- VS Code Version: 1.77.1
- OS Version: Linux Mint 21 x86_64
Repository: next.js
Issue: `export const { foo } = ...` broken
Labels: TypeScript

### 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.4.0: Mon Mar  6 20:59:58 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6020
    Binaries:
      Node: 19.8.1
      npm: 9.5.1
      Yarn: N/A
      pnpm: 8.1.1
    Relevant packages:
      next: 13.3.1-canary.1
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), TypeScript (plugin, built-in types)

### Link to the code that reproduces this issue

N/A

### To Reproduce

Declare any export like this:

```ts
export const { BlitzProvider } = setupBlitzClient({ ... });
```

### Describe the Bug

Doing the above will result in an import error

```
warn  - ./app/layout.tsx
Attempted import error: 'BlitzProvider' is not exported from 'src/blitz-client' (imported as 'BlitzProvider').

Import trace for requested module:
./app/layout.tsx
Warning: React.jsx: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Check your code at layout.tsx:21.
Warning: React.jsx: type is invalid -- expected a string (for built-in components) or a class/function (for composite components) but got: undefined. You likely forgot to export your component from the file it's defined in, or you might have mixed up default and named imports.

Check your code at layout.tsx:21.
error - node_modules/next/dist/compiled/react-server-dom-webpack/cjs/react-server-dom-webpack-server.edge.development.js (1700:8) @ attemptResolveElement
error - Error: Unsupported Server Component type: undefined
    at stringify (<anonymous>)
```

### Expected Behavior

The variable gets imported correctly

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: flutter
Issue: [pigeon] Add backtrace to `PlatformException` where possible
Labels: package,team-ecosystem,p: pigeon,P3,triaged-ecosystem

`PlatformException` has a stack trace field which we're currently not using; on platforms where we can get it at runtime we should add it. On Java for instance, the [`MethodChannel` exception code](https://github.com/flutter/engine/blob/main/shell/platform/android/io/flutter/plugin/common/MethodChannel.java#L277-L281) adds a backtrace.

We would need to make a change across all generators to make the error array 4 elements instead of 3.
Repository: next.js
Issue: If Script is removed via vanilla JS logic, it doesn't re-mount on consecutive renders
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: darwin
    Arch: arm64
    Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000
Binaries:
    Node: 18.14.2
    npm: 9.5.0
    Yarn: N/A
    pnpm: N/A
Relevant packages:
    next: 13.2.4
    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)

Script optimization (next/script)

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/naughty-meitner-jlzxub?file=%2Fpages%2Findex.tsx

### To Reproduce

Steps to reproduce are inserted into the linked codesandbox.

In short:
1. Have multiple routes to switch between.
2. Add `<Script>`-implemented script to the DOM when initial/home page mounts.
3. Right before navigating to a different route (`router.events.on('routeChangeStart')`) remove the script from step 2 via vanilla JS code (`document.body.removeChild(...)`).
4. Navigate from a different route back to the initial/home page.
5. Observe that there's no script added to the DOM, though the component itself mounts correctly.

### Describe the Bug

When navigating between app routes, `<Script>`-implemented scripts are not being added to the DOM if they were removed via vanilla JS means (e.g. `document.body.removeChild(...)`) before route switch.

### Expected Behavior

When navigating between app routes, `<Script>`-implemented scripts should be added to the DOM if they were removed via vanilla JS means (e.g. `document.body.removeChild(...)`) before route switch.

### Which browser are you using? (if relevant)

Arc (Version 0.96.0 (38004)), Chromium Engine Version 111.0.5563.146

### How are you deploying your application? (if relevant)

_No response_
Repository: excalidraw
Issue: Expose the collaboration endpoint in the component state
Labels: enhancement

After going through the documentation, I've noticed that there is no way to only change the endpoint where the collaboration server is located when Embedding the Excalidraw component, without cloning the project, changing the endpoint and republishing it. I do believe making this endpoint overridable would save a lot of people a lot of extra effort.
Repository: go
Issue: x/build/cmd/watchflakes: adjust behavior for non-default branches
Labels: Builders,NeedsInvestigation,FeatureRequest

When `watchflakes` posts to an issue (as in https://github.com/golang/go/issues/58714#issuecomment-1448384846), it gives the timestamp and Go commit hash but not the Go branch name.

For failures on release branches that occur after an attempted fix, the branch name is a very important detail: it helps us figure out whether the fix was successful (and may need to be backported) or unsuccessful (and needs to be further revised).

Specifically, I suggest that when `watchflakes` posts newly-identified test flakes:
- [ ] the summary lines for failures on non-default branches should mention the branch name, and
- [ ] `watchflakes` should not reopen a closed issue if the only new failures are on non-default branches.

(attn @cherrymui; CC @golang/release)
Repository: flutter
Issue: [Impeller] Better optimizations for subpasses which contain only a clip and texture contents.
Labels: engine,P2,e: impeller,team-engine,triaged-engine

Flutter's API favors composition over loading on properties on a single widget. That is, while applying a color filter directly to an image is faster:

```dart
Image.asset(..., colorBlendMode: BlendMode.colorDodge, color: Colors.red)
```

Its much more common for folks to nest this under a `ColorFiltered` widget:

```dart
ColorFiltered(colorFilter: ..., child: Image.asset(...)
```

Additionally, there are many such operations which are not made easy by the current framework API: Namely other types of color filters and image filters cannot be directly applied.

We should be able to avoid the subpass in these cases and provide the texture snapshot directly to the filter.
Repository: pytorch
Issue: Add test/distributed/test_c10d_mpi.py
Labels: oncall: distributed,triaged

>  We have one config where MPI is available and we build the wheels with MPI support.

https://github.com/pytorch/pytorch/pull/98545#issuecomment-1500440581

We don't have any tests for MPI as we do for gloo (test_c10d_gloo) or nccl (test_c10d_nccl). As @malfet mentions since we have support in CI for mpi, we should at least create a basic test_c10d_mpi to perform basic distributed operations (e.g. init_process_group) to prevent any future regressions.

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @kwen2501 @awgu
Repository: PowerToys
Issue: TTS (Text to speech) added the Text extractor 
Labels: Idea-Enhancement,Help Wanted,Product-Text Extractor

### Description of the new feature / enhancement

An option added to Text extractor which reads aloud the selected text after selection or a keyboard shortcut to text extractor to read aloud the selected text. 

### Scenario when this would be used?

This would be a very useful accessibility add on to Text extractor for low vision individuals. This would complement to the Windows magnifier which can read aloud only certain types of text on the screen.  
This would enhance productivity of low vision individuals.
Use case: 
a person with low vision finds a image with a long text in the image. (Their screen reader can not read the text in the image)
they press on the text extractors shortcut and make it read aloud the text.
They hear the text being read aloud. 

As a legally blind person i use text extractor to copy the text in the image to word and listen it there. This increases the latency. Also i can not look at the image while doing this.

### Supporting information

There is a large demand for properly adding alt text to images and more accessible  ways to display text on the screen from low vision individuals.  This feature would alleviate some of these problems and improve accessibility of text which are not readable by tradisional screen readers.
Repository: flutter
Issue: [shared_preferences] Remove BigInt and Set<String> support from Android implementation
Labels: p: shared_preferences,package,team-ecosystem,P3,p: requires breaking change,triaged-ecosystem

There's code in the Android implementation from many years ago that supported storing and retrieving BigInteger values. But [since at least January 2018](https://groups.google.com/g/flutter-dev/c/doKMRFpANOQ) it hasn't been possible to save such a value. We're going to remove the dead code for setting it, but *technically* removing the reading code is breaking since someone could, in theory, have a 6 year old pref that they are reading as a string (and have never written again?)

The next time we are doing a breaking change to `shared_preferences` for any other reason, we should remove that code.
Repository: tauri
Issue: [feat] Changing default Data directory for the app not per-window.
Labels: scope: core,type: feature request,priority: 3 low

### Describe the problem

I can't find a straight forward way to change the data directory of webview user data, and Its a really important feature, I saw the documentation and I can't find any example on how to make this work, can you help?

### Describe the solution you'd like

expose the path of data directory in tauri.config file or provide some examples on how to do it manually.

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: next.js
Issue: [NEXT-1102] `opengraph-image` is 404 in route group segments, both image and dynamic
Labels: Metadata,linear: next

### 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: x64
      Version: Darwin Kernel Version 20.6.0: Tue Apr 19 21:04:45 PDT 2022; root:xnu-7195.141.29~1/RELEASE_X86_64
    Binaries:
      Node: 16.19.0
      npm: 9.3.1
      Yarn: 3.4.1
      pnpm: N/A
    Relevant packages:
      next: 13.3.1-canary.2
      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)

App directory (appDir: true)

### Link to the code that reproduces this issue

https://stackblitz.com/edit/vercel-next-js-k4rkzr?file=app/(group)/segment/page.tsx

### To Reproduce

In any Next.JS 13 project, in `appDir`:

1. Create route `(group)`
2. In the route `(group)`, create a `/segment/page.tsx`
3. Create any `/segment/opengraph-image`, `(jpg|png|...)` or `(js|jsx|tsx)` – doesn't matter
4. You won't be able to access the OG Image for any page in the segment or it's leaf segments

### Describe the Bug

While setting `opengraph-image` for a segment in the route group, it doesn't work. You will see a 404 page instead.

It is detected and compiled as evidence by the console messages referring to it:
```
wait  - compiling /opengraph-image.jpg/route (client and server)...
event - compiled successfully in 362 ms (299 modules)
```
```
warn  - metadata.metadataBase is not set for resolving url "/blog/opengraph-image.jpg?0a4faadd7eacd798", fallbacks to "http://localhost:3000". See https://beta.nextjs.org/docs/api-reference/metadata#metadatabase
```

### Expected Behavior

`opengraph-image` should work the same on any nesting level, in a route group or outside of a route group.

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

_No response_

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

_No response_

<sub>[NEXT-1102](https://linear.app/vercel/issue/NEXT-1102/opengraph-image-is-404-in-route-group-segments-both-image-and-dynamic)</sub>