sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: It is recommended that users be allowed to create desktop icons with specific functions. 
Labels: Idea-Enhancement,Product-Tweak UI Design

### Description of the new feature / enhancement

It is recommended that users be allowed to create desktop icons with specific functions. Many users know about this software and like its functions very much, but they don't use it very often. As a result, every time he wants to use it, he has to open the software and then look at the shortcut keys in order to use a specific function, such as searching and picking colors. There are many such users, which are very unfriendly to low and medium frequency users at present. 
Some people will forget that they have installed such a software and want to set up the page, add an option to each function, and create a desktop icon so that users can put the icon on the start menu or the taskbar. In this way, the low-and medium-frequency user experience will be greatly improved, and even turn them into high-frequency users, really improve their efficiency. Of course, not all functions are suitable for creating icons. 
But searching and picking colors, rulers and so on really need this function.

### Scenario when this would be used?

Many users know this software and like its functions very much, but they don't use it very often. As a result, every time he wants to use it, he has to open the software and then look at the shortcut keys before he can use a specific function, such as searching and picking colors. There are many such users. At present, they are very unfriendly to low and medium frequency users. Over time, some people will forget that they have installed such a software. 
If you want to set up the page, add an option to each function and create a desktop icon

### Supporting information

_No response_
Repository: pytorch
Issue: [functorch] transforms like jacrev, jacfwd, grad, etc don't work with BatchNorm
Labels: triaged,module: functorch

### 🐛 Describe the bug

```python
import torch
import functorch

net = torch.nn.BatchNorm2d(10)
net.train()
t = torch.randn(3, 3, 10, 10)
functorch.jacrev(net)(t)
```

Error:
```
RuntimeError: During a grad (vjp, jvp, grad, etc) transform, the function provided attempted to call in-place operation (aten::add_.Tensor) that would mutate a captured Tensor. This is not supported; please rewrite the function being transformed to explicitly accept the mutated Tensor(s) as inputs.
```

This also leads to failures on multiple models from https://github.com/pytorch/benchmark

### Versions

master

cc @zou3519 @Chillee @samdow @soumith
Repository: vscode
Issue: Merge editor: restore original contents if aborting and allow to undo
Labels: under-discussion,merge-editor

This issue is 2 issues but closely related: how to get back to the workspace file contents after closing the merge editor without having resolved the conflict. The setup is:
* have the conflicting workspace file opened as a text editor
* then open the merge editor for it

I think this setup will be common because users would most likely first see the workspace file in a text editor with the git merge markers before deciding to use the merge editor.

**Auto Save: ON**
In this case the user should not see a dialog asking to revert the changes back but I think as we had discussed allowing to run the `Undo` command in the text editor would be nice to get the model at the contents how they were. 

**Auto Save: OFF**
Assuming the user has not saved the merge editor yet (i.e. the dirty indicator shows), closing the merge editor and picking "Do not save" should ideally restore the workspace file text editor as it was:
* if the editor was dirty, restore the buffer and show the editor dirty `[1]`
* if the editor was saved, restore the contents from disk

Does that make sense? I wonder how weird `[1]` would be given that after clicking "Do not save" the workspace file would show as dirty again, but I think it makes sense to restore it how it was.

//cc @isidorn @daviddossett
Repository: rust
Issue: extern "C" functions don't generate the same IR definitions as clang on x86, causing problems with cross-language LTO
Labels: A-LLVM,A-FFI,P-high,T-compiler,I-unsound,C-bug,WG-llvm,regression-untriaged,A-ABI,O-x86_32

After https://github.com/llvm/llvm-project/commit/6c8adc505471542be38bd71d1000062daa46d7bc, inlining in cross-language LTO happens in cases where it didn't happen before, including cases where things go very bad (more details in https://bugzilla.mozilla.org/show_bug.cgi?id=1789779#c7)

It seems to boil down to LLVM not liking that rust defines its `extern "C"` functions in significantly different ways than clang does for the C/C++ code that calls it. For example:
```rust
// rustc --emit=llvm-ir foo.rs --crate-type=lib --target=i686-unknown-linux-gnu
#[repr(C)]
pub struct Foo(pub u32);

#[no_mangle]
pub unsafe extern "C" fn foo(foo: Foo) -> u32 {
    foo.0
}
```
The caller:
```C
// clang -o - -S foo.c -emit-llvm --target=i686-unknown-linux-gnu
struct Foo { int a; };

extern int foo(struct Foo f);

int var(struct Foo f) {
    return foo(f);
}
```
Rust defines the function as:
```
Foo = type { i32 }

; Function Attrs: nonlazybind uwtable
define i32 @foo(%Foo* byval(%Foo) %foo) unnamed_addr #0 {
```
while the caller C code does this:
```
%struct.Foo = type { i32 }
(...)
declare i32 @foo(i32) #1
```

The equivalent C code:
```C
// clang -o - -S foo.c -emit-llvm --target=i686-unknown-linux-gnu
struct Foo { int a; };

int foo(Foo foo) {
    return foo.a;
}
```
defines the function as:
```
%struct.Foo = type { i32 }

; Function Attrs: noinline nounwind optnone uwtable
define dso_local i32 @foo(i32 %0) #0 {
```

(Ironically, rustc transforms a non-`extern "C"` version of the function to the same declaration as clang's)

Arguably, there's an underlying LLVM bug not being able to handle this case, which /could/ be considered fine, but I'm not sure it's supposed to be.

It's worth noting that rustc does not use a byval for e.g. x86_64-unknown-linux-gnu.

Cc: @nikic
Repository: PowerToys
Issue: Find My Mouse: Mouse pointer doesn't de-highlight after specified time, if mouse keeps moving slowly
Labels: Idea-Enhancement,Product-Mouse Utilities

### Microsoft PowerToys version

0.62.1

### Running as admin

- [ ] Yes

### Area(s) with issue?

Mouse Utilities

### Steps to reproduce

Turn on the Find my mouse.
Activation Method: Shake mouse
Shake the mouse. And after mouse pointer gets highlighted, keep moving mouse slowly. 


### ✔️ Expected Behavior

After specified time in "Fade delay", the mouse pointer should de-highlight if I am moving mouse slowly.
As I am moving mouse slowly, my intention is that, I found pointer on screen and I am back to work now.

### ❌ Actual Behavior

After mouse pointer gets highlighted, If I keep moving mouse slowly the mouse pointer remain highlighted even though It supposed to de-highlight after specified time

### Other Software

_No response_
Repository: material-ui
Issue: [Tabs] The selected field should automatically appear in the middle of the scrollbar, with one option before and one option after it in the scrollable grid
Labels: new feature,waiting for 👍,component: tabs

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

Let's take the instance of a calendar, with names of the months in the scrollable tab. Currently, three months are displayed in the scrollable grid. For example, while raising this issue, the month by the calendar is September. Therefore, the auto month selected is September,  but it appears as the last option in the ready view of the calendar, followed by the right scrollable icon. It would be better if September appears in the middle, followed by October. So I request the team to implement this feature in <b> Scrollable Tab</b>. Thanks.

### Examples 🌈

![image](https://user-images.githubusercontent.com/98734708/191924041-05a42d78-fd98-40a3-872c-b69ce1d28b44.png)
For instance, the above example, item four is selected. I would request a feature which automatically makes the next item, i.e. item five appear automatically when item four is selected. This will enable the user to view the next option without scrolling.

### Motivation 🔦

_No response_
Repository: next.js
Issue: 12.3.x causes `Collecting page data` to fail during build
Labels: Upstream

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 21.6.0: Mon Aug 22 20:20:05 PDT 2022; root:xnu-8020.140.49~2/RELEASE_ARM64_T8101
    Binaries:
      Node: 18.8.0
      npm: 8.18.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 12.3.1
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

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

_No response_

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

_No response_

### Describe the Bug

After upgrading from `12.2.5` to `12.3.0` or `12.3.1` I started getting build errors during "Collecting page data" step. Error output includes

```zsh
Generating static pages (0/3)TypeError: Cannot read properties of null (reading 'useContext') at exports.useContext
Error occurred prerendering page "/". Read more: https://nextjs.org/docs/messages/prerender-error
TypeError: Cannot read properties of null (reading 'useContext')
```

### Expected Behavior

Should build without issues

### Link to reproduction

https://github.com/WalletConnect/web3modal

### To Reproduce

1. Pull repository linked above
2. Inside `examples/react/package.json` change next.js version to `12.3.1`
3. From root of the repo run `npm install; npm run build`
Repository: flutter
Issue: Proposal to set different FontWeight for each font in fontFamilyFallback.
Labels: c: new feature,framework,a: typography,c: proposal,P3,team-framework,triaged-framework

Generally, the `FontWeight` used for each font is used differently.
However, it is currently not possible to give different FontWeights of fonts of `fontFamilyFallback`.
In the example below, `FontWeight.w700` is applied to all fonts.

```dart
Text(
  "Hello 안녕 こんにちは",
  style: const TextStyle(
    fontFamily: 'NotoSans',
    fontWeight: FontWeight.w700,
    fontFamilyFallback: [
      'NotoSansKR',
      'NotoSansJP',
    ]
)
```

I wonder if there is a way to give a different FontWeight for each font of the current `fontFamilyFallback`, and if not, it would be nice if a function like `TextStyleFallback` was added, for example.
Repository: vscode
Issue: Close, minimize and maximize buttons missing on macOS after using the restart to update option
Labels: bug,macos,workbench-os-integration,confirmation-pending

<!-- ⚠️⚠️ 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 (but presumably due to restart of VSCode)

<!-- 🪓 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.71.2 (updating from 1.70.X)
- OS Version: macOs Monterey 12.5.1 (21G83)

As stated in the issue title, once VSCode updates and restores the windows it fails to show the close/maximize/minimize icons:

<img width="1440" alt="Screenshot 2022-09-23 at 13 25 39" src="https://user-images.githubusercontent.com/592309/191950495-ffcbd983-6431-4158-829a-b64ab971a0c2.png">

This does not happen on all restored windows. The one showing the buttons was previously in fullscreen mode.
<img width="557" alt="Screenshot 2022-09-23 at 13 26 53" src="https://user-images.githubusercontent.com/592309/191950668-954d516b-ff57-47f0-b7ac-3bdc5d4316a1.png">

I imagine it is difficult to replicate this issue so I will list out exactly the steps I took regardless of if I think they are relevant.

Steps to Reproduce:

1. Have multiple VSCode windows open. One on the 'desktop' (ie. not fullscreen mode) and one maximised (fullscreen mode).
2. See the notification for the latest update and dismiss it
3. Open the command pallet and manually select the 'Restart Code to update' option
4. Wait for VSCode to restart

Outcome: 

- The maximized (full screen mode) windows all have the ability to minimize/control the window as expected
- The windows that were not in full screen mode no longer have the ability to control the window as the top toolbar is hidden.
- Using shortcut keys `CTRL` + `CMD` + `F` to enter fullscreen mode works on the window with the toolbar but not the one that restarted minimized
Repository: vscode
Issue: Merge editor: provide labels for undo operations to help local history timeline
Labels: polish,merge-editor

The local history view will use the label of the undo operation as label for the entry to show a more specific label than just "File Saved":

https://github.com/microsoft/vscode/blob/6d7beb43a0a3de03fe2b1ee53899416fac36154c/src/vs/platform/undoRedo/common/undoRedo.ts#L26

![image](https://user-images.githubusercontent.com/900690/191951249-0896a6b3-9709-48ce-b42e-330913c7393b.png)

I think I heard that some model operations from the merge editor have semantic, e.g. when you accept a conflict from one side or the other. Would be great if the relevant model change could have a semantic label for the undo operation. I even think we may show this label somewhere else in the "Edit" menu.
Repository: rust
Issue: Confusing error caused by double peojection in trait supertraits
Labels: A-diagnostics,T-compiler,D-confusing,fixed-by-next-solver

<!--
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.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: ([play](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=7c456d9fc795e6dcd5258407228d9d4e))

```rust
fn f<T>(_: impl A<X = T>) {}

trait A: C<Z = <<Self as A>::X as B>::Y> {
    type X: B;
}

trait B {
    type Y;
}

trait C {
    type Z;
}
```

The current output is:

```
error[E0277]: the trait bound `T: B` is not satisfied
 --> src/lib.rs:1:1
  |
1 | fn f<T>(_: impl A<X = T>) {}
  | ^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `B` is not implemented for `T`
  |
help: consider restricting type parameter `T`
  |
1 | fn f<T: B>(_: impl A<X = T>) {}
  |       +++

error[E0277]: the trait bound `T: B` is not satisfied
 --> src/lib.rs:1:17
  |
1 | fn f<T>(_: impl A<X = T>) {}
  |                 ^^^^^^^^ the trait `B` is not implemented for `T`
  |
help: consider restricting type parameter `T`
  |
1 | fn f<T: B>(_: impl A<X = T>) {}
  |       +++
```

This is confusing because it seems like this error is caused by `type X: B` in the trait, but actually it's caused by `X as B` in the supertraits, if your remove `X as B` the code compiles (as it should in any case, IMO!).


Ideally the code would compile or at least the output should look like:

```
error[E0277]: the trait bound `T: B` is not satisfied
 --> src/lib.rs:1:1
  |
1 | fn f<T>(_: impl A<X = T>) {}
  | ^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `B` is not implemented for `T`
  |
help: consider restricting type parameter `T`
  |
1 | fn f<T: B>(_: impl A<X = T>) {}
  |       +++
note: required because of this
  |
3 | trait A: C<Z = <<Self as A>::X as B>::Y> {
  |                  ^^^^^^^^^^^^^^^^^^
```

<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

<!--
If dramatically different output is caused by small changes, consider also
adding them here.

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. The output might also be
different depending on the Edition.
-->
@rustbot label +D-confusing

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: [go_router] Add support for the TabView for more beautiful animation
Labels: c: new feature,a: animation,package,c: proposal,P3,p: go_router,team-go_router,triaged-go_router

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case
In our app we are using a TabBar with TabView. This create a nice animation when using the tabs. 

![ezgif-4-6d09826040](https://user-images.githubusercontent.com/1774351/191959593-89e338a8-1dc6-4c1a-9a32-30d5993ccd5b.gif)

Now with `go_router` 5.0.0 we can use a ShellRoute but it returns the child in a Navigator. This works but we are losing the nice animation when switching tabs with a TabView.

I was thinking maybe we can create a `TabBarShellRoute` which gets wrapped in a `DefaultTabController` and then returns a child as a `TabView` with all the child routes inside of which each have their own `Navigator`.

Then maybe create a `TabViewGoRoute` which doesn't have a pageBuilder and of which the child `routes` are a list of the normal `GoRoute` objects.
<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal
```dart
TabBarShellRoute(
  navigatorKey: _homeTabBarShellNavigatorKey,
  builder: (context, state, child, controller) => HomeTabShell(
    controller: controller,
    child: child,
  ),
  routes: [
    TabViewGoRoute(
      name: TransactionsTab.name,
      path: '/transactions',
      builder: (context, state) => const TransactionsTab(),
    ),
    TabViewGoRoute(
      name: SavingsBalancesTab.name,
      path: '/savings-balances',
      builder: (context, state) => const SavingsBalancesTab(),
      routes: [
        GoRoute(
          name: OpenSavingsPage.name,
          path: 'open-new',
          parentNavigatorKey: _rootNavigatorKey,
          builder: (context, state) => const OpenSavingsPage(),
        ),
      ],
    ),
  ],
),
```
<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching something showing what you are imagining:
      * images
      * videos
      * code samples

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: godot
Issue: Unexpected behavior when Area2D is disabled by VisibleOnScreenEnabler2d
Labels: bug,topic:physics

### Godot version

4.0.beta1

### System information

Windows 10

### Issue description


Making the Area2D visible when a body is inside of it can make the area no longer detect that body.
I'm not sure if it's due to the VisibleOnScreenEnabler2d or just the act of disabling/enabling the Area2D that does it.
Toggling the area's monitoring property makes it able to detect the body again.
(I am pressing up arrow to reset their positions and visibility)

https://user-images.githubusercontent.com/43501741/191959616-0f5d5dc2-ccd7-4b36-8436-900767f5db2e.mp4



### Steps to reproduce

1.) Run MRP
2.) Using left & right arrow, move the body inside the area.
3.) Press UP arrow to reset their positions and visibility.

### Minimal reproduction project

[area-mrp.zip](https://github.com/godotengine/godot/files/9633580/area-mrp.zip)
Repository: rust
Issue: False positive dead code warning
Labels: A-lints,A-diagnostics,T-compiler,C-bug,A-proc-macros,L-dead_code

When code is generated via a proc macro there is a case which creates a false positive for the dead code warning.

Proc macro (src/lib.rs):
```rust
use proc_macro2::Span;
use quote::quote;
use syn::spanned::Spanned;
use syn::{parse_macro_input, DeriveInput, Ident};

#[proc_macro_derive(Test)]
pub fn proc_dead_code_test(tokens: proc_macro::TokenStream) -> proc_macro::TokenStream {
    let input = parse_macro_input!(tokens as DeriveInput);
    let repr = Ident::new("i8", input.span());
    let repr_call_size = Ident::new("i8", Span::call_site());
    let vis = input.vis;
    quote! {
        impl MyEnum {
            #vis fn false_positive(self) -> #repr {
                self as i8
            }
            pub(crate) fn ok_1(self) -> #repr {
                self as i8
            }
            #vis fn ok_2(self) -> i8 {
                self as i8
            }
            #vis fn ok_3(self) -> #repr_call_size {
                self as i8
            }
        }
    }
    .into()
}
```

Test (tests/all.rs):
```rust
use proc_dead_code_test::Test;

#[allow(dead_code)]
#[derive(Test)]
#[repr(i8)]
pub(crate) enum MyEnum {
    MyValue,
}
```

The current output is:

```
warning: associated function `false_positive` is never used
 --> tests/all.rs:4:10
  |
4 | #[derive(Test)]
  |          ^^^^
  |
  = note: `#[warn(dead_code)]` on by default

warning: `proc_dead_code_test` (test "all") generated 1 warning
```

The generated code for all four functions are identical (except the name, obviusly), tested with `cargo expand`. 

One is reported as dead code, though no report should be given since `#[allow(dead_code)]` is used.

On 1.63.0 this is not a warning, but with 1.65.0-beta.1 it is.

I'm aware that this is a very special case and I don't mind if it doesn't get fixed but I thought I'll report it anyway.

For a quick copy-and-paste run here the Cargo.toml:
```toml
[package]
name = "proc_dead_code_test"
version = "0.1.0"
edition = "2021"

[lib]
proc-macro = true

[dependencies]
syn = { version = "1.0.99", features = ["derive", "parsing", "extra-traits"] }
quote = "1.0.21"
proc-macro2 = "1.0.43"
```

(I don't know how to setup play.rust-lang.org to create a proc-macro and a real test, thats why it's missing.)