sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Storysource addon fills the console with warnings
Labels: bug,good first issue,help wanted,addon: storysource,sev:S2

### Describe the bug

1. Go to https://react-admin-storybook.vercel.app/
2. Open the console
3. See the warning:

> Warning: Encountered two children with the same key, `code-segment0`. Keys should be unique so that components maintain their identity across updates. Non-unique keys may cause children to be duplicated and/or omitted — the behavior is unsupported and could change in a future version.

This warning disappears as soon as the storysource addon is removed. 

### To Reproduce

1. Clone https://github.com/marmelab/react-admin
2. run `yarn`
3. run `yarn storybook`

### System

_No response_

### Additional context

The problem seems to come from here:

https://github.com/storybookjs/storybook/blob/7c21c34edc780905a24f83ec9a557c59120c2301/code/addons/storysource/src/StoryPanel.tsx#L136-L144

The first and the last 'part' have the same key
Repository: go
Issue: proposal: cmd/go: list versions of `go install`-able package
Labels: Proposal,GoCommand

### Proposal Details

When wrapping `go install` for use in https://github.com/jdx/mise, I've run into the [issue](https://github.com/jdx/mise/issues/1495) of not being able to consistently find a list of installable versions for a `go install`-able package URL.

#### Example:

`go list -m -versions -json github.com/go-task/task/v3/cmd/task` returns:
```
{
        "Path": "github.com/go-task/task/v3/cmd/task",
        "Origin": {
                "VCS": "git",
                "URL": "https://github.com/go-task/task",
                "Subdir": "v3/cmd/task",
                "TagPrefix": "v3/cmd/task/",
                "TagSum": "t1:47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU="
        }
}
```

Any software looking to find a list of valid versions for `github.com/go-task/task/v3/cmd/task` I believe has to just check:
- `github.com/go-task/task/v3/cmd/task`
- `github.com/go-task/task/v3/cmd`
- `github.com/go-task/task/v3`

before finding the "root" of the module. This is further complicated by the way major versions are incorporated into the path when the module root is not the repository root.

It would be very useful if `go install` could have a flag to list installable versions (with json?), as it does this check somewhere internally to provide it's current functionality of checking if a version is valid.
Repository: next.js
Issue: output: 'export' does not create _next/data folders but static site still looks for data json files when middleware.ts is present
Labels: bug,Runtime

### Link to the code that reproduces this issue

https://github.com/pr1ntr/next-json-bug-repro

### To Reproduce

```
npm run build
npx serve out/
```

### Current vs. Expected behavior

current behavior is tries to fetch  _next/data/<hash>/about.json from the <Link href="about" />

Expected behavior is that it wont try to fetch _next/data/<hash>/about.json

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 18.18.0
  npm: N/A
  Yarn: N/A
  pnpm: 7.26.2
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: export
```


### Which area(s) are affected? (Select all that apply)

Middleware / Edge (API routes, runtime), Static HTML Export (output: "export")

### Which stage(s) are affected? (Select all that apply)

next build (local), Other (Deployed)

### Additional context

I tested this in 14.0.4 and 14.1, another person tested canary with similar results.
Repository: flutter
Issue: Tooltips get in the way of hovering other widgets on web and desktop platforms.
Labels: framework,f: material design,platform-web,a: desktop,has reproducible steps,P2,team-design,triaged-design,found in release: 3.16,found in release: 3.19

### Steps to reproduce

Add a tooltip to a list of vertically stacked widgets which are 32x32 or about the size of the average desktop toolbar. Hover one of the items so that the tooltip shows up. Try to hover the item below, you won't be able to if your mouse lands on the tooltip because hovering the tooltip will keep the tooltip on screen.

### Expected results

When tooltips are displayed by hovering, they should be wrapped in ignorePointer: true, or if there is a good reason not to do this always, there should be an option ignorePointer on the tooltip widget. Tooltips should not get in the way of hovering other widgets. Compare to tooltips in chrome or somewhere else. This is not usually how tooltips work and it currently makes them unusable on desktop when they overlap other widgets that might need to be hovered.

### Actual results

Tooltips get in the way of hovering other widgets.

### Code sample

n/a

### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

n/a
Repository: vscode
Issue: [ux] `window.titleBarStyle: "custom"` causes rightmost pixels to resize window instead of actioning scrollbar
Labels: bug,layout,confirmation-pending

<!-- ⚠️⚠️ 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. -->
- VS Code Version: 1.85.2, 1.86, 1.88.1
- OS Version: reproducible on:
    - Windows 10 up-to-date
    - Debian 12 up-to-date, GNOME Shell 43.9, Xorg
    - Arch Linux up-to-date, GNOME Shell 45.3 & 46.0, Wayland 1.22.0

## Steps to Reproduce

1. Set pref `window.titleBarStyle` to `"custom"`
1. Tile VSCode to the right of the screen (under Windows or GNOME Shell: <kbd>Meta</kbd>+<kbd>Right</kbd>)
2. Try to scroll by clicking the right scrollbar at the right edge of the screen (the right-most column of pixels of the screen)

**Expected**: the **scrollbar** gets clicked and the buffer viewport **scrolls** up/down.

**Actual**: a **window border** gets clicked and the window **resizes**. This is annoying because it breaks _"throw mouse to very right and click"_, said differently it breaks [Fitt's Law](https://en.wikipedia.org/wiki/Fitts%27s_law), by increasing distance/difficulty to hit the right scrollbar.

## Screencast

https://github.com/microsoft/vscode/assets/522085/8a634c57-ec98-42f1-94a9-6c1863623279
Repository: flutter
Issue: Migrate Fuchsia artifacts from CIPD to GCS
Labels: platform-fuchsia,P2,team-release,triaged-release

Most engine artifacts exists on GCS, but Fuchsia is a corner case. For Google testing, we want to be able to support presubmit engine testing, which currently fails on missing Fuchsia artifacts.

The alternative to this is teaching CI about a separate CIPD path, but engine_v2 already has solved this for GCS. Instead, we'll migrate these are artifacts there.

There's only a few places relying on Fuchsia artifacts, so it will be quick to update.
Repository: pytorch
Issue: [Inductor] Kill Mutation Layout
Labels: feature,triaged,module: inductor,internal ramp-up task

### 🚀 The feature, motivation and pitch

We have replaced `MutationLayout` with `get_mutation_names()` throughout must of the code base but not entirely. See, existing PR: https://github.com/pytorch/pytorch/pull/112925. 

We should finish the migration and kill of the few remaining uses.

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @oulgen 



### Alternatives

_No response_

### Additional context

_No response_
Repository: pytorch
Issue: [Inductor] Unite all possible way to track mutation
Labels: feature,triaged,oncall: pt2,module: inductor,internal ramp-up task

### 🐛 Describe the bug

Currently there are many ways to track mutations in Inductor. Namely, `MutationLayout`, `InplaceHint`, etc used along with get_mutation_names and get_alias_names.

https://github.com/pytorch/pytorch/pull/112925 took the first step to replace `MutationLayout` with `MutationOutput` and `mark_node_as_mutating`. Lets kill and unite rest of mutation tracking with this too.

cc: @eellison @Chillee @zou3519 

### Error logs

_No response_

### Minified repro

_No response_

### Versions

master

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler
Repository: angular
Issue: bug(matSort): matSort used with Angular animations is leaking memory
Labels: area: animations,memory leak,area: forms,needs triage

### Is this a regression?

- [ ] Yes, this behavior used to work in the previous version

### The previous version in which this bug was not present was

_No response_

### Description

When destroying a matTable that uses matSort with ngIf / @if in a component that has Angular animations, detached elements and JS event listeners are left behind.

This behaviour can be reproduced with Angular version 16.2.12 and 17.1.1

I tried the following scenarios: App / Test component with Animation, without animation and only with an empty array inside test-component and app-component. Results are the following: 
![results](https://github.com/angular/components/assets/153174614/013a9054-f66e-48b7-9dff-53f169447a02)

When using an empty array in the app-component, the memory leak can't be reproduced:
![emptyArray](https://github.com/angular/components/assets/153174614/23cf617e-5727-4b91-814c-de7b861679eb)


### Reproduction

StackBlitz link: https://stackblitz.com/edit/angular-w6z5xl?file=src%2Findex.html
Please download the code from stackblitz and run it locally.
Steps to reproduce:
1. Click toggle test button and observe DOM node count and JS event listener count in Chrome performance monitor


### Expected Behavior

Garbage collector cleans up removed DOM nodes, event listener count not increasing

### Actual Behavior

DOM Node count and JS event listener count increasing steadily

### Environment

- Angular: 17.1.1
- CDK/Material: 17.1.1
- Browser(s): Google Chrome 120.0.6099.225 (Official Build) (64-bit)
- Operating System (e.g. Windows, macOS, Ubuntu): Microsoft Windows Version 22H2 (OS Build 19045.3803)
Repository: storybook
Issue: [Bug]: `viteFinal` does not honor (or pass through) `build` options
Labels: feature request,builder-vite

### Describe the bug

My Storybook Vite config is correctly inheriting most of my root Vite config, except the `build` object of options, which is missing from the input to `viteFinal`. Why is Storybook stripping this out?

### To Reproduce

_No response_

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 10 10.0.22631
    CPU: (8) x64 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz
  Binaries:
    Node: 18.16.0 - C:\Program Files\Node.js\node.EXE
    npm: 9.8.0 - C:\Program Files\Node.js\npm.CMD
    pnpm: 8.6.6 - C:\Program Files\Node.js\pnpm.CMD <----- active
  Browsers:
    Edge: Chromium (121.0.2277.83)
  npmPackages:
    @storybook/addon-actions: 7.6.7 => 7.6.7
    @storybook/addon-controls: 7.6.7 => 7.6.7
    @storybook/react: 7.6.7 => 7.6.7
    @storybook/react-vite: 7.6.7 => 7.6.7
    storybook: 7.6.7 => 7.6.7
```


### Additional context

_No response_
Repository: PowerToys
Issue: [Crop and Lock]: Add dark mode filter to cropped window.
Labels: Idea-Enhancement,Needs-Triage,Product-CropAndLock

### Description of the new feature / enhancement

A simpler way to force dark mode on a window.

There are many feedbacks requesting for a window dark mode tool.
#28439 #13005 #13225
Instead of making a new utility, adding an invert filter to the existing Crop and Lock utility would be easier to implement.

Add an "Invert" button to the title bar of the crop window, and clicking it will add an invert filter to the window image.

### Scenario when this would be used?

Users only need to reparent the application window, and then click "Invert" to force the application into dark mode.

In addition, it would be better if there is a shortcut key to quickly crop the entire window (Ctrl + A), or even invert it with one click.

### Supporting information

_No response_
Repository: pytorch
Issue: [NestedTensor] Support for operations found commonly in point cloud analysis architectures
Labels: triaged,enhancement,module: nestedtensor

### 🚀 The feature, motivation and pitch

Thanks all for such a great effort here. I do a lot of work on point cloud analysis (which often involves ragged data), and it would be great to have upstream support for this sort of thing instead of having to rely on heavyweight specialized libraries (i.e. Pytorch Geometric) which come with a lot of baggage/learning curve when creating simple pytorch networks. Lots of the common point cloud analysis architectures (PointNet++, PointNeXT, PointTransformer, etc.) involve a small handful of operations which are not yet implemented in the torch.nested module. Off the top of my head:

- nn.Conv{1D,2D}: Example: https://github.com/yanx27/Pointnet_Pointnet2_pytorch/blob/master/models/pointnet2_utils.py#L171
- BatchNorm{1D,2D}
- MaxPool{1D,2D}: Example: https://github.com/POSTECH-CVLab/point-transformer/blob/master/model/pointtransformer/pointtransformer_seg.py#L45

I've been able to hack the conv1d/2d operations reshaping / using Linear layers, since they're usually trying to do point-wise operations. But this mechanism is not efficient.

There are also various sampling/grouping operations (k-nearest-neighbors, "ball query", etc), which may or may not be efficient to implement using torch primitives (I know some of the other libraries use their own cuda implementations for certain ops, like [torch_cluster](https://pytorch-geometric.readthedocs.io/en/1.4.1/_modules/torch_cluster/radius.html).

If you think there might be interest/bandwidth to implement all or even a few of these operations, I'd be happy to:

more-thoroughly list the operations which would give reasonable coverage of point clouds
guinnea-pig new operations by implementing architectures/training procedures from some of the widely-used methods, to see that it matches expected performance.

### Alternatives

_No response_

### Additional context

_No response_

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer
Repository: rust
Issue: Lint against creating an invariant, perpetual `&mut` borrow (`&'a mut T<'a>`)
Labels: A-lints,T-lang,C-feature-request,A-variance

### Code

```Rust
pub struct Foo<'a> {
    // `Cow` just used as a convenient lifetime-bearing type
    pub foo: &'a mut std::borrow::Cow<'a, str>
}
```


### Current output

No output


### Desired output

```Shell
error: this mutable reference will borrow its referent forever
 3 | pub foo: &'a mut std::borrow::Cow<'a, str>
   |           --                      -- this use of `'a` requires it to outlive all values of type `std::borrow::Cow<'a, str>`
   |           |
   |           this use of `'a` requires the `std::borrow::Cow<'a, str>` to be exclusively borrowed until the end of `'a`    
   |
   = help: this type is valid, but almost certainly incorrect
   = help: use two distinct lifetime parameters instead: 
              <suggestions to change either the first or second to a newly introduced parameter>
   = note: `#[deny(perpetual_mut_borrow)]` on by default
```

### Rationale and extra context

`&'a mut T<'a>` is a fairly common beginner mistake. The compiler can even suggest it as an added lifetime annotation if one tries to construct a self-referential struct. It's not at all obvious that this is a mistake (especially as `&'a T<'a>` is valid and entirely suitable for many applications), and people become quite confused due to the additional, not obviously related, lifetime and drop errors that then result. Therefore, I believe it is worth having the compiler lint this case.

I propose that it be a deny-by-default lint so that

* it is more prominent than a default warning and indicates “this is so wrong that you need to stop and reassess”, but
* if someone _does_ have a situation where this is actually the correct lifetime (perhaps they truly intend to make a self-referential struct and use it inside an infinite loop), they can suppress the lint.

### Other cases

There may be some subtlety in applying the lint to arbitrary types. My hope is that a simple structural/syntactic rule is sufficiently precise to be helpful: if the same lifetime name appears _inside_ an `&mut` as the `&mut`'s own lifetime, then lint. But if it is feasible to directly check for "this reference is required to outlive-or-equal its referent" then that would more precisely identify the problem, including accounting for outlives bounds between two lifetimes that have the same effect.

### Rust Version

```Shell
rustc 1.75.0 (82e1608df 2023-12-21)
binary: rustc
commit-hash: 82e1608dfa6e0b5569232559e3d385fea5a93112
commit-date: 2023-12-21
host: x86_64-apple-darwin
release: 1.75.0
LLVM version: 17.0.6
```
Repository: go
Issue: proposal: x/tools/cmd/stringer: add -tag flag for constant name remapping, or improve line comment support
Labels: Proposal

### Proposal Details

Per the current implementation & documentation for stringer, we have a way to rename/remap constant names when we return them as string via `-linecomment` flag. But I can see cases, where comments are used for other explanatory purposes, and I'm not sure how I see you can combine a comment to both be used to rename constants with stringer, as well as preserve the other uses of the comment. I don't see how stringer currently handles that in the code:

https://cs.opensource.google/go/x/tools/+/refs/tags/v0.17.0:cmd/stringer/stringer.go;l=465

This is what I propose with 2 options to enhance the constant naming feature:

- enhance the line comment logic to support optional delimiting of comment text into sections, with the text before (first) delimiter treated as the value to rename constant name to, and text after that (first) delimiter treated as comments and ignored for the purposes of stringer. Perhaps the delimiter value can also be specified here, with default being either a comma or semicolon. If enabled this delimiting feature, comments can then be both for renaming and other uses. If not enabling this enhanced feature, then stringer's line comment feature behaves as it does currently.

- offer option of another flag to specify alternative naming than comments. Could we not use something like struct tags to label constants with alternative name for stringer? And if enabled with this flag, stringer parses the struct tags to get the alternate name, otherwise ignores the tags.

If there is already such functionality that I overlooked, please enlighten me.
Repository: excalidraw
Issue: old-deployment artifacts unavailability problem
Labels: SW-caching,build

We're getting a lot of errors where clients try to load chunks that do not exist.

![image](https://github.com/excalidraw/excalidraw/assets/5153846/e5039f7d-4cfd-4746-b99d-2ae8b9f185cc)
![image](https://github.com/excalidraw/excalidraw/assets/5153846/ebfa10c1-0854-4152-8c6e-9b40b886ea70)

Not confirmed, but the issue almost certainly arises from the fact that on each deployment, previous chunks are removed if changed (or possibly always, not sure), so if we still have clients on old versions (because their ServiceWorker didn't update) and they try to lazyload a chunk, it won't be hosted anymore.

Vercel recently introduced [Skew protection](https://vercel.com/blog/version-skew-protection) which addresses a similar issue, but focused on client/server divergence (e.g. serverless functions) within the next.js context — so not something we can use to solve this.

---

The only effective solution I can come up that at least sounds feasible is doing this:

On release, the build artifacts will be uploaded to AWS S3 or comparable, so that on subsequent release we'd merge the new build artifacts with previous N deployments, and then manually upload the build artifacts to Vercel (sidestepping their auto-deploy workflow).

This will require, manual build step, provisioning and maintaining a bucket, and manual deploy step to Vercel. Meaning, we'll have to sidestep any Vercel build/deploy automation. It's doable, but it's annoying, and it's also surprisingly slow.

Any other ideas, besides catching these errors and just telling people to hard-refresh?

/cc @ad1992
Repository: next.js
Issue: [PPR] > Parallel routes inside route groups not working with PPR (dev works, start doesnt)
Labels: bug,Parallel & Intercepting Routes,Partial Prerendering (PPR)

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/dank-cloud-t6f45n

### To Reproduce

1. Run build
2. Run start
3. See white screen (on my local machine it goes to 404, not sure why in the sandbox it displays white screen)

### Current vs. Expected behavior

Expected to render `@second/page.tsx` content since `@first/page.tsx` content is null.
FYI, dev works ok, it's only after build & start that the app doesnt work correctly.

Also when running dev, you can navigate to both '/' and '/any-other-path' and see the right results.

### 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: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.1.1-canary.20 // Latest available version is detected (14.1.1-canary.20).
  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) are affected? (Select all that apply)

Not sure, App Router

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

Again, just so It wont be missed, dev works ok, only  in prod this issue occours.