sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: Site support request:  hollywoodreporter.com  (THR)
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## 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.04.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support 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 new site support request
- [x] I've verified that I'm running youtube-dl version **2021.04.17**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

https://www.hollywoodreporter.com/news/dunkirk-team-reveals-what-christopher-nolan-said-oscar-win-meet-your-oscar-winner-1092454

https://www.hollywoodreporter.com/video/marvels-shang-chi-and-the-legend-of-the-ten-rings-debuts-first-trailer-thr-news



## Description

Hollywood reporter affiliated with:
Billboard.com
Vibe.com

those videos fail in a similar maner...so might be able to use same extractor?

https://www.billboard.com/video/the-army-will-soon-be-able-to-order-bts-favorite-mcdonalds-order-billboard-news

Thanks
Ringo
Repository: TypeScript
Issue: Better types for UrlSearchParams
Labels: Suggestion,Domain: lib.d.ts,Experience Enhancement

# Suggestion

## 🔍 Search Terms

Restrictive typing on UrlSearchParams

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [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

```ts
declare var URLSearchParams: {
    prototype: URLSearchParams;
    // new(init?: string[][] | Record<string, string> | string | URLSearchParams): URLSearchParams;
    new(init?: 
        | string
        | URLSearchParams
        | Record<string | number, string | number | boolean | string[] | number[] | boolean[]>
        | [string | number | boolean, string | number | boolean | string[] | number[] | boolean[]][]): URLSearchParams;
    toString(): string;
};
```

## 📃 Motivating Example

The actual typing design is more restrictive than the Javascript runtime itself.

## 💻 Use Cases

More possibilities to create strict typed UrlSearchParams objects:

```ts
let url = 'https://developer.microsoft.com'

const queryParams = new UrlSearchParams({
  key1: ["v1", "v2"],
  key2: ["v1", "v2", "v3"]
})

url = url + '?' + queryParams // https://developer.microsoft.com?key1=v1,v2&key2=v1,v2,v3
```
Repository: pytorch
Issue: Building with USE_TENSORPIPE=0 causes errors on import torch for MacOS
Labels: oncall: distributed,module: tensorpipe

## 🐛 Bug

Building with the following command on macos:
```
USE_TENSORPIPE=0 USE_GLOO=1 USE_CUDNN=0 BUILD_CAFFE2_OPS=0 USE_NNPACK=0 USE_QNNPACK=0 USE_MKLDNN=0 USE_FBGEMM=0 USE_CUDA=0 USE_MKLDNN=0 USE_DISTRIBUTED=1 python setup.py develop
```

Results in the following error:

```
>>> import torch
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/rvarm1/Desktop/pytorch/torch/__init__.py", line 632, in <module>
    from .functional import *  # noqa: F403
  File "/Users/rvarm1/Desktop/pytorch/torch/functional.py", line 6, in <module>
    import torch.nn.functional as F
  File "/Users/rvarm1/Desktop/pytorch/torch/nn/__init__.py", line 1, in <module>
    from .modules import *  # noqa: F403
  File "/Users/rvarm1/Desktop/pytorch/torch/nn/modules/__init__.py", line 2, in <module>
    from .linear import Identity, Linear, Bilinear, LazyLinear
  File "/Users/rvarm1/Desktop/pytorch/torch/nn/modules/linear.py", line 6, in <module>
    from .. import functional as F
  File "/Users/rvarm1/Desktop/pytorch/torch/nn/functional.py", line 11, in <module>
    from .._jit_internal import boolean_dispatch, _overload, BroadcastingList1, BroadcastingList2, BroadcastingList3
  File "/Users/rvarm1/Desktop/pytorch/torch/_jit_internal.py", line 21, in <module>
    import torch.distributed.rpc
  File "/Users/rvarm1/Desktop/pytorch/torch/distributed/rpc/__init__.py", line 25, in <module>
    from . import api, backend_registry, functions
  File "/Users/rvarm1/Desktop/pytorch/torch/distributed/rpc/api.py", line 39, in <module>
    from .constants import DEFAULT_SHUTDOWN_TIMEOUT, UNSET_RPC_TIMEOUT
  File "/Users/rvarm1/Desktop/pytorch/torch/distributed/rpc/constants.py", line 3, in <module>
    from torch._C._distributed_rpc import (
ImportError: cannot import name '_DEFAULT_NUM_WORKER_THREADS' from 'torch._C._distributed_rpc' (unknown location)
```

## To Reproduce
Build pytorch on MacOS as above.

## Expected behavior

Since tensorpipe is the default backend, it makes sense that if user sets USE_DISTRIBUTED=1, then USE_TENSORPIPE=1 should also be enabled, unless there are certain platforms where distributed is enabled but tensorpipe is not. In this case we should probably have errors during build time and not when importing torch.

Looking at the issue, it looks like `_DEFAULT_NUM_WORKER_THREADS` is only defined when `#ifdef USE_TENSORPIPE` is true, but in python we import this without checking if tensorpipe is available.

cc @osalpekar @jiayisuse @lw @beauby @pritamdamania87 @mrshenli @jjlilley @gqchen @rohan-varma @pietern @zhaojuanmao @satgera @aazzolini @agolynski @SciPioneer @H-Huang @mrzzd @cbalioglu
Repository: vscode
Issue: Include options in Issue Reporter are not persistent
Labels: bug,issue-reporter,papercut :drop_of_blood:


Issue Type: <b>Bug</b>

* Open issue reporter
* Uncheck "Include my enabled extensions"
* Close it
* Open issue reporter again
* The options are still all checked

VS Code version: Code - Insiders 1.56.0-insider (Universal) (8aff878db2542eea2dfb571c8bb485118bbb3113, 2021-04-19T05:13:43.644Z)
OS version: Darwin x64 20.3.0

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|3, 3, 3|
|Memory (System)|32.00GB (0.13GB free)|
|Process Argv|--enable-proposed-api ms-vscode.vscode-notebook-history --enable-proposed-api vscode.notebook-editing --enable-proposed-api vscode.vscode-test-resolver --enable-proposed-api donjayamanne.kusto --crash-reporter-id 1a907bbd-fa02-4595-81e0-63e1648afb31|
|Screen Reader|no|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: TypeScript
Issue: Call hierarchy doesn't work when function being inspected is the result of another function.
Labels: Bug

<!-- ⚠️⚠️ 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. -->
- VS Code Version: 1.54.3
- OS Version: Linux x64 5.11.9-arch1-1
Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
Date: 2021-03-24T18:27:15.725Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0

Steps to Reproduce:

1. Open a typescript project with the following code:
```ts
const someFactory = () => () => {}

const c = someFactory()
const b = () => c()
const a = () => b()
```
2. Try to show call hierarchy for a function.

Expected behavior:
Call hierarchy to show properly.
![image](https://user-images.githubusercontent.com/5003755/114931914-c8d4b700-9e2e-11eb-9aac-5fc3b508e138.png)


What actually happened:
No results found.
![image](https://user-images.githubusercontent.com/5003755/114932169-15b88d80-9e2f-11eb-9707-9568647824f2.png)


<!-- 🔧 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. -->
Repository: rust
Issue: Provide suggestions for unsized type parameters and when involving iterators
Labels: A-diagnostics,T-compiler,D-newcomer-roadblock

Given the following code:

```rust
    let x = vec![1, 2, 3];
    let y: Vec<dyn Display> = x.into_iter().collect();
```

[The current output is](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=d6b789dd975641c4b8a54bc72c2de184):

```
error[E0277]: the size for values of type `dyn std::fmt::Display` cannot be known at compilation time
   --> src/main.rs:5:12
    |
5   |     let y: Vec<dyn Display> = x.into_iter().collect();
    |            ^^^^^^^^^^^^^^^^ doesn't have a size known at compile-time
    |
    = help: the trait `Sized` is not implemented for `dyn std::fmt::Display`

error[E0277]: a value of type `Vec<dyn std::fmt::Display>` cannot be built from an iterator over elements of type `{integer}`
 --> src/main.rs:5:45
  |
5 |     let y: Vec<dyn Display> = x.into_iter().collect();
  |                                             ^^^^^^^ value of type `Vec<dyn std::fmt::Display>` cannot be built from `std::iter::Iterator<Item={integer}>`
  |
  = help: the trait `FromIterator<{integer}>` is not implemented for `Vec<dyn std::fmt::Display>`

error[E0277]: the size for values of type `dyn std::fmt::Display` cannot be known at compilation time
   --> src/main.rs:5:31
    |
5   |     let y: Vec<dyn Display> = x.into_iter().collect();
    |                               ^^^^^^^^^^^^^^^^^^^^^^^ doesn't have a size known at compile-time
    |
    = help: the trait `Sized` is not implemented for `dyn std::fmt::Display`
```

I can see a bunch of places where we could improve the output:

- The third error shouldn't have been emitted in the first place, the first two are more than enough
- The first error has a note, but that note with a little bit of work could be turned into a structured suggestion for boxing or borrowing
- For the second suggestion we could detect this case in particular where the result would be `!Sized` and also suggest `Box`ing
Repository: rust
Issue: Missing different-size int <-> NonZeroInt conversions
Labels: C-feature-request,T-libs

Right now, we have most of the integer type interconversions implemented, but we're missing some falliable NonZero conversions. Namely these:

* `iN` -> `NonZeroIM` (where `N` != `M`)
* `uN` -> `NonZeroIM` (where `N` != `M`)
* `iN` -> `NonZeroUM` (where `N` != `M`)
* `uN` -> `NonZeroUM` (where `N` != `M`)
* `NonZeroIN` -> `iM` (where `N` != `M`)
* `NonZeroIN` -> `uM` (where `N` != `M`)
* `NonZeroUN` -> `iM` (where `N` != `M`)
* `NonZeroUN` -> `uM` (where `N` != `M`)

Right now, all of the integer <-> non-zero integer conversions only operate on types of the same size, rather than all the different sizes that the usual conversions allow.

Not sure if these sorts of conversions would be accepted, but my guess is that closing the transitive gap would be a good idea.
Repository: terminal
Issue: Add a `path` parameter to `toggleShaderEffects` 
Labels: Help Wanted,Area-Rendering,Area-Settings,Product-Terminal,Issue-Task


Add an "enablePixelShader" setting, which can be set to true or false.

If set to "false",  but a valid pixelShaderPath was specified, this would enable Windows Terminal to be started without the pixel shader visible, but available at the press of a key combination.
Repository: flutter
Issue: `flutter test` should have a `fail on stdout` option
Labels: a: tests,tool,P3,c: tech-debt,team-tool,triaged-tool

We sometimes accidentally have output in our framework tests. It would be nice to prevent that by considering any such output to be a failure.

I suggest we add a command line option `flutter test --fail-on-print` or some such, which captures all stdout (and stderr, I guess) and fails the overall run if there was any unexpected output from any of the testers.

Then we can enable that for ourselves.
Repository: godot
Issue: Switching to Full Screen Disables HDR In Windows 10
Labels: platform:windows,topic:rendering,documentation

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
Godot v3.3-rc9

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Windows 10, Nvidia 2080 Ti, Driver 461.09, GLES2/3

**Issue description:**
<!-- What happened, and what was expected. -->
When using an HDR enabled monitor on Windows 10, switching to full screen in a Godot project causes HDR to be disabled.
https://user-images.githubusercontent.com/3398643/115322900-e316d980-a13b-11eb-9a8a-bbaa4798f211.mp4

**Steps to reproduce:**
Create a new project and call "OS.window_fullscreen = true" it goes fullscreen but then disables HDR in Windows 10 (and remains disabled even after closing the game). With the minimal project I attached, just press the F key (though you need to be testing with an HDR monitor).

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[HDR Test.zip](https://github.com/godotengine/godot/files/6339928/HDR.Test.zip)
Repository: pytorch
Issue: Raise exception when torch.clamp min value underflows the input tensor's dtype
Labels: module: error checking,triaged

Consider the following code:

```python
x = torch.relu(torch.randn(10))
x = torch.clamp(x, min=1e-8)
y = 100 / x
```

The code above runs just fine when `x.dtype == torch.float` but fails when `x.dtype == torch.half`. The error is that 1e-8 can't be represented in fp16 and silently underflows to 0. Depending on the network it can be difficult to track down the source of this class of error (especially if a network was originally written assuming fp32 and is then trained with mixed precision).

Could we validate inputs for potential underflows and raise an exception if one is detected?
Repository: opencv
Issue: Arbitrary input shape to a fully convolutional nueral network
Labels: incomplete,category: dnn

I have a FCN for segmentation which in ONNX format. By default resolution, it works fine. How to make it support arbitrary resolution input?

I have tried setInputShape of Net, but it will cause an error.
Repository: neovim
Issue: Nvim visually glitched in windows shell and prompt, when minimize/maximize and scrolling.. repeated rows, etc
Labels: platform:windows,tui,display

I am using Windows Terminal (The new stuff from Microsoft Store), and I loved it, because of the tabs, and appearance settings, and all that jazz. However, I ran into some big issues with visual glitches and stuff.

I don't know how to exactly reproduce it, or what it's causing it... but generally when I minimize and restore the terminal, I notice to be most consistent.

I tried changing every setting I can. It seems like the issue persists.
If you need some settings I can post some detail stuff, but here is how it looks like:

![neovim fooked](https://user-images.githubusercontent.com/20478714/115326491-a542a100-a18d-11eb-9f88-3c93e628adbc.png)
![neovim fooked 2](https://user-images.githubusercontent.com/20478714/115326495-a673ce00-a18d-11eb-8412-d0bfb5bd4906.png)
![neovim fooked 3](https://user-images.githubusercontent.com/20478714/115326498-a673ce00-a18d-11eb-8481-cba083f72104.png)

Sometimes you can scroll above nvim like half the height, and you have repeat of the whole stuff above, sometimes the command line below is getting like 1/3 of the screen, etc.
I am new to Vim, I have been using it for about a week, and I am super excited, I don't want this to throw me off :(

Thanks for all the help!

Update: I tried reproducing it in normal CMD prompt, I can't... which means something about the windows terminal is what's making it.
I love having tabs (since CMD doesn't support them), for like git on one, npm run blabla on another, and having them on keybinds... to make it smoother, instead of opening 3-4 instances of cmd prompt and alt tabbing around, which is quite innacurate.
Repository: rust
Issue: rustdoc: add tests that validate emitted JS and HTML
Labels: A-testsuite,T-rustdoc,A-rustdoc-js

For the rustdoc tests, it would be great to validate all emitted JS and HTML in a build of the stdlib. For the JavaScript, we could use `node -c` to check that it parses. For HTML, we could use the [W3C Markup Validator](https://validator.w3.org/docs/install.html) or the newer [W3C Nu Html Checker](https://validator.w3.org/nu/about.html).
Repository: go
Issue: cmd/cgo: arch list is not in sync with cmd/go and go/build arch list
Labels: NeedsInvestigation,compiler/runtime

There are currently 3 places where supported architectures are enumerated:

 - cmd/cgo/main.go
 - cmd/go/internal/imports/build.go
 - go/build/syslist.go

The problem is that the list in cmd/cgo/main.go is out of sync with the other lists.

From cmd/cgo/main.go:

```go
var ptrSizeMap = map[string]int64{
	"386":      4,
	"alpha":    8,
	"amd64":    8,
	"arm":      4,
	"arm64":    8,
	"m68k":     4,
	"mips":     4,
	"mipsle":   4,
	"mips64":   8,
	"mips64le": 8,
	"nios2":    4,
	"ppc":      4,
	"ppc64":    8,
	"ppc64le":  8,
	"riscv":    4,
	"riscv64":  8,
	"s390":     4,
	"s390x":    8,
	"sh":       4,
	"shbe":     4,
	"sparc":    4,
	"sparc64":  8,
}
```

From cmd/go/internal/imports/build.go:

```go
var KnownArch = map[string]bool{
	"386":         true,
	"amd64":       true,
	"amd64p32":    true, // legacy; don't remove
	"arm":         true,
	"armbe":       true,
	"arm64":       true,
	"arm64be":     true,
	"ppc64":       true,
	"ppc64le":     true,
	"mips":        true,
	"mipsle":      true,
	"mips64":      true,
	"mips64le":    true,
	"mips64p32":   true,
	"mips64p32le": true,
	"ppc":         true,
	"riscv":       true,
	"riscv64":     true,
	"s390":        true,
	"s390x":       true,
	"sparc":       true,
	"sparc64":     true,
	"wasm":        true,
}
```

`cgo` have `alpha`, `m68k` `nios2` `sh` and `shbe`, and is missing `amd64p32`, `mips64p32` and `mips64p32le`.
I don't know if there is a reason for the difference, but the problem is that the additional architectures known to `cgo` are used as a build tag in `cmd/vendor/golang.org/x/sys/unix` (in `endian_big.go` and `endian_big.go`), and since they are not known by `go`, they are probably ignored.

Another small issues is that the architecture list in `cmd/go/internal/imports/build.go` is not sorted correctly.

I'm not sure if this should be reported as an issue about `cmd/cgo` or about `golang.org/x/sys/unix`.
Probably this is harmless.
Repository: PowerToys
Issue: [FancyZones Editor - Edit Custom layout]: On activating ‘delete layout’ button, focus doesn’t land on the delete popup and the narrator doesn’t announce the delete warning message.
Labels: Issue-Bug,FancyZones-Editor,Product-FancyZones,Priority-2,Area-Accessibility,A11yE+D,A11ySev3,A11yWCAG

### Microsoft PowerToys version

"0.35.0"

### Running as admin

- [ ] Yes

### Area(s) with issue?

FancyZones Editor

### Steps to reproduce

**Test Environment:**
**OS:** Windows 10 Build 21354.1
**App version:** 0.35.0
**App name:** PowerToys
**Screen Reader:** Narrator
**Tool:** Accessibility Insight for Windows

**Repro Steps:**

1. Launch 'PowerToys' application.
2. Turn on the narrator.
3. Application will get open with default list item 'General' selected.
4. Navigate to 'FancyZones' at the left side of the pane and activate it.
5. Now navigate to 'Launch layout editor button and activate it.
6. FancyZones editor window will get open.
7. Navigate to 'Edit layout' button of any layout (say Grid) under Custom and activate it.
8. Edit layout dialog gets open.
9. Navigate to 'Delete layout' button via tab key and press 'enter' key to activate it.
10. Observe the issue.

**User Impact: Priority-2**
If a user navigates sequentially from one element to another, forced focus changes can confuse the keyboard dependent user. User will face difficulty in interacting with desired element. 

**MAS Reference:**
https://microsoft.sharepoint.com/:w:/r/sites/accessibility/_layouts/15/Doc.aspx?sourcedoc=%7BA3E028A8-2819-4CDA-B901-EC19FF068AA6%7D&file=MAS%203.2.1%20%E2%80%93%20On%20Focus.docx&wdLOR=cB8655064-3C13-4D72-AD8E-D1E431EBFAA3&action=default&mobileredirect=true&cid=46b7f46f-8fed-432f-9f68-2d65db259080

[MAS3.2.1_Actvating delete button.zip](https://github.com/microsoft/PowerToys/files/6341060/MAS3.2.1_Actvating.delete.button.zip)


### ✔️ Expected Behavior

On activating ‘delete layout’ button, focus should land on the 'Delete' button of the delete popup and the narrator should announce the delete warning message information as "Delete button are you sure are you sure you want to delete this layout dialog".

### ❌ Actual Behavior

Focus doesn’t goes to the delete popup and the narrator also doesn’t announce the delete warning message once the user activates the ‘delete layout’ button.
Activating ‘delete layout’ button narrator stays silent.

### Other Software

_No response_