sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: SSIL rendering issue on Intel IGP on Windows
Labels: bug,platform:windows,topic:rendering,topic:thirdparty,needs testing,topic:3d

### Tested versions

4.3beta1

### System information

Tested on 2 Configs

### Issue description

On Godot v4.3.beta1 - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2060 (NVIDIA; 31.0.15.4626) - Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 Threads):
![image](https://github.com/godotengine/godot/assets/10520249/6c59bfc1-5052-443e-ab90-8d1c12a8351b)

On Godot v4.3.beta1 - Windows 10.0.19045 - Vulkan (Forward+) - integrated Intel(R) UHD Graphics 620 (Intel Corporation; 31.0.101.2111) - Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz (8 Threads):
![unnamed](https://github.com/godotengine/godot/assets/10520249/cd734af9-7cb1-4bfd-85eb-cc56457465ab)


### Steps to reproduce

You can find the project below.
But in terms of replicating the issue, might be worth trying on NVIDIA vs Intel UHD Graphics?

Also I noticed that the editor camera was not set to VFOV = 10 deg when importing the project to another machine. It does affect the SSIL but does not explain the whole issue.

### Minimal reproduction project (MRP)

Project link: https://github.com/Nodragem/twin-stick-shooter-starter-kit
Repository: material-ui
Issue: [material-ui][Rating] Screen reader announces incorrect value for maximum amount of stars
Labels: bug 🐛,accessibility,package: material-ui,component: rating

### Steps to reproduce

Link to live example: https://codesandbox.io/embed/dazzling-surf-4dgzp6?fontsize=14&hidenavigation=1&theme=d

## Prerequisites
- A screen reader application, e.g. NVDA (Windows) or Voiceover (IOS), is used

## Steps:
1. Click on one of the stars (1-5) to give a rating, say the 2nd star to give a two-star rating


### Current behavior

The screen reader announces the maximum value of the rating incorrectly.
## Firefox
The screen reader announces "two of six", when max amount is actually 5.

Presumably, the value 6 comes from the number of radio inputs (on for each star, one for zero stars) in the component. By  adding aria-hidden="true" with developer tools to the zero input, the max value is read correctly.

## Chrome, Edge
The screen reader announces "two of seventeen" (!). 

For these browsers, the number 17 perhaps comes from the number of inputs on the page?

### Expected behavior

The screen reader should announce the max. value correctly, "two of five" in this case.

### Context

We use MUI Rating to allow users to provide feedback on the digital services of a large public sector institution. The accessibility of the services is naturally very important. 

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Windows 10 10.0.19045
  Binaries:
    Node: 20.5.1 - C:\Program Files\nodejs\node.EXE
    npm: 9.8.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: Not Found
  Browsers:
    Chrome: Not Found
    Edge: Chromium (123.0.2420.97)
  npmPackages:
    @emotion/react: 11.10.5 => 11.10.5
    @emotion/styled: 11.10.5 => 11.10.5
    @mui/base:  5.0.0-beta.18
    @mui/core-downloads-tracker:  5.14.10
    @mui/icons-material: 5.11.9 => 5.11.9
    @mui/material: 5.11.9 => 5.11.9
    @mui/private-theming:  5.14.10
    @mui/styled-engine:  5.14.10
    @mui/system:  5.14.10
    @mui/types:  7.2.5
    @mui/utils:  5.14.12
    @mui/x-date-pickers: 6.16.1 => 6.16.1
    @types/react: 18.2.20 => 18.2.20
    react: 18.2.0 => 18.2.0
    react-dom: 18.2.0 => 18.2.0
    typescript: 5.2.2 => 5.2.2

```
</details>


**Search keywords**: rating nvda reader
Repository: godot
Issue: Saving a scene re-selects a file
Labels: bug,topic:editor

### Tested versions

4.3 beta1

### System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description


https://github.com/godotengine/godot/assets/2223172/1c6b8abd-0407-4339-a3d8-6912fdf25b1c



### Steps to reproduce

1. Select a file in FileSystem dock
2. Deselect it by clicking empty space
3. Press Ctrl+S (make sure you are in 2D or 3D editor)

### Minimal reproduction project (MRP)

N/A
Repository: tauri
Issue: [bug] dynamic create webview in current window  crash  in  windows 10
Labels: type: bug,status: needs triage,scope: unstable flag

### Describe the bug

#[tauri::command]
pub fn create_webview_inner(
    window: tauri::Window,
    url: String,
    x: f64,
    y: f64,
    width: f64,
    height: f64,
) -> Result<String, String> {
    let window_id = WINDOW_ID.fetch_add(1, atomic::Ordering::SeqCst);
    let label = format!("webview_{}", window_id);
    let webview_builder =
        tauri::webview::WebviewBuilder::new(label.clone(), WebviewUrl::App(url.parse().unwrap()));
    let _webview = window.add_child(
        webview_builder.auto_resize(),
        LogicalPosition::new(x, y),
        LogicalSize::new(width, height),
    );
    Ok(label)
}

The above code can be allowed normally on Mac, but cannot be allowed on Windows

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
thread 'main' has overflowed its stack
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: terminal
Issue: Dynamic number of rows and columns
Labels: Issue-Feature,Product-Terminal,Area-Windowing

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

I like to use as much space my resolution allows me, and today it is possible to specify the number of rows and columns. This is great!
However, as I switch between different resolutions I need to keep changing this setting.

In my case I use an external monitor with QHD resolution, but I usually take my notebook to partners and use its own monitor, which doesn't have the same resolution. In this case, when I go from a higher to lower resolution, the terminal is so huge, that I can't even find the settings menu.

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->

Allow the users to specify the number of rows and columns as a percent of the resolution, so each time the terminal is opened it will calculate the number of rows and columns based in the current resolution.
Repository: deno
Issue: Analyzable dynamic import created before being imported throws "Module not found"
Labels: bug

**Description:**
I encountered an issue with Deno where a valid TypeScript file cannot be imported despite being confirmed as existing by `Deno.stat`.

**Steps to Reproduce:**
1. Write a simple TypeScript file:
    ```typescript
    await Deno.writeTextFile("./file.ts", "console.log('working');");
    ```
2. Check if the file exists:
    ```typescript
    console.log(await Deno.stat("./file.ts").then(v => true));
    ```
    Output: `true`
3. Attempt to import the file:
    ```typescript
    import("./file.ts");
    ```

**Expected Behavior:**
The module should be imported without errors.

**Actual Behavior:**
An error is thrown:
error: Uncaught (in promise) TypeError: Module not found "file:///code/file.ts".


**Reproduction Repository:**
[Reproduction Example](https://github.com/nestarz/deno-issue-import)
Run it using `deno run -A index.ts`and file.ts must be deleted before re-executing.

Please let me know if any further details are needed to investigate this issue.
Repository: next.js
Issue: Can not export class in action server (only async function)
Labels: examples

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #35~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue May  7 09:00:52 UTC 2
  Available memory (MB): 63931
  Available CPU cores: 12
Binaries:
  Node: 20.13.1
  npm: 10.5.2
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which example does this report relate to?

...

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

I can not export class and use it with server action...

### Expected Behavior

I would like juste use the classe for OOP mvc for my app!

### To Reproduce

**My file form/action.ts**

` "use server"
export class User{
    async changeName(form:FormData) {
      const name = form.get("name")
       console.log(name)
     }
}`

**My page.tsx**

`import styles from "./page.module.css";
import {User} from "./form/action"

export default function Home() {
 const user = new User();
  return (
    <main className={styles.main}>
      <div className={styles.description}>
      
      <form action={user.changeName}>
        <input type="text" name="name"></input>
        <button type="submit">Change name</button>
      </form>
      </div>
    </main>
  );
}`
Repository: rust
Issue: False negative lint for `unused_imports`
Labels: A-lints,A-diagnostics,T-compiler,L-unused_imports

### Code

```Rust
mod a {
  pub(crate) use crate::s;
}
mod b {
  pub mod s {}
}
use self::b::*;
use self::a::s;

fn main() {}
```


### Current output

```Shell
nothing
```


### Desired output

```Shell
Report `use self::a::s` as `unused_import`
```


### Rationale and extra context

If you make a slight modification:

```diff
mod a {
  pub(crate) use crate::s;
}
mod b {
  pub mod s {}
}
use self::b::*;
- use self::a::s;
+ use self::a::s as other_s;

fn main() {}
```

It will report ﻿`use self::a::s as other_s` as an unused import.

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.80.0-nightly (72fdf913c 2024-06-05)
binary: rustc
commit-hash: 72fdf913c53dd0e75313ba83e4aa80df3f6e2871
commit-date: 2024-06-05
host: aarch64-apple-darwin
release: 1.80.0-nightly
LLVM version: 18.1.6
```


### Anything else?

_No response_
Repository: TypeScript
Issue: Template Literal Type JSX children prop issue
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

"2745", "template literal type", "multiple children", "single child"

### 🕗 Version & Regression Information

- This is a crash

### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAKjgQwM5wEoFNkGN4BmUEIcARFDvmQNwBQdBArgHb7AQtwCCYYAFAEo4Abzpw4lGEyhd+4iXAA8APgWLRAeiQAVABbB0Ad2gBrdGjhYAHmCz4sAE0SaAvusVKAwiUgssLDAA6sAwejpY4AA2yDBYADKhWFDIUToAnnZeBlGOlCwACsRgcLg5eQEAvGTIAPp6WFFREGQqSpo+4JwBwaHhkWAxcYlxKWmZWNnAuflFEGBqHhIi2nD6hnAAUgDKABpwMMgA5gDk6Cdl0xUsJ3BgxVa29jDoMBNwJwAGdQAkIqgwKDAFhHVyfOAAHzgnwARrU-gCgSCwbcjAYypIsABHJjASjoEBMKIwYCDLClcr5AA0cBhTHgnCi6RQcFQwKOUXJl1ycCMlnuEAAbsBHE4AHRwfgAJgA7AAWACswgQbiWyk6fh6ITCEWisQSSTGGSylICcwWdQaTQg7Q13UC2v6euGhtSxsmpsKxTUGnaPrggno7jobzscCKWAIwGscEqHzqtyhJzhJ3oofJ5tj0L+Eaj1lcCMB7LB9EYrHYnDgdv8Dr6usG+pGyTdEymMzNxX4IgpV3ycFcAC5RD32ywh5nXMIxBIpDIuEpUGBkCwVCJuddXO1F8uVEG6EA

### 💻 Code

```tsx
function App() {
  return (
    <>
      {/* This works as expected */}
      <ComponentWithTemplateLiteralTypeChildrenProp children="a_hello"></ComponentWithTemplateLiteralTypeChildrenProp>

      {/* This JSX tag's 'children' prop expects type '`a_${string}` | `b_${string}`' which requires multiple children, but only a single child was provided. (2745) */}
      <ComponentWithTemplateLiteralTypeChildrenProp>a_hello</ComponentWithTemplateLiteralTypeChildrenProp>
    </>
  );
}

type Prefix = 'a_' | 'b_';
type Prop = `${Prefix}${string}`;

function ComponentWithTemplateLiteralTypeChildrenProp({ children }: { children: Prop }) {
  return <span>{children}</span>;
}

```


### 🙁 Actual behavior

A Template Literal Type "children" prop does not allow the prop to be passed between the open/close tags. Passing the value via a prop works.

### 🙂 Expected behavior

It should be possible to pass a Template Literal Type "children" prop in between the open/close tags. Not only via a named prop.

### Additional information about the issue

_No response_
Repository: flutter
Issue: Broke display for user on Linux using OpenGL ES only: `Could not open X display`
Labels: c: crash,e: device-specific,engine,platform-linux,P1,:hourglass_flowing_sand:,team-linux,triaged-linux

### Steps to reproduce

Launch a Linux desktop flutter 3.22 app on hardware supporting only OpenGL ES.

This seems to be because of PR:
https://github.com/flutter/engine/pull/50754/commits/5d7ca6edf1cac4d65f6e8eedfaa8972cbb71ad21

### Expected results

The app start

### Actual results

The app crash without opening a window

### Code sample

<details open><summary>Code sample</summary>
A simple flutter create will do
</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

![image](https://github.com/flutter/flutter/assets/1233974/4311da3b-ebb7-4a4f-9a5c-54160f7ff1d4)

</details>


### Logs

<details open><summary>Logs</summary>

See log screenshot above.

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

This is run on our build machine

```console
flutter doctor -v
[✓] Flutter (Channel stable, 3.22.2, on Ubuntu 22.04.4 LTS 6.1.72-96.166.amzn2023.aarch64, locale en_US)
    • Flutter version 3.22.2 on channel stable at /flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 761747bfc5 (22 hours ago), 2024-06-05 22:15:13 +0200
    • Engine revision edd8546116
    • Dart version 3.4.3
    • DevTools version 2.34.3
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.
[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Linux toolchain - develop for Linux desktop
    • Ubuntu clang version 14.0.0-1ubuntu1.1
    • cmake version 3.22.1
    • ninja version 1.10.1
    • pkg-config version 0.29.2
[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
[✓] Connected device (1 available)
    • Linux (desktop) • linux • linux-arm64 • Ubuntu 22.04.4 LTS 6.1.72-96.166.amzn2023.aarch64
[✓] Network resources
    • All expected network resources are available.
! Doctor found issues in 3 categories.
```

</details>
Repository: vscode
Issue: MSYS/Cygwin paths are not supported as terminal links
Labels: feature-request,windows,terminal-links

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.90.0
- OS Version: Windows 10

Steps to Reproduce:

When I compile with MSYS on the terminal, paths in warnings/errors are shown in MSYS/Cygwin style: `[/cygdrive]/d/Projects/test/foo.cpp:123`. Ctrl-clicking it opens the Quick open edit with the path, then I have to edit it, remove the leading slash, add a colon after the drive letter and press Enter.

Created PR #214435 to handle that, but it was rejected because the change was in a central component (path.ts), and was too risky.
Repository: godot
Issue: Keyboard layouts don't immediately work on wayland
Labels: bug,platform:linuxbsd,topic:porting,topic:input

### Tested versions

- Reproducible on v4.3.beta1.official [a4f2ea91a], v4.3.dev3.official [36e943b6b] and v4.3.dev6.official [64520fe67]

### System information

Godot v4.3.dev6 - NixOS #1-NixOS SMP PREEMPT_DYNAMIC Sat May 25 14:22:56 UTC 2024 - Wayland - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (nvidia; 555.42.02) - 12th Gen Intel(R) Core(TM) i5-12400F (12 Threads)

### Issue description

Switching to another keyboard layout does not immediately change what characters are typed.


https://github.com/godotengine/godot/assets/80159210/138d2a16-248b-4e2b-b694-79813f340aba

^
Buttons shown on bottom are raw keypresses, unaffected by layout



### Steps to reproduce

- Type a letter in first layout (i.e qwerty)
- switch to a second layout
- Try to type, it still will type like first layout is selected

### Minimal reproduction project (MRP)

this bug is reproducible in the project manager
Repository: next.js
Issue: styled-components don't rehyrdate properly in React Server Components
Labels: linear: next

### Link to the code that reproduces this issue

https://github.com/blairmcalpine/styled-components-repro

### To Reproduce

1. Start the application (npm run dev)
2. Visit localhost:3000 and click the "Green (click to switch)" element. You'll see that the color doesn't change, despite the [code](https://github.com/blairmcalpine/styled-components-repro/blob/main/src/app/client.page.tsx) properly swapping to a blue style. This is because the blue style is overridden with another green style:
<img width="320" alt="image" src="https://github.com/vercel/next.js/assets/97198784/95f002a7-f716-414b-8e12-f46bb6e05739">

This second green style is the result of two conflicting <style> tags generated by styled-components. One is generated on the initial doc request, and the second (and third) are adding during hydration - see the style tags marked with `data-styled-version="6.1.11"`:

<img width="606" alt="image" src="https://github.com/vercel/next.js/assets/97198784/07e7e0db-0965-44fc-b339-875e07abe3c9">

This can lead to completely incorrect styles of the page, if the second style tag contains different styles than the one in the head. While this issue is primarily with [React Streaming and styled-components](https://github.com/styled-components/styled-components/issues/4326), we want to raise awareness here as NextJS officially "supports" styled-components, and the supported implementation doesn't work properly.

### Current vs. Expected behavior

Expected Behaviour:
I expect styled-components <style> tags that are added later as a part of React Server Component hydration to be properly consolidated with the existing <style> tag.

Current Behaviour:
The <style> tag that is added to the DOM as a part of React Server Component hydration isn't combined with the <style> tag in the head, resulting in conflicting styles. Note that this is using the code from [the docs](https://nextjs.org/docs/app/building-your-application/styling/css-in-js#styled-components). 

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.5.0: Wed May  1 20:12:58 PDT 2024; root:xnu-10063.121.3~5/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.12.0
  npm: 10.5.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 14.2.3
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Developer Experience, Documentation

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Other (Deployed)

### Additional context

I have created a related issue with styled-components [here](https://github.com/styled-components/styled-components/issues/4326).