sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: [Bug Fix]: Bring parity to JS declaration generation for classes with static private members to match TS declaration output.
Labels: Needs Investigation

### Acknowledgement

- [x] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

### Comment

- TS versions: All recent (5.x)

Problem:
When generating type declarations for ESM / Javascript classes with private static members including properties and methods the code path for JS declaration generation does not take into account the `private` / `#` state of the symbol or associated declaration when collecting static members. This results in those class members becoming publicly visible in the generated declarations and furthermore with the mangled internal names assigned to private declarations in the binding process. 

You can see the problem in this [TS playground example](https://www.typescriptlang.org/play/?strict=false&noImplicitAny=false&strictFunctionTypes=false&strictPropertyInitialization=false&strictBindCallApply=false&noImplicitThis=false&noImplicitReturns=false&alwaysStrict=false&esModuleInterop=false&target=9&jsx=0&ssl=2&ssc=2&pln=5&pc=1&filetype=js&strictNullChecks=false#code/MYGwhgzhAEAqCmEAu0DeAoa1liQS2GgGIAHAJzwDdd4BlJXAgBTIHsToBeaAcgDlWKMvAC2rSvAAm0AGasy0AFK1ok+KDBlGrAHbQA5vB3wt+XQG5oeGMLETpchbFoA6HufSZsDfIVIVqJDofAgAxHQAKAEo0aGEkAFcyPX5BONFxKVl5JRU1DVM8XQMjE20dS2t0uyzHOFd3aABfTyx-KhoWdi5eWAALKqrbTOk8PWVoAHp61XVwQuLDYwWdNw8vdsD4cOjY+KSU-sGbDPsrcZVp51mC8pLl8rXm9BagA). Notice the difference in the output `.d.ts`  when switching between `Javascript` and `Typescript` via the `TS Config` options. The JS declaration generation path does not filter out static private class members nor adds the `#private` identifier based on static private members.

Please see this brief overview video showing the current results on TS `5.7.2`:
https://github.com/user-attachments/assets/85e558fa-58e9-4192-b3ed-16c749e78b46

Expected Result:
That static private members of a class are removed from generated public type declarations in the same exact way for JS & TS source files. This is also valuable because this allows `import elision` to occur for any type references associated with static private members that may otherwise not be referenced in the public declarations.

Fix:
I have added the appropriate filtering step in `src/compiler/checker.ts` -> `serializeAsClass` to remove private static members from passing through to the output declarations. I have ensured that the `#private` identifier is correctly added for classes that only have private static members. I have added a test case and baseline reference. You can view the [code changes here](https://github.com/microsoft/TypeScript/compare/main...typhonjs-svelte-scratch:ts-static-priv:main).

PR: 
Upon review and acceptance of this bug & my proposed fix I can provide a timely submission of a PR. 

Future:
I am interested in fixing more JSDoc / Javascript / declaration generation issues improving support. I'm familiar with TS AST and the TS code area of impact in the declaration generation pipeline.
Repository: godot
Issue: Custom resources with built-in scripts cannot be assigned to typed variables in the inspector
Labels: bug,topic:gdscript,topic:editor

### Tested versions

Reproducible in: 4.3.stable.mono

### System information

Windows 11

### Issue description

Custom resources using built-in GDScript scripts display unexpected behavior in the Inspector. An `@export` variable of type `MyCustomResource`, `Array[MyCustomResource]`, and so on should allow all .tres files that extend that class to be added to the array. However, if the file's script is built-in it will not be accepted even if the built-in script extends MyCustomResource. If the variable is `Array[Resource]`, though, it will be accepted.

### Steps to reproduce

- Create a custom resource with a `class_name` of your choosing (such as `MyCustomResource`).
- Create another object with an `@export var my_var : MyCustomResource`.
_- Create a .tres of MyCustomResource in the FileSystem. This file can be assigned to `my_var` without issue and demonstrates the expected behavior._ 
- Create another Resource file and view in the Inspector. Right-click on its script slot and choose _New GDScript_ to create a script built-in to the .tres file.
- Add `extends MyCustomResource` to the top of the built-in script and save.
- This cannot be added to my_var in the Inspector.
It should be noted that writing `my_var : Resource`, adding the built-in-script-resource to it, then changing `my_var:MyCustomResource` seems to keep the built-in-script-resource's assignment, it just prevents actually assigning it in the Inspector

### Minimal reproduction project (MRP)

(None)
Repository: react
Issue: Bug: Nested Suspense Fallback Not Triggering for Child Component
Labels: Status: Unconfirmed,Resolution: Needs More Information


React version: 18

Steps To Reproduce
	1.	Create a component with nested <Suspense> boundaries:
	•	Parent <Suspense> wraps a parent component (DataParent) with a fallback.
	•	Child <Suspense> wraps a child component (DataChild) with its own fallback.
	2.	Pass data-fetching promises to both parent and child components using React.use() or async/await to simulate Suspense-compatible data fetching.
	3.	Ensure the child <Suspense> fallback is rendered only when the parent data is resolved but the child data is still loading.

Here’s a sample implementation:

```
"use client";

import * as React from "react";
import { Suspense } from "react";

interface ParentProps {
  dataPromise: Promise<{ items: string[] }>;
  children?: React.ReactNode;
}

function Parent({ dataPromise, children }: ParentProps) {
  const data = React.use(dataPromise);

  return (
    <div className="parent">
      <h2>Parent Data</h2>
      <ul>
        {data.items.map((item, idx) => (
          <li key={idx}>{item}</li>
        ))}
      </ul>
      {children}
    </div>
  );
}

```
```
interface ChildProps {
  detailPromise: Promise<{ detail: string }>;
}

async function Child({ detailPromise }: ChildProps) {
  const detail = await detailPromise;

  return (
    <div className="child">
      <h3>Child Detail</h3>
      <p>{detail.detail}</p>
    </div>
  );
}
```
```

export default function SuspenseExamplePage() {
  const parentDataPromise = new Promise<{ items: string[] }>((resolve) => {
    setTimeout(() => resolve({ items: ["Item 1", "Item 2"] }), 1000);
  });

  const childDataPromise = new Promise<{ detail: string }>((resolve) => {
    setTimeout(() => resolve({ detail: "Detailed information" }), 2000);
  });

  return (
    <Suspense fallback={<div>Loading Parent...</div>}>
      <Parent dataPromise={parentDataPromise}>
        <Suspense fallback={<div>Loading Child...</div>}>
          <Child detailPromise={childDataPromise} />
        </Suspense>
      </Parent>
    </Suspense>
  );
}
```

## The current behavior

When loading the parent and child components:
	•	The fallback for the parent ("Loading Parent...") renders as expected while the parent data is loading.
	•	After the parent data resolves, the child fallback ("Loading Child...") does not trigger.
	•	Instead, the parent content renders immediately, and the child fallback is skipped altogether.
	
	

## The expected behavior

When the parent data resolves and the child data is still loading:
	•	The parent content should render normally.
	•	The child fallback ("Loading Child...") should render until the child data is ready.
Repository: flutter
Issue: [two_dimensional_scrollables] Tap Animations for row click and hover animations
Labels: c: new feature,a: animation,package,c: proposal,P3,team-framework,triaged-framework,p: two_dimensional_scrollables

### Use case

The new table view is powerful, however, it is missing one important feature that DataTable has, which is having tap animations like the material ripple and hover states for individual row.

### Proposal

provide a way to give hover state styling and ripple effects for taps and other gestures
Repository: rust
Issue: How much stack space should Windows reserve for stack overflow exceptions?
Labels: A-runtime,O-windows,T-libs,C-discussion

We reserve some stack space for handling stack overflow exceptions. Our exception handler just prints a stack overflow message along with the thread name. Currently we reserve ~20kb of stack:

https://github.com/rust-lang/rust/blob/903d2976fdb6ceeb65526b7555d8d1e6f8c02134/library/std/src/sys/pal/windows/stack_overflow.rs#L8C59-L8C65

This number is somewhat arbitrary and was chosen over a decade ago, pre-1.0, when Rust was a very different language. That said, we set the main thread to have a stack size of 1mb by default so 20kb is just a few percent of it. Still, sometimes every byte counts and I think it would be useful to have some kind of rationale for the number (e.g. is, say, 4kb not enough?).
Repository: vscode
Issue: TreeView nesting performance
Labels: bug,tree-widget

TreeView has some serious performance problems at high nesting levels
(unrelated to https://github.com/microsoft/vscode/issues/232263)

Steps to Reproduce:

1. create JSON file with snippet
```json
[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[[]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]]
```
2. open OutLine
3. scroll down to the bottom
4. freeze 🐛

![Image](https://github.com/user-attachments/assets/eff89294-d304-4072-a5ed-8ad71789502d)

performance is also exaggerated more by StickyScroll `"workbench.tree.enableStickyScroll": true`
this also affects the dropdown Breadcrumbs view

dup https://github.com/microsoft/vscode/issues/205840

cc @alexr00 

Does this issue occur when all extensions are disabled?: Yes

- VS Code Version: 1.96.0
- OS Version: Windows 11
Repository: vscode
Issue: Git - git.blame.editorDecoration.enabled should honor '.git-blame-ignore-revs'
Labels: feature-request,git

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

For some commits (formatting code, etc.) we use the file '.git-blame-ignore-revs'. It would be nice if this settings could also skip commits listed in that file when displaying the blame information.
Repository: flutter
Issue: Flutter bundles assets from all packages in a pub workspace
Labels: tool,a: assets,a: build,has reproducible steps,team-tool,found in release: 3.27,found in release: 3.28

When using the new pub workspaces, I've found a bug where assets from all packages are bundled in the built app, rather than assets from just the packages that the Flutter app depends on.

This seems to occur when packages in the workspace depend on a common shared package - in this case one called `base`.

### Steps to reproduce

Given a Flutter monorepo that uses pub workspaces in this setup:

* base - a Flutter package with an asset
* included_package - a Flutter package with an asset that depends on base
* excluded_package - a Flutter package with an asset that depends on base
* app - a Flutter app that depends on ONLY included_package

Build the app via `flutter build web` in the `app` package.

### Expected results

A Flutter app is built containing only the assets from `included_package`.

### Actual results

A Flutter app is built containing the assets from all packages.

### Code sample

<details open><summary>Code sample</summary>
See this Github repo for a sample:  https://github.com/josh-burton/flutter_workspace_assets_bug

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.27.0, on macOS 15.1.1 24B91 darwin-arm64, locale en-NZ)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 16.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] IntelliJ IDEA Ultimate Edition (version 2024.2.5)
[✓] IntelliJ IDEA Ultimate Edition (version 2024.3.1)
[✓] VS Code (version 1.95.3)
[✓] Connected device (4 available)
    ! Error: Browsing on the local area network for Ark iPhone (2). Ensure the device is unlocked and attached with a cable or associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)
[✓] Network resources

• No issues found!

```

</details>
Repository: vscode
Issue: Broken vscode after update
Labels: bug,install-update

<!-- ⚠️⚠️ 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.96.0 (user setup)
- OS Version: Windows 11

Steps to Reproduce:

I updated vscode to 1.96 after being prompted in app.

After update, which seemed to go smoothly, I was unable to start vscode, and I was told 'executable missing'. After searching for the executable, I found it in `C:\Users\caj\AppData\Local\Programs\Microsoft VS Code\_` (note weird file underscore). The main "Microsoft VS Code" directory just contains 3 files,  `unins000.dat`, `exe` and `msg`, and some directories.

`winget install Microsoft.VisualStudioCode` tells me it can't reinstall vscode, as it's already installed.

If I run `code.exe` from inside the `_` directory, things seem to work fine.

I plan on blasting the whole thing away, and reinstalling from scratch, but I'll wait a day before doing that, just in case there is a log file anyone wants me to grab, in case they want to figure out how I ended up in this situation.
Repository: vscode
Issue: Git - add a delay before showing git blame information
Labels: feature-request,git

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Currently the decoration shows instantly. I want to add a short delay (like 1 second) before it get rendered because it looks a little noisy.
Repository: pytorch
Issue: torch.onnx.errors.UnsupportedOperatorError: Exporting the operator 'aten::_native_multi_head_attention' to ONNX opset version 18 is not supported
Labels: module: onnx,triaged

### 🚀 The feature, motivation and pitch

torch.onnx.errors.UnsupportedOperatorError: Exporting the operator 'aten::_native_multi_head_attention' to ONNX opset version 18 is not supported

### Alternatives

_No response_

### Additional context

the version of my project:
```
torch                         2.4.1
torchaudio                    2.4.1
torchvision                   0.19.1
onnx                          1.17.0
onnxruntime                   1.19.2
```
Repository: godot
Issue: Writing to stdout from GDExtension crash the engine with system-provided `icu4c`
Labels: bug,topic:buildsystem,confirmed,topic:thirdparty,topic:gdextension

### Tested versions

Reproducible in recent Godot 4.x version that build with `builtin_icu4c=no` (latest attempt is Godot v4.4.dev (1fb619607))

### System information

Godot v4.4.dev (1fb619607) - Freedesktop SDK 24.08 (Flatpak runtime) on Wayland - Wayland display driver, Single-window, 1 monitor - Vulkan (Forward+) - dedicated AMD Radeon RX 6650 XT (RADV NAVI23) - 12th Gen Intel(R) Core(TM) i5-12500 (12 threads)

### Issue description

If Godot is built with `builtin_icu4c=no`, writing to stdout from GDExtension will result a segfault. A MRP is provided below.

### Steps to reproduce

1. Build example GDExtension library with `scons`.
2. Open the project with Godot editor that has every libraries.
3. The project scene runs successfully, `print` appear on stdout.
4. Build Godot editor with `builtin_icu4c=no`, and run the project.
5. Scene crashed with signal 11 when trying to output `print`.

### Minimal reproduction project (MRP)

https://github.com/j20001970/godot_builtin_icu4c_stdout_crash
Repository: next.js
Issue: when css url include '!!', next build is error
Labels: create-next-app

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/condescending-dream-9gh3ys

### To Reproduce

1、open https://codesandbox.io/p/devbox/condescending-dream-9gh3ys
2、npm run build
3、error
![image](https://github.com/user-attachments/assets/ec8629ed-ae65-46ba-adf3-66ab7e686f4e)


### Current vs. Expected behavior

i hope next build is success

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.1.1-canary.1 // Latest available version is detected (15.1.1-canary.1).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

create-next-app

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

lasted version
Repository: vscode
Issue: Improve proposed `editorHoverVerbosityLevel`
Labels: feature-request,api,editor-hover

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
For a language server, to compute a `Hover` of a different level, the typical expectation is for the client to directly inform me of the required level.
However, the current `HoverContext` only provides the last `Hover` object and the difference in levels.
I cannot determine the previous `Hover` level from this information, thus unable to compute the current level.
It is hoped that a `currentLevel` field can be included in the `HoverContext` to represent the cumulative value of all `verbosityDelta`. Alternatively, a `data` field could be provided for me to pass context information myself.
Repository: flutter
Issue: [embedder] Software Pixel Formats, Compositor documentation issue
Labels: engine,e: embedder,P3,team-engine,triaged-engine,d: docs/

In the flutter_embedder.h, the order of the components for packed software pixel formats is incorrectly documented as being the order in the native type, least-significant-bit first:

https://github.com/flutter/engine/blob/main/shell/platform/embedder/embedder.h#L329-L332

In reality it's the other way around. For RGB565, the R is the 5 most significant bits in the 2-byte pixel value, rather than the least significant bits. The test even verify it is that way:

https://github.com/flutter/engine/blob/main/shell/platform/embedder/tests/embedder_unittests.cc#L2782-L2785

PR: https://github.com/flutter/engine/pull/57156
Repository: tauri
Issue: [feat] Local server proxy
Labels: type: feature request

### Describe the problem

I would like to be able to "mount" `https://example.com/api/` under
`http://tauri.localhost/api/` so that all my requests could be same origin and easy to use. 
`@tauri-apps/plugin-http` is cool but it doesn't solve problem with urls in  `<img />` tags. 
Also cookie stores are separated so I can't access my private images if I log in using `plugin-http`.
Another problem with current approach is that request don't show up in devtools which makes debugging more difficult especially on android.

### Describe the solution you'd like

Basically I would need something like server proxy in Vite https://vite.dev/config/server-options#server-proxy
but for production use.

### Alternatives considered

alternatively ability to create own endpoints in rust. This could be even more versatile 
`POST http://tauri.localhost/api/custom/endpoint`

### Additional context

_No response_
Repository: bitcoin
Issue: CI: Cmake warnings should be errors
Labels: Build system,CI failed

It is brittle to silently ignore Cmake warnings in the CI.

They should be turned into errors.

This will uncover an issue in the centos task that the correct python version is missing. I guess this should be fixed by installing and activating an acceptable python version.
Repository: vscode
Issue: No reset location when moving SCM graph out of container and right clicking title header with default activity bar
Labels: bug,workbench-views

<img width="667" alt="Image" src="https://github.com/user-attachments/assets/13015c75-a6e0-4ffa-b2b8-15bd70051b43" />