sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: An unexpected expanded result from procedural macro
Labels: A-pretty,T-compiler,C-bug,A-proc-macros

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code to check the expanded HIR by flag -Z unpretty=hir:

```rust
// file proc_macro
extern crate proc_macro;

use proc_macro::TokenStream;
use quote::quote;
use syn::{parse_macro_input, Expr};

#[proc_macro]
pub fn mdriver(input: TokenStream) -> TokenStream {
    let expr = parse_macro_input!(input as Expr);

    let expanded = quote! {
        fn foo() {
            #expr?;
        }
    };

    TokenStream::from(expanded)
}

//file call the macro
mdriver!(0..10);
```

I expected to see this happen: 
```rust
fn foo() {
        match #[lang = "branch"](#[lang = "Range"]{ start: 0,  end: 10,}) {
                #[lang = "Break"] {  0: residual } =>
                    #[allow(unreachable_code)]
                    return #[lang = "from_residual"](residual),
                #[lang = "Continue"] {  0: val } =>
                    #[allow(unreachable_code)]
                    val,
            };
    }
```

Instead, this happened: 
```rust
fn foo() {
        #[lang = "Range"]{
            start: 0,

            end:
                match #[lang = "branch"](10) {
                        #[lang = "Break"] {  0: residual } =>
                            #[allow(unreachable_code)]
                            return #[lang = "from_residual"](residual),
                        #[lang = "Continue"] {  0: val } =>
                            #[allow(unreachable_code)]
                            val,
                    },};
    }
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.80.0-nightly (ef0027897 2024-05-12)
binary: rustc
commit-hash: ef0027897d2e9014766fb47dce9ddbb925d2f540
commit-date: 2024-05-12
host: x86_64-unknown-linux-gnu
release: 1.80.0-nightly
LLVM version: 18.1.4
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
<backtrace>
```

</p>
</details>
Repository: HelloGitHub
Issue: 【开源推荐】简易语音工具箱，提供了包括语音模型训练在内的多种自动化音频处理功能
Labels: Python 项目

## 推荐项目

<!-- 这里是 HelloGitHub 月刊推荐项目的入口，欢迎自荐和推荐开源项目，唯一要求：请按照下面的提示介绍项目。-->


<!-- 点击上方 “Preview” 立刻查看提交的内容 -->


<!--仅收录 GitHub 上的开源项目，请填写 GitHub 的项目地址-->
- 项目地址：https://github.com/Spr-Aachen/Easy-Voice-Toolkit 

<!--请从中选择（C、C#、C++、CSS、Go、Java、JS、Kotlin、Objective-C、PHP、Python、Ruby、Rust、Swift、其它、书籍、机器学习）-->
- 类别：Python

<!--请用 20 个左右的字描述它是做什么的，类似文章标题让人一目了然 -->
- 项目标题：简易语音工具箱

<!--这是个什么项目、能用来干什么、有什么特点或解决了什么痛点，适用于什么场景、能够让初学者学到什么。长度 32-256 字符-->
- 项目描述：一个基于开源语音项目实现的简易语音工具箱，提供了包括语音模型训练在内的多种自动化音频功能。[开发者介绍视频](https://www.bilibili.com/video/BV1uJ4m157P2)：简易语音工具箱v1.0

<!--令人眼前一亮的点是什么？类比同类型项目有什么特点！-->
- 亮点：音频处理、语音识别、语音转录、数据集制作、模型训练、语音合成，功能依次关联，能够形成一套完整的工作流

- 截图：目前各项功能对语言的支持情况如下：

<table border = "1">
    <tr>
        <th style = "text-align:center;">工具<br>Tool</th>
        <th style = "text-align:center;">中文<br>Chinese</th>
        <th style = "text-align:center;">英文<br>English</th>
        <th style = "text-align:center;">日文<br>Japnese</th>
    </tr>
    <tr>
        <th style = "text-align:center;">音频处理<br>Audio Processor</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
    </tr>
    <tr>
        <th style = "text-align:center;">语音识别<br>Voice Recognizer</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
    </tr>
    <tr>
        <th style = "text-align:center;">语音转录<br>Voice Transcriber</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
    </tr>
    <tr>
        <th style = "text-align:center;">数据集制作<br>DataSet Creator</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
    </tr>
    <tr>
        <th style = "text-align:center;">模型训练<br>Voice Trainer</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
    </tr>
    </tr>
        <th style = "text-align:center;">语音合成<br>Voice Converter</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
        <th style = "text-align:center;">&#10004</th>
</table>
Repository: rust
Issue: The extra newline in unpretty=hir
Labels: A-pretty,T-compiler,C-bug,requires-nightly

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code when dump the hir by -Z unpretty=hir:

```rust
// file: procedural macro
extern crate proc_macro;

use proc_macro::TokenStream;
use quote::quote;
use syn::{parse_macro_input, Expr};

#[proc_macro]
pub fn mdriver(input: TokenStream) -> TokenStream {
    let body = parse_macro_input!(input as Expr);

    let expanded = quote! {
        fn main() {
            #body
        }
    };

    TokenStream::from(expanded)
}

// file: macro call
mdriver!({
    println!("Hello, world!");
});

mdriver!({
    println!("Hello, world!");
});

mdriver!({
    println!("Hello, world!");
});

mdriver!({
    println!("Hello, world!");
});

mdriver!({
    println!("Hello, world!");
});


```

I expected to see this happen:
```rust
fn main() {
        {
                {
                        ::std::io::_print(format_arguments::new_const(&["Hello, world!\n"]));
                    };
            }
    }
fn main() {
        {
                {
                        ::std::io::_print(format_arguments::new_const(&["Hello, world!\n"]));
                    };
            }
    }
....................
```

Instead, this happened:
```rust
fn main() {
        {
// unexpected newline here








                {
                        ::std::io::_print(format_arguments::new_const(&["Hello, world!\n"]));
                    };
            }
    }
fn main() {
        {
                {
                        ::std::io::_print(format_arguments::new_const(&["Hello, world!\n"]));
                    };
            }
    }
...........
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.80.0-nightly (ef0027897 2024-05-12)
binary: rustc
commit-hash: ef0027897d2e9014766fb47dce9ddbb925d2f540
commit-date: 2024-05-12
host: x86_64-unknown-linux-gnu
release: 1.80.0-nightly
LLVM version: 18.1.4
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
<backtrace>
```

</p>
</details>
Repository: PowerToys
Issue: The title of the "Always On Top" tool missing translation and the translation is not very reasonable.
Labels: Issue-Bug,Area-Localization,Priority-1,Loc-Sent To Team,Issue-Translation

### Microsoft PowerToys version

0.80.1

### Utility with translation issue

Always on Top

### 🌐 Language affected

Chinese (Simplified)

### ❌ Actual phrase(s)

![屏幕截图 2024-05-15 151746](https://github.com/microsoft/PowerToys/assets/89643991/368223d8-ab05-4b82-9f4b-254b084e1009)


### ✔️ Expected phrase(s)

I think "Always on Top" can be translated as "始终置顶", which better reflects the function of the tool.
This translation also seems to have appeared in the previous version [#30816](https://github.com/microsoft/PowerToys/issues/30816), but I think the translation [#30816](https://github.com/microsoft/PowerToys/issues/30816) (窗口置顶器) is a bit redundant.

### ℹ Why is the current translation wrong

I think the title of the tool should also be translated, just like any other tool.
And I think the current Chinese translation (前端显示) is not quite in line with the understanding of ordinary people when using computers, and the word "前端" does not reflect "Top" well.
Repository: flutter
Issue: [web:tool] update --web-renderer option to account for html deprecation, and wasm support
Labels: platform-web,P2,e: wasm,e: web_skwasm,team-web,triaged-web

### Document Link

https://docs.flutter.dev/platform-integration/web/wasm

### What problem are you solving?

The command flutter build web --web-renderer auto can automatically select between html and canvaskit based on the environment. With the new Flutter version 3.22.0, Flutter Web now supports WASM. If I want the compiled web to adapt to the environment and automatically select between html, canvaskit, and wasm, can I also use the --web-renderer auto command?
Repository: TypeScript
Issue: Bad error when using `import()` type within JSDoc tag `@implements`
Labels: Bug,Fix Available

### 🔎 Search Terms

- `import`
- `@implements`
- `2304`

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about the JSDoc tag [`@implements`](https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html#implements)

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.5.0-beta&filetype=js#code/PQKhAIAEEsFsAcA2BTWyB2AXAzuA3nPAPYBOmAFAEQCGlAlAHQBCAvuCMAFADGi12uAIL4WQA

### 💻 Code

```js
/** @implements {import("a").B} */
class A {}
```

### 🙁 Actual behavior

Two TypeScript errors:

1. `Cannot find name 'import'.` (2304)
2. `'}' expected.` (2304)

<img width="469" alt="Screenshot 2024-05-15 at 5 59 00 PM" src="https://github.com/microsoft/TypeScript/assets/1754873/0cd66650-482b-477b-a1c0-dc326ac5d077">

### 🙂 Expected behavior

TypeScript should allow using `import()` types within the type of the JSDoc tag [`@implements`](https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html#implements).

### Additional information about the issue

A workaround is to use a JSDoc `@typedef` to import the type under an alias, and then use that alias within the JSDoc tag `@implements` type, e.g:

```js
/** @typedef {import("a").B} B */

/** @implements {B} */
class A {}
```
Repository: next.js
Issue: Canonical link doesn't accept search params on root path
Labels: bug,Metadata

### Link to the code that reproduces this issue

https://codesandbox.io/p/github/ioancruso/nextjs-bug-reproduction/main

### To Reproduce

1. Start the aplication
2. Go to main page and press the button to go to a random page.
3. Check the link tag with rel="canonical"

### Current vs. Expected behavior

Since I've set the metadataBase URL in the layout and specified the path in the page file, the link should include the path along with the search parameters I've set, but it doesn't happen. It only displays the default metadataBase URL. This issue arises only when the path contains search parameters (e.g., "?something=something"). The strange thing is that it only occurs on the root path ("/"). I've included another page in a folder, and there the path is shown correctly. 

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.12.0
  npm: 10.5.0
  Yarn: 1.22.19
  pnpm: 8.15.6
Relevant Packages:
  next: 14.3.0-canary.63 // Latest available version is detected (14.3.0-canary.63).
  eslint-config-next: N/A
  react: 19.0.0-beta-4508873393-20240430
  react-dom: 19.0.0-beta-4508873393-20240430
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Metadata

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed)

### Additional context

_No response_
Repository: ollama
Issue: Streaming Chat Completion via OpenAI API should support stream option to include Usage
Labels: feature request

In streaming mode the OpenAI chat completion has a new parameter to include Usage information after the Chunks. You just add a `{ "include_usage": true }` to the request.

Then the final chunks will look like this:

```
...
data: {"id":"chatcmpl-9P4UJf7DEdyXVro2VOMRMT9qKR0bC","object":"chat.completion.chunk","created":1715762479,"model":"gpt-3.5-turbo-0125","system_fingerprint":null,"choices":[{"index":1,"delta":{},"logprobs":null,"finish_reason":"stop"}],"usage":null}
data: {"id":"chatcmpl-9P4UJf7DEdyXVro2VOMRMT9qKR0bC","object":"chat.completion.chunk","created":1715762479,"model":"gpt-3.5-turbo-0125","system_fingerprint":null,"choices":[{"index":2,"delta":{},"logprobs":null,"finish_reason":"stop"}],"usage":null}
data: {"id":"chatcmpl-9P4UJf7DEdyXVro2VOMRMT9qKR0bC","object":"chat.completion.chunk","created":1715762479,"model":"gpt-3.5-turbo-0125","system_fingerprint":null,"choices":[],"usage":{"prompt_tokens":24,"completion_tokens":58,"total_tokens":82}}
data: [DONE]
```

The final chunk contains no choices, but a `usage`:

```
"usage":{"prompt_tokens":24,"completion_tokens":58,"total_tokens":82}
```

This usage is over all the generations from this stream.
Repository: PowerToys
Issue: Microsoft Edge will be open a new window when scribe/select any text in webpage.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.80.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Only enabled Keyboard Manager. 
![Weixin Image_20240515165633](https://github.com/microsoft/PowerToys/assets/3435611/c6716257-0369-4186-8659-d5d34069fe50)
![Weixin Image_20240515172632](https://github.com/microsoft/PowerToys/assets/3435611/7011dded-b430-4854-8354-5f912a48dd8d)



### ✔️ Expected Behavior

Microsoft Edge will be open a new window when scribe/select any text in webpage.

### ❌ Actual Behavior

I recorded a video : https://www.youtube.com/watch?v=rRfD_xiD6yY


### Other Software

Windows11
Repository: flutter
Issue: Linux_android new_gallery_opengles_impeller__transition_perf is 2.02% flaky
Labels: P2,c: flake,team-engine,triaged-engine

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Linux_android new_gallery_opengles_impeller__transition_perf"
}
-->

The post-submit test builder `Linux_android new_gallery_opengles_impeller__transition_perf` had a flaky ratio 2.02% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20new_gallery_opengles_impeller__transition_perf/1082
Commit: https://github.com/flutter/flutter/commit/13cd57a7eeb6827163516dc8e782a8a7643460b9

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20new_gallery_opengles_impeller__transition_perf/1082
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_android%20new_gallery_opengles_impeller__transition_perf/1065

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux_android%20new_gallery_opengles_impeller__transition_perf

Please follow https://github.com/flutter/flutter/wiki/Reducing-Test-Flakiness#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: storybook
Issue: [Bug]: Vue KeepAlive onActivated dose NOT work in storybook decorators
Labels: bug,help wanted,vue3

### Describe the bug

See Reproduce:
As story title said, in 'On Activated Dose Not Invock', `onActivated` dosen't be called.
```js
export default {
  title: 'Example/Page2',
  component: Page,
  decorators: [
    (story) => ({
      components: { story },
      template: `<KeepAlive><story /></KeepAlive>`, // differece: use story, not Page
    }),
  ],
};
```
![image](https://github.com/storybookjs/storybook/assets/7044628/2aa10bcf-fe19-4d97-b1d0-2e170f80d3d4)

But in `Keepalive Works Fine`, `onActivated`is called.
```js
export default {
  title: 'Example/Page',
  component: Page,
  decorators: [
    (story) => ({
      components: { Page },
      template: `<KeepAlive><Page /></KeepAlive>`,
    }),
  ],
};
```
![image](https://github.com/storybookjs/storybook/assets/7044628/b2fb2d47-7bb3-4bb8-818a-deb5718a6375)


### To Reproduce

https://stackblitz.com/edit/github-lfs33b

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.4.1
    CPU: (12) arm64 Apple M2 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
    pnpm: 8.14.1 - ~/.nvm/versions/node/v18.15.0/bin/pnpm <----- active
  Browsers:
    Chrome: 124.0.6367.158
    Safari: 17.4.1
```


### Additional context

_No response_
Repository: rust
Issue: Unclear lifetime mismatch error with anonymous lifetimes
Labels: A-diagnostics,T-compiler

### Code

```Rust
struct X;

impl std::ops::Add<&X> for &X {
    type Output = X;

    fn add(self, _rhs: Self) -> Self::Output {
        X
    }
}
```


### Current output

```Shell
error[E0308]: method not compatible with trait
 --> src/main.rs:8:5
  |
8 |     fn add(self, _rhs: Self) -> Self::Output {
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ lifetime mismatch
  |
  = note: expected signature `fn(&X, &X) -> X`
             found signature `fn(&X, &X) -> X`
note: the anonymous lifetime as defined here...
 --> src/main.rs:5:20
  |
5 | impl std::ops::Add<&X> for &X {
  |                    ^
note: ...does not necessarily outlive the anonymous lifetime as defined here
 --> src/main.rs:5:20
  |
5 | impl std::ops::Add<&X> for &X {
  |                    ^

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


### Desired output

In the first part:
```Shell
  = note: expected signature `fn(&X, &X) -> X`
             found signature `fn(&X, &X) -> X`
```
The different lifetimes should be shown since no difference is visible right now.

In the second part, one arrow should point at the right `&X`.


### Rationale and extra context

_No response_

### Other cases
When annotating the impl with two different lifetimes, the error message becomes more explanatory:

```Rust

impl<'a, 'b> std::ops::Add<&'a X> for &'b X {
    type Output = X;

    fn add(self, _rhs: Self) -> Self::Output {
        X
    }
}
```
produces
```Shell
error[E0308]: method not compatible with trait
  --> src/main.rs:16:5
   |
16 |     fn add(self, _rhs: Self) -> Self::Output {
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ lifetime mismatch
   |
   = note: expected signature `fn(&'b X, &'a X) -> X`
              found signature `fn(&'b X, &'b X) -> X`
note: the lifetime `'a` as defined here...
  --> src/main.rs:13:6
   |
13 | impl<'a, 'b> std::ops::Add<&'a X> for &'b X {
   |      ^^
note: ...does not necessarily outlive the lifetime `'b` as defined here
  --> src/main.rs:13:10
   |
13 | impl<'a, 'b> std::ops::Add<&'a X> for &'b X {
   |          ^^

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


### Rust Version

```Shell
rustc 1.78.0 (9b00956e5 2024-04-29)
binary: rustc
commit-hash: 9b00956e56009bab2aa15d7bff10916599e3d6d6
commit-date: 2024-04-29
host: x86_64-unknown-linux-gnu
release: 1.78.0
LLVM version: 18.1.2
```


### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: ollama
Issue: openai.error.InvalidRequestError: model 'deepseek-coder:6.7b' not found, try pulling it first
Labels: bug

### What is the issue?

docker run -d --gpus="device=0" -v ollama:/root/.ollama -p 8010:11434 --name ollama ollama/ollama
docker exec -it ollama ollama run deepseek-coder:6.7b

I got the error in the title when I called it on port 8010 on another computer

### OS

Linux

### GPU

Nvidia

### CPU

_No response_

### Ollama version

_No response_
Repository: storybook
Issue: [Bug]: Example Code Not Functioning Without 'args' Variable
Labels: question / support,block: source

### Describe the bug

There is an issue when writing a story for Storybook where the example code does not function unless the 'args' variable is included.

Workaround:
The issue is resolved when the first line is changed to include the 'args' variable:

`const Template6: StoryFn<typeof Chip> = (args) => (`

Thank you!

### To Reproduce

Create a story using the following code:

```
const Template6: StoryFn<typeof Chip> = () => (
    <RowContainer>
        <Chip  type="information" size="large" label="Chip with icon" icon={<HelpIcon color="inherit" />} />
    </RowContainer>
);

export const WithCustomIcon: StoryObj<typeof Chip> = {
    render: Template6,
};
```

Attempt to render the story.

Expected Behavior:
The story should render a demo showing a Chip component with a custom icon.

Actual Behavior:
The resulting example code is:

`{ render: Template6 }`

### System

```bash
PS C:\React\daf-fe-sb> npx storybook@latest info

Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22631
    CPU: (24) x64 13th Gen Intel(R) Core(TM) i7-13700KF
  Binaries:
    Node: 18.20.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers:
    Edge: Chromium (123.0.2420.97)
  npmPackages:
    @storybook/addon-a11y: ^8.1.0 => 8.1.0
    @storybook/addon-essentials: ^8.1.0 => 8.1.0
    @storybook/addon-interactions: ^8.1.0 => 8.1.0
    @storybook/addon-links: ^8.1.0 => 8.1.0
    @storybook/addon-mdx-gfm: ^8.1.0 => 8.1.0
    @storybook/addon-webpack5-compiler-swc: ^1.0.2 => 1.0.2
    @storybook/manager-api: ^8.1.0 => 8.1.0
    @storybook/mdx2-csf: ^1.1.0 => 1.1.0
    @storybook/preview-api: ^8.1.0 => 8.1.0
    @storybook/react: ^8.1.0 => 8.1.0
    @storybook/react-dom-shim: ^8.1.0 => 8.1.0
    @storybook/react-vite: ^8.1.0 => 8.1.0
    @storybook/react-webpack5: ^8.1.0 => 8.1.0
    @storybook/test: ^8.1.0 => 8.1.0
    @storybook/test-runner: ^0.18.0 => 0.18.0
    @storybook/theming: ^8.1.0 => 8.1.0
    storybook: ^8.1.0 => 8.1.0
    storybook-react-context: ^0.6.0 => 0.6.0
```


### Additional context

This issue seems to be related to the way Storybook handles the rendering of components without the 'args' parameter.