sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: opencv
Issue: undefined reference to `__aarch64_ldadd8_acq_rel - Opencv 4.9.0
Labels: bug,category: build/install,platform: android,platform: arm

### System Information

OpenCV version: 4.9.0
Operating System / Platform: Android
Compiler & compiler version: SDK 31

### Detailed description

I have an Android application running opencv c++ since version 4.5.5, until then I have always been able to add it to my CMakeLists.txt file successfully. Everything is fine with 4.5.5, 4.6.0, 4.7.0, 4.8.0. However, I tried to update to version 4.9.0 and got the following error:

undefined reference to `__aarch64_ldadd8_acq_rel

It has several error messages, I am uploading a .txt file with the error logs.

[erro_log.txt](https://github.com/opencv/opencv/files/13925301/erro_log.txt)




### Steps to reproduce

Follow my cmakelists.txt to reproduce:

```
cmake_minimum_required(VERSION 3.10.2)

project(native_facerec)

# opencv
set(OpenCV_STATIC ON)
set(OpenCV_DIR ${CMAKE_SOURCE_DIR}/../ios/Classes/OpenCV-android-sdk-4.9.0/sdk/native/jni/abi-${ANDROID_ABI})
set(ncnn_DIR ${CMAKE_SOURCE_DIR}/../ios/Classes/Ncnn-sdk/ncnn-android/${ANDROID_ABI}/lib/cmake/ncnn)

find_package (OpenCV REQUIRED)
find_package (ncnn REQUIRED)

include_directories(
    ../ios/Classes/ml_models/include
)

add_library(
    native_facerec
    SHARED
    ../ios/Classes/ml_models/src/main.cpp
    ../ios/Classes/ml_models/src/base64.cpp
    ../ios/Classes/ml_models/src/scanner.cpp
    ../ios/Classes/ml_models/src/MotionDetector.cpp
)
add_library(onnxruntime SHARED IMPORTED)
set_target_properties(onnxruntime PROPERTIES IMPORTED_LOCATION ${CMAKE_SOURCE_DIR}/../ios/Classes/onnxruntime-1.16.3/lib/${ANDROID_ABI}/libonnxruntime.so)
target_include_directories(native_facerec PRIVATE ${CMAKE_SOURCE_DIR}/../ios/Classes/onnxruntime-1.16.3/include/onnxruntime)

find_library(log-lib log)

target_compile_definitions(native_facerec PUBLIC USE_NCNN_SIMPLEOCV)

add_link_options(-fopenmp -s -ldl -lpthread)

target_link_libraries( # Specifies the target library.
    native_facerec
    ${OpenCV_LIBS}
    ${log-lib}
    ncnn
    onnxruntime
)


```

Works perfectly with other versions of opencv, this error only happens in v4.9.0.




### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: godot
Issue: Volumetric fog sporradically flooding the screen with black artifacts (Shader NaN + Reprojection?)
Labels: bug,topic:rendering,confirmed,topic:3d

### Tested versions

v4.2.1.stable.official [b09f793f5]
I lack a reliable reproduction case to test other versions currently.

### System information

Windows 10, v4.2.1, Vulkan, ForwardPlus, RTX3090 (31.0.15.3734)

### Issue description

While the video shows a more complicated scene, I encountered this bug sporadically all throughout my project.
I have not yet found a way to reproduce it. Some days the bug did not occur at all.
I observed it together with issue #74790 so it might be related or not.

- Vulkan, Forward Plus, TAA and FXAA enabled.
- I used a World environment with Volumetric fog turned on and density at 1.0
- Then I placed several overlapping FogVolumes with negative density, here -1.5, to "cut out" parts of the global fog
- At this point the issue #74790 started appearing as well as rarely the black artifacts described here
- The black artifacts can seemingly not be recovered from and will cover the viewport eventually

https://github.com/godotengine/godot/assets/22944373/2c8b5a4b-dd99-4a23-a08a-7aae6bbcfdaa

My guess is that it is a NaN being propagated by the temporal reprojection.

I will keep this post updated with any new findings and hopefully a reproduction case to do regression testing.

### Steps to reproduce

Moving trough the fog eventually causes the issue.
I have not yet found any way to reliably reproduce this.
It happens very randomly. Sometimes not at all for a whole evening.


### Minimal reproduction project (MRP)

As I said, I don't know how to reliably reproduce it, but here is a setup like mine.
[FogVolumeBug.zip](https://github.com/godotengine/godot/files/13925356/FogVolumeBug.zip)
Repository: pytorch
Issue: Memory leak while initializing tensors in child thread
Labels: module: cpu,module: memory usage,triaged

### 🐛 Describe the bug

Recently I noticed memory leak in my program and I've been managed to shrink it down to the following code.
```
import os
import sys
import time
from threading import Thread

import psutil
import torch


def foo(size):
    torch.zeros((1, size))


if __name__ == "__main__":
    track_proc = psutil.Process(os.getpid())
    mem_usage = 0
    while True:
        t = Thread(target=foo, args=(int(sys.argv[1]),))
        t.start()
        t.join()

        time.sleep(0.01)
        cur_mem_usage = track_proc.memory_full_info().uss / 1024**2
        mem_usage_diff = cur_mem_usage - mem_usage
        print(f"{cur_mem_usage=} MB, {mem_usage_diff=} MB")
        mem_usage = cur_mem_usage

```
And here comes something strange
```
$ python test_memory_leak.py 32768
cur_mem_usage=226.5546875 MB, mem_usage_diff=226.5546875 MB
cur_mem_usage=226.6796875 MB, mem_usage_diff=0.125 MB
cur_mem_usage=226.6796875 MB, mem_usage_diff=0.0 MB
cur_mem_usage=226.6796875 MB, mem_usage_diff=0.0 MB
cur_mem_usage=226.6796875 MB, mem_usage_diff=0.0 MB
cur_mem_usage=226.6796875 MB, mem_usage_diff=0.0 MB
cur_mem_usage=226.6796875 MB, mem_usage_diff=0.0 MB
cur_mem_usage=226.6796875 MB, mem_usage_diff=0.0 MB
cur_mem_usage=226.6796875 MB, mem_usage_diff=0.0 MB
...
```
```
$ python test_memory_leak.py 32769
cur_mem_usage=227.4453125 MB, mem_usage_diff=227.4453125 MB
cur_mem_usage=227.65625 MB, mem_usage_diff=0.2109375 MB
cur_mem_usage=227.8984375 MB, mem_usage_diff=0.2421875 MB
cur_mem_usage=228.109375 MB, mem_usage_diff=0.2109375 MB
cur_mem_usage=228.3515625 MB, mem_usage_diff=0.2421875 MB
cur_mem_usage=228.58203125 MB, mem_usage_diff=0.23046875 MB
cur_mem_usage=228.80859375 MB, mem_usage_diff=0.2265625 MB
cur_mem_usage=229.0234375 MB, mem_usage_diff=0.21484375 MB
cur_mem_usage=229.265625 MB, mem_usage_diff=0.2421875 MB
cur_mem_usage=229.48046875 MB, mem_usage_diff=0.21484375 MB
...
```
Any size greater than 32768(2**15) leads to a continuous growth of memory. (I've run it until my program crash so I'm pretty sure the consumption won't go down at some point.)

### Versions

My environment as below. However, I've run the test above on a few machines(different hardware, docker image, python version, pytorch version etc.) and most of the test ended with the same phenomenon. It does not seem like an issue of specific version. 
```
$ python -V && pip show torch
Python 3.10.13
Name: torch
Version: 2.0.1+cu118
Summary: Tensors and Dynamic neural networks in Python with strong GPU acceleration
Home-page: https://pytorch.org/
Author: PyTorch Team
Author-email: packages@pytorch.org
License: BSD-3
Location: /usr/local/lib/python3.10/dist-packages
Requires: filelock, jinja2, networkx, sympy, triton, typing-extensions
```

Any help or guidance is appreciated.

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10
Repository: deno
Issue: Relative import local npm package
Labels: bug,node compat,node resolution

Version: Deno 1.39.3

---

Importing relative, local npm package doesn't work under Deno using `deno.json` or `package.json`.

```js
// main.js

import 'my-lib';
```

```jsonc
// package.json
{
    "private": true,
    "type": "module",
    "dependencies": {
        "my-lib": "../.."
    }
}
```

## Deno

### Command

```bash
deno run main.js
```

### Output - error

```bash
error: Parsing version constraints in the application-level package.json is more strict at the moment.

Invalid specifier version requirement. Unexpected character.
  ../..
  ~
    at main.js:1:8
```

## Node.js

### Command

```bash
npm i && node main.js
```

### Output - no error

```bash
added 1 package, and audited 3 packages in 42ms

found ∞ vulnerabilities
```
Repository: godot
Issue: HTTPRequest get_body_size() returns -1 in HTML5
Labels: platform:web,topic:porting,documentation

### Tested versions

v3.5.3.stable.official [6c814135b]

### System information

MacOS Sonoma 14.1.2. 
Browser tested: Chrome, Firefox.

### Issue description

When calling the `HTTPRequest.get_body_size()` function, it returns -1 only in HTML5, while it works as expected in MacOS.

### Steps to reproduce

Call the function in `get_body_size()` while in HTML5.

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: [a11y] Circles on 24-hour time picker are too close together
Labels: framework,f: material design,a: accessibility,f: date/time picker,a: internationalization,has reproducible steps,P2,team-design,triaged-design,found in release: 3.16,found in release: 3.18

I reported an issue with the Cashew app - an app written in Flutter [here](https://github.com/jameskokoska/Cashew/issues/116). 

He said the problem was with Flutter so I moved here to find better support.

1. When the Android system displays in Vietnamese, French or Spanish - and 12-hour format is selected - the Cashew's (Flutter) time picker will always remain in 24-hour format, not switch to 12-hour format as desired. Does Flutter not support 12 hour format with those 3 languages?

2. Cashew's (Flutter) 24-hour time picker has two time circles picker. These two time circles picker are too close together, touching each other. I think the result is a lack of aesthetics and the ability to choose numbers incorrectly. Big fingers are more likely to pick the wrong number.

![](https://i.imgur.com/pzQALXU.png)

Caption: _10:00 touched 22:00 because they were too close to each other._

- Platform: Crdroid Android 13.
- Device: Sony Xperia 1.

=> I hope Flutter can support the 12-hour format for Vietnamese, French, and Spanish. As well as further spacing of the two numerical circles time picker to ensure ease of use and aesthetic symmetry!
Repository: react
Issue: Bug: [React Refresh] Unexpected behavior when adding/removing elements prior to uncontrolled inputs
Labels: Type: Bug,Component: Fast Refresh

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 18.2.0

## Steps To Reproduce


https://github.com/facebook/react/assets/54008264/94e69206-48a1-4064-a89c-583aadcd8269



1. https://stackblitz.com/edit/vitejs-vite-cswk6t?file=src%2FApp.tsx
2. Enter 1, 2, 3, and 4 respectively in each textbox
3. Comment and uncomment the `<br />` and save


```tsx
function App() {
  return (
    <>
      <div>
        {/* COMMENT AND UNCOMMENT THIS BR AND SAVE */}
        <br />
        <input type="text" />
        <input type="text" />
        <input type="text" />
        <input type="text" />
      </div>
    </>
  );
}

export default App;
```

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

https://stackblitz.com/edit/vitejs-vite-cswk6t?file=src%2FApp.tsx

## The current behavior

Uncontrolled inputs' values are not synced correctly. (I tested with controlled inputs, and it worked properly.)
I verified that this bug exists in Safari (Version 17.1 (19616.2.9.11.7)) and Chrome (120.0.6099.199).
Tried in both Vite and Next.js, so I'm fairly certain it's a react refresh issue.

```
"@vitejs/plugin-react": "^4.2.1",
"next": "^14.0.3",
```

## The expected behavior

Each input should keep its own value.
Repository: vscode
Issue: Xcode Style Minimap Table of Contents
Labels: feature-request,editor-minimap

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Recently, Xcode has made many advancements in its minimap department. One thing is the nice table of contents.  When you hover on any portion of code, it briefs you about what that portion is by giving a very nice blue bracket pair highlight on the minimap and a title of what that braces are enclosing at the left side of it:

<img width="300" src="https://github.com/microsoft/vscode/assets/2157285/5d245969-3393-406c-9379-25fcfd25c1e1">

Not to mention that it also provides the whole table of content if you wish:

<img width="452" alt="Screenshot 1402-10-23 at 11 33 37 AM" src="https://github.com/microsoft/vscode/assets/2157285/e98e45a9-6dda-4243-8856-52e7b4df881d">

This is honestly brilliant. The alternative in vscode is to use outlines which if you look are unclear and hard to read. (also, where's the fun in this?)

<img width="425" src="https://github.com/microsoft/vscode/assets/2157285/4760dc63-e40c-45b9-934d-430588a3b4b3">

vscode has previously adopted the sticky headers from xcode, so why not the awesome minimap? (I have also created #202402 about the other feature of minimap)
Repository: tauri
Issue: [bug] [macOs] Blank screen with default Tauri/Preact boilerplate
Labels: type: bug,platform: macOS,status: needs triage

### Describe the bug

Hey there,
I am getting started with Tauri, and I got an issue:
- I create the app using create-tauri-app or manually
- I run the `cargo tauri dev`
- I got a white screen:

<img width="870" alt="image" src="https://github.com/tauri-apps/tauri/assets/75880156/eaa57cad-bf26-4839-a061-afc7fd8173d8">

(the vite server is running fine)

Thanks for your help !

### Reproduction

Use the default vite Preact/tauri boilerplate on macos

### Expected behavior

_No response_

### Full `tauri info` output

```text
Tauri info:
[✔] Environment
    - OS: Mac OS 14.2.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (environment override by RUSTUP_TOOLCHAIN)
    - node: 18.0.0
    - pnpm: 8.8.0
    - npm: 8.6.0

[-] Packages
    - tauri [RUST]: 1.5.4
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.5
    - tauri-cli [RUST]: 1.5.9
    - @tauri-apps/api [NPM]: 1.5.3
    - @tauri-apps/cli [NPM]: 1.5.9

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite

webkit version: 19617.1.17.11.12
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: yt-dlp
Issue: How to set FLAC compression level?
Labels: enhancement,core:post-processor

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm asking a question and **not** reporting a bug or requesting a feature
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar questions **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Please make sure the question is worded well enough to be understood

Is it possible to set the compression level when using the --audio-quality flag in conjunction with the --extract-audio and --audio-format flag?

For example, would the following convert the extracted audio to FLAC with compression level of 8?
```--extract-audio --audio-format flac --audio-quality 8```

Thanks

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: next.js
Issue: <Link> component does not close dropdown menu on its click
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/pedantic-nova-ky649j

### To Reproduce

<img width="1437" alt="image" src="https://github.com/vercel/next.js/assets/65944426/e4e6ee66-3a34-40af-907f-5f2c09694058">


### Current vs. Expected behavior

Current behavior: Pure CSS Dropdown menu is not getting closed on menu item link click: <Link href='/whatever'>Click me</Link>
Expected behavior: Dropdown menu should get closed on <Link href='/whatever'>Click me</Link>

### Verify canary release

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

### Provide environment information

```bash
{
  "name": "test-app-router",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "next": "14.0.4",
    "react": "^18",
    "react-dom": "^18"
  },
  "devDependencies": {
    "@types/node": "^20",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "autoprefixer": "^10.0.1",
    "eslint": "^8",
    "eslint-config-next": "14.0.4",
    "postcss": "^8",
    "sass": "^1.69.7",
    "tailwindcss": "^3.3.0",
    "typescript": "^5"
  }
}
```


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

App Router

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

next build (local)

### Additional context

_No response_
Repository: pytorch
Issue: _register_state_dict_hook docstring is not accurate?
Labels: module: nn,triaged,topic: docs

### 📚 The doc issue

As seen in the code of [`_register_state_dict_hook()`](https://github.com/pytorch/pytorch/blob/main/torch/nn/modules/module.py#L1760), we can use this function to register hooks to modify `state_dict` before saving it to checkpoint files.

The docstring says: *The hooks may modify `state_dict` inplace or **return a new one***

However, from the code inside [`state_dict()`](https://github.com/pytorch/pytorch/blob/main/torch/nn/modules/module.py#L1895), returning a new one doesn't seem to be proper.

For example, `state_dict()` recursively calls `state_dict()` of all nested child modules, and suppose we want to apply a hook function to a child module and return a new `OrderedDict destination` (without modifying the passed-in `destination` inplace), then I think the new `destination` wouldn't have any impact to the final `state_dict` at all.

Because this [line of code](https://github.com/pytorch/pytorch/blob/main/torch/nn/modules/module.py#L1895) doesn't consider the return value of child module's`state_dict()` at all, so if inside a child module's `state_dict()`, `destination` is not modified inplace, but a new one is returned by a hook, and then that newly returned `destination` wouldn't be used.

### Suggest a potential alternative/fix

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: rust
Issue: panic branch does not get removed in presence of other function (that also does not get it removed)
Labels: A-LLVM,I-slow,T-compiler,C-bug,I-heavy

<!--
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 ([compiler explorer](https://godbolt.org/z/5468djrYa)):
```rust
#[derive(Clone, Copy)]
pub enum Enum {
    None,
    Variant1,
    Variant2,
}

impl Enum {
    #[no_mangle]
    pub fn as_str_1(self) -> &'static str {
        // switch table for reference
        match self {
            Self::None => "",
            Self::Variant1 => "1",
            Self::Variant2 => "2",
        }
    }

    #[no_mangle]
    pub fn as_str_2(self) -> &'static str {
        let len = (self as usize + 1) / 2;
        let offs = self as usize / 2;
        &"12"[offs..len + offs]
    }

    #[no_mangle]
    pub fn as_str_3(self) -> &'static str {
        let len = (self as usize + 1) / 2;
        let offs = self as usize;
        &" 12"[offs..len + offs]
    }
}
```

and this code ([compiler explorer](https://godbolt.org/z/xeM6rv149)):
```rust
#[derive(Clone, Copy)]
pub enum Enum {
    None,
    Variant1,
    Variant2,
}

impl Enum {
    #[no_mangle]
    pub fn as_str_1(self) -> &'static str {
        // switch table for reference
        match self {
            Self::None => "",
            Self::Variant1 => "1",
            Self::Variant2 => "2",
        }
    }

    #[no_mangle]
    pub fn as_str_2(self) -> &'static str {
        let len = (self as usize + 1) / 2;
        let offs = self as usize / 2;
        &"12"[offs..len + offs]
    }
}
```
(difference between the two is that `as_str_3` only exists in the first example)

I expected to see this happen:
all `as_str_` functions compile to roughly the same code (no memory accesses, just some pointer addition and getting the length right)

something like this ([compiler explorer](https://godbolt.org/z/vjxP4r7cM)):
```x86asm
as_str_4:
        movzx   edx, dil
        lea     rax, [rip + .L__unnamed_3]
        add     rax, rdx
        inc     edx
        shr     edx
        ret

.L__unnamed_3:
        .ascii  " 12"
```

Instead, this happened:
`as_str_1` became a switch table, so i pointed the compiler in the right direction with `as_str_2`, i tried a few other things, `as_str_3` with an integer division less but a byte longer string and `as_str_4` with unsafe code to get the desired output.
`as_str_2`'s panic branch *only* got removed when i commented `as_str_3` out, `as_str_3` always had one

### 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.77.0-nightly (62d7ed4a6 2024-01-11)
binary: rustc
commit-hash: 62d7ed4a6775c4490e493093ca98ef7c215b835b
commit-date: 2024-01-11
host: x86_64-unknown-linux-gnu
release: 1.77.0-nightly
LLVM version: 17.0.6
```