sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: android_camerax plugin returns .temp extension for recorded video
Labels: platform-android,p: camera,package,has reproducible steps,P1,team-android,triaged-android,found in release: 3.22

### Steps to reproduce

1. Launch example app from the camerax module
2. Start video recording
3. Stop video recording and observe extension of the reported saved file name.

### Expected results

The file returned from the stop video recording method should have a file extension corresponding to the saved file type. E.g. .mp4, .jpg etc.

### Actual results

Plugin saves recorded file with the .temp extension which does not correspond to the actual media type.

### Code sample

<details open><summary>Code sample</summary>

```dart
example app from the camerax module
```

</details>


### Screenshots or Video

N/A

### Logs

N/A

### Flutter Doctor output

N/A
Repository: tauri
Issue: [feat] Recent documents
Labels: type: feature request

### Describe the problem

`Windows` and `macOS` provide access to a list of recent documents opened by the application via JumpList or dock menu, respectively. I would like to use this API with tauri apps.

<img width=200 src="https://github.com/tauri-apps/tauri/assets/61390950/26db82ca-3742-4073-b787-ddb8e692dcb9">

<img width=200 src="https://github.com/tauri-apps/tauri/assets/61390950/307bb0ea-741b-41d1-b18a-ececeb346439">


### Describe the solution you'd like

Provide an API for modifying recent app documents on `macOS` / `Windows`

### Alternatives considered

_No response_

### Additional context

`Electron` has [Recent documents](https://www.electronjs.org/docs/latest/tutorial/recent-documents) API

macOS [electron/browser_mac.mm#L163](https://github.com/electron/electron/blob/4e702130378bb3a1cdbc1a778a3db90548f32467/shell/browser/browser_mac.mm#L163)
Windows [electron/browser_win.cc#L318](https://github.com/electron/electron/blob/4e702130378bb3a1cdbc1a778a3db90548f32467/shell/browser/browser_win.cc#L318)
Repository: storybook
Issue: [Bug]: not provided path of components to "include" property in tsconfig.json / not detect jsdoc comments
Labels: bug,angular,docgen

### Describe the bug

![image](https://github.com/storybookjs/storybook/assets/29141389/40e32a7c-09eb-406a-965e-e1863500dceb)
As on the img, by default, path to components is not added to `tsconfig.json` file. I spent too many hours wondering why my compdoc not generated documentation about my components. 

### To Reproduce

1. Create new angular app. 
2. Create new library
3. Add storybook by CLI command to library
4. see `projects/mylib/.storybook/tsconfig.json`

### System

```bash
System:
    OS: Windows 11 10.0.22631
    CPU: (16) x64 AMD Ryzen 9 5900HS with Radeon Graphics        
  Binaries:
    Node: 20.12.2 - C:\Program Files\nodejs\node.EXE
    npm: 10.5.0 - C:\Program Files\nodejs\npm.CMD <----- active
    pnpm: 8.12.0 - ~\AppData\Local\pnpm\pnpm.EXE
  Browsers:
    Edge: Chromium (123.0.2420.97)
  npmPackages:
    @storybook/addon-docs: ^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/angular: ^8.1.0 => 8.1.0 
    @storybook/blocks: ^8.1.0 => 8.1.0 
    @storybook/test: ^8.1.0 => 8.1.0 
    eslint-plugin-storybook: ^0.8.0 => 0.8.0 
    storybook: ^8.1.0 => 8.1.0
```


### Additional context

`"../src/**/*.component.ts"` should be added
Repository: pytorch
Issue: cudagraph error with set_ on inputs
Labels: triaged,module: cuda graphs,oncall: pt2

### 🐛 Describe the bug

We need to track storage liveness for correctness and expect the storages to be on the outputs. 

A possible fix here would be to add the inputs which are mutated as outputs, but needs further investigation.

Repro (right now internal only) https://www.internalfb.com/phabricator/paste/view/P1360460962.

### Error logs

...

### Minified repro

...

### Versions

master

cc @mcarilli @ezyang @peterbell10 @msaroufim @bdhirsh @anijain2305 @chauhang
Repository: rust
Issue: vtable symbols are not marked artificial in DWARF
Labels: A-LLVM,A-debuginfo,T-compiler,C-bug,WG-debugging

I tried this code, from the gdb testsuite:

```rust
fn empty () {
}

fn main () {
    let array = [1,2,3,4];
    let slice = &array[1..2];
    let hello = "hello";

    empty();			// STOP
}
```

I compiled with `-g`.

Examining the resulting DWARF, I see:

```
 <1><2a>: Abbrev Number: 2 (DW_TAG_variable)
    <2b>   DW_AT_name        : (indirect string, offset: 0xf3): <std::rt::lang_start::{closure_env#0}<()> as core::ops::function::Fn<()>>::{vtable}
    <2f>   DW_AT_type        : <0x3d>
    <33>   DW_AT_location    : 9 byte block: 3 80 24 5 0 0 0 0 0 	(DW_OP_addr: 52480)
```

I think this should be marked with `DW_AT_artificial`, as it does not correspond to any user-written code in the CU.  This will let gdb filter out these variables when displaying globals from a CU.
Repository: ollama
Issue: GPU layer control / prioritisation
Labels: feature request

Would it be possible to add into the configuration of ollama something similar to LM studio to control the gpu utilisation? 

Also would it be possible to fine tune ollama to somehow only load certain layers to the gpu similar to unsloth? 

Possibly a way to load accessed and adjacent layers maybe with configuration on how many adjacent layers/how much of the model to load at once and either offload the unused layers to ram or not load them at all and just swap out loading layers when needed instead of just loading the entire model every time 

Could maybe have add it as lazy loading or something to enable the usage of larger models at higher performance 

It seems to have a significant performance advantage especially on lower hardware for those of us without extreme setups if possible within ollama at least
Repository: pytorch
Issue: Centralized Mechanism To Pytorch Query Global Flags
Labels: triaged,oncall: pt2

### 🚀 The feature, motivation and pitch

Such as tensorfloat32 enabled, etc. 

This would be useful especially for pt2 caching mechanisms.

cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang @jamesjwu @masnesral 

### Alternatives

_No response_

### Additional context

_No response_
Repository: go
Issue: x/website: tables are awkwardly formatted
Labels: help wanted,NeedsInvestigation,website

### What is the URL of the page with the issue?

https://go.dev/ref/mod#environment-variables

### What is your user agent?

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36

### Screenshot

![image](https://github.com/golang/go/assets/203380/358aae01-98cb-4338-9299-6711f4e87011)


### What did you do?

Visit https://go.dev/ref/mod#environment-variables

### What did you see happen?

The table of environment variables has no cell borders and the content is vertically centered. This makes it needlessly difficult to understand which variable corresponds to which description, and where one description ends and the next begins.

### What did you expect to see?

If the table is going to have no borders, then I think the content should be top-aligned.

I'd expect that other tables in the Go documentation probably have this issue as well.
Repository: storybook
Issue: [Bug]: Should not be able to write in inert form
Labels: bug,sev:S3,test utilities

### Describe the bug

<img width="1255" alt="image" src="https://github.com/storybookjs/storybook/assets/10213241/6335a341-2bad-4a3c-86fe-9e127f2a1c80">

when a form is inert tests consider you can write and that it is enabled, they pass when they actually failed.

### To Reproduce

https://stackblitz.com/edit/github-h8mbsw?file=src%2Fstories%2FCase.stories.tsx

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.4.1
    CPU: (8) x64 Intel(R) Core(TM) i5-8279U CPU @ 2.40GHz
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.17.0 - ~/.nvm/versions/node/v18.17.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.17.0/bin/yarn <----- active
    npm: 9.6.7 - ~/.nvm/versions/node/v18.17.0/bin/npm
  Browsers:
    Chrome: 124.0.6367.201
    Edge: 124.0.2478.97
    Firefox: 125.0.3
    Safari: 17.4.1
  npmPackages:
    @storybook/addon-actions: 8.0.9 => 8.0.9 
    @storybook/addon-essentials: 8.0.9 => 8.0.9 
    @storybook/addon-interactions: 8.0.9 => 8.0.9 
    @storybook/addon-links: 8.0.9 => 8.0.9 
    @storybook/react: 8.0.9 => 8.0.9 
    @storybook/react-vite: 8.0.9 => 8.0.9 
    @storybook/test: ^8.0.9 => 8.0.9 
    chromatic: ^11.3.0 => 11.3.0 
    eslint-plugin-storybook: 0.8.0 => 0.8.0 
    msw-storybook-addon: 2.0.0 => 2.0.0 
    storybook: 8.0.9 => 8.0.9 
    storybook-addon-pseudo-states: 3.1.0 => 3.1.0 
    storybook-dark-mode: 4.0.1 => 4.0.1
```


### Additional context

_No response_
Repository: next.js
Issue: Not working with Yarn pnpm strategy
Labels: bug,Runtime,Module Resolution

### Link to the code that reproduces this issue

https://github.com/coreyward/next-yarn-pnpm-issue

### To Reproduce

Run `yarn dev` in the linked repo root, then open the app at localhost:3000. This will trigger the following error:

> Error: Invariant: Expected relative import to start with "next/", found "package/dist/server/future/route-modules/pages/module.compiled"
    at [Symbol.replace] (<anonymous>)
    at String.replaceAll (<anonymous>)

<img width="1110" alt="Screenshot 2024-05-14 at 2 01 12 PM" src="https://github.com/vercel/next.js/assets/81224/04baa13c-67a8-4669-894d-9583d66a2057">


### Current vs. Expected behavior

Next works fine when using the legacy `node_modules` approach for installing dependencies, and seems to have support for the Plug-N-Play strategy of pnpm, but it does not seem to account for [Yarn’s hybrid `pnpm` strategy](https://yarnpkg.com/configuration/yarnrc#nodeLinker) which is described as follows:

> node-modules will be created using symlinks and hardlinks to a global content-addressable store.

The issue seems to come about in the load-entrypoint, which seems to make unsafe assumptions about where dependencies are located on disk relative to the project. The specific error is coming from Next.js here:

https://github.com/vercel/next.js/blob/9d16112e28978aa1beed167f018ae29db607e035/packages/next/src/build/load-entrypoint.ts#L63-L70

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 4.2.2
  pnpm: N/A
Relevant Packages:
  next: 14.3.0-canary.62 // Latest available version is detected (14.3.0-canary.62).
  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)

Module Resolution, Runtime

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local)

### Additional context

This may be related to #16471.
Repository: go
Issue: internal/trace/v2: TestTraceGCStress failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "internal/trace/v2" && test == "TestTraceGCStress"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/9c4484625ad510cc925834c6bba2402099a25122)):

    --- FAIL: TestTraceGCStress (2.92s)
        --- FAIL: TestTraceGCStress/AllocFree (0.67s)
            trace_test.go:577: stderr: SIGSEGV: segmentation violation
                PC=0x80a1b1b m=17 sigcode=1 addr=0xf7865000
    
                goroutine 0 gp=0x98825a8 m=17 mp=0x9e80f08 [idle]:
                runtime.traceAdvance.func6()
                	/workdir/go/src/runtime/trace.go:667 +0xab fp=0xa313fdc sp=0xa313fc0 pc=0x80a1b1b
                runtime.systemstack(0x8825a8)
                	/workdir/go/src/runtime/asm_386.s:374 +0x41 fp=0xa313fe0 sp=0xa313fdc pc=0x80b5691
    ...
                esi    0xffff0000
                ebp    0x81a7bd8
                esp    0xa313fc0
                eip    0x80a1b1b
                eflags 0x10286
                cs     0x23
                fs     0x0
                gs     0x63
                exit status 2
            trace_test.go:579: exit status 1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: Webview sometimes displays blank on launch, until scroll
Labels: platform-android,P2,team-engine,triaged-engine,:hourglass_flowing_sand:

I noticed this while testing https://github.com/flutter/engine/pull/52532 (with the repro sample from https://github.com/flutter/flutter/issues/146570) but it occurs on main.

Sometimes (not always), the webview just displays blank on launch. As soon as I scroll it it will display properly.

<img src="https://github.com/flutter/flutter/assets/34871572/569ca824-49f6-4ee2-9fc0-554f8bcaabf7" width="300">

I write webview because I haven't tested with other platform views, but I suspect this would affect any platform view.
Repository: flutter
Issue: [webview_flutter_wkwebview] The `withWeakReferenceTo` integration test fails on CI post submit
Labels: a: tests,p: webview,package,team-ecosystem,P2,c: disabled test,triaged-ecosystem

The `withWeakReferenceTo allows encapsulating class to be garbage collected` has started failing consistently in the `webview_flutter_wkwebview` [integration test](https://github.com/flutter/packages/blob/main/packages/webview_flutter/webview_flutter_wkwebview/example/integration_test/webview_flutter_test.dart). It is failing on post-submit, but didn't fail in the presubmit.

I wasn't able to reproduce the failure locally either on flutter/flutter [034aa2f760d4d5e24fa11bed1839a9cccb297d21](https://github.com/flutter/flutter/commit/034aa2f760d4d5e24fa11bed1839a9cccb297d21). 

See https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8747939904016287009/+/u/Run_package_tests/drive_examples/stdout
Repository: flutter
Issue: [flutter_tools] RPCError: getSupportedProtocols: (-32000) Bad state: The client closed with pending request "getSupportedProtocols". 
Labels: c: crash,P2,team-tool,triaged-tool

On beta/3.22.0-0.3.pre, first seen on beta/3.22.0-0.1.pre

Command: debug_adapter
8 reports from 8 clients as of 5/14/24

```
RPCError: getSupportedProtocols: (-32000) Bad state: The client closed with pending request "getSupportedProtocols".
at new _OutstandingRequest(vm_service.dart:265)
at VmService._call.<anonymous closure>(vm_service.dart:1772)
at VmService._call(vm_service.dart:1784)
at VmService.getSupportedProtocols(vm_service.dart:1153)
at DartDebugAdapter.connectDebugger(dart.dart:651)
at <asynchronous gap>(async)
at FlutterDebugAdapter._connectDebugger(flutter_adapter.dart:381)
at <asynchronous gap>(async)
at FlutterDebugAdapter._handleDebugPort(flutter_adapter.dart:475)
at <asynchronous gap>(async)
```

cc @DanTup since I believe they might be interested in new crashes from `debug_adapter` (please let me know if I shouldn't do this)
Repository: node
Issue: `import-in-the-middle` causes exception when creating `ERR_MODULE_NOT_FOUND` message
Labels: esm,loaders

### Version

v22.1.0

### Platform

All

### Subsystem

module

### What steps will reproduce the bug?

This was triggered by a combination of `import-in-the-middle` and `tsx`, but below is a minimal reproduction without either of those.

- `import-in-the-middle` sets `parentURL` to node build-ins (`node:*`).
- `tsx` tries to resolve files that do not exist

The 

`hook.mjs`
```ts
export async function resolve(specifier, context, nextResolve) {
    specifier = 'file:///dost-not-exist.mjs';
    context.parentURL = 'node:util';
    return nextResolve(specifier, context);
}
```
`index.mjs`
```ts
import { register } from "node:module";

register('./hook.js',  import.meta.url);
await import("node:util");
```
Which gives the following error:
```
TypeError [ERR_INVALID_URL_SCHEME]: The URL must be of scheme file
    at fileURLToPath (node:internal/url:1491:11)
    at finalizeResolution (node:internal/modules/esm/resolve:265:42)
    at moduleResolve (node:internal/modules/esm/resolve:924:10)
    at defaultResolve (node:internal/modules/esm/resolve:1148:11)
    at nextResolve (node:internal/modules/esm/hooks:750:28)
    at resolve (data:application/javascript;base64,CiAgICBleHBvcnQgYXN5bmMgZnVuY3Rpb24gcmVzb2x2ZShzcGVjaWZpZXIsIGNvbnRleHQsIG5leHRSZXNvbHZlKSB7CiAgICAgIHNwZWNpZmllciA9ICdmaWxlOi8vL2Rvc3Qtbm90LWV4aXN0Lm1qcyc7CiAgICAgIGNvbnRleHQucGFyZW50VVJMID0gJ25vZGU6dXRpbCc7CiAgICAgIHJldHVybiBuZXh0UmVzb2x2ZShzcGVjaWZpZXIsIGNvbnRleHQpOwogICAgfQo=:5:14)
    at nextResolve (node:internal/modules/esm/hooks:750:28)
    at Hooks.resolve (node:internal/modules/esm/hooks:238:30)
    at MessagePort.handleMessage (node:internal/modules/esm/worker:199:24)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:821:20) {
  code: 'ERR_INVALID_URL_SCHEME'
}

```
This is caused by this code where `base` is `node:util`:
https://github.com/nodejs/node/blob/87b87a8f6017545e2c9d6048d7b081f73c8a1072/lib/internal/modules/esm/resolve.js#L264-L265

### How often does it reproduce? Is there a required condition?

Every time

### What is the expected behavior? Why is that the expected behavior?

This should throw a valid `ERR_MODULE_NOT_FOUND` error

### What do you see instead?

It's throwing while creating the message

### Additional information

This was made incredibly difficult to debug because you can't debug loader hooks!

Credit to @nwalters512 for the back and forth debugging with me!
Repository: flutter
Issue: [flutter_tools] RPCError: getVM: (112) Service has disappeared
Labels: c: crash,P2,team-tool,triaged-tool

On beta/3.22, first seen on beta/3.22.0-0.0.1.pre
Command: `debug_adapter`
6 reports from 6 clients as of 5/14/24.

```
threadRPCError: getVM: (112) Service has disappeared
at new _OutstandingRequest(vm_service.dart:265)
at VmService._call.<anonymous closure>(vm_service.dart:1772)
at VmService._call(vm_service.dart:1784)
at VmService.getVM(vm_service.dart:1249)
at DartDebugAdapter.connectDebugger(dart.dart:698)
at <asynchronous gap>(async)
at FlutterDebugAdapter._connectDebugger(flutter_adapter.dart:381)
at <asynchronous gap>(async)
at FlutterDebugAdapter._handleDebugPort(flutter_adapter.dart:475)
at <asynchronous gap>(async)
```
Repository: pytorch
Issue: Conflicting OMP implementations linked when building with MKLDNN
Labels: module: build,triaged,module: mkldnn,module: openmp

### 🐛 Describe the bug

Custom builds with MKLDNN can link to both libomp and libgomp, which could cause invalid or slow behavior if some symbols are missing from one.

This happens because the MKLDNN extension [always builds with libgomp](https://github.com/pytorch/pytorch/blob/ee0c47349ca9bd58fdf4b2e533d950852579dada/third_party/mkl-dnn.BUILD#L129), whereas pytorch [by default prefers libomp](https://github.com/pytorch/pytorch/blob/ee0c47349ca9bd58fdf4b2e533d950852579dada/cmake/Modules/FindOpenMP.cmake#L258).

Assuming libomp is present on the system, this can be replicated via a custom build with
```
export CMAKE_PREFIX_PATH="/path/to/mkl/"
cmake -DUSE_MKLDNN=1 -DUSE_STATIC_MKL=1 -DBLAS=MKL
```

Producing things like this:
```
$ readelf -d libtorch_cpu.so 

Dynamic section at offset 0x12425918 contains 40 entries:
  Tag        Type                         Name/Value
...
 0x0000000000000001 (NEEDED)             Shared library: [libomp.so]
 0x0000000000000001 (NEEDED)             Shared library: [libgomp.so.1]
...
```

I suspect the fix here would be to always use libgomp in FindOpenMP.cmake when USE_MKLDNN is true, but perhaps there's a way to make MKLDNN use whatever OMP we've discovered?

### Versions

I think this has been the case for a while.

cc @malfet @seemethere @gujinghui @PenghuiCheng @XiaobingSuper @jianyuh @jgong5 @mingfeima @sanchitintel @ashokei @jingxu10 @min-jean-cho @yanbing-j @Guobing-Chen @Xia-Weiwen @snadampal
Repository: pytorch
Issue: Allow Lazy Initialization for PipelineStage
Labels: oncall: distributed,triaged

Using this issue to track the requests in https://github.com/pytorch/pytorch/pull/126123

Some requests:
- for pipeline stage perform shape inference on first forward. 
- Remove device requirement. 
- Do not require output_args

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @osalpekar @jiayisuse @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @chauhang @d4l3k
Repository: storybook
Issue: [Bug]: calling `updateArgs` doesn't trigger docs addon `transform` function
Labels: bug,help wanted,block: source,sev:S3

### Describe the bug

I have a story with a controls panel under it, and when I make changes in the controls panel, the story canvas re-renders as expected. However the "Show code" block just underneath only ever shows the initial args passed to the story. I have a `parameters.docs.source.transform` function, which is only called once when the story initially renders. It appears that calling `updateArgs` (which the controls addon appears to do under the hood) doesn't trigger anything in the docs addon to execute the `transform` function again with the updated arguments.

### To Reproduce

I don't have the ability to create a stackblitz reproduction at the moment, but I'll try to get one added this evening.

The transform function looks like this:

```ts
transform: (unused: string, context: StoryContext): string => {
    const { args } = context;

    return `<${args.variant} size="${args.size}" />`;
},
```

Update: I am not going to be able to make a reproduction for at least a few days due to going out of town, but here is a screen recording showing the issue.

https://github.com/storybookjs/storybook/assets/198075/8644a0ea-e67b-4724-b75c-a335a85983ce

### System

```bash
Storybook Environment Info:
  System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.1 - ~/.nvm/versions/node/v20.12.1/bin/node
    npm: 10.5.0 - ~/.nvm/versions/node/v20.12.1/bin/npm <----- active
    pnpm: 8.15.6 - ~/.nvm/versions/node/v20.12.1/bin/pnpm
  Browsers:
    Chrome: 124.0.6367.208
    Edge: 124.0.2478.105
    Safari: 17.4.1
```


### Additional context

_No response_
Repository: next.js
Issue: Double redirect in RSC page when using a loading boundary
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/PaulWild/multiple-redirects-in-rsc/

### To Reproduce

- go to `/`
- Server component will redirect to `/api/redirect`
- The api route is called twice as seen by the terminal logs. 

### Current vs. Expected behaviour

The api route should only be called once

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Jan 11 04:09:03 UTC 2024
  Available memory (MB): 15935
  Available CPU cores: 8
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.3.0-canary.62 // Latest available version is detected (14.3.0-canary.62).
  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)

Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local), Vercel (Deployed)

### Additional context

This doesn't happen if there aren't any loading pages. This seems to be related to https://github.com/vercel/next.js/issues/57257