sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: "Show/Hide the Terminal window" buggy between displays
Labels: Issue-Bug,Product-Terminal,Priority-3,Area-Windowing

### Windows Terminal version

1.14.1452.0

### Windows build number

10.0.22621.0

<hr>

# Bug the first

### Steps to reproduce

1. Setting a key combination for the Action "Show/Hide the Terminal window", for example "ctrl+win+h". BTW, is this called "Global Summon"?
2. *Acts in the same display works fine*
3. **Maximize Terminal window in a bigger display**, then "Hide" it with keystroke.
4. move mouse cursor **to a smaller display**, "Show" it with keystroke.

### Expected Behavior

after `step 4`, the window shows maximized.

### Actual Behavior

Focus changed, but Terminal shows ghostly
more detail:
![image](https://user-images.githubusercontent.com/1884240/175450511-0af969f5-facc-471d-ab10-8f5783593143.png)

when display failed: (Rectangle is correct)
![image](https://user-images.githubusercontent.com/1884240/175451474-54b5a0fe-026b-45f4-9595-9a99aa31a47f.png)


# Bug the second

### Steps to reproduce

1. Setup a key combination to "Show/Hide the Terminal window".
2. Maximize Terminal window in a smaller display.
3. Move cursor to a bigger display, press keystroke to "summon" Terminal to this display

### Expected Behavior

Terminal window moves to the bigger display, and maximized

### Actual Behavior

Terminal window moved to the bigger display, and "maximized" according to the window button, but actually not maximized.

*Notice the buttons on the upper right corner*
![image](https://user-images.githubusercontent.com/1884240/175452679-22bfbc14-e326-4e27-9c53-0ba93d2feec3.png)
Repository: pytorch
Issue: `max_unpool` gives wrong gradient when `indices` has duplicate
Labels: module: autograd,module: nn,triaged,module: pooling,module: edge cases

### 🐛 Describe the bug

`max_unpool` doesn't consider that the `indices` may have duplicate elements in its gradient formula.

```python
import torch

def get_fn():
    indices = torch.tensor([[[4, 2, 3, 5]]], dtype=torch.int64, device='cuda')
    kernel_size = [1]
    stride = [2]
    def fn(input):
        fn_res = torch.nn.functional.max_unpool1d(input, indices, kernel_size, stride=stride,)
        return fn_res
    return fn
fn = get_fn()
input_tensor = torch.tensor([[[0.6418, 0.0359, 0.6088, 0.9408]]], dtype=torch.float64, device='cuda')

print(input_tensor)
# tensor([[[0.6418, 0.0359, 0.6088, 0.9408]]], dtype=torch.float64)
print(fn(input_tensor))
# tensor([[[0.6418, 0.9408, 0.6088, 0.0000, 0.0000, 0.0000, 0.0000]]],
#       dtype=torch.float64)

try:
    input = input_tensor.clone().detach().requires_grad_()
    torch.autograd.gradcheck(fn, (input), check_sparse_nnz=False, atol=0.01, rtol=0.01, check_forward_ad=False, check_backward_ad=True, check_batched_grad=False)
except Exception as e:
    print(e)

# Jacobian mismatch for output 0 with respect to input 0,
# numerical:tensor([[1.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000],
#         [0.0000, 1.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000],
#         [0.0000, 0.0000, 1.0000, 0.0000, 0.0000, 0.0000, 0.0000],
#         [0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000, 0.0000]],
#        device='cuda:0', dtype=torch.float64)
# analytical:tensor([[1., 0., 0., 0., 0., 0., 0.],
#         [0., 1., 0., 0., 0., 0., 0.],
#         [0., 0., 1., 0., 0., 0., 0.],
#         [0., 1., 0., 0., 0., 0., 0.]], device='cuda:0', dtype=torch.float64)
```

In the above example, the output of `max_unpool` only has 3 elements but the gradient computed by reverse-mode has 4 elements.

I am not sure whether this is a big issue since `max_pool` could not return `indices` with duplicate elements.

### Versions

pytorch: 1.11.0

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are
Repository: pytorch
Issue: `soft_margin_loss` gives wrong gradient when `target` with dtype uint8
Labels: module: autograd,module: nn,module: loss,triaged

### 🐛 Describe the bug

`soft_margin_loss`gives wrong gradient when`target` with dtype uint8

```python
import torch

torch.random.manual_seed(9782)
def get_fn():
    target = torch.tensor([0, 0, 1, 1], dtype=torch.uint8, device='cpu')
    def fn(input):
        fn_res = torch.nn.functional.soft_margin_loss(input, target)
        return fn_res
    return fn
fn = get_fn()
input = torch.tensor([[0.9707, 0.2672, 0.2389, 0.6876]], dtype=torch.float64, device='cpu', requires_grad=True)
try:
    torch.autograd.gradcheck(fn, (input), check_sparse_nnz=False, atol=0.01, rtol=0.01, check_forward_ad=False, check_backward_ad=True, check_batched_grad=False)
except Exception as e:
    print(e)

# Jacobian mismatch for output 0 with respect to input 0,
# numerical:tensor([[ 0.0000],
#         [ 0.0000],
#         [-0.1101],
#         [-0.0836]], dtype=torch.float64)
# analytical:tensor([[-0.0000],
#         [-0.0000],
#         [-0.2500],
#         [-0.2500]], dtype=torch.float64)
```

If `target` has dtype `int16` or `int32`, it will return the correct gradient.

### Versions

pytorch: 1.11.0

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are
Repository: pytorch
Issue: F.binary_cross_entropy_with_logits unexpected behaviour
Labels: module: nn,module: loss,triaged

I wanted to see if I put a non-binary input into `F. binary_cross_entropy_with_logits` if it will fail. Instead it gives me an answer without failing which is odd, but I can't figure out where the numbers are coming from. See example below (3rd row is confusing).

Two questions regarding below:
1. Why is this not chucking an error because of the 7 in `targets`
2. Why do I have to manually convert targets to `float` when `F.cross_entropy` expects a `LongTensor` and not `FloatTensor`.

```python
import torch
import torch.nn.functional as F

torch.manual_seed(42)

logits = torch.randn((5, 1))
targets = torch.LongTensor([0, 1, 7, 1, 0])[:, None]
log_prob = torch.cat([torch.log1p(-torch.sigmoid(logits)), F.logsigmoid(logits)], dim=-1)
print(F.binary_cross_entropy_with_logits(logits, targets_multilabel.float(), reduction="none"))
print(-log_prob)
"""
Output:
tensor([[ 0.8756],
        [ 0.6308],
        [-0.8240],
        [ 0.5846],
        [ 0.2817]])
tensor([[0.8756, 0.5389],
        [0.7596, 0.6308],
        [0.8172, 0.5828],
        [0.8149, 0.5846],
        [0.2817, 1.4045]])
"""
```



F.binary_cross_entropy_with_logits(logits, targets_multilabel.float(), reduction="none")


### Versions

Got this error, but my pytorch version is `1.11.0` and running on python 3.9
```
Collecting environment information...
Traceback (most recent call last):
  File "collect_env.py", line 492, in <module>
    main()
  File "collect_env.py", line 475, in main
    output = get_pretty_env_info()
  File "collect_env.py", line 470, in get_pretty_env_info
    return pretty_str(get_env_info())
  File "collect_env.py", line 319, in get_env_info
    pip_version, pip_list_output = get_pip_packages(run_lambda)
  File "collect_env.py", line 301, in get_pip_packages
    out = run_with_pip(sys.executable + ' -mpip')
  File "collect_env.py", line 289, in run_with_pip
    for line in out.splitlines()
AttributeError: 'NoneType' object has no attribute 'splitlines'
```

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are
Repository: opencv
Issue: SIFT，detectAndCompute，Memory leak
Labels: incomplete

##### System information (version)
- OpenCV == 4.5.1 or OpenCV == 4.5.5(debug)
- Operating System / Platform => Ubuntu 20.04.4 LTS (GNU/Linux 5.13.0-41-generic x86_64)
- Compiler => QT5.15.2

##### Detailed [description]
SIFT，detectAndCompute，Memory leak。
Image size is 2844*1280.channel=3。
Run the program for two hours，Memory increased from 200MB to 1000MB。
##### Steps to reproduce

    cv::Mat Img=cv::imread("19.jpg");
    cv::resize(Img,Img,cv::Size(),0.5,0.5);
    while (1)
    {
         cv::Ptr<cv::SIFT> ptrDetector=cv::SIFT::create();
         std::vector<cv::KeyPoint> KeyPts;
         cv::Mat Descriptor;
         ptrDetector->detectAndCompute(Img, cv::Mat(), KeyPts, Descriptor);
    }
Repository: vscode
Issue: enable both breadcrumbs in split editor in group when layout is vertical 
Labels: under-discussion,breadcrumbs

<!-- ⚠️⚠️ 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. -->

1. when is horizontal:
   we can see two minimap and we have the only one breadcrumbs 
![image](https://user-images.githubusercontent.com/1876302/175472665-4c0522bf-5d29-4a8e-acef-0312ff016e0e.png)

2. when is  vertical:
   there is no breadcrumbs for botton view.
![image](https://user-images.githubusercontent.com/1876302/175472677-4aba79bf-4ad6-4b40-a336-c69c651efb2d.png)
**great to have both bradcrumbs**
![image](https://user-images.githubusercontent.com/1876302/175472708-aee5cfc4-a90e-4228-9b5c-93e8a7c7b904.png)
Repository: ant-design
Issue: [NEW] Statistic.Timer
Labels: ☘️ New Component,Inactive

```jsx
<Timer
  type="countup"
  title="Countdown"
  value={deadline}
/>

// replace Statistic.CountDown
<Timer
  type="countdown"
  title="Countdown"
  value={deadline}
  onFinish={onFinish}
/>
```
Repository: vscode
Issue: Reverse the visual logic of text link decorators
Labels: ux,accessibility,under-discussion

Hi!

At the moment, the default design for plaintext links in VS Code is that the links are only painted in different colour in regular states, and then on hover they get `text-decoration: underline`. This makes them rather inaccessible as W3C guidelines suggest we should [not only use colour to differentiate elements](https://www.w3.org/WAI/tips/designing/#dont-use-color-alone-to-convey-information). ← Even GitHub is doing this wrong as this link is just blue, and then underlines on hover.



![link underline](https://user-images.githubusercontent.com/44162846/175490354-bbd0a707-c4bd-4844-9ad4-a0a226d72120.gif)

This causes issues when there is a lot of text, and users have to hunt where the links actually are. I am a professional designer and can spot a misaligned single pixel, yet I have some trouble visually focusing and finding where the links are in this screenshot:


<img width="747" alt="Screenshot 2022-06-24 at 08 56 45" src="https://user-images.githubusercontent.com/44162846/175490514-3d1a6155-2aa7-473e-8505-71cc24e7c1ed.png">

## Proposed Solution

Could you please simply flip the logic - have links be underlined by default, and then on hover they lose the underline.



- - - -

Version: 1.68.1 (Universal)
Commit: 30d9c6cd9483b2cc586687151bcbcd635f373630
Date: 2022-06-14T12:52:13.188Z (1 wk ago)
Electron: 17.4.7
Chromium: 98.0.4758.141
Node.js: 16.13.0
V8: 9.8.177.13-electron.0
OS: Darwin arm64 21.5.0
Repository: yt-dlp
Issue: NDR.de audio
Labels: site-bug

### Checklist

- [X] I'm reporting a broken site
- [X] I've verified that I'm running yt-dlp version **2022.06.22.1** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [X] I've checked that all URLs and arguments with special characters are [properly quoted or escaped](https://github.com/ytdl-org/youtube-dl#video-url-contains-an-ampersand-and-im-getting-some-strange-output-1-2839-or-v-is-not-recognized-as-an-internal-or-external-command)
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [X] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required

### Region

_No response_

### Description

After the latest yt-dlp update, video on this website seems to be working perfectly now.
However. audio doesn't.
Example: https://www.ndr.de/nachrichten/hamburg/Gruenes-Kerosin-fuer-Flugzeuge-Produktion-in-Hamburg-geplant,treibstoff100.html

### Verbose log

```shell
C:\WINDOWS\system32>"C:\Users\a\Desktop\MPC-BE\yt-dlp.exe" https://www.ndr.de/nachrichten/hamburg/Gruenes-Kerosin-fuer-Flugzeuge-Produktion-in-Hamburg-geplant,treibstoff100.html
[ndr] Gruenes-Kerosin-fuer-Flugzeuge-Produktion-in-Hamburg-geplant: Downloading webpage
[ndr:embed] treibstoff100: Downloading JSON metadata
ERROR: [ndr:embed] treibstoff100: Unable to download JSON metadata: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>); please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
```
Repository: rust
Issue: Private `#[no_mangle]` symbols are exported from a `cdylib`
Labels: A-linkage,T-compiler,C-bug

In C++ (MSVC) un-mangling and exporting are controlled via `extern "C"` and `__declspec(dllexport)` respectively.

```cpp
extern "C" {
    namespace to_export {
        __declspec(dllexport) int64_t foo() {
            int64_t bar();
            return bar();
        }
    }
    namespace not_to_export {
        int32_t bar() {
            return 42;
        }
    }
}
```

```
    00000000 characteristics
    FFFFFFFF time date stamp
        0.00 version
           1 ordinal base
           1 number of functions
           1 number of names

    ordinal hint RVA      name

          1    0 00001000 foo = foo
```

In Rust, however, all `#[no_mangle]` functions are exported from the final `cdylib`.

```rust
pub mod to_export {
    #[no_mangle]
    pub unsafe extern "system" fn foo() -> i64 {
        extern "system" {
            fn bar() -> i64;
        }
        bar()
    }
}
mod not_to_export {
    #[no_mangle]
    extern "system" fn bar() -> i32 {
        42
    }
}
```

```
    00000000 characteristics
    FFFFFFFF time date stamp
        0.00 version
           1 ordinal base
           2 number of functions
           2 number of names

    ordinal hint RVA      name

          1    0 00001000 bar = bar
          2    1 00001010 foo = foo
```

It seems that it is not possible to define an un-mangled and un-exported symbol in Rust.
Repository: electron
Issue: [Feature Request]: Add an API to create a `Certificate` object from a `pem` file
Labels: enhancement :sparkles:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Every use of `dialog.showCertificateTrustDialog` I've seen uses it to react to some event that passes `certificate` as an argument. There doesn't appear to be a way to create a [`Certificate`](https://www.electronjs.org/docs/latest/api/structures/certificate) from a file (without manually building the object I guess). I want to use `dialog.showCertificateTrustDialog` to trust certificates generated by [mitmproxy](https://github.com/mitmproxy/mitmproxy). What I have are `*.pem` files.

### Proposed Solution

I'm not sure where this belongs, certainly not in the `dialog` namespaces. Maybe `import { Certificate } from 'electron';` and have a static method on it like `Certificate.fromFile()`.

### Alternatives Considered

I assume it's possible to parse the file manually and re-create whatever shape electron expects the object to be. Or is `{data}` actually enough for `showCertificateTrustDialog` and all other fields are irrelevant? I don't have access to Windows or Mac right now to test it.

### Additional Information

_No response_
Repository: vscode
Issue: Support multline details in quickpick items
Labels: feature-request,quick-pick

<!-- ⚠️⚠️ 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. -->

Quickpick items can contain a `label`+`description` on one line and `detail` on a second, which overall still limits the amount of information to two lines. Can we support line breaks in the `detail` field to allow surfacing more information across multiple lines?
Repository: go
Issue: x/text/internal/testtext: contains creative commons excerpts and violates that license. 
Labels: help wanted,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
go1.18.3
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?
all


### What did you do?
Inspected source code 
https://cs.opensource.google/go/x/text/+/master:internal/testtext/text.go

### What did you expect to see?
Source code compatible with the golang license


### What did you see instead?
Source code that contained snippets of the Creative Commons license text in multiple languages.

> 	// Vietnamese is a snippet from http://creativecommons.org/licenses/by-sa/3.0/vn/
> 	Vietnamese = `Với các điều kiện sau: Ghi nhận công của tác giả. 
> Nếu bạn sử dụng, chuyển đổi, hoặc xây dựng dự án từ 
> nội dung được chia sẻ này, bạn phải áp dụng giấy phép này hoặc 
> 

That license text itself is made available under Creative Commons CC-BY-4.0 ( https://creativecommons.org/licenses/by/4.0/ ) which among other things requires attribution. 

Given that this attribution is not present, this is a violation of the license.  There does not seem any immediate harm, however this results in license compliance monitors flagging that file. And its also a bad precedent, I therefore suggest to change this texts  with text in the public domain. I am willing to prepare a PR for this, if this help.
Repository: ant-design
Issue: onCell is render a column twice?
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-oncell-bug-ynwc1m)

### Steps to reproduce

see in: console.log(index, record.name);

### What is expected?

render onCell just once

### What is actually happening?

render onCell just twice

| Environment | Info |
| --- | --- |
| antd | 4.21.3 |
| React | react |
| System | Windows 10 |
| Browser | Chrome 101.0.4951.67 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: OpInfos for torch.ops.aten operations
Labels: feature,module: tests,triaged

### 🚀 The feature, motivation and pitch

We should have OpInfos for torch.ops.aten operations that are not covered by the forward pass of our existing torch.* based OpInfos. For example: at::convolution_backward is not directly invoked by the OpInfo for torch.nn.functional.conv2d, so it falls into this category.

## Motivation

Today, to test coverage for at::convolution_backward, someone must write a "forward + backward" test for their OpInfo.
- Performance: This is inefficient because the backward pass (convolution_backward) is generally 2x more expensive than the forward pass
- DRY: You start seeing subsystems (e.g. AOTAutograd, functorch vmap) having the same logic to run forward+backward tests for their OpInfos. They wouldn't all need to duplicate this logic if the backward operations were already a part of OpInfos.
- Coverage: OpInfo samples may not cover all of the aten operations that are involved in a particular operation. This is because when one writes an OpInfo, they look at the public python PyTorch API and try to come up with some test cases, not the ATen implementation of the operator.
- API mismatch: torch.ops.aten.index_put_ and Tensor.index_put_ actually accept different inputs (torch.ops.aten.index_put_ is more general and used in more situation, but not all of it is tested via OpInfo)

Having aten operators in torch.ops.aten will make it easier for transform and backend writers to gain confidence in their implementations. 

### Alternatives

n/a

### Additional context

_No response_

cc @mruberry
Repository: godot
Issue: iOS 15 Safari renders all 3D models black (GLES3) [WebKit/ANGLE upstream bug]
Labels: bug,platform:web,platform:ios,topic:rendering,topic:thirdparty,topic:3d

### Godot version

Godot_v3.5-rc4

### System information

IOS 15.5, Safari

### Issue description

When making a web build (HTML5) with a few 3d cubes a standard material and a point light, the scene looks correct on a Galaxy tablet with chrome. But on my Iphone 12 (v15.5) using the Safari browser all 3d models are rendered black for some reason.

1. Iphone, 2. Galaxy tablet.

![image](https://user-images.githubusercontent.com/24936603/175548238-67dfb0d3-0586-4df9-bd25-22eadd0453bb.png)


### Steps to reproduce

Add a cube or some other model and built it for HTML5. Try running it in the Safari browser on mobile.

### Minimal reproduction project

[MobileTestProjectBlackModels.zip](https://github.com/godotengine/godot/files/8976708/MobileTestProjectBlackModels.zip)
Repository: TypeScript
Issue: Support opting-out of type narrowing on assignment
Labels: Suggestion,Awaiting More Feedback

# Suggestion

## 🔍 Search Terms

- assignment proxy
- assignment narrow
- narrow proxy

## ✅ Viability Checklist

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

## ⭐ Suggestion

I think there should be some way to tell TS to not narrow the type of a property when a new value is assigned to that property, to better work with proxies.

## 📃 Motivating Example

There's currently an issue in how TS works with proxies, in that it's not able to recognize if something is a proxy or not (not even JS at runtime could do that really), so it treats property assignments always the same way.

The problem is that if I assign the value `true` to a property of a non-proxy object then it's reasonable to make the assumption that that's immediately the new value of that property, that's just how the language works (assuming no property descriptor property messing with that), but if that object is a Proxy anything at all could happen, and TS doesn't understand that.

## 💻 Use Cases

In [Solid](https://www.solidjs.com) there's a type of proxied object called a "mutable store", and one detail about this object is that it will defer assignments to a later point in time if they happen inside a "batch" call, as not doing this would make the system "glitchy".

But TS just can't work with that, so mutable stores become unusable with TS, in the following example TS is certain that the `if` will never be entered, but as one can see from the console output it is in fact entered at runtime:

https://playground.solidjs.com/?hash=-1767694278&version=1.4.1