sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Storybook build fails in monorepo with pnpm
Labels: bug,needs triage

### Describe the bug

Storybook build fails in the monorepo environment.

While storybook dev works fine, storybook build crashes with the following error.


```
=> Failed to build the preview
Could not resolve "./button.css" from "../../node_modules/.pnpm/@storybook+react@8.5.1_@storybook+test@8.5.1_storybook@8.5.1_prettier@2.8.8___react-dom@19.0._6b4vza6cwbojtrjbcynfhg3dfy/node_modules/@storybook/react/template/cli/ts-3-8/Button.tsx"
file: /Users/johndoe/Projects/portal/node_modules/.pnpm/@storybook+react@8.5.1_@storybook+test@8.5.1_storybook@8.5.1_prettier@2.8.8___react-dom@19.0._6b4vza6cwbojtrjbcynfhg3dfy/node_modules/@storybook/react/template/cli/ts-3-8/Button.tsx
    at getRollupError (file:///Users/johndoe/Projects/portal/node_modules/.pnpm/rollup@4.32.0/node_modules/rollup/dist/es/shared/parseAst.js:396:41)
    at error (file:///Users/johndoe/Projects/portal/node_modules/.pnpm/rollup@4.32.0/node_modules/rollup/dist/es/shared/parseAst.js:392:42)
    at ModuleLoader.handleInvalidResolvedId (file:///Users/johndoe/Projects/portal/node_modules/.pnpm/rollup@4.32.0/node_modules/rollup/dist/es/shared/node-entry.js:20216:24)
    at file:///Users/johndoe/Projects/portal/node_modules/.pnpm/rollup@4.32.0/node_modules/rollup/dist/es/shared/node-entry.js:20176:26
```

The node_modules folder looks like this. Seems like there are no *.css files.
<img width="953" alt="Image" src="https://github.com/user-attachments/assets/a55bc57b-d160-4692-b715-fc2ce95d4a89" />


### Reproduction link

https://github.com/vladmiller/storybook-monorepo-reproduction

### Reproduction steps

1. pnpm install
2. cd apps/storybook
3. pnpm build-storybook

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 15.2
    CPU: (8) arm64 Apple M2
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 23.3.0 - ~/.nvm/versions/node/v23.3.0/bin/node
    npm: 10.9.0 - ~/.nvm/versions/node/v23.3.0/bin/npm
    pnpm: 9.15.4 - ~/Library/pnpm/pnpm <----- active
  Browsers:
    Safari: 18.2
  npmPackages:
    @storybook/addon-a11y: ^8.5.1 => 8.5.1 
    @storybook/addon-actions: ^8.5.1 => 8.5.1 
    @storybook/addon-backgrounds: ^8.5.1 => 8.5.1 
    @storybook/addon-docs: ^8.5.1 => 8.5.1 
    @storybook/addon-essentials: ^8.5.1 => 8.5.1 
    @storybook/addon-interactions: ^8.5.1 => 8.5.1 
    @storybook/addon-links: ^8.5.1 => 8.5.1 
    @storybook/blocks: ^8.5.1 => 8.5.1 
    @storybook/react: ^8.5.1 => 8.5.1 
    @storybook/react-vite: ^8.5.1 => 8.5.1 
    @storybook/test: ^8.5.1 => 8.5.1 
    storybook: ^8.5.1 => 8.5.1
```

### Additional context

_No response_
Repository: pytorch
Issue: Local config flags for torch.compile
Labels: triaged,oncall: pt2

internal x-post: https://fb.workplace.com/groups/1075192433118967/posts/1589701705001368/

Pitch: a new decorator to allow user code change configs midway through tracing.

cc @chauhang @penguinwu
Repository: opencv
Issue: Inconsistency between imwrite and imwriteanimation functions
Labels: bug,category: imgcodecs

### System Information

OpenCV version: 4.12.0-dev

### Detailed description

when i try to measure performance of `imwriteanimation` function by the code below i faced unexpected error ( indeed i accidentally created the Mat variable wrong type). i am not sure this can be considered as a bug.

test code output:
```
[ WARN:0@0.003] global loadsave.cpp:848 cv::imwrite_ Unsupported depth image for selected encoder is fallbacked to CV_8U.
0.0543036sec
0.0541429sec
[ERROR:0@0.126] global loadsave.cpp:973 cv::imwriteanimation_ imwriteanimation_('read_c.png'): can't write data: OpenCV(4.12.0-dev)
C:\projects\opencv\modules\imgproc\src\color.simd_helpers.hpp:94: error: (-2:Unspecified error) in function '__cdecl cv::impl::`anonymous-
namespace'::CvtHelper<struct cv::impl::`anonymous namespace'::Set<3,4,-1>,struct cv::impl::A0xf824bd31::Set<3,4,-1>,
struct cv::impl::A0xf824bd31::Set<0,2,5>,4>::CvtHelper(const class cv::_InputArray &,const class cv::_OutputArray &,int)'

> Unsupported depth of input image:
>     'VDepth::contains(depth)'
> where
>     'depth' is 1 (CV_8S)

0.0131287sec
```



### Steps to reproduce

```
#include <opencv2/highgui.hpp>
#include <opencv2/imgcodecs.hpp>
#include <opencv2/imgproc.hpp>
#include <iostream>

using namespace std;
using namespace cv;

int main( int argc, const char** argv )
{

    Mat m(2000,3000,CV_8SC4);

    TickMeter tm;
    tm.start();
    imwrite("read_a.png", m);
    tm.stop();
    cout << tm << endl;

    Animation tanimation;
    tanimation.frames.push_back(m);
    tanimation.durations.push_back(10);

    TickMeter tm1;
    tm1.start();
    imwritemulti("read_b.png", tanimation.frames);
    tm1.stop();
    cout << tm1 << endl;

    TickMeter tm2;
    tm2.start();
    imwriteanimation("read_c.png", tanimation);
    tm2.stop();
    cout << tm2 << endl;

    return 0;
}

```

### Issue submission checklist

- [x] I report the issue, it's not a question
- [ ] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [x] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: TypeScript
Issue: Display default values for property types.
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

- jsdoc property and default tooltip
- jsdoc declare default values on object properties
- use jsdoc property with default

### 🕗 Version & Regression Information

Unsure if it's always been this way.

### ⏯ Playground Link

https://www.typescriptlang.org/play/?filetype=js#code/LAKFHoCpNACTYAEAuBPADgUwCaYGawDeA9gEYBWmAxsgL6wAKATsegM5wKLotZNpEA5GwC2g2AB9YgkdnFTBAGwDmg+gG1mrNgDo2ASwBemALwy5AXVgAhAK7JkxAHawDxnZyQ9WmfqiJsyEz6TsoaWuw6igCGpJiKVnYOzrAxcYoeIPDgoBDQnohMmMi2TE5sRBFstAW4eNG2ishErkaYAFzSsoIANKmx8Z22TnUhOLA1WZA5IHjDNPopysVVABQAlERwsDtFJWVEk5OgisUtbpiwJl1yfWnxE1ewy8hr66BAA

### 💻 Code

```ts
/**
 * @typedef {object} Props
 * @property {'sm' | 'md' | 'lg'} [Props.size='md'] Button size.
 * @property {string} [Props.label] Button label.
 */

/**
 * @returns {Props}
 * @default { size: 'md', label: undefined }
 */
function getProps() {
    return {}
}

let { size = 'md', label } = getProps()
```


### 🙁 Actual behavior

Tooltip when hovering `size` destructured property:

```
let size: "sm" | "md" | "lg"
Button size.
```

### 🙂 Expected behavior

Tooltip when hovering `size` destructured property:

```
let size: "sm" | "md" | "lg"
Button size.
---
@default 'md'
```

### Additional information about the issue

Potentially relates to https://github.com/microsoft/TypeScript/issues/24746

When defining object property types using JSDoc default value notation, such as `@property {'sm' | 'md' | 'lg'} [Props.size='md']`, I'd like to see tooltip details about the default value. I assume the only way to denote default values with `@property` is to use `[key=value]` notation since `@default` cannot be inlined.
Repository: rust
Issue: Tracking issue for release notes of #134272: make rustc_encodable_decodable feature properly unstable
Labels: T-libs-api,relnotes,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #134272.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Library, Language
- [Remove `RustcDecodable` and `RustcEncodable`](https://github.com/rust-lang/rust/pull/134272)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @RalfJung, @ibraheemdev -- origin issue/PR authors and assignees for starting to draft text
Repository: rust
Issue: Tracking issue for release notes of #134679: Windows: remove readonly files
Labels: O-windows,T-libs-api,relnotes,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #134679.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [On recent versions of Windows `std::fs::remove_file` will now remove readonly files](https://github.com/rust-lang/rust/pull/134679)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @ChrisDenton, @Mark-Simulacrum -- origin issue/PR authors and assignees for starting to draft text
Repository: react
Issue: Bug: Support use in act testing API #25523
Labels: Status: Unconfirmed,Resolution: Needs More Information

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version:
Main branch (as of October 21, 2022, when PR #25523 was merged).

## Steps To Reproduce

1. Write a test that uses the use hook inside a component.

2. Wrap the test in act but do not await the thenable returned by act.

3. Observe that the test may fail or behave inconsistently due to improper task scheduling.

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:
javascript

import { act, render } from '@testing-library/react';
import React, { use } from 'react';

async function fetchData() {
  return Promise.resolve('data');
}

function Component() {
  const data = use(fetchData());
  return <div>{data}</div>;
}

test('use hook in act', async () => {
  await act(async () => {
    render(<Component />);
  });
});
<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
If the thenable returned by act is not awaited, tasks scheduled by use may not be flushed correctly, leading to inconsistent test behavior.

No warning is shown unless use is called, which can make debugging difficult.

## The expected behavior
The act API should fully support the use hook, ensuring tasks are properly scheduled and flushed.

A warning should be shown if the thenable returned by act is not awaited, helping developers identify potential issues.
Repository: opencv
Issue: imread animation PNG writing speed performance is dramatically bad
Labels: optimization,category: imgcodecs

### Describe the feature and motivation

using the test code below the result is as following.
```
0.0455906sec
0.0416175sec
0.465386sec
```
APNG encoder is 10x slower than the PNG encoder.

### Additional context

```
#include <opencv2/highgui.hpp>
#include <opencv2/imgcodecs.hpp>
#include <opencv2/imgproc.hpp>
#include <iostream>

using namespace std;
using namespace cv;

int main( int argc, const char** argv )
{

    Mat m(2000,3000,CV_8UC4);

    TickMeter tm;
    tm.start();
    imwrite("read_a.png", m);
    tm.stop();
    cout << tm << endl;

    Animation tanimation;
    tanimation.frames.push_back(m);
    tanimation.durations.push_back(10);

    TickMeter tm1;
    tm1.start();
    imwritemulti("read_b.png", tanimation.frames);
    tm1.stop();
    cout << tm1 << endl;

    TickMeter tm2;
    tm2.start();
    imwriteanimation("read_c.png", tanimation);
    tm2.stop();
    cout << tm2 << endl;

    return 0;
}

```
Repository: rust
Issue: Tracking issue for release notes of #135415: Add `File already exists` error doc to `hard_link` function
Labels: T-libs-api,relnotes,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #135415.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Add `File already exists` error doc to `hard_link` function](https://github.com/rust-lang/rust/pull/135415)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @Harshit933, @ChrisDenton -- origin issue/PR authors and assignees for starting to draft text
Repository: ollama
Issue: ollama with cpu to utilize the models locally
Labels: feature request

please make a more compatible version of ollama with cpu to utilize the models locally
Repository: react
Issue: Bug Report: decodeReply Causes Infinite Hang with FormData
Labels: Status: Unconfirmed,Resolution: Needs More Information

### React version
React 19 Beta

### Description
When calling decodeReply with a raw FormData object (without a zero chunk), it leads to the promise never rejecting, causing the application to hang indefinitely. This issue happens because the getRoot function is called after close(response), which leaves the connection open.

### Steps to Reproduce
Call decodeReply with a raw FormData object.
Ensure no zero chunk is passed.
Observe that the promise never rejects and the application hangs.

### Link to Code Example
missing


### The current behavior
When decodeReply is called with a raw FormData object, the promise remains unresolved, causing the application to hang indefinitely without rejecting.

### The expected behavior
The function should reject the promise appropriately when using FormData, preventing any indefinite hangs. The issue has been resolved by reordering the function calls so that close(response) occurs after getRoot(response).
Repository: flutter
Issue: SelectableText should have a selectionColor property
Labels: c: new feature,framework,f: material design,c: proposal,f: selection,team-framework

### Use case

If a Text can have a selectionColor, then a SelectableText should also be able to set this property, to set the color it should display when being selected.

### Proposal

I should be able to set a selection color for SelectableText

```dart
const SelectableText('Selectable Text') // No selectionColor
```

![Image](https://github.com/user-attachments/assets/18e99088-6901-4104-bf67-2a607fb5f714)

```dart
 const SelectionArea(
              child: Text(
                'Text wrapped in SelectionArea',
                selectionColor: Colors.red,
              ),
            )
```

![Image](https://github.com/user-attachments/assets/e287079d-3321-47d9-a41d-1c9f0ef2c89b)
Repository: flutter
Issue: conductor should run create_updated_flutter_deps.py
Labels: team-release

### Use case

When updating the dart_revision in DEPS for a release, there is a comment about running create_updated_flutter_deps.py:

https://github.com/flutter/flutter/blob/c1ffaa9d9deb3e0853176271922e0b1c1356d21f/DEPS#L53-L59

### Proposal

That script should be automatically run when using [conductor](https://github.com/flutter/flutter/tree/master/dev/conductor) to automate this process.
Repository: PowerToys
Issue: Cursor crosshair activate only selected lines, vertical and/or horizontal line
Labels: Needs-Triage

### Description of the new feature / enhancement

Like one only use vertical line.

### Scenario when this would be used?

I screenshot stock charts as pictures to review and don't need horizontal line, but only vertical line to help my eye to see the same timestamp of pair of price, macd, etc.

### Supporting information

_No response_
Repository: vscode
Issue: Output filter- support negative and multiple filters
Labels: feature-request,output

I love the new output filter, and it would be really useful to have negative filter patterns with `!` or multiple comma-separated patterns. Useful enough that I might do a PR if you don't have time and can point me to the code.

For example, I always have Copilot Chat in trace mode, but there are some very noisy logs that I'd like to filter out.
Repository: godot
Issue: Custom Resource.tres not updating values when the Resource.gd script values are changed
Labels: bug,topic:core,needs testing

### Tested versions

Godot v4.3.stable - Windows 10.0.26100 - GLES3 (Compatibility)

### System information

Godot v4.3.stable - Windows 10.0.26100 - GLES3 (Compatibility) - Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21921.1000) - 12th Gen Intel(R) Core(TM) i7-12700K (20 Threads)

### Issue description

When changing the default value of a variable in a custom resource script (.gd), existing .tres resource files display the new default value correctly in the Inspector, but at runtime, the old value is still applied.

Example:
- health_resource.gd { var value: int = 10}
- player_health.tres { displays 10 in the inspector }
- print(player_health} output = 10

Change the value:
- health_resource.gd { var value: int = 20}
- player_health.tres { displays 20 in the inspector }
- print(player_health} output = 10

### Steps to reproduce

1. Create a custom resource script "health_resource.gd".
2. set a variable in health_resource.gd, eg: var value: int = 10

3. Create a resource file "player_health.tres" from health_resource.gd:
   - The Inspector correctly displays value = 10. 
   - At runtime, print(player_health.value) outputs = 10. 

4. Modify the script to change the default value.
5. var value: int = 20
6. Observe the changes in the Inspector:     
   - Open "player_health.tres".  
   - The Inspector now displays "value = 20".  

7. Run the game and print the value:  
   print(player_health.value)
   - Expected output: 20
   - Actual output: 10 (old value)  

Additional Notes
- The `.tres` file retains the old value even though the "Inspector" shows the updated default. 
- Even when explicitly modifying the `.tres` file, the old value is applied at runtime.
- Deleting and recreating the `.tres` file applies the new default correctly.

### Minimal reproduction project (MRP)

Basic starter project.
Repository: PowerToys
Issue: Rotate videos on explorer
Labels: Needs-Triage

### Description of the new feature / enhancement

Rotate videos on explorer in the same way as we can with photos.

### Scenario when this would be used?

Hi, I'm a content creator and when I shoot videos with my professional camera, it doesn't automatically turn the videos, I always have to turn them manually in the program. It would be great if there was an option to select several videos and simply rotate them in the same way as you can with photos.

Here's my idea of a tool for future implementation. :)

### Supporting information

_No response_
Repository: go
Issue: x/tools/gopls: crashes due to apparent data race(s)
Labels: gopls,Tools,gopls/telemetry-wins,BugReport

While we've found and fixed many gopls crashes thanks to telemetry, as we gain more users it appears we're accumulating a long tail of issues that "can't happen" based on easily verifiable local invariants.

In some cases, these were related to misreporting of stacks by the runtime (#70637), but others cannot be explained by a misreported stack, and indicate some form of memory corruption or (most likely) data race.

This issue is an umbrella for those bugs. @adonovan and I will consolidate them here.
Repository: react-native
Issue: [iOS] a problem with codegen?
Labels: Platform: iOS,Resolution: PR Submitted,Type: New Architecture

### Description

Hey folks, will you please have a brief look at the issue I've created in `creact-react-native-library` repo: https://github.com/callstack/react-native-builder-bob/issues/755 (not sure whether that issue belongs there, or to the RN repo, as it seems to be caused by Codegen outputs).

Essentially, I am trying to upgrade my fork of `react-native-fs` to RN@0.77, on the way resetting the library scaffolding to the one generated by the latest version of the `create-react-native-library` generator. The upgraded code is here: https://github.com/birdofpreyru/react-native-fs/tree/dev-v2.31. I'm trying to build its Example App then, and it fails at the linking step, due to a clash between the same-named objects (like `RCTAppDependencyProvider`) present both in files generated by the codegen for the library itself, and for smth else.

I have confirmed that builds passes fine and the app works, if I just comment out the content of involved `.mm` files generated under `ios/generated` folder (relative to the repo's root); but I have no idea what is the root cause of the problem? Is it a bug inside the Codegen generating for the library some files it is not supposed to generate for it? Is it some mistake in my lib's configuration causing that Codegen behavior? Have I messed-up any other config in the project? Is it a problem with the project template used by `creact-react-native-library` (same problem happens with the new Turbo Module lib project generated by `create-react-native-library`, without any other modifications)?

I guess, it is very easy issue to narrow down for anybody who knows how exactly Codegen is supposed to behave here :) (thus, not for me 😅 )

### Steps to reproduce

N/A

### React Native Version

0.77.0

### Affected Platforms

Build - MacOS

### Areas

Codegen

### Output of `npx react-native info`

```text
N/A
```

### Stacktrace or Logs

```text
N/A
```

### Reproducer

N/A

### Screenshots and Videos

_No response_
Repository: PowerToys
Issue: Unable to copy and paste images between windows machines
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

copy image from one machine, attempt to paste on another

### ✔️ Expected Behavior

image pasted on second computer

### ❌ Actual Behavior

nothing happens

### Other Software

_No response_