sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: possible miscompilation on aarch64
Labels: O-macos,T-compiler,O-AArch64,A-linkers,C-external-bug

<!--
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.
-->

this code runs to completion when executed with miri or on x86, but segfaults on aarch64 in release builds

```toml
[package]
name = "faer-aarch64-bug"
version = "0.1.0"
edition = "2021"

[dependencies]
dyn-stack = "0.10.0"
faer-core = "0.14.1"
faer-svd = "0.14.1"
pulp = "0.17.1"
gemm = "0.16.14"
rand = "0.8.5"

[profile.release]
codegen-units=1
```

```rust
use dyn_stack::PodStack;
use faer_core::Mat;
use faer_svd::compute_svd;
use rand::{Rng, SeedableRng};

fn main() {
    let nrows = 5;
    let ncols = 5;
    let size = Ord::min(nrows, ncols);

    let mut gen = rand::rngs::StdRng::seed_from_u64(0);
    for _ in 0..10 {
        let m = Mat::from_fn(nrows, ncols, |_, _| {
            gen.gen::<f64>()
        });
        let mut s = Mat::<f64>::zeros(size, 1);
        let mut u = Mat::<f64>::zeros(nrows, nrows);
        let mut v = Mat::<f64>::zeros(ncols, ncols);

        compute_svd(
            m.as_ref(),
            s.as_mut(),
            Some(u.as_mut()),
            Some(v.as_mut()),
            faer_core::Parallelism::None,
            PodStack::new(&mut vec![0u8; 1024 * 1024]),
            Default::default(),
        );
    }
}
```

i tried isolating the issue but it's very elusive, and randomly disappears as different functions get inlined or noinlined, so the best i have is this example here

### 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.75.0-nightly (1c05d50c8 2023-10-21)
binary: rustc
commit-hash: 1c05d50c8403c56d9a8b6fb871f15aaa26fb5d07
commit-date: 2023-10-21
host: aarch64-apple-darwin
release: 1.75.0-nightly
LLVM version: 17.0.3
```
Repository: transformers
Issue: Add Model Support for xLSTM
Labels: New model

### Model description

Inspired by [recent rumors](https://www.youtube.com/watch?v=hwIt7ezy6t8) about xLSTM - a hidden successor to LSTM - by Sepp Hochreiter, this issue tracks the open source implementation about adding xLSTM to Transformers library.

### Open source status

- [x] The model implementation is available [here](https://github.com/NX-AI/xlstm) and [here](https://github.com/NX-AI/xlstm-jax) as JAX implementation
- [x] Transformers integration is currently available on their [Transformers fork](https://github.com/NX-AI/transformers/tree/integrate_xlstm) 
- [x] The model weights are available [here](https://huggingface.co/NX-AI/xLSTM-7b) (7B model)

### Provide useful links for the implementation

- [x] Paper is available [here](https://arxiv.org/abs/2405.04517)

At the moment no implementation does exist.

Only rumors that xLSTM surpasses GPT-2 on various (small) downstream datasets.

Good overview is the [xLSTM Resources](https://github.com/AI-Guru/xlstm-resources) repository from @AI-Guru.
Repository: rust
Issue: Tracking Issue for `gen` blocks and functions
Labels: B-RFC-approved,C-tracking-issue,F-gen_blocks

This is a tracking issue for the RFC "#3513" (rust-lang/rfcs#3513).
The feature gate for the issue is `#![feature(gen_blocks)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [x] Implement the RFC (happening in https://github.com/rust-lang/rust/pull/116447)
- [ ] Lots of diagnostics work
- [x] Make the `Iterator`s fused (so they keep returning `None` after the first `None` instead of panicking (which is what they do now))
- [x] implement `FusedIterator` - https://github.com/rust-lang/rust/pull/122829
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Formatting for new syntax has been added to the [Style Guide] ([nightly-style-procedure])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md 
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions

- [ ] Whether to implement `Iterator` directly or, e.g., `IntoIterator` or `IntoGenerator`.
- [ ] Whether to do what is needed for self-referential `gen` blocks prior to stabilization.
- [ ] Whether we should use some keyword other than `gen`.
    - https://github.com/rust-lang/rust/issues/123731
- [x] Whether we should reserve `gen` as a full keyword or as a contextual one.
- [ ] Whether we should opportunistically implement `size_hint`.
- [ ] Whether we should implement other traits such as `DoubleEndedIterator` or `ExactSizeIterator`.
- [ ] What to do about Rust 2015 and Rust 2018 where `k#gen` may or may not be workable.

### Related issues

* https://github.com/rust-lang/rust/issues/117486

### Implementation history

* https://github.com/rust-lang/rust/pull/116447
* https://github.com/rust-lang/rust/pull/118457
* https://github.com/rust-random/rand/issues/1435 (thanks @PatchMixolydic for talking with `rand` folks!)
Repository: godot
Issue: Handling of quotes within arguments in OS.execute()
Labels: bug,discussion,topic:core,confirmed

### Godot version

v4.1.2.stable.arch_linux

### System information

Arch Linux

### Issue description

When calling
```gdscript
OS.execute("./test.sh", ["foo \" \" bar"], output)
```
I would have expected this to be passed:
```
"foo \" \" bar"
```
But instead, this gets passed
```
"foo " " bar"
```

Having an odd number of quotes in your string may break something completely.

This can lead to dangerous unexpected behaviour, especially when user input is involved.

### Steps to reproduce

1. Have executable for testing ready such as this:
```sh
#!/bin/bash
echo $(IFS=,; echo "$*")
```
2. Create Project with a script such as this:
```gdscript
extends Node2D

func _ready():
	var output := []
	print("Expected output: foo \\\" \\\" bar")
	OS.execute("./test.sh", ["foo \" \" bar"], output)
	print(output)
	
	output = []
	print("Expected output: foo \\\"")
	OS.execute("./test.sh", ["foo \""], output)
	print(output)
```
3. Run it:
```
Expected output: foo \" \" bar
["foo , bar\n"]
Expected output: foo \"
[""]
```

### Minimal reproduction project

[mrp.zip](https://github.com/godotengine/godot/files/13068914/mrp.zip)

### TL;DR
https://github.com/godotengine/godot/assets/90388353/64f65d02-ffd6-4dc3-a15a-64f916bd19ac
Repository: next.js
Issue: React.Profiler onRender never gets called at SSR
Labels: bug,Runtime

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/pedantic-sea-jf78pq

### To Reproduce

1. Start the app, 
2. open index page


### Current vs. Expected behavior

Actual result:
- Observe 'onRender call' console message in the browser log
- Observe there's no 'onRender call' console message in the server log

Expected result:
- Observe 'onRender call' console message in the browser log
- Observe 'onRender call' console message in the server log

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 20.3.1
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 13.5.7-canary.16
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


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

Not sure, Middleware / Edge (API routes, runtime)

### Additional context

I want to use `<Profiler onRender={...}>` as the means to measure the time spent on specifically rendering components at SSR, as opposed to the time spent on preparing the data in `getInitialData` or `getStaticProps`, as that would greatly help me to pinpoint and track progress on particular issues with SSR.

The only "official" way to achieve that I managed to find was to use `React.Profiler`, but it does not seem to work in the SSR context.
Repository: Python
Issue: Nested functions can't be tested by doctest 
Labels: enhancement

### Feature description

#9943 

So I was adding doctests to a nested function in fibonacci.py, however doctest doesn't seem to be testing that function. 

The function in this case is fib_recursive_term(), that's nested inside fib_recursive, as seen below:
![image](https://github.com/TheAlgorithms/Python/assets/75509362/1f7c9f37-eae7-400e-a26d-6f8ab4da5c76)
Note: the 5 doctests for fib_recursive_term() is what I added. 

If I run the doctests, I get this output below.
As per the output below, 5 tests for fib_recursive() runs, but the 5 tests for fib_recursive_term() doesn't.
![image](https://github.com/TheAlgorithms/Python/assets/75509362/4f60d09c-ac09-4202-8e14-294a3b947cce)

So I want to propose taking the fib_recursive_term() function out of the fib_recursive() function and have it defined above it, so doctests actually goes through it. Would there be any issues there?
Repository: godot
Issue: wrong script reference after duplicate .tscn file
Labels: discussion,topic:editor,usability

### Godot version

4.1.2

### System information

Mobile

### Issue description

I copy and duplicate a folder with a .tscn inside to a different folder. Now all scenes with scripts inside do not have the reference to the scripts in the new folder but still of the old.

### Steps to reproduce

1. create a folder (A) with a scene and attach a script to it in the same folder.
2. Move / duplicate to a new folder (B)
3. Open the scene in the new folder (B) and look at the reference of the script. 

The script in the scene of folder B is not linked to the newly created script in folder B as I would expect. Instead it is linked to the script in folder A.

### Minimal reproduction project

start a new project. add a folder with a scene and add a script to the scene. Now duplicate the folder.
Repository: three.js
Issue: Documentation for add-on content
Labels: Documentation

### Description

Hello, Three.js community,

I'd like to request your input and guidance on the addition of documentation for addon features under the path: `three/examples/jsm/`. I noticed that most of the add-on stuff isn't documented. 


### Solution

Perhaps I can create a fork and get started on the documentation and others can pitch in? I believe that having comprehensive documentation for these feature would be a valuable addition to the Three.js docs.

Also, before I begin the documentation process, I wanted to confirm if anyone in the community is already working on documenting this feature or if there are existing open pull requests related to it. I'd like to avoid duplicating efforts. If there are specific guidelines, formatting requirements, or style preferences for contributing to the Three.js documentation, please let me know. I want to ensure that the documentation aligns seamlessly with the official documentation.
Repository: go
Issue: cmd/compile: some case can be inlined before unified ir(go1.19-), but can't be inilned after unified ir(go1.20+) 
Labels: NeedsInvestigation,compiler/runtime

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
devel go1.22-126db88cc8 Fri Oct 20 16:12:52 2023 +0800
</pre>

### Does this issue reproduce with the latest release?
```go
// a.go
package a

type A struct {
}

func (*A) Print() {
}
```

```go
// b.go
package b

import "./a"

var B *a.A
}
```

```go
// main.go
package main

import "./b"

func main() {
	b.B.Print()
}
```


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

GO111MODULE='on'
GOARCH='amd64'
GOBIN=''
GOCACHE='/Users/bytedance/Library/Caches/go-build'
GOENV='/Users/bytedance/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/bytedance/gopackage/pkg/mod'
GONOPROXY='*.byted.org,*.everphoto.cn,git.smartisan.com'
GONOSUMDB='*.byted.org,*.everphoto.cn,git.smartisan.com'
GOOS='darwin'
GOPATH='/Users/bytedance/gopackage'
GOPRIVATE='*.byted.org,*.everphoto.cn,git.smartisan.com'
GOPROXY='https://goproxy.byted.org|https://goproxy.cn|direct'
GOROOT='/Users/bytedance/go_google'
GOSUMDB=''
GOTMPDIR=''
GOTOOLCHAIN=''
GOTOOLDIR='/Users/bytedance/go_google/pkg/tool/darwin_amd64'
GOVCS=''
GOVERSION='devel go1.22-126db88cc8 Fri Oct 20 16:12:52 2023 +0800'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
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 -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/b1/0fd1b6hs7lz0fm_mh346lybm0000gn/T/go-build831658170=/tmp/go-build -gno-record-gcc-switches -fno-common'

</pre></details>

### What did you do?
```shell
go build -gcflags="-m"
```
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->



### What did you expect to see?
```shell
./main.go:5:6: can inline main
./main.go:6:11: inlining call to a.(*A).Print
```


### What did you see instead?
```shell
./main.go:5:6: can inline main
```
Repository: godot
Issue: Lag Spikes when moving CharacterBody2D through large TileMap2D with collision
Labels: bug,confirmed,topic:physics,topic:2d,performance

### Godot version

v4.1.stable.official [970459615]

### System information

Godot v4.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1080 (NVIDIA; 31.0.15.3699) - Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 Threads)

### Issue description

After some testing, I found that if you change the global_position of a CharacterBody2D object, it will cause quite a lag spike if there is a TileMap2D with lots of tiles between its original position and the target position. 

### Steps to reproduce

Move a CharacterBody2D object with the global_position attribute between two positions with a TileMap between them.

### Minimal reproduction project

[CharacterBody2D Bug.zip](https://github.com/godotengine/godot/files/13070023/CharacterBody2D.Bug.zip)

In this project the CharacterBody2D moves from 0, 0 to 2000, 2000. In between is a TileMap and some simple collisions. The lag spikes are clearly visible in the debugger
Repository: node
Issue: npm spining in recvfrom() when run on s390x via qemu
Labels: s390

### Version

v18.18.2

### Platform

Linux c8fdac6bf542 6.4.15-200.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep  7 00:25:01 UTC 2023 s390x Linux

### Subsystem

_No response_

### What steps will reproduce the bug?

```
docker run --platform linux/s390x -it --cap-add=SYS_PTRACE -e QEMU_STRACE=true -e QEMU_LOG_FILENAME=qemu.log -v ./qemu.log:/qemu.log --rm node:18-alpine npm install node-red@3.1.0
```

### How often does it reproduce? Is there a required condition?

Every time

### What is the expected behavior? Why is that the expected behavior?

npm to complete run on emulated s390x as this is the standard way to build s390x containers when no access to s390x hardware.

### What do you see instead?

Hang and 100% cpu from the npm process

### Additional information

See https://github.com/nodejs/docker-node/issues/1973 for qemu strace output
Repository: go
Issue: proposal: net/http: Make parsePostForm public
Labels: Proposal

Currently, `parsePostForm` is private. It is called only from `ParseForm` and one cannot call manually. This means that if one wants to call it on a non-standard HTTP method (not `POST`, `PUT`, `PATCH`) you have to temporary change method, then call `ParseForm` and then return it back. Or if you want to parse just post form and ignore any query string parameters. Currently you cannot ignore string parameters (you have to set `RawQueryString` to `""` currently). In my case, I want to parse query string and post form separately because I want o log parsed query string but not post form (the latter might have sensitive data).

I think code could be something like:

```go
func (r *Request) ParsePostForm() error {
	var err error
	if r.PostForm == nil {
		r.PostForm, err = parsePostForm(r)
		if r.PostForm == nil {
			r.PostForm = make(url.Values)
		}
	}
	return err
}
```

```go
func (r *Request) ParseForm() error {
	var err error
	if r.PostForm == nil {
		if r.Method == "POST" || r.Method == "PUT" || r.Method == "PATCH" {
			err = r.ParsePostForm()
		}
		if r.PostForm == nil {
			r.PostForm = make(url.Values)
		}
	}
	...
}
```
Repository: go
Issue: proposal: cmd/vet: warn on unused AppendFormat return value
Labels: Proposal

Currently the compiler will throw an error if the return value of `append` is not used, but it does not error or even warn if the return value of `time.AppendFormat` is not used, even though `AppendFormat` has the same semantics as `append`.

https://go.dev/play/p/IpxJrcX3FkT

If someone calls AppendFormat without using the return value, that is always an error, because it does nothing. 

I looked for linters that would catch this issue and could not find any.

EDIT: I tried to add it to  `go vet` `unusedresult` but I couldn't get it to work...is it that `unusedresult` still only works for pure functions as stated in https://github.com/golang/go/issues/14972  ?
Repository: rust
Issue: Forward the LLVM's Error Messages When Trying to Load a Plugin
Labels: A-LLVM,A-diagnostics,T-compiler,D-terse

### Code

```Rust
n/a (reproducible when loading an invalid LLVM plugin)
```


### Current output

```Shell
cargo build
   Compiling shared v0.1.0 (/home/test/plugin-test)                                            
   Compiling main-two v0.1.0 (/home/test/plugin-test/main-two)
error: failed to run LLVM passes: Failed to load pass plugin//home/test/plugin-test/libHello.so

error: could not compile `main-two` due to previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `shared` due to previous error
```


### Desired output

```Shell
cargo build
   Compiling shared v0.1.0 (/home/test/plugin-test)                                            
   Compiling main-two v0.1.0 (/home/test/plugin-test/main-two)
error: failed to run LLVM passes: Failed to load pass plugin//home/test/plugin-test/libHello.so

/usr/bin/rustc: symbol lookup error: /home/test/.rustup/toolchains/nightly-2023-03-04-x86_64-unknown-linux-gnu/lib/librustc_driver-a2afcd5e45f6bea2.so: undefined symbol: _ZN4llvm24DisableABIBreakingChecksE, version LLVM_15
/usr/bin/rustc: symbol lookup error: /home/test/.rustup/toolchains/nightly-2023-03-04-x86_64-unknown-linux-gnu/lib/librustc_driver-a2afcd5e45f6bea2.so: undefined symbol: _ZN4llvm24DisableABIBreakingChecksE, version LLVM_15

error: could not compile `main-two` due to previous error
warning: build failed, waiting for other jobs to finish...
error: could not compile `shared` due to previous error
```


### Rationale and extra context

The current error log when loading a LLVM plugin does not give much information what the error might me.

In the code, every error returned by PassPlugin::Load is wrapped and returned as a single value [1]. This makes it incredibly hard to understand the issue without adding some debugging statements and recompiling `libLLVM` or `librustc_driver`.

Instead of wrapping the error and returning a generic error message for all errors, I propose that the error message created by the LLVM is printed, allowing an easier way to debug issues with a LLVM plugin.

[1] https://github.com/rust-lang/rust/blob/655a810b665053ebef1739a3b662b79d232d75f4/compiler/rustc_llvm/llvm-wrapper/PassWrapper.cpp#L792-L796

### Other cases

_No response_

### Anything else?

_No response_
Repository: rust
Issue: nightly 2023-10-22 missing
Labels: T-infra,C-bug

latest available nightly for me seems to be `nightly-x86_64-unknown-linux-gnu unchanged - rustc 1.75.0-nightly (1c05d50c8 2023-10-21)`, looks like  `2023-10-22`which should have been released ~14-17 hours ago is somehow missing?
Repository: opencv
Issue: STMAP exporter
Labels: feature

### Describe the feature and motivation

STmaps[1][2] are quite popular in many pipelines but it seems hard to replicate what it is expected to be processed by other software like Natron, Blender, Nuke, etc.
It seems that exporting it with `initUndistortRectifyMap` it will not have the same effect in these software as OpenCV `initUndistortRectifyMap` + `remap` also using the same interpolation and datatype precision. 

It is going always to have substantial visual difference. 

[1]https://benmcewan.com/blog/2020/02/02/demystifying-st-maps/
[²]https://natron.readthedocs.io/en/rb-2.5/plugins/net.sf.openfx.STMap.html

### Additional context

It could be partially connected to https://github.com/opencv/opencv/issues/22120 as we need a direct mapping and not the inverse one expected by `remap`
Repository: create-react-app
Issue: Deployment should respect Windows environment
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

Executing `npm run build` should respect `$env:NODE_ENV = "development"` and reference values in `.env.development` instead of `.env.production`.

### Describe the solution you'd like

Overriding `.env.production` with `.env.development` values. Yuck!

### Describe alternatives you've considered

N/A

### Additional context

For: https://create-react-app.dev/docs/deployment

Change request:
```dif
-Variables in .env.production will be used as fallback because NODE_ENV will always be set to production for a build.+
+Deployment should respect the NODE_ENV variable
```