sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: E0277 suggestion for changing parameter type to a reference suggests a syntax error
Labels: C-bug,A-suggestion-diagnostics,D-invalid-suggestion

On the `yew` tutorial, starting from [this working state](https://github.com/ydirson/test-yew-tutorial/tree/c56b6936e28daec35b677f138db5625553c53f27) I tried this change:

```diff
 -#[derive(Properties, PartialEq)]
-struct VideosListProps {
-    videos: Vec<Video>,
-    on_click: Callback<Video>,
-}
-
+#[autoprops]
 #[function_component(VideosList)]
-fn videos_list(VideosListProps { videos, on_click }: &VideosListProps) -> Html {
+fn videos_list(videos: Vec<Video>, on_click: Callback<Video>) -> Html {
     let on_click = on_click.clone();
     videos.iter().map(|video| {
         let on_video_select = {
```

This resulted in this build error:

```
   Compiling yew-tuto v0.1.0 (/home/user/soft/rustweb/yew-tuto)
error[E0277]: the trait bound `Vec<Video>: ImplicitClone` is not satisfied
  --> src/main.rs:16:16
   |
14 | #[autoprops]
   | ------------ required by a bound introduced by this call
15 | #[function_component(VideosList)]
16 | fn videos_list(videos: Vec<Video>, on_click: Callback<Video>) -> Html {
   |                ^^^^^^ the trait `ImplicitClone` is not implemented for `Vec<Video>`
   |
help: consider borrowing here
   |
16 | fn videos_list(&videos: Vec<Video>, on_click: Callback<Video>) -> Html {
   |                +

For more information about this error, try `rustc --explain E0277`.
```

This produces a syntax error, a more correct suggestion would be `videos: &Vec<Video>`.

### Meta

```
rustc 1.74.0 (79e9716c9 2023-11-13)
binary: rustc
commit-hash: 79e9716c980570bfd1f666e3b16ac583f0168962
commit-date: 2023-11-13
host: x86_64-unknown-linux-gnu
release: 1.74.0
LLVM version: 17.0.4
```

```
rustc 1.76.0-nightly (3f28fe133 2023-12-18)
binary: rustc
commit-hash: 3f28fe133475ec5faf3413b556bf3cfb0d51336c
commit-date: 2023-12-18
host: x86_64-unknown-linux-gnu
release: 1.76.0-nightly
LLVM version: 17.0.6
```

<details><summary>Backtrace</summary>
<p>no backtrace:

```
user@perso-dev:yew-tuto (yew-autoprops)$ RUST_BACKTRACE=1 cargo build --target=wasm32-unknown-unknown 
   Compiling yew-tuto v0.1.0 (/home/user/soft/rustweb/yew-tuto)
error[E0277]: the trait bound `Vec<Video>: ImplicitClone` is not satisfied
  --> src/main.rs:16:16
   |
14 | #[autoprops]
   | ------------ required by a bound introduced by this call
15 | #[function_component(VideosList)]
16 | fn videos_list(videos: Vec<Video>, on_click: Callback<Video>) -> Html {
   |                ^^^^^^ the trait `ImplicitClone` is not implemented for `Vec<Video>`
   |
help: consider borrowing here
   |
16 | fn videos_list(&videos: Vec<Video>, on_click: Callback<Video>) -> Html {
   |                +

For more information about this error, try `rustc --explain E0277`.
error: could not compile `yew-tuto` (bin "yew-tuto") due to previous error
user@perso-dev:yew-tuto (yew-autoprops)$ 
```

</p>
</details>


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":null}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: material-ui
Issue: [material-ui][Autocomplete] Options list scrolls to the top if more options are added after pulling the scroll handle to the bottom
Labels: bug 🐛,package: material-ui,component: autocomplete

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/p/sandbox/dark-dust-zdlhtj?file=%2Fsrc%2FDemo.tsx%3A29%2C18

Steps:

1. Open an autocomplete that loads more data on scroll.
2. Pull the scroll handle to the bottom of the options list before the data finishes loading.
3. Observe that the options list jumps to the top.


### Current behavior 😯

When manually scrolling to the bottom of an infinite-scroll options list, if the user scrolls too fast with the scroll handle the list will jump to the top as soon as data finishes loading.

![Autocomplete bug demo](https://github.com/mui/material-ui/assets/94395089/d77148be-a6a7-449f-aa97-f75e5a4ba25d)

### Expected behavior 🤔

Scroll position should not change, as observed when scrolling with other methods.

### Context 🔦

Our QA team discovered this edge case when testing that https://github.com/mui/material-ui/issues/30249 was resolved in our product. The effect is a potentially degraded user experience when using infinite-scroll autocompletes.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

Observed using latest Chrome.

```
  System:
    OS: macOS 13.6.1
  Binaries:
    Node: 18.14.1 - ~/.nvm/versions/node/v18.14.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.14.1/bin/yarn
    npm: 8.12.1 - ~/collibra/frontend/node_modules/.bin/npm
  Browsers:
    Chrome: 120.0.6099.109
    Edge: Not Found
    Safari: 17.0
  npmPackages:
    @emotion/react: 11.11.1 => 11.11.1 
    @emotion/styled: 11.11.0 => 11.11.0 
    @mui/base:  5.0.0-beta.21 
    @mui/core-downloads-tracker:  5.14.16 
    @mui/lab: ^5.0.0-alpha.140 => 5.0.0-alpha.150 
    @mui/material: 5.14.15 => 5.14.15 
    @mui/private-theming:  5.14.15 
    @mui/styled-engine:  5.14.15 
    @mui/system: 5.14.15 => 5.14.15 
    @mui/types:  7.2.7 
    @mui/utils: ^5.14.15 => 5.14.15 
    @mui/x-data-grid:  5.17.23 
    @mui/x-data-grid-pro: ^5.17.23 => 5.17.23 
    @mui/x-date-pickers:  5.0.20 
    @mui/x-date-pickers-pro: ^6.17.0 => 5.0.20 
    @mui/x-license-pro: 6.10.2 => 5.17.12 
    @mui/x-tree-view:  6.0.0-alpha.1 
    @types/react: 18.2.24 => 18.2.24 
    react: 18.2.0 => 18.2.0 
    react-dom: 18.2.0 => 18.2.0 
    typescript: 5.2.2 => 5.2.2 
```
</details>
Repository: flutter
Issue: [web:canvaskit] consider switching to transferToImageBitmap
Labels: c: performance,a: accessibility,platform-web,e: web_canvaskit,P2,team-web,triaged-web

The CanvasKit renderer currently uses `createImageBitmap` [here](https://github.com/flutter/engine/blob/9fda016022a715ee00e1ea1f888b480a871951a0/lib/web_ui/lib/src/engine/canvaskit/surface.dart#L120C61-L120C61) when rendering through an `OffscreenCanvas`. This has two issues:

* Injects an extra layer of asynchrony into frame rendering, likely delaying the frame. The code calling `rasterizeToCanvas` is invoked inside a `requestAnimationFrame`, which is already async by waiting for vsync. The extra `Promise` produced by `createImageBitmap` essentially misses the frame (although not sure if in practice the browser still manages to fit it inside the current frame if there's still budget for it).
* It uses double the amount of bitmap data during window resize. The first bitmap is created and used as the render target for the `OffscreenCanvas`, and a second bitmap is created by calling `createImageBitmap`. Since during resize the bitmap size is volatile, we need to drop both copies and create two new copies to render every frame.
Repository: godot
Issue: An error occurs in a particular situation if the argument type of a custom shader function is sampler2D.
Labels: bug,topic:shaders

### Tested versions

- Reproducible in: Godot v4.2.1.stable.

### System information

Godot v4.2.1.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 Ti (NVIDIA; 31.0.15.4592)

### Issue description

If I defined a function with an argument of `sampler2D`.
For example:
```
void test_func(sampler2D color) {
}
```
Now I have two uniforms:
```
uniform sampler2D test_samplers[2];
uniform sampler2D test_sampler;
```
It's OK when I call the function with `test_sampler`, but the console will print `servers/rendering/shader_language.cpp:5431 - Condition "n->type != Node::NODE_TYPE_VARIABLE" is true. Continuing.` if I use `test_samplers[0]` instead. It seems pass an element of a `sampler2D` array to the function will cause the alert but the shader still works.

### Steps to reproduce

Compile a shader with the code in Editor:
```
shader_type canvas_item;

uniform sampler2D test_samplers[2];

void test_func(sampler2D color) {
}

void fragment() {
	test_func(test_samplers[0]);
}
```

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: ShellTestPlatformViewVulkan does not provide impeller::Context objects
Labels: engine,P3,e: impeller,team-engine,triaged-engine

Only ShellTestPlatformViewMetal does.

Probably not very hard to fix, but may affect other tests, so filing this as anchor for TODO. Intend to follow up on it shortly.
Repository: flutter
Issue: Migrate hybrid_android_views_integration_test off of Moto G4
Labels: P3,team-android,triaged-android

https://ci.chromium.org/ui/p/flutter/builders/staging/Linux_pixel_7pro%20hybrid_android_views_integration_test/6/overview

Maybe it's because hybrid composition isn't use on the Pixel 7 Pro?

Either way, I am going to switch `hybrid_android_views_integration_test` back to running on the Moto G4, but it will probably need to be migrated to the A02.
Repository: svelte
Issue: Svelte 5: Inaccurate source maps when `lang="ts"` is enabled
Labels: bug

### Describe the bug

Source maps are seemingly inaccurate when `lang="ts"` is enabled on the `<script>` tag. This _only_ occurs when using TS in Svelte 5. Removing `lang="ts"` fixes the issue.

When presented with the following Svelte code:

![img](https://i.imgur.com/thAzfwO.png)

Errors locations are accurate in the IDE (as shown above), but are off in both the terminal output, and the error page.

![img](https://i.imgur.com/6gOYeoF.png)

### Reproduction

https://github.com/AdrianGonz97/svelte-5-ts-source-maps-reproduction

### Logs

_No response_

### System Info

```shell
  System:
    OS: Linux 5.15 Ubuntu 20.04.5 LTS (Focal Fossa)
    CPU: (24) x64 AMD Ryzen 9 5900X 12-Core Processor
    Memory: 7.95 GB / 31.30 GB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 20.10.0 - ~/.volta/tools/image/node/20.10.0/bin/node
    Yarn: 1.22.21 - ~/.volta/tools/image/yarn/1.22.21/bin/yarn
    npm: 10.2.3 - ~/.volta/tools/image/node/20.10.0/bin/npm
    pnpm: 8.10.5 - ~/.volta/bin/pnpm
    bun: 1.0.2 - ~/.bun/bin/bun
  npmPackages:
    svelte: ^5.0.0-next.26 => 5.0.0-next.26
```


### Severity

annoyance
Repository: PowerToys
Issue: FancyZones does not work with Thinkorswim windows
Labels: Issue-Bug,FancyZones-Layouts,Needs-Triage,Area-App Compat

### Microsoft PowerToys version

0.76.2

### Installation method

Microsoft Store

### Running as admin

None

### Area(s) with issue?

FancyZones

### Steps to reproduce

click and drag a thinkorswim window while pressing shift. 

### ✔️ Expected Behavior

I expect a blue outline zone that I can attach the window to but nothing happens. other apps eg firefox, chrome, edge, windows explorer work properly.

### ❌ Actual Behavior

no blue outline appears. no ability to attach to a zone.

### Other Software

[PowerToysReport_2023-12-19-16-45-33.zip](https://github.com/microsoft/PowerToys/files/13721059/PowerToysReport_2023-12-19-16-45-33.zip)
Repository: pytorch
Issue: Memory usage appears to increase if dtype is cast after Tensor.expand
Labels: module: docs,triaged,actionable

### 🐛 Describe the bug

Hi, I was debugging a memory issue in a custom module, and encountered the following strange memory behavior; Changing dtype from fp16 to fp32 shows an increase in memory usage on a tensor that was previously expanded in shape.
I am not sure if this is indeed a bug or if I am misunderstanding, but this seems to have practical implications where I get OOM in one case and not the other.

### Code illustrating issue:

```python
import torch

x = torch.randn(100, dtype=torch.float16, device="cuda")
y = torch.randn(100, dtype=torch.float16, device="cuda")

# memory is about the same before and after dtype change
print("before x fp32\n", torch.cuda.memory_summary())
x = x.to(torch.float32)
print("after x fp32\n", torch.cuda.memory_summary())

x = x.unsqueeze(-1).expand(-1, 10000)

y = y.unsqueeze(-1).expand(-1, 10000)

# memory before the dtype change is the same as the previous print statement, but memory after the dtype change increases substantially
print("before y fp32\n", torch.cuda.memory_summary())
y = y.to(torch.float32)
print("after y fp32\n", torch.cuda.memory_summary())
```

### Versions

Versions of relevant libraries:
```
[pip3] flake8==4.0.1
[pip3] flake8-polyfill==1.0.2
[pip3] gpytorch==1.11
[pip3] mypy==0.960
[pip3] mypy-extensions==0.4.3
[pip3] numpy==1.22.4
[pip3] torch==2.0.1
[pip3] torchvision==0.15.2
[pip3] triton==2.0.0
[conda] Could not collect
```

cc @svekars @brycebortree
Repository: PowerToys
Issue: Add additional characters checkbox for math symbols in quickaccent
Labels: Idea-Enhancement,Needs-Triage,Product-Quick Accent

### Description of the new feature / enhancement

I can choose all languages in quickaccent, and I can choose one of them. There are also quickaccent shortcurs for numbers like 1,2,3,4,5, also for comma, etc. These characters may be handy, so hence the request. I want to have only one language in quickaccent and additionally these keys.

### Scenario when this would be used?

Someone wants to have a clean quickaccent menu (not all world languages) when using math symbols

### Supporting information

_No response_
Repository: ant-design
Issue: Cascader多选时父级跟子级完全受控，能够选中真实的父级节点
Labels: Inactive,unconfirmed

### What problem does this feature solve?

在某些场景下，多选需要选中真实的父级节点，类似于TreeSelect组件中treeCheckStrictly为true的情况。父级跟子级完全受控。

### What does the proposed API look like?

添加 `checkStrictly` 属性，使其完全受控

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Split Windows taskbar into sections based on FancyZones.
Labels: Needs-Triage

### Description of the new feature / enhancement

I would love an option to split the Windows Taskbar into sections below Fancy Zones. I have three horizontal sections but one giant list of buttons in the Taskbar. 

### Scenario when this would be used?

Any time using multiple FancyZones on one monitor.

### Supporting information

_No response_
Repository: vscode
Issue: Terminal sticky scroll incorrect identifies the top of buffer as a command
Labels: bug,help wanted,terminal-sticky-scroll

I had a very long terminal whose lines reached the terminal's max limit, and then had an ugly sticky scroll state:

![image](https://github.com/microsoft/vscode/assets/2230985/b4f73891-3cff-4601-a657-eee70a26f638)
Repository: flutter
Issue: [pigeon] Support `@Sendable` in Swift code
Labels: c: new feature,package,team-ecosystem,p: pigeon,P2,has partial patch,triaged-ecosystem

### Use case

I set `Strict Concurrency Checking` to `complete` in Xcode 15's Build Settings, and use `@MainActor`.

Specifically, when implementing a class conforming to a protocol generated by Pigeon, I intend to have a class conforming to `@MainActor` as a property of that class. I plan to use the functions of that class to perform operations.

Furthermore, in cases where I return a struct defined by Pigeon in a completion handler when implementing functions of the protocol, if the completion handler does not conform to `@Sendable`, the following warning is issued.

````
Capture of 'completion' with non-sendable type '(Result<[CustomType], any Error>) -> Void' in a `@Sendable` closure
````

### Proposal

```swift
// pigeon generated

// I want to add @Sendable to CustomType
struct CustomType {
  var sample1: String
  var sample2: Int
}

protocol Sample {
  // I want to @Sendable before @escaping
  func fetchSample(completion: @escaping (Result<[CustomType], Error>) -> Void)
}

// implements
final class SampleImpl: Sample, Sendable {
  private let mainActorSample: MainActorSampleClass = .init()

  // I want to @Sendable before @escaping
  func fetchSample(completion: @escaping (Result<[CustomType], Error>) -> Void) {
    Task { @MainActor in
      let customType = mainActorSample.fetchSample()
      completion(customType)
    }
  }
}
```

In practice, even with the aforementioned modifications, a warning is issued at the `reply` location due to the absence of `@Sendable` on `reply` in `setMessageHandler`.

While it is desirable to eventually address this warning at the `reply` location, we will exclude it from the scope of consideration in this issue.

The reason is likely that, given the nature of passing arguments to Flutter, it is assumed that `reply` is implicitly Sendable, and this warning within the code generated by Pigeon can be temporarily ignored.
Repository: deno
Issue: improve developer experience for deno contributors working on the js runtime
Labels: docs

My experience working on the js runtime to fix an issue a while back wasn't great. I think it would be useful for the [contributing guide](https://docs.deno.com/runtime/manual/references/contributing/) to explain various things that aren't obvious to newcomers, like what primordials are or how to debug the javascript runtime in vscode.
Repository: material-ui
Issue: [base-ui][material-ui] Uncontrolled Autocomplete component do not fully reset when inside a <form> with a reset button
Labels: package: material-ui,component: autocomplete,package: base-ui,enhancement

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example without using state: https://codesandbox.io/p/sandbox/jovial-hodgkin-rczprx

Link to live example using state: https://codesandbox.io/p/sandbox/admiring-morse-s67ssl

### Current behavior 😯

When using Autocomplete component, Pressing the reset button in a form does not revert value of the Autocomplete to its default value.

If I use Autocomplete with state then it will work properly.

### Expected behavior 🤔

Changes in the value of the Autocomplete will get reset while clicking on the reset button when we are not using the state (for the first codesandbox).

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Chromium (120.0.2210.77)
  npmPackages:
    @emotion/react: ^11.11.1 => 11.11.1
    @emotion/styled: ^11.11.0 => 11.11.0
    @mui/base:  5.0.0-beta.28
    @mui/core-downloads-tracker:  5.15.1
    @mui/material: ^5.15.1 => 5.15.1
    @mui/private-theming:  5.15.1
    @mui/styled-engine:  5.15.1
    @mui/system:  5.15.1
    @mui/types:  7.2.11
    @mui/utils:  5.15.1
    @types/react: ^18.2.45 => 18.2.45
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^4.9.5 => 4.9.5
```
</details>
Repository: stable-diffusion-webui
Issue: [Bug]: A checkpoint converted to bf16 is generated as a black image.
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

Press the Create button with the bf16 checkpoint to create a black image.

### Steps to reproduce the problem

1. bf16 Check Point
2. Create Image

### What should have happened?

fp16 and fp32 are normally generated images, but bf16 is being generated as black images

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

Microsoft Edge, Other

### Sysinfo

@echo off

git pull

set PYTHON=
set GIT=
set VENV_DIR=
set CUDA_VISIBLE_DEVICES=0
set COMMANDLINE_ARGS= --opt-split-attention --autolaunch --update-all-extensions --no-half-vae --enable-insecure-extension-access --xformers --xformers-flash-attention --opt-channelslast --use-cpu adetailer --lowvram --disable-nan-check


call webui.bat

### Console logs

```Shell
The console log does not confirm any particular circumstances.
It is usually the same as the image is created.
```


### Additional information

In version 1.7.0rc, a path domain error was displayed when the bf16 model was operated.
https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/14167

The 1.7.0 official version does not display that error, but it can be generated, but it is being generated as a black image.

For me, it's 100% reproduced.
Repository: opencv
Issue: Video stream stitching
Labels: feature

### Describe the feature and motivation

I want to use the Stitcher class to stitch multiple fixed camera frames. How can I initialize the homography matrix and use the homography matrix for subsequent frames to reduce the calculation time

### Additional context

_No response_
Repository: PowerToys
Issue: PowerToys Run all white 
Labels: Issue-Bug,Product-PowerToys Run,Area-User Interface,Needs-Triage

### Microsoft PowerToys version

0.76.2

### Installation method

WinGet

### Running as admin

None

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

When I activate the PowerToys Run by pressing Alt + Space, the PowerToys Run input field pops up alright. However it is useless due to its white in white apperence.

### ✔️ Expected Behavior

![image](https://github.com/microsoft/PowerToys/assets/48091180/277de733-6bf1-467c-a531-64d4a6236f36)


### ❌ Actual Behavior

![image](https://github.com/microsoft/PowerToys/assets/48091180/a54b9148-27d4-4509-bb95-c54650d04807)


### Other Software

Bug report:
[PowerToysReport_2023-12-20-07-39-23.zip](https://github.com/microsoft/PowerToys/files/13723932/PowerToysReport_2023-12-20-07-39-23.zip)
Repository: storybook
Issue: [Bug]: Favicon default not removed with manager-head.html in Storybook 7
Labels: bug,help wanted,builder-manager,sev:S3

### Describe the bug

Favicon default not removed with manager-head.html in Storybook 7. Because of this, it is impossible to set a custom favicon


### To Reproduce

https://stackblitz.com/edit/github-1dipzi?file=package.json,.storybook%2Fpublic%2Fui.png&preset=node

### System

```bash
System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 Intel(R) Core(TM) i9-9900 CPU @ 3.10GHz
  Binaries:
    Node: 18.15.0 - C:\Program Files\nodejs\node.EXE
    npm: 9.5.0 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers: {}
  npmPackages:
    @storybook/addon-backgrounds: ^7.6.6 => 7.6.6
    @storybook/addon-controls: ^7.6.6 => 7.6.6
    @storybook/addon-docs: ^7.6.6 => 7.6.6
    @storybook/addon-links: ^7.6.6 => 7.6.6
    @storybook/addon-styling: ^1.3.7 => 1.3.7
    @storybook/addons: ^7.6.6 => 7.6.6
    @storybook/react: ^7.6.6 => 7.6.6
    @storybook/react-webpack5: ^7.6.6 => 7.6.6
    @storybook/theming: ^7.6.6 => 7.6.6
    eslint-plugin-storybook: ^0.6.15 => 0.6.15
    storybook: ^7.6.6 => 7.6.6
```


### Additional context

head storybook version 6.5.16:
<img width="374" alt="Снимок2" src="https://github.com/storybookjs/storybook/assets/34554348/0732d712-ab11-4b2f-87b8-ece1b14fc2f9">
head storybook version 7.6.6:
<img width="603" alt="Снимок" src="https://github.com/storybookjs/storybook/assets/34554348/552a5104-38f7-407c-b4bd-607f63cca0fa">
current manager-head.html:
`<link rel="icon" type="image/svg+xml" href="./ui.png" sizes="56x56" />`