sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Moved Code Alignment Is Buggy
Labels: bug,diff-editor

Notice how equal lines are not aligned:

![Image](https://github.com/microsoft/vscode/assets/2931520/5602057f-3024-4d95-8696-5a5440331a3d)

[Monaco Editor Repro](https://microsoft.github.io/monaco-editor/playground.html?source=v0.44.0-dev-20230919#XQAAAALfJQAAAAAAAABBqQkHQ5NjdMeMm-jY7SIQ9S7DNlzs5W-mwj0fe1ZCDRFc9ws9XQE0SJE1jc2VKxhaLFIw9vEWdz-byd6rEHwrDT4JrtAnMk2QsDES2C5fYZh-rj8v3bYsJHxI3X6aee-RN2Krw3yS63FeafinyZ2dT_98Cfok5BN91DsPqOBj1mXBjHPAB7D35xzm7CBrG7g4LK2pQ4fOJNLtasHnN3ZgBTs7ejwgQmruQZedqdHH_diPvLPAE-ZlRiDl4UY1_x7e4RSCZBxAqPSQw_fpPZVxu1yrij5ro1Ww54w1FuE10jlAbKj8x-bwAkdxF_qeUWtiJ0LS6UIHNogUlhDGKCWNr9EGQ_atxMMUMEvqK7tYMBjLCq1O7sddOfiaczB-htb9SMOib2m_CE8i85ICVAv2CZR25uyQH-x2t-Axt5HtdnC5Ud4_ZngN4b8aBVQXX669TpmszUE-PYTHgWeGFO3AMbWi6zmr7MFXpQqPJl2FZIswYrYiZkzDAvk3SZweLeE92UF8eA1tf6qGR0KxUpLTAsTETND-lIVrRhKcxvfCySuEZmZsMox6M3Ap3T_MRPkVk0R0WWHtC8dqbZnV-6JY-shZH94fkzVeDIzOPKyAovJH65iXyKVaefd0aY4-Qf0vNtCoYOQYzQlrrqCCiNYbE-xrYh9YyT34xjzbQpocB_RCXKR0jJhjlbDSJ1v_5ukd5lWp5Bi3IAE3oWTAAK2YMlzfz8y3tRsIlBHkXNLmYfevDYhw0Aih7ePSL5o8PSyVdFB8wrqBD2n4qJ5svi_QdSNWisPJdBjOD8DRts8z7TO40GwHcB3SYuWe9yn3anyfrBiBhQhaURDDUP7_lfKt81eVDNeLGoS7Cav3o4--ZsCECCAioRbxrfmT8QdiK4LtQrzY_hZK5Yig4dx44YMqk8H51oE4vUoRwcvMq7SFoxC5Zs8boRMhwX7FWr1Ct9VPrac_POIBL7r2qRI2dMp-i-s946v3S2KZ5dOIOFB9aEfqqtpeszuAZkeiMxXHxrnurDbS47JBvwnjPN0CtHs4UAq0ayNFkgDloqZRh80-QizjGooeIMhsUl9Yj6Qv3jkzajtX2tQKAxsaHgPOBXA4KoNhKE72YVsQi_YpUQd5LueEN63KW80YabdhcpTIjve1h7cBOxYoPe3iriC1Y-4cRk1iRsOwMyFfEquR5jmGiURY5Eu0gmL3lbjCVBV-xuQuqf62v2Lgjj34Tuc8IQNrLazIDo9YFmNPEaieJRY2DT1Ec8XvEwubFxCNuPBS89tcYAs71rB5uSQJatwaHtcz-A9AEXrR6_BjYB03CWP4mLK20Lj1vQKCE9BERasa1EeWZvRE0jRhRUEC9yFV46Oh3IOcQ0aDYi7XHRWVvbl97U6y9jjuUc37IOUd-XfXI9FvcQ93j0_-5vVDLmfYUz6Ax8QhNLBrr55Tr6eSskQUn1yG2ngM8D5kxQ1GED3WWNtexq8ipWRkHaxnkeeQTpgO9WxMCw9vMthQ12EZQ_JBgNRqLVHCmas_7fVX0vsTdnQXUxp72vZCgZ75ryXBTFr64BhgchECeFw8XFIQJA38_Mck3B5LtoLfbLoTOm26FAa_Nuge1PGjlHl1pZOogGS2uNFT0EkkH7Tu10AJh89g9_2-89sMCUUggUfU5FnDusg21MFgWaPAJPJ_GsD4e71VA52X0R4O8zVloLT8MowBhGvAfEycr85VBmutvt0lr3nZTf3vDXMPnri6QQ8js4hCROxjXBfu1F_VxsYcKTwLyWnjMUGTQHd--KmEDft750_UkJe4Kaq5pgapGOsa8JUlbP4mKDyYS68W1d6n4SEQZG70oKwVG3yz3ApFi-eYIazdq7uG9_FLHk01IfCgqcvNl2zgwsLz9-QvzQmMYuAXfQW5KgaqMO38yUjxoN6GDDikexDDESFq4T1qbbyXr_ZaIgi6dL6ZbGi-7PXepgZueJlsE3xEAghW-a9GfjSissG4__BYb9OqEIyFjpQm7WBU_VqWoyw1bbpKSaBVfJeRUWwb2qZF-_9QGNr1GotNhsWULMAI-aj5nrasFynYbu4lXlPqNY6yaLv3Fe2uh9noffnaYY0p1H6Asdt0W_g1fHsxqvjWyqy8AGec_Oju7mv68CrjO9VjQU5kIzcUlKt4052zPZlyxCMo4LqtPEIXH6gvk3feKNs4RJLuT47TrsSR3zLrP-QM_dqrToEL9z108D9DupQN6RDCEvxvgvUZuC1R1o4Bm3_nit_3CkPdqn279Rj8FokEBSMv8aoxEH-e6ZDbvt-HvCNx_LW87a4HFdmOFkEZqQ5n_ci_o7AH2OZhas2b3jHkQA49Dcy7h7sb823H90o3TLfNaUQr890N9Ap7Kfc1ay4qLzX3H6qNU_agHJVUGQHbtyHJ6dSGjTM09t7F5GCAon6aozHwybaPaoBOD_8XOW2zIvDBAhTB2qOhbFQl0gaGjfTOiHkn0eczVV0PnBPxhyJTqRAm0RwSeeWcnvDYqAYsKegsbRMVMLrukc_dHHvxRyZpOUeaKixH2BfJNpYfhPDVyoasU_uJmVEN0q0C3vYVf2kuMhEAQdMyQBPfVpDw5TmSIq0Lrv_6S1oA)
Repository: vscode
Issue: Bug: Links resolved incorrectly after editing - timing issue
Labels: feature-request,editor-core

Current version of vscode.dev/
Version: 1.82.2
Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
Date: 2023-09-14T05:49:52.290Z
Browser: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/116.0.0.0 Safari/537.36

TLDR: Links only resolved to their saved version and when changing a link without saving the link will point to the prior target!

Steps to Reproduce:

1. Make sure auto-save is not turned on
2. Create any file
3. Paste a link into the file, e.g. https://aws.amazon.com/ecs/
4. Save the file
5. Hold ctrl/cmd and click on the link. You will end up on https://aws.amazon.com/ecs/
6. Now change the link to https://aws.amazon.com/ecs2/ BUT DO NOT SAVE THE FILE
7. Hold ctrl/cmd and click on the link. You will end up on https://aws.amazon.com/ecs/ but you would expect to end up on https://aws.amazon.com/ecs2/ (note ecs)

https://github.com/microsoft/vscode/assets/77630834/fca6644a-4b13-4470-966c-42abc4204c34

This is a continuation of https://github.com/microsoft/vscode/issues/180391
Repository: godot
Issue: Godot crash in Abandoned Spaceship Demo project (potential import bug)
Labels: bug,topic:import,crash

### Godot version

4.1

### System information

Linux Mint 21.2 (Victoria) - integrated Intel(R) HD Graphics 620 (KBL GT2) () - Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 Threads)

### Issue description

I was checking the "Abandoned Spaceship Demo" scene in Asset library projects (github link https://github.com/perfoon/Abandoned-Spaceship-Godot-Demo)
this project is made in Godot 4.0 so it had to autoconvert to 4.1, during playing with the scene Godot crashed a lot. i managed to reduce it to conflicts between a .glb scene and it's .tscn scene

see the video below (ignore the "Load errors" dialog for a moment)

https://github.com/godotengine/godot/assets/77773850/47f01986-511d-4945-8038-2a624c55b925

now back to the "Load errors" dialog.
it said that some items in .tscn file are renamed to fix the crash (the items with @ in their name and the :warning: sign) and now we have to re-save the scene. This does fix the crash but the question arises that how the duplicate nodes got created in the first place

I also tested this project in godot 4.0 and everything went fine

here's a comparison of node heirarchy of `space_craft_hangar.tscn` in 4.1 compared to 4.0 (download from asset library each time)

![result](https://github.com/godotengine/godot/assets/77773850/a3de1c5e-336f-4467-804c-31a11a7fdcfc)


### Steps to reproduce

as shown in above video

### Minimal reproduction project

too large to upload the original, and was unable to make a separate project a github link is given below
(github link https://github.com/perfoon/Abandoned-Spaceship-Godot-Demo)
Repository: vscode
Issue: Git - WSL: Change/Delete Conflicts Have Weird URLs
Labels: bug,git,WSL

Note how the right side is read-only in the diff editor, but writable once I go to the original file:

![Image](https://github.com/microsoft/vscode/assets/2931520/c01e5aa9-09af-4474-a71d-5fdc6c4c11b3)
Repository: next.js
Issue: asPath on the server does not match the requested URL (custom server)
Labels: bug,Pages Router

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/gudvinga/next-as-path-issue

### To Reproduce

1. Start application on development (yarn serve)
2. Open http://localhost:3000/i-am-fake/as-path/page
3.  Get an error

### Current vs. Expected behavior

### Current:
When I go to the page http://localhost:3000/i-am-fake/as-path/page I get the error `"Error: The text content does not match the HTML displayed by the server"` because the asPath on the server is not match request URL  (and doesn't match router.asPath from useRouter)

```
Unhandled Runtime Error
Error: Text content does not match server-rendered HTML.
Warning: Text content did not match. Server: "/" Client: "/i-am-fake/as-path/page"
See more info here: https://nextjs.org/docs/messages/react-hydration-error
```

### Expected:
asPath from `context` in getInitialProps should return the same value as `router.asPath` from useRouter on the client.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:22:52 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T8103
    Binaries:
      Node: 16.18.0
      npm: 9.2.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.35
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.2.2
    Next.js Config:
      output: N/A
```


### Which area(s) are affected? (Select all that apply)

Data fetching (gS(S)P, getInitialProps)

### Additional context

I tested my copy on different versions and the first one to introduce the bug was "`13.4.13`", since reverting to "`13.4.12`" works
Repository: stable-diffusion-webui
Issue: [Bug]: Webui connects to cloudflare.
Labels: upstream,gradio

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What happened?

I am seeing in ublock origin that the webui connects to cloudflare. Perhaps this is from gradio but it should be redirected.

Why does a local UI have to phone home to a 3rd party not even related to the project.

### Steps to reproduce the problem

Open the webui. Check Ublock advanced tab.


### What should have happened?

Only see local addresses

### Sysinfo

Dev branch, linux.

### What browsers do you use to access the UI ?

Mozilla Firefox, Google Chrome

### Console logs

```Shell
Nothing in console.
```


### Additional information

_No response_
Repository: vscode
Issue: Improve Emitter.toString
Labels: feature-request,editor-core,engineering

With https://github.com/microsoft/vscode-js-debug/pull/1802, it is possible to customize how `this` in a stack frames is rendered.

It would be very handy for debugging to have a nice representation of `Emitter.fire`.
I could imagine that emitter options allow to pass in the owner like this:
```ts
export class ElementSizeObserver extends Disposable {
        ...
	private _onDidChange = this._register(new Emitter<void>({ owner: this }));
        ...
}
```
or this:
```ts
export class ElementSizeObserver extends Disposable {
        ...
	private _onDidChange = this._register(new Emitter<void>({}, this));
        ...
}
```

Then, when building VS Code from source, the owner could be stored inside the `Emitter` and used to find out the field the emitter is stored in.
Instead of `Emitter.fire`, we could then show `ElementSizeObserver.onChange.fire`

@connor4312 what do you think of this?

---

Replace
```
=(.*)new Emitter(.*)\(\)
```
with
```
=$1new Emitter$2({ owner: this })
```

Then debugging could look like this:



![Image](https://github.com/microsoft/vscode/assets/2931520/811a0b4c-e565-4e93-b5ad-93f4e6df784f)
Repository: vscode
Issue: vscode seems don't handle newline and tab correctly in snippet string provided by inlineCompletionProvider
Labels: bug,inline-completions

<!-- ⚠️⚠️ 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.82.2 (Universal)

- OS Version: MacOS 12.1

Steps to Reproduce:
[inline_completion.zip](https://github.com/microsoft/vscode/files/12647227/inline_completion.zip)
[inline_badcase.zip](https://github.com/microsoft/vscode/files/12647285/inline_badcase.zip)
https://github.com/microsoft/vscode/assets/4253318/deee8444-00b0-4b20-8ed9-603ee44e98b0

![屏幕录制2023-09-18-19 54 48](https://github.com/microsoft/vscode/assets/4253318/927a3c0c-06f5-4007-b912-e32828e93126)

1. Unzip the inline_inline_badcase.zip file, which contains the problematic case file.
2. Unzip the inline_completion.zip file and build the test extension. Then, run the extension and open the above-mentioned case file as the workspace.  (npm install && npm run vscode:prepublish ,  then run it)
3. Go to line 5 in the editor and type something before the word 'else:' end. You will notice that some ghost inline completion text is generated, and its format is correct. However, after pressing the tab key to accept it, the file becomes corrupted, with additional tabs inserted at the beginning of each line. 
   
I have also attached a GIF to demonstrate this issue. Thank you for any assistance in resolving this problem.
Repository: next.js
Issue: Async generateMetadata hangs the app without any visible sign of loading 
Labels: Metadata

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/wiwo-dev/generatemetadata-loading-issue
https://codesandbox.io/p/github/wiwo-dev/generatemetadata-loading-issue/main 

### To Reproduce

1. Run the application using the command: `yarn run dev`.

2. Navigate to the root path (`/`). Here, you'll find two lists of "users" retrieved from jsonplaceholder. The list at the top has the problem as it uses generateMetadata. The one at the bottom doesn't use generateMetadata.

3. The top list contains links to `/user/[userId]`, and these links have a `generateMetadata` function that fetches data. Upon clicking these links, for the initial 3 seconds, there is no visible loading indication, making users believe that something might be wrong with the link.

4. In contrast, if you click on any of the links in the bottom list, which leads to `/user-no-metadata/[userId]` that doesn't use ```generateMetadata```, you'll notice that a Loading state is triggered by Suspense, providing a clear loading indication.

### Current vs. Expected behavior

**Current behaviour**
When a user navigates to a page containing a `generateMetadata` function that fetches data from a slowly working API, there's a problem. The application appears to hang, providing no indication that it's actively loading. Notably, the `fetch` operation within `generateMetadata` doesn't trigger React's Suspense, and the browser also fails to display any loading indicators.

To simulate a slow API response, a `setTimeout` is intentionally used within the `getUsers` function.

I encountered this issue while working on a project with a tens of thousands number of subpages, and it's highly likely that a given subpage will be opened for the first time and only once, with new entries continually being added.


**Expected behaviour** 
It should trigger the Suspense or show any kind of loading indicator in the browser so the user knows that something is happening under the hood and wait for the page to be displayed.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:41 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.7.0
      npm: 8.15.0
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant Packages:
      next: 13.4.20-canary.36
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
    Next.js Config:
      output: N/A
```


### Which area(s) are affected? (Select all that apply)

Metadata (metadata, generateMetadata, next/head)

### Additional context

Is there a way to display a loading state or any form of indication that something is loading while still utilising the `generateMetadata` function to fetch metadata information from a slow API?
Repository: tensorflow
Issue: BMP decode channels = 1 support
Labels: stat:awaiting tensorflower,type:feature,comp:ops,TF 2.13

### Issue type

Feature Request

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

binary

### TensorFlow version

2.13.0

### Custom code

No

### OS platform and distribution

_No response_

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

`decode_bmp` to support `channels=1`

This seems like an arbitrary limitation to not support this for BMP formats.

### Standalone code to reproduce the issue

```shell
import tensorflow

image = tensorflow.image.decode_image(bmp_bytes, channels=1)
```


### Relevant log output

```shell
`tensorflow.python.framework.errors_impl.InvalidArgumentError: {{function_node __wrapped__DecodeImage_device_/job:localhost/replica:0/task:0/device:CPU:0}} `channels` must be 0, 3 or 4 for BMP, but got 1 [Op:DecodeImage] name:`
```
Repository: opencv
Issue: videoio inferace write return void
Labels: bug,category: videoio

### System Information

OpenCV version: 4.8.0
Operating System / Platform: Ubuntu 20.04
Compiler & compiler version: GCC 9.3.0

### Detailed description


![image](https://github.com/opencv/opencv/assets/24822418/c9fa8733-d8b7-42a6-b34e-74d93d962499)
https://github.com/opencv/opencv/blob/4.x/modules/videoio/src/cap_gstreamer.cpp
In the gstreamer back-end compiled by opencv, I use the videowriter interface to push the stream to the server. If there is an interruption, I need a return mechanism. In the cap_gstreamer.cpp code, writer has a return value. Until CvVideoWriter, but in the IVideoWriter class write interface return value becomes empty, I want to open, so that I know that I can not push to the server, can return the user error message.

### Steps to reproduce

https://github.com/opencv/opencv/blob/4.x/modules/videoio/src/cap_gstreamer.cpp

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: go
Issue: log/slog: non-top level slog.Value marshals to empty json document  
Labels: Documentation,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->
slog.Value always json.marshals to an empty document, "{}", which to me was surprising behavior when using JsonHandler.  If a slog.Value is embedded in a logged non-slog.Value, for example a slice, it will effectively omit data.  On the other hand any tree of Values and Attrs passed directly to the log functions, without an intervening non-slog.Value object, marshals and logs properly.  I expect a slice, or any other non-slog.Value type, containing an slog.Value to marshal to json with the slog.Value's represented value.  TextHandler produces the expected logs for the same pattern.

### What version of Go are you using (`go version`)?
go1.21.0 darwin/arm64

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
arm64, darwin (MacOS Ventura 13.5.2)

### What did you do?
Original discussion at https://groups.google.com/g/golang-nuts/c/ZvlSL76RNaw/m/N1L_5f0vAQAJ?utm_medium=email&utm_source=footer
Demonstration at https://goplay.tools/snippet/H26amsQBiYG
There are other, arguably simpler ways to achieve my fundamental goals and I'm not blocked; I still find the behavior below to be surprising. 

I logged, using slog and a JsonHandler, values containing types other than slog.Value (e.g., slices) which in turn contain slog.Value.  My goal was to use LogValuers to redact object fields by in turn calling LogValue on component objects.  The "outer object" has a slice of the inner objects and so the outer object's LogValue returns something resembling AnyValue([]slog.Value).

I additionally directly marshaled slog.Value.

### What did you expect to see?
I expected slog to log the json representation of the "outer object" with a field containing the list of "inner objects".
I expected json-marshaled slog.Value to produce json representing the value.

Alternatively, the slog documentation (or specifically JsonHandler) could state that no non-slog.Value object passed to a log method may contain an slog.Value, and that LogValuers must maintain this invariant.

### What did you see instead?
A list of empty objects: [{}, {}, {}]
slog.Value marshals to '{}'
Repository: tauri
Issue: [feat][Windows] Change default install location 
Labels: type: feature request,platform: Windows,scope: bundler

### Describe the problem

Somewhat related to https://github.com/tauri-apps/tauri/issues/7603, but many apps (iirc it's also the default for some electron bundlers?) Install the programs in `AppData/Local/Programs` instead of `AppData/Local` and considering the linked issue we may wanna think about having an actual config for it.

### Describe the solution you'd like

A config that allows users to select between these for example:
- `AppData/Local/<appname>/`
- `AppData/Local/<company>/<appname>/`
- `AppData/Local/programs/<appname>/`
- `AppData/Local/programs/<company>/<appname>/`

And imo the company name should be an option for the Program Files variant too.

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: svelte
Issue: `#each` key is a pitfall
Labels: compiler

### Describe the problem

Again and again people have issues with `#each` because they insert into/remove from/sort the source array without using a key.

Keys are explained both in the docs and the tutorial but maybe Svelte is just *a bit too accessible* because apparently people sometimes read neither. As a result they do not even know about keying.

### Describe the proposed solution

I do not have a concrete solution to this but thought about some options:
- It could be enforced on the language level, e.g. by always requiring a key.  
  The obvious downside would be that everything gets more verbose and it would be a breaking change.
- Maybe potential issues could be detected by code analysis.  
  If not very reliably maybe only output dev-mode console warnings.
- Shift the issue to IDE language tooling, e.g. maybe an inlay hint could be shown when no key is specified, something like:  
  ![image](https://github.com/sveltejs/svelte/assets/834235/13e500fe-50bf-4b47-8b93-718d45144342)  
  Ideally that could be hover to show more information and maybe even clicked to insert a template like this, selecting the property name:
  ![image](https://github.com/sveltejs/svelte/assets/834235/545276ba-d9a2-4145-bd27-d9f2f2797910)  
  (For people who don't want the additional noise, a configuration option would then be nice.)

### Alternatives considered

(see above)

### Importance

nice to have