sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: DISABLED test_recompile_on_global_state_change (__main__.MiscTests)
Labels: module: rocm,triaged,module: flaky-tests,skipped

Platforms: rocm

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

Over the past 3 hours, it has been determined flaky in 9 workflow(s) with 18 failures and 9 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_recompile_on_global_state_change`
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/dynamo/test_misc.py", line 7855, in test_recompile_on_global_state_change
    assert read_state() == new_state
AssertionError
```

</details>


Test file path: `dynamo/test_misc.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/dynamo/test_misc.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd @clee2000 @wdvr
Repository: pytorch
Issue: DISABLED test_re_export_preserve_handle (__main__.TestNumericDebugger)
Labels: triaged,module: flaky-tests,module: macos,skipped

Platforms: mac, macos

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

Over the past 3 hours, it has been determined flaky in 5 workflow(s) with 10 failures and 5 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_re_export_preserve_handle`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_quantization.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_quantization.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @clee2000 @wdvr @malfet @albanD
Repository: pytorch
Issue: DISABLED test_compile_forward_clone_cuda_float32 (__main__.TestNestedTensorOpInfoCUDA)
Labels: triaged,module: flaky-tests,module: nestedtensor,skipped,module: unknown

Platforms: linux, slow

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

Over the past 3 hours, it has been determined flaky in 17 workflow(s) with 0 failures and 17 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_compile_forward_clone_cuda_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_nestedtensor.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_nestedtensor.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @clee2000 @wdvr @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ
Repository: pytorch
Issue: DISABLED test_compile_forward_chunk_cuda_float32 (__main__.TestNestedTensorOpInfoCUDA)
Labels: triaged,module: flaky-tests,module: nestedtensor,skipped,module: unknown

Platforms: linux, rocm, slow

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

Over the past 3 hours, it has been determined flaky in 26 workflow(s) with 2 failures and 26 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_compile_forward_chunk_cuda_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_nestedtensor.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_nestedtensor.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @clee2000 @wdvr @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ
Repository: pytorch
Issue: DISABLED test_compile_forward_select_cpu_float32 (__main__.TestNestedTensorOpInfoCPU)
Labels: triaged,module: flaky-tests,module: nestedtensor,skipped,module: unknown

Platforms: asan, linux, mac, macos, win, windows



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

Over the past 3 hours, it has been determined flaky in 8 workflow(s) with 0 failures and 8 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_compile_forward_select_cpu_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_nestedtensor.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_nestedtensor.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @clee2000 @wdvr
Repository: pytorch
Issue: DISABLED test_channel_group_quantization (__main__.TestQuantizePT2EAffineQuantization)
Labels: oncall: quantization,module: flaky-tests,skipped,module: unknown

Platforms: asan, linux, mac, macos

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

Over the past 3 hours, it has been determined flaky in 13 workflow(s) with 26 failures and 13 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_channel_group_quantization`
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 "/Users/ec2-user/runner/_work/pytorch/pytorch/test/quantization/pt2e/test_quantize_pt2e.py", line 2487, in test_channel_group_quantization
    from torch.ao.quantization.pt2e._affine_quantization import (
  File "/Users/ec2-user/runner/_work/_temp/conda_environment_12793413718/lib/python3.9/site-packages/torch/ao/quantization/pt2e/_affine_quantization.py", line 189, in <module>
    register_custom_op = _register_custom_op(quant_lib)
  File "/Users/ec2-user/runner/_work/_temp/conda_environment_12793413718/lib/python3.9/site-packages/torch/ao/quantization/pt2e/_affine_quantization.py", line 161, in _register_custom_op
    from torch._inductor.decomposition import register_decomposition
  File "/Users/ec2-user/runner/_work/_temp/conda_environment_12793413718/lib/python3.9/site-packages/torch/_inductor/decomposition.py", line 98, in <module>
    decompositions = {**core_aten_decompositions(), **inductor_decompositions}
TypeError: 'CustomDecompTable' object is not a mapping

To execute this test, run the following from the base repo dir:
    python test/quantization/pt2e/test_quantize_pt2e.py TestQuantizePT2EAffineQuantization.test_channel_group_quantization

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

</details>


Test file path: `test_quantization.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_quantization.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @msaroufim @clee2000 @wdvr
Repository: pytorch
Issue: DISABLED test_pt2_traceable_aot_eager_cpu_float8_e4m3fn (__main__.TestFloat8DtypeCPUOnlyCPU)
Labels: oncall: quantization,module: flaky-tests,skipped,module: unknown

Platforms: linux, mac, macos



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

Over the past 3 hours, it has been determined flaky in 24 workflow(s) with 48 failures and 24 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_pt2_traceable_aot_eager_cpu_float8_e4m3fn`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_quantization.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_quantization.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @msaroufim @clee2000 @wdvr
Repository: pytorch
Issue: DISABLED test_compile_forward_chunk_cpu_float32 (__main__.TestNestedTensorOpInfoCPU)
Labels: triaged,module: flaky-tests,module: nestedtensor,skipped,module: unknown

Platforms: asan, linux, mac, macos, win, windows

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

Over the past 3 hours, it has been determined flaky in 58 workflow(s) with 0 failures and 58 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_compile_forward_chunk_cpu_float32`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_nestedtensor.py`

ConnectionTimeoutError: Connect timeout for 5000ms, GET https://raw.githubusercontent.com/pytorch/pytorch/main/test/test_nestedtensor.py -2 (connected: false, keepalive socket: false, socketHandledRequests: 1, socketHandledResponses: 0)
headers: {}

cc @clee2000 @wdvr @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ
Repository: PowerToys
Issue: FanzyZones keeps swapping external monitors
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

I love FancyZones and rely on it daily. Lately I've noticed an issue where FancyZones swaps the layouts on my two external monitors. This swapping happens randomly on boot, resuming from sleep, or when connecting to my dock. This doesn't happen every time, but it's frequent enough that it happens multiple times per week. Unfortunately, this has happened with two different docks and multiple computers.

**Repro steps:**
1. Connect a Surface Dock v2 or Plugable Thunderbolt 4 dock to two 27” Dell UltraSharp monitors (U2717D)
2. Connect a Surface Laptop 5 to the Surface or Plugtable docks or an ASUS ProArt P16 to the Plugable dock
3. Set the PC to output the display to external monitors only
4. Restart the computer, wake it up from sleep, or disconnect/reconnect from the dock

### ✔️ Expected Behavior

FancyZones should remember which layout is on the left and right external displays

### ❌ Actual Behavior

FancyZones usually remembers which layout is on the left and right displays, but sometimes they are randomly swapped so the left layout is on the right monitor and the right layout is on the left monitor. This layout seems to persist across restarts until FancyZones swaps the layouts back. The only solution is to change my FancyZones layouts to be the ones I want.

### Other Software

_No response_
Repository: PowerToys
Issue: Please prevent cmd PATH override
Labels: Needs-Triage

### Description of the new feature / enhancement

When I type `>cmd` I expect it to open the normal `cmd`, with the `PATH` system variable I have meticulously extended myself.      
Instead power toys overrides `PATH`, and that removes some of my custom paths and all paths to disks other than `C:`. 

### Scenario when this would be used?

I have vscode and a bunch of `.code-workspace` files for it. They are spread accross folders so I wrote a small batch script in `C:\Scripts`.       
I have setup `PATH` so when I open `cmd` and type `wsp myproject` it will run the batch file and look for a workspace with that name.      


### Supporting information

I have extended both the system-wide and user-based `PATH`.      
PowerToys overrides `PATH`, try running `echo %PATH%` in a normal command line and in one opened from the app.       
     
P.s. couldn't call it a bug really, maybe it's intentional, but it's certainly unexpected and annoying.
Repository: flutter
Issue: `Container` can lose its child's state
Labels: framework,P2,team-framework,triaged-framework

### Use case

The `Container` widget changes the tree hierarchy when its arguments change. This causes its child will lose its state if it doesn't have a global key.

Example by @justinmc: https://dartpad.dev/?id=bd243d23a7fd661563519c3eebece032

### Proposal

If possible, we should fix `Container` such that updating its configuration doesn't cause its child to lose state.

If not possible, we should update `Container`'s docs to explain this problem and how to use a global key to workaround it.
Repository: vscode
Issue: Filter bar in Log file open in editor
Labels: feature-request,output

I love this filter:
![image](https://github.com/user-attachments/assets/51b59870-55f7-42a2-8c12-5b8caba7cfe4)

Can I also have in the editor itself somewhere?
![image](https://github.com/user-attachments/assets/ce4622a2-1b4c-4a05-80c8-3b5e83e452d6)

Usecase: I want to filter down to only events I care about, but compare an old log file to a new log file.
Repository: pytorch
Issue: Interaction between torch._dynamo.disable and fullgraph=True
Labels: triaged,oncall: pt2,module: dynamo

### 🚀 The feature, motivation and pitch

We're encouraging people to use fullgraph=True to better identify graph breaks. At the same time, we're empowering users to use escape hatches like torch._dynamo.disable. These two work against each other, and the best workaround I can think of is to ask users to stop fullgraping and to use some other tool to inspect their graph breaks e.g. tlparse, graph count, TORCH_LOGS.

We should consider special casing torch._dynamo.disable so that it does not raise errors with fullgraph=True. This could be controlled by a flag, but I think it can be the default enablement experience.

### Alternatives

_No response_

### Additional context

_No response_

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: PowerToys
Issue: FancyZones with Citrix Receivers is not working.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

FancyZones

### Steps to reproduce

I am trying to utilize FancyZones to pin my applications in a 3x3 grid. The applications in question are Citrix environments and they do not snap to the grid nor do they resize. I saw some comments from 2021 and 2022 that suggested this could be fixed using the Citrix Workplace settings to adjust for High DPI scaling, but unfortunately that does not do anything for me. Are there any other suggestions for issues with Citrix? Thanks!

### ✔️ Expected Behavior

Citrix applications to snap to 3x3 grid in the same way that the web browser panes do.

### ❌ Actual Behavior

Citrix panes do not align in the grid where they are positioned, do not resize, and do not stay within their snapped grids (they aren't snapping in at all so I guess that's part of the reason?).

### Other Software

Citrix workspace envrionments (Epic).
Repository: godot
Issue: Script reference is broken when script is moved in FileSystem dock
Labels: bug,topic:editor,regression

### Tested versions

4.4 beta1
Didn't test other versions, but probably a regression.

### System information

W10

### Issue description

When you have a script opened and then you move it to another directory, the script reference in the editor is broken. The internal path does not update, so re-focusing editor causes errors about missing file and trying to save the file will have no effect.

### Steps to reproduce

1. Open a script file in script editor
2. In FileSystem dock, move the file to another directory
3. Open the moved file in external editor
4. In Godot, modify and save the still opened script
5. See in external editor that changes are not saved

Alternatively:
3. Unfocus and focus the editor
4. Error in output

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: Cocoon backfiller could take advantage of idle bots
Labels: team-infra

Noticed while investigating [#161674](https://github.com/flutter/flutter/issues/161674#issuecomment-2594184332): The backfiller only runs one builder for each 'task'. If you look at some of the [bot lists](https://chromium-swarm.appspot.com/botlist?c=id&c=task&c=os&c=status&d=asc&f=pool%3Aluci.flutter.prod&k=pool&s=id); we should be utilizing them more - e.g. right now we have 364 idle.  If I look at some of the bot utilizations, they appear to be <33% walltime.
Repository: PowerToys
Issue: [Settings] ImageResizer new preset does not use correct custom dimensions
Labels: Issue-Bug,Resolution-Fix Committed,Product-Image Resizer

### Microsoft PowerToys version

0.87

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Settings

### Steps to reproduce

1. Open the Settings application and navigate to the ImageResizer page
2. Click the Add new size button
3. Note the dimensions of the new preset

### ✔️ Expected Behavior

The dimensions should match the custom size defaults from the `ImageresizerCustomSize` settings property: 1024 x 640.

(See the `ImageResizerProperties` class.)

### ❌ Actual Behavior

The dimensions repeat the existing Small preset width and height: 854 x 480.

### Other Software

_No response_