sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [profiler]Not passed shapes for lists of tensors to kineto_result
Labels: OSS contribution wanted,oncall: profiler

### 🐛 Describe the bug

https://github.com/pytorch/pytorch/pull/109751/files#diff-857d7d889693922265a363e8ceb661dfb4d654b34d11ca669be352f45f54998dR107. This patch not assign value to `shapes_for_kineto_event` if type is `std::vector<TensorMetadata>`. So, we can't get shapes of list tensors in https://github.com/pytorch/pytorch/blob/main/torch/autograd/profiler.py#L456.

The impact of this issue might be relatively minor.

### Versions

main

cc @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise @nbcsm @gaoteng-git @tiffzhaofb
Repository: godot
Issue: Changing `NavigationRegion3D.navigation_mesh.cell_size` doesn't set up `NavigationServer3D` respective map to correct `cell_size` resulting in mismatch error
Labels: discussion,topic:navigation

### Tested versions

v4.2.2.rc1.official [c7fb0645a]

### System information

Ubuntu 23.04, Vulkan, NVIDIA GeForce RTX™ 2060 / NVIDIA GeForce RTX™ 2060, NVIDIA Driver Version: 525.105.17, NVML Version: 12.525.105.17

### Issue description

This seems something similar to https://github.com/godotengine/godot/issues/83570, but for `NavigationRegion3D`/`NavigationMesh`.

```
ERROR: Navigation map synchronization error. Attempted to update a navigation region with a navigation mesh that uses a `cell_size` of 0.10000000149012 while assigned to a navigation map set to a `cell_size` of 0.25. The cell size for navigation maps can be changed by using the NavigationServer map_set_cell_size() function. The cell size for default navigation maps can also be changed in the ProjectSettings.
   at: update_polygons (modules/navigation/nav_region.cpp:128)
```

The error occurs when when:
1. First ever creating a `NavigationMesh` with a different `cell_size` and then using *Bake NavigationMesh*. On subsequent recreations of `NavigationMesh` in the same Godot session the error doesn't occur.
2. When opening a new Godot instance where a `NavigationMesh.cell_size` is different from the project properties default value.
3. At runtime when `NavigationMesh.cell_size` is different from the project properties default value.

The workaround is to call `NavigationServer3D.map_set_cell_size(get_navigation_map(), navigation_mesh.cell_size)` somewhere in the code.

### Steps to reproduce

Open the Minimal Reproduction Project and see the error first occur since I have assigned a `NavigationMesh` to `NavigationRegion3D.navigation_mesh` with a `cell_size` of `0.1` which is different from the default project properties of `0.25`.

When you run the project you'll also get the error.

I've attached a workaround script to `NavigationRegion3D` which calls `NavigationServer3D.map_set_cell_size(get_navigation_map(), navigation_mesh.cell_size)` and fixes the error at runtime. This code is commented out for the purpose of demonstration.

### Minimal reproduction project (MRP)

[godot-dbg.zip](https://github.com/godotengine/godot/files/14534054/godot-dbg.zip)
Repository: tauri
Issue: [bug] Software resource parsing exception in weak network environment
Labels: type: bug,status: needs triage

### Describe the bug

I used Fiddler to test the application's performance on a weak network, and found that although the webpage content had already been loaded (through F12 review, it was found that the dom element had already been loaded), it still did not render and instead showed a white screen. 

This is inconsistent with my understanding. In my opinion, after the webpage resources have been clearly loaded into the window after creation, there should not be a white screen.

Is there any way to solve it？

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
null
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: pytorch
Issue: torch.linalg.eigh is very slow compared to tf.linalg.eigh
Labels: module: performance,triaged,module: mkl,module: linear algebra

### 🚀 The feature, motivation and pitch

I'm using torch.linalg.eigh, but I have found it to be very slow compared to the tensorflow implementation of the same method. 
See the following code for the comparison between torch, tensorflow and numpy:
```

import numpy as np
import tensorflow as tf
import torch
import time

matrix = np.random.rand(2985984, 3, 3)
matrix_tf = tf.convert_to_tensor(matrix, dtype=tf.float32)
matrix_torch = torch.tensor(matrix, dtype=torch.float32)

# Benchmarking TensorFlow's eigh
start_time = time.time()
eigenvalues, eigenvectors = tf.linalg.eigh(matrix_tf)
tf_time = time.time() - start_time
print(f"TensorFlow time: {tf_time} seconds : {tf.__version__}")

# Benchmarking PyTorch's eigh
start_time = time.time()
eigenvalues, eigenvectors = torch.linalg.eigh(matrix_torch)
torch_time = time.time() - start_time
print(f"PyTorch time: {torch_time} seconds : version {torch.__version__}")

# Benchmarking numpy eigh
start_time = time.time()
eigenvalues, eigenvectors = np.linalg.eigh(matrix)
torch_time = time.time() - start_time
print(f"Numpy time: {torch_time} seconds : version {np.__version__}")
```
Results in:

> TensorFlow time: 0.07259178161621094 seconds : 2.15.0
> PyTorch time: 2.872485399246216 seconds : version 2.3.0a0+ebedce2
> Numpy time: 2.981818675994873 seconds : version 1.24.4
> 

How can the tensorflow implementation be this much more efficient?

### Alternatives

_No response_

### Additional context

_No response_

cc @jianyuh @nikitaved @pearu @mruberry @walterddr @xwang233 @Lezcano
Repository: tensorflow
Issue: The result of tf.quantization.fake_quant_with_min_max_args is inconsistent between CPU and GPU
Labels: type:bug,comp:ops,TF 2.15

### Issue type

Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

tf 2.15

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 20.04

### Mobile device

_No response_

### Python version

3.8

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

CUDA 12.2

### GPU model and memory

_No response_

### Current behavior?

For the same input, `tf.quantization.fake_quant_with_min_max_args ` produces inconsistent results on CPU and GPU.

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

input_data = tf.constant([0.0, 1.0, 2.0, 3.0, 4.0])

with tf.device('cpu:0'):
    quantized_input_data = tf.quantization.fake_quant_with_min_max_args(input_data, min=-6.0, max=6.0)
    print(quantized_input_data)

with tf.device('gpu:0'):
    quantized_input_data = tf.quantization.fake_quant_with_min_max_args(input_data, min=-6.0, max=6.0)
    print(quantized_input_data)
```


### Relevant log output

```shell
tf.Tensor([0.        0.9882353 2.0235295 3.0117648 4.       ], shape=(5,), dtype=float32)
tf.Tensor([0.        0.9882353 1.9764706 3.0117648 4.       ], shape=(5,), dtype=float32)
```
Repository: rust
Issue: `mismatched types`: data type not inferred by compiler
Labels: A-inference,A-coercions,C-discussion,T-types

```rs
fn main() {
    let arr = vec![1, 2, 3];
    let x1 = (&arr[0..0], &arr[0..0]);
    assert_eq!(x1, (&[], &[]));
}
```

compiler error:

```
mismatched types
expected tuple `(&[{integer}], &[{integer}])`
   found tuple `(&[_; 0], &[_; 0])`
```
Repository: electron
Issue: [Feature Request]:  Please support Wayland by default in Electron on Linux
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

26.2.4

### What operating system are you using?

Ubuntu

### Operating System Version

6.2.0-39-generic #40-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:18:00 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

As of today, Electron applications do not support/enable Wayland out of the box, but rather run under XWayland. Please support Wayland by default in Electron on Linux. Are there any blocker issues to enable Wayland by default?

For example, I had a discussion with RStudio developers who decided to wait enabling Wayland by default until Wayland is supported by default out-of-the-box in Electron. https://github.com/rstudio/rstudio/issues/11962#issuecomment-1984134246

### Actual Behavior

.

### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: go
Issue: proposal: iter: add Empty function
Labels: Proposal

### Proposal Details

Add `Empty` function to `iter` package.
This function returns empty iterator.

### Implementation

```go
package iter

func Empty[T any]() Seq[T] {
	return func(yield func(T) bool) {}
}

func Empty2[K, V any]() Seq2[K, V] {
	return func(yield func(K, V) bool) {}
}
```

### Usage

This function is useful to replace slice/map implementation to iter implementation.
Please see following code.
This function do something to all item when `cond` is true.

```go
func do(cond bool) {
	var all []int
	if cond {
		all = findAll()
	}
	for _, v := range all {
		doItem(v)
	}
}
```

https://github.com/golang/go/issues/65629 was declined, so range over nil function panics.
I have to rewrite like following.

```go
func do(cond bool) {
	var all iter.Seq[int]
	if cond {
		all = findAll()
	}
	if all == nil {
		return
	}
	for _, v := range all {
		doItem(v)
	}
}
```

When `Empty` function exists, I can migrate code easily.
```go
func do(cond bool) {
	var all = iter.Empty[int]()
	if cond {
		all = findAll()
	}
	for _, v := range all {
		doItem(v)
	}
}
```
Repository: next.js
Issue: Layout rerender every route navigate after build but dev is fine
Labels: bug

### Link to the code that reproduces this issue

https://github.com/zoom2009/nextjs-layout-rerender

### To Reproduce

**Develop case (Working fine)**
1. yarn dev
2. open inspect and press info or home to see a log

**Production case (bug by call useEffect every route navigate)**
1. yarn build
2. yarn start
3. open inspect and press info or home to see a log

### Current vs. Expected behavior

**Current**
after build useEffect call every route navigate that make my layout re-render every time how can I shallow it?

**Expect**
like `yarn dev` useEffect call only once in layout

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:52 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T8103
Binaries:
  Node: 20.10.0
  npm: 10.4.0
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.1.3
  eslint-config-next: 14.1.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A
```


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

App Router

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

next build (local), Vercel (Deployed)

### Additional context

**develop mode `yarn dev` is work well**

https://github.com/vercel/next.js/assets/33366155/1ad448ef-58ee-4300-84de-577e6857fa9a

<hr />

**production mode `yarn build && yarn start` is re-render every route navigate**

https://github.com/vercel/next.js/assets/33366155/d5d58dd3-e592-4bfb-bc6c-1da6ed65d3ec

<hr />

**Here my reproduce code**
https://github.com/zoom2009/nextjs-layout-rerender

Do you guy have any solution for do not make layout re-render every route navigate ?
thank you.
Repository: neovim
Issue: multibyte 'langmap' doesn't work for custom mapping
Labels: bug-vim,unicode  💩,mappings

### Problem

`langmap` works as expected for neovim motions etc but it quickly becomes _unusable_ when trying to use custom `maps` since those expect their assigned  `lhs` key , that as it seems isnt affected by the `langmap` setting.
```lua
vim.opt.langmap = {
    "ΑA", "ΒB", "ΨC", "ΔD", "ΕE", "ΦF", "ΓG", "ΗH", "ΙI", "ΞJ", "ΚK", "ΛL", "ΜM", "ΝN",
    "ΟO", "ΠP", "QQ", "ΡR", "ΣS", "ΤT", "ΘU", "ΩV", "WW", "ΧX", "ΥY", "ΖZ",
    "αa", "βb", "ψc", "δd", "εe", "φf", "γg", "ηh", "ιi", "ξj", "κk", "λl", "μm", "νn",
    "οo", "πp", "qq", "ρr", "σs", "τt", "θu", "ωv", "ςw", "χx", "υy", "ζz",
}
vim.keymap.set('n', 'Z', function() vim.notify("real lua function") end,{noremap=true})
```

### Expected behavior

I would expect that all aspects of neovim respect the langmap thus making using different languages as input seamless.

* Maybe have a way to set keymaps via keycodes (Below greek alpha and latin a have the same code on the keyboard )
![image](https://github.com/neovim/neovim/assets/61395246/c26539d5-81af-4459-9dd7-a550ffbfcf1e)
* Or extend the `langmap` to affect keymaps as well
Repository: next.js
Issue: The font loader should tolerate backtick strings without template variables
Labels: bug,Font (next/font)

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/modest-mestorf-42dh9l

### To Reproduce

1. Add a `next/font` call with backtick strings:

```ts
import {Inter} from 'next/font/google';

const inter = Inter({
  subsets: [`latin`],
  display: `swap`,
  variable: `--font-inter`,
});
```

2. Run the application

### Current vs. Expected behavior

Next.js crashes on template-less backtick strings when used within a `localFont` call. It should tolerate such strings, as they are fully static. Some lint rules even enforce their use everywhere possible, rather than `'` or `"`.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 4.1.1
  pnpm: N/A
Relevant Packages:
  next: 14.1.3
  eslint-config-next: 14.1.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A
```


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

Font optimization (next/font)

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

next dev (local), next build (local)

### Additional context

_No response_
Repository: vscode
Issue: Multi Cursor: Selections Have Different Height
Labels: bug,editor-multicursor


![Image](https://github.com/microsoft/vscode/assets/2931520/8c232683-56bb-4457-acdd-7b582531080c)

![Image](https://github.com/microsoft/vscode/assets/2931520/be5e5678-223d-4d34-ae75-b434d8050fa3)
Repository: PowerToys
Issue: [ColorPicker] Provides wrong color with magnifier
Labels: Issue-Bug,Priority-3,Product-Color Picker,Status-Reproducible

### Microsoft PowerToys version

0.79.0

### Installation method

PowerToys auto-update, Microsoft Store

### Running as admin

No

### Area(s) with issue?

ColorPicker

### Steps to reproduce

1. Open the "magnifier"
2. Enlarge the screen (cannot be 100%)
3. Open the Color Chooser
4. Choose a color
5. Bug!

![image](https://github.com/microsoft/PowerToys/assets/105980161/581d351e-082f-4bf5-bec3-e6fb7f77816a)
[PowerToysReport_2024-03-08-18-22-22.zip](https://github.com/microsoft/PowerToys/files/14536873/PowerToysReport_2024-03-08-18-22-22.zip)


### ✔️ Expected Behavior

选取的颜色是鼠标指针指着的位置的颜色
The selected color should be the color of the position pointed by the mouse pointer

### ❌ Actual Behavior

实际上，选择的颜色与鼠标指针指着的位置的颜色不一致
Actually, the selected color does not match the color of the position pointed by the mouse pointer

### Other Software

放大镜（Windows 系统自带）
Magnifier (built-in in Windows)
Repository: pytorch
Issue: Kubernetes API server as Rendezvous backend
Labels: oncall: distributed

### 🚀 The feature, motivation and pitch

The `torchrun` supports `etcd` and `c10d` as rendezvous backend. If torch run jobs need to be run in kubernetes clusters, we need to rely on `etcd` (either self hosted or hosted by the cloud provider). The Kubernetes API server is also based on `etcd`. If we can implement a `RendezvousHandler` that uses Kubernetes API server as rendezvous backend, we can run `torchrun` without any external dependencies on Kubernetes clusters.

Please provide your thoughts on this!

### Alternatives

_No response_

### Additional context

_No response_

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @chauhang
Repository: rust
Issue: snapshots sometimes leak inference variables
Labels: C-cleanup,T-types

When using `InferCtxt::probe/commit_if_ok`, we discard all inference variables created inside of this snapshot. This means that returning a type containing inference variables from it can later result in ICE if we try to access them.

This should not happen and we should protect ourselves from doing so in the future. cc https://rust-lang.zulipchat.com/#narrow/stream/144729-t-types/topic/leaking.20infer.20vars.20from.20snapshots
Repository: rustdesk
Issue: Windows compatibility issue
Labels: bug

All unreproducible Windows compatibility issues here.

### Unsolved

- [ ] https://github.com/rustdesk/rustdesk/issues/7341
- [ ] https://github.com/rustdesk/rustdesk/issues/6859
- [ ] https://github.com/rustdesk/rustdesk/issues/7355
- [ ] https://github.com/rustdesk/rustdesk/issues/7412
- [ ] https://github.com/rustdesk/rustdesk/issues/9159
Repository: go
Issue: x/arch/arm64: asm64.Decode() can not decode CASAL instruction
Labels: help wanted,NeedsInvestigation,arch-arm64

### Go version

go version go1.21.3 linux/arm64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN=''
GOCACHE='/home/tzx/.cache/go-build'
GOENV='/home/tzx/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/tzx/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/tzx/go'
GOPRIVATE=''
GOPROXY='https://goproxy.cn,direct'
GOROOT='/usr/local/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/go/pkg/tool/linux_arm64'
GOVCS=''
GOVERSION='go1.21.3'
GCCGO='gccgo'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build3822673542=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

a demo:
```go
package main

import (
	"sync/atomic"
)

func main() {
	a := atomic.Int32{}
	a.Store(1)
	a.CompareAndSwap(1, 4)
}
```

Try to use the arm64asm.Decode method to parse the elf file, the code is as follows:
```go
package main

import (
	"debug/elf"
	"fmt"
	"log"

	"golang.org/x/arch/arm64/arm64asm"
)

func main() {
	file, err := elf.Open("/home/tzx/test/casal/main")
	if err != nil {
		log.Fatal(err)
	}
	defer file.Close()

	for _, section := range file.Sections {
		if section.Flags&elf.SHF_EXECINSTR != 0 {
			data, err := section.Data()
			if err != nil {
				log.Fatal(err)
			}
			for pc := section.Addr; pc < section.Addr+section.Size; {
				instr, err := arm64asm.Decode(data[pc-section.Addr:])
				if err != nil {
					fmt.Printf("%#x: error data: ", pc)
					for i := len(data[pc-section.Addr:pc-section.Addr+4]) - 1; i >= 0; i-- {
						fmt.Printf("%02x", data[pc-section.Addr+uint64(i)])
					}
					fmt.Printf("\n")
				} else {
					fmt.Printf("%#x: %s\n", pc, instr)
				}
				pc += 4
			}
		}
	}
}

```


Use the objdump tool to output its assembly instructions, and the results are output to objdump.txt (left side of the picture)
Use `arm64asm.Decode()` to parse the elf compiled by the above demo, and the results are output to decode.txt (right side of the picture)

![bn3h75](https://github.com/golang/go/assets/67474179/d54f4514-67c2-46a3-b55c-79a48c00b41d)


### What did you see happen?

asm64.Decode() can not decode CASAL instruction.

The possible reason is that there is no description of the CASAL instruction in [table.go](https://cs.opensource.google/go/x/arch/+/master:arm64/arm64asm/tables.go)

### What did you expect to see?

In this demo, the output of objdump and arm64asm.Decode should be the same.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Adding ` "alwayson_scripts": {},` to /sdapi/v1/extra-single-image
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Hi and thank you for this awesome project!
I'm facing the problem with using extras tab with API
In fact - I want to use ReActor extension with API, but `/sdapi/v1/extra-single-image` haven't `"alwayson_scripts": {}` as option unlike txt2img and img2img.
Please add this option!

### Proposed workflow

1. Make API call
2. Nothing happens


### Additional information

_No response_
Repository: deno
Issue: `js_unit_test::{read_text_file_test, websocket_test}` are flaky
Labels: tests,flaky

```
[read_text_file_test 003.97] error: second time provided was later than self
thread 'js_unit_tests::read_text_file_test' panicked at tests/integration/js_unit_tests.rs:196:3:
assertion `left == right` failed: Deno should have exited cleanly
  left: Some(0)
 right: Some(1)
stack backtrace:
```
https://github.com/denoland/deno/actions/runs/8202276703/job/22432709852?pr=22794#step:39:3365
Repository: go
Issue: proposal: string: add HasAnyOfPrefixes, HasAnyOfSuffixes
Labels: Proposal

### Proposal Details
```
// HasAnyOfSuffixes returns an indication if the given string has any of the given suffixes.
func HasAnyOfSuffixes(input string, suffixes ...string) bool {
	for _, suffix := range suffixes {
		if HasSuffix(input, suffix) {
			return true
		}
	}

	return false
}

// HasAnyOfPrefixes returns an indication if the given string has any of the given prefixes.
func HasAnyOfPrefixes(input string, prefixes ...string) bool {
	for _, prefix := range prefixes {
		if HasPrefix(input, prefix) {
			return true
		}
	}

	return false
}
```