sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [PT2E Quantization] `prepare_pt2e` produces inconsistent data types for primitive int
Labels: oncall: quantization

### 🐛 Describe the bug

It appears that the `prepare_pt2e` function converts primitive integers to tensors, but the resulting data types are inconsistent. This inconsistency can cause quantization to fail,  especially for models with embedding layers.

#### Code
```python
import torch
import torch.export._trace
from torch.ao.quantization.quantize_pt2e import prepare_pt2e
from torch.ao.quantization.quantizer.xnnpack_quantizer import (
    XNNPACKQuantizer,
    get_symmetric_quantization_config,
)

class Net(torch.nn.Module):
    def __init__(self):
        super().__init__()

    def forward(self, x):
        return x + 2

input = torch.tensor(1, dtype=torch.int64)
model_exported = torch.export._trace._export(
    Net(), (input,), pre_dispatch=True
).module()
model_exported.graph.print_tabular()
output_exported = model_exported(input)

model_prepared = prepare_pt2e(
    model_exported,
    XNNPACKQuantizer().set_global(
        get_symmetric_quantization_config(is_per_channel=True)
    ),
)
model_prepared.graph.print_tabular()
output_prepared = model_prepared(input)

print(f'{output_exported.dtype=}')
print(f'{output_prepared.dtype=}')
print(f'{model_prepared._tensor_constant_0=}')
```

#### Output
```
opcode         name      target           args         kwargs
-------------  --------  ---------------  -----------  --------
placeholder    arg0_1    arg0_1           ()           {}
call_function  add       aten.add.Tensor  (arg0_1, 2)  {}
output         output_1  output           ((add,),)    {}

opcode         name                target              args                          kwargs
-------------  ------------------  ------------------  ----------------------------  --------
placeholder    arg0_1              arg0_1              ()                            {}
get_attr       _tensor_constant_0  _tensor_constant_0  ()                            {}
call_function  add                 aten.add.Tensor     (arg0_1, _tensor_constant_0)  {}
output         output_1            output              ((add,),)                     {}

output_exported.dtype=torch.int64
output_prepared.dtype=torch.float32

model_prepared._tensor_constant_0=tensor(2.)
```

#### Expected
```
output_exported.dtype == output_prepared.dtype == torch.int64
```

### Versions

`torch==2.3.0`

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel
Repository: TypeScript
Issue: TS 5.4.5: Return type for performance.getEntriesByType is inaccurate
Labels: Bug,Help Wanted,Domain: lib.d.ts

### ⚙ Compilation target

ESNexr

### ⚙ Library

lib.dom.d.ts

### Missing / Incorrect Definition

The return type for `getEntriesByType` is a union of many different object types. A list can be seen in the spec, or at https://developer.mozilla.org/en-US/docs/Web/API/PerformanceEntry ("The PerformanceEntry instances will always be one of the following subclasses:: _[List of possibel sub-classes]_")

The return type can - and I think should - be hard-coded for the respective string parameter to `getEntriesByType`, since there is a limited short list of possible string constants, and each corresponds exactly to one possible return type. Maybe an overloaded definition for this function?

Right now the return type is set to `PerformanceEntryList`, which is `PerformanceEntry[]`, and that type is an interface with only the minimal number of entries.

The effect is that when I use, for example, `performance.getEntriesByType('navigation')`, I get a TypeScript error trying to access the properties on the `PerformanceNavigationTiming` array I get from that query.

### Sample Code

[Playground Link](https://www.typescriptlang.org/play/?#code/GYVwdgxgLglg9mABABwIYHMCmB1VBnAJU1QBs5UATTCgCgEoAuRAIzjhOKQG8AoRfxACdMUEIKTJMg4HEEBbVJEx8BqgHRYoAUTBRBMTHgBCATwAqJyTQDkYVADcY6VLATW6K1fwD03xFsFBWSYzAGUAJgBmSIBOJgAFIMlBKBNEVMlECjhDRDA4KERMAA8YPEKEdMtMRHipGXlFCEwdPRNPL19EMwALMsR+gHcgsHQAGhZMCFQQPBqoPrwBpdRa+tkFJQA5BycXeDAzGDkYUcQ4ZgArKagO9Tw4OUwaTF1BNIBeAD4it5M1DI1D7AxDWYRkSjuADcPAAvkA)

```TypeScript
function pageWasRealoaded(): boolean {
    return performance
        .getEntriesByType('navigation')
        // Error: TS2339: Property type does not exist on type PerformanceEntry
        // This is wrong, because this is a PerformanceNavigationTiming object
        .some(entry => entry.type === 'reload');
}
```


### Documentation Link

https://developer.mozilla.org/en-US/docs/Web/API/PerformanceEntry
Repository: godot
Issue: Fragment shader on Control material: SCREEN_UV uses editor viewport coordinate instead of canvas layer coordinate
Labels: topic:editor,needs testing,topic:2d

### Tested versions

- Reproducible in v4.2.1.stable.official [b09f793f5]

### System information

Godot v4.2.1.stable - Ubuntu 22.04.4 LTS 22.04 - X11 - Vulkan (Mobile) - dedicated NVIDIA GeForce GTX 860M (nvidia; 535.161.07) - Intel(R) Core(TM) i7-4710HQ CPU @ 2.50GHz (8 Threads)

### Issue description

This is a reboot of https://github.com/godotengine/godot/issues/33905 for Godot 4

When using SCREEN_UV in a fragment shader, and assigning a Shader Material using it on a Control on some Canvas Layer, the material preview will consider the editor viewport coordinates as UV instead of the Canvas Layer, which will be used in the game at runtime.

Using this shader:

```glsl
shader_type canvas_item;

void fragment()
{
	COLOR = vec4(SCREEN_UV, 0.0, 1.0);
}
```

on a fullscreen ColorRect, I get different results depending on viewport view.

When the rect fills the viewport, I get a result similar to what I want ingame at runtime:

![image](https://github.com/godotengine/godot/assets/1067772/8d2e78a9-f72f-4a36-a4d6-6b98857721bc)

Runtime:
![image](https://github.com/godotengine/godot/assets/1067772/2d561d1b-afa2-4eec-b245-c723ea73627b)

When zooming out and panning the view, results differ:

![image](https://github.com/godotengine/godot/assets/1067772/f49c7440-8d21-4722-9317-eb13604fdade)
![image](https://github.com/godotengine/godot/assets/1067772/ec50d51d-88b5-4b86-82b4-21cac4e6f8ff)
![image](https://github.com/godotengine/godot/assets/1067772/5c53a227-aa81-4227-9edb-0153fdf5eaa6)

I understand that there is no easy way to guess what SCREEN_UV will be in all cases:
- if the shader material is used on a Node2D/3D, this depends on its placement on the viewport, which depends on the camera position and zoom
- if the shader material is used on a Control in the wild, without a Canvas Layer (not recommended, but sometimes convenient to place a small UI widget near a world character), there is no context to refer to either, except the Camera looking at the Node2D/3D it may be parented to

However, when the shader material is used on a Control under a Canvas Layer, it may be feasible to estimate where it will be relative to the future game screen (need to mind Stretch Scale though). In this case, it may be worth previewing the shader material using Canvas Layer normalized coordinates as SCREEN_UV.

### Steps to reproduce

1. Open MWE, demo scene
2. Pan the view and zoom in/out in the editor
3. Observe how the ColorRect changes appearance

### Minimal reproduction project (MRP)

[v4.2.1 - Editor viewport affects behavior of SCREEN_UV.zip](https://github.com/godotengine/godot/files/15432760/v4.2.1.-.Editor.viewport.affects.behavior.of.SCREEN_UV.zip)
Repository: excalidraw
Issue: Slow arrow navigation when elements are selected
Labels: bug

Due to `keyUp` handler triggering `bindOrUnbindLinearElements` after each `keyDown` in command palette, color picker, font picker, etc.

On the recording below pressing arrow down in rapid succession, notice the slowdown and how the items are skipped.

https://github.com/excalidraw/excalidraw/assets/20387666/54fbc53d-fb97-4d56-b845-15bdad1663ca

<img width="954" alt="image" src="https://github.com/excalidraw/excalidraw/assets/20387666/dc6d5dbf-f428-4324-8308-2e4f7aa0d273">
Repository: tensorflow
Issue: Local rendezvous is aborting with status: OUT_OF_RANGE: End of sequence when call some methods of `tf.data`
Labels: stat:awaiting tensorflower,type:bug,comp:data,TF 2.16

### Issue type

Bug

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

Yes

### Source

source

### TensorFlow version

tf 2.16

### Custom code

Yes

### OS platform and distribution

Linux Ubuntu 22.04.3 LTS (x86_64)

### Mobile device

_No response_

### Python version

3.12.3

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

When calling and iterating over the results of some of tf.data's methods it outputs "Local rendezvous is aborting with status: OUT_OF_RANGE: End of sequence".

### Standalone code to reproduce the issue

```shell
import tensorflow as tf

def dataset_test():
 
    dataset = tf.data.Dataset.from_tensor_slices(["apple", "banana", "cherry"])
    # dataset = tf.data.TextLineDataset(["file1.txt", "file2.txt"]).range(10)             # same output
    # dataset = tf.data.TFRecordDataset(["file1.tfrecords", "file2.tfrecords"]).range(10) # same output
    # dataset = tf.data.Dataset.from_tensors([1,2,3]).range(10)                           # same output

    print(list(dataset.as_numpy_iterator()))

if __name__ == "__main__":
    dataset_test()
```


### Relevant log output

```shell
2024-05-24 06:23:06.268182: I tensorflow/core/util/port.cc:113] oneDNN custom operations are on. You may see slightly different numerical results due to floating-point round-off errors from different computation orders. To turn them off, set the environment variable `TF_ENABLE_ONEDNN_OPTS=0`.
2024-05-24 06:23:06.309884: I tensorflow/core/platform/cpu_feature_guard.cc:210] This TensorFlow binary is optimized to use available CPU instructions in performance-critical operations.
To enable the following instructions: AVX2 AVX512F AVX512_VNNI FMA, in other operations, rebuild TensorFlow with the appropriate compiler flags.
2024-05-24 06:23:06.908161: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT
2024-05-24 06:23:07.558225: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1928] Created device /job:localhost/replica:0/task:0/device:GPU:0 with 22137 MB memory:  -> device: 0, name: NVIDIA GeForce RTX 3090, pci bus id: 0000:18:00.0, compute capability: 8.6
2024-05-24 06:23:07.558795: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1928] Created device /job:localhost/replica:0/task:0/device:GPU:1 with 22453 MB memory:  -> device: 1, name: NVIDIA GeForce RTX 3090, pci bus id: 0000:af:00.0, compute capability: 8.6
2024-05-24 06:23:07.917142: W tensorflow/core/framework/local_rendezvous.cc:404] Local rendezvous is aborting with status: OUT_OF_RANGE: End of sequence
```
Repository: react-native
Issue: BackHandler Does Not Work Google Pixel
Labels: API: BackHandler,Needs: Repro,Needs: Attention

### Description

More detail: https://github.com/react-navigation/react-navigation/issues/11227

It seems on Google Pixel devices the BackHandler does not work

### Steps to reproduce

Use back handler on Google Pixel 6+ device

### React Native Version

0.74

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
System:
  OS: Windows 10 10.0.19045
  CPU: (20) x64 Intel(R) Core(TM) i9-10850K CPU @ 3.60GHz
  Memory: 64.71 GB / 127.92 GB
Binaries:
  Node:
    version: 20.13.1
    path: C:\Program Files\nodejs\node.EXE
  Yarn:
    version: 4.2.1
    path: C:\Program Files\nodejs\yarn.CMD
  npm:
    version: 10.5.2
    path: C:\Program Files\nodejs\npm.CMD
  Watchman: Not Found
SDKs:
  Android SDK:
    API Levels:
      - "29"
      - "31"
      - "33"
      - "34"
    Build Tools:
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 32.0.0
      - 33.0.0
      - 33.0.1
      - 34.0.0
      - 35.0.0
    System Images:
      - android-29 | Google Play Intel x86 Atom
      - android-30 | Google Play Intel x86 Atom
      - android-31 | Google Play Intel x86_64 Atom
      - android-33 | Google Play Intel x86_64 Atom
      - android-34 | Google APIs Intel x86_64 Atom
    Android NDK: Not Found
  Windows SDK:
    AllowAllTrustedApps: Enabled
    AllowDevelopmentWithoutDevLicense: Enabled
    Versions:
      - 10.0.17763.0
IDEs:
  Android Studio: Not Found
  Visual Studio: Not Found
Languages:
  Java: 17.0.11
  Ruby: Not Found
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.73.8
    wanted: 0.73.8
  react-native-windows: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: Not found
  newArchEnabled: Not found
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
N/A
```


### Reproducer

https://github.com/Roamer77/Android13backButtonBug

### Screenshots and Videos

_No response_
Repository: PowerToys
Issue: PowerRename add shortcut and remember settings option
Labels: Needs-Triage

### Description of the new feature / enhancement

**Shortcut**
It would be great to have a shortcut (only when Windows Explorer is the active window) to easily access PowerRename.
A great default would be CTRL+H as it is the shortcut used in many applications to find & replace text.

**Separate retain settings option**
Another quirk is that you have to enable "auto-complete" in the PowerRename settings, to not only get a recents list, but also for it to remember the settings within PowerRename. Like the checkboxes for RegEx, first/all occurrences, case sensitivity and the icons for including files/folder/sub-folders and so on.
It would be good if you can set this separately from auto-complete.
The default setting once implemented could align with whether auto-complete is on or not, as this funcionality is now tied to that setting.

**Improve auto-complete**
Also auto-complete needs a clear all recents button (either in main settings or within PowerRename UI) and it would be good if SHIFT+DEL would work for deleting a single entry from the recents drop-down list as it does in Windows Explorer searchbar and all browser auto-fill fields.


These (small) improvements would make using PowerRename much better and easier to customize without needing many or complicated settings.
Thanks for all the work everyone is putting into this project.

### Scenario when this would be used?

While in PowerToys settings and in Windows Explorer.
Self-explanatory from description above.

### Supporting information

_No response_
Repository: pytorch
Issue: Wrong Flag defined for ppc64le arch
Labels: module: cpu,triaged

### 🐛 Describe the bug

I am trying to build Pytorch-2.3.0 version on ppc64le arch. While building, I came across an error message saying 
```
/opt/conda/conda-bld/pytorch-base_1716205318660/work/caffe2/utils/bench_utils.cc: In function 'uint32_t caffe2::wipe_cache()':
/opt/conda/conda-bld/pytorch-base_1716205318660/work/caffe2/utils/bench_utils.cc:100:31: error: '_SC_LEVEL1D_CACHE_SIZE' was not declared in this scope; did you mean '_SC_LEVEL1_DCACHE_SIZE'?
  100 |           wipe_size = sysconf(_SC_LEVEL1D_CACHE_SIZE);
      |                               ^~~~~~~~~~~~~~~~~~~~~~
      |                               _SC_LEVEL1_DCACHE_SIZE
make[2]: *** [caffe2/CMakeFiles/torch_cpu.dir/build.make:8259: caffe2/CMakeFiles/torch_cpu.dir/utils/bench_utils.cc.o] Error 1
make[2]: *** Waiting for unfinished jobs....
```
I checked the parameter passed to `sysconf` and I think it should have been `_SC_LEVEL1_DCACHE_SIZE` instead of `_SC_LEVEL1D_CACHE_SIZE`. The function is defined at https://github.com/pytorch/pytorch/blob/56c412d9063de3dc8163b8e1b0b9b5bf9581ad05/caffe2/utils/bench_utils.cc#L100

Any help would be appreciated,
Thank You!

### Versions

```
OS: Red Hat Enterprise Linux 9.3 (Plow) (ppc64le)
Python version: 3.11.5
```

cc @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10
Repository: material-ui
Issue: [material-ui][docs] Table demo EnhancedTable crashes
Labels: docs,component: table,package: material-ui

<!-- Please make sure you have fulfilled the following items before submitting -->
<!-- Checked checkbox should look like this: [x] -->
- [ ] I have [searched for similar issues](https://github.com/mui/material-ui/issues?q=is%3Aissue%20%5Bdocs%5D%20Demo%20EnhancedTable%20crashes) in this repository and believe that this is not a duplicate.

## Steps to reproduce
1. Visit https://mui.com/material-ui/react-table/
2. ??
3. demo *EnhancedTable* crashes

## Your environment
| Tech         | Version |
|--------------|---------|
| Version  | v5.15.18  |
| Netlify deploy | https://664b46aca0146000083372a3--material-ui-docs.netlify.app |
| Browser      | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36 Edg/125.0.0.0 |


**Search keywords**:
Repository: PowerToys
Issue: Paste as Plain Text - Excel Bug
Labels: Issue-Bug,Product-Advanced Paste

### Microsoft PowerToys version

0.80.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Advanced Paste

### Steps to reproduce

Copy 1 or more cells in Excel, then paste in Excel as plain text with ctrl-win-alt v.


### ✔️ Expected Behavior

I would expect Paste as Plain Text to have the same size as my initial selection, and for all formatting to be removed.

### ❌ Actual Behavior

1 row of cells directly beneath my paste area is cleared, as if I had copied my selection + blank cells beneath my selection.  It doesn't matter if I make a horizontal selection or a vertical selection, 1 row of null cells is allways pasted beneath my selection.

For example:

**Copy:** 
_Hello_ | _Goodbye_
**Paste:** 
_Hello_ | _Goodbye_
_null_ | _null_

![image](https://github.com/microsoft/PowerToys/assets/160156148/6f0ef763-0167-486e-b5ea-069c3bf02a1f)


### Other Software

Microsoft® Excel® for Microsoft 365 MSO (Version 2406 Build 16.0.17716.20002) 64-bit 

[PowerToysReport_2024-05-24-09-26-58.zip](https://github.com/microsoft/PowerToys/files/15435215/PowerToysReport_2024-05-24-09-26-58.zip)
Repository: vscode
Issue: Adopt Hover Verbosity Level API in the GitHub Issue showing through URLs
Labels: feature-request,editor-hover

Adopt Hover Verbosity Level API in the GitHub Issue showing through URLs
Repository: rust
Issue: Calling non-const function `core::slice::iter::<impl IntoIterator for &[u8]>::into_iter`
Labels: A-diagnostics,T-compiler,A-const-eval,D-terse

I didn't find a clear issue that was talking about that, and I'm clearly in the "nightly scape" of Rust here. I'm trying to build the following code (don't take attention to the possible unsafe part of this code, I omitted voluntary some part for better clarity):

[Playground link](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=ffb7c0eba60a5977f2650ab2d0b89360):

```rust
#![feature(const_mut_refs)]
#![feature(const_for)]
#![feature(const_maybe_uninit_write)]
#![feature(effects)]

use core::mem::MaybeUninit;

#[must_use]
const fn from_slice_unchecked(from_slice: &[u8]) -> [MaybeUninit<u8>; 1]
{
    let mut vec = [MaybeUninit::uninit(); 1];

    for byte in from_slice {
        vec[0].write(*byte);
    }

    vec
}

fn main() {
    let _ = const { from_slice_unchecked(&[0]) };
}
```

```rust
error[E0080]: evaluation of `main::{constant#0}` failed
  --> src/main.rs:13:17
   |
13 |     for byte in from_slice {
   |                 ^^^^^^^^^^ calling non-const function `core::slice::iter::<impl IntoIterator for &[u8]>::into_iter`
   |
note: inside `from_slice_unchecked`
  --> src/main.rs:13:17
   |
13 |     for byte in from_slice {
   |                 ^^^^^^^^^^
note: inside `main::{constant#0}`
  --> src/main.rs:21:21
   |
21 |     let _ = const { from_slice_unchecked(&[0]) };
   |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^

note: erroneous constant encountered
  --> src/main.rs:21:13
   |
21 |     let _ = const { from_slice_unchecked(&[0]) };
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0080`.
```

It does build if I don't const inline the call to `from_slice_unchecked()` though. But here, I'm wanted to create this buffer at build time and I don't find a way to do it "easily".

The closer issue I could find is https://github.com/rust-lang/rust/issues/103265 which contains this closed PR https://github.com/rust-lang/rust/pull/102225.
Repository: vscode
Issue: document 'bicep-extsrc:br%<REDACTED: user-file-path>%<REDACTED: user-file-path> %28private-endpoint%3A0.4.1%29?br%3Amcr.microsoft.com%2Fbicep%2Favm%2Fres%2Fnetwork%2Fprivate-endpoint%3A0.4.1#main.bicep' NOT found
Labels: error-telemetry

```javascript
Error: document 'bicep-extsrc:br%<REDACTED: user-file-path>%<REDACTED: user-file-path> %28private-endpoint%3A0.4.1%29?br%3Amcr.microsoft.com%2Fbicep%2Favm%2Fres%2Fnetwork%2Fprivate-endpoint%3A0.4.1#main.bicep' NOT found
at k.changeLanguage in src/vs/workbench/api/common/extHostLanguages.ts:46:10
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=4207ee1f8ddac59df509b75e4bdd1c77904f766e&bH=def4f113-2477-843e-a78b-7a239530e69b)
Repository: next.js
Issue: Unsupported Node.js version! Your version: undefined
Labels: bug

### Link to the code that reproduces this issue

https://github.com/richtera/wownar

### To Reproduce

```console
git checkout https://github.com/richtera/wownar
cd wownar
yarn
yarn build
```
The same thing happens with yarn pages:build which is why I posted an issue there first https://github.com/cloudflare/next-on-pages/issues/791

### Current vs. Expected behavior

Currently is errors out because the polyfill for process doesn't have version on it.
Rewriting the polyfill as
```js
function createProcessPolyfill() {
    const processPolyfill = {
        env: buildEnvironmentVariablesFrom(),
        version: process.version
    };
    const overridenValue = {};
    for (const key of Object.keys(process)){
        if (key === "env" || key === "version") continue;
        Object.defineProperty(processPolyfill, key, {
            get () {
                if (overridenValue[key] !== undefined) {
                    return overridenValue[key];
                }
                if (typeof process[key] === "function") {
                    return ()=>throwUnsupportedAPIError(`process.${key}`);
                }
                return undefined;
            },
            set (value) {
                overridenValue[key] = value;
            },
            enumerable: false
        });
    }
    return processPolyfill;
}
```

https://github.com/vercel/next.js/blob/2966b85bccf0d2593e04dd3aa0ac474f53715d2f/packages/next/src/server/web/sandbox/context.ts#L130

makes builds pass. I can't tell when this started or anything about that however. This is just a fresh nextjs project I got from elsewhere https://github.com/neynarxyz/farcaster-examples/tree/main/wownar and the bug is inside of next.js

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:49 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 12
Binaries:
  Node: 20.5.1
  npm: 9.8.0
  Yarn: 4.2.2
  pnpm: 8.8.0
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Not sure, Developer Experience

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

next build (local)

### Additional context

Since the code in canary is still missing "version" I am not sure if makes sense to attempt a canary build.