sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Tree shaking not working for pages with transpilePackages
Labels: bug,Performance,Pages Router,linear: next

### Link to the code that reproduces this issue

https://github.com/capJavert/nextjs-tree-shaking-test

### To Reproduce

1. Build application in production
2. Check `_app` bundle and it will contain `bla` const and other exports/imports from `shared/src/consts/common.ts` even though that const is only imported inside `/test` page

### Current vs. Expected behavior

We would expect `bla` to be tree shaken out of the main bundle (`_app`) and to only be included inside that page's bundle.

The above is just a small test but on a big application this has a major bundle size implications. 

The shared package is also added to `transpilePackages` and `optimizePackageImports` and `sideEffects` is set to `false`. While above helps in some other cases we noticed that this setup does not allow `transpilePackages` to work. 

We also tried moving shared to `web/src` and import directly and that correctly tree shakes the bundle and `bla` is not included inside `_app` so there must be some issue with `transpilePackages` (from our understanding). 

Looking forward to getting more eyes on this. 

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.0.0: Tue Sep 24 23:39:07 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.12.2
  npm: 10.5.0
  Yarn: 1.22.18
  pnpm: 9.0.4
Relevant Packages:
  next: 14.2.15 // Latest available version is detected (14.2.15).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: N/A
Next.js Config:
  output: N/A
```


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

create-next-app, Pages Router, Performance

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

next build (local), Vercel (Deployed)

### Additional context

I did not test this on 15.x since it is next canary but don't expect it to change since 15.x is focused on new react features.
Repository: PowerToys
Issue: [Peek] Add user-configurable support for previewing plaintext files
Labels: Needs-Triage

### Description of the new feature / enhancement

Note: this is based on a prior discussion on #34824 .

Peek discriminates supported files based on their file extension, and currently supports previewing a variety of plain text files, including source code files, .txt and so on.

However, this is currently a hard-coded list and cannot be edited or overridden by the user. Attempting to preview an unsupported file results in the summary information being displayed, not its contents.

This new feature would add support for previewing plaintext files, either by auto-detecting them at the time of preview (if we can find a reliable method), and/or by giving the user the ability to edit a list of text file extensions via Settings.

This would not replace the current method of editing the Monaco JSON file to add new languages or adding extensions to existing languages. It is proposed that if the same file extension were present in both the Monaco supported list and the user's setting, that the Monaco setting would take precedence; this is because the Monaco could also include support for syntax highlighting and other formatting improvements over a simple text-only preview.


### Scenario when this would be used?

This would be useful because power users often want to quickly preview plaintext files from a wide variety of both popular and niche applications, and also their own filetypes with custom extensions. It is infeasible for us to support all these by adding them manually for each PowerToys release.

### Supporting information

Requests for supporting new plaintext files are relatively common in the issues forum, e.g.:

#35515 - support .ion files
#34483 - support .ahk files
#33811 - support .csv files without the Office extension
etc.

The previous attempt at integrating this functionality also received supportive comments, so I believe there is demand.
Repository: godot
Issue: Minor issue: Debugger gives a poor error message for wrongly indented _: on match statements
Labels: enhancement,discussion,topic:gdscript,topic:editor,usability

### Tested versions

v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.19045 - GLES3 (Compatibility) - AMD Radeon RX 6600 (Advanced Micro Devices, Inc.; 31.0.24033.1003) - Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 Threads)

### Issue description

On a match statement, if the catch all ```_:``` is mis-aligned, eg
```
	match variable:
		"Something":
			pass
	_:
		pass
```

The debugger gives the error
```Expected statement, found "_" instead.```
It took me a while to work out what I'd done wrong because the original match statement was off screen.
I think the error message would be clearer if the error were something like
```Expected statement, found "_:" instead. Check indent.```
(note this says ```"_:"``` instead of just ```"_"```)

### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: angular
Issue: `readonly` input signals are not highlighted by the language service
Labels: area: language-service

### Which @angular/* package(s) are the source of the bug?

language-service

### Is this a regression?

No

### Description

The Angular language service doesn't highlight `readonly` signal inputs as inputs. It also doesn't do this for decorator `@Inputs` but making those `readonly` doesn't make a lot of sense anyway.

Example code:
```ts
import { Component, Input, input } from '@angular/core';
import { bootstrapApplication } from '@angular/platform-browser';

@Component({
  selector: 'app-signal-test',
  standalone: true,
  template: '',
})
export class SignalTestComponent {
  public readonly readonlySignalInput = input<number>();
  public regularSignalInput = input<number>();

  @Input()
  public readonly readonlyDecoratorInput: number | undefined;
  @Input()
  public regularDecoratorInput: number | undefined;
}

@Component({
  selector: 'app-root',
  standalone: true,
  imports: [SignalTestComponent],
  template: `<app-signal-test
    [readonlySignalInput]="123"
    [regularSignalInput]="123"
    [readonlyDecoratorInput]="123"
    [regularDecoratorInput]="123"
  />`,
})
export class PlaygroundComponent {}

bootstrapApplication(PlaygroundComponent);
```

Result when holding ctrl and hovering the readonly signal input in vscode:
![Image](https://github.com/user-attachments/assets/126a6eed-b6b7-443f-a61a-d098c6493f96)


Compared to the regular signal input:
![Image](https://github.com/user-attachments/assets/c21f53d9-86aa-49df-a491-1fad3bfce20e)


`readonly` signal inputs also do not find any usage of them when clicking "Find All References".

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)
```
Angular CLI: 18.2.9
Node: 20.14.0
Package Manager: npm 10.7.0
OS: linux x64

Angular: 18.2.8
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1802.9
@angular-devkit/build-angular   18.2.9
@angular-devkit/core            18.2.9
@angular-devkit/schematics      18.2.9
@angular/cdk                    18.2.9
@angular/cli                    18.2.9
@schematics/angular             18.2.9
rxjs                            7.8.1
typescript                      5.4.5
zone.js                         0.14.10
```

### Anything else?

_No response_
Repository: pytorch
Issue: CUDA Binary dependency chain is wrong, leading to bad binary packaging
Labels: module: binaries,module: cuda,triaged

tl;dr: the version of FindCUDAToolkit that we use [here](https://github.com/pytorch/pytorch/blob/8f3efb8797b7a2dbd958bf625374985793ed5035/cmake/Modules/FindCUDAToolkit.cmake) is old enough that we are missing quite a few cuda lib from it and the dependency between cuda libs is not accurate.
Loosely related, our script that updates the RPATH (the relative path used to find .so this depends on) within our .so to always look for the cuda installed within the pip package being shipped is broken and does not contain the appropriate entries for the newly added nvjitlink library.

This is the root cause of several user issues like https://github.com/pytorch/pytorch/issues/134929 and https://github.com/pytorch/pytorch/issues/131312 as far as I can tell.
And I can also observe it locally, where running `ldd` on the libtorch_cuda.so that is shipped with the PyTorch 2.5 binary on PyPi, I get entries ilke:
```
    libcurand.so.10 => /usr/local/cuda/lib64/libcurand.so.10
    libcublas.so.12 => /home/albandes/local/pytorch/3.10_release_binary_env/lib/python3.10/site-packages/torch/lib/../../nvidia/cublas/lib/libcublas.so.12
 ```
This mismatched libraries being picked up lead to arbitrary issues. The most common is when the installed binary for cuda 12.4 is installed with a global install <12.4. nvjitlink has been added as a dependency for libcusparse but not to our RPATH. Leading to the newer libcusparse being loaded with the global (old) nvjitlink.


How to fix this?

The most important fix and checks are:
- Fix the binary wheel script we use to generate binaries to properly add libnvjitlink to the appropriate RPATH. Making sure we load it from the installed python package and not from somewhere else.
- Add appropriate CI/Smoke test that ensures: each nvidia-* dependency we have has an appropriate RPATH entry in the appropriate .so (as checked with `readelf`).
- (BE) Add a global CUDA install to our smoke test machines. Use `ldd` on the generated .so to ensure each library is loaded from the right place. We could even make the global cuda install a fixed old version to reflect a lot of user setups.
- (BE) Clean up our RPATH script to only populate it on the relevant binaries. As of today all our .so that I tested have the full rpath, even things like _C.so which is the base cpython module with nothing else in it.
- (might be needed for 1?) Upgrade FindCUDATookit.cmake now that we use cmake>3.18, we should be able to use the latest from cmake.

cc @seemethere @malfet @osalpekar @atalman @ptrblck @msaroufim
Repository: vscode
Issue: gif/video support in chat
Labels: feature-request,panel-chat

It will be great when we have image support in core. It would be nice to also have gif/video support. For example, a dev could attach a gif to the release notes and generate alt text for it, or a user could attach a screen recording and ask for debugging help.
Repository: deno
Issue: ci: use setup-deno@v2
Labels: good first issue,build

Replace all instances of [`setup-deno@v1`](https://github.com/search?q=repo%3Adenoland%2Fdeno%20setup-deno%40v1&type=code) with `setup-deno@v2` and make sure the scripts work with Deno 2 (they mostly should).
Repository: PowerToys
Issue: 无界鼠标同步声音
Labels: Needs-Triage

### Description of the new feature / enhancement

希望无界鼠标能支持同步声音选项

### Scenario when this would be used?

方便一个音频设备使用不同的pc

### Supporting information

_No response_
Repository: flutter
Issue: Consider removing bot_update step in orchestrator when there is no work to do
Labels: team-release

In this build (https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20mac_clangd/2928/overview), it looks like there are no global tests or generators, so the bot_update step seems like it shouldn't be needed.
Repository: ollama
Issue: llama3.1 llama3.2 Chat Template Typo
Labels: bug

### What is the issue?

It seems there is a typo in the following sentence of the chat template:
"When you receive a tool call response, use the output to format an answer to the **orginal** user question."

llama3.1:  [948af2743fc7](https://ollama.com/library/llama3.1/blobs/948af2743fc7)
llama3.2:  [966de95ca8a6](https://ollama.com/library/llama3.2/blobs/966de95ca8a6)

The word "original" is misspelled as "orginal".
Although LLMs typically maps the meaning of typos to normal phrases, there are unknown effects in the actual results of all generation possibilities.

Interestingly, the typo appears to have originated from the official example of llama3.1 model card and has been widely used across many web resources.
https://www.llama.com/docs/model-cards-and-prompt-formats/llama3_1/

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: TypeScript
Issue: Can extends [any, any] but not generic which is exactly [any, any] (woks till 5.3.3 breaks from 5.4.5)
Labels: Bug

### 🔎 Search Terms

generic, tuple extends

### 🕗 Version & Regression Information

This code works in the playground with typescript version 5.3.3 but breaks since version 5.4.5 (version between are not available in the playground)

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.6.3#code/C4TwDgpgBAIghsOUC8UDacBcUCMAaKAI2wCYCA6SgY2wGY0BdBgWACg3RIoAVCAZ2DdwEHAB5uUCAA9gEAHYATPlDhyQjAHwoobKHp6SZ8pekrkAlnIBmEAE5QASodmLlGNQVUgGFSl8YMUAD8jlDYchAAbnYcwlCyAjjavAJCkGLwiBpsAPQ5+gB6QWyxXCmCwiTizsbK-j5QALJwfADWNa4qaoza7iCeagxaqLr6EtIuJmhmljb2ThO1TS2tvuT1gSFO4VExrJzQCcAkyfwVkFWZcNmseYVBQA

### 💻 Code

```ts
type Data = [a: 1, b: 2, ...c: 3[]]

type TestType1<T extends any[]> = 
    T extends [...infer R extends [any, any], ...any[]] ? R : never
type test1 = TestType1<Data>
//   ^?

type TestType2<T extends any[], Mask extends any[] = [any, any]> = 
    T extends [...infer R extends Mask, ...any[]] ? R : never
type test2 = TestType2<Data>
//   ^?
```


### 🙁 Actual behavior

When passing the `Mask ` as a generic and trying to extends the tuple with it to extract the relevant part, the resulting tuple is well formed, but item types are replaced with `any`

### 🙂 Expected behavior

Expect that constraint on infer to works wether as an explicit form or a generic holding a type with the exact same form, which used to be the case priori to typescript 5.4 bu breaks since

### Additional information about the issue

_No response_
Repository: go
Issue: net: TestDialerLocalAddr failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "net" && test == "TestDialerLocalAddr"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8733506969795613409)):

    === RUN   TestDialerLocalAddr
        dial_test.go:628: tcp [::]:0->127.0.0.1: got dial tcp [::]:0->127.0.0.1:65180: connect: connection timed out; want <nil>
    --- FAIL: TestDialerLocalAddr (75.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: neovim
Issue: image API
Labels: enhancement,api,provider,lua



# Problem

No API to load images as bytes and disiplay them using e.g. kitty image protocol.

# Expected behavior

- `vim.ui.img` (is `vim.ui` the right place for this? or `vim.os`, or ...?)
    - Could shell out to `imagemagick` CLI. For reference, https://github.com/3rd/image.nvim uses FFI but that seems unnecessary.
    - `show`
    - `load`

# Related

- https://github.com/neovim/neovim/issues/24164
- https://github.com/neovim/neovim/issues/27119
Repository: react
Issue: Bug: multiple useTransition hook in a page turn to activate first one
Labels: Status: Unconfirmed,Resolution: Stale

<!--
  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: 18.0.0

## Steps To Reproduce
As below codesandbox link
1. Click StartTransition2 button
2. see console show 'isPending true; isPending false'

<!--
  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: https://codesandbox.io/p/sandbox/usetransition-issue-68tfls?file=/src/App.js

<!--
  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
1. Click StartTransition2 button
2. see console show 'isPending true; isPending false'


## The expected behavior
1. Click StartTransition2 button
2. see console show 'isPending2 true; isPending2 false'


## Note
Actually, I'm not really sure it's a bug or mine misunderstanding.
While hook is executed in function component by order (e.g. useState), each state hook memorize its own value, useTransition hook not do this in same way. I found it in another project, and simplify to codesandbox. The reason why I use two because I have two section in viewport relying on two sources (API) with different responding speed. I intend to let first response data show immediately and the other keep loading status by useTransition.
Repository: TypeScript
Issue: Formatting Intellisense For Better JS/TS Doc Integration
Labels: Suggestion,Experience Enhancement

<!-- ⚠️⚠️ 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. -->

Does anyone know if it is possible to modify VSCode Intellisense for JSDoc and TSDoc tags? I have always been bothered by the way VSCode handles certain JS/TS doc tags and I just cannot handle it anymore.

As trivial as it might sound, when documenting custom `interface` and `type` definitions, I just want the `@property` tag to be formatted in the same manner as the `@param` tag. The following screen shots illustrate my issue:

![Image](https://github.com/user-attachments/assets/bdfe1c57-2ebe-4d78-8ee9-da190f5da179)

_Notice the emdash `—` between the `@property` tags and the keys being described above?_

![Image](https://github.com/user-attachments/assets/6c65a5de-e182-4805-a257-8313ad05c52b)

_See how it's placed after the `@param` tags and the respective keys?_

If this feature cannot be implemented, does anyone know of any extensions that already do this or which files need to be modified to make this change?

Any advice would be much appreciated. Cheers 🍻
Repository: go
Issue: x/net/http2: discrepancies in lost PING handling between Server and Transport
Labels: NeedsFix

### Go version

x/net v0.30.0

### Output of `go env` in your module/workspace:

```shell
Not important.
```


### What did you do?

I configured http2.Server with
 
* ReadIdleTimeout
* PingTimeout
* CountError

and caused PING to be lost.

### What did you see happen?

The newly added support for lost PING in server:

* only logs lost ping in verbose mode while closes the underlying connection - IMO should be logged always
* does not invoke CountError

```go
if sc.pingSent {
    sc.vlogf("timeout waiting for PING response")
    sc.conn.Close()
    return
}
```
https://cs.opensource.google/go/x/net/+/refs/tags/v0.30.0:http2/server.go;l=1047 

vs 

```go
func (cc *ClientConn) closeForLostPing() {
	err := errors.New("http2: client connection lost")
	if f := cc.t.CountError; f != nil {
		f("conn_close_lost_ping")
	}
	cc.closeForError(err)
}
```
https://cs.opensource.google/go/x/net/+/refs/tags/v0.30.0:http2/transport.go;l=1159



### What did you expect to see?

I expect to see 

* `ErrorLog` called with lost ping message
* `CountError` called with `conn_close_lost_ping`
Repository: deno
Issue: Deno LSP ignoring completeFunctionCalls setting
Labels: bug,needs info,lsp

It appears that the Deno Language Server Protocol (LSP) is not respecting the typescript.suggest.completeFunctionCalls and javascript.suggest.completeFunctionCalls settings in the `.vscode/settings.json` file. Despite setting these options to false, the imports are always being completed with the full function call, which is not the desired behavior.

## Steps to Reproduce

1. Open a Deno project in Visual Studio Code.
2. Set the following options in the `.vscode/settings.json` file:
```json
{
  "deno.enable": true,
  "deno.lint": true,
  "editor.formatOnSave": true,
  "deno.codeLens.references": false,
  "deno.codeLens.implementations": false,
  "editor.defaultFormatter": "denoland.vscode-deno",
  "javascript.suggest.completeFunctionCalls": false,
  "typescript.suggest.completeFunctionCalls": false,
  "editor.indentSize": 2,
  "editor.insertSpaces": true,
  "editor.detectIndentation": false,
  "[typescript]": {
    "editor.defaultFormatter": "denoland.vscode-deno"
  },
  "[html]": {
    "editor.defaultFormatter": "denoland.vscode-deno"
  }
}

```
3. Attempt to import a function from a module.
![image](https://github.com/user-attachments/assets/fd909520-8e30-4e6e-800b-502ae0c2baa5)
![image](https://github.com/user-attachments/assets/9c2495dc-1f7d-4932-af6d-434762db614a)
![image](https://github.com/user-attachments/assets/abe90a34-5c04-43ca-9b29-b981778fcc1b)
![image](https://github.com/user-attachments/assets/24c07a8e-2af8-496b-9695-18f5dcc7cab3)


## Expected Behavior

The import should be added without the full function call, respecting the settings specified in the `.vscode/settings.json` file.

## Actual Behavior

The import is always completed with the full function call, ignoring the `typescript.suggest.completeFunctionCalls` and `javascript.suggest.completeFunctionCalls` settings.

## Environment

Deno: 2.0.2
Repository: go
Issue: cmd/cgo/internal/testcarchive: TestCompileWithoutShared failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/cgo/internal/testcarchive" && test == "TestCompileWithoutShared"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8733462684540614305)):

    === RUN   TestCompileWithoutShared
        carchive_test.go:1094: [go build -buildmode=c-archive -gcflags=-shared=false -o libgo2.a ./libgo2]
            # testcarchive/libgo2
            /Users/swarming/.swarming/wocebm_48/ir/x/w/goroot/pkg/tool/darwin_amd64/link: running /Users/swarming/.swarming/wocebm_48/ir/cache/tools/15e204a/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ar failed: exit status 1
            /Users/swarming/.swarming/wocebm_48/ir/cache/tools/15e204a/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: $WORK/b001/exe/a.out.a(000002.o) has no symbols
            /Users/swarming/.swarming/wocebm_48/ir/cache/tools/15e204a/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: $WORK/b001/exe/a.out.a(000003.o) has no symbols
            fatal error: /Users/swarming/.swarming/wocebm_48/ir/cache/tools/15e204a/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: can't write to output file (Device error)
            /Users/swarming/.swarming/wocebm_48/ir/cache/tools/15e204a/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ar: internal ranlib command failed
            
        carchive_test.go:1096: exit status 1
    --- FAIL: TestCompileWithoutShared (4.55s)


— [watchflakes](https://go.dev/wiki/Watchflakes)