sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Certain elements disappear while screen recording
Labels: bug,topic:rendering,needs testing,topic:2d

### Godot version

3.5 rc2

### System information

Windows 11 Pro GLES3

### Issue description

I wanted to record a video of my project, except that if without recording everything is fine, then when recording the screen - hand and eye characters disappear and appear! I do not know how long this error exists, but I found it only now!
![remains](https://user-images.githubusercontent.com/91805483/170833596-11f6cd42-ae03-4ad9-9fc2-851119ae51ea.gif)

### Steps to reproduce

[Uploading Alex.zip…]()


### Minimal reproduction project

[Alex.zip](https://github.com/godotengine/godot/files/8791460/Alex.zip)
Repository: godot
Issue: Vulkan: SDFGI Artifacts due to sky sampling when Read Sky Light is enabled
Labels: bug,topic:rendering,topic:3d

### Godot version

4.0.alpha8

### System information

Windows 10, Vulkan Clustered, RTX 3060Ti, 511.79

### Issue description

Cross shaped and world normal aligned artifacts appear on objects when enabling SDFGI.
It seems like SDFGI is sampling indirect lighting from incorrect directions.
The scene in the screenshots only have a directional light, a WorldEnvironment node with a sky background and SDFGI enabled, and a sphere with a default white material.
The sphere's global illumination mode is "disabled".

SDFGI On
![SDFGI On](https://user-images.githubusercontent.com/16312261/170833590-3bd54295-5088-4bd1-9d5a-e21612791708.png)
SDFGI Off
![SDFGI Off](https://user-images.githubusercontent.com/16312261/170833564-65bdc15f-20db-4ba7-9304-370da2d2db85.png)


### Steps to reproduce

Add any object to a scene and enable SDFGI in the WorldEnvironment.
Preferrably a white and smooth object, so that the artifacts are easier to spot.

### Minimal reproduction project

[SDFGI.zip](https://github.com/godotengine/godot/files/8791455/SDFGI.zip)
Repository: react
Issue: Bug: Potential infinite loop with Suspense (and Error boundaries not triggered)
Labels: Type: Bug,Status: Unconfirmed

React version: latest stable (and experimental)

## Steps To Reproduce
1. Checkout the following repo: https://github.com/bvaughn/react-suspense-error-boundary-bug
2. Run `npm install && npm run dev`
3. Load the browser and observe an infinite loop of components re-rendering (rather than the error boundary catching the error).

I've added a lot of inline comments about things that are necessary to trigger this bug in this file:
https://github.com/bvaughn/react-suspense-error-boundary-bug/blob/main/pages/index.js

Note that I was unable to reproduce this bug with Code Sandbox or Create React App. It only reproduces when running with Next JS (and only in DEV mode). Maybe it has something to do with Next's custom error logging behavior? Unfortunately there's no way to disable this (see [vercel/next.js/discussions/13387](https://github.com/vercel/next.js/discussions/13387)) so I'm not sure.
Repository: flutter
Issue: [ios][production]: App crashes with `Fatal Exception: std::bad_alloc std::bad_alloc`
Labels: c: crash,platform-ios,a: production,P2,c: fatal crash,needs repro info,team-ios,triaged-ios

If it is necessary, I use some cool animations and other scroll based stuff. I have not expertise to resolve or suggest solution of this problem, please help.
<img width="1029" alt="Screenshot 2022-05-28 at 21 59 29" src="https://user-images.githubusercontent.com/42138594/170841195-fbab95ef-58c0-4473-a59a-10f9f4cd0cc2.png">
<img width="683" alt="Screenshot 2022-05-28 at 21 59 57" src="https://user-images.githubusercontent.com/42138594/170841198-5bc15215-a928-4167-b0ea-9533ca25e17d.png">
Repository: PowerToys
Issue: Color Picker edit with sliders in any color format
Labels: Idea-Enhancement,Product-Color Picker

### Description of the new feature / enhancement

Currently, when I click on the selected color, I can edit the current color in three ways:

1. HSV mode, using sliders for each channel;
2. RBG mode, textually editing each channel;
3. HEX mode, textually editing the entire string.

![colorpicker_current](https://user-images.githubusercontent.com/9002039/170843502-24e5d514-78ee-4ae8-baa7-2d1570048d28.png)

I would love to be able to modify the color using sliders in CIELAB -- but why not in any color format?

Illustration of desired functionality:

![colorpicker_proposed](https://user-images.githubusercontent.com/9002039/170843506-69dd46e8-87b9-4871-8329-34c5e5a1f2f6.png)

### Scenario when this would be used?

Often when designing for the frontend, I find myself going to websites like Colorizer.org to tweak colors in different color formats. Such tools are often outdated in regards to UI, and frankly I feel that an internet connection shouldn't be needed for that. With PowerToys Color Picker, I feel that such functionality is just around the corner and maybe wouldn't be too difficult to implement.

### Supporting information

Another thing that struck me as odd from the first time I used PowerToys Color Picker was: default color format is HSL (other than HEX/RGB), but the color slider uses HSV?

I find it only natural that the sliders be customizable as far as color formats go.

Thanks!
Repository: vscode
Issue: Deletion marker too little, difficult to select
Labels: git,editor-contrib,under-discussion


Issue Type: <b>Feature Request</b>

Dear developers,

I love the markers that locate inseritons, changes and deletions done in the code, especially the chance to click on these markers to discard.
While clicking green insertions and yellow changes is just perfect, it's very tricky to precisely click on the little red triangle of deletions markers!
So my advice and kindly request, is simple to make it easier to click, with a bigger triangle or another solutions that would come to your minds!

Keep up with the good work  <3
Thank you

VS Code version: Code 1.67.2 (c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5, 2022-05-17T18:20:57.384Z)
OS version: Darwin x64 17.7.0
Restricted Mode: No


<!-- generated by issue reporter -->
Repository: create-react-app
Issue: How to create an app with react 17.x version instead of the latest react 18?
Labels: needs triage

Recently I have been bothered by keeping changing the version of react and react-dom into version 17.x after using the npx create-react-app command, coz the created project will use react 18 by default which is not what I am looking for. Is there any way the users can choose React version before initing project?
Repository: rust
Issue: `x build src/tools/cargo` builds the compiler
Labels: T-bootstrap,A-contributor-roadblock

Cargo builds on stable. Building the compiler seems wrong.

Changing `ToolRustc` to `ToolBootstrap` avoids building the compiler, but gives an error when using `--stage 1` or `--stage 2` with cargo. I think in some sense that's right? Cargo should be the same regardless of the stage you use to build it.

<details><summary>ToolRustc -> ToolBootstrap</summary>

```diff
diff --git a/src/bootstrap/test.rs b/src/bootstrap/test.rs
index bc851568f89..a5cd6315b1a 100644
--- a/src/bootstrap/test.rs
+++ b/src/bootstrap/test.rs
@@ -273,7 +273,7 @@ fn run(self, builder: &Builder<'_>) {
         let mut cargo = tool::prepare_tool_cargo(
             builder,
             compiler,
-            Mode::ToolRustc,
+            Mode::ToolBootstrap,
             self.host,
             "test",
             "src/tools/cargo",
diff --git a/src/bootstrap/tool.rs b/src/bootstrap/tool.rs
index 3b30e6de12a..d775e3b4e55 100644
--- a/src/bootstrap/tool.rs
+++ b/src/bootstrap/tool.rs
@@ -609,7 +609,7 @@ fn run(self, builder: &Builder<'_>) -> PathBuf {
                 compiler: self.compiler,
                 target: self.target,
                 tool: "cargo",
-                mode: Mode::ToolRustc,
+                mode: Mode::ToolBootstrap,
                 path: "src/tools/cargo",
                 is_optional_tool: false,
                 source_type: SourceType::Submodule,
@@ -624,7 +624,7 @@ fn run(self, builder: &Builder<'_>) -> PathBuf {
                 compiler: self.compiler,
                 target: self.target,
                 tool: name,
-                mode: Mode::ToolRustc,
+                mode: Mode::ToolBootstrap,
                 path,
                 is_optional_tool: true,
                 source_type: SourceType::Submodule,
```

</details>

cc @Mark-Simulacrum: I wonder if we should make this change and give a warning when using `--stage` with cargo.

I found this in https://github.com/rust-lang/rust/pull/97268.

@rustbot label +A-rustbuild +A-contributor-roadblock
Repository: terminal
Issue: Can't run Windows Terminal without Administrator
Labels: Needs-Repro,Issue-Bug,Product-Terminal,Needs-Tag-Fix,Culprit-Centennial

### Windows Terminal version

1.13.11431.0

### Windows build number

10.0.19041.572

Yes, this has actually downgraded since my last bug report. Blame the fact that I had limited download options.

### Other Software

_No response_

### Steps to reproduce

See https://github.com/microsoft/terminal/issues/13099#issuecomment-1138459416 and the comments leading up to it.

1. I was given a command that completely ruined every app on my system.
2. I had to do an in-place upgrade to fix the issue.
3. Windows Terminal, through any amount of reinstalls, now cannot run without Administrator.

### Expected Behavior

_No response_

### Actual Behavior

Windows Terminal, through any amount of reinstalls, now cannot run without Administrator. I also cannot double-click the msixbundle to install (I get some permission error), but `Add-AppxPackage` works.

The `wt` command is not found in a non-Administrator Command Prompt, but it is found in an Administrator Command Prompt.

No Start Menu entries work for any part of Windows Terminal, not even the shortcuts, *unless* run as Administrator.
Repository: godot
Issue: Control size is updated after viewport emit changed_size signal.
Labels: bug,topic:porting

### Godot version

3.4

### System information

Windows 10, Geforce GTX 1650, GLES3

### Issue description

I made a script that connect the signal `size_changed` from the root viewport, obtained with `get_viewport()`, when resizing the window it work correctly but if i toggle fullscreen each time the viewport size is the previus before the fullscreen.

![sample](https://user-images.githubusercontent.com/89723855/170856226-7162dce3-09a6-4938-bd11-6d0a4f9f422c.png)



### Steps to reproduce

- make a new scene and connect the signal to a script, make the method print the size of the viewport.
- toggle fullscreen

### Minimal reproduction project

_No response_
Repository: ant-design
Issue: Badge display error when used in menu as part of icon
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-uvzjkr?file=/index.js)

### Steps to reproduce

Use `<Badge dot><AppstoreAddOutlined /></Badge>` as the `Icon` for the `ItemType`.
Then put the `<Menu theme="dark">` inside a `<Sider>`. 
1. (For the position of the badge) Toggle the sider collasped and expanded.
2. (For the color of the icon) Put menu in dark theme, select between the item and others.

### What is expected?

1. Badge display at a fixed location no matter the whether the Sider collasped or not.
2. The color of the icon change correctlly.

### What is actually happening?

1. Badge display at a different location when collasped and expanded.
2. The color of the icon become transparent when not selected. (in dark theme)

| Environment | Info |
| --- | --- |
| antd | 4.20.5 |
| React | ^18.1.0 |
| System | MacOS 12.3.1 (21E258) |
| Browser | Chrome 101.0.4951.64 (Official Build) (arm64)  |

---
I'm not sure if I'm using antd in the right way. Are there any other elegant way to add a badge to the menu's icon?

<img width="337" alt="image" src="https://user-images.githubusercontent.com/15214491/170856326-438bdc10-3a6a-4b65-a502-cb1021f7ff23.png">

<img width="311" alt="image" src="https://user-images.githubusercontent.com/15214491/170856358-ad52fb99-e4da-45ca-a706-76b85698db7f.png">


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Generic associated types break lifetime checks
Labels: C-bug,T-types,A-GATs

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

Here's some code with generic associated types and `impl Trait`:
```rust
#![feature(generic_associated_types)]
use std::future::{Future, ready, Ready};

pub trait Example {
    type Value<'a>: Future<Output = &'a str> where Self: 'a;
    fn example(&mut self) -> Self::Value<'_>;
}

pub struct ExImpl<'a>(&'a str);

impl Example for ExImpl<'_> {
    type Value<'a> = Ready<&'a str> where Self: 'a;
    fn example(&mut self) -> Self::Value<'_> {
        ready(self.0)
    }
}

async fn callee(mut ex: impl Example) {
    // Note that if you don't use a separate function, no errors appear
    dbg!(ex.example().await);
}

#[tokio::main]
async fn main() {
    tokio::spawn(async move {
        let ex = ExImpl("hello");
        callee(ex).await;
    });
}
```
[Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=4ed2c005596454b3692e6fc224f4d443)

Expected: `ex.example().await = "hello"`

Current behavior:
```
Compiling playground v0.0.1 (/playground)
error[[E0477]]: the type `ExImpl<'_>` does not fulfill the required lifetime
  --> src/main.rs:24:5
   |
24 |     tokio::spawn(async move {
   |     ^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0477`.
error: could not compile `playground` due to previous error
```

Clearly `ExImpl("hello")` has a static lifetime and yet borrowck still complains that the lifetime isn't static. Interestingly, if we inline the contents of `callee` (i.e. never write `impl Example`) there are no issues.

This is also a diagnostic issue: not only is the error in the wrong place, it doesn't provide any suggestions to fix and doesn't point out what lifetime `ex` actually needs.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.63.0-nightly (ebbcbfc23 2022-05-27)
binary: rustc
commit-hash: ebbcbfc236ced21d5e6a92269edb704692ff26b8
commit-date: 2022-05-27
host: x86_64-unknown-linux-gnu
release: 1.63.0-nightly
LLVM version: 14.0.4
```
Repository: PowerToys
Issue: The "Find my mouse" function should not be triggered when the mouse is pressed
Labels: Issue-Bug,Idea-Enhancement,Product-Mouse Utilities

### Description of the new feature / enhancement

Do not trigger the "Find my mouse" function when the mouse is pressed or add the option to block it.

### Scenario when this would be used?

I have set the "find my mouse" function to be triggered by "wiggling the mouse", but it is often triggered accidentally when I am dragging a window or doing something more complex.
I don't think people will find their mouse when it's pressed, or there could be an option to block it.

### Supporting information

My English is not very good so I have used machine translation for the description, hopefully without too much semantic bias.
Repository: create-react-app
Issue: Proposal: react-scripts to support react-native-web out of the box
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->
Hello.

I'm a React Native developer and I've been working with React Native on web as well in my spare time. I constantly had issues setting up [react-native-web](https://github.com/necolas/react-native-web). I managed to use react-scripts to avoid messing with configurations beyond my experience and it also makes the project cleaner. But that was not enough, and I had to constantly find solutions to overwrite webpack config using [CRACO](https://github.com/gsoft-inc/craco) or [react-app-rewired](https://github.com/timarney/react-app-rewired)

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

I would **love** if react-scripts would support react-native-web out of the box. 
### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

I'm author of https://github.com/criszz77/luna - a template that enables React Native for the web platform using react-scripts.  I had to switch from react-app-rewired to CRACO and back, depending on the versions of react-scripts.

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

Thank you all for your great work! 🚀
Repository: tauri
Issue: [bug] Application flickers when resizing in WM
Labels: type: bug,status: upstream,platform: Linux

### Describe the bug

Application flickers when resizing when using window manager (I haven't checked how on DE)

[video](https://imgur.com/qpnckA3)

*Sorry about the quality, scaling and everything*

### Reproduction

1. run any tauri app on window manager (shown on bspwm)
2. resize app

### Expected behavior

_No response_

### Platform and versions

```shell
> tauri-app@0.1.0 tauri
> tauri "info"


Environment
  › OS: Linux Rolling Release X64
  › Node.js: 18.2.0
  › npm: 8.5.5
  › pnpm: 7.1.7
  › yarn: 1.22.19
  › rustup: 1.24.3
  › rustc: 1.61.0
  › cargo: 1.61.0
  › Rust toolchain: stable-x86_64-unknown-linux-gnu 

Packages
  › @tauri-apps/cli [NPM]: 1.0.0-rc.13
  › @tauri-apps/api [NPM]: 1.0.0-rc.6
  › tauri [RUST]: 1.0.0-rc.14,
  › tauri-build [RUST]: 1.0.0-rc.12,
  › tao [RUST]: 0.9.1,
  › wry [RUST]: 0.17.0,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../build
  › devPath: http://localhost:3000/
  › framework: React

App directory structure
  ├─ node_modules
  ├─ public
  ├─ src
  ├─ .git
  ├─ src-tauri
  └─ build
```
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: TypeScript
Issue: Inferred return type of function is incorrect when one of the return types is a conditional type
Labels: Bug

# Bug Report

### 🔎 Search Terms

ignored return type generic conditional 

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `return`

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=3.3.3#code/C4TwDgpgBAYg9nAPAFQHxQLxQN4CgoFTAQC2YANgIbEBcUyA3LgL666iRQBClATiuizIoEAB7EAdgBMAzlABGCchEoSoAflgJEEgK4l5EXujrwkM4LwCWEgOaom7cNB4AvFCPERpcxXGWqgtx8Ap6SslA2AGZGUACSEjG8vBBSZviEmglJKWkIYd4RZoiqIKgZhJlQAEQgEDLVFZVQdBIQAG5GTa0dRo5RuhIAxsBWcGrEFh5i4b5KKhKoABRwYMAydMgAlDhNQ+MWUKKYUFGU5DIQjpUA9DfxUVAgcLpQ+yQk3sBEABbQ5DZoIZyHAAO4AGl+VjkA2Go3GUAsfHWTTuUBSwF0vAkNlswXcaCglDkYkgI1SkNBPysQx+kQmWLUJEoAGt6lAAAYpGS6cjADmo+4-SidX7QDjQWr1aoAOkF9D+kUeSOInwk32BYMRPxe5CkUGFookcEiZEoIyIJuAf3lGMZRGcUDgj2t0FhIzGEkhcFdvF+qiJUikuM5AB8oHpyOQOXLbvcAIJRYh+87kSHPV5DANROC8IbixV27EOzjOsWnQYe8by4AmwyctyhcOR6NE6SRb4WKxRqCg3MsmGA2OEKyPJaiHZFtQt66EKc4ZhEuSNtBMVi4fYSQ7c3nfLCTYBLSy6CBbBhAA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type Foo<T> = {
    template: T;
}

type Bar<T> = T extends boolean ? Foo<number> : Foo<string>;

type Baz<T extends boolean> = Bar<T> extends infer InferredFoo
    ? InferredFoo extends Foo<any>
        ? "yes"
        : never
    : never;

function test<T extends boolean>(opts: T) {
    const x = false;

    // If you comment the line below, this function starts
    // returning Baz<T> as expected, which in turn makes `result`
    // have the type "yes".
    // The if statement below should have no impact to the
    // return type of the function, other than adding `| null`.
    // After all, you can force the return type of the function
    // to be `Baz<T> | null` and it still works fine.
    if (x) return null;

    return {} as Baz<T>;
}

const result = test(true);
```

### 🙁 Actual behavior

`result` has type `null`

### 🙂 Expected behavior

`result` should have type `null | "yes"`
Repository: TypeScript
Issue: Type constraint not checked when a type parameter from a function is passed to a mapped type
Labels: Bug,Cursed?

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

mapped types generic type constraint lost when passed from function

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about generics

### ⏯ Playground Link
<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/LAKALgngDgpgBAZQPYFsYFkCGVYBMAq0MAPPnDAB5gwB2uAznAEowDGSATrsfWBwJY0A5gBo4mGhAB8UuAF44Ab1Bw4AbQDScQXADWMCEgBmcfAF0AXKc1nQAX1CgjAVxqsw-JDTgoIAMVdWUnIqWgZEVAxsPEJYUhkACl8AQQ4hK3wASmUQe0cQdhpeOAorZDQsHBgCIh4%20QSFZBUUjJCQrAHIAI0wODrsAbjgAemHTAAt%20RhgODk4fTH1GeloVgDo4AANeAWFNuEhYOChezDRqDjgAN08AG0xqRjBx%20BZ2Ljrd0XFJWUKdzCCMD5XwBNyfBpSBIdF4QDqZIYjMYAdXGEG0jG29T2cBoSDAcFYL1Y%20lw4iEgKKBOe8E2b043B2DREEmk%200KYABQO03meU0JXmoVDgAH4RfkJbkQEA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type SomeMappedType<T extends Record<string, any>> = {
  [K in keyof T]: T[K]
}

function myFunc<T extends SomeMappedType<T>>(myArg: T){

}

const y: SomeMappedType<object> = {foo: 'bar'}; // okay.  makes sense.

//@ts-expect-error
const x: SomeMappedType<string> = {foo: 'bar'}; // This error makes sense. `string` type parameter violates the Record<string, any> constraint

myFunc<string>('hey');  // Why is `string` not checked against the `Record<string, any>` constraint in this context ??

```

### 🙁 Actual behavior

No error when I pass in `string` as a type parameter to myFunc i.e `myFunc<string>`.

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->

Typescript errors and warns me that `string` does not satisfy the constraint of `Record<string, any>` when I attempt to make the following function call: `myFunc<string>('hey')`;