sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: GradientTexture1D/2D changed signal emitted before texture updating which causes issue in certain case
Labels: bug,topic:core

### Tested versions

Reproducible in 4.4.dev

### System information

Linux - Godot 4.4.dev

### Issue description

GradientTexture2D/1D emit changed signal before its texture actually updates, which causes issues in certain case that can't update texture by listen its changed signal. The issue was found in #102028.

### Steps to reproduce

The issue occurs if you draw gradient texture in a viewport and only update once.

Attach the follow script to a Node2D, assign a GradientTexture2D/GradientTexture1D to the texture property, then the texture display incorrectly and doesn't update after changing its gradient, unless reload the scene. Instead, assigning a NoiseTexture2D to the texture works well.
```gdscript
@tool
extends Node2D
class_name TestNode2D

@export var texture: Texture2D:
	set(value):
		if texture != null:
			texture.changed.disconnect(queue_redraw)
		texture = value
		if texture != null:
			texture.changed.connect(queue_redraw)
		queue_redraw()
@export var bg_color: Color = Color.WHITE:
	set(value):
		bg_color = value
		queue_redraw()

var size: Vector2i = Vector2i(512, 512)
var vp: RID = RenderingServer.viewport_create()
var vp_canvas: RID = RenderingServer.canvas_create()
var vp_ci: RID = RenderingServer.canvas_item_create()
var update_pending: bool = false
var vp_texture: RID


func _init() -> void:
	RenderingServer.viewport_attach_canvas(vp, vp_canvas)
	RenderingServer.canvas_item_set_parent(vp_ci, vp_canvas)
	RenderingServer.viewport_set_update_mode(vp, RenderingServer.VIEWPORT_UPDATE_ALWAYS)
	RenderingServer.viewport_set_size(vp, size.x, size.y)
	vp_texture = RenderingServer.viewport_get_texture(vp)

func _draw() -> void:
	RenderingServer.canvas_item_clear(vp_ci)
	RenderingServer.canvas_item_add_rect(vp_ci, Rect2(Vector2.ZERO, size), bg_color)
	if texture != null:
		RenderingServer.canvas_item_add_texture_rect(vp_ci, Rect2(Vector2.ZERO, size), texture.get_rid())
	RenderingServer.viewport_set_active(vp, true)
	RenderingServer.force_draw(false)
	RenderingServer.viewport_set_active(vp, false)

	RenderingServer.canvas_item_add_texture_rect(get_canvas_item(), Rect2(Vector2.ZERO, size), vp_texture)

```

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: crash bug when attempting to Restart PowerToys as administrator
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Settings, General

### Steps to reproduce

1. Use Windows Search to find and start PowerToys
2. Click "open settings" under the Welcome message. 
3. In the new window that opens, click the upper left hamburger icon and select "General"
4. Scroll down to "Administrator mode" and click the "Restart PowerToys as administrator"
5. Observe that PowerToys crashes almost immediately after clicking. 

### ✔️ Expected Behavior

Expectation was for PowerToys to cue my admin login screen, as it typical does when I restart it as admin. After I enter my login info, PowerToys is normally running in admin mode.

### ❌ Actual Behavior

When I hit "Restart PowerToys as administrator" the cursor becomes a windows-wait/blue circle of death briefly before PowerToys completely and abruptly crashes and disappears. I verified in task manager that PowerToys is no longer running after this. I've repeatedly tried to restart PowerToys as admin without success. 

### Other Software

_No response_
Repository: neovim
Issue: b:undo_ftplugin unmapping fails when filetype is changed from help set via modeline
Labels: runtime,complexity:low,filetype

### Problem

If a file has a modeline `vim:ft=help`, changing filetype raises E31 errors:
```
Error detected while processing FileType Autocommands for "*"..function <SNR>1_LoadFTPlugin[2]..modelines[1]..FileType Autocommands for "*"..function <SNR>1_LoadFTPlugin:
line    2:
E31: No such mapping
E31: No such mapping
```

which must come from https://github.com/neovim/neovim/blob/c7d4a77ff9040c8b242f9d12a98472fe6217328c/runtime/ftplugin/help.lua#L85

This does not occur when ft is set to help but not by modeline.

### Steps to reproduce

```
echo 'vim:ft=help' | nvim --clean -
:set ft=
```

### Expected behavior

E31 is not issued.

### Nvim version (nvim -v)

v0.11.0-dev-c7d4a77ff904

### Vim (not Nvim) behaves the same?

no, vim 9.1.1043

### Operating system/version

EndeavourOS

### Terminal name/version

GNOME Terminal 3.54.3 using VTE 0.78.3 +BIDI +GNUTLS +ICU +SYSTEMD

### $TERM environment variable

xterm-256color

### Installation

build from repo
Repository: electron
Issue: [Bug] `context-menu` event not working on top part of window on macOS
Labels: platform/macOS,component/menu,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.2.8

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

macOS

### Operating System Version

Tested on macOS Sequoia 15.0 & macOS Sonoma 14.6.1

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

32.2.6

### Expected Behavior

When right clicking the `context-menu` event should work on all parts of the application window, as it does in version 32.2.6 and prior! (Have not tested version 32.2.7)

### Actual Behavior

The `context-menu` event only triggers in about the bottom 20-30% of the application, and never in the top half of the application. Resizing the window to the bottom of the screen will make the event trigger as expected always.

So right clicking the exact same place inside my application leaves different results: if the part of the application window I try to right click is positioned at the top part of the screen it never works, but moving/resizing the window towards the bottom of the screen and right clicking the exact same place properly triggers the event! This leaves me to believe that this must be an Electron issue, and not an issue on my side, also that it started to happen right after I updated Electron.

### Testcase Gist URL

_No response_

### Additional Information

This commit might be related, but not sure: https://github.com/electron/electron/commit/3007f859dad930ae80bafffc6042a146a45e4e4d
Repository: transformers
Issue: AttributeError: 'dict' object has no attribute '_attn_implementation_internal'
Labels: bug

### System Info

```
ForCausalLM.from_pretrained(model_path, attn_implementation='flash_attention_2')
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/miniconda3/lib/python3.12/site-packages/transformers/modeling_utils.py", line 4084, in from_pretrained
    config = cls._autoset_attn_implementation(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/root/miniconda3/lib/python3.12/site-packages/transformers/modeling_utils.py", line 1516, in _autoset_attn_implementation
    sub_config._attn_implementation_internal = curr_attn_implementation
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'dict' object has no attribute '_attn_implementation_internal'
```

Loading from a saved_pretrained model got error.

### Who can help?

_No response_

### Information

- [x] The official example scripts
- [x] My own modified scripts

### Tasks

- [x] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [x] My own task or dataset (give details below)

### Reproduction

ef

### Expected behavior

ef
Repository: ollama
Issue: Deepseek-R1 671B - Segmentation Fault Bug
Labels: bug

### What is the issue?

Hi,

I've been using the Deepseek-R1 671B model from Ollama on my 8x H100 machine and keep running into a segmentation fault, I've noticed that the frequency of the segfault happens the larger the context becomes.

I'm using the latest Ollama release.
Hardware Specs:
- 8x H100 - 80GB SXM
- Xeon Platinum 8468 (160c)
- Micron 7450 ssd
- 1548gb of ram
- OS is ubuntu 22.04
- CUDA: 12.6
- NVIDIA driver: 560.35.05


Happy to test params or gather more data, I'm having a hard time working around this. The distilled models like the deepseek llama 70B work just fine.

[server.err.log](https://github.com/user-attachments/files/18554764/server.err.log)

Any advice is appreciated.

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.5.7
Repository: material-ui
Issue: ClassName generator not working with Next.js App router
Labels: package: system,status: waiting for maintainer,nextjs

### Steps to reproduce

Steps:
1. Open this link to live example: [click here](https://codesandbox.io/p/live/e997598e-b472-4343-addd-c9e77da9a9af)
2. npm run dev
3. Open the devtools and inspect the element tree

### Current behavior

All the class names stay unchanged:

![Image](https://github.com/user-attachments/assets/c6953910-9f37-4e46-9331-63489f582aa8)

### Expected behavior

All class names should be transformed by the ClassNameGenerator.

### Context

I also tried to import the 'init-cls.ts' as a client script, but that only affects the client side, and the server side is  just doing nothing.
I'm following this doc: https://mui.com/material-ui/experimental-api/classname-generator/

### Your environment

  System:
    OS: Linux 6.1 Debian GNU/Linux 12 (bookworm) 12 (bookworm)
  Binaries:
    Node: 20.9.0 - /usr/local/bin/node
    npm: 9.8.1 - /usr/local/bin/npm
    pnpm: 8.10.2 - /usr/local/share/npm-global/bin/pnpm
  Browsers:
    Chrome: Not Found
  npmPackages:
    @emotion/react: latest => 11.11.1 
    @emotion/styled: latest => 11.11.0 
    @mui/core-downloads-tracker:  6.0.0 
    @mui/icons-material: latest => 6.0.0 
    @mui/material: latest => 6.0.0 
    @mui/material-nextjs: latest => 6.0.0 
    @mui/private-theming:  6.0.0 
    @mui/styled-engine:  6.0.0 
    @mui/system:  6.0.0 
    @mui/types:  7.2.16 
    @mui/utils:  6.0.0 
    @types/react: ^19.0.0 => 19.0.2 
    react: ^19.0.0 => 19.0.0 
    react-dom: ^19.0.0 => 19.0.0 
    typescript: latest => 5.1.6 


**Search keywords**: next, nextjs, app, classname, styles, experimental, css, class
Repository: puppeteer
Issue: [Feature]: Support navigation history for the current page
Labels: feature

### Feature description

Description:
I would like to get the navigation history for the current page. 

Proposed Solution:
CDP supports the ability to navigation history for the current page [Page.getNavigationHistory](https://chromedevtools.github.io/devtools-protocol/tot/Page/#method-getNavigationHistory) It will be nice to have this feature exposed in Puppeteer.
Repository: excalidraw
Issue: Bug: Add Link feature changed my redicrect to link
Labels: bug,Hyperlinks

My original link: `https://www.u-nas.com/xcart/cart.php?target=product&product_id=17640`
Excalidraw saves: `https://www.u-nas.com/xcart/cart.php?target=product&amp;amp;product_id=17640`

#### Reproduce step
1. Create a random block 

![Image](https://github.com/user-attachments/assets/67b76ed6-ffa6-4ac6-a3ad-550ac54674f5)

2. ADD link

![Image](https://github.com/user-attachments/assets/e44fdf2a-b16d-4f7f-aa06-e90483c2c1eb)

3. Paste the above original link and add

![Image](https://github.com/user-attachments/assets/78a0dd36-2ac1-47be-a533-071b1a719f91)

4. Redirected link has included `amp;` and is incorrect
Repository: godot
Issue: Menu options are not detected correctly.
Labels: bug,topic:editor,topic:gui

### Tested versions

v4.4.beta1.official [d33da79d3]

### System information

w10 64

### Issue description

When moving the cursor over menu options that have additional sub-options appearing automatically in a small menu to the right, the main menu options are not properly detected as the cursor moves over them.

As shown in the video, the cursor is positioned over an option, but an additional movement is required for the menu to detect the cursor's position and highlight the intended option.

https://github.com/user-attachments/assets/b92fe306-5aec-4280-bf7a-f61a56f12f64

### Steps to reproduce

See the video

### Minimal reproduction project (MRP)

...
Repository: ollama
Issue: Error fetching  ANY model locally
Labels: bug,networking

### What is the issue?

This is the Error message that I am getting:

pulling manifest
pulling 6e9f90f02bb3...   0% ▕                                                        ▏    0 B/9.0 GB
Error: max retries exceeded: Get "https://dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com/ollama/docker/registry/v2/blobs/sha256/6e/6e9f90f02bb3b39b59e81916e8cfce9deb45aeaeb9a54a5be4414486b907dc1e/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=66040c77ac1b787c3af820529859349a%2F20250127%2Fauto%2Fs3%2Faws4_request&X-Amz-Date=20250127T091701Z&X-Amz-Expires=86400&X-Amz-SignedHeaders=host&X-Amz-Signature=1afc1dcb356baf92d38344324c5f1504f216d4c77efb000442698708739d0298": dial tcp: lookup dd20bb891979d25aebc8bec07b2b3bbc.r2.cloudflarestorage.com: no such host


the command I am using:
`ollama pull <model-name>`

I have also tried using:
`ollama run <model-name>`

Any Model that I want to fetch locally, throws this error. How to fix it? I believe, I have installed OLLAMA properly. 

Please tell me how to resolve it. 


### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.5.4
Repository: flutter
Issue: Execution failed for task ':app:compileFlutterBuildDebug'.
Labels: in triage

### Steps to reproduce

1. flutter run

### Expected results

The app should launch normally.
If I use flutter clean, flutter pub get and then flutter run the app launches fine.

### Actual results

The app crashes immediately

### Code sample

`none`

### Screenshots or Video

_No response_

### Logs

[flutter-run-logs.txt](https://github.com/user-attachments/files/18556086/flutter-run-logs.txt)

### Flutter Doctor output

[flutter-doctor-logs.txt](https://github.com/user-attachments/files/18556084/flutter-doctor-logs.txt)
Repository: rust
Issue: Heavy usage of TLS causes stack overflow
Labels: A-thread-locals,C-bug,T-libs,A-panic

i wrote a dynamic library which uses `tracing`, which internally uses `std`s TLS implemention.
On unix, when I repeatedly load and then unload my library, eventually (after maybe 10 to 20 iterations) the program encounters a stack overflow.

After some research I found that this was due to the following flow:

`pthread_key_create` is called when TLS is initialized each time my library is loaded and my `tracing` logger is used.

`pthread_key_delete` is never called, there is no cleanup in this area.

Eventually `pthread_key_create` returns `EAGAIN`, which causes a panic.

Within the panic, the number of panics for the thread is tracked using TLS so when `increase` is called, we encounter a new panic (due to `EAGAIN`), which in turn will panic for the same reason.

We enter an endless loop of panics which eventually triggers a stack overflow.
Repository: pytorch
Issue: Add `sharding strategy` for `torch.distributed.tensor.parallel.ParallelStyle` with `inference_mode`
Labels: oncall: distributed,triaged,module: dtensor

### 🚀 The feature, motivation and pitch

When using tensor parallel and `with torch.inference_mode()`, any `torch.distributed.tensor.parallel.ParallelStyle` layers, we have:

`aten.mm.default: got mixed torch.Tensor and DTensor, need to convert all torch.Tensor to DTensor before calling distributed operators!`.

With `transformers == 4.48` and `torch==2.5.1`

```python
    import torch
    from transformers import LlamaConfig, LlamaModel
    import os
    model_id = "meta-llama/Meta-Llama-3-8B-Instruct"
    bs = 1
    seqlen = 4096
    # Get distributed settings
    rank = int(os.environ["RANK"])
    world_size = int(os.environ["WORLD_SIZE"])

    # Initialize distributed
    device = torch.device(f"cuda:{rank}")
    torch.distributed.init_process_group("nccl", device_id=device)
    device_mesh = torch.distributed.init_device_mesh("cuda", (world_size,))

    # Get model config
    config = LlamaConfig.from_pretrained(model_id)
    config.hidden_size = 2048
    config.attention_bias = False
    # Instantiate model
    with device:
        model = LlamaModel(config).to(dtype=torch.float16)

    model.eval()
    model.tensor_parallel(device_mesh)

    inputs = torch.randint(config.vocab_size, (bs, seqlen), device=device)

    # Test compile
    with torch.inference_mode():
        out = model(inputs)
```

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o @tianyu-l @XilunWu @albanD as we talked about this

### Alternatives

_No response_

### Additional context

_No response_
Repository: pytorch
Issue: Add correct `__repr__` for parallel distributed modules
Labels: oncall: pt2

### 🚀 The feature, motivation and pitch

Sorry if this is a duplicated, but instantiating a `transformers` and paralellizing will print the same model, which is unintuitive. 
```python 
    import torch
    import os
    from transformers import LlamaConfig, LlamaModel
    model_id = "meta-llama/Meta-Llama-3-8B-Instruct"
    bs = 1
    seqlen = 4096
    # Get distributed settings
    rank = int(os.environ["RANK"])
    world_size = int(os.environ["WORLD_SIZE"])

    # Initialize distributed
    device = torch.device(f"cuda:{rank}")
    torch.distributed.init_process_group("nccl", device_id=device)
    device_mesh = torch.distributed.init_device_mesh("cuda", (world_size,))

    # Get model config
    config = LlamaConfig.from_pretrained(model_id)
    config.hidden_size = 2048
    config.attention_bias = False
    # Instantiate model
    with device:
        model = LlamaModel(config).to(dtype=torch.float16)

    model.eval()
    # Tensor Parallel
    if world_size > 1:
        model.tensor_parallel(device_mesh)
    print(model)
```
should IMO print `ColumParallel(...., device_mesh = [0,1])` etc


### Alternatives

_No response_

### Additional context

_No response_

cc @chauhang @penguinwu
Repository: vscode
Issue: explorer: cannot duplicate last saved version of unsaved file
Labels: feature-request,file-explorer


Type: <b>Bug</b>

1. Save a file.
1. Edit it without saving it.
1. In the VSCode file explorer, click on this file, copy and paste it in the same folder (ctrl-c, ctrl-v).
1. The copy has the same content as the unsaved file, not the content of the last saved version of the file!

This is a problem because the saved state is often a critical reference point for creating backups or comparisons.

VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i3-10110U CPU @ 2.10GHz (4 x 2592)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.76GB (1.30GB free)|
|Process Argv|--disable-extensions --crash-reporter-id dcf1a538-7ced-4334-a13e-401517f8220e|
|Screen Reader|no|
|VM|0%|
</details>Extensions disabled<details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyonecf:30548226
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
nativerepl1:31139838
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
hdaa2157:31222309
copilot_t_ci:31222730

```

</details>

<!-- generated by issue reporter -->
Repository: ant-design
Issue: In Menu, if there is `extra` and text doesn't fit in width, `extra` isn't visible at all
Labels: unconfirmed

### Reproduction link

[https://codepen.io/rakleed/pen/EaYGWeL?editors=001](https://codepen.io/rakleed/pen/EaYGWeL?editors=001)

### Steps to reproduce

1. `label` should be longer than the maximum menu width.
2. You need to add `extra`.

### What is expected?

`extra` is visible, and the text is reduced using an ellipsis.

![Image](https://github.com/user-attachments/assets/81d529d0-2dca-49c9-8c93-07bda3e8ecff)

### What is actually happening?

`extra` is not visible, and the text is not shortened.

![Image](https://github.com/user-attachments/assets/6b2d819b-f9b6-486f-9354-4c55f033e412)

| Environment | Info |
| --- | --- |
| antd | 5.23.2 |
| React | 18.3.1 |
| System | macOS 15.2 |
| Browser | Chrome 132 |

---
Probably you should wrap `label` in `<span>`, and add `overflow: hidden; text-overflow: ellipsis;` to it.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: storybook
Issue: [Bug]: strange Manager.js path that run infinitely in background
Labels: bug,compatibility with other tools,build-storybook

### Describe the bug

in my project
 
https://design.copromatic.com/

when you check your console nav you can see many error runs in background with strange url. 
i didn't found any relative issues. 


https://design.copromatic.com/sb-preview/sb-addons/essentials-backgrounds-5/sb-addons/storybook-core-core-server-presets-0/sb-addons/essentials-viewport-6/sb-addons/links-1/manager-bundle.js

when i run in local with 

> npx http-server ./storybook-static

There is no errors


I use 
storybook 8.5.1
vite 6.0.11
cloudflare pages

### Reproduction link

https://design.copromatic.com/

### Reproduction steps

_No response_

### System

```bash
npx storybook@latest info

Storybook Environment Info:

  System:
    OS: macOS 14.5
    CPU: (8) arm64 Apple M1
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.12.0 - ~/.nvm/versions/node/v22.12.0/bin/node
    npm: 10.9.0 - ~/.nvm/versions/node/v22.12.0/bin/npm <----- active
    pnpm: 9.11.0 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 132.0.6834.110
    Safari: 17.5
  npmPackages:
    @storybook/addon-essentials: ^8.5.1 => 8.5.1 
    @storybook/addon-interactions: ^8.5.1 => 8.5.1 
    @storybook/addon-links: ^8.5.1 => 8.5.1 
    @storybook/addon-mdx-gfm: ^8.5.1 => 8.5.1 
    @storybook/addon-storysource: ^8.5.1 => 8.5.1 
    @storybook/blocks: ^8.5.1 => 8.5.1 
    @storybook/manager-api: ^8.5.1 => 8.5.1 
    @storybook/test: ^8.5.1 => 8.5.1 
    @storybook/theming: ^8.5.1 => 8.5.1 
    @storybook/vue3: ^8.5.1 => 8.5.1 
    @storybook/vue3-vite: ^8.5.1 => 8.5.1 
    storybook: ^8.5.1 => 8.5.1 
    storybook-version: ^0.1.2 => 0.1.2 
    storybook-vue3-router: ^5.0.0 => 5.0.0
```

### Additional context

_No response_