sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Segmentation fault when running torch.nn.functional.fractional_max_pool3d on torch 1.13.1
Labels: needs reproduction,module: crash,triaged

### 🐛 Describe the bug

With the following input combinations, it results in segfault:
```
import torch
import numpy as np
arg_1_tensor = torch.rand([2, 4, 5, 5, 5], dtype=torch.float64)
arg_1 = arg_1_tensor.clone()
arg_2_0 = 2
arg_2_1 = 2
arg_2_2 = 2
arg_2 = [arg_2_0,arg_2_1,arg_2_2,]
arg_3 = None
arg_4_0 = 0.5
arg_4_1 = 0.5
arg_4_2 = 0.5
arg_4 = [arg_4_0,arg_4_1,arg_4_2,]
arg_5 = False
arg_6_tensor = torch.tensor([], dtype=torch.float64)
arg_6 = arg_6_tensor.clone()
try:
  res = torch.nn.functional.fractional_max_pool3d(arg_1,arg_2,arg_3,arg_4,arg_5,_random_samples=arg_6,)
except Exception as e:
  print("Error:"+str(e))
```

### Versions

PyTorch version: 1.13.1
Is debug build: False
CUDA used to build PyTorch: 11.6
ROCM used to build PyTorch: N/A

OS: Ubuntu 22.04.1 LTS (x86_64)
GCC version: (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0
Clang version: Could not collect
CMake version: Could not collect
Libc version: glibc-2.35

Python version: 3.9.15 (main, Nov 24 2022, 14:31:59) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.15.0-56-generic-x86_64-with-glibc2.35
Is CUDA available: False
CUDA runtime version: 11.6.124
CUDA_MODULE_LOADING set to: N/A
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.5
[pip3] torch==1.13.1
[pip3] torchaudio==0.13.1
[pip3] torchvision==0.14.1
[conda] blas 1.0 mkl
[conda] ffmpeg 4.3 hf484d3e_0 pytorch
[conda] mkl 2021.4.0 h06a4308_640
[conda] mkl-service 2.4.0 py39h7f8727e_0
[conda] mkl_fft 1.3.1 py39hd3c417c_0
[conda] mkl_random 1.2.2 py39h51133e4_0
[conda] numpy 1.23.5 py39h14f4228_0
[conda] numpy-base 1.23.5 py39h31eccc5_0
[conda] pytorch 1.13.1 py3.9_cuda11.6_cudnn8.3.2_0 pytorch
[conda] pytorch-cuda 11.6 h867d48c_1 pytorch
[conda] pytorch-mutex 1.0 cuda pytorch
[conda] torchaudio 0.13.1 py39_cu116 pytorch
[conda] torchvision 0.14.1 py39_cu116 pytorch
Repository: tauri
Issue: [bug] Custom actions aren't bundled from Wix fragments
Labels: type: feature request,scope: bundler

### Describe the bug

I have a `<CustomAction />` and `<InstallExecuteSequence />` in my wxs fragment but it doesn't run and isn't included in the msi file which I have confirmed with Orca. The wxs fragment is definitely being read because `light` is catching errors in it.

Perhaps I'm misunderstanding how Fragments are supposed to work but I thought I could just include this CustomAction and it would be similar to including at the end of main.wxs. For now I have just copy and pasted main.wxs from tauri-bundler into my project with the CustomAction appended and set that as the template in tauri.conf.json and it works fine.

### Reproduction

Make a .wxs fragment with a CustomAction and add it to fragmentPaths in tauri.conf.json.

An example I've been testing is an action that just launches notepad.
```xml
<?xml version="1.0" encoding="utf-8"?>
<Wix xmlns="http://schemas.microsoft.com/wix/2006/wi">
  <Fragment>
      <CustomAction Id="OpenNotepad" Directory="INSTALLDIR" Execute="immediate" ExeCommand="cmd.exe /c notepad.exe" Return="check" />
      <InstallExecuteSequence>
          <Custom Action="OpenNotepad" After="InstallInitialize" />
      </InstallExecuteSequence>
  </Fragment>
</Wix>
```

### Expected behavior

The CustomAction runs with the specified installation sequence.

### Platform and versions

Environment
  › OS: Windows 10.0.22000 X64
  › Webview2: 108.0.1462.54
  › MSVC: 
  › Node.js: 16.14.2
  › npm: 8.5.5
  › pnpm: 7.2.1
  › yarn: 1.22.19
  › rustup: 1.25.1
  › rustc: 1.65.0
  › cargo: 1.65.0
  › Rust toolchain: stable-x86_64-pc-windows-msvc 

Packages
WARNING: no lock files found, defaulting to npm
  › @tauri-apps/cli [NPM]: 1.2.1 (outdated, latest: 1.2.2)
  › @tauri-apps/api [NPM]: Not installed!
  › tauri [RUST]: 1.2.1,
  › tauri-build [RUST]: 1.2.1,
  › tao [RUST]: 0.15.6,
  › wry [RUST]: 0.22.5,

App
  › build-type: bundle
  › CSP: unset
  › distDir: []
  › devPath: []

App directory structure
  ├─ .changes
  ├─ .devcontainer
  ├─ .docker
  ├─ .git
  ├─ .github
  ├─ .husky
  ├─ .scripts
  ├─ .vscode
  ├─ audits
  ├─ core
  ├─ examples
  ├─ target
  └─ tooling

### Stack trace

_No response_

### Additional context

_No response_
Repository: flutter
Issue: `toolbarHeight` of `AppBar` not affected by Material 3
Labels: framework,f: material design,c: API break,a: fidelity,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-design,triaged-design,Design Systems Study

According to Material Design 3 specs, height of app bar is 64dp.
Here is an example of app bar in material 3: 
```
import 'package:flutter/material.dart';

void main() => runApp(const App());

class App extends StatelessWidget {
  const App({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData(
        colorSchemeSeed: const Color(0xff6750a4),
        useMaterial3: true,
      ),
      home: Scaffold(
        appBar: AppBar(title: const Text('App Bar')),
        body: Container(color: Colors.black),
      ),
    );
  }
}
```
and we can find out that height of app bar is 56 (Material 2 spec) but not 64.

After I tracked source code, I found `_AppBarDefaultsM3` is already defined `toolbarHeight` is `64.0`
https://github.com/flutter/flutter/blob/0c7d84aa789e649cb05b0f5f890c04e482f43737/packages/flutter/lib/src/material/app_bar.dart#L2381-L2387
But it is not used when building `AppBar`
https://github.com/flutter/flutter/blob/0c7d84aa789e649cb05b0f5f890c04e482f43737/packages/flutter/lib/src/material/app_bar.dart#L908-L927

Maybe change
```dart
    final double toolbarHeight = widget.toolbarHeight ?? appBarTheme.toolbarHeight ?? kToolbarHeight;
```
to
```dart
    final double toolbarHeight = widget.toolbarHeight ?? appBarTheme.toolbarHeight ?? defaults.toolbarHeight ?? kToolbarHeight;
```
will fix this issue.
Repository: go
Issue: x/tools/gopls: rename: modify [pkg.Symbol] doc links in non-doc comments too
Labels: FeatureRequest,gopls,Tools,Refactoring

[Doc Links](https://tip.golang.org/doc/comment) has been added to the go in 1.19 and it is accessible in the [AST](https://pkg.go.dev/go/doc/comment@go1.19.4#DocLink). Enabling refactoring of DocLinks will improve the maintainability of documentation.

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.19.1 windows/amd64
$  gopls version
golang.org/x/tools/gopls v0.11.0
$ vscode-go v0.37
</pre>

### What did you do?

```go
type Foo struct {
}
// struct [Foo] is a nice struct ...
```

Refactor "Foo" to "Bar"

### What did you expect to see?

```go
type Bar struct {
}
// struct [Bar] is a nice struct ...
```

### What did you see instead?

```go
type Bar struct {
}
// struct [Foo] is a nice struct ...
```
Repository: storybook
Issue: [Bug]: Subcomponents doesn't show code preview in docs (v7)
Labels: bug,needs more info,needs reproduction,needs triage

### Describe the bug

Hello,

We created a component based on MUI modal, with subcomponents (Title, Content & ContentActions):
![image](https://user-images.githubusercontent.com/408965/210403673-a33dfc8d-4de0-4b3d-b971-c99f5725f14f.png)


And created stories to show it like this one: 
![image](https://user-images.githubusercontent.com/408965/210403765-185c9ca0-5e01-4c18-89b5-e90bbda972e3.png)


But, when I ran the storybook and went to docs and show code, I received this as return:
![image](https://user-images.githubusercontent.com/408965/210403932-084e0c4a-9c55-4fdd-8982-dc052b16a0f1.png)


### To Reproduce

_No response_

### System

_No response_

### Additional context

<details>
  <summary><code>npx @mui/envinfo</code></summary>

System:
    OS: macOS 12.6.2
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: Not Found
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: Not Found
    Edge: Not Found
    Firefox: Not Found
    Safari: 16.2
  npmPackages:
    @emotion/react: ^11.10.5 => 11.10.5 
    @emotion/styled: ^11.10.5 => 11.10.5 
    @mui/base:  5.0.0-alpha.112 
    @mui/core-downloads-tracker:  5.11.2 
    @mui/material: ^5.11.2 => 5.11.2 
    @mui/private-theming:  5.11.2 
    @mui/styled-engine:  5.11.0 
    @mui/system:  5.11.2 
    @mui/types:  7.2.3 
    @mui/utils:  5.11.2 
    @types/react: ^18.x => 18.0.26 
    react: ^18.x => 18.2.0 
    react-dom: ^18.x => 18.2.0 
    typescript: ^4.9.4 => 4.9.4 
</details>
Repository: godot
Issue: Failed to export C# project to IOS
Labels: enhancement,platform:ios,usability,topic:dotnet,topic:export

### Godot version

3.5.1mono

### System information

windows10

### Issue description

![image](https://user-images.githubusercontent.com/119792950/210405439-82432c5d-87c6-45ec-93c8-59d44e00831f.png)


### Steps to reproduce

Create a project
Create a scene
Create a C# script and mount it to any node of any scene
Create an IOS export setting
Export it
Get this
![image](https://user-images.githubusercontent.com/119792950/210405815-6026541d-9115-44a4-9e2e-7e2e4acc1b6a.png)



### Minimal reproduction project

[test.zip](https://github.com/godotengine/godot/files/10338441/test.zip)
Repository: TypeScript
Issue: React props in typescript are displayed in alphabetical order instead of showing component props at the top when running "trigger suggest"
Labels: Suggestion,Domain: Completion Lists,Awaiting More Feedback

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version:  1.74.2
- OS Version:  macOS 12.6

Steps to Reproduce:

1. git clone reproduction repo at https://github.com/MichaelHindley/vscode-react-props-alphabetical
2. start vscode with --disable-extensions flag
3. run `npm i` to install dependencies
4.  go to Line 25 in App.tsx, place curser inside the Menu component opening tag
5.  run the "Trigger suggest" command
6. Observe the props being sorted in *alphabetical order* instead of showing the *components own props* at the top
![image](https://user-images.githubusercontent.com/1016639/210223762-46fb44ec-4958-464a-874e-28949195c98b.png)
 
What should happen instead is that the component scoped variables from "MenuProps" should be at the top, rather than being alphabetically sorted. The alphabetical sorting is a very poor developer experience. When triggering suggestions in a react component, the most common scenario by far is to see which props the component type has, which vscode is aware of.

<img width="702" alt="image" src="https://user-images.githubusercontent.com/1016639/210223891-6827d918-9a4b-4ec8-9d5f-daddf55ee1bc.png">

Notice the equivalent of "trigger suggest" in Intellij, showing the components props above all the default html props;
<img width="1692" alt="image" src="https://user-images.githubusercontent.com/1016639/210224277-fb95e733-3ef5-4acd-aceb-0cedb4fd44fe.png">
Repository: flutter
Issue: [google_maps_flutter] Convert to Pigeon
Labels: team,p: maps,package,team-ecosystem,P2,triaged-ecosystem

Part of https://github.com/flutter/flutter/issues/117844

~This is a case where we may want to build more instance-tracking functionality into Pigeon itself before doing a conversion, since we currently use per-instance channels.~ This is now implemented.

## Progress

- [x] `google_maps_flutter_android`
  - [x] Convert inspector calls
  - [x] Convert Dart->Host calls at the method level
  - [ ] Convert data objects passed in method calls (can be done incrementally)
    - [x] `PlatformCameraUpdate`
    - [x] `PlatformCircle`
    - [ ] `PlatformHeatmap`
    - [x] `PlatformMarker`
    - [x] `PlatformPolygon`
    - [x] `PlatformPolyline`
    - [x] `PlatformTileOverlay`
  - [x] Convert Host->Dart calls - https://github.com/flutter/packages/pull/7040
  - [x] Convert platform view creation params ~(blocked on https://github.com/flutter/flutter/issues/150631)~ - https://github.com/flutter/packages/pull/7207
- [ ] `google_maps_flutter_ios`
  - [x] Convert inspector calls - https://github.com/flutter/packages/pull/6937
  - [x] Convert Dart->Host calls at the method level - https://github.com/flutter/packages/pull/7079
  - [ ] Convert data objects passed in method calls (can be done incrementally, and the Dart portion of the Android conversions of these classes can be re-used modulo any platform-SDK-specific differences)
    - [x] `PlatformCameraUpdate`
    - [x] `PlatformCircle`
    - [ ] `PlatformHeatmap`
    - [x] `PlatformMarker`
    - [x] `PlatformPolygon`
    - [x] `PlatformPolyline`
    - [x] `PlatformTileOverlay`
  - [x] Convert Host->Dart calls - https://github.com/flutter/packages/pull/7086
  - [x] Convert platform view creation params ~(blocked on https://github.com/flutter/flutter/issues/150631)~ - https://github.com/flutter/packages/pull/7207
Repository: flutter
Issue: [in_app_purchase] Convert to Pigeon
Labels: team,p: in_app_purchase,package,team-ecosystem,P2,triaged-ecosystem

Part of https://github.com/flutter/flutter/issues/117844

- [x] `in_app_purchase_android`
- [ ] `in_app_purchase_storekit`
Repository: TypeScript
Issue: Treat `T[keyof T]` as covariant (rather than invariant) during variance measurement
Labels: Suggestion,Awaiting More Feedback

# Suggestion

See title.  Will fill in more details later.

## 🔍 Search Terms

<!--
  💡 Did you know? TypeScript has over 2,000 open suggestions!
  🔎 Please search thoroughly before logging new feature requests as most common ideas already have a proposal in progress.
  The "Common Feature Requests" section of the FAQ lists many popular requests: https://github.com/Microsoft/TypeScript/wiki/FAQ#common-feature-requests

  Replace the text below:
-->

List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
My suggestion meets these guidelines:

* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [ ] This wouldn't change the runtime behavior of existing JavaScript code
* [ ] This could be implemented without emitting different JS based on the types of the expressions
* [ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

<!-- A summary of what you'd like to see added or changed -->

## 📃 Motivating Example

<!--
  If you were announcing this feature in a blog post, what's a short explanation that shows
  a developer why this feature improves the language?
-->

## 💻 Use Cases

<!--
  What do you want to use this for?
  What shortcomings exist with current approaches?
  What workarounds are you using in the meantime?
-->
Repository: neovim
Issue: remote ssh plugin (like vscode remote-ssh)
Labels: enhancement,plugin,gsoc,remote

This is mostly just for tracking. Obviously everyone wants this, but it looks like work... 😏 

# Problem

vscode has "remote" tools (broadly referred to as `vscode-remote`, in particular `vscode remote-ssh`)

- https://code.visualstudio.com/docs/remote/remote-overview
- https://code.visualstudio.com/docs/remote/ssh

... that allow the user to

1. input a ssh URI (hostname + port)
     - or select from a list of hosts discovered from your local `~/.ssh/config`
2. vscode connects to the remote ssh endpoint using your local `~/.ssh` credentials
    - or prompts for password as needed
3. vscode starts a new local UI
4. vscode installs _another vscode_ on the remote machine automatically
    - it also installs your plugins, on the remote!
5. the new local vscode UI controls the remote vscode server, and you can use it to work on the remote machine very much like a local vscode.

# Ideaaaaaa

1. Implement a "universal installer" script (sh, powershell) that pulls from 
https://github.com/neovim/neovim/releases and installs the correct Nvim on the current machine
   ```
    curl https://neovim.io/install-hax && bash install-hax
   ```
    - does something like this already exist? 
        - https://github.com/rhysd/action-setup-vim
        - https://github.com/NTBBloodbath/nvenv
        - https://github.com/MordechaiHadad/bob
2. Implement an Nvim plugin that works like vscode remote-ssh (described above)
    - select ssh host from `~/.ssh/config`
    - installs Nvim on the remote (if suitable `nvim` version is not found on the remote)
    - starts remote Nvim server
    - configures ssh tunnel
    - starts local Nvim UI connected to the remote Nvim
Repository: godot
Issue: Viewport bug with the gridmap copying tiles and selecting another node in a scene
Labels: bug,topic:editor,topic:3d

### Godot version

4.0 Beta 10

### System information

Windows 10

### Issue description

I found another bug with the gridmap just right now,
I was trying to copy content from one gridmap to another in the scene, and then was wondering why I saw something even with no gridmap set to visible. I then tried it a few more times, it always happens. In some cases it appeared only in the scene where I tried to copy, and disappeared after closing and reopening the scene. In other cases I had this in every scene even if it has no gridmap and disappearing after restarting the editor
https://user-images.githubusercontent.com/82282845/210422074-47db5bfc-1ce4-47cc-9227-dfe71610111f.mp4

(also note that these were these tiles visible in the second scene, I had created the other scene for testing, but this one is empty and has a different meshlib too)
![gridmap_bug](https://user-images.githubusercontent.com/82282845/210424244-76c073e9-0f26-4d59-a6af-67e78935ffee.png)
I can even see the parts in the 3d viewport when no scene is opened

### Steps to reproduce

Create or open a scene that has a gridmap and another node.
Select something in a gridmap to copy without clicking to place the tiles anywhere, then click onto another node. Make everything inside the scene invisible. There will be still tiles visible

### Minimal reproduction project

every project with a gridmap
Repository: rust
Issue: Nightly `#![feature(generic_const_exprs)]`: cycle detected when building an abstract representation for the const argument
Labels: C-bug,A-const-generics,requires-nightly,F-generic_const_exprs,requires-incomplete-features,I-cycle

Code:
```rust
#![feature(generic_const_exprs)]

pub trait Foo<const K: u32> {
    type T;
}

struct Bar<const A: u32>
where
    (): Foo<{A as u32}>,
    //(): Foo<A>,
    <() as Foo<A>>::T: Sized,
{}

fn main() {}

```
Error:
```
error[E0391]: cycle detected when building an abstract representation for the const argument `Bar::{constant#0}`
 --> src/bin/clone_demo2.rs:9:13
  |
9 |     (): Foo<{A as u32}>,
  |             ^^^^^^^^^^
  |
note: ...which requires building THIR for `Bar::{constant#0}`...
 --> src/bin/clone_demo2.rs:9:13
  |
9 |     (): Foo<{A as u32}>,
  |             ^^^^^^^^^^
note: ...which requires type-checking the const argument `Bar::{constant#0}`...
 --> src/bin/clone_demo2.rs:9:13
  |
9 |     (): Foo<{A as u32}>,
  |             ^^^^^^^^^^
note: ...which requires computing normalized predicates of `Bar::{constant#0}`...
 --> src/bin/clone_demo2.rs:9:13
  |
9 |     (): Foo<{A as u32}>,
  |             ^^^^^^^^^^
  = note: ...which again requires building an abstract representation for the const argument `Bar::{constant#0}`, completing the cycle
note: cycle used when computing normalized predicates of `Bar`
 --> src/bin/clone_demo2.rs:7:1
  |
7 | struct Bar<const A: u32>
  | ^^^^^^^^^^^^^^^^^^^^^^^^

error: aborting due to previous error; 1 warning emitted
```

To work around, replace `{A as u32}` with `A`.

The same issue happens with `<() as Foo<{A as u32}>>::T: Sized,`.

May be related to https://github.com/rust-lang/rust/issues/106419 ?

### Meta
`rustc --version --verbose`:
```
rustc 1.68.0-nightly (d6f99e535 2023-01-02)
binary: rustc
commit-hash: d6f99e535a301a421dfee52a7c25bb4bdf420344
commit-date: 2023-01-02
host: x86_64-unknown-linux-gnu
release: 1.68.0-nightly
LLVM version: 15.0.6
```
Repository: deno
Issue: NPM compatibility - Crypto module cannot be resolved
Labels: needs investigation,node compat

On usage of the NPM Module [@azure/storage-blob](https://www.npmjs.com/package/@azure/storage-blob) in the following context:

```
import * as AzureStorageBlob from "npm:@azure/storage-blob"

const BlobClient = AzureStorageBlob.BlobServiceClient.fromConnectionString(configs.azureconnectionstring);
const containerClient = BlobClient.getContainerClient(configs.azure_container);

//fetch image
//...


let uuid = crypto.randomUUID();
const response = await fetch(image.url);
await containerClient.getBlockBlobClient(`${user.id}/${uuid}${image.url.substring(image.url.lastIndexOf("."))}`).upload(response.body, response.body.length);
```

the following error is thrown:

```
error: Uncaught (in promise) Error: Cannot find module 'crypto'
Require stack:
- C:\Users\micha\AppData\Local\deno\npm\registry.npmjs.org\uuid\8.3.2\dist\rng.js
- C:\Users\micha\AppData\Local\deno\npm\registry.npmjs.org\uuid\8.3.2\dist\v1.js
- C:\Users\micha\AppData\Local\deno\npm\registry.npmjs.org\uuid\8.3.2\./dist/index.js
- C:\Users\micha\AppData\Local\deno\npm\registry.npmjs.org\@azure\core-http\2.3.1\dist\index.js
- C:\Users\micha\AppData\Local\deno\npm\registry.npmjs.org\@azure\storage-blob\12.12.0\dist\index.js
- C:\Users\micha\AppData\Local\deno\npm\registry.npmjs.org\@azure\storage-blob\12.12.0\dist\index.js
    at Function.Module._resolveFilename (deno:ext/node/02_require.js:624:17)
    at Function.Module._load (deno:ext/node/02_require.js:456:29)
    at Module.require (deno:ext/node/02_require.js:667:21)
    at require (deno:ext/node/02_require.js:807:18)
    at Object.<anonymous> (file:///C:/Users/micha/AppData/Local/deno/npm/registry.npmjs.org/uuid/8.3.2/dist/rng.js:8:38)
    at Object.<anonymous> (file:///C:/Users/micha/AppData/Local/deno/npm/registry.npmjs.org/uuid/8.3.2/dist/rng.js:25:4)
    at Module._compile (deno:ext/node/02_require.js:734:36)
    at Object.Module._extensions..js (deno:ext/node/02_require.js:767:12)
    at Module.load (deno:ext/node/02_require.js:645:34)
    at Function.Module._load (deno:ext/node/02_require.js:502:14)
```

but following the Deno Documentation, this shouldn't be an issue, it seems to be a Deno Bug.

Deno Version:

```
deno 1.29.1 (release, x86_64-pc-windows-msvc)
v8 10.9.194.5
typescript 4.9.4
```