sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: RPI with armhrf architecture support
Labels: feature request,build

### What is the issue?

I followed all possible guide online,
either using curl and your install.sh, the docker, or the snap package and I could manage to install ollama, not clear how to compile the code (there is no configure file). The main issue is that everyzthing has been prepared for arm64 and not for my architecture armhrf with I need for my current display. Is there as way to install the arm64 on the armhrf architecture?

### OS

Linux

### GPU

_No response_

### CPU

Other

### Ollama version

any
Repository: ui
Issue: [bug]: DropdownMenuSubTrigger hover/focus bg not working
Labels: bug

### Describe the bug


https://github.com/user-attachments/assets/c562db81-04b8-4ab3-9ceb-0870c3121ccf

As shown in the video, when I hover on the theme menu item, it will correctly pick up focused bg, but soon it will become grey. How to make it consistent and use focused bg?

```
              <DropdownMenuSubTrigger className="focus:bg-bg-weak-50 hover:bg-bg-weak-50 hover:rounded-[var(--radius-8,8px)] rounded-[var(--radius-8,8px)] bg-[var(--bg-white-0,#FFF)] flex p-3 items-center gap-2 self-stretch text-[var(--text-strong-950,#0E121B)] font-inter text-sm font-normal leading-[20px] tracking-[-0.084px] cursor-pointer">
                {theme === 'light' ? lightIcon : darkIcon}
                {theme === 'light' ? 'Light' : 'Dark'}
              </DropdownMenuSubTrigger>
```

### Affected component/components

              <DropdownMenuSubTrigger className="focus:bg-bg-weak-50 hover:bg-bg-weak-50 hover:rounded-[var(--radius-8,8px)] rounded-[var(--radius-8,8px)] bg-[var(--bg-white-0,#FFF)] flex p-3 items-center gap-2 self-stretch text-[var(--text-strong-950,#0E121B)] font-inter text-sm font-normal leading-[20px] tracking-[-0.084px] cursor-pointer">

### How to reproduce

Use 
```
              <DropdownMenuSubTrigger className="focus:bg-bg-weak-50 hover:bg-bg-weak-50 hover:rounded-[var(--radius-8,8px)] rounded-[var(--radius-8,8px)] bg-[var(--bg-white-0,#FFF)] flex p-3 items-center gap-2 self-stretch text-[var(--text-strong-950,#0E121B)] font-inter text-sm font-normal leading-[20px] tracking-[-0.084px] cursor-pointer">
                {theme === 'light' ? lightIcon : darkIcon}
                {theme === 'light' ? 'Light' : 'Dark'}
              </DropdownMenuSubTrigger>
```


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: godot
Issue: Godot crashes when opening a project 
Labels: needs testing,crash

### Tested versions

This happened to me on the latest versions (4.3) on Steam and Chrome (64-bit)

### System information

Windows 10 Intel core i5-7300HQ CPU 2.GHZ 16 GB RAM GeForce gtx 1050

### Issue description

Godot closes by itself when opening a project or creating it. I tried to fix the problem by restarting my PC and installing the steam and google versions 

### Steps to reproduce

This is my first question on github, I don't know what this is XDD

### Minimal reproduction project (MRP)

Also :v
Repository: PowerToys
Issue: Files locksmith. Does not appear in context menu. 
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.83

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

File Locksmith

### Steps to reproduce

Does not appear in context menu. Changed options, rebooted - nothing.
![lock](https://github.com/user-attachments/assets/ae933c1a-435c-46bf-9901-b5463c7c25ee)


### ✔️ Expected Behavior

Show File Locksmith punkt menu

### ❌ Actual Behavior

Null

### Other Software

_No response_
Repository: storybook
Issue: [Bug]: The preview.js 'globals' field is deprecated and will be removed in Storybook 9.0.
Labels: bug,needs triage

### Describe the bug

I think @storybook/addon-themes is adding to the deprecated globals field.

<img width="844" alt="image" src="https://github.com/user-attachments/assets/6d66c548-23a0-4d9a-a423-47ad94830416">

causing an unexpected error to be thrown that me, as a user, cannot fix.


### Reproduction link

https://stackblitz.com/edit/github-edphde?file=.storybook%2Fmain.js

### Reproduction steps

1. Add a theme with tailwind following https://github.com/storybookjs/storybook/blob/next/code/addons/themes/docs/getting-started/tailwind.md
2. open the console to see the error

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.5
    CPU: (12) arm64 Apple M3 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.2 - ~/.local/state/fnm_multishells/70585_1725326396129/bin/node
    npm: 10.8.2 - ~/.local/state/fnm_multishells/70585_1725326396129/bin/npm <----- active
  Browsers:
    Chrome: 128.0.6613.114
    Safari: 17.5
  npmPackages:
    @storybook/addon-actions: ^8.2.9 => 8.2.9 
    @storybook/addon-essentials: ^8.2.9 => 8.2.9 
    @storybook/addon-interactions: ^8.2.9 => 8.2.9 
    @storybook/addon-links: ^8.2.9 => 8.2.9 
    @storybook/addon-themes: ^8.2.9 => 8.2.9 
    @storybook/react: ^8.2.9 => 8.2.9 
    @storybook/react-vite: ^8.2.9 => 8.2.9 
    @storybook/test: ^8.2.9 => 8.2.9 
    msw-storybook-addon: ^2.0.3 => 2.0.3 
    storybook: ^8.2.9 => 8.2.9
```


### Additional context

I tried to repro this in stackblitz but it is using beta versions of storybook and may have been fixed?
Repository: vscode
Issue: Markdown language detection is overly aggressive and cannot be disabled
Labels: feature-request,languages-guessing

<!-- ⚠️⚠️ 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?: Yes

<!-- 🪓 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
- OS Version: macOS Sonoma 14.6.1

Steps to Reproduce:

1. Open a new file
2. Type `how about vscode not do this` (or your preferred string). Or paste any URL (like https://github.com/microsoft/vscode/issues/227416).
3. VS Code detects the file as Markdown for some reason?

This happens if History Based Language Detection is enabled or disabled.

The `workbench.editor.languageDetection` setting is of no use here, so it doesn't seem like this can be disabled.

When I click on the Select Language Mode button, the probability that I am switching from Markdown to Plain Text is approximately 100%.

Please fix Markdown language detection, or give us a setting to turn it off for specific languages.
Repository: react-native
Issue: Currency unit EURO (€) is spoken only for Google Pixel device and not for Samsung devices in Talkback
Labels: Needs: Repro,Newer Patch Available,Needs: Attention

### Description

Currency unit EURO (represented by the € symbol) is spoken ONLY for Google Pixel device and NOT for Samsung devices

### Steps to reproduce

1) Install the application with yarn android
2) Enable Talkback
3) Listen to speech output for prices

### React Native Version

0.73.6

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.6.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 62.84 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.13.0
    path: ~/.asdf/installs/nodejs/18.13.0/bin/node
  Yarn:
    version: 1.22.22
    path: ~/.asdf/installs/nodejs/18.13.0/bin/yarn
  npm:
    version: 8.19.3
    path: ~/.asdf/plugins/nodejs/shims/npm
  Watchman:
    version: 2024.05.06.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.12.1
    path: /Users/I583816/.asdf/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK:
    API Levels:
      - "30"
      - "31"
      - "32"
      - "33"
      - "33"
      - "34"
    Build Tools:
      - 29.0.2
      - 30.0.3
      - 31.0.0
      - 32.0.0
      - 33.0.0
      - 33.0.1
      - 33.0.2
      - 34.0.0
      - 34.0.0
      - 34.0.0
    System Images:
      - android-30 | Google APIs ARM 64 v8a
      - android-31 | Google APIs ARM 64 v8a
      - android-31 | Google Play ARM 64 v8a
      - android-33 | Google APIs ARM 64 v8a
      - android-34 | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.11005911
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.9
    path: /Users/I583816/Library/Java/JavaVirtualMachines/corretto-17.0.9/Contents/Home/bin/javac
  Ruby:
    version: 3.1.1
    path: /Users/I583816/.asdf/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.6
    wanted: 0.73.6
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```


### Stacktrace or Logs

```text
N/A
```


### Reproducer

N/A

### Screenshots and Videos

_No response_
Repository: vscode
Issue: Deprecate API setNotebookMetadata in ipynb extension
Labels: debt,notebook

This was created when notebook API wasn't stable, but was required for Julia extension.
Now that the API is stable, we can remove this = After Julia extension adopts the new API & stops using this old API.

See here for more details https://github.com/julia-vscode/julia-vscode/pull/2424
Repository: storybook
Issue: [Bug]: >= v8.2.0 Storybook versions no longer splits the sb-manager into chunks
Labels: bug,sev:S3,upgrade:8.2

### Describe the bug

After upgrading from 8.1.11 to 8.2 onwards, I noticed that sb-manager files no longer gets split into chunks by webpackFinal's configurations:
`config.optimization = {
      ...config.optimization,
      splitChunks: {
        chunks: 'all',
        maxInitialRequests: Infinity,
        minSize: 30 * 1024,
        maxSize: 500 * 1024,
      },
    };`

### Reproduction link

https://stackblitz.com/edit/github-xmmg5f?file=.storybook%2Fmain.ts

### Reproduction steps

1. Initiate a new project using react-webpack5 as the framework.
2. run `npm run build-storybook`
3. Inside storybook-static/sb-manager, the js files are not split into chunks.
4. Expected to be split as of 8.1.11

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.6.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.2/bin/npm <----- active
  Browsers:
    Chrome: 128.0.6613.114
    Safari: 17.6
  npmPackages:
    @storybook/addon-essentials: ^8.2.9 => 8.2.9 
    @storybook/addon-interactions: ^8.2.9 => 8.2.9 
    @storybook/addon-links: ^8.2.9 => 8.2.9 
    @storybook/addon-styling-webpack: ^1.0.0 => 1.0.0 
    @storybook/addon-themes: ^8.2.9 => 8.2.9 
    @storybook/addon-webpack5-compiler-swc: ^1.0.5 => 1.0.5 
    @storybook/blocks: ^8.2.9 => 8.2.9 
    @storybook/react: ^8.2.9 => 8.2.9 
    @storybook/react-webpack5: ^8.2.9 => 8.2.9 
    @storybook/test: ^8.2.9 => 8.2.9 
    storybook: ^8.2.9 => 8.2.9
```


### Additional context

_No response_
Repository: ollama
Issue: Unable to resolve Cuda-drivers on RHEL8.9
Labels: bug

### What is the issue?

While in RHEL8.9 Ollama Installation cannot finish due to an issue while installing cuda-drivers. 
Nvidia repository is successfully installed and I can see cuda-drivers are listed there but when triggering repolist only cuda-drivers-fabricmanager are listed.
I an running crazy with this issue, I have Ollama installed in other similar instances but since the latest update it seems I cannot install it for some reason.
Hoping anyone here had the same issue and can guide me to fix it.

`>>> Installing CUDA driver...
Updating Subscription Management repositories.
Unable to read consumer identity
Last metadata expiration check: 0:00:06 ago on Tue 03 Sep 2024 08:27:42 AM +04.
All matches were filtered out by modular filtering for argument: cuda-drivers
Error: Unable to find a match: cuda-drivers`

Thanks in advance.


### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.7
Repository: flutter
Issue: consider changing the behavior of `CarouselView.padding`
Labels: c: new feature,framework,f: material design,d: api docs,c: proposal,P3,team-design,triaged-design

## Summary

- The properties within `CarouselView` are confusing because they do not include the word "item," even though they are related to individual items.
  - For example, `backgroundColor` and `shape` are applied to each item.
- The behavior of `CarouselView.padding` differs from `ListView.padding`.
  - While `ListView.padding` applies to the entire `ListView`, `CarouselView.padding` applies to the padding of each individual item in the `CarouselView`, which disrupts consistency across Flutter.

### Proposal

- Would it be better to rename these properties to `CarouselView.itemBackgroundColor`, and `CarouselView.itemShape` for clarity?
- Also, consider changing the behavior of CarouselView.padding to match that of ListView, where it would apply to the padding of the entire viewable area.
Repository: godot
Issue: Tooltips disappear when mouse leaves initiating Element with Single Window Mode
Labels: bug,topic:gui

### Tested versions

- Reproducible in: v4.3.stable

### System information

Linux - Artix (Arch) - Moksha (Enlightenment) - Nvidia - Vulkan

### Issue description

On Linux enabling Single Windowed Mode in editor settings makes focusing and scrolling tooltips impossible, Is curious that in #57425 the issue is solved just enabling this option but in my case is just the opposite.

### Steps to reproduce

1. Open Editor
2. Enable Single Windowed Mode in Editor Settings
3. Move the mouse over to display a tooltip on any property in the inspector
4. Try to move/scroll mouse on displayed tooltip

### Minimal reproduction project (MRP)

Not applicable
Repository: godot
Issue: Empty line above GDScript syntax error line wrongly gets highlighted in red too
Labels: bug,topic:gdscript,topic:editor

### Tested versions

v4.4.dev1.official [28a72fa43]

### System information

w10 64

### Issue description

Notice the red error line, it doubles up when I create an empty line above it.

https://github.com/user-attachments/assets/5da25e7c-edd9-4164-b6ec-2c6e0a4e25fb



### Steps to reproduce

See the video

### Minimal reproduction project (MRP)

...
Repository: puppeteer
Issue: [Feature]: support custom arguments in the launch command
Labels: feature,@puppeteer/browsers,P3

### Steps to reproduce

```
npx @puppeteer/browsers launch chrome-headless-shell@stable -- --remote-debugging-port=9222  --headless --no-sandbox
```

this always exits immediately with exit code 130 (break?) while it works for normal chrome's 

[testing on mac arm]

### Expected results

headless chrome should run with remote debugging active 

### Actual results

the process exits immediately
Repository: ollama
Issue: Report better error message on old drivers (show detected version and minimum requirement)
Labels: feature request,nvidia

### What is the issue?

[log.txt](https://github.com/user-attachments/files/16846086/log.txt)
This is a log

### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.9
Repository: angular
Issue: There is no way to subscribe to control validators presence changes
Labels: area: forms,forms: change detection

### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

There is no way to be notified when someone added/removed validator to formControl.

### Proposed solution

I propose new stream `validatorsChanges`
```
this.control.validatorsChanges.subscribe(() => ...)
```

### Alternatives considered

-
Repository: pytorch
Issue: [BUG]: torch.profiler is blocked in "_disable_profiler()" when profiling cuda graph on single GPU
Labels: oncall: profiler

### 🐛 Describe the bug

I use torch.profiler to profile a cuda graph, but the program is blocked in function `_disable_profiler()` of torch.profiler when torch.profiler stop the trace. 

minimal example:
```
import torch

a = torch.tensor(1, device='cuda')
# WarnUp before cuda graph capture
for _ in range(11):
    b = a + a
# Graph Capture
g = torch.cuda.CUDAGraph()
with torch.cuda.graph(g):
    b = a + a
# Torch.profiler
with torch.profiler.profile():
    g.replay()
    torch.cuda.synchronize()
```
I use pdb to the locate the stuck area, the picture below shows torch.profiler is blocked in `_disable_profiler()` which is a CPU function:
<img width="643" alt="Screenshot 2024-09-03 at 16 51 06" src="https://github.com/user-attachments/assets/abbae824-117b-4cee-87fc-87c6661cce8b">

### Versions

Platforms: linux
Hardware: 1*A100
Software versions: **cuda11.8**, python3.10.14
PyTorch version: 2.3.1+cu118
I tried it on pytorch2.1.2, pytorch2.3.1+cu118 and pytorch2.4.0+cu118 and got the same result.

Update:
I tried it on pytorch 2.3.0+cu121 and the torch.profiler is not blocked, and I got the right result. Thus I think maybe there are bugs in pytorchxxx+cu118.



cc @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise
Repository: node
Issue: Node-API V8 Fast API
Labels: feature request,node-api

### What is the problem this feature will solve?

Node-API methods could be faster in certain cases

### What is the feature you are proposing to solve the problem?

Somehow add support for V8 Fast API.

### What alternatives have you considered?

_No response_
Repository: flutter
Issue: [DatePicker] Material3 DatePicker should follow OS regional settings or provide additional setting
Labels: framework,f: material design,f: date/time picker,a: internationalization,has reproducible steps,P2,team-design,triaged-design,found in release: 3.24,found in release: 3.25

### Steps to reproduce

1. Use `showDatePicker` method on Flutter project with material3
2. Set English (USA) language on your OS
3. Change regional settings - first day of week to Monday
4. Open app and open date picker
5. First day of week will be Sunday (locale default - completely ignores regional settings)

### Expected results

I would expect to at least follow OS regional setting or provide an method to set first day of week manually.

### Actual results

OS regional settings are completely ignored, and datePicker always uses locale default settings which cannot be changed at all and there is no other option to override first day of week manually.

### Code sample

<details open><summary>Code sample</summary>

```dart
showDatePicker(
    context: context,
    firstDate: DateTime.now().subtract(const Duration(days: 365)),
    lastDate: DateTime.now().add(const Duration(days: 365)),
    initialDate: DateTime.now(),
  )
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

![datePicker_screenshot](https://github.com/user-attachments/assets/4b9e2918-d9fe-4412-8db9-b05ae1203051)

![regional_settings](https://github.com/user-attachments/assets/edb9b1c3-7c60-4ed8-ac03-58ab21630b25)


</details>


### Logs

_No response_

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel stable, 3.24.1, on macOS 14.6.1 23G93 darwin-arm64, locale en-SI)
[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.4)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2024.1)
[✓] VS Code (version 1.92.2)
[✓] Connected device (6 available)
[✓] Network resource
```

</details>
Repository: godot
Issue: `NavigationServer3D::query_path` does not find optimal path across multiple aligned navigation meshes.
Labels: enhancement,topic:navigation,performance

### Tested versions

4.3-stable

### System information

Windows 11

### Issue description

It seems that `NavigationServer3D::query_path` has some issues optimizing/finding longer paths. All individual optimal path segments exist, even across mesh borders. However the full path takes a totally different route that is way longer. I have tried with `simplify_path` `true` and false, and `PATH_POSTPROCESSING_CORRIDORFUNNEL` and `PATH_POSTPROCESSING_EDGECENTERED`. `simplify_path=true` and `PATH_POSTPROCESSING_CORRIDORFUNNEL` produces the best result from all options but it is still far from optimal.

![image](https://github.com/user-attachments/assets/0d239fe7-a038-4cbc-95d2-a521183cdb69)
![image](https://github.com/user-attachments/assets/8de30e4b-abe5-4416-91b2-2364e3ab4d79)
![image](https://github.com/user-attachments/assets/f705a186-33a0-424f-a03d-61c5d62b8f8f)
![image](https://github.com/user-attachments/assets/32a0033d-a336-4255-9452-46c65173f515)
![image](https://github.com/user-attachments/assets/2352d6ab-f360-4c94-8308-419f06640fd9)
![image](https://github.com/user-attachments/assets/adcd4abc-ffd0-4f6f-91fe-8959958b3c6d)


![image](https://github.com/user-attachments/assets/3234e194-ef84-49cb-9f6e-f3bab48eab81)

### Steps to reproduce

```
func find_path() -> void:
	var start: Vector3 = %Start.position
	var end: Vector3 = %End.position
	var query := NavigationPathQueryParameters3D.new()
	query.start_position = start
	query.target_position = end
	query.map = get_world_3d().navigation_map
	query.simplify_path = true

	var result := NavigationPathQueryResult3D.new()
	NavigationServer3D.query_path(query, result)
	%Path.draw_path(result.path)
```

### Minimal reproduction project (MRP)

-
Repository: vscode
Issue: Deprecated extension recommendation: Volar
Labels: feature-request,extensions

<!-- ⚠️⚠️ 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?: Yes/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
- OS Version: Win10

Steps to Reproduce:

1. Open a vue3 project
2. Vscode recommends Volar

![image](https://github.com/user-attachments/assets/e0dbb6cb-2e32-4db0-a472-e65225fe5b5c)
![image](https://github.com/user-attachments/assets/8d65a819-7d32-4751-96a8-289fbcc56dea)