sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: autodoc for angular components does not include jsdoc-documentation
Labels: bug,angular,needs triage

### Describe the bug

There are issues regarding the same problem (#21387, #11674) which are already closed, but the problem still exists.

The autodoc documentation does not contain the information from jsdoc-comments. Just add storybook to an existing angular project and check the documentation of Example/Button (which is created during the installation of storybook), which looks like this:

![story-book-autodoc](https://github.com/storybookjs/storybook/assets/1615068/35715688-f13b-4a1b-9ad6-c996b1eb0b80)

I've created a stackblitz reproduction (uploaded my local project), but at the time of creating this issue, running `npm install` at stackblitz was always failing with ECONNRESET. Downloading the project from stackblitz and trying locally works.


### Reproduction link

https://stackblitz.com/edit/stackblitz-starters-dcmzh2

### Reproduction steps

1. `ng new storybook-doc-test --create-application=false`
2. `cd storybook-doc-test`
3. `ng g library @sb/doc-test`
4. `npx storybook@latest init`  (question regarding compodoc answered with yes, but the problem still exists, if answered with no)
5. since the latest compodoc-version has a dependency to angular 18 (which causes a warning during npm install, because the node-version I'm using is not compatible with angular 18), I've changed the version of compodoc to "1.1.21"
6. `npm install` again
7. `npm run storybook`

=> look at the documentation for the button-component, which was created by storybook itself => all the jsdoc comments do not show up in the documentation, therefore it is quite useless.



### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics   
  Binaries:
    Node: 18.19.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.21 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.2.3 - C:\Program Files\nodejs\npm.CMD <----- active
    pnpm: 8.4.0 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Chrome: 114.0.5735.134
    Edge: Chromium (126.0.2592.87)
  npmPackages:
    @storybook/addon-docs: ^8.2.0 => 8.2.0
    @storybook/addon-essentials: ^8.2.0 => 8.2.0
    @storybook/addon-interactions: ^8.2.0 => 8.2.0
    @storybook/addon-links: ^8.2.0 => 8.2.0
    @storybook/addon-onboarding: ^8.2.0 => 8.2.0
    @storybook/angular: ^8.2.0 => 8.2.0
    @storybook/blocks: ^8.2.0 => 8.2.0
    @storybook/test: ^8.2.0 => 8.2.0
    storybook: ^8.2.0 => 8.2.0
```


### Additional context

The angular cli version used to create the project was 17.3.8.
Repository: storybook
Issue: [Bug]: Color control automatically pops up, without triggering the control itself
Labels: addon: controls

### Describe the bug

When visiting a story with a color control, the control will automatically open

### Reproduction steps

1. Go to https://634ff0d0ec053b270775979d-vpmrbjlyny.chromatic.com/?path=/story/addons-controls-basics--undefined
2. In the controls panel, the color picker is automatically opened

![image](https://github.com/storybookjs/storybook/assets/5889929/88c0ce72-abb6-42f8-823d-71a2945c1b7f)



### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Angular - Source Code view doesn’t show args mapping
Labels: bug,help wanted,angular,sev:S3

### Describe the bug

The source view always shows the element rendered without any properties.

### Reproduction steps

1. Create a story for an Angular components
2. Write a story with some arguments defined for the component
3. Go to the autodocs page and open the Source code view
4. The args aren't shown

![image](https://github.com/storybookjs/storybook/assets/5889929/fcd882aa-77b5-435f-b142-77e670ebf81e)

### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Inconsistent behavior of showing stories with mount-in-play functions on auto docs pages
Labels: bug,needs triage

### Describe the bug

An autogenerated docs page will show the first story with the following error message if it uses mount in the play function:

```
This story mounts inside of play. Set autoplay to true to view this story.
```

The `STORIES` section does not show any story which uses the mount function.

As discussed with @kasperpeulen and @shilman, we no longer want to filter out the stories.

![image](https://github.com/storybookjs/storybook/assets/5889929/5288000d-90ae-4f61-9e75-b00a5d21c5bd)
Repository: pytorch
Issue: Error occurred when executing KolorsSampler:
Labels: feature,triaged,module: mps

### 🐛 Describe the bug

Error occurred when executing KolorsSampler:

The operator 'aten::_linalg_solve_ex.result' is not currently implemented for the MPS device. If you want this op to be added in priority during the prototype phase of this feature, please comment on https://github.com/pytorch/pytorch/issues/77764. As a temporary fix, you can set the environment variable `PYTORCH_ENABLE_MPS_FALLBACK=1` to use the CPU as a fallback for this op. WARNING: this will be slower than running natively on MPS.

### Versions

Error occurred when executing KolorsSampler:

The operator 'aten::_linalg_solve_ex.result' is not currently implemented for the MPS device. If you want this op to be added in priority during the prototype phase of this feature, please comment on https://github.com/pytorch/pytorch/issues/77764. As a temporary fix, you can set the environment variable `PYTORCH_ENABLE_MPS_FALLBACK=1` to use the CPU as a fallback for this op. WARNING: this will be slower than running natively on MPS.

cc @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen
Repository: vscode
Issue: Packaging task has poor parallelization
Labels: debt,engineering

<!-- ⚠️⚠️ 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: `main`
- OS Version: Linux Devcontainer

Steps to Reproduce:

1. Clone out repository
2. Start Devcontainer
3. Run `yarn gulp vscode-linux-x64`

The build&package process takes about 45 minutes and only uses about 1 core out of 48 available ones. If it would allow for better parallelization, this task could be reduced to about 1 minute.
Repository: godot
Issue: `filesystem/external_programs/*` doesn't really work on macOS
Labels: bug,platform:macos,topic:editor

### Tested versions

Reproducible in: 4.3.beta [ec02d406ca0b9c822addff49cf58e9a72cf74eb0]

### System information

macOS 13.6.7

### Issue description

When trying to use the `filesystem/external_programs/*` editor settings on macOS, like for example `filesystem/external_programs/raster_image_editor`, there are several issues currently:

1. When clicking the button next to the setting you're met with a dialog to pick a file, whereas applications on macOS are folders (`*.app`) (generally located in `/Applications`) making you have to dig through the `*.app` folder to look for the relevant binary, of which there may be several.
2. Even if you point the setting to the appropriate `*.app` folder, for example `/Applications/Adobe Photoshop 2024/Adobe Photoshop 2024.app`, it'll open Photoshop when executing the "Open in External Program" action in the FileSystem dock, but it won't actually open the desired file within Photoshop. This is true even if you point the setting to the actual binary within the `*.app` folder as well.

Note that the second problem doesn't manifest with all applications. Things seem to work fine with Krita for example, but not with Photoshop. ~~Either way, I believe the idiomatic way of opening applications like this on macOS is using `/usr/bin/open` (which seems to work fine) as opposed to the traditional Unix-style invocation.~~

~~It seems to me that the following changes need to be made:~~

1. ~~Change these settings to use `PROPERTY_HINT_GLOBAL_DIR` on macOS.~~
2. ~~Ideally have the dialog open in `/Applications` right away, if possible.~~
3. ~~Open the application using `open /Applications/Some.app --args /Path/To/File` rather than `/Applications/Some.app /Path/To/File`.~~

Also note that just using "Open in External Program" without having these settings assigned works fine, as that goes through `OS_MacOS::shell_open` rather than `OS_Unix::create_process`, but that requires having assigned the program as the default in macOS, which may not be desirable.

### Steps to reproduce

1. Open any project with a raster image file in it.
2. Go to "Editor Settings" > "FileSystem" > "External Programs".
3. Point "Raster Image Editor" to Photoshop (e.g. `/Applications/Adobe Photoshop 2024/Adobe Photoshop 2024.app`).
4. Right-click a raster image file in the FileSystem dock.
5. Click "Open in External Program".
6. Note how Photoshop launches.
7. Note how the file itself doesn't open in Photoshop.

### Minimal reproduction project (MRP)

N/A
Repository: ant-design
Issue: Body is not styled in V5 as it was in V4
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/antd-reproduce-5x-7oix8v?file=demo.tsx)

### Steps to reproduce

Run the reproduction app. Inspect styling of the "This child is placed in the document body." element that is teleported to the body.

### What is expected?

Element teleported to the body should inherit styling from antd theme.

### What is actually happening?

Teleported element is not inheriting styles, as styles are only applied starting from Layout antd component, which is inside the body and container element, where app is rendered.
In previous version body was styled using those less variables:
```
body {
  color: @text-color;
  font-size: @font-size-base;
  font-family: @font-family;
  font-variant: @font-variant-base;
  line-height: @line-height-base;
  background-color: @body-background; // 2
  font-feature-settings: @font-feature-settings-base;
}
```
Now it is not happening, since antd V5 uses css-in-js.

| Environment | Info |
| --- | --- |
| antd | 5.19.1 |
| React | 17.0.2 |
| System | macOS Sonoma 14.5 |
| Browser | Google Chrome Version 126.0.6478.127 (Official Build) (arm64) |

---
1. I know this philosophy to make body being styled with theme variables contradicts to using css-in-js, but maybe you have some idea how can we go around it? Probably use the same variable in theme and in body styles. But I think this is a general issue, as it is often needed to teleport stuff to body to be properly displayed.
2. I noticed, that in the reset.css you do not provide font family for body, but you provide monospace font family for monospace html tags. Why? What if someone change fontFamilyCode in the theme - that won't be reflected in the reset.css?

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: ollama
Issue: Please add new model about academic LLM
Labels: model request

Hi,
Could you please add some LLM models which has been trained with a lot of academical research papers? Thus we can ask professional questions to it. I don't seek something that can read research paper but something has been trained with them.
Thank you very much!
Repository: next.js
Issue: getServerSideProps: setHeader("Cache-Control", ...) is ignored for 404 pages 
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/elated-mendeleev-ygp74n?file=%2Fpages%2Findex.tsx%3A4%2C1

### To Reproduce

```tsx
export const getServerSideProps() {
  res.setHeader('Cache-Control', 'max-age=0, s-maxage=300')
  return { notFound: true }
}
```

The Cache-Control header remains unchanged.

### Current vs. Expected behavior

I would expect Next.js to honor the `Cache-Control` header if set by the developer. Other headers are properly set by Next.js on 404 pages.

I think the fix would be to check if the header is already set, otherwise default.



### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.1.3
  eslint-config-next: 14.2.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.5.2
Next.js Config:
  output: N/A
```


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

Pages Router

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

next start (local)

### Additional context

Could this be the relevant line? https://github.com/vercel/next.js/blob/caa2bb1dc692f89028f3c33948c00bf39e9501a8/packages/next/src/server/lib/router-server.ts#L527C3-L531C8

There might be other places as well.
Repository: godot
Issue: `CSGSphere3D`'s has less rings than the specified
Labels: bug,discussion,breaks compat,topic:3d

### Tested versions

v4.3.beta.custom_build [82cedc83c]

### System information

Windows 11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; 31.0.15.4633)

### Issue description

`CSGSphere3D` on the left and a mesh instance `SphereMesh` on the right. They both are configured with 5 `rings` but the `CSGSphere3D` produces a mesh with 4 rings instead. The result is always `rings`-1.

![image](https://github.com/godotengine/godot/assets/133662278/16ed1c65-b5ce-4990-ba83-f72e61efa23c)


### Steps to reproduce

* Add a `CSGSphere3D`. Set `rings` to 5.
* Add `MeshInstance3D`. Set `rings` to 5.
* Enable display wireframe.

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: Problems tree view cuts off error message when in sidebar, should be more responsive
Labels: feature-request,error-list

When I move the Problems panel to the side bar, and it's in tree view, it cuts off the error messages (highlighted in yellow) in favor of displaying error codes and Ln/Col numbers.

![image](https://github.com/microsoft/vscode/assets/524783/1764cab1-bb52-444e-af3f-eadc3ea16284)

In a narrow space, I would suggest that the priority of things to display should be roughly the following:

1. Error message (most important)
2. Line number
3. Error code
4. Column number (least important)
Repository: TypeScript
Issue: Expose MappedType in typescript.d.ts
Labels: Suggestion,In Discussion

### 🔍 Search Terms

mappedtype interface typeParameter constraintType templateType

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Coming over from typescript-eslint, we need to look at the properties on mapped types for the [`@typescript-eslint/no-unnecessary-type-parameters` ("Golden Rule of Generics") rule](https://typescript-eslint.io/rules/no-unnecessary-type-parameters). But, `MappedType` is marked as `@internal` in TypeScript's definition:

https://github.com/microsoft/TypeScript/blob/22bbe867fd4b86e2187270f6c284e6cfd92a3fea/src/compiler/types.ts#L6584-L6594

Could we have that interface be public, please? Even if all the fields other than `constraintType`, `templateType`, and `typeParameter` are switched to `@internal`. I don't know of a more sanctioned way to access those type properties. Is there one?

### 📃 Motivating Example

Marking `MappedType` as public would provide a way for type checker API consumers to reason about mapped types.


### 💻 Use Cases

See https://github.com/typescript-eslint/typescript-eslint/pull/8173 & https://github.com/typescript-eslint/typescript-eslint/pull/9530: in typescript-eslint, we need to access a few properties of mapped types to check if they're uses of a type parameter. We ended up writing [our own `interface MappedType extends ts.ObjectType`](https://github.com/typescript-eslint/typescript-eslint/blob/88dd82803d252be1aff4f440bea34e82d3a85d23/packages/eslint-plugin/src/rules/no-unnecessary-type-parameters.ts#L373-L375):

```ts
interface MappedType extends ts.ObjectType {
  typeParameter?: ts.Type; // #8173
  constraintType?: ts.Type; // #9530
  templateType?: ts.Type; // #9530
}
```
Repository: vscode
Issue: undo not working in settings search input when i paste some text
Labels: bug,settings-editor,confirmed

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.91
- OS Version: win10 and macos

Steps to Reproduce:

1. ctrl v to paste some text in search input
2. the first ctrl z not working and try to again. it's ok!

![image](https://github.com/microsoft/vscode/assets/26105827/7a7251c6-0b72-4e21-a6ae-7d0bed6a1ffa)
Repository: bitcoin
Issue: utils: add support for `bitcoin-wallet` tool configuration file
Labels: Feature

### Please describe the feature you'd like to see added.

I would like to propose the addition of support for a configuration file specifically for the `bitcoin-wallet` tool. This feature would allow users to specify command-line options in a configuration file (e.g., `wallet.conf`), similar to how `bitcoin.conf` works for `bitcoind`. The configuration file should be automatically loaded by `bitcoin-wallet` if present in the default data directory or specified via a command-line option.

### Is your feature related to a problem, if so please describe it.

Yes, this feature is related to the problem of having to repeatedly specify command-line options every time the `bitcoin-wallet` tool is used. For users who frequently interact with the `bitcoin-wallet` tool, it can be cumbersome and error-prone to enter the same options repeatedly, such as `-datadir`, `-wallet`, and debugging options.

### Describe the solution you'd like

- **Configuration File Support**: Implement support for a `wallet.conf` file that can contain the various options and arguments currently passed via the command line.
- **Automatic Loading**: If a `wallet.conf` file is found in the default data directory, it should be automatically loaded by the bitcoin-wallet tool.
- **Command-line Override**: Allow users to specify an alternative configuration file location using a `-conf=<file>` command-line option.
- **Option Precedence**: Command-line options should take precedence over those specified in the configuration file, allowing for flexible and dynamic usage.

### Describe any alternatives you've considered

_No response_

### Please leave any additional context

_No response_
Repository: godot
Issue: Overriding a native method does not display a warning for addons
Labels: discussion,topic:gdscript

### Tested versions

- Reproducible in v4.3.beta2.official [b75f0485b]

### System information

Ubuntu 24.04 LTS

### Issue description

In plugins, when overriding a native built-in method of a node in a derived class, no warning is displayed to indicate that this is not permitted and that the method will never be called.
![image](https://github.com/godotengine/godot/assets/44928041/d4a8a561-c1b6-42d5-83bb-43f36d80a650)
Warnings are displayed in the terminal if you start godot from it, but not in the editor.

### Steps to reproduce

- Create a plugin.
- Add a custom class that extends any node.
- Override any native method of the base node: No warning is displayed.
- Reload project: Warnings are displayed in the terminal if this is how you started godot, but not in the editor.


### Minimal reproduction project (MRP)

[mrp-overriding-native-method-no-warnings.zip](https://github.com/user-attachments/files/16162826/mrp-overriding-native-method-no-warnings.zip)
Repository: deno
Issue: Bug: `deno task` erroring on brace expansion
Labels: bug,node compat,task runner

## Steps to reproduce

1. Clone https://github.com/sass/node-sass
2. Run `npm i`
3. Run `DENO_FUTURE=1 deno task test`

Error:
```sh
$ DENO_FUTURE=1 deno task test
Task test mocha test/{*,**/**}.js
error: Error parsing script 'test'.

Caused by:
    Unexpected character.
      {*,**/**}.js
```

Version: Deno 1.44.4
Repository: vscode
Issue: BUG: `Move line down` command doesnt preserve indentation
Labels: bug,editor-autoindent


<!-- ⚠️⚠️ 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. -->
Version: 1.91.0
Commit: ea1445cc7016315d0f5728f8e8b12a45dc0a7286


Steps to Reproduce:

1. Put TS code
```ts
import {
    bla
} from 'bla';
```
2. Being on first line use command `Move line down`, move `import` on second line
3. Now move `import` back to first line
4. Formatting is lost:
```ts
import {
bla  // here is lost original formatting
} from 'bla';
```
Repository: rust
Issue: Guarantee that thread-local storage destructors run before join() returns
Labels: T-libs-api,A-docs,A-thread-locals,C-discussion,A-thread

As discussed in https://github.com/rust-lang/rust/issues/116237#issuecomment-2217941740, this is already the implemented behaviour but it is not guaranteed. Unless there is a good reason not to, this guarantee should be made and documented.