sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: Question: Async React Reconciler
Labels: Status: Unconfirmed,Resolution: Needs More Information

Apologies for using the bug template, but I have a question regarding React Reconciler. I understand that this is not intended for questions, and I appreciate your understanding.

I'm building a custom React reconciler by using `react-reconciler` package. I'm wondering if it is possible having an async reconciler. I need to dynamic import a module in the _createInstance_ method of HostConfig based on the _type_ parameter. A minimal implementation example could be:

```typescript
// reconciler.ts
async createInstance(type, props, rootContainer, hostContext, internalHandle){
    const Module = await import(`my-module-path/${type}`);
    const instance = new Module();
    return instance;
}

getPublicInstance(instance){
    return instance; // this is a Promise
}
```

The main issue is that in this way i'm returning a Promise as ref and then i should handle it in this way:

```typescript
// Component.tsx
  useEffect(() => {
    ref.current.then((instance) => {
      // access here to instance
    })
  }, [ref])
```


Mine is not a primary renderer so, as workaround, i thought to traversing the Fiber node (generated by React reconciler) to get the all tag names (JSX intrinsic elements) and then dynamic import them before to start the secondary rendering process (`createContainer` and `updateContainer`). Unfortunately this not entirely correct because the root Fiber node does not encompass all components of the tree. For example, in the following scenario, only one between the box and the sphere will be included:

```typescript
condition ? <box /> : <sphere />
```

Are there other ways to think about this problem?

---

React (react package) version: 18.3.1
React reconciler (react-reconciler package): 0.29.2
Repository: PowerToys
Issue: The PowerToys Preview pane cannot preview files properly, you need to close the format in the preview
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

File Explorer: Preview Pane

### Steps to reproduce

Normal open file Explorer, preview txt display can not preview this file, but close the format support in file preview, and you can preview the file normally

### ✔️ Expected Behavior

Preview the file normally and display the file content

### ❌ Actual Behavior

This file cannot be previewed

### Other Software

_No response_
Repository: material-ui
Issue: [RFC] Start a small collaboration with RJSF to enhance the Material UI theme they have created?
Labels: waiting for 👍,ready to take,RFC

### What's the problem?

The [RJSF library](https://github.com/rjsf-team/react-jsonschema-form) has a community-maintained Material UI theme. The library is actively maintained and used in many projects.

However, some widgets do not properly use Material UI theming. There is the `data-url` widget and the date & time ones: `date`, `date-time`, and `time`. Documentation [here](https://rjsf-team.github.io/react-jsonschema-form/docs/usage/widgets/).

I'm sure there are developers here who had to build their custom widgets for the RJSF Material UI theme to conform to Material Design properly. Even sharing these examples would be helpful for those who don't yet have their solutions.

I decided to start this RFC after noticing that besides the date & time widgets missing, the `data-url` (file) widget is also missing proper Material UI integration. Creating this widget does not seem like a huge endeavor.

@oliviertassinari What do you think? Could the Material UI team consider contributing to the RJSF Material UI theme at some point?
Even just documentation examples (either on our side or theirs) would greatly help. I opened an issue regarding this over at rjsf-team/react-jsonschema-form#4447.
The Material UI theme for RJSF was, at least for me, a deciding factor in adopting Material UI overall in my project.
As a taste of what this would take, here's an issue I opened where I made a custom Material UI password widget for RJSF, with an eye icon to show/hide the input: rjsf-team/react-jsonschema-form#4274

### What are the requirements?

_No response_

### What are our options?

_No response_

### Proposed solution

_No response_

### Resources and benchmarks

_No response_

**Search keywords**:
Repository: PowerToys
Issue: A number of mistranslation in Korean text
Labels: Issue-Bug,Area-Localization,Needs-Triage,Issue-Translation

### Microsoft PowerToys version

0.87.1

### Utility with translation issue

General

### 🌐 Language affected

Korean

### ❌ Actual phrase(s)

1. Microsoft PowerToys는 **강력한 사용자**가 생산성을 높이기 위해 Windows 환경을 조정하고 간소화할 수 있는 유틸리티 세트입니다. **Microsoft 및 PowerToys 💗커뮤니티에서** 만들었습니다. (Microsoft PowerToys is a set of utilities for power users to tune and streamline their Windows experience for greater productivity. Made with 💗 by Microsoft and the PowerToys community.) *(General settings)*
2. **관리자 자격**으로 PowerToys 다시 시작 (Restart PowerToys as administrator) *(General settings)*
3. **특성** (Attribution) *(recurring phrase in a number of tool settings)*
4. **Awake 만들기에서 Den Delimarsky의 작업** (Den Delimarsky's work on creating Awake) *(Awake attribution)*
5. Rooler에서 **영감을 받습니다.** (Inspired by Rooler) *(Screen Ruler attribution)*
6. **빠른 강조**에 대한 자세한 정보 (Learn more about Quick Accent) *(Quick Accent settings)*

![PowerToys General settings window; app description text and "Restart PowerToys as administrator" button is highlighted](https://github.com/user-attachments/assets/f2a79d22-9604-47dd-84a8-9443ad93405b)

![Awake in PowerToys Settings window; the text "특성" is highlighted](https://github.com/user-attachments/assets/7fb7868c-5670-4a4e-bc12-678fb5691eb2)

### ✔️ Expected phrase(s)

1. Microsoft PowerToys는 **고급 사용자**가 생산성을 높이기 위해 Windows 환경을 조정하고 간소화할 수 있는 유틸리티 세트입니다. **Microsoft 및 PowerToys 커뮤니티에서 💗을 담아** 만들었습니다.
2. **관리자 권한**으로 PowerToys 다시 시작
3. **기여자** (lit. *contributors*)
4. **Awake 개발에 Den Delimarsky님이 참여** (lit. *Den Delimarsky has participated on developing Awake*)
5. Rooler에서 **착안**
6. **빠른 악센트**에 대한 자세한 정보

### ℹ Why is the current translation wrong

1. First sentence is inconsistent with the identical Welcome to PowerToys text; additionally, the phrase "power user" makes little sense if translated literally to "강력한 사용자" (lit. *strong user*). Second sentence was mistranslated to mean "Made by Microsoft and the PowerToys 💗community".
2. Inconsistent with the rest of Windows interface, which consistently translates "as administrator" to "관리자 권한으로".
3. The Korean word "특성" only means characteristic/property/quality and can not be used for acknowledgement of authorship. "기여자" (or "기여" (lit. *contributions*)) is one of the closest term to *attribution* I can think of.
4. Translated sentence is very unnatural and awkward in Korean.
5. "받습니다" is considered present tense and easily considered awkward in this context. "영감을 받음" would be another good candidate, but "착안" (uses noun rather than inflected verb) seems more consistent and idiomatic.
6. Inconsistent with the rest of PowerToys interface, which consistently translates *Quick Accent* to "빠른 악센트". Additionally, "강조" means emphasis and can not be used to refer to diacritics.
Repository: rust
Issue: E0499 mentions "previous iteration of the loop" in proc macro code without any loops.
Labels: A-diagnostics,T-compiler

### Code

```Rust
use quote::quote;

#[proc_macro]
pub fn my_macro(_: proc_macro::TokenStream) -> proc_macro::TokenStream {
    quote! {
        struct Thing<'a>(&'a mut i32);
        impl Drop for Thing<'_> {
            fn drop(&mut self) {}
        }
        #[allow(unused)]
        fn test() {
            let mut foo = 1;
            if let Some(thing) = Some(Thing(&mut foo)) {
            } else {
                let x = &mut foo;
            }
        }
    }
    .into()
}
```

### Current output

```Shell
error[E0499]: cannot borrow `foo` as mutable more than once at a time
 --> src/lib.rs:1:1
  |
1 | bar::my_macro!();
  | ^^^^^^^^^^^^^^^-
  | |              |
  | |              ... and the first borrow might be used here, when that temporary is dropped and runs the destructor for type `Option<Thing<'_>>`
  | `foo` was mutably borrowed here in the previous iteration of the loop
  | a temporary with access to the first borrow is created here ...
  |
  = note: this error originates in the macro `bar::my_macro` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0499`.
error: could not compile `foo` (lib) due to 1 previous error
```

### Desired output

```Shell
Something not mentioning loops
```

### Rationale and extra context

I was poking around to see how the rust 2024 "`if let` temporary scope" changes interact with different spans from proc macros, and I discovered this issue.

The error output above occurs when the macro is called from another crate with no arguments. Both the calling crate and the proc macro crate use edition 2021.

Full code for reproducing the issue: [foo.zip](https://github.com/user-attachments/files/18389368/foo.zip)

### Other cases

```Rust

```

### Rust Version

```Shell
rustc 1.86.0-nightly (eb54a5083 2025-01-11)
binary: rustc
commit-hash: eb54a50837ad4bcc9842924f27e7287ca66e294c
commit-date: 2025-01-11
host: aarch64-apple-darwin
release: 1.86.0-nightly
LLVM version: 19.1.6
```

### Anything else?

_No response_
Repository: rust
Issue: Wrong type suggested in `overflowing_bin_hex`
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn main() {
    _ = 0x8FFF_FFFF_FFFF_FFFEu32;
}
```

### Current output

```Shell
error: literal out of range for `i32`
 --> src/main.rs:2:9
  |
2 |     _ = 0x8FFF_FFFF_FFFF_FFFE;
  |         ^^^^^^^^^^^^^^^^^^^^^
  |
  = note: the literal `0x8FFF_FFFF_FFFF_FFFE` (decimal `10376293541461622782`) does not fit into the type `i32` and will become `-2i32`
  = help: consider using the type `i128` instead
  = note: `#[deny(overflowing_literals)]` on by default
help: to use as a negative number (decimal `-2`), consider using the type `u32` for the literal and cast it to `i32`
  |
2 |     _ = 0x8FFF_FFFF_FFFF_FFFEu32 as i32;
  |         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```

### Desired output

```Shell
error: literal out of range for `i32`
 --> src/main.rs:2:9
  |
2 |     _ = 0x8FFF_FFFF_FFFF_FFFE;
  |         ^^^^^^^^^^^^^^^^^^^^^
  |
  = note: the literal `0x8FFF_FFFF_FFFF_FFFE` (decimal `10376293541461622782`) does not fit into the type `i32` and will become `-2i32`
  = help: consider using the type `i128` instead
  = note: `#[deny(overflowing_literals)]` on by default
help: to use as a negative number (decimal `-2`), consider using the type `u64` for the literal and cast it to `i32`
  |
2 |     _ = 0x8FFF_FFFF_FFFF_FFFEu64 as i32;
  |         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```

### Rationale and extra context

Found this when working on #135249. Wrong type is suggested in overflowing bin/hex literals for them to be casted back to current type.

### Other cases

```Rust

```

### Rust Version

```Shell
rustc 1.84.0 (9fc6b4312 2025-01-07)
binary: rustc
commit-hash: 9fc6b43126469e3858e2fe86cafb4f0fd5068869
commit-date: 2025-01-07
host: x86_64-unknown-linux-gnu
release: 1.84.0
LLVM version: 19.1.5
```

### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"11happy"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: puppeteer
Issue: [Bug]: getting started seems buggy
Labels: bug,confirmed,documentation,P3

### Minimal, reproducible example

```TypeScript
// index.js
import puppeteer from "puppeteer";

(async () => {
  // Launch the browser and open a new blank page
  const browser = await puppeteer.launch({ headless: false });
  const page = await browser.newPage();

  // Navigate the page to a URL
  await page.goto("https://developer.chrome.com/");

  // Set screen size
  await page.setViewport({ width: 1080, height: 1024 });
  // Type into search box
  await page.type(".devsite-search-field", "automate beyond recorder");

  // Wait and click on first result
  const searchResultSelector = ".devsite-result-item-link";
  await page.waitForSelector(searchResultSelector);
  await page.click(searchResultSelector);

  // Locate the full title with a unique string
  const textSelector = await page.waitForSelector(
    "text/Customize and automate"
  );
  const fullTitle = await textSelector?.evaluate((el) => el.textContent);

  // Print the full title
  console.log('The title of this blog post is "%s".', fullTitle);

  await browser.close();
})();
```


### Background

trying to get started lol

### Expectation

this getting started should work without debug

### Reality

i tried node index.js page.type not working so page.waitForSelector timed out
but when i used debug mod add break point in each step, it works lol, pretty strange

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

24.0.0

### Node version

18.12.1

### Package manager

npm

### Package manager version

8.19.2

### Operating system

Windows
Repository: flutter
Issue: [Impeller] An app crashes on Umidigi Bison 2 Pro
Labels: waiting for customer response,in triage

### Steps to reproduce

Hello,
You have asked to submit issues with Impeller on Android.
After upgrading an app to Flutter 3.27.1, a customer has reported that the app stopped working on this device:
- Umidigi Bison 2 Pro
After disabling Impeller in AndroidManifest.xml, it works again for him.

### Expected results

The app is working with Impeller.

### Actual results

The app is crashing with Impeller enabled, but works with Skia.

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[Paste your output here]
```

</details>
Repository: pytorch
Issue: nn.functional.interpolate doesn't work correctly with NCW tensors when output W exceeds 2^23
Labels: module: nn,triaged,module: edge cases

### 🐛 Describe the bug

nn.functional.interpolate returns strange results for NCW tensors when output W exceeds 2^23.

**Reproduction:**
```
import torch

n = (1 << 22) + 4
x = []
for i in range(n // 2):
    x.append(0.0)
    x.append(1.0)

x = torch.tensor(x, device="cuda:0", dtype=torch.float)
x = x.view(1, 1, -1)
y = torch.nn.functional.interpolate(x, size = n * 2, mode="linear")

print(y[0, 0, :20])
print(y[0, 0, -20:])
```

**Output:**
```
tensor([0.0000, 0.2500, 0.7500, 0.7500, 0.2500, 0.2500, 0.7500, 0.7500, 0.2500,
        0.2500, 0.7500, 0.7500, 0.2500, 0.2500, 0.7500, 0.7500, 0.2500, 0.2500,
        0.7500, 0.7500], device='cuda:0')
tensor([0.2500, 0.2500, 0.7500, 0.7500, 0.2500, 0.2500, 0.7500, 0.7500, 0.2500,
        0.2500, 0.7500, 0.7500, 0.5000, 0.5000, 0.5000, 0.5000, 0.5000, 0.5000,
        0.5000, 1.0000], device='cuda:0')
```

Only the first 2^23 values are correct.
It reproduces with float32 and float16 types on CPU and CUDA

### Versions

PyTorch: 2.5.1 CUDA 12.4
Python: 3.12.3
OS: Ubuntu 24.04


cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: vscode
Issue: Buttons in the showInformationMessage modal can completely cover the source
Labels: feature-request,workbench-notifications

<!-- ⚠️⚠️ 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.96.2 (Universal)
- OS Version: Darwin arm64 24.2.0

## Issue:
**Buttons in the `showInformationMessage` modal can completely cover the source**

### Real world example ([Svelte for VS Code](https://marketplace.visualstudio.com/items?itemName=svelte.svelte-vscode))
<img src="https://github.com/user-attachments/assets/2161f88e-1cba-4cba-9da6-b6d9e03fbfd8" width="500">

### Real world example, tweaked (User can't hover over Source!)
<img width="482" alt="Image" src="https://github.com/user-attachments/assets/db083ddb-1e44-4541-a4e9-e92184e690e4" />

### Real world example with added `min-width: 15%`
**User can hover and see the Source in the tooltip**
<img src="https://github.com/user-attachments/assets/3180972a-bf67-4681-af70-b1f91581292e" width="500">

## Steps to Reproduce:

1. Call the `window.showInformationMessage` with buttons that have long labels
2. Buttons completely cover the source, user can't hover over it
Repository: PowerToys
Issue: RAM Optimizer
Labels: Needs-Triage

### Description of the new feature / enhancement

A small tool to:

1. Clean up the RAM in one click
2. Show real-time RAM usage and available RAM of system with an awesome UI.
3. Should be able to run over other apps or be in the taskbar so that it is accessible all the time except when the user is in full screen mode.

May also include:

1. Dropdown to show major apps running and an option to kill app / process from there.

### Scenario when this would be used?

It will be very useful to people using a lot of apps on system. Many apps when closed do not free up the Space in RAM completely. So, after closing multiple apps like those if the user tries to open an application which uses a lot of memory gets laggy.

### Supporting information

The sample of the app which I am referring to can be found bundled with Advanced system care from iobit called as performance Monitor.
Repository: PowerToys
Issue: to past text without leading spaces
Labels: Needs-Triage

### Description of the new feature / enhancement

to past text without leading spaces

### Scenario when this would be used?

copying from mail or from word

### Supporting information

_No response_
Repository: next.js
Issue: [DynamicIO] Production build fails if you add intercepting routes inside multi-root layouts
Labels: dynamicIO

### Link to the code that reproduces this issue

https://github.com/apostolos/nextjs-intercepting-multi-root

### To Reproduce

1. Build the application `pnpm run build`

### Current vs. Expected behavior

The app fails to build when an intercepting route is inside a multi-root layout. No matter what I've tried it causes prerendering errors similar to the below:

In this repro:
<img width="1152" alt="image" src="https://github.com/user-attachments/assets/88f50d37-5f5f-4f13-af07-717f68a584b1" />

In a real app:
<img width="748" alt="image" src="https://github.com/user-attachments/assets/bcc85020-6f32-4bdc-9775-e29bb947b73b" />

The only thing I've tried that didn't cause a production build error, was adding a `loading.tsx` at the `app/` level. This of course causes hydration errors since it creates a `Suspense` boundary above `<html>`, something that is not allowed.

### Provide environment information

```bash
Node.js v23.6.0

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Dec  6 18:56:34 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 12
Binaries:
  Node: 23.6.0
  npm: 11.0.0
  Yarn: N/A
  pnpm: 9.15.3
Relevant Packages:
  next: 15.2.0-canary.5 // Latest available version is detected (15.2.0-canary.5).
  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)

dynamicIO

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

next build (local)

### Additional context

_No response_
Repository: godot
Issue: Drag text files in filesystem makes the engine throw the error `No loader found for resource: "file_path" (expected type: )`
Labels: bug,topic:editor

### Tested versions

- Reproducible: Between v4.0.beta2.official [f8745f2f7] ~ v4.0.beta8.official [45cac42c0] and from v4.0.beta11.official [91713ced8] upwards

- Not reproducible: v4.0.beta1.official [20d667284] and lower and between v4.0.beta9.official [e780dc332] ~ v4.0.beta10.official [d0398f62f]

### System information

Godot v4.4.dev (abf8e1e6f) - Windows 10 (build 19045) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated AMD Radeon RX 580 2048SP (Advanced Micro Devices, Inc.; 31.0.21921.1000) - AMD Ryzen 5 3600 6-Core Processor (12 threads)

### Issue description

As the title says, dragging a text file in the editor raises the pointed error, json files seems to be the exception. Also, open the text file stops the error for the file opened until you restart the editor, the others will keep raising the error until you open them.

https://github.com/user-attachments/assets/de2c1e94-f6c4-4d90-8d87-97e499d6ea55

<br>

Bisecting points the pr #62413 (in 4.0 beta 2) as the one that introduced this issue. Pr #68498 (in 4.0 beta 9) made the error stop but had to be reverted in 4.0 beta 11 because introduced other regressions:

![Image](https://github.com/user-attachments/assets/8d0a643b-e12f-48b1-8172-a7038624c3d9)

<br>

CC @willnationsdev

### Steps to reproduce

Drag a txt file in the filesystem.

### Minimal reproduction project (MRP)

Not necessary, any project with a txt file can reproduce.