sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: Flex attention support with arbitrary 4d mask for LlamaModel
Labels: Feature request,Flash Attention

### Feature request

It would be nice to combine the benefits of flex attention and 4d masking.

Perhaps the llama model could be a first case, allowing arbitrary 4d masks to be handled via an efficient flex attention path.

### Motivation

Custom attention masking/biasing patterns lead to considerable improvements in flexibility, and are central to state-of-the-art models like AlphaFold and recent multimodal models.

4d attention masking in Transformers already provides the user with the flexibility to define custom biases, however performance is limited by the fact that 4d masking is incompatible with flash attention.

A 4d mask supporting flex attention attention path would retain full flexibility while maintaining performance. As far as I understand, nothing comparable exists in Transformers currently.

### Your contribution

Not very familiar with what this would take.
Repository: PowerToys
Issue: Actually just disable the function to launch Start Menu with Win key
Labels: Needs-Triage

### Description of the new feature / enhancement

This is so crutial that it deserves to be a separate feature!
For whatever reason every OS thinks that having Win/Super/Meta key to launch Start Menu (Apps Menu) is an awesome idea (it is not!).
And even Linux distros usually do not include option to disable this absolutely silly function in keyboard shortscuts settings (you have to find and edit config file by yourself).

### Scenario when this would be used?

When you want to use shortcuts with Win, you often fuck things up!
This is because other modifier keys (Ctrl, Shift, Alt) do nothing by themselves! They are only used for shortcuts!
Let's block the "Win launches Start Menu" function!

### Supporting information

1) Hit Win key
2) Do not open Start Menu (just do nothing!)
3) Still have other standart Win shortcuts working (Win+D, Win+E, Win+R, etc)
Repository: PowerToys
Issue: Key remapping issue with bluetooth headphone play/pause actions
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Remapped a key combination, e.g. CTRL + Tab as Alt+Tab.
Now when I use my Bluetooth headphone to play / pause music on a music player, the key remapping doesn't work anymore.

### ✔️ Expected Behavior

Key mapping should not be affected by the Bluetooth headphone actions.

### ❌ Actual Behavior

Key remapping was not working anymore. Need to lock and unlock the laptop.

### Other Software

_No response_
Repository: vscode
Issue: When doing suggestions for symbols, it would be useful to show the path relative to the workspace
Labels: feature-request,typescript


In this situation, it would be a lot easier to show the path relative to the workspace root instead of the relative path because I often move from file to file and I never really know what folder I'm in. The relative paths don't help me with picking the correct symbol. This could be a setting if not everyone would find it useful.


![Image](https://github.com/user-attachments/assets/435147e4-8ccb-4702-9946-a2b7355baca6)
Repository: PowerToys
Issue: Allow remapping of shifted key independent of base key in Keyboard Manager, or allow shortcuts to be created from remapped keys
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

Keyboard manager currently only allows remapping keys based on base key. Shifted keys can be remapped as a shortcut combo, however this creates issues when attempting to remap a shortcut using a key that is already remaped, especially if remapped to a character on a shifted keyboard layer

For example, if I wish to remap \ to #, my options are to remap the \ key to output the text #, or to remap it to Shift + 3

Both of these options render the shifted character | as impossible to press, as there is no # key on the base layer of a US QWERTY layout,  additionally, if remapped to shift + 3, a shortcut that utilises shift + 3 will override the remapped # key through chaining behaviour. Finally, the new # key cannot be used in shortcuts due to powertoys only recognising the base key \ when pressed, which has now been remapped.

### Scenario when this would be used?

Any scenario where users wish to remap a key and it's shifted key behaviour independently, especially in cases where the remapped key exists on a shifted layer of another key, or doesn't have an existing dedicated key, it is currently impossible to remap a key and use that same remapped key in a shortcut under these circumstances.

For example, Microsoft IME insists on using a US QWERTY layout for Halfwidth Alphaneumeric typing input irrespective of keyboard used, this would allow users to remap number, symbol, and accented keys within the IME to match their usecase without having to switch input languages when done typing in Japanese.

### Supporting information

https://www.google.com/search?q=windows+japanese+ime+using+qwerty+layout+site:www.reddit.com&sca_esv=6590bfce35d1c64e&rlz=1C1ONGR_enGB1080GB1080&sxsrf=ADLYWIJy8lxa7F5aqGHN5JcI7hCI4nFW0w:1727893882955&sa=X&ved=2ahUKEwi9l-moqvCIAxXtY0EAHXdpBUgQrQIoBHoECDUQBQ&biw=1706&bih=838&dpr=1.5

A google search for the issue I described shows it is a persistent issue with Microsoft IME for many foreign keyboard users that they have refused to fix, this modification could allow a user-friendly solution through Powertoys to present itself by allowing for finer key remapping.
Repository: rust
Issue: `target_arch` is wrong in `arm64ec-pc-windows-msvc`
Labels: O-windows,T-compiler,C-bug,O-AArch64

Rust's `target_arch` cfg is generally very generic, and does not include e.g. the sub-architecture.

For example, the `arm64e-apple-darwin` has `target_arch = "aarch64"`. This is also true of all the ARM targets, these all have `target_arch = "arm"` even though the full target name is much longer.

`arm64ec-pc-windows-msvc` is the only target that differs here, and sets `target_arch = "arm64ec"`. I am not familiar with the specifics of ARM64EC, but I think it should probably set `target_arch = "aarch64"` too? Or, if it _really_ needs to be different, `target_arch = "aarch64ec"`, since Rust prefers Aarch64 over ARM64? Or maybe `target_arch = "aarch64"`, but with an extra `target_feature` to allow distinguishing them?

I would've filed a PR to fix it myself, but it's a bit of work since a lot of places in `rustc` check for `target.arch == "arm64ec"`, so I wanted to make sure I was on the right path first.

CC target maintainer @dpaoliello.
@rustbot label O-windows O-AArch64
Repository: PowerToys
Issue: I LOVE NEW+!
Labels: Needs-Triage

### Description of the new feature / enhancement

I'm sure there are planned updates, but let me request...

1. Tokens to be replaced in file and folder names, like date/time, username, parent folder, and similar
2. Tokens like a counter so that if file1 is already there, file2 is created
3. Tokens that work between files so that file2 can named "similar to but different than" file1
4. Loop on a creation so it automatically creates file1, file2, file3, etc. to whatever value (could be great in setting up a multi-project dev environment)

### Scenario when this would be used?

Anytime someone is creating multiple similar files. I can see uses in development environments, game development, graphics and video creation, even publishing.

### Supporting information

It would also be nice to have a menu at the top of the New+ menu that is the current regular New menu. Getting rid of the original is more convenient and provides a one-stop-shop and reduces confusion.
Repository: godot
Issue: MSAA 2x Breaks Proximity Fade on Vulkan
Labels: bug,platform:windows,topic:rendering,topic:thirdparty,topic:3d

### Tested versions

reproduce on 4.3 Stable

### System information

Windows 11 - I3-10105f with RX 6600 Adrenalin 24.9.1

### Issue description

Enabling MSAA 2x Breaks Proximity fade on Vulkan

![image](https://github.com/user-attachments/assets/f9a6b63d-068c-43e1-97bb-f5046f1b0a14)

MSAA above 2x works fine, as well as no MSAA.

Possible AMD Driver Issue.

Observed while testing SMAA S2x which requires MSAA 2x (https://github.com/RGDTAB/Godot-SMAA) but happens without SMAA.

### Steps to reproduce

Enable MSAA 2x with a Proximity Fade Material in view on Vulkan

### Minimal reproduction project (MRP)

[MSAA.zip](https://github.com/user-attachments/files/17235173/MSAA.zip)
Repository: pytorch
Issue: `aot_eager` does not error on mismatching data-types in out tensors.
Labels: triaged,oncall: pt2,module: fakeTensor,module: aotdispatch,module: pt2-dispatcher

### 🐛 Describe the bug

There is an inconsistency when running `torch.aminmax` out variant on eager and inductor. This behavior is also found when using `aot_eager` backend.

```python
def run(op):
    inp = torch.rand(10, 10)
    out1 = torch.empty(10, dtype=torch.float64)
    out2 = torch.empty(10, dtype=torch.float64)
    op(inp, dim=-1, out=(out1, out2))

>>> run(torch.aminmax)
Traceback (most recent call last):
  File "examples/inductor.py", line 26, in <module>
    run(torch.aminmax)
  File "examples/inductor.py", line 24, in run
    op(inp, dim=-1, out=(out1, out2))
RuntimeError: Expected out tensor to have dtype float, but got double instead

>>> run(torch.compile(torch.aminmax))
torch.return_types.aminmax_out(min=..., max=...)
```

### Versions

PyTorch version: 2.5.0a0+git7128504
Is debug build: True
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

cc @ezyang @chauhang @penguinwu @eellison @zou3519 @bdhirsh @yf225
Repository: vscode
Issue: Support for search engines
Labels: feature-request,search

We want to extend clangd-vscode with an AST search engine besides regex and plain text search, unfortunately it looks like, that VSCode does not support to extend the global and lokal search.
It would be very useful, if one could just add a search engine. Currently we have to add a new separate view, but that is unintentional.

Optionally it would be good to also support a pop-up dialog, with the ability to modify specific search options and a larger search field with semantic linting.

<!-- ⚠️⚠️ 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. -->
Repository: PowerToys
Issue: New+ Keyboard Shortcut
Labels: Idea-Enhancement,Needs-Triage,Product-New+

### Description of the new feature / enhancement

A keyboard shortcut, maybe Ctrl+N, that would open the New+ menu.

### Scenario when this would be used?

When making files, it is easier to press a keyboard shortcut than having to browse through the right-click menu. I already use the Ctrl+Shift+N shortcut to make folders, and this shortcut would be very useful.

### Supporting information

_No response_
Repository: tauri
Issue: [feat] Force Bundle Identifier against rust's rules on iOS
Labels: type: feature request

### Describe the problem

I use the bundle ID `ch.2221.billet`. This is an invalid bundle ID on Android, but it is valid on iOS. I use this bundle ID because I've used a different tech stack before that would allow it, and I own the domain 2221.ch. I currently get this error if I try to use it:

```
manaf@Cooper.local:~/Developer/billet.2221.ch (master*) $ pnpm tauri ios build                                                                                                                        130

> billetterie-2221@1.0.0 tauri /Users/manaf/Developer/billet.2221.ch
> tauri "ios" "build"

thread '<unnamed>' panicked at crates/tauri-cli/src/mobile/mod.rs:421:6:
called `Result::unwrap()` on an `Err` value: IdentifierInvalid { identifier: "ch.2221.billet", cause: StartsWithDigit { label: "2221" } }
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
 ELIFECYCLE  Command failed.
[1]    60141 abort      pnpm tauri ios build
```

When I started working with Tauri V2 RC, I simply put `ch.u2221.billet` as the bundle ID, and searched and replaced that with `ch.2221.billet` in `project.pbxproj`. Now, since the latest Tauri V2 stable release, the bundle ID gets replaced by `ch.u2221.billet` at every build. I believe this is due to `synchronize_project_config` being called at every build https://github.com/tauri-apps/tauri/blob/983e7800b643e1d277cae55ea73f392fa99708ae/crates/tauri-cli/src/mobile/ios/build.rs#L205-L214
that sets the bundle identifier each time
https://github.com/tauri-apps/tauri/blob/983e7800b643e1d277cae55ea73f392fa99708ae/crates/tauri-cli/src/mobile/ios/mod.rs#L458-L462

### Describe the solution you'd like

I would like to have an option to force the bundle Identifier, or to prevent synchronizing the pbxproj file at every build / dev.

### Alternatives considered

Downgrade to the release candidate that still worked, or simply just not use Tauri. I cannot change bundle ids, because that means my already published app would have to get republished on the App Store, meaning the people that have it installed right now will have to delete the old one and download the new one from the store.

### Additional context

_No response_
Repository: pytorch
Issue: Automagically lift assertions / shape checks into torch._check
Labels: triaged,oncall: pt2,module: dynamic shapes

A lot of user code looks like the following:
```
if a.shape[0] != 2:
    raise RuntimeError("wrong shape")
```
if a is an unbacked symint, this throws a GuardOnDataDependent. Does it make sense to automagically turn this into a torch._check (and/or runtime assertion?)

cc @ezyang @chauhang @penguinwu @bobrenjc93
Repository: pytorch
Issue: custom_op/triton_op autograd handling leads to off-by-one error message
Labels: module: autograd,triaged,module: custom-operators,oncall: pt2,module: pt2-dispatcher

Original reported by @aakhundov and @embg:

"in the error message [here](https://github.com/pytorch/pytorch/blob/main/torch/csrc/autograd/python_function.cpp#L177-L178) num_forward_inputs and num_outputs seem to be +1 from the reality [we are] seeing 5/4 in the error, where in reality [we] has 4/3). do we include self here? does this look like a bug? thanks!"

The problem is that [this](https://github.com/pytorch/pytorch/blob/4a9225fa1fe006d95fe7318cbbec27532b548683/torch/_library/autograd.py#L111) adds an additional argument to the autograd.Function, which the error message interprets as one additional argument. We should figure out some way to report a nicer error to the user.

cc @ezyang @albanD @gqchen @pearu @nikitaved @soulitzer @Varal7 @xmfan @chauhang @penguinwu @bdhirsh @yf225
Repository: PowerToys
Issue: Incorrect format when pasting the same data multiple times
Labels: Issue-Bug,Resolution-Fix Committed,Status-Reproducible,Product-Advanced Paste

### Microsoft PowerToys version

0.85.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Advanced Paste

### Steps to reproduce

Incorrect format when pasting as JSON the same data multiple times

### ✔️ Expected Behavior

[
  "Incorrect format when pasting the same data multiple times"
]
[
  "Incorrect format when pasting the same data multiple times"
]


### ❌ Actual Behavior

[
  "Incorrect format when pasting the same data multiple times"
]
[
  "[",
  "  \"Incorrect format when pasting the same data multiple times\"",
  "]"
]

### Other Software

_No response_
Repository: pytorch
Issue: Less restrictive guards when using int(log2(sz))
Labels: triaged,oncall: pt2,module: dynamic shapes

### 🚀 The feature, motivation and pitch

```python
import torch
import torch._inductor.utils
from math import log2

def fn(x):
    sz = x.size(0)
    lg = log2(sz)
    i_lg = int(lg)
    return x + i_lg

with torch._inductor.utils.fresh_inductor_cache():
    fn_c = torch.compile(fn, dynamic=True)
    for i in range(8):
        fn_c(torch.randn((17 + i,), device="cuda"))
```

`int(log2(x.size(0)))` will be `4` for all 8 inputs to this function, but it compiles 8 times and each time guards on the specific size of the input.  It would be great if the guard ended up just being `16 <= s0 < 32` instead.

Note: today, the specialization happens in `log2()`, not in `int()`

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @chauhang @penguinwu @bobrenjc93
Repository: flutter
Issue: `impeller_frame` makes debugging gpu usage on ios difficult
Labels: P3,e: impeller,team-engine,triaged-engine

At some point we changed the way we handle frames in impeller on Metal.  This broke the "Graphics Overlay" (it just doesn't show up) and broke the gpu probes inside of xcode when executing an app.  You can sometimes profile with the frame debugger to get a sense but the "impeller_frame" boundary doesn't always show up making it impossible to measure.

xcode's gpu probe is empty
<img width="1400" alt="Screenshot 2024-10-02 at 2 28 40 PM" src="https://github.com/user-attachments/assets/d8e82fa8-ded2-43b6-99b7-546cb848fb86">

`impeller_frame` option not available
<img width="381" alt="Screenshot 2024-10-02 at 2 33 21 PM" src="https://github.com/user-attachments/assets/7806a6a6-aee2-4f94-a5da-05833f9beea0">

seen on: xcode 15.4

My understanding is that this was related to a change in [`displaySyncEnabled`](https://developer.apple.com/documentation/quartzcore/cametallayer/2887087-displaysyncenabled).  I think there is a plist argument to avoid it.

cc @jonahwilliams
Repository: pytorch
Issue: DISABLED test_memory_plots_free_segment_stack (__main__.TestCudaMallocAsync)
Labels: module: rocm,triaged,module: flaky-tests,skipped

Platforms: linux, rocm, slow



This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_memory_plots_free_segment_stack&suite=TestCudaMallocAsync&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/30986672699).

Over the past 3 hours, it has been determined flaky in 49 workflow(s) with 147 failures and 49 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_memory_plots_free_segment_stack`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/pytorch/test/test_cuda.py", line 3569, in test_memory_plots_free_segment_stack
    self.assertTrue(("empty_cache" in ss) == (context == "all"))
  File "/opt/conda/envs/py_3.10/lib/python3.10/unittest/case.py", line 687, in assertTrue
    raise self.failureException(msg)
AssertionError: False is not true

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_WITH_ROCM=1 python test/test_cuda.py TestCudaMallocAsync.test_memory_plots_free_segment_stack

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `test_cuda.py`

ResponseTimeoutError: Response timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_cuda.py -1 (connected: true, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd @clee2000
Repository: godot
Issue: Scaling a Node3D with Physics Interpolation active shows incorrect scale for 1 frame, when using Tween
Labels: topic:core,documentation

### Tested versions

- v4.4.dev.custom_build [4254946de]

### System information

Windows 10 - Vulkan

### Issue description

Using Tween to scale a Node3D when coming from a different visibility state will display the wrong scale for at least 1 frame.
For example: a MeshInstance3D is hidden at the start with a scale of (1,1,1), a tween is used to show the mesh (order doesn't change it) then scale it from (0,0,0) to (1,1,1) - for at least 1 frame it will display the original scale of (1,1,1).

Tween's `set_process_mode` doesn't change the behaviour. Physics Interpolation has to be ON for the bug to occur.

### Steps to reproduce

3D scene with a camera and a MeshInstance3D

```gdscript
extends Node3D

@onready var mesh: MeshInstance3D = $MeshInstance3D

func _ready() -> void:
	mesh.hide()
	
	var new_tween: Tween = create_tween()#.set_process_mode(Tween.TWEEN_PROCESS_PHYSICS) # Bug occurs in both process modes
	new_tween.tween_interval(1.0) # Let scene be visible
	# Example 1
	new_tween.tween_callback(mesh.show)
	new_tween.tween_property(mesh, "scale", Vector3.ONE, 2.0).from(Vector3.ZERO)
	# Example 2 (comment 2 lines above and uncomment next line)
	#new_tween.tween_callback(show_and_scale)

# Example 2
func show_and_scale() -> void:
	mesh.show()
	mesh.scale = Vector3.ZERO
	
	var new_tween: Tween = create_tween()
	new_tween.tween_property(mesh, "scale", Vector3.ONE, 2.0) # ".from_current()" also shows bug and ".from(mesh.scale)" also
```

### Minimal reproduction project (MRP)

[interp bug.zip](https://github.com/user-attachments/files/17236345/interp.bug.zip)
I include 2 examples in the MRP, simply comment and uncomment the lines as shown in the script.

Showcase:
<video src="https://github.com/user-attachments/assets/6723f6d1-746a-4398-b239-82956291837b">
Repository: pytorch
Issue: Upgrade AWS lambda functions from version 2.x to 3.x of the AWS SDK for JavaScript
Labels: module: ci,triaged

v2 reached maintenance mode in Sept 2024 and will reach end of life Sept 2025

Context:
https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-javascript-v2/

Specifically, our autoscaler lambdas use are running on v2.x (and other lambdas may be using it as well) and need to be updated

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: PowerToys
Issue: Dark bg color in tray
Labels: Needs-Triage,Area-Flyout

### Description of the new feature / enhancement

Dark mode in general settings not working for tray app menu. I suggest improving this to work similarly to Phone Link app.

### Scenario when this would be used?

Launch tray app menu when dark mode is enable.

### Supporting information

_No response_