sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: the mpi backend not support to transfer float16/bfloat16 tensor and would post "IndexError: map::at" when transferring float16/bfloat16 tensor
Labels: triaged,module: mpi

### 🐛 Describe the bug
when using mpi communication backend to transfer float16/bfloat16 tensor, the code will post "IndexError: map::at", like below:
`Traceback (most recent call last):
  File "/home/torch-mccl/tests/test_mpi.py", line 10, in <module>
Traceback (most recent call last):
  File "/home/torch-mccl/tests/test_mpi.py", line 10, in <module>
    dist.all_reduce(tensor=ins)
  File "/root/miniconda3/envs/for_pytorch/lib/python3.9/site-packages/torch/distributed/c10d_logger.py", line 72, in wrapper
    dist.all_reduce(tensor=ins)
  File "/root/miniconda3/envs/for_pytorch/lib/python3.9/site-packages/torch/distributed/c10d_logger.py", line 72, in wrapper
    return func(*args, **kwargs)
  File "/root/miniconda3/envs/for_pytorch/lib/python3.9/site-packages/torch/distributed/distributed_c10d.py", line 1997, in all_reduce
    return func(*args, **kwargs)
  File "/root/miniconda3/envs/for_pytorch/lib/python3.9/site-packages/torch/distributed/distributed_c10d.py", line 1997, in all_reduce
    work.wait()
IndexError: map::at
    work.wait()
IndexError: map::at
`
the code:
`
import torch.distributed as dist
import torch

dist.init_process_group("mpi")

rank = dist.get_rank()
ins = torch.randn(2, 3).to(torch.float16)

print("rank-{}, before broadcast, ins: {}.\n".format(rank, ins))
dist.all_reduce(tensor=ins)
print("rank-{}, after broadcast, ins: {}.\n".format(rank, ins))
`

### Versions

PyTorch version: 2.2.0a0+git8ac9b20
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.6 LTS (x86_64)
GCC version: (Ubuntu 9.4.0-1ubuntu1~20.04.2) 9.4.0
Clang version: Could not collect
CMake version: version 3.26.4
Libc version: glibc-2.31

Python version: 3.9.17 (main, Jul  5 2023, 20:41:20)  [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.4.0-189-generic-x86_64-with-glibc2.31
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.25.2
[pip3] optree==0.13.0
[pip3] torch==2.2.0a0+git8ac9b20
[conda] mkl                       2023.1.0         h213fc3f_46343  
[conda] mkl-include               2023.1.0         h06a4308_46343  
[conda] numpy                     1.25.2                   pypi_0    pypi
[conda] optree                    0.13.0                   pypi_0    pypi
[conda] torch                     2.2.0a0+git8ac9b20           dev_0    <develop>
```[tasklist]
### Tasks
```
Repository: rust
Issue: std::process::Command::spawn cause panic on Windows 10 21H2 19044.2846
Labels: O-windows-msvc,C-bug,T-libs,S-needs-repro

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->
I tried this code:

```rust
#[test]
fn test2() {
    std::process::Command::new("adb")
    .args(["devices"])
    .stdout(Stdio::piped())
    .stderr(Stdio::piped())
    .spawn()
    .unwrap();
}
```
Only panics when using use std::process::Command; in **Test Debug** mode, but not in other cases.
And only panic on Windows 10 21H2 19044.2846.

Here is an issue discussing this problem, and it includes two videos of about ten seconds to demonstrate the situation.
https://github.com/tokio-rs/tokio/issues/6934


### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-pc-windows-msvc
release: 1.82.0
LLVM version: 19.1.1
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```

test test2 ... FAILED

successes:

successes:

failures:

---- test2 stdout ----
thread 'test2' panicked at src/main.rs:80:6:
called `Result::unwrap()` on an `Err` value: Os { code: 6, kind: Uncategorized, message: "鍙ユ焺鏃犳晥銆? }
stack backtrace:
   0: std::panicking::begin_panic_handler
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/std\src\panicking.rs:662
   1: core::panicking::panic_fmt
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/core\src\panicking.rs:74
   2: core::result::unwrap_failed
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/core\src\result.rs:1677
   3: enum2$<core::result::Result<std::process::Child,std::io::error::Error> >::unwrap
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library\core\src\result.rs:1102
   4: static_lib::test2
             at .\src\main.rs:77
   5: static_lib::test2::closure$0
             at .\src\main.rs:76
   6: core::ops::function::FnOnce::call_once<static_lib::test2::closure_env$0,tuple$<> >
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library\core\src\ops\function.rs:250
   7: core::ops::function::FnOnce::call_once
             at /rustc/f6e511eec7342f59a25f7c0534f1dbea00d01b14\library/core\src\ops\function.rs:250
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
2

failures:
    test2

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.07s
```

I deciphered the garbled message, and it seems to mean "The handle is invalid."
</p>
</details>
Repository: Python
Issue: Request to Implement Shor Algorithm
Labels: enhancement

### Feature description

Hi, I wanted to implement the logical algorithm without the use of Qiskit and Cirq 
to show how Shor Algorithm that is used in quantum computing
breaks RSA cryptography by easily finding n that is used to develop the public and private key of a user.
Repository: go
Issue: proposal: runtime/mainthread: add mainthread.Do for mediating access to the main thread
Labels: Proposal

### Proposal Details

This is https://github.com/golang/go/issues/64777#issuecomment-2424750130 in proposal form. It is a reduced and compatible variant of https://github.com/golang/go/issues/64777#issuecomment-2261119181.

I propose to add a new package, `mainthread`, with a single function, `Do`, that allows Go programs to execute a function on the main thread.

```go
// Package mainthread mediates access to the program's main thread.
//
// Most Go programs do not need to run on specific threads 
// and can ignore this package, but some C libraries, often GUI-related libraries,
// only work when invoked from the program's main thread.
//
// [Do] runs a function on the main thread. No other code can run on the main thread
// until that function returns.
//
// Each package's initialization functions always run on the main thread,
// as if by successive calls to Do(init).
//
// For compatibility with earlier versions of Go, if an init function calls [runtime.LockOSThread], 
// then package main's func main also runs on the main thread, as if by Do(main).
package mainthread // imported as "runtime/mainthread"

// Do calls f on the main thread.
// Nothing else runs on the main thread until f returns.
// If f calls Do, the nested call panics.
//
// Package initialization functions run as if by Do(init).
// If an init function calls [runtime.LockOSThread], then package main's func main
// runs as if by Do(main), until the thread is unlocked using [runtime.UnlockOSThread].
//
// Do panics if the Go runtime is not in control of the main thread, such as in build modes
// c-shared and c-archive.
func Do(f func())
```

The larger proposal (https://github.com/golang/go/issues/64777#issuecomment-2261119181) adds `Yield` and `Waiting` to support sharing the main thread in a Go program. However, the Go runtime doesn't always have control over the main thread, most notably in c-shared or c-archive mode on platforms such as Android. In those cases, the platform facility for mediating main thread access are strictly superior to `mainthread.Do`. See https://github.com/golang/go/issues/64777#issuecomment-2384085299 for a detailed analysis and assumptions.

In short, I believe it's better to accept this simpler proposal to only allow Go programs access to the main thread when the Go runtime has control over it, and let other cases be handled by platform API.

I hope this can be implemented in Go 1.24.
Repository: angular
Issue: Service worker not updating after its response headers are updated
Labels: help wanted,area: service-worker

### Which @angular/* package(s) are the source of the bug?

Don't known / other

### Is this a regression?

Yes

### Description

Hello,

I have came across a strange issue. I have a CSP policy setup done by the server through response headers. I also have a service worker running for the same page.

When I update the CSP in the server, its getting updated for the index.html, But the service-worker itself is not getting updated with the new CSP. The service worker is throwing CSP errors even tough the index.html and other assets got the CSP updated.

could you please give an way to re-load/update the service worker(ngsw-worker.js), when its own response headers are updated?

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

Angular CLI: 17.1.4
Node: 20.12.2
Package Manager: npm 10.8.2
OS: win32 x64

Angular: 17.1.2
... animations, cdk, common, compiler, compiler-cli, core, forms
... language-service, localize, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1701.2
@angular-devkit/build-angular   17.1.2
@angular-devkit/core            17.1.2
@angular-devkit/schematics      17.1.2
@angular/cli                    17.1.4
@schematics/angular             17.1.2
ng-packagr                      17.1.2
rxjs                            7.8.0
typescript                      5.3.3
zone.js                         0.14.3

### Anything else?

_No response_
Repository: godot
Issue: Animation is bugged on import
Labels: bug,confirmed,topic:import,topic:animation

### Tested versions

4.2.1 stable

### System information

Godot v4.2.1.stable - Windows 10.0.19044 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 6GB (NVIDIA; 31.0.15.5244) - Intel(R) Core(TM) i5-4440 CPU @ 3.10GHz (4 Threads)

### Issue description

Importing animations in Godot batters them up - bones aren't being parented, or they are moved in another place for whatever reason. An example of one of them animations, in Blender (4.1) and Godot: (sorry for low fps)

https://github.com/user-attachments/assets/44747829-cb1c-4196-8433-bc274634c463

https://github.com/user-attachments/assets/228b92cb-39b6-4ed1-8726-46a13bb27f39

Tried disabling Optimizer - not working. I am also using the Dynamic Parent addon for Blender - could that be the issue?



### Steps to reproduce

Just open the project and open v_hammer.tscn. All of the animations there are messed up in some way. In idle, the hammer is moved, in draw it moves on the last frame, in holster it doesn't move at all, and in attack_1 the head of the hammer is also moved slightly - might want to slow down animation speed to see it.

### Minimal reproduction project (MRP)

[AnimationBug.zip](https://github.com/user-attachments/files/17556058/AnimationBug.zip)
Repository: TypeScript
Issue: Using JSX syntax in a namespace may incorrectly use the exported members of the current namespace as intrinsic elements (starting with a lowercase letter)
Labels: Bug,Help Wanted

### 🔎 Search Terms

jsx namespace preserve export intrinsic

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about (no entries for this)


### ⏯ Playground Link

https://www.typescriptlang.org/play/?jsx=1&ts=5.6.3#code/JYWwDg9gTgLgBAbzgKQMoA04F84DMoQhwBEUApgIYDGMxA3AFBkAekscAdhSGQM5jUyeaEQQM4cFm3hUIHXvGAcwAV3gBeTioA22xhKnQZchXBh8NcADxLV8APQA+cXHv2JHz168A9APwMWAxAA

### 💻 Code

WITH `jsx: preserve` enabled in tsconfig.json
```ts
export namespace form {
  export const input = null;
  export const test = <input />
}
```


### 🙁 Actual behavior

generated code:
```js
export var form;
(function (form) {
    form.input = null;
    form.test = <form.input />;
})(form || (form = {}));
```

### 🙂 Expected behavior

generated code:
```js
export var form;
(function (form) {
    form.input = null;
    form.test = <input />;
})(form || (form = {}));
```

### Additional information about the issue

In fact, I observed this problem in a certain version of swc (swc does not support preserve mode, and the problem can be reproduced without enabling preserve mode). Considering that swc largely replicates the behavior of tsc, I suspected that this problem also exists in ts, and it is true, but only in jsx: preserve mode
Repository: PowerToys
Issue: Mouse without borders become crazy when the wifi signal lost and restore.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

I have 4 machines with same version of powertoys. 2 of them by wire and 2 other by wifi.

With one wired machine being master, y use the other 3 machines as slaves.

When the wifi lost and reconect, the mouse without borders go crazy and if i move my mouse arround screen, the cursor clicks random and make keyboard pulsations. Seems to repeat my last actions but in random places.

I have MWB with service enabled and using it with shortcuts. Not use de move out cursor to change the machine.

### ✔️ Expected Behavior

If i need to reload the service, or reload the config saved of PowerToys or similar action to restore de normal funcion of the cursor and keyboard, it's not problem... but... i don't know.

The only solution is restart the wifi PC to restore normal function.

### ❌ Actual Behavior

The cursor go crazy and do random clicks and keyboard strokes....

### Other Software

_No response_
Repository: go
Issue: cmd/go: inconsistent reporting of default Go version
Labels: NeedsInvestigation,GoCommand

In the transcript below, there is no go line in the go.mod.
Builds say I can't use post-Go 1.16 features, but then when I say
"go get go@1.21.0" (using a sufficiently old version so as not to break any users),
it claims I am downgrading from Go 1.24.

```
% go install
# rsc.io/tmp/jsonfmt
./jsonfmt.go:95:9: predeclared any requires go1.18 or later (-lang was set to go1.16; check go.mod)
% cat go.mod
module rsc.io/tmp/jsonfmt
% go get go@go1.21.0
go: downgraded go 1.24 => 1.21.0
go: added toolchain go1.24
% cat go.mod
module rsc.io/tmp/jsonfmt

go 1.21.0

toolchain go1.24
% 
```
Repository: godot
Issue: Error when setting Texture3D slices to 16x16
Labels: bug,topic:rendering

### Tested versions

- Reproducible in v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU (NVIDIA; 32.0.15.6603) - 13th Gen Intel(R) Core(TM) i7-13700H (20 Threads)

### Issue description

When importing a Texture3D resource with the following characteristics:
- 2048x2048 resolution
- channels used: RGBA
- number of slices: 16

Godot reports the following error:

```
  Data for slice index 0 (mapped to layer 0) differs in size (supplied: 4793584) than what is required by the format (4793568).
  servers/rendering/renderer_rd/storage_rd/texture_storage.cpp:1070 - Condition "texture.rd_texture.is_null()" is true.
  Attempting to use an uninitialized RID
  servers/rendering/renderer_rd/storage_rd/texture_storage.cpp:1362 - Parameter "tex" is null.

```

Setting the slices to 8x8 does not result in an error. I've tried different combinations of resolutions, and import settings, but only the slices number seem to be the culprit. I've attached the texture file to this report.
[T_Fog_1.zip](https://github.com/user-attachments/files/17556389/T_Fog_1.zip)

I realize that 16x16 slices are over-the-top. Perhaps then the number of slices should be capped to 8?

### Steps to reproduce

- Import the texture with the following settings:

![image](https://github.com/user-attachments/assets/0546e86d-e7bf-4987-a02f-9a47279c1864)

- Use it in a shader (see attached example)

### Minimal reproduction project (MRP)

A test scene is attached.

[godot_bug_noise.zip](https://github.com/user-attachments/files/17556563/godot_bug_noise.zip)
Repository: transformers
Issue: Please don't kill BetterTransformer — 1.88x faster inference than SDPA
Labels: Feature request

### Feature request

I would like to request that BetterTransformer not be deprecated. See also [optimum#2083](https://github.com/huggingface/optimum/issues/2083).

This issue is intended to track the lack of feature-parity in Hugging Face `transformers` with BetterTransformer.

### Motivation

This is a simple example that demonstrates just how valuable BetterTransformer is to users of BERT-like models:
```python
```python
import torch

from transformers import RobertaModel, RobertaTokenizerFast

# BEGIN CONFIG #
MODEL_NAME = 'umarbutler/emubert'
EXAMPLE_INPUT = "\
The Parliament shall, subject to this Constitution,\
have power to make laws for the peace, order, and good\
government of the Commonwealth with respect to:\
    (i) trade and commerce with other countries, and among\
        the States;\
    (ii) taxation; but so as not to discriminate between"""
# END CONFIG #

sdpa_model = RobertaModel.from_pretrained(MODEL_NAME, attn_implementation = 'sdpa').to(torch.bfloat16).to('cuda').eval()
bettertransformer_model = RobertaModel.from_pretrained(MODEL_NAME).to(torch.bfloat16).to_bettertransformer().to('cuda').eval()
tokenizer = RobertaTokenizerFast.from_pretrained(MODEL_NAME)
input_tokens = tokenizer(EXAMPLE_INPUT, return_tensors='pt').to('cuda')

with torch.inference_mode():
    # Do unbenched forward passes to control for potential caching effects.
    for _ in range(10):
        bettertransformer_model(**input_tokens)
        sdpa_model(**input_tokens)
    
    # Benchmark the models.
    %timeit bettertransformer_model(**input_tokens)
    %timeit sdpa_model(**input_tokens)
```

On my 4090, BetterTransformer achieves `1.93 ms ± 104 μs` and SDPA achieves `3.64 ms ± 259 μs`. BetterTransformer is almost 2x faster (1.88x)...

I have found both training and inference to be *significantly* faster with BetterTransformer enabled, even compared to SPDA and flash attention 2. I believe this is because of how it fuses layers into a single encoder block. Until/if ever that functionality and its associated performance gains can be incorporated into Hugging Face, I'd be fine with having BetterTransformer deprecated, but until then, BetterTransformer's removal would make my code and the code of other users of BetterTransformer significantly slower.

### Your contribution

This request.
Repository: transformers
Issue: Vision (Auto)Processor multiple images finetuning example.
Labels: Examples,Feature request,Multimodal

### Feature request

Is it possible to upload an example of how to finetune PaLIGemma on multi-image inputs?
Something similar to [multi-image-inference](https://huggingface.co/docs/transformers/main/model_doc/paligemma#multi-image-inference), which shows how to perform multi-image inference over PaLIGemma.

### Motivation

enabling finetuning of multi-image PaLIGemma

### Your contribution

.
Repository: PowerToys
Issue: remap shortcut not working
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.85.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

remap a key or shortcuts still not working

### ✔️ Expected Behavior

fix this bug

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: vscode
Issue: Hovering warning icon in terminal tab is difficult to action
Labels: bug,workbench-hover,terminal-tabs

Repro:

1. Build and debug terminal-sample
2. Run Terminal API: update or clear environment commands, a ⚠ should show
3. Hover it, try move the mouse into the hover

![Image](https://github.com/user-attachments/assets/d253214e-fecd-4ba7-99fb-9b1aa4b0929d)

A solution after https://github.com/microsoft/vscode/pull/232435 would be for the warning icon to have its own hover
Repository: next.js
Issue: Emotion compiler not properly working when using "paths" in TypeScript since 13.5.x
Labels: bug,SWC

### Link to the code that reproduces this issue

https://github.com/Itrulia/material-ui-next-nx

### To Reproduce

1. npm install && npx nx dev emotion-test
2. Open `http://localhost:3000`
3. Inspect the HTML output and see `.mui-fh6enu{color:pink;}.mui-fh6enu .undefined{color:#f00!important;}.mui-bdz642{color:pink;}`

4. Change next to `~13.4.19` and it works. 
5. OR move 

```
${StyledPageWebsite} {
    color: #f00 !important;
  }
```

to the app (for example index.ts) and it works again.

### Current vs. Expected behavior

The emotion plugin does not seem to be applied to a library that is referenced via the tsconfig paths. Component selectors by  emotion thus don't work properly.

Expected (v13.4.x) vs Now (15.0.0)
![image](https://github.com/user-attachments/assets/db1ed3e2-3a25-48dd-a766-b52f263c8e9c)

![image](https://github.com/user-attachments/assets/c05973c4-6ad1-4536-88d1-8bc48b0a8923)



### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 22.8.0
  npm: 10.8.2
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 15.0.1 // Latest available version is detected (15.0.1).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: N/A
```


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

SWC

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

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

When changing next to `~13.4.19` it works again, changing it to `~13.5.0` it stopps working.

At first I thought it was this change: https://github.com/vercel/next.js/commit/311eea4c6ab847548d81421a8edbf86ac77341f9

But this is actually setting it to `@emotion/react`:

```
console.error(isServerLayer, (jsConfig == null ? void 0 : (_jsConfig_compilerOptions4 = jsConfig.compilerOptions) == null ? void 0 : _jsConfig_compilerOptions4.jsxImportSource) ?? ((compilerOptions == null ? void 0 : compilerOptions.emotion) && !isServerLayer ? "@emotion/react" : "react"))

> false @emotion/react
```