sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: CuDNN SDPA Issue Tracker
Labels: module: cudnn,module: cuda,triaged,module: sdpa

# Summary 
Keeps track of known issues and the current state of the integration, with the goal to bump order in priority list with higher confidence





```[tasklist]
### Tasks
- [ ] https://github.com/pytorch/pytorch/issues/139298
- [x] Match Query's stride layout https://github.com/pytorch/pytorch/pull/138354
- [x] gradOutput vs Ouput stride mismatch, blocked by cudnn bump: https://github.com/pytorch/pytorch/pull/138354#issuecomment-2488863424
- [ ] Fill Value twiddiling: https://github.com/pytorch/pytorch/pull/140837
- [ ] Debugging PR: https://github.com/pytorch/pytorch/pull/139699
- [ ] Update CuDNN backend to respect enable_gqa https://github.com/pytorch/pytorch/issues/139586
- [ ] Mitigated: https://github.com/pytorch/pytorch/issues/138529 but should see if fixed in new version of cudnn
- [ ] WSL: https://github.com/huggingface/diffusers/issues/9704 | need to fix or guard correctly
```


cc @csarofeen @ptrblck @xwang233 @eqy @msaroufim @mikaylagawarecki
Repository: PowerToys
Issue: Time Picker for Awake - 12H option
Labels: Idea-Enhancement,Needs-Triage,Product-Awake

### Description of the new feature / enhancement

Can we add option for 24H vs 12H option for picking end time of awake expire?

### Scenario when this would be used?

Choosing end time for Awake expire on specific time and date.

### Supporting information

_No response_
Repository: go
Issue: testing: panic in AllocsPerRun during parallel test
Labels: Proposal,Proposal-Accepted

I propose that testing.AllocsPerRun panic if called during a parallel test,
because it cannot give accurate results in that context. Tests that use
the result in that context will be flaky.

For example, flake #70327 was caused by a test that called t.Parallel
and then used AllocsPerRun. The other tests running in parallel
had allocations that were observed by the AllocsPerRun, resulting
in inconsistent results and a flaky failure.

I've implemented this change in [CL 630137](https://go.dev/cl/630137).
Repository: kubernetes
Issue: Migrating cel ext library cost close to the func
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

Current we keep the extension libraries added in Kubernetes located at: https://github.com/kubernetes/kubernetes/tree/master/staging/src/k8s.io/apiserver/pkg/cel/library
All the cost defined for the ext library is defined in https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/cel/library/cost.go which is separately from the definition of func. Future contributors who is not familiar with the ext library would easily missing adding cost while adding new library. It would be great to have cost defined closer to the func. 

### Why is this needed?

Good for code maintenance.

/sig api-machinery
/triage accepted
Repository: godot
Issue: Error when using Move/Duplicate To
Labels: bug,topic:editor,needs testing,crash

### Tested versions

Engine version: Godot Engine v4.4.dev4.official (36e6207bb48fafd43b98a458d0c461ad982b4e68)

### System information

Godot v4.4.dev4 - Pop!_OS 22.04 LTS on X11 - X11 display driver, Multi-window, 2 monitors - Vulkan (Forward+) - dedicated Quadro P1000 (nvidia; 560.35.03) - Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12 threads)

### Issue description

Godot crashes when trying to copy a file to another location using the Move'/Duplicate To option in the FileSystem.

This is the error I get:

```
ERROR: Task '_update_scan_actions' already exists.
   at: add_task (editor/progress_dialog.cpp:173)

================================================================
handle_crash: Program crashed with signal 11
Engine version: Godot Engine v4.4.dev4.official (36e6207bb48fafd43b98a458d0c461ad982b4e68)
Dumping the backtrace. Please include this when reporting the bug to the project developer.
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7c0f70e42520] (??:0)
[2] /usr/local/bin/godot() [0x1588dd0] (??:0)
[3] /usr/local/bin/godot() [0x158b9c3] (??:0)
[4] /usr/local/bin/godot() [0x4215a28] (??:0)
[5] /usr/local/bin/godot() [0x25ec59c] (??:0)
[6] /usr/local/bin/godot() [0x2602c93] (??:0)
[7] /usr/local/bin/godot() [0x2606159] (??:0)
[8] /usr/local/bin/godot() [0x52ee92] (??:0)
[9] /usr/local/bin/godot() [0x184fe53] (??:0)
[10] /usr/local/bin/godot() [0x16677c1] (??:0)
[11] /usr/local/bin/godot() [0x1589215] (??:0)
[12] /usr/local/bin/godot() [0x158bf78] (??:0)
[13] /usr/local/bin/godot() [0x4264c7d] (??:0)
[14] /usr/local/bin/godot() [0x26060fc] (??:0)
[15] /usr/local/bin/godot() [0x52ee92] (??:0)
[16] /usr/local/bin/godot() [0x41c2fa] (??:0)
[17] /lib/x86_64-linux-gnu/libc.so.6(+0x29d90) [0x7c0f70e29d90] (??:0)
[18] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x80) [0x7c0f70e29e40] (??:0)
[19] /usr/local/bin/godot() [0x43af1a] (??:0)
-- END OF BACKTRACE --
================================================================
```

### Steps to reproduce

Right click in one file in the FileSystem section and chose Move/Duplicate To option. Then select another location in the dialog and chose Copy on the options below. Godot crashes completely.

### Minimal reproduction project (MRP)

I'm using an empty 2D project with just a few folders and files, nothing special.
Repository: bitcoin
Issue: Functional tests: `feature_bind_port_discover.py` is failing
Labels: Tests,CI failed

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

The test is failing due to `Discover()` not being able to finding the local addresses "1.1.1.1" and "2.2.2.2".

### Expected behaviour

The test should pass. Addr1 and Addr2 should be found.

### Steps to reproduce

Run the following commands:
```bash
sudo ifconfig lo:0 1.1.1.1/32 up && sudo ifconfig lo:1 2.2.2.2/32 up
./build/test/functional/test_runner.py --ihave1111and2222 feature_bind_port_discover.py
```

### Relevant log output

```bash
andre@acer:~/repos/bitcoin$ build/test/functional/test_runner.py --ihave1111and2222 feature_bind_port_discover.py
Temporary test directory at /tmp/test_runner_₿_🏃_20241120_141406
Remaining jobs: [feature_bind_port_discover.py]
1/1 - feature_bind_port_discover.py failed, Duration: 1 s

stdout:
2024-11-20T17:14:06.192000Z TestFramework (INFO): PRNG seed is: 4142310399432710311
2024-11-20T17:14:06.193000Z TestFramework (INFO): Initializing test directory /tmp/test_runner_₿_🏃_20241120_141406/feature_bind_port_discover_0
2024-11-20T17:14:06.511000Z TestFramework (INFO): Test that if -bind= is not passed then all addresses are added to localaddresses
2024-11-20T17:14:06.512000Z TestFramework (ERROR): Assertion failed
Traceback (most recent call last):
  File "/home/andre/repos/bitcoin/test/functional/test_framework/test_framework.py", line 132, in main
    self.run_test()
  File "/home/andre/repos/bitcoin/build/test/functional/feature_bind_port_discover.py", line 63, in run_test
    assert found_addr1
AssertionError
2024-11-20T17:14:06.563000Z TestFramework (INFO): Stopping nodes
2024-11-20T17:14:06.716000Z TestFramework (WARNING): Not cleaning up dir /tmp/test_runner_₿_🏃_20241120_141406/feature_bind_port_discover_0
2024-11-20T17:14:06.716000Z TestFramework (ERROR): Test failed. Test logging available at /tmp/test_runner_₿_🏃_20241120_141406/feature_bind_port_discover_0/test_framework.log
2024-11-20T17:14:06.716000Z TestFramework (ERROR): 
2024-11-20T17:14:06.716000Z TestFramework (ERROR): Hint: Call /home/andre/repos/bitcoin/test/functional/combine_logs.py '/tmp/test_runner_₿_🏃_20241120_141406/feature_bind_port_discover_0' to consolidate all logs
2024-11-20T17:14:06.716000Z TestFramework (ERROR): 
2024-11-20T17:14:06.716000Z TestFramework (ERROR): If this failure happened unexpectedly or intermittently, please file a bug and provide a link or upload of the combined log.
2024-11-20T17:14:06.716000Z TestFramework (ERROR): https://github.com/bitcoin/bitcoin/issues
2024-11-20T17:14:06.716000Z TestFramework (ERROR): 


stderr:



TEST                          | STATUS    | DURATION

feature_bind_port_discover.py | ✖ Failed  | 1 s

ALL                           | ✖ Failed  | 1 s (accumulated) 
Runtime: 1 s
```

### How did you obtain Bitcoin Core

Compiled from source

### What version of Bitcoin Core are you using?

Bitcoin Core daemon version v28.99.0-22ef95dbe3e4

### Operating system and version

Ubuntu 22.04

### Machine specifications

_No response_
Repository: flutter
Issue: [Android] Consider implementing backwards compatibility for sensitive content protection
Labels: c: new feature,platform-android,engine,P3,team-android,triaged-android

Flutter is currently working to support sensitive context protection on Android (see https://github.com/flutter/flutter/issues/150218) which is based  on the [View#setContentSensitivity](https://developer.android.com/reference/android/view/View#setContentSensitivity(int)) API that is only supported on Android 15+. We should consider implementing some form of backwards compatibility for lower API versions by trying to detect when the screen is being shared by using the [DisplayManager](https://developer.android.com/reference/android/hardware/display/DisplayManager) to detect active `Display`s.

Note that this would also require figuring out how to obscure sensitive content if we are able to detect screen sharing on Android APIs < 15.

See comment on technical limitations section in go/flutter-android-sensitive-content for more context.
Repository: pytorch
Issue: Consider noting the PyTorch version for BC-breaking error messages
Labels: module: bc-breaking,triaged,topic: improvements

I hit the following error message in torch.load https://github.com/pytorch/pytorch/blob/8d708090c0eb306facfd8f85d58c578a8cbbe689/torch/serialization.py#L1338-L1341 while working on enabling a model with torch.compile for user empathy day.

It took me a couple of minutes to parse the error message and to determine if it was my fault, the code's fault, or PyTorch's fault. My conclusion was that this code used to succeed in the past but we have changed it to fail in a recent release (or on main). I would have appreciated an error message to that effect, like:

"In PyTorch 2.x we changed the behavior of torch.load to only load weights. This torch.load failed because it serialized more than just weights. If you're confident that the file is safe to load, then you may pass weights_only=False to torch.load)."

cc @ezyang @gchanan @mikaylagawarecki
Repository: tauri
Issue: [bug] BSOD rarely when exiting the application
Labels: type: bug,status: needs triage

### Describe the bug

Hello
My application causes a BSOD, error code “Video_scheduler_internal_error”, very rarely (about once out of 70 times) when it is exited, either by code, by alt+F4, by reloading the code or by clicking on the exit button
The event observer also gives the indication “The driver detected an internal driver error on \Device\VBoxNetLwf.”

My dependencies are :
serde_json = “1.0
serde = { version = “1.0”, features = [“derive”] }
tokio = { version = “1”, features = [“full”] }
tauri = { version = “1.8.1”, features = [“api-all”] }
reqwest = { version = “0.11”, features = [“json”, “rustls-tls”] }
futures = “0.3”
zip = “2.1.6”

My application is developed on Windows 10, npm and javascript. Version of tauri-cli 2.1.0

Let me know if you need any further information

### Reproduction

Quitting the application gives it a small but real chance of causing a BSOD; it doesn't matter how you quit

### Expected behavior

Application no longer causes BSODs

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 130.0.2849.80
    ✔ MSVC: Visual Studio Community 2022  
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 21.7.1
    - npm: 9.1.2

[-] Packages
    - tauri [RUST]: 1.8.1
    - tauri-build [RUST]: 1.5.5
    - wry [RUST]: 0.24.11
    - tao [RUST]: 0.16.10
    - @tauri-apps/api [NPM]: 1.6.0 (outdated, latest: 2.1.1)
    - @tauri-apps/cli [NPM]: 1.6.3 (outdated, latest: 2.1.0)

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: angular
Issue: Select tag is flickering SSR
Labels: workaround2: non-obvious,area: forms,area: server,P3

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

Don't known / other

### Is this a regression?

Yes

### Description

As you can see on the video, the select tag is flickering compared to input tag, I use SSR

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

https://stackblitz.com/~/github.com/illunix/flickering-issue-angular

### Please provide the exception or error you saw

https://github.com/user-attachments/assets/71172d3c-bb6b-462b-8738-84b3aa88419e

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 19.0.0
Node: 20.16.0
Package Manager: npm 10.9.0
OS: win32 x64
```

### Anything else?

_No response_
Repository: go
Issue: build: build failure on gotip-linux-loong64
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder == "gotip-linux-loong64" && repo == "go" && mode == "build"
```

Issue created automatically to collect these failures.

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

    [W2024-11-21T00:44:36.689641+08:00 1080691 0 json_subtract.go:121] Unknown fields while parsing property namespace "": {"is_google":false,"mode":0}
    2024/11/21 00:44:36 run starting
    2024/11/21 00:44:37 installed tools


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: Quick search does not retain search term when moving to view
Labels: bug,search

Notice the term isn't carried over to the view:

![Image](https://github.com/user-attachments/assets/f9185c18-257f-44b1-b29b-5a85dca47b33)
Repository: vscode
Issue: Provide quick fix for missing copyright statement in CSS files
Labels: feature-request,engineering

TS file:

![Image](https://github.com/user-attachments/assets/2be03b48-cc51-4f23-9ec8-5050c23791f3)


CSS file:

![Image](https://github.com/user-attachments/assets/47b708ef-fa39-47bf-a4a9-1d283640628d)
Repository: next.js
Issue: All imports must resolve in `next.config` when running `next lint`.  This prevents monorepos from linting before building dependent packages.
Labels: bug,Linting

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/damp-sea-q85m6v

### To Reproduce

`npm run lint`


### Current vs. Expected behavior

`Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in /project/sandbox/node_modules/some-package/package.json imported from /project/sandbox/next.config.mjs`

It should be possible to lint a project _without_ a package being used as a plugin in the next config being built.  In monorepo pipelines it's common to lint prior to building all dependent packages.

Running `eslint` independently in a monorepo does not complain when a package referenced by a `file:` resolution in `package.json` points to non-existent files; this is a run-time not a lint-time concern.


### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.0.4-canary.20 // Latest available version is detected (15.0.4-canary.20).
  eslint-config-next: N/A
  react: 19.0.0-rc-380f5d67-20241113
  react-dom: 19.0.0-rc-380f5d67-20241113
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Developer Experience, Linting

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

next dev (local)

### Additional context

_No response_
Repository: flutter
Issue: Deprecate and remove Dart-side `DeferredComponents`
Labels: team,platform-android,c: API break,c: proposal,P2,c: tech-debt,fyi-android,fyi-tool

Flutter supports two sets of features around deferring code: (a) deferring chunks of Dart and (b) deferring the engine. The latter (b) is used, including in google3, to, quote _"not pay 5mb when a 1000 screen app adds their first 1 Flutter screen"_. The former feature, however, is not known to have any internal use, and we suspect very little (or no) external use.

Feature overview:

- https://github.com/flutter/flutter/wiki/Deferred-Components
- https://docs.flutter.dev/perf/deferred-components

From talking to @jonahwilliams and in my own experiences spelunking through the `flutter` tool, deferred components is a complex feature that is almost not tested at all, and has implementation elements throughout most of the product - in the tool, framework, and engine. Deprecating and removing it would remove a significant source of [haunted graveyard](https://www.usenix.org/sites/default/files/conference/protected-files/srecon17americas_slides_reese.pdf)-style complexity, especially if the feature is not used or tested.

As a first step, I'll work with @andrewkolos to enable Google analytics tracking for this feature.
Repository: PowerToys
Issue: Screen Ruler Crashing
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Screen ruler

### Steps to reproduce

STEP 1:
- Go down to the Windows10 taskbar and click on the PowerToys icon.
- Click on Screen Ruler from the quick access menu.
OR
- Use the default Win + Shift + m

STEPs 2-4:
- This itself doesn't always bring up the tool, but when it does press the Vertical Spacing button.
- If it hasn't frozen yet, click anywhere on your screen.
- Without fail it will freeze and become unresponsive requiring killing the process,

### ✔️ Expected Behavior

For the tool to open every time I press the icon from the taskbar or use the keyboard shortcut and for the tool not to crash.

### ❌ Actual Behavior

The tool inconsistently opens using any regular method of opening it and always crashes when it does manage to open within a very short amount of time (seemingly after one action and then clicking off).

### Other Software

[PowerToysReport_2024-11-20-12-25-12.zip](https://github.com/user-attachments/files/17835262/PowerToysReport_2024-11-20-12-25-12.zip)
Repository: kubernetes
Issue: fix device manager permafailing test
Labels: priority/important-soon,sig/node,kind/failing-test,triage/accepted

### Which jobs are failing?

https://testgrid.k8s.io/sig-node-presubmits#pr-node-kubelet-serial-containerd-flaky

### Which tests are failing?

E2eNode Suite: [It] [sig-node] Device Plugin [NodeFeature:DevicePlugin] [Serial] DevicePlugin [Serial] [Disruptive] Keeps device plugin assignments across node reboots (no pod restart, no device plugin re-registration) [Flaky]

### Since when has it been failing?

Oct 30 2024, likely before https://github.com/kubernetes/kubernetes/issues/128114

### Testgrid link

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/directory/pull-kubernetes-node-kubelet-containerd-flaky/1851562955540271104

### Reason for failure (if possible)

need to review the test purpose and update or remove it, with a rationale

### Anything else we need to know?

followup of https://github.com/kubernetes/kubernetes/issues/128443
put issue on me to make sure we followup and we review the tests

### Relevant SIG(s)

/sig
Repository: next.js
Issue: Inconsistent behaviour of revalidatePath between local and Vercel
Labels: bug,Middleware,Internationalization (i18n),Runtime

### Link to the code that reproduces this issue

https://github.com/damianfrizzi/next-revalidate-bug

### To Reproduce

- Go to [https://next-revalidate-bug.vercel.app](https://t.co/BBukGxf9iY) and note the number at the top
- Navigate to "Go to some page" and note the number at the top
- Go back to homepage and click "Invalidate German" and refresh page
- Number correctly changes on the homepage
- BUT number also changes on the "/somePage" route. This shouldn't happen

### Current vs. Expected behavior

`revalidatePath` behaves correctly when using `bun build && bun start` on my local machine. I.e., invalidating the homepage doesn't invalidate any other (sub) pages. 

When deployed to Vercel, invalidating the homepage also invalidates other (sub) pages.

### 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.17.0
  npm: 10.8.2
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


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

Internationalization (i18n), Middleware, Runtime

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

Vercel (Deployed)

### Additional context

I'm using `trailingSlash: true` in my next.config. I suspect that there is an error in connection with this configuration.
Repository: vscode
Issue: Feature Request: Expose findWidget Actions State via API
Labels: feature-request,api

The VS Code Find Widget allows toggling control options like `toggleFindCaseSensitive`, `toggleFindWholeWord`, `toggleFindRegex`. However, there is no way to programmatically query the current state of these options via the extension API (that I'm aware of). This limitation prevents extensions from seamlessly integrating with or enhancing the Find Widget’s functionality.

### Proposed Solution

Expose the current state of the Find Widget toggles (e.g., `findCaseSensitive`, `findWholeWord`, `findRegex`) through the extension API. 

These could be added to the `activeTextEditor` options either nested or directly:

`vscode.window.activeTextEditor.options.findWidget.findCaseSensitive`

An alternative would be to allow toggling to an explicit state:

`vscode.commands.executeCommand("toggleFindCaseSensitive", true)`

### Workarounds / Context

I've thus far not been able to find a way to work around this- I am attempting to write an extension that modifies the cmd+d selection functionality to more closely match Atom/Pulsar in such a way that it determines if you are trying to select a full word (cursor on the word, nothing actively selected) vs partial matches (highlighted/selected text first, THEN cmd+d) but because there is no way to check these settings I am unable to toggle them to the desired state based on context.
Repository: deno
Issue: Upgrade to TypeScript 5.7
Labels: feat,tsc

We're going to push this back a release to Deno 2.2 due to https://devblogs.microsoft.com/typescript/announcing-typescript-5-7-beta/#typedarrays-are-now-generic-over-arraybufferlike in order to find a better migration strategy.