sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: autocast() got an unexpected keyword argument 'cache_enabled when use trainer.torch_jit_model_eval
Labels: bug

### System Info

- `transformers` version: 4.46.3
- Platform: Linux-4.18.0-147.el8_1.x86_64-x86_64-with-glibc2.10
- Python version: 3.8.10
- Huggingface_hub version: 0.26.5
- Safetensors version: 0.4.5
- Accelerate version: 1.0.1
- Accelerate config:    not found
- PyTorch version (GPU?): 2.4.1+cu118 (True)
- Tensorflow version (GPU?): not installed (NA)
- Flax version (CPU?/GPU?/TPU?): not installed (NA)
- Jax version: not installed
- JaxLib version: not installed
- Using distributed or parallel set-up in script?: <fill in>
- Using GPU in script?: <fill in>
- GPU type: NVIDIA A100-SXM4-80GB

### Who can help?

@muellerzr 
@SunMarc

### Information

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

### Tasks

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

### Reproduction

When using the `torch_jit_model_eval()` method in trainer, it prompts 

> "failed to use PyTorch jit mode due to: autocast() got an unexpected keyword argument 'cache_enabled'." 

Looking at the details, it was found that the error was caused by the `self.accelerator.autocast(cache_enabled=False)` method. Its method definition is `def autocast(self, autocast_handler: AutocastKwargs = None)`, and there is no `cache_enabled` method.

Is this because the code here has not been updated, or because I ignored some settings?

Is there a solution now?

### Expected behavior

Work normally.
Repository: flutter
Issue: [mobile web]: Flutter freezes while scrolling
Labels: framework,c: performance,f: scrolling,platform-web,browser: chrome-android,team-web

### Steps to reproduce

flutter build web or flutter build web --wasm 
On the web platform release mode, a normal scrolling list will freeze and drop frames when scrolling.


### Expected results

Should scroll smoothly

### Actual results

Scrolling freezes and drops frames

### Code sample

<details open><summary>Code sample</summary>

```dart
class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter ListView Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: ColorfulListView(),
    );
  }
}

class ColorfulListView extends StatelessWidget {
  final List<Color> colors = [
    Colors.red,
    Colors.green,
    Colors.blue,
  ];

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('Colorful List'),
      ),
      body: ListView.builder(
        itemCount: 50,
        itemBuilder: (context, index) {
          final color = colors[index % colors.length];
          return Container(
            color: color,
            padding: EdgeInsets.all(16.0),
            child: Text(
              'Item ${index + 1}',
              style: TextStyle(color: Colors.white, fontSize: 18),
            ),
          );
        },
      ),
    );
  }
}
```

</details>


### Screenshots or Video




### Logs




### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel stable, 3.27.2, on macOS 15.0.1 24A348 darwin-arm64, locale zh-Hans-CN)
    • Flutter version 3.27.2 on channel stable at /Users/bob/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 68415ad1d9 (2 days ago), 2025-01-13 10:22:03 -0800
    • Engine revision e672b006cb
    • Dart version 3.6.1
    • DevTools version 2.40.2
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

```

</details>
Repository: kubernetes
Issue: Recovery after injecting memory overload fault,  pod cannot be scheduled
Labels: kind/bug,sig/storage,needs-triage

### What happened?

Recovery after injecting memory overload fault,  pod cannot be scheduled

### What did you expect to happen?

Recovery after injecting memory overload fault,  pod can be scheduled normal

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

Direct cause:
Two PVCs are bound to the same master node (master3), and pod configuration has anti affinity, making it impossible to schedule to the same node
Process analysis:
1. Injecting memory overload fault, scheduling multiple replicas of deployment in the scheduler: after scheduling the first pod to master3, calling the local CSI interface through volume_manager for 10 minutes without response, continuing to sequentially schedule other replicas;
2. When the scheduler schedules to the second replica pod, as the first pod has not yet completed scheduling on master3, it continues to schedule the second replica pod to master3. After 4 minutes, the local CSI responds, and both volumes are successfully created. At this point, the pod is bound to PVC, causing both PVCs to be bound to master3;



When the scheduler schedules a pod to master3, if there is no response for 10 minutes when calling the local CSI interface through volumn_manager, the timeout scheduling fails. When scheduling other pods to Master3 again, after 4 minutes, LocalCSI responded and successfully bound two volumes to PVC, resulting in two PVCs being bound to Master3. Authsercice has anti affinity configuration and cannot be scheduled to the same node at the same time, causing it to remain pending

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# Version: v1.28.1
```

</details>


### Cloud provider

<details>
na
</details>


### 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: flutter
Issue: windows BSOD(blue screen) when  running `flutter run -d emulator-5554`
Labels: waiting for customer response,in triage

### Steps to reproduce

flutter run -d emulator-5554 
BSOD occur

but when I run this with the "flutter run -d emulator-5554 " with the "--no-enable-impeller " flag

there's no problem i think its the impeller's bug 

### Expected results

BSOD WHEN RUNNING flutter run -d emulator-5554 without the flag "--no-enable-impeller" flag

### Actual results

BSOD

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[Paste your output here]
```

</details>
Repository: pytorch
Issue: Batching rule for aten::_thnn_fused_gru_cell
Labels: triaged,module: functorch

### 🚀 The feature, motivation and pitch

I am currently using `vmap` with GRUCell and got following message:

> There is a performance drop because we have not yet implemented the batching rule for aten::_thnn_fused_gru_cell. Please file us an issue on GitHub so that we can prioritize its implementation. (Triggered internally at ../aten/src/ATen/functorch/BatchedFallback.cpp:81.)

According to the [vmap operator support list](https://docs.google.com/spreadsheets/d/1Sp4HUjxwMifS5oDQg0yvjqk7hKOpCfKO4jWH4MTGP-k/edit#gid=0), the batching rule is indeed not implemented yet. Are there any plans to work on this in the near future or are there any suggestion for a workaround? Would be awesome to have such a batching rule! 

### Alternatives

_No response_

### Additional context

_No response_

cc @zou3519 @Chillee @samdow @kshitij12345
Repository: pytorch
Issue: torch.distributed hangs between Linux (X86) and Mac (M2 Pro)
Labels: oncall: distributed

### 🐛 Describe the bug

I have pared the example code back to the simplest it can be and tried this on both machines. Both ends hang until the timeout.

Linux code:
```
import os
import torch.distributed as dist
from datetime import timedelta

def init_process(rank, world_size):
    os.environ["MASTER_ADDR"] = "192.168.10.104"
    os.environ["MASTER_PORT"] = "23456"
    os.environ["TORCH_DISTRIBUTED_DEBUG"] = "DETAIL"
    os.environ["NCCL_DEBUG"] = "INFO"
    os.environ["GLOO_SOCKET_IFNAME"] = "enp3s0"  # Specify correct network interface

    print(f"Rank {rank}: Setting up process group...")
    try:
        dist.init_process_group(
            backend="gloo",  # or "nccl" if using GPUs
            init_method="tcp://192.168.10.104:23456",
            rank=rank,
            world_size=world_size,
            timeout=timedelta(seconds=120),  # Adjust timeout
        )
        print(f"Rank {rank}: Process group initialized")
    except Exception as e:
        print(f"Rank {rank}: Error during initialization - {e}")
    print(f"Rank {rank}: Reached end of init_process")

if __name__ == "__main__":
    rank = int(os.environ.get("RANK", 0))
    world_size = int(os.environ.get("WORLD_SIZE", 2))
    init_process(rank, world_size)
```

On the Mac:
```
import os
import torch.distributed as dist
from datetime import timedelta

os.environ["MASTER_ADDR"] = "192.168.10.104"  # Linux IPv4 address
os.environ["MASTER_PORT"] = "23456"
os.environ["GLOO_SOCKET_IFNAME"] = "en0"  # Specify correct network interface

print("Rank 0: Setting up process group...")
dist.init_process_group(
    backend="gloo",
    init_method="tcp://192.168.10.104:23456",  # Replace with Linux IPv4
    rank=1,
    world_size=2,
    timeout=timedelta(seconds=60),
)
print("Rank 0: Process group initialized")
```

I have checked network connectivity between the machines and there are no firewall issues on either side.

I have used-up all my Claude.ai & ChatGPT credits investigating ways around and finally decided to raise this as an issue.

Hopefully someone real can help :-)

### Versions

Linux PyTorch version:
`python -c "import torch; print(torch.__version__)"
2.5.1+cpu
`

Mac PyTorch version:
` python -c "import torch; print(torch.__version__)"
2.5.1
`

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: godot
Issue: AnimationTree.advance() on custom thread breaks update of the skeleton.
Labels: discussion,needs testing,topic:animation

### Tested versions

v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated GeForce 920M - Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz (4 Threads)

### Issue description

I've been unhappy with performance of skeletal animations so I moved everything to  animation calculation on a **custom** thread inherited from Godot `Thread`. And is turns out that its not supported, and you'll say "of cause its not". But! You can make it work. You need some tricks. You need to call `advance()` on main thread once to create cache and then it can be updated. Also it need unique instances of `AnimationTreeNode`, sharing animation root is not an option here. 

At first it gave me **4x** time performance boost as well if was not interfering with main thread ( _as oppose to running animation on **SubThread** which slows down main thread. And on **SubThread** it works fine, nothing breaks._ )

So while its running at first ok, after some time **skeleton** that is connected to `AnimationTree` stops updating positions. But transforms are still being calculated, animation still going. As you can see video below, I'm coping (_using simple_ `SkeletonModifier3D`)  transforms from `AnimationTree` skeleton to **another skeleton** and its still being animated.

https://github.com/user-attachments/assets/7cc009f2-8165-4f69-b0e2-5bb213618e95

Anyway I've decided to report it as a bug. Since its possible and I'm not only one who will try it. And I feel like its totally possible.

One thing is calling `advance()` on thread will print an error to the console.
That because of `emit_signal(SNAME("mixer_applied"));` in the `AnimationMixer::_process_animation`. I have my edited version of engine where I just did this:
```
if(Thread::is_main_thread())
	emit_signal(SNAME("mixer_applied"));
```
Behavior of bug is the same, regardless.

### Steps to reproduce

Run test project provided and wait for a while. Sometimes you need to wait a minute. Sometimes its 30 minutes.

### Minimal reproduction project (MRP)

[test_manual_advance.zip](https://github.com/user-attachments/files/18421243/test_manual_advance.zip)
Repository: opencv
Issue: The findContours function is significantly slower in version 4.11 compared to version 4.7.
Labels: feature

### Describe the feature and motivation

Thank you for your work, but I tested and found that the speed of this function in version 4.11 is slower than in version 4.7.
Here are the test images and test results.
``` c++
#include <opencv2/opencv.hpp>
using namespace std;
using namespace cv;
int main()
{
	Mat img = imread("111.bmp", cv::IMREAD_GRAYSCALE);

	cv::Mat mask;
	inRange(img, 110, 120, mask);

	std::vector<std::vector<cv::Point>> v_cont;
	for (int i = 0; i < 10; i++)
	{
		v_cont.clear();
		auto start = chrono::system_clock::now();
		cv::findContours(mask, v_cont, cv::RETR_EXTERNAL, cv::CHAIN_APPROX_SIMPLE);
		auto end = chrono::system_clock::now();
		auto duration = chrono::duration_cast<chrono::microseconds>(end - start) / 1000.;
		cout << "4.11 findContours cost" << double(duration.count()) << "ms" << endl;
	}
}
```
![1234](https://github.com/user-attachments/assets/edc7d3a5-c3b5-4f9f-a91f-8654395a3f8e)

![image](https://github.com/user-attachments/assets/c36ebc72-71f9-4a2f-b04a-d50a8b0250e4)
![image](https://github.com/user-attachments/assets/2623e51b-3a8f-44be-b0bf-22a0ab407f48)


### Additional context

_No response_
Repository: flutter
Issue: Mac_mokey run_debug_test_android is 10.42% flaky
Labels: P0,c: flake,team-tool

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Mac_mokey run_debug_test_android"
}
-->

The post-submit test builder `Mac_mokey run_debug_test_android` had a flaky ratio 10.42% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1937
Commit: https://github.com/flutter/flutter/commit/e23c31265d75644fa89423321a5504620f09fa1c

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1937
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1934
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1932
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1931
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1924
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1922
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1917
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1910
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1909
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1905
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1902
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1900
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_mokey%20run_debug_test_android/1897

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_mokey%20run_debug_test_android

Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: flutter
Issue: Mac_arm64 build_tests_2_4 is 2.08% flaky
Labels: P0,c: flake,team-tool

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Mac_arm64 build_tests_2_4"
}
-->

The post-submit test builder `Mac_arm64 build_tests_2_4` had a flaky ratio 2.08% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64%20build_tests_2_4/4973
Commit: https://github.com/flutter/flutter/commit/0009cc358ff7e2c06d67b239cfa1f054cff93132

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64%20build_tests_2_4/4973
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64%20build_tests_2_4/4955

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Mac_arm64%20build_tests_2_4

Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: rust
Issue: `-Z split-dwarf-kind={single,split}` is undocumented in the unstable book
Labels: A-debuginfo,T-compiler,A-docs,A-CLI

Implementation history:

- In [rustc: Stabilize `-Z run-dsymutil` as `-C split-debuginfo` #79570][pr-79570]:
    - `-Z split-dwarf=single` became `-C split-debuginfo=packed`
    - `-Z split-dwarf=split` became `-C split-debuginfo=unpacked`
- However, as @davidtwco noted in 08ed338f561b000ce5672b55c0545fa7f3f13591 ([cg: split dwarf for crate dependencies #89819][pr-89819]):
    > In https://github.com/rust-lang/rust/pull/79570, `-Z split-dwarf-kind={none,single,split}` was replaced by `-C split-debuginfo={off,packed,unpacked}`. `-C split-debuginfo`'s packed and unpacked aren't exact parallels to single and split, respectively.
- As such, #89819 introduced `-Z split-dwarf-kind={single,split}` to fill in the gap.

This unstable compiler flag doesn't seem to have an entry in the unstable book, I only discovered them while looking at `tests/run-make/split-debuginfo`. It would be nice to document its behavior and also the meaning of its values.


[pr-79570]: https://github.com/rust-lang/rust/pull/79570
[pr-89819]: https://github.com/rust-lang/rust/pull/89819
Repository: ui
Issue: [bug]: After first rendering, when clicking on the bar, the tooltip position is incorrect.
Labels: bug

### Describe the bug

When I initially click on the bar after rendering, the tooltip moves to the wrong position.
In the example, I clicked on Jun and the tooltip's position changed even though the mouse position did not change.

![eeeee](https://github.com/user-attachments/assets/c4eec9b8-383c-42be-86ef-3b8c7b5b7d2b)
![err2](https://github.com/user-attachments/assets/d150fed8-b1cf-4375-ab47-aad3f4e38d6e)


An error occurs only the first time you click, and it operates normally from then on.

### Affected component/components

Chart

### How to reproduce

1. Bar Chart
2. click the bar
3. tooltip position changed, even though mouse position did not change.


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Mac, Chrome 131.0.6778.140(arm64)
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ant-design
Issue: ✨ 关于Table组件在虚拟滚动 行展开的略糟糕的体验说明
Labels: 🐛 Bug

### What problem does this feature solve?

行展开 虚拟滚动使用的时候，第一行点击展开之后展开到上面去了，第二行及下面几行的展开效果是期望的
demo🔗:  https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-zrzvf7



### What does the proposed API look like?

期望第一行点击展开之后能和第二行及之后的行同样向下展开，而非向上展开

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: i am getting error after running the command flutter doctor
Labels: waiting for customer response,in triage

### Steps to reproduce

Because flutter_tools depends on vm_service_interface 1.1.0 which doesn't match any versions, version solving failed.

### Actual results

Because flutter_tools depends on vm_service_interface 1.1.0 which doesn't match any versions, version solving failed.

### Logs

<details open>
<summary>Logs</summary>

```console

<!-- Paste your logs here -->

```

</details>


### Flutter Doctor output

<details open>
<summary>Doctor output</summary>

```console

<!-- Paste your output here -->

```

</details>
Repository: kubernetes
Issue: Prevent alpha feature gates from being enabled by default
Labels: kind/bug,sig/windows,sig/architecture,needs-triage

### What happened?

An alpha feature was accidently introduced as on-by-default which probably should not be allowed.
Maybe there should be some ci checks to prevent this from happening in the future?

https://github.com/kubernetes/kubernetes/blob/2d0a4f75560154454682b193b42813159b20f284/pkg/features/versioned_kube_features.go#L826

### What did you expect to happen?

Alpha features should not be on-by-default

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

https://github.com/kubernetes/kubernetes/blob/2d0a4f75560154454682b193b42813159b20f284/pkg/features/versioned_kube_features.go#L826

### Anything else we need to know?

/cc @enj 

### Kubernetes version

<details>

v1.32

</details>


### Cloud provider

<details>

N/A
</details>


### OS version

<details>

N/A

</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: PowerToys
Issue: Shortcut capability to easily change main display
Labels: Needs-Triage

### Description of the new feature / enhancement

Key combination to avoid having to use Settings>Display>[click on desired display]>Make this my main display.

### Scenario when this would be used?

Some games will only run on the main display.  The main display may not be the desired display when not running the game.  A quick way to switch main displays with shortcuts would be nice.

### Supporting information

Similar to the NirSoft MultiMonitorControl utility that I'm having trouble running the exec from command line in a batch file -- "The app will not run on this PC."
Repository: ui
Issue: [bug]: a couple of issues on iPhone 12 mini, viewport: 375x812
Labels: bug

### Describe the bug

1. carousel not filling width of container, works fine on other iPhone's and Android devices.
<img width="406" alt="Screenshot 2025-01-15 at 10 37 23" src="https://github.com/user-attachments/assets/3ac0acd6-235e-4e40-83ad-bb66ef17a740" />

2. The sheet content originating from top will create some glitch-y movement when trying to close.

### Affected component/components

Carousel, Sheet

### How to reproduce

Open website on iPhone 12 mini with these components and notice various issues.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
macOS 15.2, node v22.12.0, pnpm 9.15.3
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues