sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: unpretty=hir,typed output confusing for `futures::select!` macro
Labels: T-compiler,A-HIR,C-bug,requires-nightly

<!--
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.
-->

I tried this code:

```rust
#![feature(lang_items)]
#![feature(stmt_expr_attributes)]
#![allow(dead_code)]

use futures::FutureExt;

async fn other() { }

async fn async_main_exansion_is_strange() { futures::select! { _ignored = other().fuse() => { } } }

fn main() { }
```

with this `Cargo.toml`:

```toml
[package]
name = "confusing"
version = "0.1.0"
edition = "2021"

[dependencies]
futures = "0.3.21"

[workspace]
```

and I built it like this:

```
cargo +nightly build && touch src/main.rs && cargo +nightly rustc -- -Zunpretty=hir,typed > expanded.rs
```

I expected to see this happen: I had hoped the output `expanded.rs` would resemble legible Rust code

Instead, this happened: The output in `expanded.rs` included portions like this:

```rust
(match ((#[lang = "into_future"] as
                    fn(Yield) -> <Yield as std::future::IntoFuture>::IntoFuture {<Yield as std::future::IntoFuture>::into_future})(((...
```

In other words, its got this weird `#[attribute] as Type` construction that is not valid Rust.

The -Zunpretty=hir output does not share this problem, it looks something like:

```rust
match #[lang = "into_future"](__futures_crate::future::poll_fn(__poll_fn))
```

### 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.62.0-nightly (a5ad0d29a 2022-05-12)
binary: rustc
commit-hash: a5ad0d29a401007b51715852cc702e441ac2248c
commit-date: 2022-05-12
host: x86_64-unknown-linux-gnu
release: 1.62.0-nightly
LLVM version: 14.0.1
```
Repository: rust
Issue: FakeRead is semantically meaningful to miri (but gets optimized away)
Labels: T-compiler,C-bug,A-miri,A-mir-opt,T-opsem

Given this sample program:

```rust
#![feature(generators)]

fn main() {
    let x = Some(22);
    let _a = match x {
        Some(y) if foo() => (),
        _ => (),
    };
}

fn foo() -> bool { 
    true
}
```

the desugaring of the match intentionally adds some borrows when executing the guard:

```
    bb3: {
        StorageLive(_6);                 // scope 1 at foo.rs:6:14: 6:15
        _6 = &((_1 as Some).0: i32);     // scope 1 at foo.rs:6:14: 6:15
        _4 = &shallow _1;                // scope 1 at foo.rs:5:20: 5:21
        StorageLive(_7);                 // scope 1 at foo.rs:6:20: 6:25
        _7 = foo() -> [return: bb4, unwind: bb8]; // scope 1 at foo.rs:6:20: 6:25
                                         // mir::Constant
                                         // + span: foo.rs:6:20: 6:23
                                         // + literal: Const { ty: fn() -> bool {foo}, val: Value(Scalar(<ZST>)) }
    }

    bb4: {
        switchInt(move _7) -> [false: bb6, otherwise: bb5]; // scope 1 at foo.rs:6:20: 6:25
    }

    bb5: {
        StorageDead(_7);                 // scope 1 at foo.rs:6:24: 6:25
        FakeRead(ForMatchGuard, _4);     // scope 1 at foo.rs:6:24: 6:25
        FakeRead(ForGuardBinding, _6);   // scope 1 at foo.rs:6:24: 6:25
```

The purposeof the `FakeRead` of `_4`and `_6` is to ensure that the discriminant does not change while the guard executes -- i.e., that the guard doesn't (via unsafe code, say) mutate `x` to be `None`. But after optimizations those FakeReads are removed:

```

    bb0: {
        Deinit(_1);                      // scope 0 at foo.rs:4:13: 4:21
        ((_1 as Some).0: i32) = const 22_i32; // scope 0 at foo.rs:4:13: 4:21
        discriminant(_1) = 1;            // scope 0 at foo.rs:4:13: 4:21
        _4 = &((_1 as Some).0: i32);     // scope 1 at foo.rs:6:14: 6:15
        _5 = foo() -> bb1;               // scope 1 at foo.rs:6:20: 6:25
                                         // mir::Constant
                                         // + span: foo.rs:6:20: 6:23
                                         // + literal: Const { ty: fn() -> bool {foo}, val: Value(Scalar(<ZST>)) }
    }

    bb1: {
        switchInt(move _5) -> [false: bb3, otherwise: bb2]; // scope 1 at foo.rs:6:20: 6:25
    }
```

this means that `foo()` could trigger writes without causing UB. This seems bad!

UPDATE: This is overstating the case. It's ok for us to optimize FakeRead away, but tools like miri or some future sanitizers would still want to see them (for the reasons give above).
Repository: vscode
Issue: The "$tsc-webpack-watch" from "amodio.tsl-problem-matcher" problem matcher does match, but doesn't mark the task as failed
Labels: bug,tasks

<!-- ⚠️⚠️ 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?: 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.67.1
- OS Version: macOS 12.3.1

Steps to Reproduce:

1. Generate a new extension using `yo code`, that uses webpack, and open it in VS Code.
2. Install the recommended extensions.
4. Introduce an error into `extesnion.ts` and close it.
4. Run the `npm watch` task.
5. Split the terminal that runs the task.
6. Notice that the task is marked as successful rather than failed (Checkmark instead of circled red cross).

The problem matcher from does seem to be defined correctly by testing its regex manually and the fact that it does match the start and end of webpack compilation and shows the error in the problems panel.

<img width="1390" alt="image" src="https://user-images.githubusercontent.com/24731903/168699567-61f61c36-6495-4284-9b6f-e911e821b114.png">

(P.S. Is there any tool in VS Code to make it easier to debug problem matchers?)
Repository: pytorch
Issue: PyTorch fails to build on gcc 12 due to gloo
Labels: module: build,triaged,module: third_party

### 🐛 Describe the bug

```
/home/gaoxiang/pytorch-nvfuser-master/third_party/gloo/gloo/transport/tcp/device.cc:151:39: error: implicit instantiation of undefined template 'std::array<char, 64>'
      std::array<char, HOST_NAME_MAX> hostname;
```

Adding `#include <array>` to that file should fix the problem. But looks like the `gloo` submodule haven't been updated for long time, so I don't know how this issue should be fixed.

### Versions

```
Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: Arch Linux (x86_64)
GCC version: (GCC) 12.1.0
Clang version: 13.0.1
CMake version: version 3.23.1
Libc version: glibc-2.35

Python version: 3.10.4 (main, Mar 23 2022, 23:05:40) [GCC 11.2.0] (64-bit runtime)
Python platform: Linux-5.17.6-arch1-1-x86_64-with-glibc2.35
Is CUDA available: N/A
CUDA runtime version: 11.6.124
GPU models and configuration: 
GPU 0: NVIDIA GeForce RTX 3090
GPU 1: NVIDIA GeForce RTX 2080 Ti

Nvidia driver version: 510.68.02
cuDNN version: Probably one of the following:
/usr/lib/libcudnn.so.8.4.0
/usr/lib/libcudnn_adv_infer.so.8.4.0
/usr/lib/libcudnn_adv_train.so.8.4.0
/usr/lib/libcudnn_cnn_infer.so.8.4.0
/usr/lib/libcudnn_cnn_train.so.8.4.0
/usr/lib/libcudnn_ops_infer.so.8.4.0
/usr/lib/libcudnn_ops_train.so.8.4.0
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

Versions of relevant libraries:
[pip3] numpy==1.22.3
[pip3] torch-ucc==1.0.0
[pip3] torchani==2.2
[pip3] torchvision==0.2.2.post3
[conda] Could not collect

```

cc @malfet @seemethere
Repository: TypeScript
Issue: Better error message for optional chained properties on never, null, or undefined
Labels: Suggestion,Experience Enhancement

# Suggestion

## 🔍 Search Terms

optional chaining null undefined property never

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

If a value is type `never`, `null`, or `undefined`, accessing a property on it using optional chaining gives a type error like:

```ts
declare const missing: undefined;

missing?.member;
//       ~~~~~~
// Error: Property 'member' does not exist on type 'never'.
```

Note that the error message for regular property lookups on `null` and `undefined` (though not `never`) is already specialized:

```ts
declare const missing: undefined;

missing.member; /*
~~~~~~~ */
// Error: Object is possibly 'undefined'. 
```

## 📃 Motivating Example

That error message is accurate but not precise. Users sometimes accidentally try to optional chain on properties of a value narrowed to a falsy type. Seeing something about the `never` type can be confusing. 

A more clear, precise error message might say something like...

```ts
declare const missing: undefined;

missing?.member;
//       ~~~~~~
// Error: 'missing' is type 'undefined', which does not have any properties.
```

Maybe there's a standard phrasing that could apply to both traditional property accesses and optional chained one?

## 💻 Use Cases

We can infer from the occasional related issues -#48280, #41766- that it's not always clear why the optional chained property isn't allowed. My original context is [this Playground example demonstrating accidental narrowing in the falsy case of a type predicate](https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABDAzgGQQcwMpQE4xiYAUhADiFAFyIr6GaIA+i4AJgKbCEdsCUNcpWQpa9IogDeAKERzEeDlBB4kAQjWkwFKIgBke5NsoA6ADYciUABaIAfAF5EAdj4BuaQF9p00JFgIiADucHgA1gDqMDYAKhwAHlDEUAnUYgQSLOxcPPxSsvIwwIik6Fi4GSQpiXx8+fINiAD0TYgxAJ5kHIhwxdVpdJUFjYgQCChwFuZwJABEGBL9VLMANIj95paYNu7DiJ6IHGYo3TIjci1tnd2966k02dxgvHsNY2ATU2YzxLPY1qFdEtVndEgB+TZWay7c7NVoAP0RSNe8kuAFE8HhQjQAApYrp4KDtRAAcgsUJJiDYcA4ojAcF0CVQukCRK6pOeADcOHgSSY9t5PEA).

Note: I am not proposing the type checker change its core behavior in any way. This just proposed having a specialized error message for the cases of `never`, `null`, and `undefined`.
Repository: flutter
Issue: The UI fails to response after the screen is locked for a while
Labels: engine,platform-windows,a: desktop,P2,team-windows,triaged-windows

I write a RTC application in windows using flutter platform channel, the application's implementation details are as follows

1、in dart side, it uses [Texture class ](https://api.flutter.dev/flutter/widgets/Texture-class.html) to render realtime video.

2、in C++ side, it uses flutter::PixelBufferTexture. When realtime video frame is arrived, it invokes TextureRegistrar::MarkTextureFrameAvailable to notify flutter engine to render.

During testing, I find a problem that the UI fails to response after the screen is locked and the camera is left open for a while, for example when button pressed, the button's onPressed function is not executed. The longer the screen is locked, the more serious the problem is and the more memory the program uses. After some time, the UI recovers to response.
Repository: flutter
Issue: Refactor RenderObject/PaintingContext to allow for more asserts/restrictions around errors/inefficiencies
Labels: c: new feature,framework,P3,team-framework,triaged-framework

Today, [RenderObject] is a relatively challenging protocol to implement, and it is relatively easy to make multiple mistakes that cannot be statically or dynamcially detected by the framework.

For example, there's currently no good way to validate the implementation of `describeApproximatePaintClip` to make sure that it does not provide a clip for a child that is painted with `clipBehavior = Clip.none`. Another example is that there is no way to make sure it disposes of its layers if it doesn't use the `layer` property, and that in some cases it is expected to not touch the `layer` (which is used by the framework to make it a repaint boundary). Yet another example are methods like the newly added `paintsChild` compared to `applyPaintTransform`.

RenderObjects rarely seem to use all of the complexity available to them, and many of the ones that do more work in paint could (and perhaps should) be refactored into smaller, simpler objects.
Repository: rust
Issue: Tracking Issue for ExitCode::exit_process()
Labels: T-libs-api,C-tracking-issue,A-process

Feature gate: `#![feature(exitcode_exit_method)]`

This is a tracking issue for the `ExitCode::exit_process()` method.

`exit_code.exit_process()` exits the process with the `ExitCode` passed as the self argument. 
### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
impl std::process::ExitCode {
    pub fn exit_process(self) -> !;
}
```

### Steps / History

- [x] Implementation: #95356
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilzation PR can be opened by anyone.
-->

### Unresolved Questions

- Name of the method? Might be better to have a free function instead of associated method, but then there's no good name for it that wouldn't overlap with the existing `process::exit`. As a postfix verb it's sorta clunky, or maybe doesn't communicate explicitly with _what_ the process is being exited? I think exit_process strikes a good balance but I discussed it more in the impl PR #95356.
Repository: vscode
Issue: The detail of QuickPick item is truncated by QuickPick separator
Labels: bug,quick-pick

<!-- ⚠️⚠️ 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.67.1
- OS Version: Windows_NT x64 10.0.22621

Since the detail and label are on different rows, it should not affect each other.

Steps to Reproduce:

1. Set a long label of QuickPickItem which is separator.
2. Set a long detail of QuickPickItem below the separator item.

Effect:
![image](https://user-images.githubusercontent.com/886116/168725267-66cde8ff-b965-4e50-a1a0-d8934294fe5e.png)
Repository: PowerToys
Issue: remap 'alt' to 'alt + shift' for Fusion 360
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager

### Description of the new feature / enhancement

I want to remap the single alt press to alt + shift specifically for Fusion 360

as it stands powertoys does not allow for the mapping of a single modifier key to some other combination

### Scenario when this would be used?

for camera navigation purposes to better align with other applications that use this key combination ( maya for example )

### Supporting information

_No response_
Repository: flutter
Issue: [in_app_purchase][ios]: Purchase multiple quantity of one product
Labels: c: new feature,platform-ios,p: in_app_purchase,package,c: proposal,P3,team-ios,triaged-ios

In my [pull request](https://github.com/flutter/plugins/pull/5711) I added ability to purchase multiple quantity of one product using the [in_app_purchase](https://pub.dev/packages/in_app_purchase) plugin. This is going to work only with the App Store underlying store. You can define a quantity in AppStorePurchaseParam.  Here is example of using new feature:
```dart
purchaseParam = AppStorePurchaseParam(
                    productDetails: productDetails,
                    quantity: 5,
                    applicationUserName: null,
                  );
_inAppPurchase.buyConsumable(purchaseParam: purchaseParam);
```
Repository: PowerToys
Issue: Add wushowhide
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

The Windows Update 'wushowhide' utility is and will likely always be useful for blocking bad updates or drivers. As it is, the utility is already great, but it could be extended to blocking updates for a device permanently if the user so chooses, as you can do through Group Policy.

### Scenario when this would be used?

i just used wushowhide yesterday to hide Intel display driver 27.20.100.8729 because 30.0.101.1960 is on Intel's website and available from Intel Driver & Support Assistant. The 30 release works fine on my system and Windows Update is relentless in installing its older version over what I installed without wushowhide. 

This utility is better than blocking by device ID in group policy because you will catch the next WU driver release when available. For me, this is the preferred way to handle this as I do want automatic updates for all of my devices. But we do need an option for the one-off, and extending the utility to add a single device to block all updates for should be considered as well.

### Supporting information

_No response_
Repository: yt-dlp
Issue: DISCUSSIONS
Labels: discussion/announcement

#### Since Github allows pinning only 3 issues, here's some important discussions:

# Active

* https://github.com/yt-dlp/yt-dlp/issues/11242
* https://github.com/yt-dlp/yt-dlp/issues/4846
* https://github.com/yt-dlp/yt-dlp/issues/4827
* https://github.com/yt-dlp/yt-dlp/issues/1918
* https://github.com/yt-dlp/yt-dlp/issues/1354
* https://github.com/yt-dlp/yt-dlp/discussions/803#discussioncomment-2021803

# Closed

* https://github.com/yt-dlp/yt-dlp/issues/10086
* https://github.com/yt-dlp/yt-dlp/issues/10087
* https://github.com/yt-dlp/yt-dlp/issues/7803
* https://github.com/yt-dlp/yt-dlp/issues/8370
* https://github.com/yt-dlp/yt-dlp/issues/3764
* https://github.com/yt-dlp/yt-dlp/issues/267
* https://github.com/yt-dlp/yt-dlp/issues/390
* https://github.com/yt-dlp/yt-dlp/issues/389
* https://github.com/yt-dlp/yt-dlp/issues/1839
* https://github.com/yt-dlp/yt-dlp/issues/2345
Repository: create-react-app
Issue: Build project, doest not show console.log
Labels: needs triage,issue: bug report

So basically, the `react-scripts build` does not show any errors or anything, its hard to debug the project.
The local build is working fine, but the server build does not show any sign of errors, it hard to debug in this case, I hope this team should put options not to remove console, though they already declared it on their documentation that **NODE_ENV** is not editable. But why ? so the real deal is `react-scripts` should only be used by the elite? Hope you made some exceptions also.

Can someone help me show the console logs?
Repository: godot
Issue: font does not work in bbcode of richtextlabel
Labels: bug,confirmed,topic:gui

### Godot version

3.4.4

### System information

Mac OS 12.3.1

### Issue description

set bbcode 
64[font=res://font/32.fnt][color=blue]32[/color][/font]
the text of 32 does not use font 32.fnt

### Steps to reproduce

add a richtextlabel
enable bbcode
set bbcode to 
64[font=res://font/32.fnt][color=blue]32[/color][/font]


### Minimal reproduction project

[font.zip](https://github.com/godotengine/godot/files/8707617/font.zip)
Repository: godot
Issue: (Editor Scene tree) Node Label coming in front instead of hiding
Labels: bug,topic:editor,topic:gui

### Godot version

3.4.4.stable

### System information

Doesn't matter

### Issue description

Hy, so whenever i decrease the width of the scene editor this happens (it's kinda unpleasant to the eye)

https://user-images.githubusercontent.com/77773850/168814893-69e21880-727f-4371-a966-a6a39d3138cb.mp4


### Steps to reproduce

In the project below, while checking the **LAST** node try slowly decreasing the width as shown above

### Minimal reproduction project

[New Game Project.zip](https://github.com/godotengine/godot/files/8708442/New.Game.Project.zip)
Repository: TypeScript
Issue: `ts.convertToBase64` does not handle emojis
Labels: Bug,Help Wanted

# Bug Report

https://github.com/microsoft/TypeScript/blob/da00ba67ed1182ad334f7c713b8254fba174aeba/src/compiler/utilities.ts#L5244

```
> ts.convertToBase64("📣❓")
'7aC97bOj4p2T'
> Buffer.from("📣❓").toString("base64")
'8J+To+Kdkw=='
```

### 🔎 Search Terms

- ts.convertToBase64
- emojis

### 🕗 Version & Regression Information

Probably a long time.

### ⏯ Playground Link

N/A

### 💻 Code

```ts
ts.convertToBase64("📣❓")
```

### 🙁 Actual behavior

```
7aC97bOj4p2T
```

### 🙂 Expected behavior

```
8J+To+Kdkw==
```