sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: global option to set default floating window border
Labels: enhancement,ui,floatwin,options

### Feature already in Vim?

No

### Feature description

**Why?**
Currently unifying the look and feel of neovim ui is kind of hard to deal with because of absence of such options.

From user perspective if you want something more unique then `single` or `rounded` borders you would need for every plugin that is using floating windows at some point to add few lines of code for controlling (if plugin allows this) its look.

From plugin author perspective you need to make it public such an option (complicate plugin config) instead of something like `nvim_open_win(.... { border = vim.get_float_border() }` and forget about it.

---
Because of `:h api-contract` and some limitation of vim options (can't be real lists or dicts) it's hard to deal with such problem.

<details><summary><b>What I suggest</b></summary>
Not sure if it is the best thing (maybe community/devs can find a better one solution).
Lets introduce two new options and one new function (`vim` or `vim.api`):
- first option is `floatborder` (or you name it) which can be one of already provided options of the border for `nvim_open_win` such as *none, single, double, rounded, solid, shadow* or any others plus one new option named *borderchars*.
- second option is `borderchars` itself with is a comma-separated characters (or maybe something like *fillchars* for more conrol) for the border the same as array for `nvim_open_win()` border option.
- our new function should just from `floatborder` and `borderchars` options generate string or array required for `nvim_open_win()` border option.

So at the end users will just need to change such two options to have the same borders. And plugin authors just to call the function to generate border option when they add `nvim_open_win()` in their plugin.
</details>

Any ideas how to improve this suggestion? What do you think overall about this feature request?

---
**EDIT** as **bfredl** suggested just some lua option like `vim.ui.border_style` seems even less work to implement this and for users and plugin authors to use.
Repository: node
Issue: Disable node_modules lookup for all subpaths of builtin modules
Labels: module

Something else discussed in https://github.com/nodejs/node/pull/44250 that we should consider is making new subpath additions (like any other core module getting `/promises`) allowable as semver-minor. This might be a code change, to ensure that nonexistent subpaths (like `process/promises`) throw rather than try to resolve to something like `node_modules/process/promises`; but once that’s done we should update the docs accordingly.

_Originally posted by @GeoffreyBooth in https://github.com/nodejs/node/issues/44576#issuecomment-1241239416_
Repository: PowerToys
Issue: Press Enter to open windows calculator after doing a calculation
Labels: Idea-Enhancement,Run-Plugin

### Description of the new feature / enhancement

When doing a calculation, I'd like to press enter to open the windows calculator, and have my current Run calculation automatically transferred to the Windows calculator.

### Scenario when this would be used?

When I'm doing a calculation, or a few, and I realise things are a bit more complex I now need the full windows calculator...

This would save me having to stop my Run calculation, and open calculator, and then re-enter my calculation again into the calculator.

### Supporting information

I think this is the way Spotlight on Mac works with calculations.
Repository: pytorch
Issue: primTorch/nvfuser: have a way to check that refs are added to __all__
Labels: feature,triaged,module: nvfuser,module: primTorch

### 🐛 Describe the bug

In primTorch, with regular PyTorch refs, it's easy to check them based on the `_refs` prefix and look them up in `__all__`. For nvfuser-specific ones, it's not yet clear what to do. There's no `__all__` and the prefix is different: `ops.nvprims`.

See https://github.com/pytorch/pytorch/pull/84792 for more context.

### Versions

master

cc @ezyang @mruberry @ngimel @Lezcano @fdrocha
Repository: TypeScript
Issue: Tsdoc of `hmi.System` is shown for `hmi`, too
Labels: Bug,Help Wanted,Effort: Moderate,Domain: Quick Info

# Bug Report


### 🔎 Search Terms

tsdoc, jsdoc, tooltip, intellisense

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries.

### ⏯ Playground Link
[Playground link with relevant code](https://www.typescriptlang.org/play?ssl=7&ssc=2&pln=1&pc=1#code/PQKhAIAkFkElwC4HskBsEEsAO4TALABQAtkgCYCuqAplMRgN7hHjOEC+RoEMsAdAGUAngGcE1YohTpsuAiXJVakeoNHjiDIuyA)

### 💻 Code
```ts
/** HMI tooltip */
module Hmi{ 
  
}
/** HMI.System tooltip */
module Hmi.System{
}
```
### 🙁 Actual behavior
Tooltip over `HMI`
![image](https://user-images.githubusercontent.com/2410353/190383049-6ebf1698-ec9a-4138-b1dd-abfb577b8aa0.png)
### 🙂 Expected behavior
Tooltip of `HMI.System` should not appended to `HMI` in my opinion.
Repository: rust
Issue: Addition does not commute in generic_const_exprs
Labels: C-bug,A-const-generics,requires-nightly,F-generic_const_exprs,requires-incomplete-features

I tried this code:

```rust
#![allow(incomplete_features)]
#![feature(generic_const_exprs)]

// Works!
pub fn append<T: Default, const SIZE: usize>(input: [T; SIZE]) -> [T; SIZE + 1] {
    concat(input, [T::default()])
}

// Fails to compile...
pub fn prepend<T: Default, const SIZE: usize>(input: [T; SIZE]) -> [T; SIZE + 1] {
    concat([T::default()], input)
}

pub fn concat<T, const M: usize, const N: usize>(_: [T; M], _: [T; N]) -> [T; M + N] {
    unimplemented!()
}
```

I expected that both `append` and `prepend` would compile because they evaluate to the same expression.

Instead, I realise that addition does not commute and that you can switch which implementation does not compile by switching `N` and `M`.

I realise that [generic_const_exprs](https://github.com/rust-lang/rust/issues/76560) is still unstable. Just thought I'd add it here for visibility and perhaps to illicit a workaround. It's currently blocking [array_append](https://github.com/LoganDark/array-append) from being used ergonomically.

### Meta
```
$ rustc --version --verbose
rustc 1.65.0-nightly (eaadb8947 2022-08-27)
binary: rustc
commit-hash: eaadb8947b850a025404082f6297766c4680a42a
commit-date: 2022-08-27
host: x86_64-unknown-linux-gnu
release: 1.65.0-nightly
LLVM version: 15.0.0
```
Repository: vscode
Issue: Add version support for published diagnostics
Labels: feature-request,api,languages-diagnostics

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Supporting [versioned diagnostics](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_publishDiagnostics) in VSCode would be quite useful. Diagnostics for some document could replace older diagnostics, according to the version. The editor could also use the version property to move the rendered diagnostic to the correct location if the document has changed since the last collection of diagnostics were published.
Repository: PowerToys
Issue: Different layout of the tree on the left
Labels: Idea-Enhancement,Product-Settings,Area-User Interface,Needs-Triage

### Description of the new feature / enhancement

The tree on the left that lists General and each of the features should be changed.

General should move down to the non-scrollable section that also lists Welcome to PowerToys and Give Feedback.

And then the (currently) 15 features in the scrollable section should be split into two sections: one showing those enabled and one showing those disabled.

### Scenario when this would be used?

I currently use only one of the 15 items, though I plan to test out more in the future.

There's no way for me to know which are currently enabled or disabled without actually clicking into each of the 15 items.

### Supporting information

_No response_
Repository: TypeScript
Issue: Literal strings with generics are inconsistant when strictNullChecks is false
Labels: Needs Investigation,Fix Available

# Bug Report

### 🔎 Search Terms

- string literal
- strictNullChecks
- keyof

### 🕗 Version & Regression Information

It works properly on v4.7.4 but is failing on v4.8.2 and with the nightly build.
It also works normally when `strictNullChecks` is `true`.

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?strictNullChecks=false&ts=4.8.2#code/C4TwDgpgBAsg9gEwgGygXigbygZwFy7ABOAlgHYDmA3FAEYG1xzIQCGZUAvgFAvBRgSAYwDWBADwBpCCBxQIAD2AQyCOSJlwAZrEQoAfAAowROJCLASEfFCJsEcMshBRpsgNoBdAJTp9UAAVhEXF4JGQAGlcZHH1eCH5idhwtOCIAWwkAFSM4WgArAizfNH8s7m4hRxx+OxwAV2RgAEZ0KCSyFLT042DDdwAiHAGfbwqqzv5yZQyIBBJWZTbBUX6hkbGJmttrRuAAJjaOrozDaYhZ+cWIbyA)

### 💻 Code

```ts
type Model = { s: string; b: boolean }
let pick: <Keys extends keyof Model>(properties: readonly Keys[]) => Pick<Model, Keys>
let transform: <T>(obj: T) => T

const result1 = transform(pick(["s"]))

const intermediate = pick(["s"])
const result2 = transform(intermediate)
```

### 🙁 Actual behavior

`result1` has a type of `Pick<Model, keyof Model>` and `result2` as a type of `Pick<Model, "s">`

### 🙂 Expected behavior

`result1` and `result2` should have the same type `Pick<Model, "s">`.
Repository: vscode
Issue: [scss] Wrongly shown selector in SCSS
Labels: bug,help wanted,css-less-scss

![image](https://user-images.githubusercontent.com/62809719/190411204-05aed465-9a88-4818-baa5-a67cc24d4bd7.png)
![image](https://user-images.githubusercontent.com/62809719/190411239-7b51bf43-d89a-4c44-aa4b-928f937dcf95.png)

In the first picture it should also show `<element name="jmeno">` like in the second one.
Repository: flutter
Issue: When I use the trackpad on my macbook, the two-fingered right click doesn't work
Labels: framework,f: gestures,platform-web,a: desktop,has reproducible steps,P2,p: pointer_interceptor,found in release: 3.3,found in release: 3.4,team-framework,triaged-framework

When I use the trackpad on my macbook, the two-fingered right click doesn't work.
```
Scaffold(
  body: InteractiveViewer(
    child: GestureDetector(
      onSecondaryTapUp: (TapUpDetails details) {
        //<==== this is not work!!!!!
        print(DateTime.now());
      },
      onTap: (){
        //<==== but this is work
        print(DateTime.now());
      },
      child: Container(
        width: 500,
        height: 500,
        color: Colors.blue.withOpacity(0.1),
        child: const Center(
          child: Text("xxx"),
        ),
      ),
    ),
  ),
)
```
Repository: PowerToys
Issue: Didn't Detect All Symbols Properly
Labels: Issue-Bug,Priority-2,Product-Text Extractor

### Microsoft PowerToys version

"0.62.0"

### Running as admin

- [X] Yes

### Area(s) with issue?

TextExtractor

### Steps to reproduce

It didn't detect following symbols in the C++ program :
- curly brackets **{ }**
- semi-colon **;** 
- hyphens =  **-** 
- Greater-than sign  **>**


Here is the screenshot of C++ program for testing:
![image](https://user-images.githubusercontent.com/67585828/190426392-c5212232-26c3-421a-ae59-1f2f08d283ed.png)


### ✔️ Expected Behavior

class Student
    public:
        int age;
        const int rollNumber;
        int &x;        // age reference variable

        Student (int r, int age) : rollNumber( r) , age(age), x(this -> age) {
        //rollNumber = r;
        }
};

### ❌ Actual Behavior

class Student
public
int age;
const int rollNumber;
int &x;
// age reference variable
Student (int r, int age)
//r011Number = r;
rollNumber( r) ,
age(age),
x (this age)

### Other Software

_No response_
Repository: PowerToys
Issue: Scaling the mouse cursor based on display scaling
Labels: Idea-Enhancement,Product-Mouse Utilities

### Description of the new feature / enhancement

I want the mouse cursor to scale based on the display scaling factor.
My problem is that on for instance higher dpi smaller monitors where I put scaling 125% (to get a fairly uniform user interface experience), the mouse cursor is very small since it's not also being scaled up.
This can make the cursor hard to locate on the screen, which can harm productivity wasting time locating the cursor.

### Scenario when this would be used?

On multi-screen setups with different display scalings.

### Supporting information

_No response_
Repository: opencv
Issue: G-API: Provide API to configure IE backend.
Labels: category: g-api / gapi

# Design proposal
## Introduction
OpenVINO provides API for specifying input/output nn model characteristics such as: `Precision`, `Layout`, particularly for `input` it's also possible to specify if some `preprocessing` should be applied. This characteristics are individual per `input` or `output` and configurable via: [IE::Data](https://docs.openvino.ai/latest/classInferenceEngine_1_1Data.html).
## Motivation
To make user's life easier `G-API` configure `OpenVINO` with following behavior:
1. `Precision` for every input layer set automatically to type that came as graph input meta. https://github.com/opencv/opencv/blob/4.x/modules/gapi/src/backends/ie/giebackend.cpp#L1076
2. `Layout` for every input layer calculated based on this:
2.1 Check if input either `IMAGE` or `TENSOR`: 
https://github.com/opencv/opencv/blob/4.x/modules/gapi/src/backends/ie/giebackend.cpp#L138
2.2 In case `IMAGE` it will be always `NHWC`.
2.3 In case `TENSOR` it will be decided based on number of dims: https://github.com/opencv/opencv/blob/4.x/modules/gapi/src/backends/ie/giebackend.cpp#L96
3. Output `Precision`/`Layout` is impossible to configure at all. They're left by default.

Based on this behavior there are several flaws:
1. Multi-dim (dim == 4) `cv::Mat` is always treated as `NCHW` and there is no any chance to specify `NHWC` instead.
2. Multi-dim (dim == 2) `cv::Mat` is always treated as `NC` and there is no any chance to specify `HW` instead.
3. `Precision`/`Layout` for output layers impossible to configure. It might slightly improve performance if user let's say wanna receive `FP16` output data without conversion performed on `OpenVINO` side.

## Proposal
Actually proposal is simple, introduce following handles inside `cv::gapi::ie::Params` structure:

API Example:
```
cv::gapi::ie::Params(...).cfgInputLayout('input0', 'NCHW')
                         .cfgOutputPrecision('output0', 'FP16')
                         .cfgOutputLayout('output0', 'NCHW')
                         .cfgOutputPrecision('output1', 'FP16')
                         .cfgOutputLayout('output1', 'NCHW')
```
Another idea is use `CV_*` enums to specify precision:
```
cv::gapi::ie::Params(...).cfgOutputPrecision(CV_16F) // set all output layers precision to ie::FP16
```
I'd suggest using `string` as type for `Layout` (probably for Precision)
1. OV2.0 uses strings: https://docs.openvino.ai/latest/openvino_docs_OV_UG_Layout_Overview.html
2. It doesn't require extra `enum`'s on `G-API` side. 
3. Easy adopt to python
Repository: storybook
Issue: Vue3 no longer exports app in 7.0-alpha
Labels: bug,vue3

This commit removes the `app` export from `@storybook/vue3`:

https://github.com/storybookjs/storybook/commit/24251e27f1233a568fd441df65af3355d89cf0f5#diff-63c4fc9feba520d3505ec8a6796e7d0576ef804b6f92d68ae8b8c2e64f18264c

We should try to restore it so that users can use it to add global components and directives.
Repository: pytorch
Issue: reentrant torch.utils.checkpoint does not work with NamedTuple outputs
Labels: high priority,triage review,oncall: distributed,module: checkpoint

### 🐛 Describe the bug

The reentrant (default) version of torch.utils.checkpoint does not work with NamedTuple outputs, it instead returns back a regular tuple so the outputs cannot be accessed via their original names. For a repro, see:

```
import torch
from torch.utils.checkpoint import checkpoint

from collections import namedtuple

Tup = namedtuple("Tup", "a b c")

tup = Tup(torch.ones(10, requires_grad=True), torch.ones(10, requires_grad=True), torch.ones(10, requires_grad=True))

def foo(tup):
	return Tup(tup.a + tup.b, tup.b, tup.a + tup.b + tup.c)

import pdb ; pdb.set_trace()
out = checkpoint(foo, tup, use_reentrant=False)
```

### Versions

main

cc @ezyang @gchanan @zou3519 @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @kwen2501
Repository: flutter
Issue: iOS 16 text selection menu unit converter
Labels: a: text input,framework,a: fidelity,f: cupertino,c: proposal,P3,team-design,triaged-design

The iOS 16 text selection menu has a built-in unit converter:

![image](https://user-images.githubusercontent.com/389558/190458753-dcfb6922-0fb1-4651-845c-3728d15ca477.png)

### Flutter implementation

This is very similar to the ["email button" demo](https://github.com/flutter/flutter/pull/107193/files#diff-c37e45d149cf86a6565f1eb32f738d5faaf4170b8bd4f1f6421651f0af2f1bfa) that I wrote with the new context menu system.  If we can write something that correctly identifies convertable strings and their conversions then it should be easy to implement in the context menu.

### Reference
  * An article that mentions this feature:
    - https://www.macstories.net/stories/ios-16-the-macstories-review/14/#content
  * Issue about all missing context menu buttons:
    - https://github.com/flutter/flutter/issues/107578
Repository: pytorch
Issue: Memoizing AOT Autograd Input Conversion Breaks Training with Tied Parameters
Labels: triaged,module: functorch

### 🐛 Describe the bug

AOT Autograd converts inputs to a new set of TensorImpls, either by converting them to fake tensor or by detaching the tensors and then adding back in the gradient `x.detach().requires_grad_(x.requires_grad)`.

When that conversion is memoized, so that two tied parameters are converted to the same FakeTensor/Detached Tensor, models with tied parameters fail. You can replicate this failure:

```
diff --git a/functorch/_src/aot_autograd.py b/functorch/_src/aot_autograd.py
index 6bb4401784..74c2577c73 100644
--- a/functorch/_src/aot_autograd.py
+++ b/functorch/_src/aot_autograd.py
@@ -435,8 +435,14 @@ def create_aot_dispatcher_function(
                 # (resnet50_quantized_qat and mobilenet_v2_quantized_qat)
                 # because they use a "running-mean" style op that requires
                 # resizing the running counter buffers stored on the module.
+                seen = {}
+
                 def make_input(x):
-                    return x.detach().requires_grad_(x.requires_grad)
+                    if id(x) in seen:
+                        return seen[id(x)]
+                    out = x.detach().requires_grad_(x.requires_grad)
+                    seen[id(x)] = out
+                    return out
```

and by running in torchdynamo 
```python benchmarks/huggingface.py --ci -d cuda --float32 --backend=aot_nop --training --only=RobertaForCausalLM```

We would like to memoize the the conversion and reflect shared identities of Parameters so that inplace metadata mutations are reflected on tied parameters. We need to fix the tied parameter gradient issue to do so. 

### Versions

master

cc @zou3519 @Chillee @samdow @soumith
Repository: node
Issue: Requiring a dynamically added dependency fails when the package has no `index.js` file
Labels: module,esm

### Version

v7.1.0 and newer (last working version was v6.17.1)

### Platform

Linux

### Subsystem

_No response_

### What steps will reproduce the bug?

Require a dependency that doesn't exist. Catch the error. Dynamically add the missing package to the node_modules. It should not contain an `index.js` file but should use a custom entry point instead. Require the now not missing package again.

Expected result: the modules is loaded.
Actual result: module not found error is thrown.

I have create a repro repo: https://github.com/zkochan/require-issue


### How often does it reproduce? Is there a required condition?

_No response_

### What is the expected behavior?

_No response_

### What do you see instead?

On the second require the module is loaded

### Additional information

cc @GiladShoham @davidfirst
Repository: flutter
Issue: Output for small differences in golden tests is misleading.
Labels: a: tests,framework,c: proposal,P3,team-framework,triaged-framework

## Use case
For golden test failures where there is a very small difference between the running test and the golden file, the output currently says "0.00% diff detected". While the test _does_ error out correctly, the output makes it feel more like an error with the framework instead of a valid test failure.

## Proposal
Update the output when failing at small margins like this to show a non-zero value. Current ideas:

* Round to the first non-zero digit. This will potentially make the output longer, but will make sure there's always a non-zero value.
* If rounding would output "0.00%", instead output "X pixels did not match" or similar
* If rounding would output "0.00%", instead output "a small diff was detected" or similar
Repository: flutter
Issue: Bot doesn't recognize multi-line comments as test-exempt
Labels: a: annoyance,team-infra,P3,triaged-infra

# From https://github.com/flutter/flutter/pull/111623
A PR that was submitted only made changes to comments and the auto-submit bot commented on the post complaining that the PR was not tested. Is it possible for the bot to see that the diff only contains changes to comments?

From [Tree Hygiene](https://github.com/flutter/flutter/wiki/Tree-hygiene#how-to-review-code)
> * only remove code (no modified or added lines) to remove a feature or remove dead code. (Removing code to fix a bug still needs a test.)
> * **only affect comments (including documentation).**
> * only affect code inside the .github directory, .cirrus.yml or .ci.yaml config files.
> * only affect .md files.
> * are generated by automated bots (rollers).
> * have an explicit exemption (a message from Hixie starting with test-exempt:).