sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Inlay hints cover up horizontal bracket pair guides
Labels: under-discussion,inlay-hints,bracket-pair-guides

<!-- ⚠️⚠️ 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?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.66.2
- OS Version: Kubuntu 20.04

Steps to Reproduce:

1. Turn on a set of `inlayHints` that creates hints on the same line as an open bracket (like in a function call/definition)
2. Turn on `editor.bracketPairColorization` and set `editor.bracketPairs` to true or active
3. move the cursor so a horizontal pair guide is shown through the inlay hints and observe the horizontal line is covered up by the inlay background (may have to play with inlay background color depending on your theme).

The video below shows this problem and also a work around I found. Changing the `editor.inlayHints.fontSize` to smaller can shrink the whole inlay element so it's no longer obstructing the horizontal line. Alternatively you can set the `editorInlayHint.background` color to have transparency which lets the horizontal guide show through some.

Ideally these shouldn't conflict. Maybe the inlay hints need to be moved up so they can never overflow below the line of code's baseline or the horizontal guide needs to be drawn on top of everything. As it is I think it looks bad and incohesive to have the horizontal guide get broken up like this

https://user-images.githubusercontent.com/8007967/164290935-b3cd04e1-c231-4262-a7b9-6069cd3b5b4b.mp4
Repository: PowerToys
Issue: "Hold to hide" on Always on top windows
Labels: Idea-Enhancement,Product-Always On Top,Needs-Triage

### Description of the new feature / enhancement

The feature would allow you to hold down a button to temporarily hide the window you have always on top until you let go of the keyboard shortcut

### Scenario when this would be used?

This would be used when switching windows underneath the one you have always on top, for example, I'm using it for a spotting sheet for audio in a shortfilm, but when somebody messages me, my corner of the screen is still taken up by the window and I have to either minimize the window or toggle off always on top before responding, or opening up another link. being able to just hold down a button to hide it while I respond (or toggling it on and off with a button) would be amazing to have and make it a lot less time consuming to navigate through the windows underneath

### Supporting information

_No response_
Repository: go
Issue: x/website: place the link to go.dev/project in a more visible place
Labels: NeedsInvestigation,website

The project tab in the old page (golang.org) was my most frequently visited place.
After unifying to go.dev, I found the page was not easily discoverable.
Eventually, I found a link at the bottom of the page, which is with "About".

![image](https://user-images.githubusercontent.com/4999471/164295570-56c02254-7e4e-4010-a42a-1402f0ab447d.png)

Can we place the `go.dev/project` page or contribution guide page in a more visible location than this, so contributors can find where to go easily from go.dev?

Additionally,
- Is there a reason that "Connect" is linked to the golang's twitter account?  Is it the primary contact point?
Repository: terminal
Issue: Search bar for Settings UI
Labels: Issue-Feature,Help Wanted,Product-Terminal,Area-SettingsUI

When there's many global settings, it's useful to have a search bar (Windows Settings and other complex software packages feature this).

Another feature may auto-save for Settings. Windows Settings has this (more debatable).
```[tasklist]
### Tasks
```
Repository: vscode
Issue: SCM - screenreader not reading git commit formatting warnings
Labels: bug,accessibility,scm

Issue Type: <b>Bug</b>

even though I am blind, I care about the formatting of commit messages. I believe contribution guidelines should be followed by everyone, including people with disabilities. That means the tools used to check commit formatting have to be accessible to everyone, but vscode has some issues in this department.

# steps to reproduce

1. Turn on a windows or linux screenreader(those are the only platforms I have access to). For windows, I tested with nvda, for linux I tested with orca
2. Open vscode
3. In the open a folder or clone a repository pane, select a git repository
4. Make some changes to one or more files, enough for the commit window to be accessible
5. In the switcher, select source controll
6. Assuming you set up git properly, try typing a message in the commit message field that appears when you select the source controll tab. Of course, the message isn't just a string of text, it should be formatted according to the git commit conventions

# expected behaviour

when the commit message has a line longer than 72 columns, the screenreader should say something like you typed x more characters than 72.

# actual behaviour

I'm told this warning appears, but only visually, as a kind of popup. The screenreader isn't informed of it in any way, even though stuff like trying to rename a file with invalid names for the filesystem is actually read, perhaps this should get the same treatment from an accessibility standpoint?

# additional info

VS Code version: Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:46:01.075Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx   (8 x 2096)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|5.92GB (2.18GB free)|
|Process Argv|--crash-reporter-id 6c81e49b-7fec-4d30-89a0-045d0b5ab14e|
|Screen Reader|yes|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: pytorch
Issue: run_test.py option to write out failed tests
Labels: module: tests,triaged,better-engineering

### 🐛 Describe the bug

Sometimes I need to make a wide ranging change to PyTorch and run the entire test suite, and I only expect a few tests scattered here and there to fail. It would be nice to get a list of failing tests, which I could then pipe into the runner, and only execute those tests to see if my fix worked.

### Versions

master

cc @mruberry
Repository: pytorch
Issue: test_license_for_wheel always fails on my local dev copy
Labels: module: tests,triaged

### 🐛 Describe the bug

```
python test/test_license.py
sE
======================================================================
ERROR: test_license_for_wheel (__main__.TestLicense)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/data/users/ezyang/pytorch-tmp/test/test_license.py", line 27, in test_license_for_wheel
    create_bundled('third_party', current)
  File "/data/users/ezyang/pytorch-tmp/third_party/build_bundled.py", line 41, in create_bundled
    collected = collect_license(d)
  File "/data/users/ezyang/pytorch-tmp/third_party/build_bundled.py", line 19, in collect_license
    raise ValueError('could not identify license file '
ValueError: could not identify license file for third_party/cudnn_frontend

----------------------------------------------------------------------
Ran 2 tests in 0.168s

FAILED (errors=1, skipped=1)
```

this seems to pass on master CI so I guess it's a problem with my local dev env... would be nice to make this test more robust

### Versions

master

cc @mruberry
Repository: rust
Issue: Poor error message for closure expression that does not infer required higher-ranked lifetime
Labels: A-diagnostics,A-lifetimes,A-closures,T-compiler,D-terse

If I have a method that takes a generic parameter constrained by a trait, and the trait is implemented for `F: for<'a> FnOnce(Foo<'a>) -> Bar<'a>`[^foobar], then calling the method with a closure expression fails to infer the higher-ranked lifetime and produces a confusing error.

[^foobar]: `Foo<'a>` and `Bar<'a>` may also be `&'a T`.

Given the following code: ([play.rust-lang.org](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=a4b1147ed32815ada980ab19e31472c2))

```rust
use std::marker::PhantomData;
struct Value<'a> {
    _marker: PhantomData<&'a ()>,
}
impl<'a> Value<'a> {
    fn new() -> Self {
        Self {
            _marker: PhantomData,
        }
    }
}
trait Callable {
    fn call<'a>(self, s: Value<'a>) -> Value<'a>;
}

impl<F> Callable for F
where
    F: for<'a> FnOnce(Value<'a>) -> Value<'a>,
{
    fn call<'a>(self, s: Value<'a>) -> Value<'a> {
        self(s)
    }
}

fn take_callable<C: Callable>(_: C) {}

fn main() {
    take_callable(|v: Value| Value::new());
}
```

The current output is:

```
error[E0308]: mismatched types
  --> src/main.rs:28:5
   |
28 |     take_callable(|v: Value| Value::new());
   |     ^^^^^^^^^^^^^ lifetime mismatch
   |
   = note: expected struct `Value<'_>`
              found struct `Value<'a>`
note: the lifetime requirement is introduced here
  --> src/main.rs:25:21
   |
25 | fn take_callable<C: Callable>(_: C) {}
   |                     ^^^^^^^^

For more information about this error, try `rustc --explain E0308`.
```

This error does not mention higher-ranked lifetimes, does not explain where the `'a` came from or the `'_` (and if I use a type like `&str` instead of `Value` then it doesn't even print the `'_` lifetime), flips the "expected" and "found" types, points at the `C: Callable` bound as the lifetime requirement despite no lifetime being visible on that bound, and does not even highlight the closure expression's span. If I modify the code to return `v` instead of a `Value<'static>` then it does add the following note:

```
note: the anonymous lifetime #1 defined here doesn't meet the lifetime requirements
  --> src/main.rs:28:19
   |
28 |     take_callable(|v: Value| v);
   |                   ^^^^^^^^^^^^
```

This is a slight improvement but is still confusing.

This is especially confusing as having a method that is bounded by `FnOnce` directly avoids this error, which I'm told is a special-case in the compiler for inferring higher-ranked lifetimes on closure expressions.

My expectation here is the error should mention higher-ranked lifetimes somehow, preferably both specifying `for<'a> Value<'a>` and including a note that explains that closure expressions do not infer higher-ranked lifetimes when the generic bound does not specify the higher-ranked lifetime directly.
Repository: rust
Issue: Tracking Issue for TCP_QUICKACK support on Linux
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(tcp_quickack)]`

This is a tracking issue for linux specific socket option `TCP_QUICKACK`

from linux man page TCP:
        _"Enable quickack mode if set or disable quickack mode if
        cleared.  In quickack mode, acks are sent immediately,
        rather than delayed if needed in accordance to normal TCP
        operation.  This flag is not permanent, it only enables a
        switch to or from quickack mode.  Subsequent operation of
        the TCP protocol will once again enter/leave quickack mode
        depending on internal protocol processing and factors such
        as delayed ack timeouts occurring and data transfer.  This
        option should not be used in code intended to be portable."_


### Public API
```rust
// std::os::linux::net

// sealed trait, implemented for std::net::TcpStream
pub trait TcpStreamExt: Sealed{
  fn quickack(&self) -> io::Result<bool>;
  fn set_quickack(&self, quickack: bool) -> io::Result<()>;
}
```

### Steps / History

- [x] Implementation: 
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

[Zulip Discussion](https://rust-lang.zulipchat.com/#narrow/stream/219381-t-libs/topic/First.20contribution.20TCP_QUICKACK)
[Windows .NET Discussion](https://github.com/dotnet/runtime/issues/798)

Seems the windows API is significantly different from the Linux one to warrant a Linux specific trait.
Repository: deno
Issue: Reading from stdin or opening a named pipe blocks uncaught errors
Labels: bug,deno_core,public API

Before printing the error and exiting, `deno run a.js` waits for input, `sleep 5 | deno run a.js` waits 5 seconds, and `deno run --allow-read b.js` waits for the named pipe to be written.

```js
// a.js
Deno.stdin.read(new Uint8Array(1));
throw new Error();

// b.js
Deno.open("named pipe");
throw new Error();
```

```shellsession
$ deno --version
deno 1.20.6+2612b6f (canary, x86_64-apple-darwin)
v8 10.0.139.6
typescript 4.6.2
```
Repository: flutter
Issue: Support custom repository overrides for Flutter gradle dependencies
Labels: c: new feature,platform-android,tool,t: gradle,c: proposal,good first issue,P3,team-android,triaged-android

## Use case

Recently our organization has moved to restrict access to many popular public repositories (including centralMaven()), instead opting to use an internally hosted repository management solution.


I updated all of our projects' references to these repositories and replaced them with references to our own hosted repositories. Following this change I was still having issues resolving dependencies.

<img width="963" alt="Pasted Graphic" src="https://user-images.githubusercontent.com/104011621/164316289-2365e65e-4e0f-420d-a2ac-c4247dd6424f.png">

I tracked this dependency back to flutter.gradle 
https://github.com/flutter/flutter/blob/fce3cee7763c601648e1d98027d0a4aa85f22ebd/packages/flutter_tools/gradle/flutter.gradle#L57-L66

I manually added our organization’s custom repositories to the build script and removed the standard public repositories.

<img width="574" alt="buildscript {" src="https://user-images.githubusercontent.com/104011621/164316947-d4f5f1d0-e28a-4922-b06f-e4075e8e7309.png">

Following this change I was able to resolve the dependency properly and build our app.  I looked through the documentation and have been unable to find a way to configure Flutter to add custom repositories and prioritize those repositories over the standard public repositories listed above.

## Proposal

Flutter should support overriding the previously mentioned gradle repository configuration.  I was imagining utilizing a system environment variable(similar to `FLUTTER_STORAGE_BASE_URL`) to set a custom repository for this shared build dependency.  That value should be prioritized above the public repositories when set.  This change would allow teams the freedom to resolve flutter build dependencies through their repository of choice rather than being constrained to using these specific repositories.
Repository: pytorch
Issue: Coverage test is only checking packages and not all submodules
Labels: module: docs,triaged,module: python frontend

The check for `ispkg` should be removed from this check: https://github.com/pytorch/pytorch/blob/81722f66306aef05334c27bb2a64137d8fa6493a/docs/source/conf.py#L469 The allowlist need to be updated to reflect that.



cc @brianjo @mruberry
Repository: terminal
Issue: Window doesn't close when it's dragged WHILE CLI app exits
Labels: Help Wanted,Issue-Bug,Product-Terminal,Needs-Tag-Fix,Priority-1

### Windows Terminal version

1.12.10733.0

### Windows build number

10.0.22000.613

### Other Software

_No response_

### Steps to reproduce

1. Create batch-file with `timeout /t 5`
2. Doubleclick batch file
3. While timer is going down move the window until the timer ends with the mouse (It is not important, when you start moving the windows, it is important that you have it ON your mouse with a pressed key, when the timer ends)
4. Try to close the windows with pressing a key or pressing the `X`-Button in the right upper corner to close it


### Expected Behavior

The window should close automatically after releasing the mouse (Or with pressing a key or the `X`-Button)

### Actual Behavior

The window is NOT closing automatically, with pressing a key or with the `X`-Button.
<img width="866" alt="image" src="https://user-images.githubusercontent.com/86119630/164322409-df315851-e36c-4916-89c3-56126e01b3e9.png">

https://user-images.githubusercontent.com/86119630/164326069-bd55d556-6c07-4f75-af06-e90b9ce69939.mp4
Repository: PowerToys
Issue: [bug] redundant / double entries in PowerToys Run
Labels: Issue-Bug,Product-PowerToys Run,Needs-Repro,Needs-Team-Response

### Microsoft PowerToys version

0.57.2

### Running as admin

- [ ] Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

Since some of the last versions, sometimes it happens that double or even way more of the same elements are shown, or missing icons:

![image](https://user-images.githubusercontent.com/6721083/164338845-74a63fae-3677-412f-87e1-98418db99a2d.png)

![image](https://user-images.githubusercontent.com/6721083/164338908-314dca3b-ae9d-4d19-8e81-fc7307561059.png)


### ✔️ Expected Behavior

no double entries

### ❌ Actual Behavior

double or even more elements of the same kind shown

### Other Software

_No response_
Repository: deno
Issue: deno test --doc shouldn't run files that have no docs
Labels: bug,testing

Running `deno task test` in deno_std shows:
```
running 0 tests from ./testing/chai_example.ts
running 0 tests from ./testing/fast_check_example.ts
running 0 tests from ./testing/mock.ts
running 0 tests from ./testing/mock_examples/internals_injection.ts
running 1 test from ./testing/mock_examples/internals_injection_test.ts
square calls multiply and returns results ... ok (7ms)
running 0 tests from ./testing/mock_examples/interval.ts
running 1 test from ./testing/mock_examples/interval_test.ts
secondInterval calls callback every second and stops after being cleared ... ok (7ms)
```
My first thought was that `deno test` was broken and it was included files that shouldn't be there. Turns out, that it's okay because of `--doc` flag, but we should improve it so that if no doctests are discovered in a file we don't print "running 0 tests from ...".
Repository: go
Issue: net/http: HTTP/2 retry loop broken when net/http manages dials
Labels: NeedsInvestigation

`http2.Transport.RoundTripOpt` retries requests under some circumstances ([transport.go#492](https://go.googlesource.com/net/+/refs/heads/master/http2/transport.go#492)):

```go
for retry := 0; ; retry++ {
  cc, err := t.connPool().GetClientConn(req, addr)
   if err != nil {
    t.vlogf("http2: Transport failed to get client conn for %s: %v", addr, err)
    return nil, err
  }
  // ...
```

When using the bundled HTTP/2 support in `net/http`, however, `GetClientConn` does not dial connections when none are available. Instead, it returns `ErrNoCachedConn` and `net/http` handles the dial.

This results in an infinite retry loop  when the server immediately hangs up on a retryable request.
Repository: opencv
Issue: I have a problem please anyone help me? cmake error
Labels: category: build/install

Hello every one I have a problem when cmake compile, I have try to find the solution i can not find, please helpme..

- OpenCV => 4.5
- Operating System / Platform => redhat 
- Compiler => cmake
- cuda : 11.4
- cudnn : 8.2.1 
- NVIDIA A100-PCI
build command 
 cmake -D CMAKE_BUILD_TYPE=RELEASE \
-D CMAKE_INSTALL_PREFIX=/usr/local \
-D WITH_TBB=OFF \
-D WITH_IPP=OFF \
-D WITH_1394=OFF \
-D BUILD_WITH_DEBUG_INFO=OFF \
-D BUILD_DOCS=OFF \
-D BUILD_EXAMPLES=OFF \
-D BUILD_TESTS=OFF \
-D BUILD_PERF_TESTS=OFF \
-D WITH_CUDA=ON \
-D WITH_CUDNN=ON \
-D OPENCV_DNN_CUDA=ON \
-D CUDA_FAST_MATH=ON \
-D CUDA_ARCH_BIN=8.0 \
-D CUDA_ARCH_PTX=8.0 \
-D WITH_CUBLAS=ON \
-D WITH_CUFFT=ON \
-D WITH_QT=ON \
-D WITH_GTK=OFF \
-D WITH_OPENGL=ON \
-D WITH_V4L=ON \
-D WITH_FFMPEG=ON \
-D WITH_XINE=ON \
-D BUILD_NEW_PYTHON_SUPPORT=ON \
-D INSTALL_C_EXAMPLES=OFF \
-D INSTALL_PYTHON_EXAMPLES=OFF \
-D OPENCV_GENERATE_PKGCONFIG=ON \
-D OPENCV_EXTRA_MODULES_PATH=../../opencv_contrib/modules \
-D OPENCV_ENABLE_NONFREE=ON \
-D CUDNN_LIBRARY=/usr/local/cuda/lib64/libcudnn.so.8.2.1 \
-D CUDNN_INCLUDE_DIR=/usr/local/cuda/include \
-D PYTHON_EXECUTABLE=/root/anaconda3/bin/python3 \
-D PYTHON3_INCLUDE_DIR=/root/anaconda3/include/python3.7m \
-D PYTHON3_NUMPY_INCLUDE_DIRS=/root/anaconda3/lib/python3.7/site-packages/numpy/core/include \
-D PYTHON3_PACKAGES_PATH=/root/anaconda3/lib/python3.7/site-packages \
-D PYTHON3_LIBRARY=/root/anaconda3/lib/libpython3.7.so \
-D PYTHOB3_LIBRARIES=/root/anaconda3/lib/python3.7 \
-D BUILD_EXAMPLES=OFF ..

/udsk/ifai/OpenCV/opencv/modules/dnn/src/layers/recurrent_layers.cpp:702:55:   required from here
/udsk/ifai/OpenCV/opencv/modules/dnn/src/layers/../cuda4dnn/primitives/../../cuda4dnn/csl/cudnn/cudnn.hpp:298:9: **erro                                                                                                                        r: function ‘cv::dnn::cuda4dnn::csl::cudnn::TensorDescriptorsArray<T>::TensorDescriptorsArray() [with T = __half]’**                                                                                                                         defaulted on its first declaration with an exception-specification that differs from the implicit declaration ‘cv::d                                                                                                                        nn::cuda4dnn::csl::cudnn::TensorDescriptorsArray<__half>::TensorDescriptorsArray()’
         TensorDescriptorsArray() noexcept = default;
Repository: flutter
Issue: [web] Reject flutter.js promises when critical assets fail to download
Labels: platform-web,P2,team-web,triaged-web

It is currently impossible for users to detect when certain critical assets fail to download (like canvaskit.js/wasm, and I imagine fonts, and maybe others).

(I suggested using `window.onerror` to workaround this limitation, but this is a fair feature request!)

In any case, the `flutter.js` API should have a failure mode where the appropriate promise is *rejected* when its critical resources fail to download or initialize.

<img width="547" alt="Capture d’écran 2022-04-20 à 22 22 07" src="https://user-images.githubusercontent.com/2970449/164316223-7da32728-9206-49ae-ad8d-fea9802bfcf9.png">

_Originally posted by @jaumard in https://github.com/flutter/flutter/issues/76009#issuecomment-1104423766_