sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: proposal: x/crypto/ssh: export structured disconnect message / reason error
Labels: Proposal,Proposal-Crypto

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.3 linux/amd64
</pre>

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/jayschwa/.cache/go-build"
GOENV="/home/jayschwa/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/jayschwa/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/snap/go/5759"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/snap/go/5759/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/jayschwa/golang-crypto/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build549371117=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### Proposal

The SSH protocol defines disconnect reason codes in [section 11.1 of RFC 4253](https://tools.ietf.org/html/rfc4253#section-11.1). I have an application where I want to inspect the disconnect reason code. I currently do this by checking the error string, but this is considered a bad practice.

Internally, the `x/crypto/ssh` package contains a `disconnectMsg` error type that is the structured form of the disconnect reason data. However, that type is not exposed externally for use with a function such as `errors.As`. I propose that `disconnectMsg` (or something like it) be exported so that users may unwrap the error and inspect the reason code.
Repository: terminal
Issue: Using Windows+Shift+(arrow key) to move Terminal between monitors with different scaling ratios causes incorrect resize of the window
Labels: Help Wanted,Issue-Bug,Area-UserInterface,Product-Terminal,Priority-3

# Environment

```none
Windows build number: 10.0.18363.836
Windows Terminal version (if applicable): 1.0.1401.0
```

# Steps to reproduce

Two monitors in the environment: One is 4K resolution, scaling ratio 200%; the other is 1080p resolution, scaling ratio 100%
The 4K monitor is the default monitor.

Open Windows Terminal.  It opens on the 4K monitor.
Use "Windows+Shift+right arrow" to move it to the 1080p monitor.

# Expected behavior

Windows Terminal should show up on the 1080p monitor with the same number of rows and columns as it had when it was on the 4K monitor.  (This is what happens if you *drag* it over.)

# Actual behavior

Windows Terminal has been sized down and has half of the rows and columns that it had before the move.
Repository: angular
Issue: Using directive in ICU in Ivy is not allowed, and the error message is really vague
Labels: help wanted,area: i18n,hotlist: error messages,freq1: low,hotlist: google,type: confusing,P4

<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅

Oh hi there! 😄

To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.

🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->


# 🐞 bug report

### Affected Package
@angular/compiler?


### Is this a regression?
No

### Description

<!-- ✍️--> A clear and concise description of the problem...
Ivy disallows using directives in ICU

```html
<span i18n>Updated: {minutes, plural,
  =0 {just now}
  =1 {one <b custom-directive>minute</b> ago}
  other {{{minutes}} minutes ago by {gender, select, male {male} female {female} other {other}}}}
</span>
```

Will compile, but produce the following error in run-time:

```
InvalidCharacterError: Failed to execute 'setAttribute' on 'Element': '[custom-directive]' is not a valid attribute name.
```

This is misleading, better message would be something like 
```
Directive [custom-directive] is not allowed in ICU
```
Or something similar

## 🔬 Minimal Reproduction

* Enable Ivy
* Create an empty custom directive
* Try using it in a template inside of ICU

<!--
Please create and share minimal reproduction of the issue starting with this template: https://stackblitz.com/fork/angular-issue-repro2
-->
I couldn't find how to enable Ivy in stackblitz

<!--
If StackBlitz is not suitable for reproduction of your issue, please create a minimal GitHub repository with the reproduction of the issue.
A good way to make a minimal reproduction is to create a new app via `ng new repro-app` and add the minimum possible code to show the problem. 
Share the link to the repo below along with step-by-step instructions to reproduce the problem, as well as expected and actual behavior.

Issues that don't have enough info and can't be reproduced will be closed.

You can read more about issue submission guidelines here: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-submitting-an-issue
-->

## 🔥 Exception or Error
<pre><code>
<!-- If the issue is accompanied by an exception or an error, please share it below: -->
<!-- ✍️-->

</code></pre>


## 🌍  Your Environment
Angular 9+ with Ivy
Repository: excalidraw
Issue: [grouping] selected and editing groups should be shared in collaborative mode
Labels: collaboration,grouping
Repository: rust
Issue: Tracking Issue for Extend::{extend_one,extend_reserve}
Labels: A-collections,T-libs-api,B-unstable,C-tracking-issue,A-iterators,Libs-Tracked

This is a tracking issue for the trait methods `Extend::extend_one` and `extend_reserve`.
The feature gate for the issue is `#![feature(extend_one)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also uses as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

- [x] Implement the API
- [x] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions

- Are these method names appropriate?
  - Note that `Extend` is in the prelude, so the explicit `extend_` prefix avoids ambiguity.
- Is `Extend` the best place for just methods?
  - One goal is to improve `Iterator::unzip`, which only has `Default + Extend`, so there's not really much choice.

### Implementation history

- Initial implementation in #72162.
Repository: terminal
Issue: Access keys for new tab drop down menu items
Labels: Issue-Feature,Help Wanted,Area-UserInterface,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement
Currently, bringing up the new tab drop down requires using arrow keys to move to each option. It would make accessibility easier if users could press access keys that correlate with each entry to jump to that entry or cycle through similarly identified entries.

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
One possible solution:
If the menu looks like the following,
* **P**owerShell
* **C**ommand Prompt
* **P**SCore
* <hr>
* **S**ettings
* **F**eedback
* **A**bout

It would be helpful if a user could press `p` twice to select "PSCore" or `c` once to select "Command Prompt".  This may be doable simply by setting `AccessKey` for each `MenuFlyoutItem` in `TerminalPage::_CreateNewTabFlyout`.

Another possible solution would be to support `_` syntax, mirroring WPF's implementation in the config JSON's profile names.
Repository: bitcoin
Issue: build: Investigate aarch64 pointer authentication
Labels: Build system

This would entail adding `-mbranch-protection=standard` to our hardening flags. We should also check if this feature requires kernel/glibc support that our ABI doesn't include.

More info: https://fedoraproject.org/wiki/Changes/Aarch64_PointerAuthentication
Repository: flutter
Issue: InteractiveViewer overscroll
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

InteractiveViewer, introduced in https://github.com/flutter/flutter/pull/56409, should allow an overscroll feature in both directions when its boundary is reached.  Google Photos and Apple Photos both have this feature after zooming in slightly on a photo.  This is also mentioned in https://github.com/flutter/flutter/issues/20175.

Edit: Also, the physics involved should probably be configurable, similar to how it's possible to pass in scroll physics to a scroll view.
Repository: TypeScript
Issue: Comment directive activated when longer string used
Labels: Bug

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
     Done.
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
     Done.

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  typescript@4.0.0-dev.20200526
**NodeJS Version:** v12.16.2
**Visual Studio Code:** 
```text
Version: 1.45.1 (system setup)
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:27:35.169Z
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 6.1.7601
```
<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** comment directive, @ts-ignore

**Code**

```ts
let obj = { }
// @ts-ignoreThisShouldNotMatchButItDoes
console.log( `obj.a = ${obj.a}` )
```

**Expected behavior:**
Property 'a' does not exist on type 'object'.ts(2339)

**Actual behavior:**
compile time: no 2339 error or indication in VS Code
run time: obj.a = undefined

**Description**
Visual Studio code and running tsc will produce error 2339 when the comment directive is removed. When adding in the comment `// @ts-ignore` both Visual Studio code and tsc will ignore the error. However, misspelling `ts-ignore` as `ts-ignoree` or `ts-ignoreThisShouldNotMatchButItDoes` will invoke the `@ts-ignore` directive and ignore the error.

I didn't test other directives to see whether they had similar issues... trying to keep things simple, but this issue could be symptomatic of all comment directives, assuming they re-use the same code for parsing.

**Playground Link:** https://www.typescriptlang.org/play/?target=6&jsx=0&ssl=2&ssc=13&pln=2&pc=41#code/DYUwLgBA9gRgVhAvBA3hAvgKAPTYgATAGcBaASwHMA7KAJxABUALMogZSagFdgATAOShgAsgEMwAYyYAhLmACSYACJQQRTBKhUiUUADpgUCgAoIAA1hw9opBAAkKS9fRmIASkxA

**Related Issues:** None that I could find. Searched under @ts-ignore, comment directive
Repository: vscode
Issue: Bulb menu should open immediately after clicking on the info icon in the problems view
Labels: feature-request,error-list

<!-- ⚠️⚠️ 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. -->

When working through large no.s of lints in the 'problems' pane I use the quick fix bulb to rapidly fix many trivial errors.

This process is slowed down by how the 'quick fix bulb' appears and then disappears.
The process I used to apply these fixes is:
Open the 'problems pane'.
click on the line
wait for the bulb to appear
click the bulb
select the action.

The problem is that the bulb will appear and then disappear before re-appearing.
It also changes color from white to yellow (which I'm sure indicates something but I've not worked it out as yet).
My preferred operation would be:
click line
click 'info' icon.
The code then looks for quick fixes and displays the menu.

This would eliminate the slight delay in having to wait for the bulb to appear.

![May-26-2020 14-38-21](https://user-images.githubusercontent.com/1078012/82907572-af98f280-9f5e-11ea-9fe5-9b038493f965.gif)
Repository: rust
Issue: Suggest importable type that differs only in capitalization
Labels: C-enhancement,A-diagnostics,T-compiler,A-suggestion-diagnostics,D-papercut

```rust
struct S {
    m: Hashmap<String, ()>,
}
```

```console
error[E0412]: cannot find type `Hashmap` in this scope
 --> src/main.rs:2:8
  |
2 |     m: Hashmap<String, ()>,
  |        ^^^^^^^ not found in this scope
```

If the code had been written with `HashMap` instead of `Hashmap`, we would get the following extremely likely correct suggestion:

```console
error[E0412]: cannot find type `HashMap` in this scope
 --> src/main.rs:2:8
  |
2 |     m: HashMap<String, ()>,
  |        ^^^^^^^ not found in this scope
  |
help: consider importing one of these items
  |
1 | use std::collections::HashMap;
  |
1 | use std::collections::hash_map::HashMap;
  |
```

`Hashmap` is a fairly common capitalization in other languages (https://grep.app/search?q=Hashmap&case=true) so it would be good to provide an appropriate suggestion in this case.

(For whatever reason this doesn't trigger #72640.)

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: opencv
Issue: opencv.js 4.x cannot new ORB/AKAZE with enum argument
Labels: category: javascript (js)

##### System information (version)
- OpenCV => 4.x (4.0, 4.1, 4.2, 4.3 checked)
- Operating System / Platform => Mac Mini, Chrome 81.0.4044.138
- Compiler => Non, using "https://docs.opencv.org/4.x.0/opencv.js"

##### Detailed description
When I new ORB/AKAZE with enum argument, got error: 

`UnboundTypeError: Cannot construct AKAZE due to unbound types: N2cv5AKAZE14DescriptorTypeE`

and

`UnboundTypeError: Cannot construct ORB due to unbound types: N2cv3ORB9ScoreTypeE`

No problem without arguments.
```javascript
// no error
new cv.ORB();
new cv.AKAZE();
```

##### Steps to reproduce

after loaded, code in console:
```javascript
orb = new cv.ORB(500, 1.2, 8, 31, 0, 2, cv.ORB_HARRIS_SCORE, 31, 20);
```
```javascript
akaze = new cv.AKAZE(cv.AKAZE_DESCRIPTOR_MLDB, 0, 3, 0.001, 4, 4, 1);
```

##### Issue submission checklist

 - [x] I report the issue, it's not a question
   <!--
   OpenCV team works with answers.opencv.org, Stack Overflow and other communities
   to discuss problems. Tickets with question without real issue statement will be
   closed.
   -->
 - [x] I checked the problem with documentation, FAQ, open issues,
       answers.opencv.org, Stack Overflow, etc and have not found solution
   <!--
   Places to check:
   * OpenCV documentation: https://docs.opencv.org
   * FAQ page: https://github.com/opencv/opencv/wiki/FAQ
   * OpenCV forum: https://answers.opencv.org
   * OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
   * Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
   -->
 - [x] I updated to latest OpenCV version and the issue is still there
   <!--
   master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
   OpenCV team supports only latest release for each branch.
   The ticket is closed, if the problem is not reproduced with modern version.
   -->
 - [x] There is reproducer code and related data files: videos, images, onnx, etc
   <!--
   The best reproducer -- test case for OpenCV that we can add to the library.
   Recommendations for media files and binary files:
   * Try to reproduce the issue with images and videos in opencv_extra repository
     to reduce attachment size
   * Use PNG for images, if you report some CV related bug, but not image reader
     issue
   * Attach the image as archite to the ticket, if you report some reader issue.
     Image hosting services compress images and it breaks the repro code.
   * Provide ONNX file for some public model or ONNX file with with random weights,
     if you report ONNX parsing or handling issue. Architecture details diagram
     from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
   -->
Repository: opencv
Issue: The virtual_try_on.py  can change C++？
Labels: feature,category: samples,category: dnn


- OpenCV => 4.3
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017


##### Detailed description
The virtual_try_on.py  can change C++？
Repository: pytorch
Issue: PyTorch Issue w/ GPU
Labels: needs reproduction,module: cuda,triaged

Hi,

My python code crash after I call 'backward()' method only in GPU mode, in CPU mode it works well.

This is my setup:
 - - - -
1. GPU Device - NVIDIA GeForce RTX 2060 Super
2. Cuda - 10.2.89.441.22 (Display Driver 441.22)
3. Operation System - Windows 10 64 Bit (Ver 1903 OS Build 18362.836)
4. Python 3.8 64 Bit
5. PyTorch Version 1.5.0

I installed the PyTorch module through pip using the link generated by PyTorch.org (The link was generated by the pytorch.org generator according to my setup specifications)

* P.S - is_cuda_available() returns true


cc @ngimel
Repository: flutter
Issue: Debug console only display log from print()
Labels: platform-ios,tool,P3,team-ios,triaged-ios

Problems: no exceptions or debug logs shown in console, only log from `print()` is being shown, similar to [41133](https://github.com/flutter/flutter/issues/41133)

Tested on:
- iPhone 5S iOS
- iPhone X
- iPhone 7

those device using iOS version 13

flutter doctor -v
```
[✓] Flutter (Channel master, 1.19.0-2.0.pre.143, on Mac OS X 10.15.4 19E287, locale en-US)
    • Flutter version 1.19.0-2.0.pre.143 at /Applications/development/mobile/flutterSDK/flutter
    • Framework revision 9d58a87066 (4 days ago), 2020-05-22 22:37:01 -0700
    • Engine revision 9ce1e5c5c7
    • Dart version 2.9.0 (build 2.9.0-10.0.dev 7706afbcf5)

 
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at /Users/berkatbejana/Library/Android/sdk
    • Platform android-29, build-tools 29.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.4.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.4.1, Build version 11E503a
    • CocoaPods version 1.9.0

[✓] Android Studio (version 3.6)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 45.1.1
    • Dart plugin version 192.8052
    • Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)

[✓] Connected device (1 available)
    • iPhone • 2295cce0eb128bb1d06c2b1eee522a1de3a7c6f7 • ios • iOS 13.3.1
```
Repository: TypeScript
Issue: Language service doesn't suggest global variables
Labels: Bug,Domain: Completion Lists

Re-exporting global variables overwrites suggestions of global variables.

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.7.x-dev.20200526

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
// global.ts
const global: typeof globalThis = void 0
  || typeof globalThis !== 'undefined' && globalThis
  || typeof self !== 'undefined' && self
  || Function('return this')();
export = global;
// module.ts
Obj
```

**Expected behavior:**
Language service suggests the `Object` variable defined as a global variable and the `Object` variable exported from global.ts.
**Actual behavior:**
Language service suggests the duplicate two `Object` variables exported from global.ts.
**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** #36468 #35478
Repository: rust
Issue: Missed optimization: Option<fieldless enum> equality
Labels: I-slow,C-enhancement,T-compiler,C-optimization

This is similar to #49892, but different.
It's not limited to non-zero integer types. This happens for any types that have holes but no uninitialized bits.
I think comparing `Option<some fieldless enum>` values is not uncommon, so it adds to the severity of the issue.

### To reproduce
1. Create the following program:
    ```rust
    pub fn eq(x: Option<bool>, y: Option<bool>) -> bool {
        x == y
    }
    ```
2. Inspect generated code, for example by running
    ```
    cargo rustc --release --lib -- --emit asm -Cllvm-args=--x86-asm-syntax=intel
    ```
    Or just visit [godbolt](https://godbolt.org/z/XYaWdR).

### Expected result

```asm
eq:
        cmp     dil, sil
        sete    al
        ret
```

### Actual result

```asm
eq:
        cmp     dil, 2
        sete    al
        cmp     sil, 2
        setne   cl
        cmp     al, cl
        je      .LBB0_1
        mov     al, 1
        cmp     dil, 2
        je      .LBB0_5
        cmp     sil, 2
        je      .LBB0_5
        test    dil, dil
        sete    cl
        test    sil, sil
        setne   al
        xor     al, cl
.LBB0_5:
        ret
.LBB0_1:
        xor     eax, eax
        ret
```


### Meta
This happens both on 1.43.0 stable and on the recent nightly:

```
> rustc --version --verbose
rustc 1.45.0-nightly (8970e8bcf 2020-05-23)
binary: rustc
commit-hash: 8970e8bcf6153d1ead2283f1a0ed7b192230eca6
commit-date: 2020-05-23
host: x86_64-pc-windows-msvc
release: 1.45.0-nightly
LLVM version: 10.0
```