sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: `impl ... for Box<CoreType>` in alloc should not require `#[cfg(not(test))]`
Labels: T-compiler,T-bootstrap,A-docs,C-bug,E-needs-investigation

`library/alloc/src/ffi/c_str.rs` has:

```rust
#[cfg(not(test))]
#[stable(feature = "box_from_c_str", since = "1.17.0")]
impl From<&CStr> for Box<CStr> {
```

As far as I can tell, `#[cfg(not(test))]` is a workaround for something like https://github.com/rust-lang/rust/issues/87534, as evidenced by error messages like:
```note: the crate `alloc` is compiled multiple times, possibly with different configurations```

`alloc` is being compiled a second time as part of tests, and the two compilations are conflicting.

1) This workaround shouldn't be necessary.

2) This should be much better documented, so it doesn't send people on multi-hour debugging adventures when they try to write *new* trait impls in `alloc`.
Repository: neovim
Issue: `vim.o.term` is missing
Labels: bug,compatibility,complexity:low,options

### Problem

`vim.o.term` used to be available in 0.9.x but now it's gone in 0.10.x. The Vimscript equivalent option is still present (`:echo &term`).

More info in this discussion: https://github.com/neovim/neovim/discussions/28982

### Steps to reproduce

- nvim --clean
- :lua print(vim.o.term)
- :lua print(vim.opt.term)

### Expected behavior

Both commands should print the detected terminal.

### Nvim version (nvim -v)

0.10.3

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

Arch Linux

### Terminal name/version

Alacritty 0.14.0 / Neovide 0.14.0

### $TERM environment variable

xterm-256color

### Installation

Arch Linux (extra)
Repository: go
Issue: proposal: go/parser: deprecate parser.ParseDir (which returns deprecated type ast.Package)
Labels: Proposal

### Go version

1.23.4

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/home/soeren/.cache/go-build'
GOENV='/home/soeren/.config/go/env'
GOEXE=''
GOEXPERIMENT='nocoverageredesign'
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/soeren/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/soeren/go'
GOPRIVATE=''
GOPROXY='direct'
GOROOT='/opt/go'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/opt/go/pkg/tool/linux_amd64'
GOVCS=''
GOVERSION='go1.23.4'
GODEBUG=''
GOTELEMETRY='local'
GOTELEMETRYDIR='/home/soeren/.config/go/telemetry'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/home/soeren/usrdev/go-util-mutation/go.mod'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build2925151345=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

Write some simple code using the go/ast and go/parser:
```
func createAST() {
	ast := map[string]*ast.Package{}
	fset := token.NewFileSet()
	chain := &util.ChainContext{}

	chain.Chain(func() {
		ast, chain.Err = parser.ParseDir(fset, ".", nil, 0)
	}).Chain(func() {
		chain.Err = format.Node(os.Stdout, fset, ast)
	}).ChainFatal("Error")
}
```


### What did you see happen?

The IDE marks `ast.Package` as deprecated conforming to the comment on the type. But `parser.ParseDir()` nevertheless references `ast.Package` in its return type.

### What did you expect to see?

Either:
* Having deprecated types consistently replaced in the stdlib. Thus, let `ParseDir()` use the recommended replacement type.

Or:
* Having `ParseDir()` marked as deprecated too.
Repository: godot
Issue: godot crashes after I close the debug window with the game
Labels: bug,topic:rendering,crash

### Tested versions

- version: 4.3-stable, 15 August 2024


### System information

windows 11 pro, Vulkan (Forward+), HexaCore AMD Ryzen 5 5600, 4442 MHz (44.5 x 100), ASRock B450M Pro4 R2.0, GTX 1650 4GB

### Issue description

I bought a new computer board and processor - b450m pro 4 2.0, r5 5600, and once I started working in godot. After I close the debug window with the game, rarely, but an error occurs, my monitor turns off completely, and after 2-3 seconds it turns on and Godot turns into a gray window without buttons, etc.

The error is endlessly reported to the console:
```
ERROR: Condition “err != VK_SUCCESS” is true. Returning: FAILED
at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2266)
ERROR: Condition “err != VK_SUCCESS” is true. Returning: FAILED
at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2266)
ERROR: Condition “err != VK_SUCCESS” is true. Returning: FAILED
at: fence_wait (drivers/vulkan/rendering_device_driver_vulkan.cpp:2066)
ERROR: Condition “err != VK_SUCCESS” is true. Returning: ERR_CANT_CREATE
at: swap_chain_resize (drivers/vulkan/rendering_device_driver_vulkan.cpp:2718)
ERROR: Condition “err != VK_SUCCESS” is true. Returning: FAILED
at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2266)
ERROR: Condition “err != VK_SUCCESS” is true. Returning: FAILED
at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2266)
ERROR: Condition “err != VK_SUCCESS” is true. Returning: FAILED
at: fence_wait (drivers/vulkan/rendering_device_driver_vulkan.cpp:2066)
ERROR: Condition “err != VK_SUCCESS” is true. Returning: FAILED
at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2266)
ERROR: Condition “err != VK_SUCCESS” is true. Returning: FAILED
at: command_queue_execute_and_present (drivers/vulkan/rendering_device_driver_vulkan.cpp:2266)
```
### Steps to reproduce

the error appears only after I close the debug window

### Minimal reproduction project (MRP)

the error appears in 2 of my projects
Repository: go
Issue: runtime: SEGV in mapaccess2 (go1.23.2 darwin/amd64)
Labels: NeedsInvestigation,gopls,Tools,compiler/runtime,gopls/telemetry-wins,BugReport

```
#!stacks
"runtime.sigpanic" && "runtime.mapaccess2:+22"
```
Issue created by [stacks](https://pkg.go.dev/golang.org/x/tools/gopls/internal/telemetry/cmd/stacks).

The line numbers are again suspicious, possibly an instance of #70885.

This stack `zjaBOQ` was [reported by telemetry](https://storage.googleapis.com/prod-telemetry-merged/2025-01-03.json):

- `crash/crash`
- [`runtime.throw:+9`](https://cs.opensource.google/go/go/+/go1.23.2:src/runtime/panic.go;l=1067)
- [`runtime.sigpanic:+33`](https://cs.opensource.google/go/go/+/go1.23.2:src/runtime/signal_unix.go;l=914)
- [`runtime.interhash:+6`](https://cs.opensource.google/go/go/+/go1.23.2:src/runtime/alg.go;l=160)
- [`runtime.mapaccess2:+22`](https://cs.opensource.google/go/go/+/go1.23.2:src/runtime/map.go;l=501)
- [`golang.org/x/tools/internal/gcimporter.(*iexporter).typOff:+1`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=973)
- [`golang.org/x/tools/internal/gcimporter.(*exportWriter).typ:+1`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=959)
- [`golang.org/x/tools/internal/gcimporter.(*exportWriter).doTyp:+44`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=1031)
- [`golang.org/x/tools/internal/gcimporter.(*iexporter).typOff:+4`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=976)
- [`golang.org/x/tools/internal/gcimporter.(*exportWriter).typ:+1`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=959)
- [`golang.org/x/tools/internal/gcimporter.(*exportWriter).param:+3`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=1278)
- [`golang.org/x/tools/internal/gcimporter.(*exportWriter).paramList:+4`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=1271)
- [`golang.org/x/tools/internal/gcimporter.(*exportWriter).signature:+1`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=1210)
- [`golang.org/x/tools/internal/gcimporter.(*iexporter).doDecl:+141`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=832)
- [`golang.org/x/tools/internal/gcimporter.iexportCommon:+55`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=390)
- [`golang.org/x/tools/internal/gcimporter.IExportShallow:+8`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:internal/gcimporter/iexport.go;l=286)
- [`golang.org/x/tools/gopls/internal/cache.storePackageResults:+9`](https://cs.opensource.google/go/x/tools/+/gopls/v0.17.1:gopls/internal/cache/check.go;l=443)
```
golang.org/x/tools/gopls@v0.17.1 go1.23.2 darwin/amd64 other (1)
```

@prattmic
Repository: angular
Issue: Routing documentation does not appear to describe how to change route programatically
Labels: needs: clarification,area: docs

### Describe the problem that you experienced

Unless I'm missing something there does not appear to be anything in the documentation on how to control the loaded route programatically.

[Common routing tasks](https://angular.dev/guide/routing/common-router-tasks) - nothing here.
[Routing in signle-page applications](https://angular.dev/guide/routing/router-tutorial) - nothing here.
[Creating custom route matches](https://angular.dev/guide/routing/routing-with-urlmatcher) - nothing here.
[Router reference](https://angular.dev/guide/routing/router-reference#configuration) - nothing here.



### Enter the URL of the topic with the problem

_No response_

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true

```

### Provide any additional information here in as much as detail as you can

```true

```
Repository: godot
Issue: Atlas Merge Tool crashes when selecting entries to merge 2
Labels: bug,topic:editor,confirmed,crash,topic:2d

### Tested versions

Godot v4.3.stable (77dcf97d8) - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce GTX 980 Ti (NVIDIA; 32.0.15.6094) - Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 Threads)

### System information

Godot v4.3.stable (77dcf97d8) - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce GTX 980 Ti (NVIDIA; 32.0.15.6094) - Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz (8 Threads)

### Issue description

Godot crashes when I select multiple atlases to merge using the Atlas Merge Tool.  

I found [this closed issue from 2023](https://github.com/godotengine/godot/issues/75354) that seemed like the same problem.  I downloaded the MRP and everything worked fine so this doesn't seem to be the same issue.

I suspect it only crashes when you try to merge atlases that have already had their properties changed and/or used in a TileMapLayer.



### Steps to reproduce

1. Load several atlases into a Tile Set resource

2a. Define collision shapes for several tiles
and/or
2b. Setup animations for several tiles
and/or
2c. Setup terrain sets for several tiles
and/or
2d. Use tiles in a TileMapLayer node

4. Open Atlas Merge Tool

5. Hold shift and select multiple atlases



### Minimal reproduction project (MRP)

The assets used for the MRP are CC0.  They are from here: https://kevins-moms-house.itch.io/

[atlas merge bug.zip](https://github.com/user-attachments/files/18307593/atlas.merge.bug.zip)
Repository: PowerToys
Issue: Add an option to re-arrange image sizes in Image Resizer
Labels: Needs-Triage

### Description of the new feature / enhancement

I'd like an option to re-arrange image sizes in Image Resizer, please. This makes it easier to re-arrange image sizes in any order for example:

From
Small - 854x480
Medium - 1024x768
Large - 1280x1024

To
Large - 1280x1024
Small - 854x480
Medium - 1024x768

### Scenario when this would be used?

Either drag-and-drop the image preset sizes or click the up and down arrows to re-arrange them.

### Supporting information

It'd be useful to re-arrange the image preset sizes instead of deleting and manually re-creating them.
Repository: PowerToys
Issue: CalculatorApp.exe on Excluded apss for Fancy Zones, maximizes to zone when first opened.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

CalculatorApp.exe on Excluded apss for Fancy Zones, maximize to zone when it is first opened. It should be opened with its last width and height.


### ✔️ Expected Behavior

It should be opened with its last width and height.


### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: neovim
Issue: Allow `String`s to not be nul-terminated
Labels: enhancement,performance,core

### Problem

Even though the [`String`](https://github.com/neovim/neovim/blob/master/src/nvim/api/private/defs.h#L80-L83) struct contains a `size` field, the string data is still required to be nul-terminated.

I imagine this is to use it in functions operating on C strings, but it also creates some issues:

- performance overhead: need to scan for the nul terminator to find a string's end, even though we already know its length;
- double source of truth: having both the `size` field and nul terminator means there are two ways to determine a string's length, which need to be kept in sync;
- memory waste: each string requires an extra byte;

Personally, I'd like to avoid having to allocate every time a string is passed from Rust to C in `nvim-oxi`, which isn't currently possible due to `&str`s not being nul-terminated.

### Expected behavior

I'm curious how feasible it would be to modify the internal string-handling functions to work with length-delimited strings. This could be done by either:

- having them take a `String` instead of a `char *const` and use its `size` field;
- adding a length parameter;

External functions like `xstrdup` would need to be re-implemented.

Thoughts? I'm happy to work on this if there's interest.
Repository: rust
Issue: The implementation of `InPlaceIterable` for `Flatten`&`FlatMap` is unsound
Labels: I-unsound,C-bug,A-iterators,T-libs

```rust
const S: String = String::new();
fn main() {
    let v = vec![[S, "Hello World!".into()], [S, S]];
    let mut i = v.into_iter().flatten();
    let _ = i.next();
    let result: Vec<String> = i.clone().collect();
    println!("{result:?}");
}
```
([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=4dd1a5df2c3d8a19afc99b33f71264c3))
```rust
["\0\0\0\0\0\0\0\0rld!", "\0\0\0\0\0\0\0\0rld!", ""]
free(): invalid pointer
[1]    1131073 IOT instruction (core dumped)
```

The above code is analogous to #85322 but applied to `Flatten` instead of `Peekable`: cloning the whole iterator doesn't preserve capacity in the inner `vec::IntoIter`. (This also applies to `FlatMap`.)

Introduced in 1.76

cc @the8472, #110353

@rustbot label T-libs, I-unsound, A-iterators
Repository: flutter
Issue: Internationalization for certain prebuilt Widgets 
Labels: framework,f: material design,a: internationalization,P2,team-design,triaged-design

### Use case

I have been making a few apps and utilizing the [`showLicensePage`](https://github.com/flutter/flutter/blob/main/packages/flutter/lib/src/material/about.dart#L396) function to show all the builtin app functions and noticed that some of the strings such as "Powered by Flutter" were just hard-coded into the framework, which forced me to write my own `showLicensePage` alternative that was able to respect the locale.

### Proposal

For hard-coded strings like the `"Powered by Flutter"` string in `showLicensePage(...)` [here](https://github.com/flutter/flutter/blob/main/packages/flutter/lib/src/material/about.dart#L727) in prebuilt widgets, it would be helpful to allow for better usability by incorporating i18n. 

It would likely respect the `locale` property within the parent `MaterialApp` or another parent widget that is able to provide a `Locale` object.

I am not too sure, but looking into the tooling for Flutter, the [localization bit](https://github.com/flutter/flutter/tree/master/packages/flutter_localizations) could come handy
Repository: neovim
Issue: vim.fs assumes case-sensitive filesystem
Labels: bug,needs:decision,complexity:high,filesystem

# Problem

Windows, macOS, and even Linux support filesystems that may be case-insensitive.

Examples

- Windows supports directory-specific decision about case sensitivity
    - and case handling depends on the *current locale*
- macOS partitions may be case-sensitive or not
- on Linux, [mounts to usb, smb, etc.](https://github.com/neovim/neovim/pull/31833#issuecomment-2571308366) may have a case-insensitive filesystem

References:

- `vim.fn.has('fname_case')`
- https://github.com/neovim/neovim/pull/31833
- https://github.com/dart-lang/core/issues/529
- https://stackoverflow.com/questions/33998669/windows-ntfs-and-case-sensitivity/34000339#34000339
- https://hasufell.github.io/posts/2022-06-29-fixing-haskell-filepaths.html
- https://learn.microsoft.com/en-us/windows/wsl/case-sensitivity
- https://www.tiraniddo.dev/2019/02/ntfs-case-sensitivity-on-windows.html

# Proposal

Until we have a "full" solution for detecting filesystem case-sensitivity, `vim.fs.normalize()` will behave as case-sensitive.

- [x] Some parts of a filepath (such as Windows drive-letters) are guaranteed to never be case-sensitive. `vim.fs.normalize()` can safely force those parts to a upper/lower-case without considering the system context. #31833
- [ ] Implement filesystem-aware case-sensitivity detection in `vim.fs.normalize()`.
    - This can be done incrementally for each filesystem.
Repository: pytorch
Issue: [typing] Add static type hints to `torch.distributions`.
Labels: module: distributions,module: typing,triaged

### 🚀 The feature, motivation and pitch

Current lack of type hints causes some issues, for instance #76772

- [x] Add type hints for `lazy_property` class (#144110)
- [x] Add type hints for `@property` and `@lazy_property` (#144110)
- [ ] Add type hints to `__init__` methods (#144197)
- [ ] Add type hints to methods (#144219)
- [ ] Add type hints to attributes (#144219)
- [ ] Add type hints to utility functions (#144219)

### Alternatives

_No response_

### Additional context

_No response_

cc @fritzo @neerajprad @alicanb @nikitaved @ezyang @malfet @xuzhao9 @gramster
Repository: PowerToys
Issue: [PTRun][Calc] Improve handling of non base 10 numbers
Labels: Idea-Enhancement,Resolution-Fix Committed,Run-Plugin

### Description of the new feature / enhancement

* Make division by zero check aware of binary and octal numbers
* Allow octal numbers in `CalculateHelper.InputValid()`
* Allow uppercase base notation (as in `0X`) in `CalculateHelper.InputValid()`
* Make division by zero in another base trigger the division by zero check
Repository: ant-design
Issue: Ant Design Select component jerks when controlHeight is set in theme configuration
Labels: unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/tags-antd-5-22-7-forked-39r3jw?file=%2Fpackage.json%3A10%2C14-10%2C20)

### Steps to reproduce

Create a React app with Ant Design installed.
Add a Select component from Ant Design with the mode="tags" option.
In the ConfigProvider, set controlHeight to a value (e.g., 40px) in the theme configuration.
Run the app and try to interact with the Select component by typing in the input.

### What is expected?

The Select component should render smoothly without any jerking or unexpected behavior when controlHeight is set.

### What is actually happening?

When controlHeight is set in the theme configuration, the Select component (select options)  starts jerking during text input. This issue does not occur when controlHeight is unset.

| Environment | Info |
| --- | --- |
| antd | 5.22.7 |
| React | react 18.x.x |
| System | ubuntu 22 |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: storybook
Issue: [Bug]: --exact-port Not Working
Labels: bug,help wanted,cli

### Describe the bug

`storybook dev --exact-port 6006` failed to run, while `storybook dev --port 6006` works.

### Reproduction link

https://github.com/ianzone/react-storybook

### Reproduction steps

1. clone https://github.com/ianzone/react-storybook
2. pnpm install
3. run `storybook dev --exact-port 6006`

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.15 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)
    CPU: (20) x64 13th Gen Intel(R) Core(TM) i7-13800H
    Shell: 5.9 - /home/linuxbrew/.linuxbrew/bin/zsh
  Binaries:
    Node: 22.12.0 - /home/linuxbrew/.linuxbrew/opt/node@22/bin/node
    npm: 10.9.0 - /home/linuxbrew/.linuxbrew/opt/node@22/bin/npm
    pnpm: 9.15.2 - /home/linuxbrew/.linuxbrew/bin/pnpm <----- active
  npmPackages:
    @storybook/addon-a11y: ^8.4.7 => 8.4.7
    @storybook/addon-coverage: ^1.0.5 => 1.0.5
    @storybook/addon-essentials: ^8.4.7 => 8.4.7
    @storybook/addon-interactions: ^8.4.7 => 8.4.7
    @storybook/addon-links: ^8.4.7 => 8.4.7
    @storybook/blocks: ^8.4.7 => 8.4.7
    @storybook/react: ^8.4.7 => 8.4.7
    @storybook/react-vite: ^8.4.7 => 8.4.7
    @storybook/test: ^8.4.7 => 8.4.7
    @storybook/test-runner: ^0.21.0 => 0.21.0
    chromatic: ^11.22.0 => 11.22.0
    storybook: ^8.4.7 => 8.4.7
```

### Additional context

_No response_
Repository: tauri
Issue: [bug] Cannot resize window with custom titlebar when "unstable" feature is enabled on Windows
Labels: type: bug,status: needs triage,scope: unstable flag

### Describe the bug

This issue probably reopened this one (https://github.com/tauri-apps/tauri/issues/8519), also look at the recent comments for additional context.

### Reproduction

1.  `pnpm create tauri-app`
2. Duplicate code from [here](https://v2.tauri.app/learn/window-customization/#creating-a-custom-titlebar)  and update permissions
3. Change `tauri.conf.json`
```
"windows": [
      {
        "title": "resize-bug",
        "width": 800,
        "height": 600,
        "decorations": false,
        "transparent": true,
        "shadow": false
      }
    ],
```
4. Now if you run `pnpm tauri dev` resize will work.
5. Update `Cargo.toml`
```
tauri = { version = "2", features = ["unstable"] }
```
6. Now resize doesn't work.

### Expected behavior

The application is able to be resize when "unstable" feature is enabled and "decorations": false.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.19045 x86_64 (X64)
    ✔ WebView2: 128.0.2739.67
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.79.0 (129f3b996 2024-06-10)
    ✔ cargo: 1.79.0 (ffa9cf99a 2024-06-03)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.15.0
    - pnpm: 9.5.0
    - npm: 10.7.0

[-] Packages
    - tauri 🦀: 2.2.0
    - tauri-build 🦀: 2.0.4
    - wry 🦀: 0.48.0
    - tao 🦀: 0.31.1
    - @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

_No response_

### Additional context

_No response_