sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [Desktop] Multimedia key events not reported to HardwareKeyboard
Labels: a: text input,platform-mac,a: desktop,P2,team-text-input,triaged-text-input


## Steps to Reproduce

1. Add the following to a root level StatelessWidget:

```dart
@override
void initState() {
  super.initState();
  HardwareKeyboard.instance.addHandler(
    (e) {
      print(e);
      return false;
    },
  );
}
```

2. Build to a desktop target (I tested versus macOS).
3. Press most keys, see print statements.
4. Press F-keys, see print statements.
5. Press Multimedia keys (On macOS, same physical keys as F-keys, but with FN-toggle), see nothing printed.

As these are system events, it makes sense that most would not be sent to the app (screen brightness, volume, etc). But it's common for media player apps to require access to Play/Pause, Forward, and Backward keypresses.


**Expected results:** <!-- what did you want to see? -->

I expected to be able to receive keyboard events for media playback keypresses. These must be registered with each OS - e.g., currently on my machine, Spotify is receiving those events and toggling playback regardless of what window has focus. Flutter should be able to similarly register for these privileged events.


<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 2.11.0-0.0.pre.802, on macOS 12.2.1 21D62 darwin-x64, locale en-US)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[!] Xcode - develop for iOS and macOS (Xcode 13.1)
    ! CocoaPods 1.10.0.rc.1 out of date (1.11.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.65.0)
[✓] Connected device (2 available)
[✓] HTTP Host Availability

! Doctor found issues in 2 categories.
```
Repository: PowerToys
Issue: [PT Run] [Time and Date plugin] Allow custom format string
Labels: Idea-Enhancement,Help Wanted,Product-PowerToys Run,Needs-Triage,Run-Plugin

### Description of the new feature / enhancement

The PR #16662 implements a new plugin for date and time values.

It might be interesting to support custom format string as user input like the wox plugin "DateTimeFormatter".

### Scenario when this would be used?

If the user needs an unsupported format.

### Supporting information

https://github.com/sobujbd/Wox.Plugin.DateTimeFormatter

---

⚠ The work on this enhancement can't begin before the plugin code is merged into main branch!!
Repository: flutter
Issue: Benchmark text rendering in languages not supported by Roboto
Labels: framework,a: typography,perf: speed,P2,team-framework,triaged-framework

Currently, we only benchmark text layout/rendering in Latin script.

Roboto supports Latin, Cyrillic, and some Greek.

We should add benchmark(s) using CJK scripts.

We should investigate whether it would be faster if we specified Noto as the first font to avoid fallback when using CJK scripts.

/cc @goderbauer @jlavrova @jason-simmons fyi
Repository: go
Issue: x/vulndb: consider encoding known false positive paths in reports
Labels: NeedsInvestigation,vulncheck or vulndb

Looking at #51565, this is an obvious case of a false positive. Any package that imports x/text will be immediately marked as vulnerable, since there is a (non-vulnerable) usage of the vulnerable symbol in an `init` function.

This seems like something we should be able to avoid, since it creates noise that is likely to irritate users and maintainers. Possibly including some metadata in the report could help vulncheck ignore these kinds of cases. One option is to include call chain fragments which vulncheck can use to ignore specific chains during analysis. For example in this case any chain terminating in `x/text/cases.init#1 -> x/text/language.MustParse` can be safely ignored, since we know that particular invocation is not vulnerable.

Also, we should look into tooling that detects, or at least surfaces, this kind of issue during report ingestion.

cc @golang/vulndb
Repository: rust
Issue: Recursive call warning does not appear inside a match statement
Labels: C-enhancement,A-lints,T-compiler,C-bug,A-control-flow,L-unconditional_recursion

<!--
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
#[derive(Copy, Clone)]
enum Test {
    ValueA,
    ValueB,
    #[allow(dead_code)]
    Any
}

impl PartialEq for Test {
    fn eq(&self, other: &Test) -> bool {
        match *self {
            Test::Any => true,
            _ => *self == *other,
        }
    }
}

#[allow(dead_code)]
#[derive(Copy, Clone)]
enum Test2 {
    ValueA,
    ValueB,
    Any
}

impl PartialEq for Test2 {
     fn eq(&self, other: &Test2) -> bool {
        *self == *other
    }
}

fn main() {
    let a = Test::ValueA;
    let b = Test::ValueB;
    
    println!("{}", a ==  b);
}
```

[Rust Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=2149b4f78fabc2aa7f99845a1a8af8b4)

I expected to see this happen: the compiler should of warned me that the implementation `PartialEq` for `Test` is recursive.

Instead, this happened: it compiled the implementation for `Test` without warnings and produced a stack overflow. Implementation for `Test2` is included to show that it does produce a warning when the recursive call is made not inside a `match` statement.

Compiler output:

```
 Compiling so v0.1.0 (/home/lev/Projects/so)
warning: function cannot return without recursing
  --> src/main.rs:28:6
   |
28 |      fn eq(&self, other: &Test2) -> bool {
   |      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot return without recursing
29 |         *self == *other
   |         --------------- recursive call site
   |
   = note: `#[warn(unconditional_recursion)]` on by default
   = help: a `loop` may express intention better if this is on purpose

warning: `so` (bin "so") generated 1 warning
```

### 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.59.0 (9d1b2106e 2022-02-23)
binary: rustc
commit-hash: 9d1b2106e23b1abd32fce1f17267604a5102f57a
commit-date: 2022-02-23
host: x86_64-unknown-linux-gnu
release: 1.59.0
LLVM version: 13.0.0
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
    Finished dev [unoptimized + debuginfo] target(s) in 0.16s
     Running `target/debug/so`

thread 'main' has overflowed its stack
fatal runtime error: stack overflow
Aborted
```

</p>
</details>
Repository: next.js
Issue: Since 12.1.0, POST methods are not allowed (but nothing in changelog)
Labels: bug,linear: next

### Verify canary release

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

### Provide environment information

Error: ENOENT: no such file or directory, realpath '/Users/mypath/frontend/info'

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

98.0.87

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

/

### Describe the Bug

I am using Next.js as a proxy for a legacy Symfony server. Since 12.1.0, I have `405 POST method not allowed` when trying to proxy POST routes, but in 12.0.7 it works. I found nothing mentioning this change in the changelog.

### Expected Behavior

No changes between 12.0.7 and 12.1.0

### To Reproduce

In next.config.js:
```
rewrites: () => {
        return {
          fallback: [
            {
              source: '/:path*',
              destination: `${process.env.SYMFONY_URL}/:path*`,
            },
          ],
        };
      },
```

Where SYMFONY_URL points to a server with POST routes that are not implemented by the Next.js server.

Try hitting a POST route.
Repository: TypeScript
Issue: Diagnostic for incompatible overload signature doesn't explain why
Labels: Bug,Help Wanted

# Bug Report

### 🔎 Search Terms

function incompatible overload implementation signature assignability TS2394

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about function overloads

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABAUwB4EMC2AHANsgCjgDdkAnXOdAE2WoC5EBnKMmMAcwEpGW3OA3AFgAUKEiwEKDDnwF00EOlyMwITACNyAGkRxsksAH5GGuHHzowPZq3YdEAb1GJEZZFBBkkAAwAkjgqeygC+AfqGIT7CIiFAA)

### 💻 Code

```ts
function example(overloaded: string): string;
function example(actual: number, option?: boolean): string {
  return `${actual}${option}`;
}
```

### 🙁 Actual behavior

A single line of error message that doesn't indicate which parameter or return type is the issue.

```ts
function example(overloaded: string): string;
//       ~~~~~~~
// Error: This overload signature is not compatible with its implementation signature.
```

### 🙂 Expected behavior

Can we elaborate on that error message with the first assignability issue?

Bikeshedding on the error message specifics welcome...

```ts
function example(overloaded: string): string;
//       ~~~~~~~
// Error: This overload signature is not compatible with its implementation signature.
//   Overload parameter 'overload: string' is not assignable to implementation parameter 'actual: number'.
```
Repository: rust
Issue: Tracking Issue for `Iterator::collect_into`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(iter_collect_into)]`

This is a tracking issue for adding the `collect_into` method to the `Iterator` trait.
`Iterator::collect_into` lets an iterator to be collected into a collection which implements the `Extend` trait, consuming the iterator and adding every of its item to the collection.
Adding this method has also the benefit of making the `Extend` trait more discoverable.

### Public API

```rust
trait Iterator {
    type Item;

    fn collect_into<E: Extend<Self::Item>>(self, collection: &mut E) -> &mut E
    where
        Self: Sized;
}
```

### Steps / History

- [x] Implementation: #93057
- [ ] 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

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- [ ] Is it worth it to have this API? The `Iterator` interface is already pretty large, and use cases can easily be written differently without this API.
    - See https://github.com/rust-lang/rust/pull/93057#pullrequestreview-865694602
    - And https://github.com/rust-lang/rust/pull/93057#issuecomment-1024029073
Repository: godot
Issue: [Bullet] Enabling CCD (Continuous Collision Detection) is broken
Labels: bug,topic:physics,topic:3d

### Godot version

3.4.3.stable, 3.4.4.rc1

### System information

macOS 12, Windows 10

### Issue description

Summary:
CCD can't be disabled via editor on iOS and Windows and can't be enabled on macOS at all

Description:
[Solved] ~~On Windows CCD is enabled even though the check for ```continuous_cd``` is disabled in the editor, the only way to disable it is via code (apparently the editor check is broken or not connected or the value is never assigned)~~
On macOS CCD can't be enabled. Both editor and code won't enable it, even though it's working on iOS and Windows

<img width="291" alt="Screen Shot 2022-03-09 at 14 23 16" src="https://user-images.githubusercontent.com/2546522/157529576-ff991887-9b01-4312-8c99-0a2d7aa62fc1.png">



### Steps to reproduce

Project is attached to test the issues. Just shoot the ball and: 

1. On macOS CCD won't work at all. 
2. [Solved] ~~On Windows click RigidBody and in the editor disable Continuous Cd and it will remain enabled, only disabling it via code will disable it. To disable it via code, click on the root Spatial node and a variable is exposed to control it, or open the script and change the code~~

### Minimal reproduction project

[CCD.zip](https://github.com/godotengine/godot/files/8217894/CCD.zip)
Repository: rust
Issue: Tracking Issue for `#![feature(deprecated_suggestion)]`
Labels: T-libs-api,C-tracking-issue,L-deprecated

Feature gate: `#![feature(deprecated_suggestion)]`

This is a tracking issue for suggested replacements on deprecations. This has been used as part of the `#[rustc_deprecated]` attribute since 2019-01-31. The suggestions are machine-applicable, in that `cargo fix` is capable of making the replacement without further user intervention. As such, the suggestion must be valid Rust (though this is not enforced).

### Public API

```rust
#![feature(deprecated_suggestion)]

struct Foo;

impl Foo {
    #[deprecated(suggestion = "baz")]
    fn bar() {}
    fn baz() {}
}
```

### Steps / History

- [x] Implementation:
  - for `#[rustc_deprecated]` in #58002 (merged 2019-01-31)
  - for `#[deprecated]` in #94635 (merged 2022-03-10)
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

- None yet.
Repository: PowerToys
Issue: Find My Mouse: Deactivation configuration options
Labels: Idea-Enhancement,Needs-Team-Response,Product-Mouse Utilities

### Description of the new feature / enhancement

Allow the user to configure some options regarding what happens AFTER the mouse has been found (ie. the spotlight is on the mouse).
* Allow the deactivation timer to count down if the mouse is moving, but no longer SHAKING
* (bonus) Deactivation time (it currently seems to be 2-3 seconds, but I'm asking to allow the user to configure this)

### Scenario when this would be used?

I'm usually using the Find My Mouse feature because I have 4x 4K monitors and need to see where it is. Almost immediately (usually even as the spotlight is animating in) I can see where the mouse is and want to immediately start using it, however I always find myself shaking to find the mouse, and then frustrated because the spotlight won't go away until I keep it still for the above time limit (or press a key/mouse button). I'd like to be able to start using the mouse immediately (normal movement usage, not shaking, no clicking/etc..) and still have the spotlight timer count down so it'll go away.

### Supporting information

_No response_
Repository: PowerToys
Issue: Awake: Don't display log when started via CLI
Labels: Idea-Enhancement,Product-Awake

### Description of the new feature / enhancement

When Awake is started via the CLI, it shows a log screen with the options that have been used to start it, and this dialog remains on screen:

![image](https://user-images.githubusercontent.com/36198985/157540232-4774cceb-e15b-4f4c-8efd-c5cef3117043.png)

Instead, there should be an option to turn off this screen so that Awake appears in the tray similar to that if it had been started via the Power Toys configuration screen.




### Scenario when this would be used?

This is useful when running Awake in batch/via CLI via task scheduler, since Awake is not always needed 100% of the time.

### Supporting information

_No response_
Repository: pytorch
Issue: Release note bot is not sending messages on PRs anymore
Labels: oncall: releng,triaged

https://github.com/pytorch/pytorch/pull/73961 landed 2 hours ago without any release notes/topic label but the bot didn't message there.

Is that expected?
Repository: godot
Issue: Closing a scene tab using shortcut always re-saves the scene (fixed in `master`)
Labels: bug,topic:editor,usability

### Godot version

3.4

### System information

macOS

### Issue description

Closing a tab by clicking on the X will close it immediately if the scene is already saved. Using the shortcut Shift + Command + W for Close Scene will save the scene again, even if there are no changes, making the process much slower

The problem increases when you are closing multiple tabs since you have to wait for the saving dialog for each tab, so closing several tabs requires more time than it should

### Steps to reproduce

Open multiple scenes and close them using the Close Scene shortcut

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: Lazy: add support for index ops
Labels: triaged,module: lazy

See deleted/unused code https://github.com/pytorch/pytorch/pull/73993

Intend to use codegen for new implementations, but expect it needs updating to handle inplace-only variants
Repository: TypeScript
Issue: JS merge quickinfo is inconsistent
Labels: Bug,checkJs,Domain: Quick Info,Domain: JavaScript

Given [this playground](https://www.typescriptlang.org/play?filetype=js#code/LYewJgrgNgpgdDAHgBxAJwC4GcAEBeHAYygEMtcBhHAbwF8BYAKFElgRXWzgDMA7fHNwi9CGAJYheACgCUNWkA),
```js
module.exports = class C {}
module.exports.fn = function() {}
```
quick info display on hover of `class C` depends on if you hover `module.exports` first or not. If you hover `module.exports` first, it's 
```
(local class) C
module C
```
if you hover `class C` first, _without_ hovering anything else, it's
```
(local class) C
```

The first - the version with `module C` - is the correct one. In the later case, we fail to merge the module and class symbols.
Repository: godot
Issue: CharacterBody: Different Colliders from Mesh Options have unexpected behaviour
Labels: bug,topic:editor,topic:physics,topic:3d

### Godot version

4.0 alpha 3

### System information

Win 10, 5600x, 3060

### Issue description

Concave meshes are not read at all. Convex meshes can either completely tank the performance or cause abnormal behavior (mesh getting stuck at places).

### Steps to reproduce

Take a glb mesh. Generate colliders. Use a characterbody to move over them (I'm yet to try other physics bodies).

### Minimal reproduction project

[CharacterBody3dTest.zip](https://github.com/godotengine/godot/files/8220986/CharacterBody3dTest.zip)
Repository: pytorch
Issue: Inconsistent implementation on SWA
Labels: module: docs,module: optimizer,triaged,actionable

### 🐛 Describe the bug

Why `swa_utils` implement SWA different from the original paper? For example, there is no way to do a cyclical lr schedule to average model, the API only supports annealing the lr from its initial value to a given lr in n epochs, after this, the lr is fixed, different with one may expect.

### Versions

1.10.0

cc @svekars @holly1238 @vincentqb @jbschlosser @albanD
Repository: angular
Issue: Reactive forms cleared input becomes empty string instead of null 
Labels: area: forms,P3

### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

No

### Description

I have created a minimal reproducible sample of the problem here: https://stackblitz.com/edit/angular-ivy-4ltwow

Here you can see the mocked model input (that I receive from server API in the real app) is null at first, but after I edit the value in textbox and clear it, it becomes empty string.

I test this value server side to see if it has changed since before, and empty string is different from null so I have to test the difference from null AND empty string literally everywhere.

I have no alternative other than creating a directive and applying on every text input, but there are literally thousands and if I forget to put only one the problem arises again.

Shouldn't `getRawValue` return null if the input control is blanked? Wouldn't it be possibile to include an option in the form initialization (or a parameter of `getRawValue`) to get this desired behavior?

Thanks! 

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-ivy-4ltwow

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 9.0.2 (but I tested up to Angular 13 and it's the same)
Node: 16.14.0
OS: win32 x64

Angular: 9.0.1
... animations, common, compiler, compiler-cli, core, forms       
... language-service, platform-browser, platform-browser-dynamic  
... router
Ivy Workspace: Yes
```


### Anything else?

_No response_
Repository: create-react-app
Issue:  Could not find a declaration file for module 'history'
Labels: needs triage,issue: bug report

Windows 11 64bit

I just did a fresh install of this app and `npm start` threw the following error:

![image](https://user-images.githubusercontent.com/10029073/157641276-2ed81d56-faa8-4893-b579-4530a932ba86.png)



```
ERROR in src/index.tsx:4:38
TS7016: Could not find a declaration file for module 'history'. 'D:/Design und Development/epam react/my-app/node_modules/history/index.js' implicitly has an 'any' type.
  If the 'history' package actually exposes this module, consider sending a pull request to amend 'https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/history'
    2 | import ReactDOM from 'react-dom';
    3 | import { Router } from 'react-router-dom';
  > 4 | import { createBrowserHistory } from 'history';
      |                                      ^^^^^^^^^
    5 | import { ContextProvider } from '@epam/uui';
    6 | import { Snackbar, Modals } from '@epam/uui-components';
    7 | import { ErrorHandler } from '@epam/loveship';
```
Repository: create-react-app
Issue: Add Vite to the template
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?
Hot Module Replacement (HMR) can be slow in large SPA. Tooling is difficult to configure, example proxy things to a backend API.

### Describe the solution you'd like

[Vite](https://vitejs.dev/) is a front end tooling with lightning fast Hot Module Replacement (HMR).
Instead of recompiling the whole application it just replaces the module that changed, this makes it very fast, especially for larger SPAs resulting in a better developer experience through a faster inner development loop.
Easier configuration with [`vite.config.js`](https://vitejs.dev/config/).