sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: `Link` component is buggy when used in app router
Labels: Link (next/link)

### Link to the code that reproduces this issue

https://github.com/mehulmpt/nextjs-app-router-link-bug

### To Reproduce

1. Clone the GitHub repository
2. Run `npm run bugcheck` command in your terminal
3. Visit `http://localhost:3000`



### Current vs. Expected behavior

Current behavior:

The links rightly point to `/link?productid=1` / `/link?productid=2` ... and so on. However, when you click on it, they redirect you to the wrong page!

Expected behavior:

Redirect works properly

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 18.20.4
  npm: 8.19.2
  Yarn: 1.22.19
  pnpm: 8.7.6
Relevant Packages:
  next: 15.1.3 // There is a newer version (15.1.6) available, upgrade recommended! 
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: export
```

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

Navigation

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

Other (Deployed), Vercel (Deployed), next start (local)

### Additional context

I spent 20 minutes debugging this for one of our clients today and finally figured out this is a bug with Next.js itself. The reproduction code above is extremely minimal and does not include anything else other than the required code.

The behavior is very weird, the link shown is correct in the browser preview on the bottom left but the moment it is clicked, it takes you to the wrong page. I am also attaching the video that showcases it:

- In the first half of the video I show you wrong behavior
- In the second half of the video I disable javascript and show you how it should actually work


https://github.com/user-attachments/assets/d64a0fe2-57bf-4d5d-b081-faa5220b7cee
Repository: svelte
Issue: Clarify status of class:directive
Labels: documentation

### Describe the bug

Currently, the [docs on svelte class directive](https://svelte.dev/docs/svelte/class#The-class:-directive) state:

> Unless you’re using an older version of Svelte, consider avoiding `class:`, since the attribute is more powerful and composable.

Upon [requesting the `cli` maintainers to work on a migration script](https://github.com/sveltejs/cli/issues/393), the svelte team member said that perhaps the docs is pushing the new syntax a bit too much and may require clarification.

As I do not have the data or heuristics to know if and when there is noticeable differences in performance or DevEx, it seems best for a maintainer to edit the docs in one or two sentences to clarify the future of class:directives, performance gains/losses, and whether this is opt-in or the new norm.

A starting point could be

> You can opt-in to the more powerful and composable attribute syntax above. There is currently no plan to deprecate the directive syntax.

### Reproduction

N/A

### Logs

```shell

```

### System Info

```shell
N/A
```

### Severity

annoyance
Repository: angular
Issue: Provide better type safety for viewChild (and viewChildren)
Labels: area: core,core: queries

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description

At the moment, it is easy to incorrectly type a `viewChild()` (or `viewChildren()`) signal. For example:

```
readonly myElement = viewChild<HTMLInputElement>('someSelector');
```

Here I am passing a generic argument, HTMLInputElement, but the element may have a different type. Often I forget to wrap the element within an `ElementRef`, as I did here, but I digress. The point is, I often waste time being unsure of what is actually being injected by Angular in the component class.

### Proposed solution

I believe that the easiest solution would be to include some kind of validator function:
```
readonly myElement = viewChild('someSelector', { validator: e => e instanceof HTMLInputElement });
```

Type signature would be as follows:

```
<T>(selector: string, options: { validator: (el: unknown) => el is T }) : Signal<T>;
```

### Alternatives considered

**Alternative 1:**

The current API is not as ergonomic as it could be. Why can't the Angular Language service ensure that `myElement` is of the correct type:
```
readonly myElement: HTMLElement;
```
... and in the template:
```
<input #myElement />    <!-- throw error here (if not of type HTMLElement) -->
```

**Alternative 2:**

I thought about creating an external utility function that wraps the existing functionality but does an additional type check when the signal is invoked. I was unsuccessful. Perhaps you could tell me how to facilitate this.
Repository: tauri
Issue: [breaking] Remove v1Compatible
Labels: type: breaking change

Opening an issue for this because it was planned for v3 but may be pushed back to v4. Ref https://discord.com/channels/616186924390023171/731495028677148753/1332806348664209490

Edit: We should also update the deprecation warnings if we end up pushing it back.
Repository: flutter
Issue: [Text Selection] Cannot select consecutive emojis when starting from one, and selection may stop unexpectedly with emojis.
Labels: in triage

### Steps to reproduce

To reproduce the issue, please use the sample code from [this GitHub comment](https://github.com/flutter/flutter/issues/162197#issuecomment-2613746878), alongside the flow demonstrated in the attached videos. Tested on iphone 13pro iOS 17.4.1.
The issue occurs when the user types a few emojis and then starts selecting from one of the emojis. The selection tool quits unexpectedly, preventing the user from dragging to select multiple emojis.

https://github.com/user-attachments/assets/f8000041-5fa8-4624-adbc-e88e31ddc48c


Similar issue occur when user select an initial text placed after emojis and move handler to the left, the selection quits.

https://github.com/user-attachments/assets/8b30d033-c7ae-4e71-8ae9-83c184c561bf



### Expected results

User should be able to select a single emoji or more emoji starting the selection from one emoji or text after emojis.

### Actual results

User cannot select emojis when starting the selection from one emoji and selection quits unexpectedly with emojis if user start selection on text and emojis get selected, especially from right to left side.

### Code sample

<details open><summary>Code sample</summary>

```dart
The code from this issue can be used for testing. 
https://github.com/flutter/flutter/issues/162197#issuecomment-2613746878
```

</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
[!] Flutter (Channel [user-branch], 3.24.5, on macOS 14.2.1 23C71 darwin-arm64, locale en-IT)
    ! Flutter version 3.24.5 on channel [user-branch] at /Users/delfme/Development/flutter
      Currently on an unknown channel. Run `flutter channel` to switch to an official channel.
      If that doesn't fix the issue, reinstall Flutter by following instructions at https://flutter.dev/setup.
    ! Upstream repository unknown source is not a standard remote.
      Set environment variable "FLUTTER_GIT_URL" to unknown source to dismiss this error.
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] Connected device (4 available)
    ! Error: Browsing on the local area network for iPhone. 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
```

</details>
Repository: godot
Issue: StyleBox inconsistencies - referred to as both "style_box" and "stylebox"
Labels: discussion,topic:gui,topic:codestyle

### Tested versions

All

### System information

N/A

### Issue description

To start I'll show this single line:
```cpp
draw_style_box(get_theme_stylebox(SN_STYLEBOX_PLUS), plus_rect);
```

Here you can see in `draw_style_box` the StyleBox is referred to as `style_box` while in `get_theme_stylebox` it is `stylebox`, missing an underscore.

In some places, variables that use StyleBox call it `style_box` while others call it `stylebox`. The class StyleBox has Box uppercase, so I think `style_box` makes more sense.
This isn't a major issue, this is just a thing I noticed that could be adjusted later for consistency. (or rename & deprecate functions or something)

![Image](https://github.com/user-attachments/assets/af15a74b-db29-4ae1-aee1-349a21021ae9)

![Image](https://github.com/user-attachments/assets/b4b21842-d117-41f1-b0b5-ce35c7f6e100)

### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: rust
Issue: Suggest `{to,from}_ne_bytes` when people use transmute between arrays and integers
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn bytes_at_home_1(a: [u8; 4]) -> u32 {
    unsafe { std::mem::transmute(a) }
}

fn bytes_at_home_2(x: u32) -> [u8; 4] {
    unsafe { std::mem::transmute(x) }
}
```

### Current output

```Shell
(no warnings)
```

### Desired output

```text
Warning: use the safe alternative instead
|
|    unsafe { std::mem::transmute(a) }
|             ^^^^^^^^^^^^^^^^^^^ This can be done with `u32::from_ne_bytes(a)` instead
|
hint: there's also `from_le_bytes` and `from_ne_bytes` if you expect a particular byte order

Warning: use the safe alternative instead
|
|    unsafe { std::mem::transmute(x) }
|             ^^^^^^^^^^^^^^^^^^^ This can be done with `x.to_ne_bytes()` instead
|
hint: there's also `to_le_bytes` and `to_ne_bytes` if you expect a particular byte order
```

### Rationale and extra context

I see people doing this a bunch, like it just came up [in Discord](https://discord.com/channels/273534239310479360/592856094527848449/1332818871920492594).

It would be nice to point them to the safe alternative when possible.

### Other cases

```Rust

```

### Rust Version

```Shell
Playground nightly ⬇
```

### Anything else?

<https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=a89dfdaa49736b9d106b2099ca48ddd7>

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"bend-n"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: vscode
Issue: Co pilote pro
Labels: info-needed,*english-please,translation-required-french


Type: <b>Bug</b>

Bonjour ,
J'utilise co-pilote pro , et j'ai le message comme quoi j'ai atteint le maximum de message et qu'il faut que j'upgrade pour co-pilote pro , sauf que je l'ai deja je comprend pas trop

VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26100
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-12700H (20 x 2688)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.64GB (4.98GB free)|
|Process Argv|C:\\Users\\jorda\\Desktop\\Serveur GTA\\Radiance V\\resources\\[dev2]\\radiance_permis --crash-reporter-id fe697b13-1dd6-4730-9124-2b66f3333435|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (26)</summary>

Extension|Author (truncated)|Version
---|---|---
nodejs-bundle|1Yi|1.0.0
svelte-bundle|1Yi|1.0.0
svelte-intellisense|ard|0.7.1
dart-code|Dar|3.102.0
flutter|Dar|3.102.0
fivem-lua|dha|1.0.1
vscode-html-css|ecm|2.0.13
fivem-esx-snippets|eth|1.5.0
fivem-vscode|fiv|0.3.3
vscode-svelte-snippets|fiv|0.5.0
copilot|Git|1.259.0
copilot-chat|Git|0.23.2
svg|joc|1.5.4
vscode-language-pack-fr|MS-|1.96.2024121109
debugpy|ms-|2024.14.0
python|ms-|2024.22.2
vscode-pylance|ms-|2024.12.1
cfxlua-vscode|ove|1.7.32
roo-cline|Roo|3.3.1
vs-code-prettier-eslint|rve|6.0.0
claude-dev|sao|3.2.5
html5-boilerplate|sid|1.1.1
vscode-standard|sta|2.1.3
lua|sum|3.13.5
svelte-vscode|sve|109.5.2
vscode-surround|yat|1.5.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
vscaac:30438847
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
9064b325:31222308
copilot_t_ci:31222730

```

</details>

<!-- generated by issue reporter -->
Repository: vscode
Issue: The `cwd` cannot be resolved in a multi folder workspace. Solution: "cwd" : "${Workspacefolder.name}"
Labels: info-needed

<!-- ⚠️⚠️ 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.4
- OS Version: Windows 10

Steps to Reproduce:

1. idk i just started using vscode
2. 

![Image](https://github.com/user-attachments/assets/827ad899-58a7-495a-a362-5cf3ff9ff45a)
Repository: PowerToys
Issue: Window Centering Helper
Labels: Needs-Triage

### Description of the new feature / enhancement

There is a Window Centering Helper program, add its PowerToys functionality.

### Scenario when this would be used?

There is a Window Centering Helper program, add its PowerToys functionality.

### Supporting information

_No response_
Repository: pytorch
Issue: [Inductor-CPU] `add` is not being fused with templated int8 WoQ GEMM while running LLaMA2
Labels: oncall: cpu inductor

### 🐛 Describe the bug

When max-autotune is enabled with Inductor-CPU, and when int8 WoQ GEMM is used with auto-tuning enabled, `add` isn't being fused with it.

So, there's an opportunity cost. i.e. For LLaMA, for BF16 dtype, with BF16 templated GEMM, we are even able to fuse `add` & RMSNorm's decomposed ops as epilogues.
But the same doesn't happen when the activation is BF16 & the weights are quantized to int8.

This issue is not reproducible with a simple UT, so will have to check the precise scenario in LLaMA2 to ascertain why the intended fusions are not happening.

cc @leslie-fang-intel @Guobing-Chen @chunyuan-w @jianan-gu 

### Versions

Current main branch
Repository: terminal
Issue: Allow opening cmd.exe as service user such as SYSTEM or LOCALSERVICE
Labels: Issue-Feature,Needs-Triage,Needs-Tag-Fix

### Description of the new feature

currently I use `psexec -i -s cmd` or `pxexec -i -u "nt authority\localservice" cmd` to open a cmd  as servcie account. But it opens a new cmd window and it will not have some of the customizations availble to the terminal. Such as For example `Ctrl+shift+F` to search.

### Proposed technical implementation details

_No response_
Repository: go
Issue: cmd/compile: unnecessary bounds check when indexing slice from range
Labels: NeedsInvestigation,compiler/runtime,BugReport

### Go version

go1.23

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

```shell
GOARCH=amd64
GOOS=linux
```

### What did you do?

Compile the following:
```go
package main

import "archive/tar"

var src []tar.Header
var dst *tar.Header

func main() {
	for i := range src {
		dst = &src[i] // line 10
	}
}
```

### What did you see happen?

I see this compiled out:
```
...
0x0069 00105 (main.go:10)	PCDATA	$1, $0
0x0069 00105 (main.go:10)	CALL	runtime.panicIndex(SB)
0x006e 00110 (main.go:10)	XCHGL	AX, AX
...
```

### What did you expect to see?

No such call to `runtime.panicIndex`. The slice is indexed from an iteration integer that is provably bounded by the length of `src` itself. The only possible way a panic occurs is if `src` is mutated during the iteration (or asynchronously in another goroutine, in which case there must be synchronization primitives).
Repository: node
Issue: `path.win32.isAbsolute` considers relative paths absolute
Labels: path

### Version

22.11.0

### Platform

```text
Linux pc 6.8.0-48-generic #48-Ubuntu SMP PREEMPT_DYNAMIC Fri Sep 27 14:04:52 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```

### Subsystem

_No response_

### What steps will reproduce the bug?

```
require('path').win32.isAbsolute('\\foo') === true
```

### How often does it reproduce? Is there a required condition?

Yes. No.

### What is the expected behavior? Why is that the expected behavior?

Here's a behavior of `cd` on `Windows`:

```
C:\Users\user> cd \Windows
C:\Windows>
```

`\Windows` is relative to drive name.

Expected output for `isAbsolute()` is false.

### What do you see instead?

`isAbsolute()` is true.

### Additional information

_No response_
Repository: pytorch
Issue: AMD MI300A Unified Memory Support
Labels: module: rocm

### 🚀 The feature, motivation and pitch

I am working on improving performance for LLM workloads on AMD Instinct™ MI300A Accelerator. This APU is equipped with a fully unified-memory architecture not taken advantage by PyTorch at this time. Because both the GPU and CPU share the same physical memory, memcpy ops become redundant and can limit the size of the model we can train. Adding support for unified memory on ROCm for that particular APU  would allow for zero-copy operations.

The motivation is similar that of #140787, but for ROCm instead of MPS.

Given that this APU is targeted for the most demanding HPC ML workloads, there is a great interest in optimizing the performance of PyTorch for it. Notably, El Capitan, the top1 Supercomputer from [top500](https://top500.org/) runs exclusively with AMD's MI300A.

### Alternatives

_No response_

### Additional context

To facilitate understanding I provide more details as to the kind of changes this involves.

To understand the differences in operations between non-unified and unified memory, let us consider a regular matrix multiplication of matrices $A$ and $B$ where the result is stored in matrix $C$. 

In a non-unified setup with a discrete GPU (device):

1. `malloc` matrices $A,B,C$ on the host each of size $n \times n$.
2. ... values are written on matrices $A$,$B$
3. `CudaMalloc` to allocate memory for matrices $A',B',C'$ 
4. `CudaMemcpy` $A \rightarrow A'$, and $B \rightarrow B'$ (`hostToDevice`)
5. Kernel launch (results are written in $C'$).
6. `CudaMemcpy` $C' \rightarrow C$ (`DeviceToHost`) to get back the results

Whereas with unified-memory you would have:

1. `CudaMallocManaged` matrices $A,B,C$ on the host each of size $n \times n$.
2. ... values are written on matrices $A$,$B$
5. Kernel launch (results are written in $C$).


On machines with discrete GPUs the concept of unified-memory is purely virtual and still results in memory movement by way of page faults and page migrations. This adds a lot of overhead.

On architectures where CPU and GPU share the same physical memory such as the MAC, AMD MI300A, any memcpy operation becomes pointless and wastes space and time.


The quickest and dirtiest *hack* for the support of unified memory on Pytorch is to replace all `cudaMalloc` by `cudaMallocManaged` and to get rid of `memCopy` operations. [Like in this paper](https://doi.org/10.1109/ACSOS-C52956.2021.00029). This however is not ideal, nor portable.


Perhaps a better way to do it would be to toggle on or off the unified memory. Given that this is a relatively new architecture, more hardware is likely to come out with such configuration from different manufacturers and so it would be great to have a device-agnostic support of unified memory.



cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd
Repository: kubernetes
Issue: Inconsistent workloads and the pod ready state
Labels: sig/storage,sig/node,kind/feature,needs-triage

### What would you like to be added?

k8s version is 1.28.1.

The problem handling process is as follows:
1. Use STS to create a pod webswingservice.
2. A CSI plug-in is customized. webswingservice depends on this plug-in.
3. The first startup process is smooth.
4. The node is powered off once after startup.
5. After the system is powered on, the customized CSI fault is not rectified. As a result, volumes fail to be mounted to webswingservice.
6. The webswingservice does not execute the probe because the volume fails to be attached. Therefore, the phase and conditions.Ready in the pod are still in the ready state.
7. In this case, the pod status is not ready, but the workload is not updated. As a result, the inconsistency occurs.
8. The following figure shows the proble
```
[root@master1 ~]# kubectl get po -A | grep webswingservice
webswingservice-0	0/2	Unknown	47h
webswingservice-1	0/2	Unknown	47h
webswingservice-2	0/2	Unknown	47h
[root@master1 ~]#
[root@master1 ~]#
[root@master1 ~]#
[root@master1 ~]# kubectl get sts -n test webswingservice
NAME	ReADY	AGE
webswingservice	3/3	47h
[root@master1 ~]#
```



Code snippet:
1. The probe is executed only when the volume is successfully attached to the SyncPod.
https://github.com/kubernetes/kubernetes/blob/9d9e08b3179aa8df23909b495c2001b8cccf494a/pkg/kubelet/kubelet.go#L1911-L1933


2. The sts checks whether the pod is ready.
https://github.com/kubernetes/kubernetes/blob/9d9e08b3179aa8df23909b495c2001b8cccf494a/pkg/controller/statefulset/stateful_set_utils.go#L461-L464




### Why is this needed?

Is this a problem? Is there any solution?
Repository: vscode
Issue: After New Copilot coding doesn't save!
Labels: info-needed


Type: <b>Bug</b>

After the Copilot update, whenever I finish coding, save my work, and exit VS Code, the changes are not saved in the actual document but are only recorded in the timeline. As a result, I have to restore my work every time I reopen VS Code. Additionally, there are instances where the saved work in the timeline has errors or is documented at random times, with coding sessions being saved prematurely.

This issue means that when I open VS Code, I have to manually restore my work from the last session because the script file itself never ends up saving properly.

VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.26100


<!-- generated by issue reporter -->