sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Dragging Scrollbar with long lists freezes the app
Labels: framework,f: material design,f: scrolling,has reproducible steps,P2,team-framework,triaged-framework,found in release: 3.27,found in release: 3.28

### Steps to reproduce

1. Launch app
2. drag scrollbar

### Expected results

app not crash

### Actual results

app crash

### Code sample

<details open><summary>Code sample</summary>

```dart
import 'package:flutter/cupertino.dart';
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      home: Scaffold(
        backgroundColor: Colors.white,
        body: CupertinoScrollbar(
          child: ListView.builder(
            itemBuilder: (_, index) {
              return ListTile(
                title: Text('Cell #${index}'),
              );
            },
            itemCount: 100000,
          ),
        ),
      ),
    );
  }
}

```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

Flutter | iOS native:
:-: | :-:
<video src='https://github.com/user-attachments/assets/3bf35513-fba3-4cb1-98c6-166cf67d0082' width=180/> | <video src='https://github.com/user-attachments/assets/3e4ae02a-35e7-4130-b09c-8915978771ca' width=180/> 

</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 stable, 3.24.4, on macOS 15.1.1 24B91 darwin-arm64, locale zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 16.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.2)
[✓] VS Code (version 1.95.3)
[!] Proxy Configuration
    ! NO_PROXY is not set
[✓] Connected device (7 available)
    ! Error: Browsing on the local area network for Johnny 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)
    ! Error: Browsing on the local area network for Hynn’s 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)
    ! Error: Browsing on the local area network for BrankoTian. 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: pytorch
Issue: FFT half precision only let CUDA pass the check
Labels: triaged,module: fft,module: PrivateUse1

### 🚀 The feature, motivation and pitch

This check is in `CompositeImplicitAutograd` ops like `fft_fft`. What if my `privateuseone` backend like `_fft_c2c` also support fft half precision?😂
https://github.com/pytorch/pytorch/blob/18785c1af9b428a90e197673f8633ecc32f8873c/aten/src/ATen/native/SpectralOps.cpp#L83-L92

### Alternatives

_No response_

### Additional context

_No response_

cc @mruberry @NmomoN @mengpenghui @fwenguang @cdzhan @1274085042 @PHLens
Repository: material-ui
Issue: [docs] Theme mode switching is infinite when switching fast
Labels: website,enhancement

### Steps to reproduce

Steps:
1. There is no link because it is exist on mui.com documentation pages. But I will provide simple steps to reproduce.
2. PLEASE, BE CAREFUL. This behavior could negatively impact individuals who are sensitive to rapid changes in screen brightness, such as those with photosensitivity or other visual sensitivities. So don't try to reproduce it if you have high sensitivity for that.
3. At first open Dark mode documentation page https://mui.com/material-ui/customization/dark-mode/#toggling-color-mode
4. Then open these 4 tabs in the same browser. 
- https://mui.com/material-ui/customization/css-theme-variables/configuration/
- https://mui.com/material-ui/react-drawer/
- https://mui.com/material-ui/react-app-bar/#app-bar-with-responsive-menu
- https://mui.com/material-ui/customization/breakpoints/
5. On Dark mode page start quickly change light mode to dark and vise versa 
https://mui.com/material-ui/customization/dark-mode/#toggling-color-mode
6. Then stop clicking and see how modes switches by their own without any additional interaction.
7. To stop those infinite mode changing, just close all tabs and leave one of them.


### Current behavior

When more than 4 tabs opened, frequent theme mode changing starts infinite mode changing between all tabs.  

### Expected behavior

When user change theme modes, mode is changes only once user clicked.

### Context

This is crucial to take a look, because such behavior may impact on people feeling which have problems while look at frequently changing screens from dark to light.
I think this is because the tabs synchronize data about the active mode of the theme. Because after closing the tabs, the problem disappears. Apparently, the tabs react to changes from other tabs asynchronously and at the same time send these changes to other tabs. And because of this event, the changes run back and forth

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: theme, mode, flickering, infinite
Repository: godot
Issue: Z coordinate in shaders is not the same across Compatibility and Forward+/Mobile
Labels: topic:rendering,documentation,topic:3d

### Tested versions

Tested and reproducible in Godot 4.3 stable and Godot 4.4 dev6.

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21912.14)

### Issue description

This issue explains the problem https://github.com/tiffany352/godot-starlight/issues/2

To sum it up, the background shader gets rendered on top of a cube object as you can see in this image, notice the little white spots on top of the cube:

![Image](https://github.com/user-attachments/assets/10356f42-882c-4afe-b6b6-376c857f679e)

The problem has been identified with this line:

https://github.com/tiffany352/godot-starlight/blob/bc7a4cc22b53fc42986a6c9c0fe369f86b8f3a9d/addons/starlight/Star.gdshader#L65

The solution is to change the way the background shader handles depth.

For me, this solution works for Compatibility renderer:
```
POSITION.z = -1.0 * projected.w;
```
Godot v4.3.stable - Windows 10.0.19045 - GLES3 (Compatibility) - Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21912.14)



But Forward+/Mobile, I need to do that instead:
```
POSITION.z = 1.0 / projected.w;
```
Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated Radeon RX 580 Series (Advanced Micro Devices, Inc.; 31.0.21912.14)


### Steps to reproduce

Open https://github.com/tiffany352/godot-starlight in Godot 4.3 and move the 3d viewport camera in front of the cube object in the scene, and observe how the background renders on the cube. Switch renderer between Forward+/Mobile and Compatibility.

### Minimal reproduction project (MRP)

https://github.com/tiffany352/godot-starlight
Repository: vscode
Issue: Cell execution time verbosity - Time and Date formatting (internationalization)
Labels: feature-request,notebook-statusbar

<!-- ⚠️⚠️ 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. -->
With release 1.96.0 the - much appreciated! - cell execution time display was greatly extended. However, it defaults to US American time and date display, no matter what the format on the respective workstation/computer is. 

The original Jupyter extension has a format option(defaulting to ISO dates), see https://jupyter-contrib-nbextensions.readthedocs.io/en/latest/nbextensions/execute_time/readme.html

I would like to be able to configure that in VSC, too!
Repository: rust
Issue: `x test` should support --show-output
Labels: E-hard,C-enhancement,T-bootstrap,A-test-infra

we should teach bootstrap to respect `--show-output`, which in normal libtest prints the output at the end:
```
; c t --lib -- --show-output
warning: `[project]` is deprecated in favor of `[package]`
    Finished `test` profile [unoptimized + debuginfo] target(s) in 0.01s
     Running unittests src/lib.rs (/home/jyn/.local/lib/cargo/target/debug/deps/example-d78220620848f9e6)

running 2 tests
test bar ... ok
test foo ... ok

successes:

---- bar stdout ----
jieyouxu

---- foo stdout ----
hi


successes:
    bar
    foo

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
```

right now compiletest only supports `--nocapture`, which doesn't buffer output at all and as a result ends up interleaved with libtest's own progress reporting.

note this is non-trivial because bootstrap reimplements its own formatter for the json output: https://github.com/rust-lang/rust/blob/2a71007bce27ddbf8d9883c99060548ac0d66a0e/src/bootstrap/src/utils/render_tests.rs#L214

_Originally posted by @jyn514 in https://github.com/rust-lang/rust/pull/134111#discussion_r1881984253_
Repository: tensorflow
Issue: error message is inconsistent with documentation in `tf.raw_ops.MaxPoolGradWithArgmax`
Labels: type:docs-bug,stat:awaiting tensorflower,type:bug,comp:ops,TF 2.16

### Issue type

Documentation Bug

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

Yes

### Source

source

### TensorFlow version

tf 2.16.1

### Custom code

Yes

### OS platform and distribution

Ubuntu 20.04

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

According to [Doc tf.raw_ops.MaxPoolGradWithArgmax](https://www.tensorflow.org/api_docs/python/tf/raw_ops/MaxPoolGradWithArgmax), the argument `argmax` can be `int32` or `int64`. However, after actual testing, the parameter `argmax` can only support tensor input of data type `int64`.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

input_tensor = tf.constant(1, shape=[1, 2, 2, 1], dtype=tf.float32)
grad_tensor = tf.constant(1, shape=[1, 1, 1, 1], dtype=tf.float32)
argmax_indices = tf.constant(1, shape=[1, 1, 1, 1], dtype=tf.int32)
ksize = [1, 2, 2, 1]
strides = [1, 1, 1, 1]
padding = "VALID"

output_grad = tf.raw_ops.MaxPoolGradWithArgmax(
    input=input_tensor,
    grad=grad_tensor,
    argmax=argmax_indices,
    ksize=ksize,
    strides=strides,
    padding=padding,
    include_batch_in_index=False
)
```


### Relevant log output

```shell
NotFoundError: Could not find device for node: {{node MaxPoolGradWithArgmax}} = MaxPoolGradWithArgmax[T=DT_FLOAT, Targmax=DT_INT32, include_batch_in_index=false, ksize=[1, 2, 2, 1], padding="VALID", strides=[1, 1, 1, 1]]
All kernels registered for op MaxPoolGradWithArgmax:
  device='CPU'; T in [DT_DOUBLE]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_FLOAT]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_BFLOAT16]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_HALF]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_INT32]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_INT8]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_UINT8]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_INT16]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_UINT16]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_UINT32]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_INT64]; Targmax in [DT_INT64]
  device='CPU'; T in [DT_UINT64]; Targmax in [DT_INT64]
  device='GPU'; T in [DT_DOUBLE]; Targmax in [DT_INT64]
  device='GPU'; T in [DT_FLOAT]; Targmax in [DT_INT64]
  device='GPU'; T in [DT_BFLOAT16]; Targmax in [DT_INT64]
  device='GPU'; T in [DT_HALF]; Targmax in [DT_INT64]
 [Op:MaxPoolGradWithArgmax] name:
```
Repository: kubernetes
Issue: The actual pod call to the readNamespacedPod returned a 404 NotFound error.
Labels: kind/bug,needs-sig,needs-triage

### What happened?

This is the response from the call:
header:{audit-id=[22e1f76c-4364-41d6-a826-16f26b0df14b], cache-control=[no-cache, private], content-length=[228], content-type=[application/json], date=[Thu, 12 Dec 2024 12:53:25 GMT], x-kubernetes-pf-flowschema-uid=[38efc94f-5c70-40e9-8e97-167a23b9942a], x-kubernetes-pf-prioritylevel-uid=[09099773-afa1-4ec2-b873-29bc7bc42106]}, body:{"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods \"iac-pod-xxx\" not found","reason":"NotFound","details":{"name":"iac-pod-xxx","kind":"pods"},"code":404}

### What did you expect to happen?

the pod is existed，but it returned a 404 error

### How can we reproduce it (as minimally and precisely as possible)?

This is an intermittent issue.



### Anything else we need to know?

_No response_

### Kubernetes version

        <dependency>
            <groupId>io.kubernetes</groupId>
            <artifactId>client-java</artifactId>
            <version>16.0.0</version>
        </dependency>

### Cloud provider

alibaba cloud

### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: vscode
Issue: Jupyter Notebook Extention Terminated Unexpectedly
Labels: bug,freeze-slow-crash-leak,notebook

Steps to Reproduce
Install the Jupyter and Python extensions in Visual Studio Code.
Open a Python file or a Jupyter notebook.
Set the Python interpreter to Python 3.9.19 from the Anaconda distribution (~\Anaconda3\python.exe).
Attempt to run Python scripts or interact with the notebook environment.
Expected Behavior
The extensions should activate successfully, and the Python/Jupyter environment should work without errors.
**Actual Behavior**
The extension host terminates unexpectedly three times within five minutes, disrupting the workflow.
The issue persists after:
Clearing workspace storage.
Reinstalling the Jupyter and Python extensions.
Reinstalling Visual Studio Code with default settings.
Verifying the environment variables and paths are properly set to Anaconda Python.
Logs
Below are relevant log entries:
2024-12-12 [INFO] Extension host terminated unexpectedly 3 times
Skipping acquiring lock for c:\Users\TCVOAYDOGMUS\AppData\Roaming\Code\User\workspaceStorage\...
The ms-python.python and ms-toolsai.jupyter extensions are activating but appear to trigger the crashes.
Environment Details
Operating System: Windows 10
VSCode Version: (Enter your VSCode version here, e.g., 1.83.x)
Python Version: 3.9.19 (Anaconda)

2024-12-12 16:20:49.838 [info] Extension host with pid 18820 started
2024-12-12 16:20:49.839 [info] Skipping acquiring lock for c:\Users\TCVOAYDOGMUS\AppData\Roaming\Code\User\workspaceStorage\59ae2d4e61ce96abb074ad15fef99edd.
2024-12-12 16:20:49.839 [info] ExtensionService#_doActivateExtension vscode.github-authentication, startup: false, activationEvent: 'onAuthenticationRequest:github'
2024-12-12 16:20:49.839 [info] ExtensionService#_doActivateExtension vscode.emmet, startup: false, activationEvent: 'onLanguage'
2024-12-12 16:20:49.839 [info] ExtensionService#_doActivateExtension vscode.ipynb, startup: false, activationEvent: 'onNotebookSerializer:jupyter-notebook'
2024-12-12 16:20:49.848 [info] ExtensionService#_doActivateExtension vscode.git-base, startup: true, activationEvent: '*', root cause: vscode.git
2024-12-12 16:20:49.907 [info] ExtensionService#_doActivateExtension vscode.git, startup: true, activationEvent: '*'
2024-12-12 16:20:50.104 [info] ExtensionService#_doActivateExtension vscode.github, startup: true, activationEvent: '*'
2024-12-12 16:20:50.771 [info] ExtensionService#_doActivateExtension ms-toolsai.jupyter, startup: false, activationEvent: 'onNotebook:jupyter-notebook'
2024-12-12 16:20:51.015 [info] ExtensionService#_doActivateExtension ms-toolsai.vscode-jupyter-cell-tags, startup: false, activationEvent: 'onNotebook:jupyter-notebook'
2024-12-12 16:20:51.133 [info] ExtensionService#_doActivateExtension ms-toolsai.vscode-jupyter-slideshow, startup: false, activationEvent: 'onNotebook:jupyter-notebook'

VS Code About;
Version: 1.96.0 (user setup)
Commit: 138f619c86f1199955d53b4166bef66ef252935c
Date: 2024-12-11T02:29:09.626Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.19045
Repository: PowerToys
Issue: [Power toys]: Screen reader announces irrelevant information instead of available options in the Advanced Paste menu.
Labels: Issue-Bug,Resolution-Fix Committed,Priority-1,Area-Accessibility,A11yE+D,A11ySev1,A11yWCAG

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Advanced Paste

### Steps to reproduce

**Test environment: **
OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.1340)
Power toys version: v0.86.0
Screen Reader: Narrator

**Repro Steps**

1. Launch Power Toys and ensure the Advanced Paste feature is enabled.
2. Open any text editor (e.g., Notepad) and copy some text to the clipboard.
3. Press Win + Shift + V to open the Advanced Paste menu.
4. Navigate through the options (e.g., "Paste as plain text," "Paste as markdown") using the arrow keys.
5. Attempt to select the highlighted option by pressing Enter or Space.
6. Test with the corresponding shortcut (e.g., Ctrl+1) for the same option.

**User Experience: **
Screen reader users cannot perceive the available options in the Advanced Paste menu due to irrelevant announcements. Additionally, users relying on the keyboard cannot select highlighted options using Enter or Space, limiting operability and causing frustration.

**Note: **
Screen Reader only announces Button on 'Clipboard History' button.

**Guideline reference: **
https://www.w3.org/WAI/WCAG22/Understanding/name-role-value

### ✔️ Expected Behavior

Screen reader should announce the available options in the Advanced Paste menu, such as "Paste as plain text" or "Paste as markdown," as the user navigates through them. Users should also be able to select a highlighted option by pressing Enter or Space, in addition to using the keyboard shortcuts.

### ❌ Actual Behavior

screen reader fails to announce the available options in the Advanced Paste menu and instead reads the menu as blank. Additionally, pressing Enter or Space does not select the highlighted option. The only way to select an option is by using the corresponding keyboard shortcuts, such as Ctrl+1.

### Other Software

https://github.com/user-attachments/assets/8a20a0bd-2ab9-4b2b-a0fc-f7284974f440

https://github.com/user-attachments/assets/355b01bf-c161-491b-a3a7-0df3609f4b82
Repository: next.js
Issue: Fetch requests aren't revalidated properly
Labels: Performance,Runtime,dynamicIO

### Link to the code that reproduces this issue

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

### To Reproduce

1. Start the app in development mode and load `localhost:3000`
2. The server logs will show `cache skip` for the first fetch request in `/` and `cache-hit` for following three:
```sh
GET / 200 in 2802ms
 │ GET https://api.restful-api.dev/objects 200 in 880ms (cache skip)
 │ │ Cache skipped reason: (cache-control: no-cache (hard refresh))
 │ GET https://api.restful-api.dev/objects 200 in 4ms (cache hit)
 │ GET https://api.restful-api.dev/objects 200 in 0ms (cache hit)
 │ GET https://api.restful-api.dev/objects 200 in 0ms (cache hit)
```
3. Reload the page after waiting several seconds. All fetch requests will now show `cache-hit`.

### Current vs. Expected behavior

The reproduction uses a `getData` function to fetch data from a single URL four times, with the following request options object:
```ts
{
  method: "GET",
  cache:'force-cache',
  next: { revalidate: 1 },
}
```

My understanding is that the first `fetch` request should be a `miss`, or a `cache skip`, and subsequent requests should be a `cache hit` for a single second. In other words, that the cache should be revalidated after one second.

Loading the page for the first time indeed shows this behavior. However, a subsequent load after even several minutes will show a `cache hit` for all requests, including the initial one, meaning that the cache was not revalidated as expected.

As an aside, turning on `dynamicIO` displays the same behavior, just that each request is sent 3 times, so there are 12 `cache hit`s instead of 4.

Another aside, is that my understanding (though I can't find anything about that in the docs) was that calls to `fetch` with the same URL have a request-level cache by default, but that is not the case (navigate to [`/no-cache`](http://localhost:3000/no-cache) and you'll see four `cache skip`s). I could find a way to achieve this, other than using `revalidateTag` inside `after`, which, I don't know, seems wrong and unsafe.

### 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): 65536
  Available CPU cores: 10
Binaries:
  Node: 20.13.1
  npm: 10.5.2
  Yarn: 1.22.19
  pnpm: 9.12.0
Relevant Packages:
  next: 15.1.1-canary.1 // Latest available version is detected (15.1.1-canary.1).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


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

dynamicIO, Performance, Runtime

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

next dev (local), next start (local)

### Additional context

_No response_