sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Define 'tagName' values in Element interfaces to prevent misleading type acceptance.
Labels: Suggestion,Awaiting More Feedback

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->
- HTML Element Interfaces
- Element tagName
- Element Interfaces
- Incorrect element types accepted

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about Element interfaces

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/PTAEFEBsFMFtoHYBcDOoDGBDBoBG1RMUUBLAcwWgBNQkB7UAN0wCcTNcY06AzUOpAAtoLUNBjxktAJ4AHaGnxYArigK9QJZCJ6Z06xiMiZZi6FrKgUynjxLoSiJADoAsACgYSMRKcAuUAAJABUAWQAZAGVZbCg4J1AAXlAqOnRlSRd0FmhMJGg4zIAKACIqEkYSgEoAbg8PEFAAST4hAi18ll19NC10SGUqalphQllZFjoJ9nzQAHIkTDIAOUx4OdAJqZEkaRGSNHQ6ZUgafEJGOhIhqmc7jy8rGIRC-yCwqOfXqQAyUABvWhLVbwAIlSIABQAgssSqAAL5JFJpDJOZzZXL5b5IUrlSpVQhoEIRAAiFWxoD+gMWKzW0DBJKaADU4fCakA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
// Elements can be assigned to variables of other element types because of interface overlaps being sufficient.
let element: HTMLSpanElement = document.createElement("div");

// If the interfaces included the appropriate 'tagName' property this could be avoided...
let spanElement: HTMLSpanElement & { tagName: "SPAN" } = document.createElement("div") as HTMLDivElement & { tagName: "DIV" };
```

### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->
e.g. 'HTMLDivElement' instance can be assigned to variables of type 'HTMLSpanElement'.

### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->
This should fail the type checking to avoid accidentally assigning elements of an incorrect type.
Repository: flutter
Issue: GradientTransform has no arbitrary matrix version
Labels: c: new feature,framework,a: quality,P2,team-framework,triaged-framework

The underlying gradient logic takes arbitrary matrices, but the painting library's Gradient subclasses take a GradientTransform which doesn't have an arbitrary 4x4 matrix version.
Repository: pytorch
Issue: maybe_wrap_dim should have an example attached to it
Labels: module: docs,triaged

## 📚 Documentation

https://github.com/pytorch/pytorch/blob/7c588d5d00177230ac98bd92510e39bd0ce6f2da/aten/src/ATen/WrapDimUtils.h#L9-L11

This should have an example attached to it. I've had to look up the math for this multiple times in the past and I wish it were just captured in a comment in code.

cc @brianjo @mruberry
Repository: TypeScript
Issue: JS checking makes JSX props optional when inferred through JSX.LibraryManagedAttributes
Labels: Needs Investigation,checkJs

# Bug Report

Reported as part of #45140, moving to its own issue.

### 🔎 Search Terms

js jsx props optional

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?filetype=js#code/JYWwDg9gTgLgBAJQKYEMDG8BmUIjgIilQ3wG4AoUSWOABRzABUBPMJAZzm1wLAYFoYrDmXLlMAVwB2GYBClwAsswDCuSFKRSYACgDecPhDABGADSGGAJgtGwAZjgBfAJRw95OHCIwJUBTqeXnAAPAAmwABuAHxBwaHsYChS0Xp2Jk4hAPSJybHxXiG5KWnWmTlJKXGhWRExQS4UTmLKauDyWjAAdHYsbJwAvO5B6QBcdAx9HF3sMFDAUgDmXcDsyACOEsBEYWYj1uP0xlPsXQBGEBAANntedvaHk8Kn7AAWKGz61aaPx88zcwWiyCrnITgo5Fa6g62i6YSQmBQEiuMCOYEGwzuBy4KCu7CQYIhWSycAAglcrpZjJw3hAAO5wFCcYwwORSXFwBZwTbANAAa05UkwEDgJLQ6iuSFZ8nYFmSYTgMFeSCIAHJOFIRSqcFAuNA4CBVuwgVTTF1yMS4IxlYrhHAIJhFTaAFIAZQAGqbOKtBZhtUgFdw8AADKHtTSw3rPYNwSLAFBwN3uroAGWAZygKCgzEUyRQiwDpJggLOEhgHD2ltL8CVSHtYGl7KuwCEjLAbCznDpOCWXTgrrpLbQrxNtbgV2Siwk+brMBFU1daHmDYNKD5HCdPrOSHekTrTLgSAAHmwMAHzToQmGNJ1TVZRdEXOQgA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
// @Filename: index.jsx

import React from "react";
import PropTypes from "prop-types";

function MyComponent({ prop1, prop2, prop3 }) {
  return (
    <div>
      <span>{prop1}</span>
      <span>{prop2}</span>
    </div>
  );
}

MyComponent.propTypes = {
  prop1: PropTypes.string.isRequired,
  prop2: PropTypes.bool,
  prop3: PropTypes.shape({
    p1: PropTypes.string
  })
};

// All props show as optional in quick info / completions, and there's no error for missing prop1.
// The type of the JSX props is inferred from `MyComponent.propTypes` via JSX.LibraryManagedAttributes,
// but the optionality appears wrong. Switching the language to TypeScript makes this behave as expected.
(<MyComponent prop2 />)
```

### 🙁 Actual behavior

All props show as optional in quick info / completions, and there's no error for missing prop1. The type of the JSX props is inferred from `MyComponent.propTypes` via JSX.LibraryManagedAttributes, but the optionality appears wrong. Switching the language to TypeScript makes this behave as expected.

### 🙂 Expected behavior

The `prop1` JSX prop shows as required and an error is shown on the JSX element since it’s missing.
Repository: pytorch
Issue: [feature request] Expand a given dim
Labels: triaged,enhancement,module: viewing and reshaping

This would be a simpler API for torch.repeat / expand, Or maybe does it exist already?

```python
import torch

expand_dim = lambda tensor, dim, expand: tensor.unsqueeze(dim).expand((-1, ) * (dim if dim >= 0 else tensor.ndim + dim + 1) + (expand, ) + (-1, ) * (tensor.ndim - (dim if dim >= 0 else tensor.ndim + dim + 1)))

a = torch.rand(3, 4, 5)
b = expand_dim(a, dim = -2, expand =  6)
c = expand_dim(a, dim = 3, expand =  8)

print(a.shape)
# torch.Size([3, 4, 5])
print(b.shape)
# torch.Size([3, 4, 6, 5])
print(c.shape)
# torch.Size([3, 4, 5, 8])
```
Repository: pytorch
Issue: Some way to specify expected failures for OpInfo-based tests
Labels: module: tests,triaged,enhancement

## 🚀 Feature

A way to specify expected failure for OpInfo-based tests that works with unittest's expected failure reporting

## Motivation

For functorch we have automated coverage tests for OpInfos. E.g. there is a test that for each OpInfo, checks vmap support for the OpInfo. Tests that are currently failing are put into a denylist and skipped instead of running. It would be nice if we could mark them as expected failure instead.

## Alternatives

We can emulate expected failures by doing a try-except and checking for the presence of an exception. The main problem I have with this approach is the UX: the unittest runner shows an "expected failure" as a passed test, when it would be nice to see that it is an expected failure in the runner.


cc @mruberry @VitalyFedyunin @walterddr
Repository: pytorch
Issue: torch.cholesky_inverse supports tensors with more than 2 dimensions
Labels: module: docs,triaged,module: linear algebra

## 📚 Documentation

The docs suggest that it only accepts 2D tensors. Either the docs are wrong or the operator is wrong:
```

[ins] In [1]: import torch
x =
[ins] In [2]: x = torch.eye(3, 3)

[ins] In [3]: x
Out[3]:
tensor([[1., 0., 0.],
        [0., 1., 0.],
        [0., 0., 1.]])

[ins] In [4]: torch.cholesky_inverse(x)
Out[4]:
tensor([[1., 0., -0.],
        [0., 1., -0.],
        [-0., -0., 1.]])

[ins] In [5]: y = torch.stack([x, x])

[ins] In [6]: torch.cholesky_inverse(y)
Out[6]:
tensor([[[1., 0., -0.],
         [0., 1., -0.],
         [-0., -0., 1.]],

        [[1., 0., -0.],
         [0., 1., -0.],
         [-0., -0., 1.]]])

```

cc @brianjo @mruberry @jianyuh @nikitaved @pearu @heitorschueroff @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: flutter
Issue: AnimatedScale and AnimatedRotation should take an AlignmentGeometry instead of Alignment
Labels: framework,a: internationalization,a: quality,P2,team-framework,triaged-framework

AnimatedScale and AnimatedRotation should take an AlignmentGeometry instead of just Alignment.

cc @flar
Repository: go
Issue: cmd/link: support symbol indexing for DUPOK symbols
Labels: NeedsInvestigation,FeatureRequest,compiler/runtime

A common situation within the compiler is package A defines a DUPOK symbol X, package B imports package A, and then package B needs to refer to that same DUPOK symbol X.

Today, we handle this by having package B re-defined symbol X, and the linker discards the duplicates. This works fine (and in general, we do need the linker to support DUPOK symbols), but it means the compiler spends unnecessary time re-defining the symbol, and it means the object files are unnecessarily large with redundant definitions.

It would be nice if we could still use symbol indexing to refer to DUPOK symbols defined in another object file. Today, this would already be useful for cutting down redundant type descriptors for anonymous types and method wrappers; but it's likely to be useful for avoiding time spent compiling redundant instantiations of generic functions/types too.

/cc @cherrymui
Repository: node
Issue: [DNS] TLSA records [HTTPS] DANE request
Labels: tls,https,dns,feature request,cares

<!--
Thank you for suggesting an idea to make Node.js better.

Please fill in as much of the template below as you're able.
-->

**Is your feature request related to a problem? Please describe.**
I'd like to make an HTTPS request to a server that uses a self-signed certificate that follows the DANE protocol ([Wikipedia](https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities))

**Describe the solution you'd like**
I believe the best option would be an extra option on HTTPS request:
```
https.get('https://example.com', {dane: true})
```

**Describe alternatives you've considered**
I tried to create a new `https.Agent` that forces `rejectUnauthorized: false`;
Then, I got the `tlsSocket` instance in the `keylog` event and added a listener for the `secureConnect` event;
This moment I realised that the DNS api don't have a `resolveTLSA`.
Not sure how to continue from here.
Repository: vscode
Issue: Prevent menu dismissal due to updates for toolbar dropdowns
Labels: debt,menus

When clicking a `...` dropdown menu on a toolbar, the dropdown can be dismissed if the context key changes and triggers an update to the actions for the toolbar.

In notebook, we had workarounds to postpone the actions update to prevent dismissing the dropdown menu but ideally it should be handled by the toolbar itself.

re
* https://github.com/microsoft/vscode/commit/e7cdbd8024570a7540fcc6dc29f3ca06fd31d7df
* https://github.com/microsoft/vscode/commit/c0a100d41095f506db69937a4ac8b358ada67d95
Repository: youtube-dl
Issue: REQUEST: granular quiet option
Labels: request

REQUEST: granular quiet option

## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

WRITE DESCRIPTION HERE


It would be cool if --quiet was more granular. For each video I run the program twice, once with --get-filename and once with --quiet... There are a number of options that simulate the download and produce data. It would be great if there were an option to run the download and specify which data should be displayed.
Repository: youtube-dl
Issue: REQUEST: multi-threaded execution option
Labels: request

REQUEST: multi-threaded execution option

## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

WRITE DESCRIPTION HERE

I created a batch script to start the program in four simultaneous threads. It works, but I wish this were a built in feature. Because I am doing it I cannot use the download-archive in my threads for fear of a collision. My workaround is to reprocess the playlist in a single thread after downloading the files in multiple threads. The files already exist so it goes relatively quickly, but it is redundant and it exemplifies a problem all similar solution will face.

If multiprocessing is left to outside solutions such as xargs then the user must re-implement all of the logging features of youtube-dl. I read somewhere that youtube-dl doesn't want to be a multifunction program, but the fact is that it already is and multiprocessing/threading massively speeds up the downloading of videos when compared to serial processing.
Repository: youtube-dl
Issue: REQUEST: option to append failed downloads to a log file
Labels: request

REQUEST: option to append failed downloads to a log file

## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

WRITE DESCRIPTION HERE


Speaking of logs, it would be great if youtube-dl could be instructed to append failed downloads like the seven in my bug report to a list in another file. I am capturing these and producing my own list by running the program a second time, with --get-id, capturing the output and producing my own file, but it could be unnecessary.
Repository: youtube-dl
Issue: REQUEST: log unavailable videos to a log file
Labels: request

REQUEST: log unavailable videos to a log file

## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

WRITE DESCRIPTION HERE


I noticed that some videos which have become private return an Error: Join this channel to get access to members-only content like this video, and other exclusive perks.

There's not much we can do about that, but I wonder if youtube-dl should produce a log file containing a list of those urls.
Repository: godot
Issue: Screen space effects + 16× MSAA cause blurry screen
Labels: topic:rendering,documentation,topic:3d

### Godot version

3.3.2.stable

### System information

Windows 10, Vulkan, RTX 2080

### Issue description

MSAA appears to mistakenly cause blurry screen when screen space effects are enabled. FXAA does not have the same problem.

MSAA 16x, SSAO OFF, SS Reflections OFF

![image](https://user-images.githubusercontent.com/87843097/127407801-29f29cd6-b737-4a0f-9701-bdab5b0c8ee6.png)

MSAA 16x, SSAO **ON**, SS Reflections OFF

![image](https://user-images.githubusercontent.com/87843097/127407879-478c2991-2b13-4b1a-b672-e5d9d914096b.png)

MSAA 16x, SSAO OFF, SS Reflections **ON**

![image](https://user-images.githubusercontent.com/87843097/127407953-6ea68c37-4c3c-4e22-8122-aea93be788cc.png)


### Steps to reproduce

1. Enable MSAA to 16x in project settings
2. Add a WorldEnvironment node to scene
3. Either enable Ssao or Ss Reflections

### Minimal reproduction project

_No response_
Repository: go
Issue: html/template: imagesrcset incorrectly escaped
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version go1.16.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

* https://play.golang.org/p/-lKXlZo1DXy

### What did you expect to see?

* `<link rel="preload" as="image" imagesrcset="http://example.com/1.jpg 100w, http://example.com/2.jpg 200w" />`

### What did you see instead?

* `<link rel="preload" as="image" imagesrcset="http://example.com/1.jpg%20100w,%20http://example.com/2.jpg%20200w" />`

### References

* https://web.dev/preload-responsive-images/#imagesrcset-and-imagesizes
* Related to: https://github.com/golang/go/issues/17441

Ta!
Repository: rust
Issue: Tracking Issue for `for`-loops in constants
Labels: C-tracking-issue,A-const-eval

This tracks `#![feature(const_for)]`, added in https://github.com/rust-lang/rust/pull/87237.

This feature depends on [`const_trait_impl`](https://github.com/rust-lang/rust/issues/67792) and is not currently usable.
Repository: vscode
Issue: Allow extension contributed walkthroughs to specify a "Next section" link.
Labels: feature-request,getting-started

<!-- ⚠️⚠️ 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. -->

### Idea
Let extension contributed walkthroughs link or chain multiple walkthroughs together similar to the built-in walkthroughs. 

### Details

If a walkthrough specifies a "nextWalkthroughId" property then:
* the "Next section ->" link is shown
* Clicking the "Next section ->" link opens the specified walkthrough.

I've attached an image that shows the "Next section" link I'm referring to.

![image](https://user-images.githubusercontent.com/12476526/127416896-9865fa46-94ae-4c7c-91b2-d204b9de068d.png)
Repository: ant-design
Issue: Nested List props 会透传
Labels: Inactive

- [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-tn19h?file=/index.js)

### Steps to reproduce
看最小化重现即可

### What is expected?
内部List 不会受到外部List 的props.split影响

### What is actually happening?
会跟随外部split变化

| Environment | Info |
|---|---|
| antd | 4.16.9 |
| React | 16.14 |
| System | macOS 11.5.1 |
| Browser | Chrome 92.0.4515 |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: go
Issue: cmd/compile: optimize append([]byte(string), ...) to avoid a duplication
Labels: Performance,NeedsInvestigation,compiler/runtime

<!--
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.17rc1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

```Go
package main

import "testing"

var str = "1234567890123456789012345678901234567890"

func f() {
	_ = append([]byte(str), str...)
}

func main() {
	stat := func( f func() ) int {
		allocs := testing.AllocsPerRun(1, f)
		return int(allocs)
	}
	println(stat(f)) // 2
}
```

### What did you expect to see?

One allocation.

### What did you see instead?

Two instead.

The allocation for `[]byte(str)` could be saved.

Partially related to https://github.com/golang/go/issues/43429.