sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: AoT: Remember if an app has Always on Top set, turn on when reopened
Labels: Idea-Enhancement,Product-Always On Top,Cost-Large

### Description of the new feature / enhancement

Be able to always designate a window as always on top, even if its dismissed, so that next time it comes up, it still always on top

### Scenario when this would be used?

Outlook reminders window.  When you dismiss reminders, the window closes.  The next time there is a Reminder, its no longer always on top.

### Supporting information

_No response_
Repository: flutter
Issue: Can Key frame be part of the framework?
Labels: framework,c: proposal,P3,team-framework,triaged-framework

Here is an amazing Flutter key frame render optimize for Flutter, 
The optimize provide a new [may not new ] to render the widget in parallel or split them from full order.

Looks very smoth. 

My question, can this optimize be import to flutter/flutter 

FYI:
https://github.com/LianjiaTech/keframe
Repository: godot
Issue: A custom class connection that extends nothing is disconnected by yield.
Labels: bug,topic:core

### Godot version

3.3.4 , 3.4.2

### System information

Windows10

### Issue description

class_a.gd
```
class_name ClassA

signal test_started
signal test_finished

func start():
	emit_signal("test_started")
	yield(test(),"completed")
	emit_signal("test_finished")

func test():
	print("wait start")
	yield( SingletonNode.get_tree().create_timer(1.0) , "timeout" )
	print("wait end")
```
class_b.gd
```

class_name ClassB

func start():
	
	var obj = ClassA.new()
	var _err
	
	_err = obj.connect("test_started",self,"_start")
	_err = obj.connect("test_finished",self,"_finish")
	
	obj.start()

func _start():
	print("obj start")

func _finish():
	print("obj finish")

```
test_scene.gd
```
extends Node2D

func _ready():
	var obj = ClassB.new()
	var _err
	
	obj.start()
```
When I executed the node to which test_scene.gd was assigned in the above source code, the following execution result was obtained.
![image](https://user-images.githubusercontent.com/73507097/148482543-f01c2a46-db5a-4511-ac3d-54493c147980.png)

Originally, _finish () of ClassB should be called by "test_finished" of ClassA, but it was not called.
If there is no "yield", it works normally.

### Steps to reproduce

Run test_scene.tscn in SignalAndYield. (Already set as the main scene.)

### Minimal reproduction project

[SignalAndYield.zip](https://github.com/godotengine/godot/files/7825921/SignalAndYield.zip)
Repository: material-ui
Issue: [ESM] Webpack 5 - NodeJs Server
Labels: breaking change,enhancement,scope: code-infra

### Current behavior 😯

 ESM are not usable in server side, after node 12 esm is enabled and when we want to use esm is imposible since the packages.json does not have type: module or the files are not properly named with .mjs ext.

when using import Accordion from '@mui/material/Accordion';

this throw an error since is getting the index.js in that folder instead the main in package wich is the commonjs file.

### Expected behavior 🤔

expected imported either commonjs file correctly or mark the package.json with type: module as per nodes specs.



### Steps to reproduce 🕹

Steps:

1. import any material module
2. mark you own package with type:module as well
3. execute node supporting modules


### Context 🔦

Server Side

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  System:
    OS: macOS 12.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 2.95 GB / 64.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 17.0.1 - ~/.nvm/versions/node/v17.0.1/bin/node
    npm: 8.1.3 - ~/.nvm/versions/node/v17.0.1/bin/npm
  Managers:
    Homebrew: 3.3.3 - /opt/homebrew/bin/brew
    pip3: 21.2.4 - /opt/homebrew/bin/pip3
    RubyGems: 3.0.3.1 - /usr/bin/gem
  Utilities:
    Make: 3.81 - /usr/bin/make
    GCC: 4.2.1 - /usr/bin/gcc
    Git: 2.32.0 - /usr/bin/git
    Clang: 13.0.0 - /usr/bin/clang
    FFmpeg: 4.4.1 - /opt/homebrew/bin/ffmpeg
  Servers:
    Apache: 2.4.51 - /usr/sbin/apachectl
  Virtualization:
    Docker: 20.10.10 - /usr/local/bin/docker
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
  IDEs:
    Nano: 2.0.6 - /usr/bin/nano
    Vim: 8.2 - /usr/bin/vim
    Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
  Languages:
    Bash: 3.2.57 - /bin/bash
    Perl: 5.30.3 - /usr/bin/perl
    Python: 2.7.18 - /usr/bin/python
    Python3: 3.9.7 - /opt/homebrew/bin/python3
    Ruby: 2.6.8 - /usr/bin/ruby
  Databases:
    MySQL: 10.6.4 (MariaDB) - /opt/homebrew/bin/mysql
    SQLite: 3.36.0 - /usr/bin/sqlite3
  Browsers:
    Chrome: 96.0.4664.110
    Safari: 15.2
```
</details>
Repository: pytorch
Issue: argmin/argmax incorrect doc for the first form
Labels: module: docs,triaged,module: reductions

### 📚 The doc issue

The first half of the doc appears to be incorrect here: https://pytorch.org/docs/stable/generated/torch.argmax.html

> torch.argmax(input) → LongTensor
> Returns the indices of the maximum value of all elements in the input tensor.
> This is the second value returned by torch.max(). See its documentation for the exact semantics of this method.
> Note
> If there are multiple maximal values then the indices of the first maximal value are returned.


### Suggest a potential alternative/fix

If I'm not mistaken:

1. It should be `s/indices/index/g` everywhere as the first form returns a single global index. 
2. And it's not the second value returned by `torch.max()`, because the latter in this form returns only one value and it's not the index

The example is also a bit less than great, since `tensor(0)` doesn't immediately show the reader that it's a global index, it'd have been better to have a max number somewhere in row 2 or higher to show that its a global index.

If this is indeed a mistake, then https://pytorch.org/docs/stable/generated/torch.argmin.html has the same copy-cat issue as argmax.

Thanks.


cc @brianjo @mruberry
Repository: PowerToys
Issue: Image Resizer - capacity to specify full path for resized images 
Labels: Idea-Enhancement,Product-Image Resizer

### Description of the new feature / enhancement

At present, it seems like resized images can only be saved to the same folder, or a subfolder of the same folder, in which the original image is located.  The naming syntax for resized images is good but the capacity to specify the full location to save resized images - including drive letter - would be a very handy addition.  Perhaps the standard Windows file "Save As" dialogue box could be invoked to navigate to the required folder.

### Scenario when this would be used?

Whenever resizing images.  These can be stored anywhere in my PC's file system which extends across five separate drives.  I usually want to work on resized images in a particular working folder.  This would be a welcome expansion of functionality.

### Supporting information

_No response_
Repository: vscode
Issue: terminal.integrated.defaultProfile and terminal.integrated.automationProfile behaves differently
Labels: feature-request,tasks,terminal-profiles

<!-- ⚠️⚠️ 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.64.0-insider (user setup)
- OS Version: Windows_NT x64 10.0.19044

I can define my preferred terminal profile using the `terminal.integrated.profiles.linux` setting:
```
    "terminal.integrated.profiles.linux": {
        "zsh": {
            "path": "zsh",
            "args": [
                "--login"
            ],
            "env": {
                "TMUX": "false"
            }
        }
    },
```

...and I can specify this profile (referring to it by name) as my `defaultProfile`:
```
    "terminal.integrated.defaultProfile.linux": "zsh",
```

So this works fine for the standard built-in Terminal in VS Code.

However, I also want to use this terminal profile in the debugging-terminals. And according to the documentation, the setting `terminal.integrated.automationProfile.linux` should work like the `terminal.integrated.defaultProfile.linux`, allowing me to specify:

```
    "terminal.integrated.automationProfile.linux": "zsh",
```

But this does NOT work. The setting `terminal.integrated.automationProfile.linux` expects a dictionary/object like the `terminal.integrated.profiles` setting. But it only accepts keywords `path` and `icon`, so I'm not able to specify the `args` and `env` that I need.


Proposed fix: Make sure `terminal.integrated.automationProfile` behaves like `terminal.integrated.defaultProfile` (and according to the documentation), allowing us to specify a profile name defined in the `terminal.integrated.profiles` setting.
Repository: flutter
Issue: [Proposal] GestureDetector Configure duration of `onLongPress`
Labels: c: new feature,framework,f: gestures,c: proposal,P3,team-framework,triaged-framework

## Use case

In my application i need to custom longPress time, and it's not good idea use onPanDown and onPanEnd with using Timer.
This method going to conflict with event onTap.

## Proposal

Insert a propriety timeConsideration for LongPress.
I saw in pub.dev and I found this package https://pub.dev/packages/gesture_x_detector , but when i try in my real iPhone 8 Plus working bad, every event are freezed, but in my android and iOS emulator and in real iPhone 11 working good.

It's good idea implement this propriety for GestureDetector, 
what do you think? 

## My Use Case

Now I using XGestureDetector, it's good package but not working good in my iPhone and I not know why.

https://github.com/EliaTolin/infinity_sweeper/blob/50748744a7847930521e13596a44885734308a34/lib/widgets/game/cell_widget.dart#L45
Repository: rust
Issue: bad rustdoc ux: trait method implementations have their docstrings ommitted in the "implementors" section
Labels: T-rustdoc,A-impl-trait,C-bug,A-rustdoc-ui

I opened documentation of FromIterator ( https://doc.rust-lang.org/std/iter/trait.FromIterator.html ), then I scrolled to section "Implementors" and found this implementation:
```rust
impl<A, E, V> FromIterator<Result<A, E>> for Result<V, E>
where
    V: FromIterator<A>,
```
This implementation was not documented on this page. I clicked "[src]" and was able to see docs in source. So, I thought that there is some bug in rustdoc, which causes this docs not to render. Then I opened page on Result ( https://doc.rust-lang.org/std/result/enum.Result.html ) and (susprisiongly) found that this impl is documented there! So, for unknown reasons rustdoc shows this doc on Result page, but doesn't show it on FromIterator page
Repository: node
Issue: Error in building the Linux x86 library
Labels: build

### Version

16.13.0

### Platform

Linux DESKTOP-GFGGCIN 5.10.16.3-microsoft-standard-WSL2 #1 SMP Fri Apr 2 22:23:49 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

### Error

Error in building the Linux x86 library
<br />
Screenshots of the problem:
<br />
<img src="https://i.ibb.co/bJtV9LQ/Screenshot-1.png" />
<img src="https://i.ibb.co/WDvJpsq/Screenshot-2.png" />
<br />
Versions:
<br />
<img src="https://i.ibb.co/rQbQfB7/Screenshot-3.png" />
Repository: rust
Issue: Missed optimization opportunity during stack pinning
Labels: A-LLVM,I-slow,T-compiler

Hi,

This code:

```rust
#![feature(bench_black_box)]

use core::hint::black_box;

#[inline(never)]
pub fn foo<T>(mut val: T) {
    loop {
        black_box(&mut val);
    }
}

pub fn bar() {
    foo([0u8; 1024]);
}
```

... compiles to:

```
define ... {
start:
  %0 = alloca [1024 x i8]*, align 8
  %1 = bitcast [1024 x i8]** %0 to i8*
  
  /* ... */
}
```

... but "pinning" `val` to the stack:

```rust
#[inline(never)]
pub fn foo<T>(val: T) {
    let mut val = val;

    loop {
        black_box(&mut val);
    }
}
```

... causes rustc to emit a seemingly spurious `alloca` + `memcpy`:

```
define ... {
start:
  %0 = alloca [1024 x i8]*, align 8
  %val1 = alloca [1024 x i8], align 1
  %1 = getelementptr inbounds [1024 x i8], [1024 x i8]* %val1, i64 0, i64 0
  %2 = getelementptr inbounds [1024 x i8], [1024 x i8]* %val, i64 0, i64 0
  call void @llvm.memcpy.p0i8.p0i8.i64(...)
  %3 = bitcast [1024 x i8]** %0 to i8*
  /* ... */
}
```

(checked on current nightly & `--release`.)

Emitting that `alloca` + `mempy` (or LLVM not eliding them, for what it's worth) makes the function require _twice_ the amount of stack size it would need otherwise, considering the fact that the parameter already lives on the stack and doesn't escape it.

I think this accounts for a missed optimization opportunity either in rustc (as in `this shouldn't have been emitted`) or LLVM (as in `this should've been elided via MemCpyOptimizer`) 🙂 

In the wild, I've found this issue when writing an async executor for AVR - using [`futures::pin_mut!()`](https://docs.rs/futures/latest/futures/macro.pin_mut.html) made my executor require twice the amount of stack size, triggering stack overflow for seemingly innocuous, small futures. But that's just for context - I think this potentially missed optimization is not related to AVR, since it's present inside the LLVM IR itself.
Repository: rust
Issue: Error when running `ui` tests after `run-make-fulldeps`
Labels: A-testsuite,T-bootstrap,C-bug

While running the test suite I noticed that executing the `run-make-fulldeps` suite *before* the `ui` suite causes the following tests to fail:

* `ui/allocator/no_std-alloc-error-handler-default.rs`
* `ui/allocator/no_std-alloc-error-handler-custom.rs`

```
error[E0464]: multiple matching crates for `libc`
  --> /.../src/test/ui/allocator/no_std-alloc-error-handler-default.rs:16:1
   |
LL | extern crate libc;
   | ^^^^^^^^^^^^^^^^^^
   |
   = note: candidates:
           crate `libc`: /.../build/x86_64-unknown-linux-gnu/stage2/lib/rustlib/x86_64-unknown-linux-gnu/lib/liblibc-2383dbda905dd8ee.rlib
           crate `libc`: /.../build/x86_64-unknown-linux-gnu/stage2/lib/rustlib/x86_64-unknown-linux-gnu/lib/liblibc-a96bf8e49971bcfd.rlib

error: aborting due to previous error

For more information about this error, try `rustc --explain E0464`.
```

After a quick investigation it seems like building `rustc-demangler` puts an extra copy of `liblibc-HASH.rlib` (with a different hash) in the stage2 libs directory, causing the UI test not to know which `libc` to link to.

**Reproduction**

Running this command (just the `ui` test before `run-make-fulldeps`) works:

```
./x.py --stage 2 test src/test/ui/allocator/no_std-alloc-error-handler-default.rs src/test/run-make-fulldeps
```

Running this command (`run-make-fulldeps` before the `ui` test) fails:

```
./x.py --stage 2 src/test/run-make-fulldeps test src/test/ui/allocator/no_std-alloc-error-handler-default.rs
```
Repository: PowerToys
Issue: PowerToys ColorPicker stores the logs outside standard convention
Labels: Idea-Enhancement,Product-Color Picker,Area-Logging

### Microsoft PowerToys version

0.53.0

### Running as admin

- [ ] Yes

### Area(s) with issue?

ColorPicker

### Steps to reproduce

![image](https://user-images.githubusercontent.com/61519853/148528871-e19664ee-b241-4b23-9488-75745f193320.png)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: rust
Issue: Implementation-specific "empty lifetime in universe" error
Labels: A-diagnostics,T-compiler,D-confusing

[Given the following code:](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=3875315ad027e156fa808e6fb5676e2f)
```rust
use std::borrow::Cow;

fn foo<K, F>(f: F)
where
    F: Fn(&String) -> Cow<'_, K>,
    for<'any> Cow<'any, K>: PartialEq,
    K: ToOwned + ?Sized,
{
    let mut s = "test".to_string();
    {
        let a = f(&s);
        let b = f(&s);
        dbg!(a == b);
    }
    s.push_str(" borrows done");
}

fn main() {
    foo(|s| Cow::<'_, usize>::Owned(s.len()));
    foo(|s| Cow::Borrowed(&s[0..1]));
    fn f<F: for<'l> Fn(&'l String) -> Cow<'l, Option<Cow<'l, str>>>>(f: F) -> F { f }
    foo::<Option<Cow<'_,str>>, _>(f(|s| Cow::Owned(s.get(0..1).map(Cow::Borrowed))));
}
```

The current output is:

```

error[E0308]: mismatched types
  --> src/main.rs:22:5
   |
22 |     foo::<Option<Cow<'_,str>>, _>(f(|s| Cow::Owned(s.get(0..1).map(Cow::Borrowed))));
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^   ----------------------------------------------
   |     |                               |
   |     |                               the expected closure
   |     |                               the found closure
   |     lifetime mismatch
   |
   = note: expected associated type `<[closure@src/main.rs:22:37: 22:83] as FnOnce<(&String,)>>::Output`
              found associated type `<[closure@src/main.rs:22:37: 22:83] as FnOnce<(&String,)>>::Output`
   = note: the required lifetime does not necessarily outlive the empty lifetime in universe U6
note: the lifetime requirement is introduced here
  --> src/main.rs:5:23
   |
5  |     F: Fn(&String) -> Cow<'_, K>,
   |                       ^^^^^^^^^^
```

<!-- The following is not always necessary. -->
Ideally the output should be:

An inscrutable error that doesn't mention universes or the empty lifetime.

----

I didn't expect this to compile, and I didn't expect a simple error either, but I was surprised to see such implementation-specific details as the empty lifetime and "universe U6".  I thought you'd want to know too.

Discovered on the Playground, Rust 1.57.0, no change on Beta or Nightly.
Repository: PowerToys
Issue: Allow originial context menus in file explorer for Win11
Labels: Idea-New PowerToy,Product-Tweak UI Design

### Description of the new feature / enhancement

It would greatly be appreciated, if you would include a feature allowing us to turn back on the original context menus. In Windows 11.

### Scenario when this would be used?

When I wanted to switch to it. For a more proficient work flow.

### Supporting information

_No response_
Repository: godot
Issue: Vulkan: Decal 'Normal Fade' feature appears incorrect on scaled meshes
Labels: bug,topic:rendering,confirmed,topic:3d

### Godot version

v4.0.dev.20211210.official [21b81998b]

### System information

Windows 7, Vulkan Clustered, RX 570 (21.5.1)

### Issue description

When a mesh is scaled either with its own Scale transform or the Scale of any parent nodes, the Normal Fade feature of Decals applied to it will misbehave.

The Decal's normal fading appears inconsistent and buggy.
When the mesh node's scale is even (all fields have the same value), there is a visible pattern: When the mesh is scaled up, the Decal appears too opaque. And vice versa for meshes that are scaled down, the Decal appears too transparent. Otherwise, there isn't any pattern I can discern.

The Decal's place in the scene tree does not matter, including its own scale.

![image](https://user-images.githubusercontent.com/71602778/148539673-5cf84f1b-547e-44c1-8f98-c4fcc77f74d9.png)
Three unshaded SphereMeshes, identical aside from their Scale. All of these Decals have their Normal Fade set to `0.5`. Their Vertical Fade was also lowered to 0, to not interfere with the test.

I expect that all the Decals appear just like the middle one, fading the exact same amount based on the normal.

### Steps to reproduce

1. Create a `MeshInstance3D`, preferably with a `SphereMesh` Mesh
2. Create a `Decal`, give it any Albedo texture. Set the Normal Fade to a value above 0. I also recommend setting both Vertical Fade properties to 0, so that they do not cause confusion.
3. Move the Decal so that it's applied to the mesh. Make it a child of the mesh node so that it's in the same position on the mesh, and covers the same area on it.
4. Scale the mesh node. Observe the decal's transparency changing. Drag the Decal's Normal Fade property around, to clearly see how it's been affected.

### Minimal reproduction project

[DecalFadeTest.zip](https://github.com/godotengine/godot/files/7828725/DecalFadeTest.zip)
Repository: rust
Issue: Bad "try_into" usage causes message "the trait bound `u8: From<char>` is not satisfied"
Labels: A-diagnostics,T-compiler

Given the following code: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=705695b1b99a0894bc73e755bfc8ad63

```rust
fn main() {
    let _: u8 = 'a'.try_into().unwrap();
}
```

The current output is:

```
error[E0277]: the trait bound `u8: From<char>` is not satisfied
 --> src/main.rs:2:21
  |
2 |     let _: u8 = 'a'.try_into().unwrap();
  |                     ^^^^^^^^ the trait `From<char>` is not implemented for `u8`
  |
  = help: the following implementations were found:
            <u8 as From<NonZeroU8>>
            <u8 as From<bool>>
  = note: required because of the requirements on the impl of `Into<u8>` for `char`
  = note: required because of the requirements on the impl of `TryFrom<char>` for `u8`
  = note: required because of the requirements on the impl of `TryInto<u8>` for `char`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `playground` due to previous error
```

The output should mention TryInto or TryFrom instead of From
Repository: PowerToys
Issue: [PowerToys Run] Support windows app synonyms
Labels: Idea-Enhancement,Help Wanted,Product-PowerToys Run

### Description of the new feature / enhancement

I found a text file containing app synonyms, and in there lies some explanation as to why and how the search feature in Windows 10 lists search results as it does when searching for applications, apps, and settings.

It lists all common misspellings of some common applications. For instance, did you know that you can do a search for “exell” and it will display “Excel 2016” in the search results? You can also type “npo” to find “Notepad“, or type “c prompt” that will list “command prompt”, or “exx” that will find “Internet Explorer” or if you search for “ie” and it will list “Edge”.

The file where all these synonyms are gathered is named appssynonyms.txt and is located in
```
%LocalAppData%\Packages\Microsoft.Windows.Search_cw5n1h2txyewy\LocalState\ConstraintIndex\Input_{7c5356ce-e01e-44c3-8f22-0ba9ef94aa3a}\
```

I want this feature for PowerToys Run.

### Scenario when this would be used?

Play Store -> Microsoft Store
![image](https://user-images.githubusercontent.com/23485114/148555949-3c10db30-92e8-4d64-b639-15ff2e2ef8c2.png)
![image](https://user-images.githubusercontent.com/23485114/148556521-c67fb986-ad23-41a5-804a-175704086608.png)
### Supporting information

_No response_