sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: [PPR] Dynamic route segment params are double encoded
Labels: bug,Partial Prerendering (PPR)

### Link to the code that reproduces this issue

https://github.com/marmalade-labs/ppr-double-encode

### To Reproduce

1. Navigate to https://ppr-double-encode.vercel.app/hello%20world

(note: this bug _only_ shows when deployed to Vercel, not when running locally).


### Current vs. Expected behavior

I expected `hello%20world` to be displayed but instead we see `hello%2520world`. When running locally or with PPR disabled, it works as expected.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Fri, 04 Oct 2024 21:51:11 +0000
  Available memory (MB): 62093
  Available CPU cores: 16
Binaries:
  Node: 22.9.0
  npm: 10.8.3
  Yarn: 1.22.22
  pnpm: 9.12.1
Relevant Packages:
  next: 15.0.0-canary.181 // Latest available version is detected (15.0.0-canary.181).
  eslint-config-next: N/A
  react: 19.0.0-rc-2d16326d-20240930
  react-dom: 19.0.0-rc-2d16326d-20240930
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Partial Prerendering (PPR)

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

Vercel (Deployed)

### Additional context

@wyattjoh, @ztanner - thought you might find this one interesting !
Repository: rust
Issue: Tracking Issue for gracefully handling broken pipes in the compiler
Labels: E-hard,T-compiler,C-bug,C-tracking-issue

### Context

std `print!` and `println!` by default will panic on a broken pipe if `-Zon-broken-pipe=kill` is not set when building rustc itself and left as default. If such a panic occurs and is not otherwise caught, it will manifest as an ICE. In bootstrap we build rustc with `-Zon-broken-pipe=kill` which terminates rustc to paper over issues like `rustc --print=sysroot | false` ICEing from the I/O panic from a broken pipe, but this is not always the desirabled behavior. As Nora said:

> `rustc --print=target-list | head -n5` should definitely work as expected and print only 5 targets and exit successfully, ICEing or erroring are not acceptable imo
> so kill should still be passed
> and `rustc --print=target-list >/dev/full` emitting an error instead of crashing would be neat too

See https://rust-lang.zulipchat.com/#narrow/stream/131828-t-compiler/topic/Internal.20lint.20for.20raw.20.60print!.60.20and.20.60println!.60.3F for a timeline of how we ended up with the `-Zon-broken-pipe=kill` paper.

### Prior Art

Cargo denies `print{,ln}!` usages via `clippy::print_std{err,out}`:

See:
- https://github.com/rust-lang/cargo/blob/15fbd2f607d4defc87053b8b76bf5038f2483cf4/Cargo.toml#L125-L126
- https://github.com/rust-lang/cargo/blob/15fbd2f607d4defc87053b8b76bf5038f2483cf4/src/doc/contrib/src/implementation/console.md?plain=1#L3-L5

### Steps

- [ ] Survey current usages of `print{,ln}!` macro usages in rustc.
- [ ] Classify desired behavior if we do handle I/O errors if we use some `safe_print{,ln}` alternative instead of panicking like `print{,ln}` (some might want to exit with success, some might want to error, but we probably never want to ICE).
- [ ] Open an MCP to propose migrating `print{,ln}!` macro usages to properly handle errors and adding an internal lint to deny (in CI, but allow locally to still allow printf debugging) raw usages of `print{,ln}!`.
- [ ] Fix existing `print{,ln}!` macro usages to properly handle errors.
- [ ] Drop `-Zon-broken-pipe=kill` when building rustc.
- [ ] Update `tests/run-make/broken-pipe-no-ice/rmake.rs` regression test.
- [ ] Implement the internal lint.
- [ ] Add documentation about `print{,ln}!` macro usages in the dev-guide.
Repository: godot
Issue: OSX - Godot crashing when quitting or reloading project
Labels: bug,platform:macos,topic:editor,crash

### Tested versions

4.3.stable

### System information

Apple M3 Pro - macOS Sequoia 15.0 (24A335)

### Issue description

Hello everyone
I'm having this quite annoying but not critical bug on my dev platform for a while
When quitting or reloading Godot, it crashes with the following errors:

<img width="1112" alt="Capture d’écran 2024-10-09 à 07 14 53" src="https://github.com/user-attachments/assets/e5bcf717-6dc3-4f39-ba92-2997422684bd">
<img width="1112" alt="Capture d’écran 2024-10-09 à 07 15 00" src="https://github.com/user-attachments/assets/63404c5c-d24d-420c-bd11-7c4fd31ffe22">
<img width="1112" alt="Capture d’écran 2024-10-09 à 07 36 31" src="https://github.com/user-attachments/assets/72c9b3e7-63ba-4f12-b393-d6fbf6e926e9">
<img width="1112" alt="Capture d’écran 2024-10-09 à 07 36 36" src="https://github.com/user-attachments/assets/882a70bb-847e-46e6-a0e6-2163e36a1012">


### Steps to reproduce

It's quite difficult to give you steps to reproduce as it may be linked to my project.

### Minimal reproduction project (MRP)

I have a 2 years project going-on :) I'm not able to give you a MRP but I can do some tests or give you system logs if needed
Repository: PowerToys
Issue: Layout switch activate on monitor with active-focus window instead of in-which mouse cursor in multiple monitors setup
Labels: Needs-Triage

### Description of the new feature / enhancement

Please add option to activate layout switch on monitor with active-focus windows instead of in-which mouse cursor in multiple monitors setup.

### Scenario when this would be used?

Users don't have to move mouse to new monitor that they want to activate fast layout switch shortcut.

### Supporting information

Similar to that of launch option, which already integrated.
Repository: opencv
Issue: Support for OpenCL-OpenGL interoperability on Apple
Labels: feature

### Describe the feature and motivation

I would like to have support for cl_APPLE_gl_sharing extension which enables sharing data between OpenCL and OpenGL on apple as well. At the moment only android/egl, windows/wgl, linux/glx are supported (linux/egl support -> #22703).

### Additional context

_No response_
Repository: vscode
Issue: Resolver error: Error: Failed to download VS Code Server (Failed to fetch)
Labels: bug,vscode-website,confirmation-pending,network

<!-- ⚠️⚠️ 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.93.0
- OS Version: windows



![image](https://github.com/user-attachments/assets/46286380-7706-45db-bfde-67546f8c8cba)

```
 090e3.tar.gz.done and vscode-server.tar.gz to exist
[13:50:20.174] Got request to download on client for {"artifact":"cli-alpine-x64","destPath":"/root/.vscode-server/vscode-cli-XXX.tar.gz"}
[13:50:20.175] server download URL: https://update.code.visualstudio.com/commit:XXX/cli-alpine-x64/stable
[13:50:20.175] Downloading VS Code server locally...
[13:50:20.189] > 
> 
[13:50:20.207] Resolver error: Error: Failed to download VS Code Server (Failed to fetch)
```


Steps to Reproduce:

1. download remote explorer on vscode
2. open vscode on windows
3. using remote explorer to ssh linux
4. It show the error

I don't know what happen.
But if it is the network, how to connect the vscode by myself without vsocde process automatically.
Repository: PowerToys
Issue: [Mouse Without Borders] Mouse pointer draw by PowerToys not follow pointer size in system setting 
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

GitHub, PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

1. Change system mouse pointer size to larger size than default `1`
2. Restart system without a physical mouse connected

### ✔️ Expected Behavior

Mouse pointer (cursor) draw by powertoys has right size set by system settings

### ❌ Actual Behavior

Mouse pointer draw by powertoys has size equal to default `1` size.

### Other Software

Windows 11 23H2 + PowerToys 0.85.1 on both connected machines
Repository: pytorch
Issue: vmap specializing on dynamic shapes with index_put_
Labels: triaged,oncall: pt2,module: functorch,module: dynamic shapes

### 🐛 Describe the bug

```python
from torch import Tensor
torch.set_default_device('cuda')

# @torch.compile(dynamic=True)
def _ordered_to_dense(num_blocks_in_row: Tensor, col_indices: Tensor):
    num_rows = col_indices.shape[-2]
    num_cols = col_indices.shape[-1]
    batch_dims = num_blocks_in_row.shape[:-1]
    device = num_blocks_in_row.device

    def create_dense_one(kv_num_blocks, kv_indices):
        dense_mask = kv_indices.new_zeros(num_rows, num_cols + 1, dtype=torch.int32)

        row_indices = torch.arange(num_rows, dtype=torch.int, device=device).unsqueeze(
            -1
        )
        col_range = torch.arange(num_cols, dtype=torch.int, device=device)
        index_mask = col_range < kv_num_blocks.unsqueeze(-1)

        # We write to one spot "out of bounds"
        valid_indices = torch.where(index_mask, kv_indices, num_cols)
        # set the values in 'a' to 1 where the indices are valid
        # torch.ops.aten.index_put_(dense_mask, [row_indices, col_range], dense_mask.new_ones(()), accumulate=False)
        dense_mask[row_indices, valid_indices] = 1
        return dense_mask[:, :num_cols].contiguous()

    create_dense_batched = create_dense_one
    for _ in range(len(batch_dims)):
        create_dense_batched = torch.vmap(create_dense_batched, in_dims=(0, 0))

    out = create_dense_batched(num_blocks_in_row, col_indices)
    return out
_ordered_to_dense = torch.compile(torch.vmap(torch.vmap(_ordered_to_dense)), dynamic=True)

num_blocks = torch.ones(4, 5, 8)
indices = torch.arange(9).expand(4, 5, 8, 9)
out = _ordered_to_dense(num_blocks, indices)
```
Running with `TORCH_LOGS="aot_graphs"` we see that the number 5 shows up (indicating it's specialized)
### Versions

N/A

cc @ezyang @chauhang @penguinwu @zou3519 @samdow @kshitij12345 @bobrenjc93
Repository: excalidraw
Issue: Adding a Line in Mobile/Tablet View Generates Two Control Points even with a single tap.
Labels: bug

When adding a line in mobile view, two control points are generated even with a single tap.


https://github.com/user-attachments/assets/6e714d0a-e7cf-4ff8-b12c-ffccf12b668b
Repository: pytorch
Issue: Implement Incremental PCA with GPU support
Labels: feature,module: cuda,triaged

### 🚀 The feature, motivation and pitch

Feature: Implement Incremental PCA with native GPU support in PyTorch.

Motivation: I'm working on a large-scale machine learning project that requires dimensionality reduction on datasets too large to fit in memory. Currently, PyTorch lacks a native implementation of Incremental PCA, especially one that leverages GPU acceleration. I think this feature would benefit many users as I also found this existing issue about it: #40770 

Pitch:
1. Memory efficiency: Allows processing of datasets larger than available RAM, addressing a common limitation in data analysis.
2. GPU acceleration: Native GPU support would significantly speed up Incremental PCA computations (compared to existing versions such as `sklearn.decomposition.IncrementalPCA`, enabling faster dimensionality reduction and feature extraction on large-scale datasets.
3. PyTorch integration: Seamless integration with PyTorch's ecosystem, allowing easy use with existing PyTorch models and workflows.

### Alternatives

Using scikit-learn's Incremental PCA by moving data to CPU. Very slow.

### Additional context

I submitted an RFC here: [https://github.com/pytorch/rfcs/pull/70](https://github.com/pytorch/rfcs/pull/70)

cc @ptrblck @msaroufim
Repository: godot
Issue: Controller names no longer contain brand / type
Labels: bug,platform:macos,needs testing,topic:input

### Tested versions

Tested in 4.3.stable

### System information

Godot v4.3.stable - macOS 15.0.1 - Vulkan (Mobile) - integrated Apple M3 Max - Apple M3 Max (14 Threads)

### Issue description

I don't know when this started happening – perhaps with a new macOS version – but somehow `print(Input.get_joy_name(device_id))` only returns names like `Controller` and `Wireless Controller` making it impossible for me to determine the type of controller and subsequently show the right icons in my game.

- Xbox One controller returns: `Controller`
- PS4 controller returns: `Wireless Controller`
- Haven't tested PS5 and Nintendo Switch yet.

**Showing the right icons is an important feature for compliance with stores and platforms.** There should be a solid way to at the very least differentiate between controllers from Microsoft, Sony, Nintendo, and generic controllers.

If there is a workaround, please let me know.

### Steps to reproduce

On macOS, connect any controller and print its name using `Input.get_joy_name(device_id)`.

### Minimal reproduction project (MRP)

n/a
Repository: ui
Issue: [feat]: Snackbar
Labels: area: request

### Feature description

Snackbars are designed to have interactions (like an "Undo" button).
Toasts are usually kept simple and meant to be passive (without interaction).

### Affected component/components

Toast

### Additional Context

According to design best practices, Toast should not include interactions, while Snackbars are intended to provide actionable buttons (e.g., "Undo", "Retry"). Please correct me if I am wrong.

PFA : Attachment of a Toast with an action.
<img width="321" alt="toast-with-action" src="https://github.com/user-attachments/assets/a7a34cc4-7daa-419e-acdf-07016cb77643">


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: opencv
Issue: cv::VideoWriter fails writing colorless images
Labels: bug,category: videoio

### System Information

**Ubuntu 22.04**
OpenCV version: 4.5.4
Compiler & compiler version: Clang 15.0.7

**Ubuntu 24.04 LTS**
OpenCV version: 4.6.0
Compiler & compiler version: GCC 13.2

### Detailed description

If an instance of `cv::VideoWriter` is used to write matrices to a file using the colorless format, the resulting video is empty and cannot be opened with any media player. This is not the case if the instance is set to use colored matrices.\
This problem has been tested and confirmed with the following input material:
1. Using artificially created matrices as shown in the example code below.
2. Loading matrices as images from any video using `cv::VideoCapture`
3. Converted ROS2 `sensor_msgs::msg::Image` messages.

### Steps to reproduce

CPP File:
```
#include <opencv2/videoio.hpp>

#include <iostream>

int main()
{
    cv::Mat mat(480, 640, CV_8UC3, cv::Scalar::all(0));
    mat.setTo(cv::Scalar(255, 0, 0));
    // Setting the last parameter to true will write a blue mat
    auto videoWriter = cv::VideoWriter("../result.mp4", cv::VideoWriter::fourcc('m', 'p', '4', 'v'), 30, mat.size(), false);

    auto frameCount = 1;
    // Write a 3-second-video
    while (frameCount <= 90) {
        std::cout << "Encoding frame " << frameCount << " of 90..." << std::endl;
        videoWriter.write(mat);

        frameCount++;
    }

    return 0;
}
```

CMakeLists.txt:
```
cmake_minimum_required(VERSION 3.8)

set(CMAKE_CXX_STANDARD 17)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

project(CVTest LANGUAGES CXX)

find_package(OpenCV REQUIRED)

add_executable(CVTest
    ${CMAKE_CURRENT_LIST_DIR}/main.cpp
)

target_link_libraries(CVTest
    PRIVATE ${OpenCV_LIBS}
)
```

To build:
1. Copy the code into a `main.cpp` and `CMakeLists.txt`, respectively.
2. `mkdir build && cd build`
3. `cmake ..`
4. `make`
5. Start the application with `./CVTest` and check the resulting video.

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [x] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: PowerToys
Issue: Frequent AMD GPU Driver Crashes Affecting PowerToys Functionality
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.85.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

PowerToys Run, FancyZones, FancyZones Editor

### Steps to reproduce

Dear Developers,

I've recently switched to an AMD GPU and have been experiencing frequent driver crashes. When the crash occurs, the screen goes black for 1-2 seconds, after which almost all software recovers except for certain PowerToys functionalities, specifically PowerToys Run and FancyZones. I haven't paid much attention to other components.

PowerToys Display Issue: Post-crash, FancyZones only shows a shaded area without any content, and PowerToys Run displays an empty candidate list.

Affected Versions: This issue affects both the latest version (0.85.1) and all previous versions that I have used.

Hypothesis: AMD GPU driver crashes typically generate a Windows event with ID 4101. One approach could be to monitor this event and re-render PowerToys when it is triggered.

Reproduction Steps: Due to the random nature of the driver crashes, I am unable to provide precise steps to reproduce the issue.

I hope this information helps in diagnosing and resolving the bug. Thank you for your assistance!

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: tensorflow
Issue: tf.nn.conv2d terminates process with invalid input shape instead of raising an exception
Labels: stat:awaiting tensorflower,type:bug,comp:ops,2.17

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

2.17.0

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 22.04.3 LTS

### Mobile device

_No response_

### Python version

3.11.9

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

TensorFlow terminates the process when passing an invalid input shape to `tf.nn.conv2d`. Instead of raising a Python exception that can be caught with a try-except block.

I expected TensorFlow to raise a catchable Python exception indicating that the input tensor shape is invalid. This would allow the error to be handled in a try-except block, instead of terminating the process. The error message should clearly explain the shape mismatch issue.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

# Define invalid input tensor and kernel
input_tensor = [[1.0, 2.0, 3.0]]
kernel = [[0.5, 0.5], [0.5, 0.5]]

try:
    # Create TensorFlow constants
    input_tf = tf.constant(input_tensor, dtype=tf.float32)
    kernel_tf = tf.constant(kernel, dtype=tf.float32)
    
    # Attempt to perform convolution, expecting an error
    output_tf = tf.nn.conv2d(
        tf.expand_dims(input_tf, axis=0), 
        tf.expand_dims(kernel_tf, axis=0), 
        strides=[1, 1, 1, 1], 
        padding='VALID'
    )
    
    print("TensorFlow Output:", output_tf.numpy())
except Exception as e:
    print("TensorFlow Error:", e)
```


### Relevant log output

```shell
2024-10-09 14:53:31.118589: F ./tensorflow/core/util/tensor_format.h:427] Check failed: index >= 0 && index < num_total_dims Invalid index from the dimension: 3, 0, C Aborted (core dumped)
```
Repository: tauri
Issue: [bug] maximized window config causes black flash on launch
Labels: type: bug,platform: Windows

### Describe the bug

I have encountered an issue with the `maximized` window setting where this causes a black flash on application launch.

It only happens sometimes and the black flash is always on the right hand part of the screen:

Here is a screen recording:

https://github.com/user-attachments/assets/1cf93837-8791-482c-a719-f59068f91bd1

### Reproduction

Here is a repo with the default tauri-vue app which has just one setting changed:
in `tauri.conf.json` I added `"maximized": true`

https://github.com/mr-zwets/tauri-test

If reproduction is not possible on the first try, re-open the app multiple times again, as the bug only happens part of the time.

### Expected behavior

I expect the  maximized window not to cause a black flash

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22631 x86_64 (X64)
    ✔ WebView2: 129.0.2792.79
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
    ✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.18.0
    - yarn: 1.22.22
    - npm: 10.8.2

[-] Packages
    - tauri 🦀: 2.0.2
    - tauri-build 🦀: 2.0.1
    - wry 🦀: 0.44.1
    - tao 🦀: 0.30.3
    - @tauri-apps/api : 2.0.2
    - @tauri-apps/cli : 2.0.2

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.1
    - @tauri-apps/plugin-shell : 2.0.0

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist/spa
    - devUrl: http://localhost:9000/
    - framework: Vue.js (Quasar)
    - bundler: Vite
```


### Stack trace

```text
/
```


### Additional context

_No response_
Repository: pytorch
Issue: [feature request] Provide FlexAttention as a new available/selectable backend for SDPA
Labels: triaged,enhancement,module: sdpa

### 🚀 The feature, motivation and pitch

Originally discussed here with @drisspg :
- https://github.com/pytorch/pytorch/pull/137526#issuecomment-2401115408

This would be good for exercising FlexAttention in existing SDPA workloads for perf testing.

Also wondering if FlexAttention could then be extended to work natively/fused with some quantized dtypes from torchao @msaroufim - to do fused quant/dequant or even quant-native computation (e.g. in int8) - supporting quantized dtypes would be a useful extension for existing SDPA api

Ideally, FlexAttention can also support `attn_bias=` argument of SDPA and hopefully outperform the existing math/mem_efficient backends (flash does not support attn_bias for now AFAIK)

### Alternatives

_No response_

### Additional context

_No response_

cc @jbschlosser @bhosmer @cpuhrsch @erichan1 @drisspg @mikaylagawarecki