sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Integrate ULFM and FTI for OpenMPI (torch.distributed)
Labels: oncall: distributed,feature

### 🚀 The feature, motivation and pitch

I am working on a distributed framework and I want to be able to manage node failures. Is is possible to integrate the use of _User Level Failure Mitigation_ ([ULFM](https://github.com/ICLDisco/ulfm-testing)) and _Fault Tolerance Interface_ ([FTI](https://github.com/leobago/fti)) libraries, please ?

### Alternatives

Create a manual checkpoint with `torch.save` or with Berkeley Lab Checkpoint/Restart (BLCR).

### Additional context

_No response_

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: ollama
Issue: COULDN'T run qwen2.5-7b-instuct-q4_k on cpu; error wsarecv: An existing connection was forcibly closed by the remote host.
Labels: bug

### What is the issue?

(cmd) ollama run qwen2.5-7b-instuct-q4_k
Error: Post "http://127.0.0.1:11434/api/generate": read tcp 127.0.0.1:50665->127.0.0.1:11434: wsarecv: An existing connection was forcibly closed by the remote host.

----------
server.log

2025/01/06 16:28:24 routes.go:1259: INFO server config env="map[CUDA_VISIBLE_DEVICES: GPU_DEVICE_ORDINAL: HIP_VISIBLE_DEVICES: HSA_OVERRIDE_GFX_VERSION: HTTPS_PROXY: HTTP_PROXY: NO_PROXY: OLLAMA_DEBUG:false OLLAMA_FLASH_ATTENTION:false OLLAMA_GPU_OVERHEAD:0 OLLAMA_HOST:http://127.0.0.1:11434 OLLAMA_INTEL_GPU:false OLLAMA_KEEP_ALIVE:5m0s OLLAMA_KV_CACHE_TYPE: OLLAMA_LLM_LIBRARY: OLLAMA_LOAD_TIMEOUT:5m0s OLLAMA_MAX_LOADED_MODELS:0 OLLAMA_MAX_QUEUE:512 OLLAMA_MODELS:D:\\workspace\\ollama\\ollama_model OLLAMA_MULTIUSER_CACHE:false OLLAMA_NOHISTORY:false OLLAMA_NOPRUNE:false OLLAMA_NUM_PARALLEL:0 OLLAMA_ORIGINS:[http://localhost https://localhost http://localhost:* https://localhost:* http://127.0.0.1 https://127.0.0.1 http://127.0.0.1:* https://127.0.0.1:* http://0.0.0.0 https://0.0.0.0 http://0.0.0.0:* https://0.0.0.0:* app://* file://* tauri://* vscode-webview://*] OLLAMA_SCHED_SPREAD:false ROCR_VISIBLE_DEVICES:]"
time=2025-01-06T16:28:24.613+08:00 level=INFO source=images.go:757 msg="total blobs: 5"
time=2025-01-06T16:28:24.613+08:00 level=INFO source=images.go:764 msg="total unused blobs removed: 0"
time=2025-01-06T16:28:24.614+08:00 level=INFO source=routes.go:1310 msg="Listening on 127.0.0.1:11434 (version 0.5.4)"
time=2025-01-06T16:28:24.614+08:00 level=INFO source=routes.go:1339 msg="Dynamic LLM libraries" runners="[cuda_v12_avx rocm_avx cpu cpu_avx cpu_avx2 cuda_v11_avx]"
time=2025-01-06T16:28:24.614+08:00 level=INFO source=gpu.go:226 msg="looking for compatible GPUs"
time=2025-01-06T16:28:24.614+08:00 level=INFO source=gpu_windows.go:167 msg=packages count=1
time=2025-01-06T16:28:24.614+08:00 level=INFO source=gpu_windows.go:183 msg="efficiency cores detected" maxEfficiencyClass=1
time=2025-01-06T16:28:24.614+08:00 level=INFO source=gpu_windows.go:214 msg="" package=0 cores=12 efficiency=4 threads=20
time=2025-01-06T16:28:24.629+08:00 level=INFO source=gpu.go:392 msg="no compatible GPUs were discovered"
time=2025-01-06T16:28:24.629+08:00 level=INFO source=types.go:131 msg="inference compute" id=0 library=cpu variant=avx2 compute="" driver=0.0 name="" total="31.7 GiB" available="21.0 GiB"


----------
however I could run qwen2.5-0.5b-instruct-q8_0

### OS

Windows

### GPU

Other

### CPU

Intel

### Ollama version

0.5.4
Repository: svelte
Issue: Loudly error for invalid `:global` placement
Labels: css

### Describe the bug

In https://discord.com/channels/457912077277855764/1325334674784129035 someone was confused by a certain syntax failing with a "unclosed comment" error. Turns out it's us no erroring on a wrong `:global` placement, which leads to subsequent wrong "comment this out" logic.

The solution is to throw a validation error here.

### Reproduction

[playground link](https://svelte.dev/playground/hello-world?version=5.16.2#H4sIAAAAAAAACm2OTW6EMAyFr2J5M4NEYZ9JkbqbnqHpgh_PNFJIosTQQYi7VwHasphIluLP9ntvRlv3hAKvZIyDbxdMB2fqNFOXYY43bSii-JiRJ5_2EsD89-rN-yKOZDixpo70jLfOMlmOKFDGNmjPYGp7f1XIUWGlLOxP994FhndrKcAtuB5ORbl2u9jpoqwsN41KWWVlpJa1swcR2enx0P5hX10p0CkCfxG4gSnAHkyW_tnBalzJLcDRoNwcZPlvnpLwZCh9Weh4TrWPodMjiLtxTW0yKGrvzfTS64e2GXiYN-HWGRcENGagSyILrAarJubI9GAUHAZaPpcfQY6NHrQBAAA=)

### Logs

_No response_

### System Info

```shell
irrelevant
```


### Severity

annoyance
Repository: flutter
Issue: [rfw] Alternative to `source.optionalChild()` with when constructor requires specific Widget?
Labels: waiting for customer response,in triage

### Use case

This is regarding rfw https://pub.dev/packages/rfw

I have a custom widget that has parameter `final Text? text`
```
class MarqueeContinuous extends StatelessWidget {
  final Text? text; // Need this
  final Duration duration;
  final Duration delay;
  final double step;
  final double endPadding;
  final int scrollCount;

  const MarqueeContinuous({
    Key? key,
    this.text,
    this.delay = const Duration(seconds: 2),
    this.duration = const Duration(seconds: 2),
    this.step = 50,
    this.endPadding = 4,
    this.scrollCount = -1,
  }) : super(key: key);
```

There are only two function calls that returns Widget -  `source.child()` and `source.optionalChild()`.
But the compiler is complaining because `Widget` is not `Text`.

Screenshot below is my custom `LocalWidgetLibrary`
![image](https://github.com/user-attachments/assets/a317f911-a3da-4c6d-9a66-ab5960130b5a)

May I know if there is solution to this? Thanks in advance.

### Proposal

Let `sourceChild()` return specific Widget.
Repository: vscode
Issue: Add context menu on folders to add to chat
Labels: feature-request,file-explorer,chat

Today there is a Copilot menu for files:

![Image](https://github.com/user-attachments/assets/708f3ad7-fa34-4e41-9cbc-19767b01596d)

Since we now support folders too, I would suggest to have it for folders as well.
Repository: vscode
Issue: Explorer: Sticky folder cannot be dragged
Labels: feature-request,tree-sticky-scroll

In the explorer, folders appear sticky. They have a context menu but do not respond to drag and drop operations.

![Image](https://github.com/user-attachments/assets/8fa184ff-f11b-49f4-b404-8a27816c19a9)
Repository: vscode
Issue: Git blame: allow action to open commit on GH
Labels: feature-request,git

I prefer to view a commit on GH.com, allow me to configure the click gesture to open the commit.
Repository: vscode
Issue: Missing screen reader output at opening / saving file input on remote
Labels: bug,accessibility,simple-file-dialog


Type: <b>Bug</b>

If there is a workaround, it may not necessarily be a bug.

1. Open a remote using the vscode-remote extension. E.G. WSL.
2. Try to open a folder, or save a new file.
3. Try to input filename, or edit the current input with screen reader.
4. inputs and deletions are not announced by screen reader at all. Moving cursor doesn't announce the focused character.
5. Expected: They are announced.

I think this box was originally a simple text field. In a older version (probably 6 month to 1 year ago?), it also started to act as a combo box, allowing me to autocomplete directories.
After the change, I am unable to smoothly finalize the destination to what I want the path to be. I just thought I would be able to adapt to this when it was introduced, but now feeling like reporting it here and seek for some workarounds.

It does not occur in local development since it uses the native dialog, at least on Windows. It only happens when I am developing on a remote.

I'm not really sure this custom dialog is provided by the vscode-side or the extension-side.

Extension version: 0.88.5
VS Code version: Code 1.96.1 (42b266171e51a016313f47d0c48aca9295b9cbb2, 2024-12-17T17:50:05.206Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 5.15.167.4-microsoft-standard-WSL2

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

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-1255U (12 x 2611)|
|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: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.69GB (2.62GB free)|
|Process Argv|--crash-reporter-id 16c020cb-6298-45d1-bf2f-54354940af72|
|Screen Reader|yes|
|VM|0%|

|Item|Value|
|---|---|
|Remote|WSL: Ubuntu|
|OS|Linux x64 5.15.167.4-microsoft-standard-WSL2|
|CPUs|12th Gen Intel(R) Core(TM) i7-1255U (12 x 0)|
|Memory (System)|7.60GB (4.88GB free)|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256859
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupytercf:31046870
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc2:31192216
cf971741:31144450
iacca1:31171482
notype1cf:31157160
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624

```

</details>

<!-- generated by issue reporter -->
Repository: transformers
Issue: Trainer: update `state.num_input_tokens_seen` to use `num_items_in_batch`
Labels: Feature request

### Feature request

Trainer has a state and inside the state there is a field called `num_input_tokens_seen`, which could be relevant for callbacks and other information.
The problem is that this field is updated using numel() which means it counts the padding as well. 
https://github.com/huggingface/transformers/blob/241c04d36867259cdf11dbb4e9d9a60f9cb65ebc/src/transformers/trainer.py#L2492-L2496

In a recent update the class calculates `num_tokens_in_batch` so it can be used for the loss calculation, this ignores padding. and can be used to give a more accurate picture for `num_input_tokens_seen`. 


__

### Motivation

`num_input_tokens_seen` is improtant information when you train a model. Having a more accurate picture for it will help people understand their training. It can also be used for callbacks (e.g. stop training after X tokens).

This will also eliminate the double calculation for num_tokens_seen (we are already calculating it once), and eliminate the discrepancy between the `num_input_tokens_seen` and  `num_tokens_in_batch`

### Your contribution

I maybe be able to do a PR for this
Repository: pytorch
Issue: F.interpolate returns NAN on MPS if align_corner is True.
Labels: module: nn,triaged,module: correctness (silent),module: mps

### 🐛 Describe the bug

When using interpolate on MPS with align_corner=True, the result consists only of NaN value, which is inconsistent to the CPU implementation. 

You can replicate this by the following code snippet:

```python
import torch
import torch.nn.functional as F


test = torch.Tensor([[1],[2],[4]]).to("mps")
result = F.interpolate(test.unsqueeze(1), 3, mode="linear", align_corners=True).squeeze(1)

print(result)
# tensor([[nan, nan, nan],
#         [nan, nan, nan],
#         [nan, nan, nan]], device='mps:0')
test = torch.Tensor([[1],[2],[4]]).to("cpu")
result = F.interpolate(test.unsqueeze(1), 3, mode="linear", align_corners=True).squeeze(1)

print(result)
# tensor([[1., 1., 1.],
#         [2., 2., 2.],
#         [4., 4., 4.]])

```



### Versions

Collecting environment information...
PyTorch version: 2.5.1
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: macOS 15.1 (arm64)
GCC version: Could not collect
Clang version: 16.0.0 (clang-1600.0.26.4)
CMake version: Could not collect
Libc version: N/A

Python version: 3.11.9 (main, Jun 29 2024, 14:01:21) [Clang 15.0.0 (clang-1500.1.0.2.5)] (64-bit runtime)
Python platform: macOS-15.1-arm64-arm-64bit
Is CUDA available: False
CUDA runtime version: No CUDA
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Apple M2

Versions of relevant libraries:
[pip3] flake8==7.1.1
[pip3] mypy==1.11.2
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] pytorch-forecasting==1.1.1
[pip3] pytorch-lightning==2.4.0
[pip3] pytorch_optimizer==2.12.0
[pip3] torch==2.5.1
[pip3] torchmetrics==1.4.1
[pip3] torchvision==0.19.0
[conda] Could not collect


cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @kulinseth @malfet @DenisVieriu97 @jhavukainen
Repository: godot
Issue: In canvas shader, INSTANCE_ID is always 0.
Labels: documentation,topic:shaders

### Tested versions

4.3

### System information

win11

### Issue description

What **not** it supposed to:
the color should not be sync;
![Image](https://github.com/user-attachments/assets/40cc04d5-bc29-4463-b117-feb59bfcb05c)
What is supposed to:
the color is not sync (intented)
![Image](https://github.com/user-attachments/assets/186be47f-5413-4089-92c5-5ae9ea9970d5)

I want to use a different number in different shader instances to make them look different without changing the uniform parameter in the script.
I can do this via INSTANCE_ID in 3d, but not in 2d.
In Canvas, this INSTANCE_ID always seems to be 0.
As demonstrated above, the shader code is meant to make different shader instances to do a color-changing animation with a time offset by a unique number which is INSTANCE_ID;

Maybe this is not implemented in canvas shader, or intended?

### Steps to reproduce

use the shader code below, create multiple sprites, and make shader Material unique.
The Color of sprites is sync in the case, which means INSTANCE_ID is always the same.
```
shader_type canvas_item; 
varying flat float seed;
void vertex() {
	seed = fract(float(INSTANCE_ID) * 0.1 + TIME);
}

void fragment() {
	COLOR = vec4(seed, 1.0, 1.0, 1.0);
}
```


### Minimal reproduction project (MRP)
[4.3test (4).zip](https://github.com/user-attachments/files/18318602/4.3test.4.zip)
Repository: ant-design
Issue: Table 设置 scroll={{x: 1500 }} 后，expandedRowRender 里的 table 的sticky 的特性会消失；
Labels: 🙅🏻‍♀️ WON'T RESOLVE

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-jyh2k9)

### Steps to reproduce

Table 中的expandable 也是一个 table,给expandable 里的 table 添加 sticky 属性，这时再个外层的 table 添加   scroll={{x: 1500 }} ，expandable里sticky，固定表头的特性就会消失

### What is expected?

设置  scroll={{x: 1500 }} expandedRowRender 里的table 的sticky 特性不会消失

### What is actually happening?

外层 table 设置scroll={{x: 1500 }} 后，expandedRowRender里的table 的sticky 特性会消失

| Environment | Info |
| --- | --- |
| antd | 5.23.0 |
| React | 18.0.0 |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: excalidraw
Issue: Cursor reappearing while writing on tablet
Labels: bug


### Discussed in https://github.com/excalidraw/excalidraw/discussions/8922

<div type='discussions-op-text'>

<sup>Originally posted by **happyfunction** December 17, 2024</sup>
When using the pen tool, the crosshair is always displayed when using the mouse, whether you are writing (pressing the left mouse button) or just moving the cursor. However, when using a digital pen and a graphics tablet, the cursor disappears when the digital pen touches the graphics tablet. When the digital pen leaves the graphics tablet, the cursor reappears. If you write relatively fast, the cursor will appear and disappear from time to time, and this kind of experience is not good.</div>
Repository: vscode
Issue: Remove initialising of extension sizes
Labels: debt,extensions

Remove initialising of extension sizes
Repository: electron
Issue: setAspectRatio does not follow the useContentSize
Labels: platform/windows,bug :beetle:,33-x-y

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

33.3.0

### What operating system(s) are you using?

Windows

### Operating System Version

Windows 10 22H2

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

I'm creating a program for a game and need to fix the window ratio to 16:9. Window size should stay 16:9

### Actual Behavior

when `setAspectRatio` the window does not follow the useContentSize.

### Testcase Gist URL

[https://gist.github.com/nini22P/85113721f1f3aad7c78f1837c6f2a677](https://gist.github.com/nini22P/85113721f1f3aad7c78f1837c6f2a677)

### Additional Information

I created a 16:9 centered div, then set the window to 1280 x 720 and set the `seContentSize: true`.

The previous setting of `useContentSize: true` , the `mainWindow.setAspectRatio(16 / 9)` should directly make the content ratio 16:9.

But the content ratio isn't 16:9, and a black border appears
Repository: vscode
Issue: Screen cheese in the debug console
Labels: bug,debug

![Image](https://github.com/user-attachments/assets/eaf409e2-39cc-4a7a-aa68-46e276f66f62)

I've also seen it appear to be empty, but with a scrollbar and a lot of distance to scroll.
Repository: pytorch
Issue: [Inductor] Unify the data type propagation between Triton and CPP Backend
Labels: oncall: pt2,oncall: cpu inductor

### 🚀 The feature, motivation and pitch

Previously, `dtype` is the attr of `CppCSEVariable` but not `CSEVariable`. And thus CPP backend has its data type propagation mechanism in `CppCSEVariable.update_on_args`: https://github.com/pytorch/pytorch/blob/d85ae4be734cfd53f5b893240894381ac65fe8b4/torch/_inductor/codegen/cpp_utils.py#L218

Now, triton backend has also introduced new the data type propagation  in https://github.com/pytorch/pytorch/blob/d85ae4be734cfd53f5b893240894381ac65fe8b4/torch/_inductor/codegen/common.py#L1825-L1866. We may consolidate these 2 mechanisms to save redundant code.

### Alternatives

No

### Additional context

No

cc @soulitzer @chauhang @penguinwu
Repository: tauri
Issue: [bug] Improve error messages if `cargo metadata` fails.
Labels: type: bug,good first issue,status: backlog

### Describe the bug

Running: 

`cargo create-tauri-app` or `sh <(curl https://create.tauri.app/sh)`
  - Tried rust-based (tried vanilla and leptos)  frontend as well as Typescript based (vanilla with pnpm or deno)

then 

`cargo tauri android init` or `pnpm tauri android init` or `deno task tauri android init` _all_ produce:

```
failed to get cargo metadata: expected value at line 1 column 1
```

Trying `cargo tauri dev` instead of `android init` gives the same issue. 

Adding verbose flag with `-v` doesn't give any useful info.   


_Apologies in advance if this is something trivial I've missed; at the same time, the quickstart should  be as foolproof as possible IMO, so this could still highlight an area for improvement._
  

### Reproduction

```
sh <(curl https://create.tauri.app/sh)
# Select any frontend option
cargo tauri android init 
# OR
cargo tauri dev
```

### Expected behavior

Should `android init` should create android scaffold, or `cargo tauri dev` should correctly build app and launch dev server.

### Full `tauri info` output

```text
cargo tauri info


[✔] Environment
    - OS: EndeavourOS Rolling Release x86_64 (X64) (Unknown DE on wayland)
    ✔ webkit2gtk-4.1: 2.46.5
    ✔ rsvg2: 2.59.2
    ✔ rustc: 1.83.0 (90b35a623 2024-11-26)
    ✔ cargo: 
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (environment override by RUSTUP_TOOLCHAIN)
    - node: 20.18.1
    - pnpm: 9.15.3
    - yarn: 1.22.22
    - npm: 11.0.0
    - bun: 1.0.7
    - deno: deno 2.0.6

[-] Packages
    - tauri 🦀: 2
    - tauri-build 🦀: No version detected
    - wry 🦀: No version detected
    - tao 🦀: No version detected
    -  🦀: cargo 1.83.0 (5ffbef321 2024-10-29)
    - @tauri-apps/api : 2.2.0
    - @tauri-apps/cli : 2.2.2

[-] Plugins

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - bundler: Vite
```


### Stack trace

```text
failed to get cargo metadata: expected value at line 1 column 1
```


### Additional context

_No response_
Repository: storybook
Issue: [Bug]: Storybook couldn't evaluate your
Labels: bug,core

### Describe the bug

when I try to run it gives an error:
```
SB_CORE-SERVER_0007 (MainFileEvaluationError): Storybook couldn't evaluate your .storybook\main.ts file.

Original error:
Error: Transform failed with 1 error:
(define name):1:0: ERROR: Expected identifier but found "import"
    at failureErrorWithLog (\node_modules\esbuild\lib\main.js:1476:15)
    at responseCallbacks.<computed> (\node_modules\esbuild\lib\main.js:622:9)
    at Socket.readFromStdout (\node_modules\esbuild\lib\main.js:600:7)
    at Socket.emit (node:events:520:28)
    at addChunk (node:internal/streams/readable:559:12)
    at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
    at Readable.push (node:internal/streams/readable:390:5)
    at Pipe.onStreamRead (node:internal/stream_base_commons:191:23)
    at loadMainConfig (.\node_modules\@storybook\core\dist\common\index.cjs:17511:11)
    at async buildDevStandalone (.\node_modules\@storybook\core\dist\core-server\index.cjs:37134:11)
    at async withTelemetry (.\node_modules\@storybook\core\dist\core-server\index.cjs:35757:12)
    at async dev (.\node_modules\@storybook\core\dist\cli\bin\index.cjs:2591:3)
    at async s.<anonymous> (.\node_modules\@storybook\core\dist\cli\bin\index.cjs:2643:74)

WARN Broken build, fix the error above.
WARN You may need to refresh the browser.
```
I use next js version 14
I found answers for Vite but couldn't find one that suited me

### Reproduction link

https://stackblitz.com/edit/github-p7lfsqcw?file=.storybook%2Fmain.ts,.storybook%2Fpreview.ts&preset=node

### Reproduction steps

_No response_

### System

```bash
System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 AMD Ryzen 5 2600X Six-Core Processor
  Binaries:
    Node: 22.0.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - C:\Program Files\nodejs\yarn.CMD <----- active
    npm: 10.5.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (129.0.2792.89)
  npmPackages:
    @storybook/addon-essentials: 8.4.2 => 8.4.2
    @storybook/addon-interactions: 8.4.2 => 8.4.2
    @storybook/addon-onboarding: 8.4.2 => 8.4.2
    @storybook/blocks: 8.4.2 => 8.4.2
    @storybook/nextjs: ^8.4.2 => 8.4.7
    @storybook/preview-api: ^8.4.2 => 8.4.7
    @storybook/react: 8.4.2 => 8.4.2
    @storybook/test: 8.4.2 => 8.4.2
    eslint-plugin-storybook: ^0.11.0 => 0.11.1
    storybook: 8.4.2 => 8.4.2
```

### Additional context

_No response_