sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: `unreachable_patterns` fires on match arm that can't be removed.
Labels: A-lints,T-compiler,F-never_type,D-invalid-suggestion,L-unreachable_patterns

[playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=6178d0d0ebf5070b1cc2995575e38505)

```rust
use core::future::Future;

async fn select<A: Future, B: Future>(_: A, _: B) -> Result<A::Output, B::Output> {
    todo!()
}

pub async fn wtf() -> ! {
    let a = async { loop {} };
    let b = async { loop {} };
    match select(a, b).await {
        Ok(x) => x,
        Err(x) => x,
    }
}
```

warns with `unreachable_patterns` on both arms

```
warning: unreachable pattern
  --> src/lib.rs:11:9
   |
11 |         Ok(x) => x,
   |         ^^^^^
   |
   = note: this pattern matches no values because `Result<!, !>` is uninhabited
   = note: `#[warn(unreachable_patterns)]` on by default
```

but removing either doesn't actually compile

```
error[E0004]: non-exhaustive patterns: `Ok(_)` not covered
   --> src/lib.rs:10:11
    |
10  |     match select(a, b).await {
    |           ^^^^^^^^^^^^^^^^^^ pattern `Ok(_)` not covered
    |
note: `Result<(), !>` defined here
   --> /playground/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/result.rs:527:1
    |
527 | pub enum Result<T, E> {
    | ^^^^^^^^^^^^^^^^^^^^^
...
531 |     Ok(#[stable(feature = "rust1", since = "1.0.0")] T),
    |     -- not covered
    = note: the matched value is of type `Result<(), !>`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an explicit pattern as shown
    |
11  ~         Err(x) => x,
12  ~         Ok(_) => todo!(),
```

So this code seems "unfixable" with the new lint.

What's happening is the match arm is unreachable, but it still has the "side effect" of making the async block be inferred to `Future<Output=!>` instead of `Future<Output=()>`. So, if you remove it the future now gets inferred to return `()`, and the arm is not unreachable anymore.

In edition 2024 it Just Works if you write `match select(a, b).await {}`, because the fallback is `!` instead of `()`. 

This seems a bit hard to mitigate in Edition 2021, it seems more like an unfortunate combination of the lint and the inference fallback more than a bug. I'm opening the issue anyway to share it, just in case anyone has an idea.
Repository: tensorflow
Issue: Einsum optimization setting guidelines
Labels: stat:awaiting tensorflower,comp:ops,type:performance,TF 2.16

### Issue type

Performance

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

2.16

### Custom code

No

### OS platform and distribution

Linux Ubuntu 20

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

Existing tensorflow supports [einops](https://www.tensorflow.org/api_docs/python/tf/einsum), which enable seamless tensor reduction ops. Parameter to this functionality (kwarg) is the `optimize` parameter, i.e.
```
optimize: Optimization strategy to use to find contraction path using opt_einsum. Must be 'greedy', 'optimal', 'branch-2', 'branch-all' or 'auto'. (optional, default: 'greedy').
```

Is it documented somewhere what the use cases that benefit from these options are in practice?  Further, are effects of these expected to this library perhaps? https://optimized-einsum.readthedocs.io/en/stable/

Simple benchmarking doesn't really reveal any (significant?) differences. Thanks!

### Standalone code to reproduce the issue

```python
A simple benchmark of form:

import tensorflow as tf
import numpy as np
import time

# Define three large matrices A, B, and C of size 1000x1000
A = tf.random.uniform((1000, 1000), dtype=tf.float32)
B = tf.random.uniform((1000, 1000), dtype=tf.float32)
C = tf.random.uniform((1000, 1000), dtype=tf.float32)
D = tf.random.uniform((1000, 1000), dtype=tf.float32)
E = tf.random.uniform((1000, 1000), dtype=tf.float32)

greedy = []
non_greedy = []
for _ in range(1000):
    # Perform matrix multiplication using tf.einsum with optimize='greedy'
    start_time_greedy = time.time()
    result_greedy = tf.einsum('ij,jk,kl,lm,mn->in', A, B, C, D, E, optimize='greedy')
    end_time_greedy = time.time()

    # Perform matrix multiplication using tf.einsum with optimize='optimal'
    start_time_branch_all = time.time()
    result_branch_all = tf.einsum('ij,jk,kl,lm,mn->in', A, B, C, D, E, optimize='optimal')
    end_time_branch_all = time.time()

    # Print the execution times
    greedy.append(end_time_greedy - start_time_greedy)
    non_greedy.append(end_time_branch_all - start_time_branch_all)

print(f"Greedy time: {np.mean(greedy)}")
print(f"Optimal time: {np.mean(non_greedy)}")
```

### Relevant log output

```
Greedy time: 0.067701251745224
Optimal time: 0.06806995582580566
```
Repository: deno
Issue: npm:isolated-vm  is not supported
Labels: bug,node compat,triage required 👀

Version: Deno x.x.x

npm:isolated-vm 

Is the alternative to launch an isolate with:
new Worker?


```ts
// Create a new isolate limited to 128MB
import ivm from 'npm:isolated-vm';
const isolate = new ivm.Isolate({ memoryLimit: 128 });
```
raises
error: Uncaught (in promise) Error: Cannot find module './out/isolated_vm'
Require stack:



What is the best way to run a child that does not crash the main thread?
Repository: material-ui
Issue: [Badge] export default component for 'badge' slot
Labels: component: badge,customization: dom

### Summary

Would like to be able to use the `badge` slot on the badge component, so that I can wrap it with a `ButtonBase` and make it interactive. The badge exposes a slot for the "badge" component, but no way to reuse the default component.

Exporting the default component could potentially make sense for any slot that is offered.

### Examples


```tsx
import Badge, { BadgeSlot } from '@mui/material/badge'
import ButtonBase from '@mui/material/ButtonBase'

function MyBadge() {
  return <ButtonBase onClick={() => alert('hello word!')}><BadgeSlot {...props} /></ButtonBase>
}

<Badge 
  badgeContent="click me"
  slots={{
    badge: MyBadge
  }} 
>
  ...
</Badge>
```

### Motivation

_No response_

**Search keywords**: badge slot
Repository: go
Issue: cmd/go: telemetry data should not be in $XDG_CONFIG_HOME
Labels: NeedsDecision,GoCommand,telemetry

### Go version

go version go1.23.0 linux/amd64

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

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/andrew/.cache/go-build'
GOENV='/home/andrew/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS='-modcacherw'
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/andrew/.go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/andrew/.go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/opt/golang/go1.23.0'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/golang/go1.23.0/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.0'
GODEBUG=''
GOTELEMETRY='off'
GOTELEMETRYDIR='/home/andrew/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='0'
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 -m64 -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build2289507740=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

1. Upgrade to Go 1.23.0
2. Use Go for several days

### What did you see happen?

My `$XDG_CONFIG_HOME/go/telemetry` directory (`$HOME/.config/go/telemetry`) is now full of data files, in violation of the [XDG Base Directory Specification](https://specifications.freedesktop.org/basedir-spec/latest/index.html) which reserves `$XDG_CONFIG_HOME` for configuration.

### What did you expect to see?

I expected telemetry data to be stored in `$XDG_STATE_HOME` instead.
Repository: electron
Issue: [Bug]: Reopen from issue #40328. Multiple Electron Apps are affected,
Labels: platform/linux,bug :beetle:,32-x-y

### 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

32.0.0

### What operating system(s) are you using?

Other Linux

### Operating System Version

RHEL8 and Fedora

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior


In the recent months, several Electron Apps that I am using on Linux have started to report this error message on Linux (RHEL8):

Teams for Linux, reported here: https://github.com/IsmaelMartinez/teams-for-linux/issues/998
or
5898:ERROR:network_service_instance_impl.cc(663)] Network service crashed, restarting service.
Standard Notes, reported here: https://github.com/standardnotes/forum/issues/3312

This causes a delay of several seconds on startup. For teams on Linux, the App does not even work anymore.

### Actual Behavior


No error should be seen and the apps should work/start fine.

### Testcase Gist URL

_No response_

### Additional Information

RHEL8 and Fedora 37+ x86_64
Repository: electron
Issue: [Bug]: Context menu appears on the wrong workspace in GNOME when running ELECTRON_OZONE_PLATFORM_HINT=wayland
Labels: platform/linux,bug :beetle:,30-x-y,31-x-y

### 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

30.1.2, 31.3.0

### What operating system(s) are you using?

Other Linux

### Operating System Version

Arch Linux, Fedora 40

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

**Setup:** An Electron app (e.g. VSCode, Draw.io Desktop) is running under Linux in the GNOME desktop environment using Wayland. For the electron app the platform is explicitly set to Wayland (`ELECTRON_OZONE_PLATFORM_HINT=wayland`). Multiple windows of the application are open on different workspaces.

**Expected Behavior:** When opening the context menu in one of the Electron apps by an action (e.g. right-clicking with a mouse) the context menu should appear in the window (and on the workspace) where the action was performed. E.g. with windows A on workspace 1 and B on workspace 2, when right clicking in window A the context menu should appear in window A on workspace 1.

### Actual Behavior

The context menu triggered from a window on its respective workspace always appears in the most recently opened app window on its workspace. This makes it impossible to open the context menu in any other window than the most recently opened one.

### Testcase Gist URL

_No response_

### Additional Information

The issue does not occur with `ELECTRON_OZONE_PLATFORM_HINT=x11`. Tested with GNOME both on Arch Linux and Fedora 40. Issue happens with VSCode installed through the method described on [code.visualstudio.com](https://code.visualstudio.com/docs/setup/linux#_rhel-fedora-and-centos-based-distributions) through Flatpak, and the AUR (Electron Version 30.1.2). It also happens with the Draw.io Desktop app (Electron 31.3.0).

I suspect that there are different implementations of context menus in Electron apps, since this issue always happens in VSCode but in e.g. Draw.io it only happens with the 'native-looking' context menu triggered when right-clicking e.g. on the menu bar and not for the context menu triggered inside the drawing area.
Repository: godot
Issue: Migration to Parallax 2D node could update the attach script during migration
Labels: enhancement,discussion,topic:editor,topic:2d

### Tested versions

- v4.3.stable.steam [77dcf97d8]

### System information

Windows 11, v4.3.stable.steam [77dcf97d8]

### Issue description

After using the migration button from ParallaxBackground to Paralax2D Node, Attached script should extend to new node Paralax2D in the script linked to the node.

This script for example was attach to a ParallaxLayer Object
```gdscript
extends ParallaxLayer

func _ready():
	for child in get_children():
		child.scale.y = 0;

func entering_battle():
	for child in get_children():
		var tween = get_tree().create_tween()
		tween.tween_property(child, "scale",Vector2(1,1),1.0)
			
func exiting_battle():
	for child in get_children():
		var tween = get_tree().create_tween()
		tween.tween_property(child, "scale",Vector2(1,0),1.0)
```

After using the migration tool the script should look like this
```gdscript
extends Parallax2D

func _ready():
	for child in get_children():
		child.scale.y = 0;

func entering_battle():
	for child in get_children():
		var tween = get_tree().create_tween()
		tween.tween_property(child, "scale",Vector2(1,1),1.0)
			
func exiting_battle():
	for child in get_children():
		var tween = get_tree().create_tween()
		tween.tween_property(child, "scale",Vector2(1,0),1.0)
```


### Steps to reproduce

Start a project with a ParallaxBackground node, then add a ParallaxLayer node, then attach a script to the layer.
Your now ready to use the migration tool. Use it you'll see that the extends of the script isn't updated to the new node type witch is now a Parallax2D node

### Minimal reproduction project (MRP)

[migrationissue.zip](https://github.com/user-attachments/files/16693014/migrationissue.zip)
Repository: vscode
Issue: GitHub Extension: Unable to resolve nonexistent file error when using GitHub in vscode.dev
Labels: bug,github-repositories

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.92.2 (VS Code for web running on vscode.dev)
- OS Version: macOS 12.4

Steps to Reproduce:

1. Open a GitHub repo in vscode.dev, e.g. https://vscode.dev/github/microsoft/vscode
2. Create a new folder in the root containing another folder e.g. `tmp/temp`

<img width="696" alt="Screenshot 2024-08-21 at 15 33 30" src="https://github.com/user-attachments/assets/df00c25c-2678-4cea-87fc-761a3a4692fe">

3. Delete this folder tree using the context menu

<img width="697" alt="Screenshot 2024-08-21 at 15 33 42" src="https://github.com/user-attachments/assets/2507499a-d7e7-4a29-8f74-4fe08659ca1a">

4. Try to recreate the `tmp` base folder again

<img width="692" alt="Screenshot 2024-08-21 at 15 34 05" src="https://github.com/user-attachments/assets/2f81626a-7c80-4bce-882a-818d42476e93">

5. Error received: `Unable to resolve nonexistent file 'vscode-vfs://github/microsoft/vscode/tmp'`

<img width="480" alt="Screenshot 2024-08-21 at 15 34 13" src="https://github.com/user-attachments/assets/4fe78943-1faa-4c5c-8b8a-97337f67e433">
Repository: storybook
Issue: [Bug]: error Unable to resolve module storybook/internal/preview-api
Labels: bug,dependencies,react-native,has workaround

### Describe the bug

cannot run react-native with latests versions



```
error Unable to resolve module storybook/internal/preview-api from /Users/alain/myproject/node_modules/@storybook/addon-actions/dist/preview.js: storybook/internal/preview-api could not be found within the project or in these directories:
  node_modules
  2 |
  3 | var uuid = require('uuid');
> 4 | var previewApi = require('storybook/internal/preview-api');
    |                           ^
  5 | var global = require('@storybook/global');
  6 | var previewErrors = require('storybook/internal/preview-errors');
  7 |.
  
  
```


versions used 

```
"react-native": "0.74.3",
"@storybook/addon-actions": "^8.2.9",
"@storybook/addon-ondevice-actions": "^7.6.20",
"@storybook/addon-ondevice-controls": "^7.6.20",
"@storybook/addon-themes": "^8.2.9",
"@storybook/preview-api": "^8.2.9",
"@storybook/react": "^8.2.9",
"@storybook/react-native": "^7.6.20",
"@storybook/react-native-theming": "^7.6.20",
```


project was running with this previous following versions but storybook stopped working few month ago since i udpate react-native itself. it stuck on splascreen most of the time

```
  "@storybook/addon-actions": "^7.6.17",
  "@storybook/addon-ondevice-actions": "^7.6.15",
  "@storybook/addon-ondevice-controls": "^7.6.15",
  "@storybook/addon-themes": "^7.6.17",
  "@storybook/react": "^7.6.17",
  "@storybook/react-native": "^7.6.15",
  "@storybook/react-native-theming": "^7.6.15",
  ```

### Reproduction link

nolink.com

### Reproduction steps

just try to run project

### System

```bash
System:
    OS: macOS 14.6.1
    CPU: (10) arm64 Apple M2 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.6.0 - /opt/homebrew/bin/node
    Yarn: 4.2.1 - /usr/local/bin/yarn <----- active
    npm: 10.8.2 - /opt/homebrew/bin/npm
  Browsers:
    Chrome: 127.0.6533.120
    Safari: 17.6
  npmPackages:
    @storybook/addon-actions: ^8.2.9 => 8.2.9
    @storybook/addon-ondevice-actions: ^7.6.20 => 7.6.20
    @storybook/addon-ondevice-controls: ^7.6.20 => 7.6.20
    @storybook/addon-themes: ^8.2.9 => 8.2.9
    @storybook/preview-api: ^8.2.9 => 8.2.9
    @storybook/react: ^8.2.9 => 8.2.9
    @storybook/react-native: ^7.6.20 => 7.6.20
    @storybook/react-native-theming: ^7.6.20 => 7.6.20
```


### Additional context

_No response_
Repository: PowerToys
Issue: Add force close option to powertoys run 
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

when running powertoys run to find applications currently there is 4 icons 1. run as an admin 2. run as another user 3. open folder 4. copy path in console
the request is to add another icon to force close the application 

### Scenario when this would be used?

inset of opening task manager navigate to desired application right click and select end task just having a kill switch in run will make it much easier to do 

### Supporting information

_No response_
Repository: material-ui
Issue: [Collapse] Support anchoring content to the bottom/right
Labels: component: Collapse,package: material-ui,v6.x,enhancement

### Summary

Would like to be able to anchor the collapsed content to the bottom of to container. The effect can be achieved by adding following styles to the `Collapse` but it would be nice to have a prop that can handle this:
```tsx
sx={{
  display: "flex",
  flexDirection: "column-reverse",
}}
```
Perhaps the `direction` prop can even be expanded to account for this use-case. If not accepted, perhaps this use-case could be added to the docs?

### Examples

Here's a codesandbox that displays the desired behavior: https://codesandbox.io/p/sandbox/lucid-heyrovsky-wrjrnp?file=%2Fsrc%2FDemo.tsx%3A47%2C45


https://github.com/user-attachments/assets/9e8f89dc-5d60-4ee6-80f0-ddd286fe6a8a



### Motivation

I struggled a bit with this when building Toolpad component catalog, which feels better when it looks like the drawer is pulled from under the left edge, rather than it being already in place and revealed gradually. Now I'm running into it again with another component.


https://github.com/user-attachments/assets/0398c9c8-7fb3-42df-a94f-ecd53b223b31

vs.

https://github.com/user-attachments/assets/5aa03937-8810-4541-b021-af2caea3d114



**Search keywords**: collapse reverse
Repository: kubernetes
Issue: Unstructured Extract should use OpenAPI V3 instead of OpenAPI V2
Labels: sig/api-machinery,triage/accepted

https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/applyconfigurations/meta/v1/unstructured.go#L59 should fetch from OpenAPI V3 rather than V2.
Repository: rust
Issue: Error message suggests to use a Box to wrap dyn Trait when it's unnecessary
Labels: A-diagnostics,T-compiler

### Code

```Rust
use std::io::Write;

fn foo(f: Option<&mut dyn Write>) {
    if let Some(f) = f {
        writeln!(f, "Hello").unwrap();
    }
}

fn bar() {
    let mut out = Some(std::io::stdout());
    foo(out.as_mut());
}
```


### Current output

```Shell
error[E0308]: mismatched types
  --> src/lib.rs:11:9
   |
11 |     foo(out.as_mut());
   |     --- ^^^^^^^^^^^^ expected `Option<&mut dyn Write>`, found `Option<&mut Stdout>`
   |     |
   |     arguments to this function are incorrect
   |
   = note: expected enum `Option<&mut dyn std::io::Write>`
              found enum `Option<&mut Stdout>`
   = help: `Stdout` implements `Write` so you could box the found value and coerce it to the trait object `Box<dyn Write>`, you will have to change the expected type as well
note: function defined here
  --> src/lib.rs:3:4
   |
3  | fn foo(f: Option<&mut dyn Write>) {
   |    ^^^ -------------------------
```


### Desired output

```Shell
= help: `Stdout` implements `Write` so you could make a reference to the found value and coerce it to the trait object `&mut dyn Write` or `Box<&dyn Write>`, you will have to change the expected type as well
```


### Rationale and extra context

I can make it compile without using a Box.

```rust
fn bar() {
    let mut out = Some(std::io::stdout());
    foo(out.as_mut().map(|p| p as &mut dyn Write));
}
```

I don't think error message should suggest to use a Box when it's not necessary.

Also maybe it's just me but I'm not quite sure what `you will have to change the expected type as well` means.

### Other cases

_No response_

### Rust Version

```Shell
$ rustc --version --verbose
rustc 1.80.1 (3f5fd8dd4 2024-08-06)
binary: rustc
commit-hash: 3f5fd8dd41153bc5fdca9427e9e05be2c767ba23
commit-date: 2024-08-06
host: x86_64-unknown-linux-gnu
release: 1.80.1
```


### Anything else?

_No response_
Repository: ui
Issue: "[Bug]: Issue with textarea blur when content is scrollable in Dialog Box"
Labels: bug

### Describe the bug

This issue arises when a textarea is placed inside a ShadCN dialog box. When the content within the textarea becomes scrollable, due to overflow, and a blur effect is applied to text

### Affected component/components

Textarea

### How to reproduce

![image](https://github.com/user-attachments/assets/c3e654c8-a563-48a2-b82a-6418db0e7a54)


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Windows 10 Pro
Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz   2.81 GHz

Google Chrome
Version 127.0.6533.120 (Official Build) (64-bit)
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues