sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: DISABLED test_non_contiguous_input_mm_plus_mm (__main__.TestMaxAutotune)
Labels: triaged,module: flaky-tests,skipped,oncall: pt2,module: inductor

Platforms: linux, slow

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

Over the past 3 hours, it has been determined flaky in 7 workflow(s) with 21 failures and 7 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_non_contiguous_input_mm_plus_mm`
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/workspace/test/inductor/test_max_autotune.py", line 720, in test_non_contiguous_input_mm_plus_mm
    self.assertTrue(torch.allclose(ref, act, atol=4 * 1e-3, rtol=4 * 1e-3))
  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_CUDA_MEM_LEAK_CHECK=1 PYTORCH_TEST_WITH_SLOW_GRADCHECK=1 python test/inductor/test_max_autotune.py -k TestMaxAutotune.test_non_contiguous_input_mm_plus_mm

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

</details>


Test file path: `inductor/test_max_autotune.py`

cc @clee2000 @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: node
Issue: `fs.watch` doesn't listen changes of file containing JSON stringified if changes happen too quickly (behavior different with non JSON)
Labels: fs

### Version

v20.11.0

### Platform

23.2.0 Darwin

### Subsystem

node:fs

### What steps will reproduce the bug?

```Javascript
const fs = require('fs');
const path = require('path');

const filePath = path.join(__dirname, 'test.json');
// Create the file if it doesn't exist
if (!fs.existsSync(filePath)) {
    fs.writeFileSync(filePath, "{ }");
}

fs.watch(filePath, (eventType, filename) => {
    console.log(`Event type is: ${eventType}`);
    if (filename) {
        console.log(`Filename provided: ${filename}`);
    } else {
        console.log('Filename not provided');
    }
});

fs.writeFileSync(filePath, "{ \"test\": \"test\", \"test2\": \"test2\" }"); // same with JSON.stringify(...)
// Listener above is called if we replace line above with:
// fs.writeFileSync(filePath, "very ok or not but I need a longer text to test something...");
```

### How often does it reproduce? Is there a required condition?

With the code above it happens all the time. But if you change the content of the file to normal string (not JSON stringified) it seems to happen only few times but I don't know why...

Something to keep in mind is that if we add a delay before updating the file, it will always be detected (JSON stringified or not)

### What is the expected behavior? Why is that the expected behavior?

```
Event type is: change
Filename provided: test.json
```

### What do you see instead?

*Nothing*

### Additional information

I wanted to watch changes on a file storing JSON stringified data but the listener passed in `fs.watch` is not called if the change happen too quickly after the call of `fs.watch`. The strange thing is that if the content is only a text (without JSON format) the watcher emit the event correctly...

I have tested this behavior on different version of node :
- v20.11.0
- v18.17.1
- v16.20.1

Before creating this issue here, I created a help request ( https://github.com/nodejs/node/issues/53111 ) where other members confirmed this strange behavior
Repository: godot
Issue: TAA is very slow on macOS
Labels: bug,platform:macos,topic:rendering,confirmed,topic:3d,performance

### Tested versions

v4.3.dev6.official [89850d553]

### System information

Godot v4.3.dev6 - macOS 14.4.1 - Vulkan (Forward+) - integrated Apple M1 Max - Apple M1 Max (10 Threads)

### Issue description

This is an empty project

TAA off: ~220fps
TAA on: ~53fps



https://github.com/godotengine/godot/assets/60579014/fb9d21af-8e24-4af3-9a6d-6b016a2e8069



### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

New empty project
Repository: PowerToys
Issue: PowerToys fancy zones resets some settings after reboot
Labels: Issue-Bug,FancyZones-Settings,Needs-Team-Response

### Microsoft PowerToys version

v0.81.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Problem Statement:
After restarting the PC, the Fancy Zones configuration for two of the six connected monitors changes unexpectedly. Specifically, the zone settings for Screen 2 always move to Screen 4, while Screen 3 retains its configuration.

Steps to Reproduce:

Connect six monitors to the PC.
Configure Fancy Zones on Screen 2 and Screen 3.
Restart the PC.
Observe the Fancy Zones configuration.
Expected Behavior:

Screen 2 and Screen 3 should retain their Fancy Zones settings after a restart.
Actual Behavior:

Screen 3 retains its Fancy Zones settings.
Screen 2’s Fancy Zones settings move to Screen 4 after a restart.
System Configuration:

Number of monitors: 6
Operating System: [Specify OS version]
Fancy Zones version: [Specify version]
Steps Taken to Troubleshoot:

Verified all monitors are correctly connected.
Checked and updated graphics card drivers.
Reconfigured Fancy Zones settings before restarting.

### ✔️ Expected Behavior

Screen 2 and Screen 3 should retain their Fancy Zones settings after a restart.

### ❌ Actual Behavior

Screen 3 retains its Fancy Zones settings.
Screen 2’s Fancy Zones settings move to Screen 4 after a restart.

### Other Software

Windows 10 Pro
Repository: godot
Issue: Implement MOUSE_MODE_CAPTURED for iOS
Labels: enhancement,platform:ios,topic:porting,topic:input

### Tested versions

v4.2.1.stable.official [b09f793f5]

### System information

iPadOS 17.4, iPad 9th gen

### Issue description

I'm trying to use a bluetooth mouse on my iPad to control an FPS camera. To do this, the mouse should be locked into the center of the screen and hidden. I tried MOUSE_MODE_CAPTURED but it has no affect. It is not implemented.

Keyboard and mouse gaming is possible to do on iPad today. For instance, I can play FPS games through Steam link just fine. See this talk by Apple. It has a mouse locking example at 7:30
https://developer.apple.com/videos/play/wwdc2020/10617


### Steps to reproduce

Minimal script for enabling mouse lock/capture
```gdscript
extends Node

func _ready():
	DisplayServer.mouse_set_mode(DisplayServer.MOUSE_MODE_CAPTURED)
```

### Minimal reproduction project (MRP)

[mouse-capture-MRP.zip](https://github.com/godotengine/godot/files/15404020/mouse-capture-MRP.zip)
Repository: vscode
Issue: "Add selection to next find match" (cmd+d) is selecting also inlay hint
Labels: bug,editor-core,inlay-hints

Repro: 
1. Turn on inlay hints for function parameters in typescript
2. Put cursor on a parameter with inlay hint before it
3. Invoke "add selection to next find match" command (cmd+d or ctrl+d on windows) - :bug:

https://github.com/microsoft/vscode/assets/16353531/d10382a7-d703-40c7-8d95-b23f6179e185




Version: 1.90.0-insider
Commit: 405ce83a24f38fd70751b03438763a1503329fe0
Date: 2024-05-20T23:10:59.594Z
Electron: 29.3.1
ElectronBuildId: 9464424
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Darwin arm64 23.4.0
Repository: PowerToys
Issue: Screen Ruler: red lines are not visible.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.81.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Screen ruler

### Steps to reproduce

When I want to take a measurement, the red lines do not appear and the cursor disappears.

### ✔️ Expected Behavior

Red lines appear when I want to take a measurement.

### ❌ Actual Behavior

When I want to take a measurement, the cursor disappears. It doesn't come back until I press the ESC key.

### Other Software

_No response_
Repository: kubernetes
Issue: ValidatingAdmissionPolicy objects have different runtime type compared to CRDValidationRules
Labels: kind/bug,sig/api-machinery,triage/accepted

### What happened?

Applied CRD:

```yaml
openAPIV3Schema:
        type: object
        properties:
          duration:
            type: string
            format: duration
            "x-kubernetes-validations":
            - rule: "self >= duration(\"60m\")"
              message: "duration must be at least 1 hour"
```

Created policy with following rule:

```yaml
  validations:
    - expression: "object.duration >= duration(\"2h\")"
      message: "duration must be at least 2 hours"
```

Applied instances of CRD:

```yaml
apiVersion: example.com/v1
kind: Thing
metadata:
  name: example-thing
duration: 2h
---
apiVersion: example.com/v1
kind: Thing
metadata:
  name: bad-thing
duration: 5m
```

Correctly received error from CRD rule for `bad-thing`, incorrectly received error for `good-thing` on policy due to missing overload for `>=` operator:

```console
❯ kubectl apply -f ./instance.yaml
Error from server (Invalid): error when creating "./instance.yaml": things.example.com "example-thing" is forbidden: ValidatingAdmissionPolicy 'example-policy.example.com' with binding 'example-binding.example.com' denied request: expression 'object.duration >= duration("2h")' resulted in error: no such overload
Error from server (Invalid): error when creating "./instance.yaml": Thing.example.com "bad-thing" is invalid: duration: Invalid value: "string": duration must be at least 1 hour
```


This is because CRDValidationRules consider the schema when representing the object in CEL, while VAP directly exposes the unstructured serialization. i.e.  a `duration`-format `string` in a CRD is represented in CEL using a CEL `duration`, but in VAP it is represented using a `string`

https://github.com/kubernetes/kubernetes/blob/e1b0bc3d0a7fb89a1e60f4ec1ee34b10de22d00a/staging/src/k8s.io/apiserver/pkg/admission/plugin/cel/filter.go#L158-L174

https://github.com/kubernetes/kubernetes/blob/1453085b44ff96b10ab25b68ce34929829114521/staging/src/k8s.io/apiextensions-apiserver/pkg/apiserver/schema/cel/validation.go#L786-L804

### What did you expect to happen?

VAP expressions and CRD rules to work the same way on the same objects in CEL

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

https://gist.github.com/alexzielenski/db4faa6cb26a6b31dc967fa18dc79199

### Anything else we need to know?

_No response_

### Kubernetes version

1.30

### Cloud provider

N/A

### OS version

Tested using kind 1.30

### Install tools

N/A

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

N/A

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

N/A
Repository: vscode
Issue: In diff mode, user is forced to interact with a dialog instead of direct hitting the revert button
Labels: bug,diff-editor

Type: <b>Bug</b>

When a diff between two files is open, and the second file is empty, while the first file has no new lines, but is not empty, the following three-dot + "Revert Block" button appears:
![image](https://github.com/microsoft/vscode/assets/44567586/8e5800e4-fd05-4734-9005-102ac156c7f3)


The issue is that clicking on the three dots button will only display one option. At that point it's worthless having a three-dot dialog, and instead the usual right arrow should be displayed to avoid having to click twice to achieve the same result.

VS Code version: Code 1.89.1 (dc96b837cf6bb4af9cd736aa3af08cf8279f7685, 2024-05-07T05:13:33.891Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details><summary>Extensions (25)</summary>

Extension|Author (truncated)|Version
---|---|---
ng-template|Ang|17.3.2
dart-code|Dar|3.88.1
flutter|Dar|3.88.0
copilot|Git|1.194.0
copilot-chat|Git|0.15.2
todo-tree|Gru|0.0.226
vscode-drawio|hed|1.6.6
plantuml|jeb|2.18.1
azure-pipelines|ms-|1.228.0
vscode-azureresourcegroups|ms-|0.9.0
vscode-docker|ms-|1.29.1
debugpy|ms-|2024.7.11371017
isort|ms-|2023.10.1
python|ms-|2024.6.0
vscode-pylance|ms-|2024.5.1
jupyter|ms-|2024.4.0
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.17
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
azure-account|ms-|0.12.0
vsliveshare|ms-|1.0.5918
vscode-yaml|red|1.14.0
markdown-preview-enhanced|shd|0.8.13
vscode-icons|vsc|12.7.0


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
chatpanelc:31048052
dsvsc021:30996838
01bff139:31013167
pythoncenvptcf:31049071
a69g1124:31046351
pythonprt:31047983
dwnewjupyter:31046869
26j00206:31048877

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: Add warning messages to provide info about expected performance improvement using cuda for a specific model
Labels: module: cuda,module: molly-guard,triaged

### 🚀 The feature, motivation and pitch

### Motivation
Since there are certain properties of a neural network that make it beneficial or inconsequential to use a gpu, it would be helpful, for beginners like me, to have a function that gets as input the neural network object (net object) and outputs a message as to how much **value** the gpu is expected to add in training time.

That can be implemented via the command `net = net.to(device)`


### Long story
So, as a beginner in the Machine Learning world, I have started training a certain model. 

After performing all the steps of installing the cuda and cudaNN drivers, it was time to train my network with a gpu, like an adult.

And then.... the performance was the same.

I checked the task manager, my gpu was being utilized at 100%, so I was sure it was working (and vice versa, when I would deactivate it, it would not even show up in the task manager). 

### Alternatives

_No response_

### Additional context

_No response_

cc @ptrblck @msaroufim @jbschlosser @bhosmer @cpuhrsch @erichan1 @drisspg @mikaylagawarecki
Repository: storybook
Issue: [Bug]: ESM presets are not loading in Windows
Labels: bug,presets,windows,sev:S2

### Describe the bug

If you publish an addon with a preset written in ESM, it's not being loaded on Windows.
E.g. we published https://www.npmjs.com/package/@web/storybook-framework-web-components as ESM

Tested on Windows 10 and 11.
(It works on macOS though, tested on Sonoma 14.4.1, so seems to be a Windows specific bug)

![image](https://github.com/storybookjs/storybook/assets/137844/7d8313b0-f513-4025-a2fa-2d37aaa7d7d4)


### Reproduction link

https://github.com/thepassle/sb-windows-repro

### Reproduction steps

git clone https://github.com/thepassle/sb-windows-repro.git
cd sb-windows-repo
npm i
npm start

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 Intel(R) Xeon(R) CPU E5-2678 v3 @ 2.50GHz
  Binaries:
    Node: 20.12.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers:
    Edge: Chromium (125.0.2535.51)
  npmPackages:
    storybook: ^7.0.0 => 7.6.19
```


### Additional context

Preset file is also `.mjs`, but the Storybook expects package.json `exports` to define it without extension.
Ideally I think the extension should be also part of the public interface, so it's just a file and node should be able to load ".mjs" normally. Right now I think the problem is somewhere in `interopRequireDefault`, not sure why it's only happening on Windows.
Repository: transformers
Issue: Training GPT2 with run_clm.py exceeds the described memory amount .
Labels: Examples,Good Second Issue

### System Info

- `transformers` version: 4.40.0.dev0
- Platform: Linux-6.5.0-28-generic-x86_64-with-glibc2.17
- Python version: 3.8.19
- Huggingface_hub version: 0.22.2
- Safetensors version: 0.4.2
- Accelerate version: 0.29.2
- Accelerate config:    not found
- PyTorch version (GPU?): 1.10.0+cu111 (True)
- Tensorflow version (GPU?): not installed (NA)
- Flax version (CPU?/GPU?/TPU?): not installed (NA)
- Jax version: not installed
- JaxLib version: not installed
- Using GPU in script?: <fill in>
- Using distributed or parallel set-up in script?: <fill in>

### Who can help?

 @ArthurZucker and @younesbelkada

### Information

- [X] The official example scripts
- [ ] My own modified scripts

### Tasks

- [X] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

python run_clm.py \
    --model_name_or_path openai-community/gpt2 \
    --dataset_name wikitext \
    --dataset_config_name wikitext-2-raw-v1 \
    --per_device_train_batch_size 8 \
    --per_device_eval_batch_size 8 \
    --do_train \
    --do_eval \
    --overwrite_output_dir \
    --output_dir /tmp/test-clm

### Expected behavior

The example in the script mentions training with a K80 GPU at a batch size of 8, noting that the K80 has 24GB of memory. However, when I use an RTX 3090 with a batch size set to 4, it consumes 20GB of memory without modifying any settings. Why is this the case?
Repository: deno
Issue: LSP really slow
Labels: perf,lsp

Version: deno 1.43.6+7ab7a14 (canary, x86_64-unknown-linux-gnu)

https://github.com/denoland/deno/assets/54838975/e19b2f91-6e99-410c-938c-e31bbd4affca

seems to happen on vendored project.

[3-Deno Language Server.log](https://github.com/denoland/deno/files/15404836/3-Deno.Language.Server.log)
Repository: storybook
Issue: [Bug]: Bundled CSS imported through preview.ts is wrongly applied to the whole docs page
Labels: bug,has workaround,addon: docs

### Describe the bug

As documented, it is possible to [apply bundled CSS to all the stories](https://storybook.js.org/docs/configure/styling-and-css) by importing it in the preview.ts.

Doing so works fine in stories as the CSS is only applied to the Canvas.
In docs however, the CSS is applied to the whole page generating potential conflicts with the args table

e.g. importing a simple style like this in `preview.ts`
```css
label:has(input[role='switch']) {
	background-color: red;
}
```

Will have the following effect on the docs:
![image](https://github.com/storybookjs/storybook/assets/5543595/770fce22-96cc-498e-b873-aed6fef144e9)


### Reproduction link

https://stackblitz.com/edit/github-aofmqe?file=src%2Fstories%2FButton.stories.js

### Reproduction steps

1. Got to the above link
2. In the Docs of the Button Stories, the "disabled" switch toggle should not be affected by the styles defined in /public/index.css and imported in preview.js

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.1.2 => 8.1.2 
    @storybook/addon-links: ^8.1.2 => 8.1.2 
    @storybook/blocks: ^8.1.2 => 8.1.2 
    @storybook/test: ^8.1.2 => 8.1.2 
    @storybook/web-components: ^8.1.2 => 8.1.2 
    @storybook/web-components-vite: ^8.1.2 => 8.1.2 
    storybook: ^8.1.2 => 8.1.2
```


### Additional context

_No response_
Repository: kubernetes
Issue: `kube-proxy`'s `--healthz-bind-address` should support IPv4 and IPv6 simultaneously (dual stack)
Labels: sig/network,area/kube-proxy,kind/feature,triage/accepted

### What would you like to be added?

>  `--healthz-bind-address` `ipport`     Default: 0.0.0.0:10256
--
  | The IP address and port for the health check server to serve on, defaulting to "0.0.0.0:10256" (if --bind-address is unset or IPv4), or "[::]:10256" (if --bind-address is IPv6). Set empty to disable. This parameter is ignored if a config file is specified by `--config`.

The documentation suggests that the bind address is singular and that it's either of the IPv4 or IPv6 family. I think that's doubtful, `0.0.0.0` and `::` also bind to both families in `kube-apiserver`. Fix the docs (but see *) or fix the implementation.

### Why is this needed?

This artificial limitation makes it unpredictable where the healthz socket listens when running a dual-stack cluster. 
*: It is particularly problematic and not fixable as a docs fix when the user wants to listen on loopback addresses for both  families, since there's no notation for that, unlike 'all addresses' (0.0.0.0 and ::).
Repository: PowerToys
Issue: Keyboard Manager - Salvaging CapsLock (or any key) for Shortcut after Remapping to Disable 
Labels: Needs-Triage

### Description of the new feature / enhancement

Adding the option for key reuse in a Shortcut post Remap. Currently, disabling a key by Remap to Disable then removes that key for use in a shortcut (apparently, the key is simply "killed"). Keeping at least the option to still use that key in a shortcut would allow for much greater flexibility in remapping. The need for this was discovered via attempting to make CapsLock *only* triggerable via a shortcut - please refer to the Scenario provided below.

### Scenario when this would be used?

To suppress entering of the dreaded cAPSLOCK state unintentionally, but still retaining the functionality for when it is occasionally needed, making CapsLock *only* triggerable by pressing the combination of LeftShift+CapsLock. This is just how old typewriters worked, and it was quite an elegant solution.

### Supporting information

I am not sure if this is a bug or an oversight or even an intended behavior, so I am posting here. Apologies if I missed a setting or mapping that allows for the desired behavior - and if so, please advise as to how.