sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Flutter 3.19.x made wayland an unconditional requirement
Labels: engine,platform-linux,P3,team-engine,triaged-engine

When compiling without Wayland, the following errors occur:
```
flutter/third_party/swiftshader/src/WSI/libWaylandClient.hpp:18:10: fatal error: 'wayland-client.h' file not found
../../flutter/third_party/swiftshader/src/WSI/WaylandSurfaceKHR.hpp:22:10: fatal error: 'wayland-client.h' file not found
```

I am not sure what exact commit caused the above error, but the above does not happen when compiling Flutter 3.16.8 using the Buildroot linux embedded sdk when cross-compiling an arm64 build 

My testing was done via the [Buildroot](https://buildroot.org/) embedded Linux SDK and updating from Flutter 3.16.8 to 3.19.2 cross-compiling an ARM64 build of Flutter using an X64 host without Wayland. 

Edit: Here are the configure commands:

```
>>> flutter-engine 3.16.8 Configuring
/usr/bin/sed -i -e "s%vulkan_use_x11.*%vulkan_use_x11 = false%g" output/build/flutter-engine-3.16.8/build_overrides/vulkan_headers.gni
/usr/bin/sed -i -e "s%vulkan_use_wayland.*%vulkan_use_wayland = false%g" output/build/flutter-engine-3.16.8/build_overrides/vulkan_headers.gni


cd output/build/flutter-engine-3.16.8 && rm -rf output/build/flutter-engine-3.16.8/out/linux_release_arm64 && PATH=output/host/share/depot_tools:"output/host/bin:output/host/sbin:/home/adam/.local/bin:/home/adam/Applications/bin:/home/adam/Applications/depot_tools:/home/adam/Applications/scripts:/snap/bin:/opt/zscaler/bin/:/usr/local/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/var/lib/snapd/snap/bin" PUB_CACHE=dl/br-flutter-pub-cache HOME=output/host/share/flutter/sdk ./flutter/tools/gn \
--clang \
--embedder-for-target \
--linux-cpu arm64 \
--no-build-embedder-examples \
--no-clang-static-analyzer \
--no-enable-unittests \
--no-goma \
--no-prebuilt-dart-sdk \
--no-stripped \
--use-mallinfo2 \
--runtime-mode release \
--target-os linux \
--target-sysroot output/host/aarch64-buildroot-linux-gnu/sysroot \
--target-toolchain output/build/flutter-engine-3.16.8/buildtools/linux-x64/clang \
--target-triple aarch64-unknown-linux-gnu \
--no-lto \
--enable-impeller-opengles \
--no-build-glfw-shell \
--disable-desktop-embeddings
```
Repository: vscode
Issue: Add option to increase the clickable space between the gutter and the first character of the line
Labels: feature-request,editor-core

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

This was requested a few years ago in [this Issue](https://github.com/microsoft/vscode/issues/135114), but there seems to have been confusion around how the feature was described.

It was actually assigned to a developer but then for some reason un-assigned. I'm not sure exactly what happened there. The issue did garner quite a bit of support as seen from the comments, but since the issue is long buried, I figured I'd try to start fresh and clarify exactly what the request is.

## Issue:
The gutter is extremely close to the first character of each line. So if you want to click to place the cursor before the first character (or to begin selecting text from the first character), you often end up missing and clicking the gutter instead. Often this results in accidentally folding parts of the code. Ultimately it just makes placing the cursor there more tedious than it needs to be.

## Request
Add an option, something like `editor.contentLeftPadding`, which allows the user to decide how much space is there. The important bit here is that it should operate such that if you click in that space, it places the cursor at the start of that line.

Some have suggested an aesthetic fix/hack, adding 
```
.monaco-editor .lines-content {
  padding-left: 8px;
}
```
to "vs/workbench/workbench.desktop.main.css"

This does in fact add some visual space between the text and the gutter. But crucially, you *cannot* click in that space to place the cursor.

If I have not adequately explained, I pray this meme may succeed where my words have failed me

![drake meme](https://github.com/microsoft/vscode/assets/11950317/3a58d491-32aa-44d7-b178-7c37fe65328c)

Thanks!
Repository: next.js
Issue: request host header is [::]:3000 in middleware when redirecting in server action
Labels: bug,Runtime

### Link to the code that reproduces this issue

https://github.com/kevinmitch14/redirects

### To Reproduce

1. Start application npm run build + start
2. Press submit button to trigger redirect
3. View console logs

### Current vs. Expected behavior

Current: request host header is [::]:3000
Expected: request host header is localhost:3000

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: 8.15.1
Relevant Packages:
  next: 14.2.0-canary.0 // Latest available version is detected (14.2.0-canary.0).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


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

App Router, Middleware / Edge (API routes, runtime)

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

next dev (local), next build (local)

### Additional context

---
Host looks to be okay when deployed to Vercel. However I wasn't able to test this with subdomains.

I've tracked it down to this PR https://github.com/vercel/next.js/pull/62561. Using the canary version before this logs host as localhost:3000.

For context, our app is a multi tenant app, each tenant lives on a subdomain. We use rewrites to handle this. To get the subdomain, we use the request host header.
Repository: deno
Issue: lsp: slow types diagnostics quick fixes
Labels: feat,cli,jsr

In order to reduce developer friction, the LSP could support surfacing slow type diagnostics directly in an IDE.

For example, the following slow type diagnostic could be made available:

```
error[missing-explicit-return-type]: missing explicit return type in the public API
   --> /Users/kitsonk/github/oak/application.ts:841:3
    | 
841 |   [Symbol.for("Deno.customInspect")](
    |   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ this function is missing an explicit return type
    = hint: add an explicit return type to the function

  info: all functions in the public API must have an explicit return type
  docs: https://jsr.io/go/slow-type-missing-explicit-return-type
```

In addition, the lsp could make quick fixes available to extract the inferred type from tsc to resolve the diagnostic.
Repository: TypeScript
Issue: Parameters typed as `unknown` even when the function type has the correct types
Labels: Needs More Info

### 🔎 Search Terms

mapped types, function types

### 🕗 Version & Regression Information

- This is the behavior that starts in version 4.9, and I reviewed the FAQ for entries about function types
All the versions prior to 4.9 have both scenarios with the params typed to `unknown`

### ⏯ Playground Link

[Playground Link](https://www.typescriptlang.org/play?target=99&jsx=0&exactOptionalPropertyTypes=true&noErrorTruncation=true#code/KYDwDg9gTgLgBDAnmYcDCAbAlsAdjAGSwGcY9gpiAeAFTlDNwBNi4aoBDXYgM2gFsKxAHxwAvHADeAKDhy4AegVwAYtDjEIguFGAdNuOFh5G4TCPjMQ4AMikBfBAAtUTYDw4BXDDFbEs-GAYiFaWAO7QANZwXExG8GFYGBgIyKj8HABW0FhIcBAmME5YuADmrDDWuMAAbhSy8gDaANJGhpHAiAVsALoA-ABccAAUNC09tg4AlPQgjCxSTrEYFEPDwwB0WxxQ5UMlPBRwAKozYqIHRwBKU44N8vJ9cJ64kbgQYYYMeAtXcPcPQFPdZbDY7PYnM6iACCYQ4uQ4ACMVlQXm8PrhhFMAYD5EM-t9mKxGmj3p8ADRwUHQqCcRCo15kzETYGbba7Yj4qFwWHwmBIlGkjFYuBrYbgrniGFwhHI4AM9GfLE4vFwap1KD-ewAbmk0lAkFgqRQPJl-LltFEEgAClAtCR5TRRAAfNi6g3QeAlMhQDwAY1Q7C4vAEQikAN0HCYiEGUjgS2YKygaz92DwMCGmBw+EpYA4iAwECjQ0kNSGuE8-ERFHs3KFnzgOuk9n14E9bR9-tQWfTAHkwDAsBZqHRCQsg9w+FBBJRRDIHthSORKJm0-giEvqpRLbqHjBOJPQ5RYzRdS3pG5UztUFfiKwe-haLN5qwJyHp2GJG+pzOROGHn6w77p4fqVFAwwQAOQ7cKu2YwP2g7DpaUxnnqHpGpeGDXnAPAvKB0FwH6kZkA+MBPmOr4Hu+v7CBBUHDrBfb0dwyFDLa9rEPKpGWsIurSEoJxOPwfR9NIRF6CRa4wMM87yIujBCCWKpyJG0bDMpigKAAeqJuK4qmcG5vmhZRhpDxKDpGkzJILYPC2tZ6gJ1r6P4ZRqtY4KVumFTWEUqC4bg+EWHAERQJExBicRwCkTJAL7sGP6Kf+emqYgSl6YCCZMEmaxTEMpBQCUpRSnAABEpUabZ8j2OSALycunLJbiqXqRlFm6Rl8gGemZnyO1VkOAC9nYvxyjOXeRUxLsXn4D5zj+XhiGGIikbhZFEnRVJsV7lRiUrk1gKpelnVyFlOUjN1+B5Ro+6TecUiAdwEArBshalMMl0wChOjADAnhQIY5VVbiwONrVC4kAp+2yc1ehqRp-UnXIn29XIiN6dZoPDY5yg0MUrAkIR0C6KB0jVGE6BbTDcD1VujXUw8LUI9pHUnZ9RkFkWTCo5plkZZjQ3NiNo1sPjRisBwGCaETtLAKT5OU3B23yPFh4ftDGlHQdGVnasIzXQVd2iOVlVDeDcmQw1x2w1GiCtXp6Ns1JPOO4CAt2ULONwAA6ks8C1Hg4vxhwYAoLgk0uLoZPABTMXU6r1FJQz8ha8nuK68mF1SQbt1ufdkiPZoL1vR92faj9f0A2VpWgx7dnm3ItNJ5rcN28zfNIyjSO86zbuDR7tZAA)

### 💻 Code

_No response_

### 🙁 Actual behavior

The function with no default shows the proper function type but the parameters are typed as `unknown`

### 🙂 Expected behavior

The parameters should have the types of the function params

### Additional information about the issue

There is also a [smaller reproduction](https://www.typescriptlang.org/play?target=99&jsx=0&exactOptionalPropertyTypes=true&noErrorTruncation=true#code/C4TwDgpgBAMglgZ2BAdhATgHgCoD4oC8AUFFAHID2KZArgDZ0CGARnRDvhAB7IoAmCKAApG6AOYAuKHBQAzDFACqASkL4aKANYoKAdxQlSUAPzDRkpaoLqtO-YdJS0ANwxEioSFADCjBs0YAY01CM3EpAHJdYFkIqxttPQMiPghApnRoWQ1A4DgqKB0AEQhZRnpgbHAIAAVRRgBbCGQsbChuXgEfPzoA4NwhWSl4JFQMDmUpZwo4PhS0jKycvILUsoqqyDr0Rubxto7ULt9-IJCCbtP+weHEXn3cSahp2fdi0vK6Surt3ZahQwAekBUAAesZDCJxPEoABvAC+ABogSDwURlO41p9vlt6k1-iiwRDSFCxDCEcjSMCieigA) that was made by `mkantor` on discord.
Repository: go
Issue: proposal: embed: embed and expose also media/mime type
Labels: Proposal

### Proposal Details

I think this is a common use case: we use embed to embed some files at compile time and then we serve them at runtime using HTTP. But to serve files at runtime, one has to also know the media/mime type of the file, to set `Content-Type` correctly. One way to do that is to use standard `mime.TypeByExtension` on the embedded filenames. This works well if filenames have known file extensions and developer can generally predict the outcome if they notice a file extension is missing or if the file extension is an obscure one.

But what is hard to observe by a developer is that `mime.TypeByExtension` requires system installation of a corresponding database. If that database is missing, then behavior on their local machine might differ from the production machine. Even worse, the behavior might be different if the database is different (e.g., locally one uses Ubuntu and production uses Alpine).

To make production deployment work well, we use static builds. But sadly, because of the dependency on this database, even static build can behave differently.

## Proposal

I propose that embedded files with `embed.FS` detect the media/mime type at compile time and expose it in some way to the developer (I am open to how exactly this is implemented). The critical point here is that this is done at compile where developer has easier time controlling the environment, so that the behavior is the same wherever the binary is later on deployed/ran.

## Alternative proposal

Maybe there should be a way to embed currently available mime/media type database into the binary at compile time.
Repository: godot
Issue: [GDScript] Godot allows to run game with non-existing constant value. Error comes only after executing the line.
Labels: topic:gdscript,documentation

### Tested versions

Godot 4.2.1.

### System information

Windows 10, Godot 4.2.1, Forward+

### Issue description

When executing a game which has a scene, which uses constants from another scene, the Godot lets you build the game and run it normally. Game executes normally until Godot hits the certain line which has the non-existing const value, then game crashes and throws an error. This is problematic because if the game won't hit the certain line, it will execute normamally until then. Although you can clear this error with unit testing, it is problematic because you can ship a software with and error which is not found in compile.

### Steps to reproduce

Make a scene which has const values. Make other scene which uses the const values from other scene. The game builds without and runs without any errors until the non-existing const line is reached in execution.

### Minimal reproduction project (MRP)

[bugtest.zip](https://github.com/godotengine/godot/files/14501480/bugtest.zip)
Repository: storybook
Issue: [Bug]: SolidJS deprecated package
Labels: bug,good first issue,help wanted,solid

### Describe the bug

When a user installs the latest version of Storybook in their SolidJS project out of the box, he automatically gets the now deprecated `@storybook/testing-library` as part of the installation process. Also, the examples provided relate to the package. This presents a disconnect where the user is presented with a deprecated package and examples irrelevant to the current version of Storybook, where we introduced the `@storybook/test` package as the default one. For example:
![storybook-rc-solid-packages-stories](https://github.com/storybookjs/storybook/assets/22988955/573f2ecf-4286-4804-b445-1a4365480748)

This issue becomes more relevant if they try to upgrade from a previous Storybook version (e.g., 7.5/7.6) to the latest version, where two things happen:
- The user is prompted to remove the `@storybook/testing-library` package from the project as part of the upgrade process.
- The package is installed as a direct dependency and not as a dev dependency as other Storybook packages, as shown below

https://github.com/storybookjs/storybook/assets/22988955/fdc08e9a-ff7e-4f19-9a99-639498c4ffa6


I'm aware that SolidJS is not part of the core frameworks we support, is currently maintained by the community, and may not be on par with the other frameworks we support. However, it would be in our best interest to ensure that if the `@storybook/test` package is not supported, we should not install it as part of the migration process. Or if it is supported, we should provide the relevant examples (i.e., the Button component example for args mocking) and fix the package to be installed as a dev dependency.

cc @vanessayuenn @kasperpeulen @JReinhold 


### To Reproduce

- Set up a SolidJS project
- Install the latest Storybook version 
- Run the upgrade process

### System

_No response_

### Additional context

_No response_
Repository: pytorch
Issue: Support TorchBind x PT2
Labels: triaged,oncall: pt2,module: pt2-dispatcher

Tracking issue.
```[tasklist]
### Tasks
```


cc @ezyang @msaroufim @bdhirsh @anijain2305 @chauhang
Repository: next.js
Issue: Incorrect alternates Example in Metadata Interface Documentation
Labels: bug,TypeScript

### Link to the code that reproduces this issue

https://github.com/ciruz/next.js-hreflang

### To Reproduce

The `metadata-interface.d.ts` file contains incorrect documentation regarding the structure of the alternates property within the Metadata type. The example provided uses `hreflang` to define alternate languages, which contradicts the actual interface definition that expects a `languages` property.

![image](https://github.com/vercel/next.js/assets/987947/88e49bed-00d4-4578-9e3a-9d260da35a55)

![image](https://github.com/vercel/next.js/assets/987947/024d3994-de1a-4f7e-8918-649e3bc294c2)

![image](https://github.com/vercel/next.js/assets/987947/c67a698f-4e27-4a12-b9f3-90b429e7b64e)

![image](https://github.com/vercel/next.js/assets/987947/7c84a246-41c7-46ee-b522-3cbad82e94f8)


### Current vs. Expected behavior

Show a correct example.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
Binaries:
  Node: 18.18.2
  npm: N/A
  Yarn: N/A
  pnpm: 8.15.4
Relevant Packages:
  next: 14.1.2
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.2
Next.js Config:
  output: N/A
```


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

TypeScript (plugin, built-in types)

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

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

_No response_
Repository: flutter
Issue: [pigeon] Move common helper methods to language `Generator` class
Labels: package,team-ecosystem,p: pigeon,P2,c: tech-debt,triaged-ecosystem

Some common checks are used in the generator of most languages (e.g. `hasHostApi`, `hasFlutterMethod`, etc...). These checks can be moved to the `Generator` class so the code can be reused.
Repository: flutter
Issue: Rendering errors with Rect.largest when used with toImage (e.g. gold image tests) using impeller
Labels: engine,P2,e: impeller,team-engine,triaged-engine

If you run the following using `flutter test --enable-impeller`, you get a `test.png` containing a hollow square with the top left corner damaged, but it should just be a hollow square:

![](https://github.com/flutter/flutter/assets/551196/2fd9f494-58d1-41d8-91dd-d52cdab6fa38)

```dart
// Copyright 2014 The Flutter Authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.

import 'dart:io';
import 'dart:ui';

const double z = 1000000000; // aka _giantScalar, used in Rect.largest

void main() async {
  final PictureRecorder recorder = PictureRecorder();
  final Canvas canvas = Canvas(recorder);
  final Path clip = Path()
    ..fillType = PathFillType.evenOdd
    ..addRect(const Rect.fromLTRB(-z, -z, z, z))
    ..addRect(const Offset(50.0, 50.0) & const Size(100.0, 100.0));
  canvas.clipPath(clip);
  canvas.drawPaint(Paint()..color = const Color(0xFF33CC66));
  final Picture picture = recorder.endRecording();
  await File('test.png').writeAsBytes((await (await picture.toImage(200, 200)).toByteData(format: ImageByteFormat.png))!.buffer.asUint8List());
}
```
Repository: storybook
Issue: [Bug]: Static assets referenced by absolute URI not respected in Template block
Labels: bug,vue3,sev:S2

### Describe the bug

When passing a `<template>` block `staticDirs` configuration is not respected and instead a dynamic import is attempted.



### To Reproduce


`.storybook/main.js`

```
staticDirs: ['../public'],
```

This directory contains a subdirectory `images` which contains image files.

`apps/helloWorld.vue`

```
<template>
	<div class="app-helloWorld">
		<img src="/images/foo.jpg"/>
	</div>
</template>
```

Result:

```
Failed to fetch dynamically imported module: http://localhost:32000/apps/helloWorld.stories.js?t=1709680763172
```

### System

```bash
Storybook Environment Info:

  System:
    OS: Linux 5.10 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
    CPU: (8) x64 Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 18.18.0 - ~/.nvm/versions/node/v18.18.0/bin/node
    npm: 9.8.1 - ~/.nvm/versions/node/v18.18.0/bin/npm <----- active
  Browsers:
    Chrome: 122.0.6261.69
  npmPackages:
    @storybook/addon-essentials: ^7.6.17 => 7.6.17 
    @storybook/addon-interactions: ^7.6.17 => 7.6.17 
    @storybook/addon-links: ^7.6.17 => 7.6.17 
    @storybook/addon-styling: ^1.3.7 => 1.3.7 
    @storybook/blocks: ^7.6.17 => 7.6.17 
    @storybook/testing-library: ^0.2.2 => 0.2.2 
    @storybook/vue3: ^7.6.17 => 7.6.17 
    @storybook/vue3-vite: ^7.6.17 => 7.6.17 
    msw-storybook-addon: ^1.10.0 => 1.10.0 
    storybook: ^7.6.17 => 7.6.17
```


### Additional context

Fully qualified URI are respected i.e. http://localhost:32000/images/foo.jpg
Repository: PowerToys
Issue: [Keyboard Manager] allow running UWP apps with keyboard shortcuts
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

1. The user is able to select a UWP app to launch when a keyboard shortcut is pressed.
2. The user is able to select a shortcut (.lnk) file to launch when a keyboard shortcut is pressed.

### Scenario when this would be used?

I am trying to launch Windows Terminal when windows+return is pressed. This workflow is often used in Linux.

### Supporting information

I tried a few workarounds that doesn't work:
1. Creating a shortcut on the Desktop and selecting the shortcut (causes "Catastrophic failure")[1]
2. Selecting wt.exe directly (doesn't launch)
3. Selecting explorer.exe with the argument `shell:AppsFolder\(AppID)` (causes a crash)[2]

My current workaround is to call `cmd.exe` with this exact argument: `/s /c "start shell:AppsFolder\(AppID)"` where `(AppID)` is the result of `Get-StartApps Terminal`.
This solution is suboptimal since it briefly shows the `cmd` window before closing and laucnhing Windows Terminal itself.

# System Info

PowerToys: 0.79.0
Windows: Windows 11 Enterprise 22H2 22621.3235


[1]: https://github.com/microsoft/PowerToys/assets/20792268/1d6080db-5d93-4754-9844-cc4644816448
[2]: https://github.com/microsoft/PowerToys/assets/20792268/d426e103-0421-460b-b27c-c8bc764a891f
Repository: deno
Issue: suggestion: option to only publish exported module graph
Labels: suggestion,publish,jsr

`deno publish` currently publishes all files within a package, even those not part of the exported module graph ([example](https://jsr.io/@std/collections/0.218.2) - test files aren't included in exports). I suggest adding a user-defined option that, when enabled, only publishes files that are included in the exported module graph.

According to @dsherret, doing such a thing automatically is problematic because detecting whether a script is fully analyzable is challenging. Hence, the option being user-defined. As enabling this functionality could be problematic, it'd be best to accompany the feature with clear documentation and warnings if misused.

The benefits of such a feature include:
1. Fewer files published to JSR.
2. In most cases, it avoids the need to define files to be excluded from publishing ([example](https://github.com/denoland/deno_std/blob/6c7b13d5cac74e55519579d06f0ec207c643163f/_tools/convert_to_workspace.ts#L233-L237)). In other words, less boilerplate.
Repository: godot
Issue: FileDialog() file picker does not default to the current_path property when it opens
Labels: documentation,topic:gui

### Tested versions

v4.3.dev3.official [36e943b6b]

### System information

Linux Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8

### Issue description

- When opening a file picker dialog using the `FileDialog` class/node it does not default to the  `current_path` (or `current_dir`) property. Issues seems to be with both native and non native dialog. 

### Steps to reproduce

Add the following code to an empty `Control` node scene and run it. The native folder picker will open but if does not position nor select the `current_path`. What it should do, is display and position to the folder as specified in `current_path`. Same issue happens with the godot file picker (setting `file_dialog.use_native_dialog=false`)

```python
extends Control

var default_dir='/home'
var file_dialog:FileDialog

func _ready():
	ProjectSettings.set_setting("display/window/subwindows/embed_subwindows", false)
	file_dialog=FileDialog.new()
	file_dialog.visible=false
	#file_dialog.use_native_dialog=false
	file_dialog.use_native_dialog=true	
	file_dialog.current_dir=default_dir
	file_dialog.access=FileDialog.ACCESS_FILESYSTEM
	file_dialog.file_mode=FileDialog.FILE_MODE_OPEN_DIR	
	add_child(file_dialog)
	file_dialog.visible=true	
	pass # Replace with function body.
```

### Minimal reproduction project (MRP)

see code above