sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/wiki,cmd/go: document how to fetch private repos with Yubikey SSH authentication
Labels: Documentation,help wanted,NeedsFix,modules

From the changelog of Go 1.17, I see:

```
Password prompts

The go command by default now suppresses SSH password prompts and Git Credential Manager prompts when fetching Git repositories using SSH, as it already did previously for other Git password prompts. Users authenticating to private Git repos with password-protected SSH may configure an ssh-agent to enable the go command to use password-protected SSH keys. 
```

I use private repos with SSH and have correctly set up my `.netrc` and all. I use a yubikey with PIN for SSH authentication.

**Go 1.16 behavior**

I try and get a lib / run `go mod vendor`, the git client will prompt me for my yubikey PIN in order to authenticate with the remote server, once I enter it correctly, it all works well. (EDIT: Probably the SSH client which git calls, but either way, it worked fine)

```
go mod vendor
Enter PIN for 'PIV Card Holder pin (PIV_II)': 
Enter PIN for 'PIV Card Holder pin (PIV_II)': 
Enter PIN for 'PIV Card Holder pin (PIV_II)': 
go: downloading gitlab.com/[redacted]
go: downloading gitlab.com/[redacted]
go: downloading gitlab.com/[redacted]
```

Note: There are multiple prompts, I enter my pin for each one.


**Go 1.17 behavior**

I try and run go mod vendor or something, and it will fail with this:

```
go: gitlab.com/[redacted]: invalid version: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /home/raghu/go/pkg/mod/cache/vcs/[redacted]: exit status 128:
	git@gitlab.com: Permission denied (publickey,keyboard-interactive).
	fatal: Could not read from remote repository.
	
	Please make sure you have the correct access rights
	and the repository exists.
```

I am 99% sure this is due to the change in Go 1.17 to disable "password prompts", since if I revert to Go 1.16 all works as expected. 

I am able to use my Yubikey w/ PIN prompt for Git and other SSH stuff just fine. The changelog suggests using an ssh-agent for password-protected keys, but in my case, the key resides on my Yubikey, and I need to enter the pin in order to perform cryptographic operations with it. Since the key is not accessible, I cannot cache it within SSH agent. (Additionally, I do not want to cache my yubikey pin).

This change introduces in Go 1.17 seems like a nerf to security, since for SSH repos, it seems to force you to have an SSH key which is cached by ssh-agent.

If there is no way to disable this with a flag on my end or something, I think it should be reverted for Go 1.18, as @bcmills suggested it is being "given a try" in Go 1.17 - https://github.com/golang/go/issues/44904#issuecomment-830978943
Repository: vscode
Issue: Provide a extension api option to set the word-wrap state of a document upon opening.
Labels: feature-request,editor-api

<!-- ⚠️⚠️ 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. -->
As an extension developer, I would like to have my extension open and show my user a document to edit with the word wrap 'already toggled' on. (Similar to having toggled word-wrap with [alt+z] right after having opened a file in an editor with focus on it)

Simply opening and displaying a file in an editor for the user is easy with vscode.workspace.openTextDocument( some_uri ) and / or vscode.window.showTextDocument( the_document, options )  But the options of showTextDocument **do not allow to provide a starting word-wrap state** - only viewColumn, preserveFocus, preview and selection range.

Since I know the alt-z 'toggle word wrap' command exists, (that's what I'm trying to prevent the user from having to do in those specific cases for my extension) I'm tempted to think it would be possible have the word-wrap state offered as an option when opening a document with the extension API, for the user to have it in an editor already toggled on (or off). 

_Use case: my extension displays some files to the user, sometimes it would be nice to show it with word wrap turned on, sometimes off. I know about specific filetype configurations which could set wrap states for specific file types, but my extension does so with abstract/arbitrary filetypes. (for some documentations files where wrapping is desired.)_

Sorry for my english (second language) & Thanks for reading my feature request! 

(edit: typo)
Repository: go
Issue: crypto/x509: wrong result checking signature of CSR with unordered multi-value RDN
Labels: NeedsDecision

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### 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/adriano/.cache/go-build"
GOENV="/home/adriano/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/adriano/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/adriano/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/lib/go-1.17"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go-1.17/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17.1"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
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-build274131833=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

I checked the signature of a CSR (Certificate Signing Request) via the CertificateRequest.CheckSignature() method.

Here is the CSR:
[problem-csr-20211109.txt](https://github.com/golang/go/files/7518645/problem-csr-20211109.txt)

Link to a runnable program:   https://play.golang.org/p/R7hiD6-HmXm
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?

I expected to get a **negative** result, as the signature on the attached CSR (also embedded in the example program) was not computed according to RFC2986. In particular, the attached CSR contains an unordered multi-value RDN, that is an unordered SET OF, in its Subject field, and this was apparently ignored when the CSR was generated (RFC2986 requires DER-encoding the certificationRequestInfo component prior to signing it). So the signature, although it's cryptographically correct, was computed over the wrong data, and I'd expect a CSR validator to detect that.

A number of other tool(kit)s report the signature as **invalid**, which IMO is the correct result, including **GnuTLS** and **BouncyCastle**.

### What did you see instead?

I got a positive result.
Repository: pytorch
Issue: Upgrade NCCL2.11.4 in the new PyTorch
Labels: module: cuda,triaged

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->

Upgrade  NCCL 2.11.4 in the next version of PyTorch
## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->

Only NCCL 2.11.4 + supports WSL2 (this is also described in NVIDIA's official documents, https://docs.nvidia.com/cuda/wsl-user-guide/index.html ）. Now, if WSL2 users want to use NCCL, they need to download the source code of pytorch to recompile, which takes a lot of time, and there are still many uncertainties in the compilation process, which can not ensure success. Therefore, it is necessary for WSL2 users to upgrade NCCL 2.11.4 in the next version.
## Pitch

<!-- A clear and concise description of what you want to happen. -->
The next version of PyTorch (perhaps version 1.11 or 1.10.1?) integrate NCCL2.11.4
## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @ngimel
Repository: node
Issue: Usage of Oilpan / V8 C++ Garbage Collector
Labels: c++,memory

I have recently read the article about Olipan: https://v8.dev/blog/oilpan-library.

It might be worthwhile investigating if it's something we could use inside Node.js C++ internals to simplify some of our memory management and wrapping logic.
Repository: youtube-dl
Issue: How Download Multi Part of Serie in oreilly with Medium quality
Labels: question

How Download Video Serie in oreilly with Small quality?

When Normal Start Download HQ Quality! but need small quality. How i can set download for Medium quality?
Repository: vscode
Issue: GitHub - auth broken
Labels: bug,git

<!-- ⚠️⚠️ 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?: Local part yes, containers with `ms-vscode-remote.remote-containers`

<!-- 🪓 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:
![image](https://user-images.githubusercontent.com/39068198/141293298-5ce82757-da00-4330-8ad0-976392591509.png)
and 
![image](https://user-images.githubusercontent.com/39068198/141293397-6dc07f1b-07b1-45a9-91c2-0295c218dab1.png)

- OS Version:
![image](https://user-images.githubusercontent.com/39068198/141293596-267eb0d7-baea-4727-b423-d18e8e771a0c.png)

### Steps to reproduce

1. Remove GitHub from trusted extensions.
1. Open integrated console.
1. Run git command that requires authentication (e.g. git clone/fetch from private repository).

### Expected behavior
![image](https://user-images.githubusercontent.com/39068198/141294076-dedcd61a-6f73-4d08-a969-e64ef7921bde.png)
When accepted the browser should open with the authentication request.

### Actual behavior

**In `vscode` locally:** Instant prompt as expected.

**In `vscode` on devcontainer:**
![image](https://user-images.githubusercontent.com/39068198/141294877-897e94e9-f46f-4a62-9cdc-0a9056f79bac.png)
And then it hangs forever.

**In `vscode-insiders` locally:**
![image](https://user-images.githubusercontent.com/39068198/141295123-a3b19516-a448-4d53-aceb-e82ed19d8d4c.png)

**In `vscode-insiders` on devcontainer:**
![image](https://user-images.githubusercontent.com/39068198/141296573-b64b8fd7-8bec-49a1-a184-821c6d397026.png)
And then it prompts as expected.
Repository: rust
Issue: When try_from argument isn't borrowed but should be, the compiler doesn't suggest borrowing
Labels: A-diagnostics,T-compiler

# Steps to reproduce

1. Clone https://github.com/hsivonen/icu4x
2. Switch to branch `with-borrow`
3. `cargo build` (this should succeed)
4. Switch to branch `without-borrow` (differs from `with-borrow` by one missing borrow)
5. `cargo build`

The current output is:

```
error[E0277]: the trait bound `CodePointTrie<'_, u32>: From<TomlCodePointTrie>` is not satisfied
   --> provider/uprops/src/canonical_decompositions.rs:55:20
    |
55  |         let trie = CodePointTrie::<u32>::try_from(toml_data.trie);
    |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `From<TomlCodePointTrie>` is not implemented for `CodePointTrie<'_, u32>`
    |
    = note: required because of the requirements on the impl of `Into<CodePointTrie<'_, u32>>` for `TomlCodePointTrie`
note: required because of the requirements on the impl of `TryFrom<TomlCodePointTrie>` for `CodePointTrie<'_, u32>`
   --> provider/uprops/src/codepointtrie.rs:53:20
    |
53  | impl<T: TrieValue> TryFrom<&TomlCodePointTrie>
    |                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^
54  |     for CodePointTrie<'static, T>
    |         ^^^^^^^^^^^^^^^^^^^^^^^^^
note: required by `try_from`
```

Ideally the output should look like:

Propose adding a borrow to the argument of `try_from`.
Repository: pytorch
Issue: RFC: “What’s in a (NumPY) name?” — Changing PyTorch Operator Names
Labels: high priority,triaged,module: numpy

**Should we change the names of some popular PyTorch operators to make PyTorch more consistent with NumPy?**

Today in PyTorch there are operations — like repeat() —  that do one thing in PyTorch and another in NumPy. This is a surprising pain for NumPy users coming to PyTorch, and it means that regular users of both frameworks have to remember which ops are different.

Removing “stumbling blocks” like these is one of PyTorch’s major user experience goals. Over the past year and a half we’ve added over 100 operators from NumPy and SciPy, including the torch.fft, torch.linalg, and torch.special modules. These updates have made it easier than ever to transition between PyTorch and NumPy (and SciPy). Changing operator names is, however, a little disruptive since it requires users update their existing programs.

Here’s the operators this RFC proposes renaming:


* repeat → tile
    * PyTorch’s repeat is different from NumPy’s repeat but identical to NumPy’s tile
* split → split_size
    * PyTorch’s split is different from NumPy’s split because it asks what size the resulting chunks should be, instead of how many there should be (see this issue (https://github.com/pytorch/pytorch/issues/50012) for details)
* nonzero → argwhere
    * PyTorch’s nonzero is different from NumPy’s nonzero but identical to NumPy’s argwhere
* max → amax, max_with_indices
    * PyTorch’s max has unusual behavior where it sometimes returns just the maximum value of a tensor and other times returns the maximum and the indices of the maximum values. Splitting this into amax (which just returns the maximum) and max_with_indices (which always returns both) is a clearer user experience.
* size → shape
    * PyTorch already supports the shape attribute, but we use the ambiguous “size” to refer to shape while other frameworks often use it to refer to numel. Encouraging more consistent use of shape and numel is clearer and more consistent with other frameworks.


To accommodate each rename the new operation would be added (in most cases above it already exists) and users would be pointed to the new name for two releases. Then we’d remove the old names for one release, and finally restore the old names with behavior consistent with NumPy. This means users will have half a year or longer to find and replace names in their programs.

What are your thoughts? Comment below if you think consistency with NumPy is important or you’d like to argue that these disruptions, while small, aren’t worthwhile. 


cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @mruberry @rgommers
Repository: vscode
Issue: [bug] Virtual Keyboard covers cursor and code on iOS/iPad if below keyboard waterline 
Labels: bug,editor-core,ios-ipados

ADD ISSUE DESCRIPTION HERE
If you have a text file open on vscode.dev and you tap text low on the screen to edit it, the keyboard opens and blocks your view of the text. 

See video. I’m tapping on the word ’Reference’ at the bottom of the text 

https://user-images.githubusercontent.com/1845/141315465-e9f3f12b-b0d5-4f81-a9d1-b3f088cf7e55.mov



Version: 1.62.1
Commit: f4af3cbf5a99787542e2a30fe1fd37cd644cc31f
User Agent: Mozilla/5.0 (iPhone; CPU iPhone OS 15_0_2 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Mobile/15E148 Safari/604.1
Embedder: github.dev

<!-- generated by web issue reporter -->
Repository: opencv
Issue: cuda::remap never stops in case of overflow and params INTER_CUBIC, BORDER_REPLICATE
Labels: bug,category: gpu/cuda (contrib)

##### System information (version)
- OpenCV => 4.x
- Operating System / Platform => Ubuntu
- Compiler => :grey_question: 

##### Detailed description

There is issue #18224 about illegal memory access during `remap` w/ params INTER_LINEAR and BORDER_CONSTANT.
If we try to call `remap` with the same `xmap` and `ymap` but with other params INTER_CUBIC and BORDER_REPLICATE it will never stop.

##### Steps to reproduce
Test all params for remap:

```.cpp
class RemapOutOfScope : public  Remap {};
CUDA_TEST_P(RemapOutOfScope, Regression_18224)
{
    cv::Mat src = randomMat(size, type);
    cv::cuda::GpuMat dst = createMat(xmap.size(), type, useRoi);
    randu(xmap, NPP_MAX_32S, NPP_MAXABS_32F);
    randu(ymap, NPP_MAX_32S, NPP_MAXABS_32F);

    cv::cuda::remap(loadMat(src, useRoi), dst, loadMat(xmap, useRoi), loadMat(ymap, useRoi), interpolation, borderType, 0.);

    cv::Mat dst_gold;
    remapGold(src, xmap, ymap, dst_gold, interpolation, borderType, 0.);

    EXPECT_MAT_NEAR(dst_gold, dst, src.depth() == CV_32F ? 1e-3 : 1.0);
}

INSTANTIATE_TEST_CASE_P(CUDA_Warping, RemapOutOfScope, testing::Combine(
        ALL_DEVICES,
        DIFFERENT_SIZES,
        testing::Values(MatType(CV_8UC1), MatType(CV_8UC3), MatType(CV_8UC4), MatType(CV_32FC1), MatType(CV_32FC3), MatType(CV_32FC4)),
        testing::Values(Interpolation(cv::INTER_NEAREST), Interpolation(cv::INTER_LINEAR), Interpolation(cv::INTER_CUBIC)),
        testing::Values(BorderType(cv::BORDER_REFLECT101), BorderType(cv::BORDER_REPLICATE), BorderType(cv::BORDER_CONSTANT), BorderType(cv::BORDER_REFLECT), BorderType(cv::BORDER_WRAP)),
        WHOLE_SUBMAT));
```

##### Issue submission checklist

 - [x] I report the issue, it's not a question
 - [x] I checked the problem with documentation, FAQ, open issues,
       forum.opencv.org, Stack Overflow, etc and have not found solution
 - [x] I updated to latest OpenCV version and the issue is still there
 - [x] There is reproducer code and related data files: videos, images, onnx, etc
Repository: pytorch
Issue: torch.nn.Linear wrong type annotation for bias
Labels: module: nn,module: typing,triaged

## 🐛 Bug

It seems that `torch.nn.Linear` gives wrong type annotation for bias:
Expect `NoneType`, but get `torch.nn.parameter.Parameter`.

## To Reproduce

I am using PyTorch 1.9.0.

```python
import torch
x = torch.nn.Linear(3, 5, bias=False)
# `reveal_type(x.bias)` gives `torch.nn.parameter.Parameter` which is wrong.
# But printing will give `NoneType` which is correct.
print(type(x.bias))
```

## Expected behavior

`torch.nn.Linear.bias` should be `Union[types.NoneType, torch.nn.parameter.Parameter]`, or have a `torch.nn.LinearNoBias` as a subclass?

## Environment

Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```

 - PyTorch Version (e.g., 1.0): 1.9.0
 - OS (e.g., Linux): Linux
 - How you installed PyTorch (`conda`, `pip`, source): pip
 - Build command you used (if compiling from source):
 - Python version: 3.9.7
 - CUDA/cuDNN version: 10.2
 - GPU models and configuration:
 - Any other relevant information:


cc @albanD @mruberry @jbschlosser @walterddr @ezyang @malfet @rgommers @xuzhao9 @gramster
Repository: ant-design
Issue: TextColor of `help` content when `Form.Item`'s validate status is `warning` is unreadable with light theme
Labels: Inactive,⌨️ Accessibility

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-m5jq4)

### Steps to reproduce
/

Just view the template page.

### What is expected?
Warning message is as clear and readable as error message, or to say that the yellow color should be darker.

### What is actually happening?
Warning message is quite difficult to recognize from white background.

| Environment | Info |
|---|---|
| antd | 4.16.13 |
| React | 17.0.2 |
| System | Windows 10 |
| Browser | Chrome latest |

---
WCAG Guidelines for Contrast suggests that the ratio **4.5:1** represents the minimum legibility (AA standard) on the web.

However the yellow color against the white bg's contrast ratio is **1.9:1** (calculated by https://webaim.org/resources/contrastchecker/), which is far from the recommended value, and of course is downgrading real user experiences.

I humbly request to make warning color on text be darker (border color is fine).

Plus:
In case you are interested in this, the contrast ratio between the red color in error status and the white bg is **3.26:1**, which also fails the readability test in the link given before.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Tween.stop_all briefly resets tween status in recursive tweens
Labels: bug,topic:animation

### Godot version

3.4

### System information

Windows 10

### Issue description

Calling _Tween.stop_all_ in a "recursive tween" (i.e. such that the on_tween_completed callback makes the tween restart) briefly resets the property state to the initial value of the previous iteration.

Additional notes:

- If the interpolate_property method is initialized with **null** as a start value then the property briefly resets to its very first value on each iteration.
- If _stop_all_ is replaced with _stop(object, property)_ everything works as expected.

### Steps to reproduce

Run the main scene of the reproduction project.


### Minimal reproduction project

[TweenBug.zip](https://github.com/godotengine/godot/files/7521745/TweenBug.zip)