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

Platforms: linux

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

Over the past 3 hours, it has been determined flaky in 3 workflow(s) with 3 failures and 3 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_split_scan`
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_multi_kernel.py", line 272, in test_split_scan
    self.assertEqual(expect, actual)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4007, in assertEqual
    raise error_metas.pop()[0].to_error(
AssertionError: Tensor-likes are not close!

Mismatched elements: 44 / 3717120 (0.0%)
Greatest absolute difference: 22.0 at index (3650050,) (up to 1e-05 allowed)
Greatest relative difference: 1.370539848721819e-06 at index (3407607,) (up to 1.3e-06 allowed)

To execute this test, run the following from the base repo dir:
    python test/inductor/test_multi_kernel.py MultiKernelTest.test_split_scan

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

</details>


Test file path: `inductor/test_multi_kernel.py`

cc @clee2000 @wdvr @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov
Repository: pytorch
Issue: "RuntimeError: Triton Error [CUDA]: device kernel image is invalid" when running generated Triton code
Labels: triaged,module: inductor

### 🐛 Describe the bug

In https://github.com/pytorch/pytorch/issues/140395 I would like to run the generated Triton code for the program the user gave me. But I cannot: it has hard-coded what GPU architecture it is for, and I don't have exactly the same GPU. So when I run it, it fails with

```
Traceback (most recent call last):
  File "/data/users/ezyang/b/pytorch/wiggu.py", line 46, in <module>
    triton_red_fused__native_batch_norm_legit_functional_native_batch_norm_backward_threshold_backward_0 = async_compile.triton('triton_', '''
  File "/data/users/ezyang/b/pytorch/torch/_inductor/async_compile.py", line 235, in triton
    kernel.precompile()
  File "/data/users/ezyang/b/pytorch/torch/_inductor/runtime/triton_heuristics.py", line 293, in precompile
    compiled_binary, launcher = self._precompile_config(
  File "/data/users/ezyang/b/pytorch/torch/_inductor/runtime/triton_heuristics.py", line 520, in _precompile_config
    binary._init_handles()
  File "/home/ezyang/local/b/pytorch-env/lib/python3.10/site-packages/triton/compiler/compiler.py", line 376, in _init_handles
    self.module, self.function, self.n_regs, self.n_spills = driver.active.utils.load_binary(
RuntimeError: Triton Error [CUDA]: device kernel image is invalid
```

This makes me sad. It would be nice if the file did not actually bake in the architecture so it was portable across A100/H100/etc

### Versions

main

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov @oulgen @davidberard98
Repository: pytorch
Issue: How to specify the port for processes with rank > 1 in the Gloo communication backend?
Labels: oncall: distributed,triaged

In Pytorch, when performing distributed training using gloo as the communication backend, you only need to specify master_addr and master_port; other processes will actively connect and use random ports for initialization. May I ask if it is possible for other processes to perform initialization by specifying the port?

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: go
Issue: proposal: add a handful of acquire/release atomics (make the internal runtime versions public)
Labels: Proposal

### Proposal Details

I asked for this a [decade ago](https://github.com/golang/go/issues/35639), and I want to start this discussion up again.

I'm not saying Go should add the full gamut of relaxed, acquire, release, etc orderings available in other languages.

But I am saying it's useful to have some basic acquire and release loads and stores for 32bit, 64bit, and uintptr.

To see that this is useful one need look no further than the Go runtime which use exactly these. 

uintptr:
internal/runtime/atomic.LoadAcquintptr
internal/runtime/atomic.StoreReluintptr

uint32:
internal/runtime/atomic.LoadAcq
internal/runtime/atomic.StoreRel

uint64:
internal/runtime/atomic.LoadAcq64
internal/runtime/atomic.StoreRel64

I would like that we make these 6 functions available in the atomics package and a LoadAcq and StoreRel on each of the atomic types. I can make a PR.

It's not that these are so advanced and so dangerous that only Go runtime authors should have them. We deserve advanced tools too. For a language with concurrency as a strength, it's lacking in some important primitives to develop performant concurrent data structures. And it's not that we can't have that in Go, it's already implemented, it just isn't public.
Repository: next.js
Issue: [codemod] Unused params Causes next build Failure After Async API Codemod Execution
Labels: bug,Output (export/standalone)

### Link to the code that reproduces this issue

https://github.com/CastaChick/next_codemod_example

### To Reproduce

1. Create new next app using `next@14` by `npx create-next-app@14` command.
2. Add new pages with/without unused params

`app/example-unused-params/[id]/page.tsx`
```tsx
interface ExampleUnusedParamsProps {
   params: {
        id: string;
   }
}

// eslint-disable-next-line @typescript-eslint/no-unused-vars
export default function ExampleUnusedParams({params}: ExampleUnusedParamsProps) {
  return (
    <div>foo</div>
  )
}
```
`app/example-used-params/[id]/page.tsx`
```tsx
interface ExampleUsedParamsProps {
   params: {
        id: string;
   }
}

export default function ExampleUsedParams({params}: ExampleUsedParamsProps) {
  console.log(params.id)
  return (
    <div>foo</div>
  )
}
```

3. Run the migration command to `next@15` by running `npx @next/codemod@canary upgrade latest`
4. Then build the next app by running `npm run build` ← build failed

```
src/app/example-unused-params/[id]/page.tsx
Type error: Type 'ExampleUnusedParamsProps' does not satisfy the constraint 'PageProps'.
  Types of property 'params' are incompatible.
    Type '{ id: string; }' is missing the following properties from type 'Promise<any>': then, catch, finally, [Symbol.toStringTag]
```

### Current vs. Expected behavior

In Pull Request #71664 , it appears that transform is not executed when `params` is not accessed within a function. However, even if `params` is not used within the function, the build process (`next build`) will fail if `params` is not wrapped in a `Promise`.

To ensure developers can confidently build their projects after running `npx @next/codemod@canary next-async-request-api .`, I suggest either removing this behavior or ignoring unused, synchronously declared `params` during the build process. This adjustment would provide a smoother and more reliable development experience.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


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

Developer Experience, Output (export/standalone)

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

next build (local)

### Additional context

_No response_
Repository: transformers
Issue: BatchEncoding.to throws away columns silently, thus no way to pass non-tensor columns such as String in Trainer metric computation
Labels: bug

### System Info

unrelated

### Who can help?

@muellerzr @SunMarc
(original tags, no longer valid)

@ArthurZucker 
(re-tag because want to discuss patch release)

### Information

- [ ] The official example scripts
- [ ] 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

Hi thanks for the library! Consider this simple line:

```
x = transformers.tokenization_utils_base.BatchEncoding({'a': ['x','y']})
x.to('cpu') # or cuda or whatever
```

The column `a` is then silently removed :(

This is annoying in the following scenario: For each of my training/eval sample, I have a string column that serves as a tag for it, and want to utilize it when computing metrics and losses.

Then it does not work. After some debugging, the root reason is that it gets silently removed in the `to` mentioned above.

It seems torch does not support a tensor of dtype `str`, thus it seems impossible to have data pass through.

### Expected behavior

(see above)
Repository: tauri
Issue: [bug] How to display a window without taking focus in Linux
Labels: type: bug,status: needs triage

### Describe the bug

I am trying to implement a function: a pop-up floating window does not grab the focus of the previous application. For example, I am renaming a file and a floating window is opened through a shortcut key. I should be in the file name editing state and the window is displayed on the top layer.

Currently, there is no API that can achieve this effect

### Reproduction

I tried the functions `request_user_attention` and `set_ignore_cursor_events`, also without calling `set_focus`

### Expected behavior

_No response_

### Full `tauri info` output

```text
$ pnpm tauri info                                                                                                                 INT ✘ 

> eco-paste@0.4.0 tauri /home/witt/codes/open-source/EcoPaste
> tauri "info"


[✔] Environment
    - OS: Manjaro 24.1.2 x86_64 (X64)
    ✔ webkit2gtk-4.1: 2.44.4
    ✔ rsvg2: 2.58.4
    ✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
    ✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (2024-05-07)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 23.0.0
    - pnpm: 9.12.2
    - yarn: 1.22.22
    - npm: 10.9.0

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.2
    - tao 🦀: 0.30.8
    - @tauri-apps/api : 2.1.1
    - @tauri-apps/cli : 2.1.0

[-] Plugins
    - tauri-plugin-log 🦀: 2.0.2
    - @tauri-apps/plugin-log : 2.0.0
    - tauri-plugin-shell 🦀: 2.0.2
    - @tauri-apps/plugin-shell : 2.0.1
    - tauri-plugin-dialog 🦀: 2.0.3
    - @tauri-apps/plugin-dialog : 2.0.1
    - tauri-plugin-process 🦀: 2.0.1
    - @tauri-apps/plugin-process : 2.0.0
    - tauri-plugin-single-instance 🦀: 2.0.1
    - @tauri-apps/plugin-single-instance : not installed!
    - tauri-plugin-updater 🦀: 2.0.2
    - @tauri-apps/plugin-updater : 2.0.0
    - tauri-plugin-global-shortcut 🦀: 2.0.1
    - @tauri-apps/plugin-global-shortcut : 2.0.0
    - tauri-plugin-fs 🦀: 2.0.3
    - @tauri-apps/plugin-fs : 2.0.2
    - tauri-plugin-sql 🦀: 2.0.2
    - @tauri-apps/plugin-sql : 2.0.1
    - tauri-plugin-os 🦀: 2.0.1
    - @tauri-apps/plugin-os : 2.0.0
    - tauri-plugin-autostart 🦀: 2.0.1
    - @tauri-apps/plugin-autostart : 2.0.0

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: ant-design
Issue: antd 的 5.13.0 的更新，会导致在ios 13.3.1版本的手机浏览器里，Input输入框出现每输入一个字符，键盘就收起的情况
Labels: 📱Mobile Device

### Steps to reproduce

1、使用umi4新建一个测试项目
2、在umi4中，集成antd 5.13.0
3、随便写一个页面，在页面里，输一个Input框
4、启动起来，复制本地服务器地址
5、将地址复制到ios 13.3.1版本浏览器中
6、点击输入框，输入任一字符，会出现每输入一个字符，键盘就收起的情况

### What is expected?

Input在ios 13.3.1版本浏览器中，Input能正常输入，每输入一个字符，键盘不会收起

### What is actually happening?

antd 的 5.13.0 的更新，会导致在ios 13.3.1版本的手机浏览器里，Input输入框出现每输入一个字符，键盘就收起的情况

| Environment | Info |
| --- | --- |
| antd | 5.13.0 |
| React | "react": "^18.2.0", |
| System | ios 13.3.1 |
| Browser | safari |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: svelte
Issue: tick() doesn't seem to work
Labels: documentation

### Describe the bug

The code below is supposed to change the `clientHeight` of the `div` when the `button` is pressed and then `console.log` the original and the new height. According to the [svelte documentation](https://svelte.dev/docs/svelte/lifecycle-hooks#tick), you can "use `tick` to ensure that the UI is updated before continuing". But it doesn't work and still `console.log`s the original height. If you replace the `tick` function call in line 14 with my crude `customTick` function, it seems to work fine.

### Reproduction

```html
<script>
	import { tick } from 'svelte';
	const contents = ['Hello World', 'Hello<br />World'];
	let currentContent = $state(0);
	let clientHeight = $state();

	function customTick() {
		return new Promise((resolve, reject) => setTimeout(resolve, 1));
	}
	
	function changeContent() {
		console.log(`Client Height Before Change: ${clientHeight}px`);
		currentContent = (currentContent + 1) % 2;
		tick().then(() => console.log(`Client Height After Change: ${clientHeight}px`)); // Doesn't work
	}
</script>

<button onclick={changeContent}>Change Content</button>
<br /><br />
<div bind:clientHeight style="border: 1px solid red;">{@html contents[currentContent]}</div>
```
[Svelte Playground](https://svelte.dev/playground/4a8870c6f55e4271982626128dcb454a?version=5.2.10)

### Logs

_No response_

### System Info

```shell
I used the playground on svelte.dev
```


### Severity

annoyance
Repository: vscode
Issue: Invalid outline in search editor
Labels: bug,outline

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.95.3
- OS Version: Windows 24H2 26100.2454

Steps to Reproduce:

1. Navigate to search panel
2. Open new search editor
3. Perform some search
4. Navigate to outline panel
5. Jump to some file item in outline panel
6. Open new tab with error `Unable to resolve resource search-editor:#0.38606787525588104`
Repository: godot
Issue: Reordering node highlights it in scene tree but doesn't open it in inspector
Labels: bug,topic:editor,usability

### Tested versions

- Reproducible in: 4.3.stable

### System information

macOS 15.1.1 - Godot v4.3.stable - Forward+ - M1 Pro

### Issue description

Reparenting a node in the scene tree highlights the node and opens it in the inspector. However, reordering a node in the scene tree doesn't open the node in the inspector even though it highlights the node.

Not only is this inconsistent, it prevents one from then opening the node in the inspector as it is already highlighted, trying to rename the file instead.

See the video below for a demo of 1. reparenting a node vs 2. reordering a node. Pay attention to the inspector on the right.

https://github.com/user-attachments/assets/9c43c96b-4faf-46a5-9099-b030e8673783


### Steps to reproduce

- Reorder a node in the scene view.
- Observe that the node is not opened in the inspector.

### Minimal reproduction project (MRP)

N/A
Repository: transformers
Issue: No use `no_sync` context manager when using gradient accumulation w/ deepspeed's zero stage 2 or 3 via `accelerate`
Labels: Feature request

### Feature request

`trainer.train` with deepspeed stage 2 or 3 via `accelerate` and gradient accumulation does not work as I expected. I suspect this is because deepspeed 0.16.0 introduces `no_sync` context manager https://github.com/microsoft/DeepSpeed/pull/6675.

For example, the error looks like 

```
Traceback (most recent call last):
  File "main.py", line 70, in <module>
    main()
  File "main.py", line 90, in main
    trainer.train()
  File "/usr/local/lib/python3.11/dist-packages/transformers/trainer.py", line 2123, in train
    return inner_training_loop(
           ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/transformers/trainer.py", line 2480, in _inner_training_loop
    with context():
  File "/usr/lib/python3.11/contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/accelerate/accelerator.py", line 973, in no_sync
    with context():
  File "/usr/lib/python3.11/contextlib.py", line 137, in __enter__
    return next(self.gen)
           ^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/dist-packages/deepspeed/runtime/engine.py", line 1995, in no_sync
    assert not self.zero_optimization_partition_gradients(), \
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AssertionError: no_sync context manager is incompatible with gradient partitioning logic of ZeRO stage 3
```


### Motivation

In my understanding, `trainer.train()` with deepspeed via HF `accelerate` and gradient accumulation uses own forward implementation rather than `accelerate.accumulate` defined at 

https://github.com/huggingface/transformers/blob/052e652d6d53c2b26ffde87e039b723949a53493/src/transformers/trainer.py#L2474C75-L2482

So `no_sync` is always used. Even we give

```python
accelerator_config={'split_batches': False, 'dispatch_batches': None, 'even_batches': True, 'use_seedable_sampler': True, 'non_blocking': False, 'gradient_accumulation_kwargs': {'sync_each_batch': True}, 'use_configured_state': False}
``` 
to `TrainingArguments` to use a feature introduced by https://github.com/huggingface/transformers/issues/29425.


### Your contribution

As suggested in https://github.com/huggingface/transformers/issues/29425#issuecomment-2505015569, adding some warning to config args on docs might be helpful, but ideally addressing this feature is much nicer but I do not know the right approach.
Repository: next.js
Issue: Fast Refreshing dynamic component with CSS modules unloads CSS
Labels: bug,Lazy Loading,dynamicIO,CSS

### Link to the code that reproduces this issue

https://github.com/edenstrom/nextjs-dynamic-css-modules-reproduction

### To Reproduce

1. Start the application in development mode with `npm run dev`
2. Open MyComponent.tsx
3. Make any change, e.g. change the text in the component
4. CSS module unloads and the red text disappears

> [!NOTE]
> The bug only happens _without_ using Turbopack.
> Activating Turbopack fixes the issue
>
> In our case we still need the legacy bundler in our project

### Current vs. Expected behavior

I expected the CSS to still exist after fast refreshing, but I observed it disappearing instead.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.14.1
Relevant Packages:
  next: 15.0.4-canary.30 // Latest available version is detected (15.0.4-canary.30).
  eslint-config-next: N/A
  react: 19.0.0-rc-b01722d5-20241114
  react-dom: 19.0.0-rc-b01722d5-20241114
  typescript: 5.7.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Developer Experience, Lazy Loading

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

I've tested a lot of canary versions, and the bug were introduced in 15.0.0-canary.10.
It's not reproducible in 15.0.0-canary.9 or below.