sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: inductor slow kernel choice for max(x) if x is not contiguous
Labels: triaged,oncall: pt2,module: inductor

### 🐛 Describe the bug

I noticed that if `x` is not contiguous, torchinductor generates unexpectedly slow cuda kernels for `torch.max(x)`.  Small repro:

```
import torch
import fire
from torch._inductor.utils import do_bench_using_profiling

torch.manual_seed(0)

def get_max(x):
    x = torch.max(x)
    return x

def run(is_contiguous: bool = True):
    x = torch.randn(4096, 8192, dtype=torch.bfloat16, device="cuda")

    if not is_contiguous:
        x = x.t().contiguous().t()

    get_max_c = torch.compile(get_max)

    # warmup
    y = get_max_c(x)

    # perf
    duration_microseconds = do_bench_using_profiling(lambda: get_max_c(x))
    print('duration in microseconds', duration_microseconds)

if __name__ == '__main__':
    fire.Fire(run)
```

Running this script with `is_contiguous=True` results in the expected (to me) pattern of a two stage reduction.  Running this script with `is_contiguous=False` results in a three stage reduction, which seems to be significantly slower than the two-stage variant - ~8x slower on my machine for this example input.

Example script calls with logs:

```
> TORCH_LOGS_FORMAT="short" TORCH_LOGS="output_code" python ~/local/tmp/20250108_max_repro.py --is_contiguous True 2>&1 | with-proxy gh gist create
- Creating gist...
✓ Created secret gist
https://gist.github.com/vkuzo/4798af9dbd1a13ff66d9586312c04d03

> TORCH_LOGS_FORMAT="short" TORCH_LOGS="output_code" python ~/local/tmp/20250108_max_repro.py --is_contiguous False 2>&1 | with-proxy gh gist create
- Creating gist...
✓ Created secret gist
https://gist.github.com/vkuzo/6b9d3e1397ff808b4897d75a59b7eaab
```

For context, I noticed this during a refactor of torchao float8 code (https://github.com/pytorch/ao/pull/1481).  I can work around by manually passing contiguous tensors to `max(tensor)` in the modeling code, but sharing this as it was unexpected.

### Versions

PyTorch commit: 768d73f6929be2a6eb81fe7424416dceb4a4aca9 (main branch)
hardware: NVIDIA H100

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @aakhundov @BoyuanFeng
Repository: storybook
Issue: [Bug]: Matching characters in search results disappear when using High Contrast Mode (hcm)
Labels: bug,ui,accessibility

### Describe the bug

When in Windows High Contrast Mode, matching characters in the search results disappear into the background. ![Screenshot showing the issue at hand](https://github.com/user-attachments/assets/73d5650b-cedc-4ef5-92e3-446cfe368f61)


### Reproduction link

https://github.com/TGiles/storybook-test

### Reproduction steps

1. Given a new Storybook instance that was created via `npx storybook@next init`, [see my storybook-test repo for this new instance](https://github.com/TGiles/storybook-test) and running either Windows 10 or Windows 11
2. Enable High Contrast Mode
3. Serve new Storybook instance locally
4. Use the search bar and type in the character "d"

Expected Results:
- The "d" in Docs is highlighted or marked in some way that indicates a match to the search query

Actual Results:
- The "d" in Docs is set to the background/canvas color and becomes invisible.

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (24) x64 AMD Ryzen 9 9900X 12-Core Processor
  Binaries:
    Node: 22.13.0 - C:\nvm4w\nodejs\node.EXE
    Yarn: 1.22.22 - C:\nvm4w\nodejs\yarn.CMD
    npm: 10.9.2 - C:\nvm4w\nodejs\npm.CMD <----- active
  Browsers:
    Chrome: 131.0.6778.206
    Edge: Chromium (127.0.2651.98)
  npmPackages:
    @storybook/addon-essentials: ^8.5.0-beta.8 => 8.5.0-beta.8
    @storybook/blocks: ^8.5.0-beta.8 => 8.5.0-beta.8
    @storybook/test: ^8.5.0-beta.8 => 8.5.0-beta.8
    @storybook/web-components: ^8.5.0-beta.8 => 8.5.0-beta.8
    @storybook/web-components-vite: ^8.5.0-beta.8 => 8.5.0-beta.8
    chromatic: ^11.22.1 => 11.22.1
    storybook: ^8.5.0-beta.8 => 8.5.0-beta.8
```

### Additional context

_No response_
Repository: rust
Issue: "error occurred: unknown target" when trying to add a new target
Labels: T-bootstrap,C-bug,A-contributor-roadblock

when forking the rust-lang/rust repo and attempting to add support for a new target triple, x will fail to recognise the new target when trying to build the cross compiling rustc

this happens when exactly following the directions laid out by "adding a new target" on the rustc dev guide, so either x has an issue with building the new rustc, or the documentation needs updating!

i've added the target triple to the supported targets macro, included it in the stage0 missing targets array, and (not entirely sure if this is necessary but still did it) supplied a json file with a rough specification of the target platform

the exact error given by x (presumably coming from the rustc used for building) is: `error occurred: unknown target 'my-target-triple'`
Repository: storybook
Issue: [Bug]: Difficult to determine if text is a link or not in High Contrast Mode (hcm)
Labels: bug,ui,accessibility

### Describe the bug

When in High Contrast Mode on Windows 10 or 11, it is difficult to determine if certain text is an interactive link or not. For example, hovering over the settings cog will change the cursor to a pointer and change the background color, while focusing the settings cog will display an outline around the button.

When hovering or keyboard navigating through the docs, components, and stories in the sidebar, the only indication that these items are interactive is the cursor to pointer change. 

![Image](https://github.com/user-attachments/assets/a41ecdd1-73af-49a1-a965-a4ac8c805eb5)



### Reproduction link

https://github.com/TGiles/storybook-test

### Reproduction steps

1. Given a newly created Storybook instance and a machine running Windows 10 or Windows 11
2. Enable High Contrast Mode
3. Navigate through the sidebar (either hovering or keyboard navigation)

Expected result:
- Links have an indicator, other than the cursor turning into a pointer, that distinguishes the text as a link.

Actual result:
- Links only have the cursor to pointer change, making it difficult to determine if the item is a button or a link that can be interacted with.

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (24) x64 AMD Ryzen 9 9900X 12-Core Processor
  Binaries:
    Node: 22.13.0 - C:\nvm4w\nodejs\node.EXE
    Yarn: 1.22.22 - C:\nvm4w\nodejs\yarn.CMD
    npm: 10.9.2 - C:\nvm4w\nodejs\npm.CMD <----- active
  Browsers:
    Chrome: 131.0.6778.206
    Edge: Chromium (127.0.2651.98)
  npmPackages:
    @storybook/addon-essentials: ^8.5.0-beta.8 => 8.5.0-beta.8
    @storybook/blocks: ^8.5.0-beta.8 => 8.5.0-beta.8
    @storybook/test: ^8.5.0-beta.8 => 8.5.0-beta.8
    @storybook/web-components: ^8.5.0-beta.8 => 8.5.0-beta.8
    @storybook/web-components-vite: ^8.5.0-beta.8 => 8.5.0-beta.8
    chromatic: ^11.22.1 => 11.22.1
    storybook: ^8.5.0-beta.8 => 8.5.0-beta.8
```

### Additional context

Having the cursor: pointer is helpful, but having some form of underline on links is extremely beneficial in HCM. There are a few ways to handle this:

- Make underlines appear on hover and focus. This strategy is what [Wikipedia uses for their links](https://github.com/TGiles/storybook-test/blob/main/links_underline_on_hover_wikipedia.png). ![Image](https://github.com/user-attachments/assets/3579606c-0909-4236-acaa-d2ccf79d4977)

- Always show underlines but make them disappear on hover and focus. MDN uses this for links in the [main content of articles](https://github.com/TGiles/storybook-test/blob/main/links_underline_disappears_on_hover_mdn.png). ![Image](https://github.com/user-attachments/assets/1b699d1e-4d42-4e14-ab53-ec0a399f1a2b)

 - Always show underlines regardless of hover and focus. This is the default user agent styling in Firefox, seen in this [demo on MDN](https://github.com/TGiles/storybook-test/blob/main/links_underline_always_present_mdn.png) ![Image](https://github.com/user-attachments/assets/0944592e-b67c-4841-b6bf-15685a5f2b4a)
Repository: godot
Issue: Spurious Warning on Menu Accelerators With Mask Modifiers
Labels: bug,topic:gdscript

### Tested versions

Reproducible in 4.3dev

### System information

N/A

### Issue description

Adding accelerators the documented way is creating spurious warnings when a modifier mask is used.
NOTE: I already checked, it's not the 2nd parameter that's the error since the 1st line here does not get an error.
```gdscript
	popup.add_item("Rail Line", -1, KEY_T)
	popup.add_item("Train Station", -1, KEY_MASK_CTRL | KEY_MASK_SHIFT | KEY_T)
	popup.add_item("Freight Depot", -1, KEY_MASK_ALT | KEY_T)
```

The errors for the 2nd and 3rd items are:
```
W 0:00:02:0329   Integer used when an enum value is expected. If this is intended cast the integer to the enum type.
  <C++ Error>    INT_AS_ENUM_WITHOUT_CAST
  <C++ Source>   new_tools_container.tscn::GDScript_erqco:10
W 0:00:02:0329   Cannot pass 301989972 as Enum "Key": no enum member has matching value.
  <C++ Error>    INT_AS_ENUM_WITHOUT_MATCH
  <C++ Source>   new_tools_container.tscn::GDScript_erqco:10
W 0:00:02:0329   Integer used when an enum value is expected. If this is intended cast the integer to the enum type.
  <C++ Error>    INT_AS_ENUM_WITHOUT_CAST
  <C++ Source>   new_tools_container.tscn::GDScript_erqco:11
W 0:00:02:0329   Cannot pass 67108948 as Enum "Key": no enum member has matching value.
  <C++ Error>    INT_AS_ENUM_WITHOUT_MATCH
  <C++ Source>   new_tools_container.tscn::GDScript_erqco:11
```

I don't expect this since this is what the docs say to do:
![Image](https://github.com/user-attachments/assets/b8c69c88-548a-4f06-91cb-713669179309)



### Steps to reproduce

Given above small script ^^^

### Minimal reproduction project (MRP)

N/A its in the docs
Repository: next.js
Issue: [turbopack] dynamic imports fallback to single existing file when target file does not exist
Labels: Turbopack

### Link to the code that reproduces this issue

https://github.com/qnten/reproduction-dynamic-import

### To Reproduce

1. Start the application in dev with turbo enabled `npm run dev`
2. The page `/` should display the following:

```
1. first file exists so "first name" should be displayed: first file
2. second file does not exist so "no name found" should be displayed: first file
3. third file does not exist so "no name found" should be displayed: first file
```

### Current vs. Expected behavior

**Current Behavior**

When using dynamic import to load files from a directory that contains only one file, the import incorrectly falls back to that existing file even if the requested file does not match the import path. Specifically, in the provided example:
	•	First File (first.ts): Exists and correctly returns "first name".
	•	Second File (second.ts): Does not exist, but getExportFromFile("second") still returns "first name" instead of "no name found".
	•	Third File (third.ts): Does not exist, but getExportFromFile("third") also returns "first name" instead of "no name found".

_This behavior occurs only when the directory contains a single file. If a second file is added (`second.ts`) everything works as expected._

**Expected Behavior**

The dynamic import should strictly attempt to load the specified file based on the provided path. If the target file does not exist within the directory, the import should throw.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Dec  6 19:01:59 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 22.4.1
  npm: 10.8.1
  Yarn: 1.22.22
  pnpm: 9.5.0
Relevant Packages:
  next: 15.2.0-canary.1 // Latest available version is detected (15.2.0-canary.1).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```


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

Turbopack

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

next dev (local)

### Additional context

_No response_
Repository: langchain
Issue: langchain-cli for MacOS unable to load required files
Labels: 🤖:bug

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

When calling langchain-cli migrate <path> I get the error below.

### Error Message and Stack Trace (if applicable)

CLIError: Failed to download Grit CLI from 
https://github.com/getgrit/gritql/releases/latest/download/marzano-aarch64-apple-darwin.tar.gz

### Description

Migrate versions according to the documentation

### System Info

System Information
------------------
> OS:  Darwin
> OS Version:  Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:46 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6031
> Python Version:  3.12.5 (main, Aug  6 2024, 19:08:49) [Clang 15.0.0 (clang-1500.3.9.4)]

Package Information
-------------------
> langchain_core: 0.3.29
> langchain: 0.3.14
> langchain_community: 0.3.14
> langsmith: 0.1.148rc1
> langchain_anthropic: 0.2.4
> langchain_cli: 0.0.35
> langchain_experimental: 0.3.4
> langchain_google_genai: 2.0.7
> langchain_openai: 0.2.14
> langchain_pinecone: 0.2.0
> langchain_text_splitters: 0.3.4
> langgraph_sdk: 0.1.48
> langserve: 0.3.1

Other Dependencies
------------------
> aiohttp: 3.9.5
> anthropic: 0.42.0
> async-timeout: Installed. No version info available.
> dataclasses-json: 0.6.7
> defusedxml: 0.7.1
> fastapi: 0.115.6
> filetype: 1.2.0
> gitpython: 3.1.44
> google-generativeai: 0.8.3
> gritql: 0.1.5
> httpx: 0.28.1
> httpx-sse: 0.4.0
> jsonpatch: 1.33
> langserve[all]: Installed. No version info available.
> langsmith-pyo3: Installed. No version info available.
> numpy: 1.26.4
> openai: 1.59.3
> orjson: 3.10.13
> packaging: 24.2
> pinecone-client: 5.0.1
> pydantic: 2.10.4
> pydantic-settings: 2.7.1
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> SQLAlchemy: 2.0.36
> sse-starlette: 1.8.2
> tenacity: 9.0.0
> tiktoken: 0.8.0
> tomlkit: 0.13.2
> typer[all]: Installed. No version info available.
> typing-extensions: 4.12.2
> uvicorn: 0.34.0
Repository: pytorch
Issue: [dynamo][graph break] omegaconfig ListConfig `__contains__`
Labels: triaged,oncall: pt2,module: dynamo

### 🐛 Describe the bug

Fixing this graph break should help with the performance regression in https://github.com/pytorch/pytorch/issues/132872

~~~

+    @unittest.skipIf(not HAS_OMEGACONG, "missing omegaconf package")
+    def test_omegaconf_listconfig_contains(self):
+        def fn(cfg, x):
+            if 1 in cfg:
+                return torch.sin(x)
+            return torch.cos(x)
+
+        config = list_config = OmegaConf.create([1, 2, 3, {"key": "value"}])
+
+        x = torch.randn(4)
+        opt_fn = torch.compile(fn, backend="eager", fullgraph=True)
+        self.assertEqual(fn(config, x), opt_fn(config, x))
+
+
~~~

### Error logs

```
  File "/home/anijain/local/pytorch/torch/_dynamo/symbolic_convert.py", line 1076, in run
    while self.step():
          ^^^^^^^^^^^
  File "/home/anijain/local/pytorch/torch/_dynamo/symbolic_convert.py", line 986, in step
    self.dispatch_table[inst.opcode](self, inst)
  File "/home/anijain/local/pytorch/torch/_dynamo/symbolic_convert.py", line 1676, in COMPARE_OP
    self.push(compare_op_handlers[inst.argval](self, self.popn(2), {}))
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/anijain/local/pytorch/torch/_dynamo/variables/builtin.py", line 1008, in call_function
    return handler(tx, args, kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/anijain/local/pytorch/torch/_dynamo/variables/builtin.py", line 859, in builtin_dispatch
    unimplemented(error_msg)
  File "/home/anijain/local/pytorch/torch/_dynamo/exc.py", line 356, in unimplemented
    raise Unsupported(msg, case_name=case_name)
torch._dynamo.exc.Unsupported: builtin: eq [<class 'torch._dynamo.variables.user_defined.UserDefinedObjectVariable'>, <class 'torch._dynamo.variables.constant.ConstantVariable'>] False

from user code:
   File "/home/anijain/local/pytorch/test/dynamo/test_repros.py", line 6137, in fn
    if 1 in cfg:
  File "/home/anijain/.conda/envs/pytorch-3.11/lib/python3.11/site-packages/omegaconf/listconfig.py", line 606, in __contains__
    if x == item:

Set TORCH_LOGS="+dynamo" and TORCHDYNAMO_VERBOSE=1 for more information


You can suppress this exception and fall back to eager by setting:
    import torch._dynamo
    torch._dynamo.config.suppress_errors = True


To execute this test, run the following from the base repo dir:
    python test/dynamo/test_repros.py ReproTests.test_omegaconf_listconfig_contains

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
````



### Versions

NA

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: flutter
Issue: Enforce semantics role checks on required parameters
Labels: a: accessibility,c: proposal,P1,team-accessibility,triaged-accessibility

### Use case

After this pr https://github.com/flutter/flutter/pull/161260
we will be backfilling all the missing role in http://flutter.dev/go/semantics-roles, this will add a bunch of new ways people can get it wrong when assigning the new role to their widget. to help reduce the chaos we should also implement a way to enforce semantics role requirements. See [this doc](https://docs.google.com/document/d/1WOEraK9VIh9dzpJ3mrXgenzfbpRxeISNAdgH8Sh80a4/edit?tab=t.0#heading=h.j9ifh1mhb7b0)

For example, if user assigns a tab role, they needs to have a ontap if it is enabled etc.



### Proposal

implement the checks
Repository: flutter
Issue: Remove `dev_dependency`s from generated plugin registrants on all platforms
Labels: tool,P1,team-android,triaged-android

https://github.com/flutter/flutter/pull/161343 will remove dev dependencies from the generated plugin registrant for Android as part of a fix for enabling dev dependncies being removed from release builds (https://github.com/flutter/flutter/issues/160407).

We should follow up that PR by doing the same for all platforms, just not Android. This is what the change for Android looked like for context:

```dart
Future<void> _writeAndroidPluginRegistrant(FlutterProject project, List<Plugin> plugins, {required bool releaseMode}) async {
  Iterable<Plugin> methodChannelPlugins = _filterMethodChannelPlugins(plugins, AndroidPlugin.kConfigKey);
  if (releaseMode) {
    methodChannelPlugins = methodChannelPlugins.where((Plugin p) => !p.isDevDependency);
  }
```
Repository: go
Issue: build: build failure on go1.23-linux-arm64_c4ah72-perf_vs_release
Labels: NeedsInvestigation

```
#!watchflakes
default <- builder == "go1.23-linux-arm64_c4ah72-perf_vs_release" && repo == "go" && mode == "build"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8726290771046120449)):

    go: downloading github.com/BurntSushi/toml v1.0.0
    go: downloading github.com/kballard/go-shellquote v0.0.0-20180428030007-95032a82bc51
    2025/01/08 17:35:29 Load average: 7.18 2.02 0.69 1/1008 35022
    2025/01/08 17:35:29 Waiting for load average to drop below 0.20...
    2025/01/08 17:35:59 Load average: 4.35 1.83 0.67 1/1006 35022
    2025/01/08 17:35:59 Waiting for load average to drop below 0.20...
    2025/01/08 17:36:29 Load average: 2.63 1.65 0.64 1/1006 35022
    2025/01/08 17:36:29 Waiting for load average to drop below 0.20...
    2025/01/08 17:36:59 Load average: 1.59 1.49 0.62 1/1006 35022
    2025/01/08 17:36:59 Waiting for load average to drop below 0.20...
    ...
    [sweet] Running benchmark tile38 for experiment: run 8
    [sweet] Running benchmark tile38 for baseline: run 8
    [sweet] Running benchmark tile38 for experiment: run 9
    [sweet] Running benchmark tile38 for baseline: run 9
    [sweet] Running benchmark tile38 for experiment: run 10
    [sweet] Running benchmark tile38 for baseline: run 10
    [sweet] error: failed to execute benchmarks: cockroachdb
    2025/01/08 20:39:08 Error running sweet: error running sweet run: exit status 1
    2025/01/08 20:39:08 FAIL
    exit status 1


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: storybook
Issue: [Bug]: ENAMETOOLONG with deeply nested folder structure in storybook/next
Labels: bug,help wanted,nextjs,builder-webpack5

### Describe the bug

If you have a folder structure with long names that is deeply nested, it's possible to overrun the OS's maximum file length as there is no built in truncation

You should then see an issue like

```
=> Failed to build the preview
SB_BUILDER-WEBPACK5_0002 (WebpackInvocationError): ENAMETOOLONG: name too long, open './storybook-static/app-some-folder2-some-sub-folder-some-sub-sub-folder-some-sub-sub-sub-folder-some-sub-sub-sub-sub-folder-some-sub-sub-sub-sub-sub-folder-some-sub-sub-sub-sub-sub-sub-folder-something_is_going_to_get_cha-SomeComponent-AComponent-stories.a38fd5fb.iframe.bundle.js'
```
This error is because the file name being written to the disk is too long and the OS rejects it. It appears as though the config is using a concatenation of the entire chunk file name and path to create the output file name. This error doesn't happen in standard webpack or in next.js, they have a maxlength for the filename and truncate it.

webpack for example
```
dist/src_some-folder_some-sub-folder_some-sub-sub-folder_some-sub-sub-sub-folder_some-sub-sub-sub--921ea3.js
```

next.js for example
```
.next/static/chunks/9e8ad_something_is_going_to_get_cha_SomeComponent_AComponent_tsx_2394de._.js
```

it is possible to work around this issue by manually setting the webpack config output.filename to not include the [name] param.

### Reproduction link

https://github.com/diffidentDude/next-test

### Reproduction steps

I have created a repo to repro the issue https://github.com/diffidentDude/next-test

### System

```bash
% npx storybook@latest info
npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported
npm warn deprecated rimraf@2.6.3: Rimraf versions prior to v4 are no longer supported

Storybook Environment Info:

  System:
    OS: macOS 14.7
    CPU: (10) arm64 Apple M1 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.14.0 - ~/Code/next-test/.devbox/nix/profile/default/bin/node
    npm: 10.7.0 - ~/Code/next-test/.devbox/nix/profile/default/bin/npm <----- active
    pnpm: 9.11.0 - ~/Code/next-test/.devbox/virtenv/nodejs/corepack-bin/pnpm
  Browsers:
    Chrome: 131.0.6778.205
    Safari: 18.0
  npmPackages:
    @storybook/addon-essentials: ^8.4.7 => 8.4.7 
    @storybook/addon-interactions: ^8.4.7 => 8.4.7 
    @storybook/addon-onboarding: ^8.4.7 => 8.4.7 
    @storybook/blocks: ^8.4.7 => 8.4.7 
    @storybook/nextjs: ^8.4.7 => 8.4.7 
    @storybook/react: ^8.4.7 => 8.4.7 
    @storybook/test: ^8.4.7 => 8.4.7 
    eslint-plugin-storybook: ^0.11.2 => 0.11.2 
    storybook: ^8.4.7 => 8.4.7
```

### Additional context

_No response_