sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: [Compiler Bug]: null reference exception if you assume a value is not null in a callback (which can be valid)
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEAKgmDgBTBEC2AhgJ4BGCAclADacA0RAvgEoiwADrEicQhUnMiAXiJQwCAML1uzenADWlSsPkA+EeKLmiaTNSIAPZHSasO3AHS2BggNxmBfANoMLOxcvAC63uK+MAg4sMRBzqFEAPxEADxgAA70xAD0Jg7pACZ4AG5EhKqceLrywHDM-EQFPpj8IPxAA

### Repro steps

Similiar to https://github.com/facebook/react/issues/31550 but with useCallback and no external deps.

You seem to assume that accessing `x.y` is safe in the render method if it is safe in a callback.

### How often does this bug happen?

Every time

### What version of React are you using?

18.3.1

### What version of React Compiler are you using?

19.0.0-beta-a7bf2bd-20241110
Repository: rust
Issue: compiletest: Locally running clang-based tests assumes a hard-coded path to clang
Labels: T-bootstrap,C-bug,A-compiletest

When trying to run clang-based run-make tests locally, it doesn't seem to be possible to easily change or specify the path to a custom clang. For example, if I run:
```
RUSTBUILD_FORCE_CLANG_BASED_TESTS=1 ./x test tests/run-make/pointer-auth-link-with-c-lto-clang
```
Then the rmake build will be invoked with
```
CLANG="~/rust/rust/build/aarch64-unknown-linux-gnu/llvm/bin/clang"
LLVM_BIN_DIR="~/llvm/rust-llvm/build/bin"
```
LLVM_BIN_DIR is set from config.toml and that's correct. CLANG, on the other hand, is hard-coded by bootstrap to be overwritten to where the CI puts it. Setting the envvar manually does not work and the test keeps crashing unless I symlink the clang binary to where it points it to or modify the bootstrap source.

Compiletest has an option to specify the clang path, so the test _could_ be invoked as follows:
```
RUSTBUILD_FORCE_CLANG_BASED_TESTS=1 ./x test tests/run-make/pointer-auth-link-with-c-lto-clang -- --run-clang-based-tests-with ~/llvm/rust-llvm/build/bin/clang
```
But bootstrap already passes that flag to it so no luck, still complains:
```
Testing stage1 compiletest suite=run-make mode=run-make (aarch64-unknown-linux-gnu)                                                                             
thread 'main' panicked at src/tools/compiletest/src/lib.rs:198:19:                                                                                                   
OptionDuplicated("run-clang-based-tests-with")                                                                                                                         
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace                                                                                          
Build completed unsuccessfully in 0:00:01
```
I think the easiest solution here would be to just make it so that compiletest lets you override this option by just taking whichever one comes last. A cleaner solution would be removing the assumption on the path to the clang binary and making it configurable.

cc @jieyouxu
Repository: vscode
Issue: vscode window is large then it seems. transparent unclickable area around all windows.
Labels: bug,ux,linux,workbench-os-integration


Type: <b>Bug</b>

Unable to click anything under window, transparent area of aproximately 50px, all around. Since there is a shadow around, every vscode window, issue reporter included, has this issue. I'm guessing it has something to do with the shadow. 

Basically the window is larger then it seems and clicking at the edge of vscode, i'm unable to switch to another app that is underneat it. Representated by white rectangular, aproximation of area around the window.

![Image](https://github.com/user-attachments/assets/f38391d4-fd27-4f6d-ba40-4f97d45ed140)

VS Code version: Code 1.95.2 (e8653663e8840adaf45af01eab5c627a5af81807, 2024-11-07T11:07:22.054Z)
OS version: Linux x64 6.11.7-300.fc41.x86_64
Modes:

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

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 5800X3D 8-Core Processor (16 x 3553)|
|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: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off<br>webnn: disabled_off|
|Load (avg)|1, 0, 0|
|Memory (System)|62.71GB (55.33GB free)|
|Process Argv|/home/tomi/Documents --crash-reporter-id ac1fc1ed-1df5-4e41-a000-f6055199a477|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|gnome|
|XDG_CURRENT_DESKTOP|GNOME|
|XDG_SESSION_DESKTOP|gnome|
|XDG_SESSION_TYPE|wayland|
</details><details><summary>Extensions (5)</summary>

Extension|Author (truncated)|Version
---|---|---
xml|Dot|2.5.1
vscode-docker|ms-|1.29.3
default-keys-windows|smc|0.0.10
php-debug|xde|1.35.0
php-intellisense|zob|1.3.3


</details><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_surveyone:30548225
vscrpc:30673769
962ge761:30959799
9b8hh234:30694863
pythonnoceb:30805159
asynctok:30898717
pythonmypyd1:30879173
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
dvdeprecation:31068756
dwnewjupytercf:31046870
2f103344:31071589
impr_priority:31102340
nativerepl1:31139838
pythonrstrctxt:31112756
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31181875

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: [AOTI] Test case `test_aot_inductor.py::test_multi_device_cpu` is Running GPU AOT Inductor in CPU container runner.
Labels: oncall: pt2,oncall: export,module: aotinductor

### 🐛 Describe the bug

The test case [`test_multi_device_cpu`](https://github.com/pytorch/pytorch/blob/1b95ca904f5020ad8649677cbef683fac9d8e768/test/inductor/test_aot_inductor.py#L304C1-L314C50) actually runs in the `AOTIModelContainerRunnerCpu`, but in the `torch.compile` see it's is GPU, here is "cuda". So the generated AOT Inductor Cpp code all defined USE_CUDA=1, but the container runner is CPU, which has the stream as `nullptr`.
This case happed to pass in CUDA machine because CUDA API will recognize the `nullptr` as current stream.
But for XPU which I'm implemented, the SYCL API get crashed with `nullptr` stream. So I think we need to refine this test case.  

### Versions

Collecting environment information...
PyTorch version: 2.6.0a0+git8a80cee
Is debug build: False
CUDA used to build PyTorch: 12.4
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.1 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.31.0
Libc version: glibc-2.35

Python version: 3.9.20 | packaged by conda-forge | (main, Sep 30 2024, 17:49:10) [GCC 13.3.0] (64-bit runtime)
Python platform: Linux-5.15.0-125-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 12.4.99
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA A100-PCIE-40GB
Nvidia driver version: 550.120
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4 @desertfire @chenyang78 @ezyang
Repository: PowerToys
Issue: Color picker: add color viewer mode
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Hi,

In color viewer mode, all color formats would be editable and a additional panel on the right would show a preview of the input color.

### Scenario when this would be used?

I often need to visualize color whose format is not common and there are not many tool to do it.
Repository: rust
Issue: `--nocapture` doesn't follow common CLI conventions, making it a stumbling block to people debugging failures
Labels: A-libtest,C-bug,disposition-merge,finished-final-comment-period,T-testing-devex

By convention, users would expect to type in `--no-capture`.  The fact that the argument is `--nocapture` trips people up, especially as they have to wait for their test to compile before they see the failure.  Without spelling suggestions, they need to then consult the help to then remember its without the middle `-`.  Unless someone is doing this all the time to build up muscle memory to counteract intuition, this will trip people up each time.

See also
- #24451
- https://hachyderm.io/@wezm@mastodon.decentralised.social/113485301109871075
- https://rust-lang.zulipchat.com/#narrow/channel/404371-t-testing-devex/topic/--nocapture/near/482538793
Repository: node
Issue: [v18.20.5 / next v20.x LTS version] NodeJS should provide some kind of warning when using import assertions as they are non-standard
Labels: v18.x,v20.x

# Clarification
v18.20.4 (previous v18.x release) and v20.18.0 have a warning for both import assertions and import attributes

v18.20.5 removes this warning for both cases, I believe the import assertion warning should still be around

Seems to be caused by https://github.com/nodejs/node/pull/55333

### Version

v18.20.5

### Platform

All


### Subsystem

_No response_

### What steps will reproduce the bug?


```sh
node --input-type=module -e 'import "data:application/json,{}" assert { type: "json" }'
```


### How often does it reproduce? Is there a required condition?

Every time

### What is the expected behavior? Why is that the expected behavior?

Regarding [What steps will reproduce the bug?]

It should provide some kind of warning since import assertions (not import attributes) are non-standard

### Additional information

This also applies to the next v20.x LTS version
Repository: react-native
Issue: [0.76] AccessibilityValue in View throws exception: "Exception in HostFunction: Loss of precision during arithmetic conversion: (long) " 
Labels: Platform: Android,Needs: Triage :mag:,Newer Patch Available,Type: New Architecture

### Description

Similar to https://github.com/react-native-elements/react-native-elements/issues/3955 https://github.com/Sharcoux/slider/issues/102 https://github.com/callstack/react-native-paper/issues/4544, when any non-zero value is given to `AccessibilityValue.now` on Android & iOS, conversion occurs and an exception will be thrown. 

(remark: Using `Math.round()` to avoid any (long) value will fix the issue temporarily.)

Both Expo (0.52) and bare React Native App (0.76.1 + SDK 34, 0.76.2 + SDK 35) can reproduce the bug. Expo 0.51 will not, so it is very likely related to New Architecture.

Same issue found in iOS 18 in some cases, but expo demo can show that

### Steps to reproduce

1. go to [demo](https://snack.expo.dev/OEofab5meHPozAXyOQg6_)
2. switch to Android/iOS and make sure expo == 0.52
3. click "Start Progress" to see the crash

### React Native Version

0.76.2

### Affected Platforms

Runtime - Android
Runtime - iOS

### Areas

Fabric - The New Renderer

### Output of `npx react-native info`

```text
Binaries:
  Node:
    version: 23.1.0
    path: /opt/homebrew/bin/node
  Yarn:
    version: 3.6.4
    path: /opt/homebrew/bin/yarn
  npm:
    version: 10.9.0
    path: /opt/homebrew/bin/npm
  Watchman:
    version: 2024.11.04.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.16.2
    path: /opt/homebrew/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23339.11.2421.12550806
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.13
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.0
    wanted: 15.0.0
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.1
    wanted: 0.76.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: true
  newArchEnabled: true
```


### Stacktrace or Logs

Android:
```text
Exception in HostFunction: Loss of precision during arithmetic conversion: (long) 0.00001
```

iOS:
```text
Exception in HostFunction: Loss of precision during arithmetic conversion: (long long) 0.00001
```


### Reproducer

[https://snack.expo.dev/OEofab5meHPozAXyOQg6_](https://snack.expo.dev/OEofab5meHPozAXyOQg6_)

### Screenshots and Videos

_No response_
Repository: vscode
Issue: Option to place "Start Debugging" control in Command Center
Labels: feature-request,debug

<!-- ⚠️⚠️ 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. -->

I love having the Debug Toolbar within the Command Center. Since it only appears while debugging, it would be helpful to have the "Start Debugging" control appear in its place when not debugging. This would eliminate the need to switch to the Run and Debug pane, making the workflow more convenient.

Here's a visual for what I'm suggesting:

![Image](https://github.com/user-attachments/assets/67507ced-4cc6-4371-9e2b-d6fec5c24d9e)

Thank you!
Repository: PowerToys
Issue: A simplified functionality option for Awake
Labels: Idea-Enhancement,Product-Awake

### Description of the new feature / enhancement

An option where a single tap/left click on the Awake icon in the Taskbar could toggle it between "OFF" and "USER-SPECFIC CHOICE" modes.

### Scenario when this would be used?

I am a heavy user of Awake but rather than assigning it specific time to stay awake, I always go for "Indefinite" because I don't know how each session may turn out. The existing options are probably more useful to other users, but it would be great if each user could customize the toggle functionality to their preference, i.e. single tap/left click toggle between "OFF" and "USER-SPECFIC CHOICE". In my case, the "user-specific choice" would be "INDEFINITE", but it can be a "SPECIFIC TIME" for other users.

### Supporting information

_No response_
Repository: pytorch
Issue: [XPU] test_xpu.py::TestXpuXPU::test_generic_stream_event_xpu crashed with XPU support package 2025.0
Labels: triaged,module: xpu

### 🐛 Describe the bug

```
___________________ TestXpuXPU.test_generic_stream_event_xpu ___________________
Traceback (most recent call last):
  File "/var/lib/jenkins/pytorch/test/test_xpu.py", line 288, in test_generic_stream_event
    self.assertGreater(event1.elapsed_time(event2), 0)
RuntimeError: Profiling information is unavailable as the queue associated with the event does not have the 'enable_profiling' property.

To execute this test, run the following from the base repo dir:
    python test/test_xpu.py TestXpuXPU.test_generic_stream_event_xpu
```
Refer: https://github.com/pytorch/pytorch/actions/runs/11855073324/job/33041258828#step:14:2504

### Versions

Python main: ae7f809bfcadb426f8024a8abf3f33f0ecfd5308

cc @gujinghui @EikanWang @fengyuan14 @guangyey
Repository: godot
Issue: Shader compilation errors in the output have comments removed, but empty lines kept instead
Labels: enhancement,discussion,usability,topic:shaders

### Tested versions

- Reproducible in `master` (76fa7b291455a8ba24c50005072ebdb58f8a5984)
- Reproducible in 4.3.stable

### System information

Godot v4.3.stable - Fedora Linux 41 (KDE Plasma) - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 7600M XT (RADV NAVI33) - AMD Ryzen 7 7840HS w/ Radeon 780M Graphics (16 Threads)

### Issue description

When a Godot shader has an error, the whole shader is printed to the Output dock / stdout, with a mark for where the error is.

That's not great UX, but that's not what this issue is about. The problem is that in the process of compilation we seem to strip comments, but not remove the comment lines, so for example this shader:
```glsl
shader_type spatial;

void vertex() {
	// Called for every vertex the material is visible on.
}

void fragment() {
	xx
	// Called for every pixel the material is visible on.
}

//void light() {
	// Called for every pixel for every light affecting the material.
	// Uncomment to replace the default light processing function with this one.
//}
```

Becomes this in the output:
```
  res://test.gdshader:8 - Unknown identifier in expression: 'xx'.
  Shader compilation failed.
--res://test.gdshader--
    1 | shader_type spatial;
    2 | 
    3 | void vertex() {
    4 |  
    5 | }
    6 | 
    7 | void fragment() {
E   8->  xx
    9 |  
   10 | }
   11 | 
   12 | 
   13 |  
   14 |  
   15 | 
   16 |
```

All those empty lines are where comments were present in the source, and IMO make things pretty confusing.

Ideally, I think it would be best if comments were still present in that output.

Alternatively, the lines where comments were present could be deleted, instead of just replaced by empty lines. One issue there is that the line number for where the error happens would differ in the log output and in the source shader.

### Steps to reproduce

- Add MeshInstance3D with a ShaderMaterial
- In the shader, add a compilation error somewhere (e.g. `xx` in the `vertex` function)
- See the output and compare with the source shader

### Minimal reproduction project (MRP)

[test-shader.zip](https://github.com/user-attachments/files/17777876/test-shader.zip)
Repository: vscode
Issue: Make Command Center debug launcher offer most recently used configuration first
Labels: feature-request,debug,good first issue

Type: <b>Feature Request</b>

If I most recently used the second of my debug configurations the debug status bar panel shows this:

![Image](https://github.com/user-attachments/assets/09f32884-0064-4070-b76a-0dfdd765a5cc)

But when I click on it the list that Command Center shows lacks a most-recently-used first entry, so it defaults to the first one:

![Image](https://github.com/user-attachments/assets/099e787c-939e-4e1d-8e7f-72cd77444bdc)

VS Code version: Code - Insiders 1.96.0-insider (28f7008e9b2799e3004c48c26fff3d02ec8f13d8, 2024-11-15T05:04:10.294Z)
OS version: Windows_NT x64 10.0.22631
Modes:


<!-- generated by issue reporter -->
Repository: PowerToys
Issue: Shortcut key combinations are missing in the Power Toys Shortcut Guide
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

Shortcut Guide

### Steps to reproduce

The Power Toys "Shortcut Guide" is missing important keystrokes, such as ⊞+p.

### ✔️ Expected Behavior

I was expecting an exhaustive list of keyboard shortcuts with the ⊞ key.

### ❌ Actual Behavior

Some shortcuts are missing

### Other Software

_No response_
Repository: rust
Issue: rustdoc: single comma is put on newline if it occurs after item in double ticks
Labels: T-rustdoc,C-bug,A-rustdoc-ui,T-rustdoc-frontend,E-needs-investigation

### Problem

Here is a part of the documentation in my fork of the `colstodian` crate's `lib.rs`:

```rust
//! If you also have alpha (i.e. four values instead of three), then
//! [`Color::srgba_u8`], [`Color::srgba_f32`], and [`Color::linear_srgba`]
//! are the equivalents of the above with an alpha component.
```

And here is how that gets rendered/formatted in the docs:

![Image](https://github.com/user-attachments/assets/a13ec36a-385e-472c-b303-22a5095a59c4)

Note the lonely comma on the 2nd line, this should be connected/stay with the `Color::srgba_f32` item at the end of the previous line.

I presume this is a CSS issue rather.

### Version

```text
cargo 1.84.0-nightly (4a2d8dc63 2024-11-09)
release: 1.84.0-nightly
commit-hash: 4a2d8dc636445b276288543882e076f254b3ae95
commit-date: 2024-11-09
host: x86_64-unknown-linux-gnu
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.9.0-DEV (sys:0.4.74+curl-8.9.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Ubuntu 24.10.0 (oracular) [64-bit]
```
Repository: vscode
Issue: Improve wording and flow of restart EH blocker
Labels: feature-request,polish,extensions,verification-needed,author-verification-requested

* run a debug session
* update an extension and trigger EH restart
* 😕 be confused about the wording here 

![Image](https://github.com/user-attachments/assets/0227e649-2c8c-4d99-96af-4b690fc10096)


How about a less technical language. Like 

```
Restart Extension Blocked

A debug session is still running and would be terminated otherwise

[OK]
[Restart Anyways]

```
Repository: vscode
Issue: variables view is not working as expected
Labels: bug,accessibility,notebook-variables

cc @jooyoungseo

enter a variable in the interactive repl, like `x=12`. run the focus variables view command. note that no `x` is within that table.

![Image](https://github.com/user-attachments/assets/49a4cd53-ead2-4f7b-8f43-c38f8a4a9013)
Repository: vscode
Issue: terminal quick fixes don't work for screen reader users sometimes
Labels: bug,windows,terminal-quick-fix

From @jooyoungseo

waiting for the logs

![Image](https://github.com/user-attachments/assets/8c1bbcd1-c06f-4dd3-9cc3-49d91d730ab2)
Repository: svelte
Issue: Svelte 5 Exporting $state compile problem
Labels: feature request,runes

### Describe the bug

If I want to export a shared state, the normal way is to do like this:

### Option 1
```ts
// rune.svelte.ts

export const rune = <T>(initialValue: T) => {

    let _rune = $state(initialValue);

    return {
        get value() {
            return _rune;
        },
        set value(v: T) {
            _rune = v;
        }
    };
};
```
### Option 2
This also works:
```ts
// rune.svelte.ts

export const rune = <T>(initialValue: T) => {
    const _rune = $state({ value: initialValue });
    return _rune;
};
```
### Option 3
However, if I simplify option 2, I get a compile error:
```ts
export const rune = <T>(initialValue: T) => $state({ value: initialValue });

// OR

export const rune = <T>(initialValue: T) => {
  return $state({ value: initialValue });
};
```
I get the error:
```
$state(...)` can only be used as a variable declaration initializer or a class field
```

I would expect Option 3 to compile the exact same way as option 2 !? 


### Reproduction

[REPL](https://svelte.dev/playground/2c06d586d890466e8dc7da6fb111efb7?version=5.2.0#H4sIAAAAAAAACnWPwUrEQAyGXyUEYbtQuicv7XbBg7CHPYiCF0ekliyOtJkyk66VYd5dZrbKFvWY5PuTLx656QlL3JsPEAOjI5A3gocTdUJwf3t3wByPuiOH5ZNH-RwiHRuYf2dvhqFwKYA5vjaO_uq3hoVYHJa4da3Vg-wUK9H9YKyABzsyQYCjNT2sik0s53Dx7laV4ki3hp3ABHXCs-t1pXi7-Vnnp-LUdCMFzFFoEizFjhTyf7yXN5buv2YX_jQl57NM8q4h06xFN91jvL-GegdeMczMywxdOWmEMg_JsoTLDIT4jBJLMlo-RyrFoVr-8hy-ADlJFLyzAQAA)

### Logs

```shell
Error message above.
```


### System Info

```shell
Svelte 5.2.0
```


### Severity

annoyance