sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: [abc.net.au]   Youtube embed results in "Unable to extract video urls" error.
Labels: bug

- [x] I've **verified** and **I assure** that I'm running youtube-dl **2016.09.15**
### Before submitting an _issue_ make sure you have:
- [x] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [x] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your _issue_?
- [x] Bug report (encountered problems with youtube-dl)
- [ ] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other

```
$ y -v http://www.abc.net.au/news/2015-08-17/warren-entsch-introduces-same-sex-marriage-bill/6702326
[debug] System config: []
[debug] User config: ['-4', '-f', 'best', '--prefer-free-formats', '--no-cache-dir', '--no-mtime', '--youtube-skip-dash-manifest']
[debug] Command-line args: ['-v', 'http://www.abc.net.au/news/2015-08-17/warren-entsch-introduces-same-sex-marriage-bill/6702326']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.09.15
[debug] Python version 3.6.0b1 - Linux-4.8.0-rc5-686-i686-with-debian-stretch-sid
[debug] exe versions: ffmpeg 3.1.3, ffprobe 3.1.3, rtmpdump 2.4
[debug] Proxy map: {}
[abc.net.au] 6702326: Downloading webpage
ERROR: Unable to extract video urls; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/YoutubeDL.py", line 694, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/common.py", line 355, in extract
    return self._real_extract(url)
  File "/usr/local/lib/python3.6/dist-packages/youtube_dl/extractor/abc.py", line 67, in _real_extract
    raise ExtractorError('Unable to extract video urls')
youtube_dl.utils.ExtractorError: Unable to extract video urls; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

```

http://www.abc.net.au/news/2015-08-17/warren-entsch-introduces-same-sex-marriage-bill/6702326
Repository: rust
Issue: In some cases, the compiler doesn't find a proper macro rule even when it exists
Labels: A-macros,T-compiler,C-bug

Macro rules, that are generated with macro rules, are not working in some cases. See the following example:

```
/* lib.rs */
macro_rules! gen_lookup {
    ($e:expr) => {
        #[macro_export]
        macro_rules! lookup {
            ($e) => { "bug" };
            ("works") => { "works" };
        }
    }
}

gen_lookup!("bug");

pub fn run()
{
    println!("{}", lookup!("works"));
    // println!("{}", lookup!("bug"));
}
```

```
/* main.rs */
#[macro_use]
extern crate rustbug;

fn main() {
    rustbug::run();
    println!("{}", lookup!("bug"));
}
```

When you include the commented line, you should get `error: no rules expected the token `"bug"``. This is especially weird, since the exactly same line works in case where the macro is used from an external crate (see main.rs). As usual, when gen_lookup is removed and lookup macro is written manually, everything works as expected.
Repository: godot
Issue: inst2dict does not turn classes inside classes to dict
Labels: bug,discussion,topic:core,topic:gdscript,confirmed

inst2dict does not turn classes inside classes to dict. 

Here is an example of to_json() output;

```json
{
	"description": "Some Desc",
	"id": 1337,
	"@path": "res://data/classes/project_class.gd",
	"tasks": [
		"[Reference:835]",
		"[Reference:836]",
		"[Reference:837]"
	],
	"@subpath": "",
	"name":"P Name"
}
```

I believe the classes (Reference:8XX) should also be converted to Dictionary for this to work as intended. :)

Currently; a workaround for this is to save the other classes as Dict, and use a set/get where you convert between class and dictionary. However I am sure inst2dict should also include subclasses. 

Hope to see a fix implemented in the future :)
Repository: vscode
Issue: Possibility to display line endings in text area
Labels: feature-request,editor-render-whitespace

- VSCode Version: 1.5
- OS Version: Win 7 x64

At the moment there is only the little statusbar menu which display/change the line ending if the actual file. But sometimes it would be great to see the line endings directly in every line (see atom f.e.) especially when there are mixed line endings (not good, but this happens from time to time).

Greetings
Tonka
Repository: create-react-app
Issue: Duplicate React
Labels: contributions: up for grabs!,issue: proposal,difficulty: medium

“Duplicate React” is an incredibly common issue that produces weird errors and confuses beginners and advanced users alike. It happens when you install `react` but some component you’re using installs its own copy of `react` (often with a different version).

React doesn’t throw in such cases because there are situations in which multiple React may validly coexist in the page (e.g. a third-party React-powered widget on a React-powered website). However it seems to make much less sense inside a single bundle. Webpack is in a perfect position to do this, but of course it won’t add any library-specific code. The good news is that we’re on top of webpack, so we might be able to do something.

There are several possible options:
- 1. Do nothing. (Like now)
- 2. Warn/error on duplicate React in the bundle.
- 3. Alias React to always be the one on the top level, regardless of Node resolution mechanism.

Option (3) seems like the easiest to do (we can special-case React in our Webpack, and maybe Jest, configs). It also “just works” from the user’s point of view because they don’t need to delete any `node_modules` or mess with projects’ `peerDependencies`. The downside is the ecosystem loses because project authors don’t become aware that their components incorrectly depend on React, or that their components are outdated.

Option (2) seems like more work. It’s not immediately clear what message we could provide. Would we tell the user to delete the extra `react` from the respective `node_modules` subfolder? Would we tell them to file an issue with that component or library?

Finally, we could stick with doing nothing.
Any thoughts?
Repository: go
Issue: os/exec: Cannot execute command with space in the name on Windows, when there are parameters
Labels: OS-Windows,NeedsFix,early-in-cycle

Go 1.7.1 on windows-amd64, Windows 10 latest.

Consider a test project:

```
src/github.com/calmh/wincmdtest/
    main.go
    folder name/
        test.bat
```

`main.go` contents:

``` go
package main

import (
    "fmt"
    "os/exec"
    "strings"
)

func main() {
    execCmd("./folder name/test.bat")
    execCmd("./folder name/test.bat", "one param")
}

func execCmd(path string, args ...string) {
    fmt.Printf("Running: %q %q\n", path, strings.Join(args, " "))
    cmd := exec.Command(path, args...)
    bs, err := cmd.CombinedOutput()
    fmt.Printf("Output: %s", bs)
    fmt.Printf("Error: %v\n\n", err)
}
```

`folder name/test.bat` contents:

``` bat
@echo off
echo Success
```

Expected output is two runs with "Success" in them.

Actual:

```
C:\Users\jb\Go\src\github.com\calmh\wincmdtest>go run main.go
Running: "./folder name/test.bat" ""
Output: Success
Error: <nil>

Running: "./folder name/test.bat" "one param"
Output: '.' is not recognized as an internal or external command,
operable program or batch file.
Error: exit status 1
```

It appears that having params on a command, where the command contains a space, breaks the parsing of it. I haven't been able to work around this by experimenting with various ways of quoting the command, using backslashes or slashes, etc.
Repository: nvm
Issue: Using the system node as default
Labels: needs followup

I've done `nvm alias default system`, and doing `nvm use system` shows `Now using system version of node: v6.5.0 (npm v3.10.6)`. But if I do `nvm exec system node app.js` I get an error:

```
N/A: version "system" is not yet installed.

You need to run "nvm install system" to install it before using it.
```

What's the correct way to use the system node as the default? (I only switch to nvm versions of node when I'm in a directory with an .nvmrc.)
Repository: rust
Issue: Closures should infer to capture by copy
Labels: C-enhancement,A-closures,T-lang,A-inference,C-feature-request

Inspired by a common stumbling block with `Iterator::flat_map`.

This code does not compile:

``` rust
(0..10).flat_map(|i| (0..i).map(|j| i + j))
```

```
error: `i` does not live long enough
```

[(playground code)](https://play.rust-lang.org/?gist=8579249badd19920bd552376eb1fbb3a&version=stable&backtrace=0)

The problem: `i` is a local variable and captured by reference in a closure we're trying to return. It's an integer, its data size is equal or smaller as a value instead of a reference.

Can rustc infer that the closure should capture `i` by "move" here (Copy)?
Repository: go
Issue: cmd/go: drop runtime from plugins
Labels: NeedsFix

It looks like plugins contain a copy of the runtime. I guess that copy is unused, and could probably be dropped, reducing binary size.
Repository: rust
Issue: Collision between extern-block fn and #[no_mangle] fn not detected
Labels: A-FFI,T-lang,T-compiler,C-feature-request

This code compiles and `x::foo` calls itself recursively.

``` rust
#![crate_type="lib"]

extern {
    fn foo();
}

pub mod x {
    #[no_mangle]
    pub unsafe extern "C" fn foo() { ::foo() }
}
```

https://play.rust-lang.org/?gist=dc191ae3cfb84887ba39bbf327a2e6fe&version=stable&backtrace=1

We don't end up seeing a re-definition because the `foo` in the extern block only creates a declaration.

EDIT: Here's an example that is actually a problem we should probably prevent:

``` rust
#![crate_type="lib"]

extern {
    fn foo(x: i32);
}

pub mod x {
    #[no_mangle]
    pub unsafe extern "C" fn foo() { ::foo(0) }
}
```

This happily compiles, and probably shouldn't.
Repository: awesome-mac
Issue: 协作工具
Labels: vote

notion  https://www.notion.so/
Repository: opencv
Issue: calibration using circle grid pattern has perspective bias
Labels: feature,category: calib3d

##### Detailed description

the perspective bias using circle grid is not considered in the calibrtion pipeline, when using a circle grid pattern, a circle on the board in real world, projects on the image to be an ellipse (unconsidering distortion), according to the projective geometry, the center of the circle does not correspond to the center of the ellipse (or the centroid of the blob), this is showed in the following picture:

http://paste.ubuntu.org.cn/4219097

the perspective bias affects the calibration precision, this is detailed in the paper

Heikkila J. Geometric camera calibration using circular control points[J]. IEEE Transactions on pattern analysis and machine intelligence, 2000, 22(10): 1066-1077.
Repository: rust
Issue: Rust has trouble seeing higher ranked lifetimes through generics
Labels: A-type-system,A-lifetimes,A-closures,T-lang,T-compiler,C-bug,T-types,A-higher-ranked

Rust has trouble seeing that a generic function is "generic" over higher ranked lifetimes. This behavior is best described by example. Given:

``` rust
fn id<X>(x: X) -> X { x }

fn id_wrapped<'a, T>(v: &'a T) -> &'a T {
    // Defined for<'a>. No coercion.
    id::<&'a T>(v)
}

fn has_hrl<F: Fn(&()) -> &()>(f: F) {}

fn main() {
    has_hrl(id);
    has_hrl(id_wrapped);
    has_hrl(|x| id(x));
}
```

Rust complains:

``` rust
error[E0281]: type mismatch: the type `fn(_) -> _ {id::<_>}` implements the trait `std::ops::Fn<(_,)>`, but the trait `for<'r> std::ops::Fn<(&'r (),)>` is required (expected concrete lifetime, found bound lifetime parameter )
  --> tmp.rs:11:5
   |
11 |     has_hrl(id);
   |     ^^^^^^^
   |
   = note: required by `has_hrl`

error[E0271]: type mismatch resolving `for<'r> <fn(_) -> _ {id::<_>} as std::ops::FnOnce<(&'r (),)>>::Output == &'r ()`
  --> tmp.rs:11:5
   |
11 |     has_hrl(id);
   |     ^^^^^^^ expected bound lifetime parameter , found concrete lifetime
   |
   = note: concrete lifetime that was found is lifetime '_#0r
   = note: required by `has_hrl`

error: aborting due to 2 previous errors
```

However, the `has_hrl(id_wrapped)` and `has_hrl(|x| id(x))` calls demonstrate that, at some level, the rust type checker infers that `id` implements `for<'r> Fn(&'r ()) -> &'r ()`. That's why I filed this as a bug instead of an RFC issue. However, I can move this if you feel that it's too much of a feature request.

---

My motivation is functional programming. Not being able to infer that a generic function is defined for some HRL makes it impossible to use such functions with, e.g., `Iterator::filter`.
Repository: TypeScript
Issue: Unintuitive error message with 'unreachable' code
Labels: Suggestion,Help Wanted,Effort: Difficult,Domain: Error Messages

<!-- BUGS: Please use this template. -->

<!-- QUESTIONS: This is not a general support forum! Ask Qs at http://stackoverflow.com/questions/tagged/typescript -->

<!-- SUGGESTIONS: See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md -->

**TypeScript Version:**  2.0.02

**Code**

``` ts
const enum Keys {
    Tab = 10,
    Shift = 13
}

function bug() {
    let key: Keys;

    if (key === Keys.Tab) {
        return;
    }

    if (key === Keys.Tab || key === Keys.Shift) {
        console.log('Bug');
    }
}
```

On line 13 you get an error message that === can't be applied as an operator. Took me quite some time to find out that the same comparison was above (the real code was a little bit more complicated) and was leaving the function.
Repository: kubernetes
Issue: Replication controller (and RS): Don't make more than 1k unschedulable pods
Labels: priority/important-soon,area/controller-manager,area/reliability,sig/apps,area/workload-api/replicaset,lifecycle/frozen

Observed a cluster with a nonsensically high value for spec.replicas and replication controller was trying to honor it, and crushing the master in the process. RC should probably not make more than a reasonable number of pending pods, maybe like 500 or 1000, it should make enough to give signal to sizers looking for unscheduled pods but not more. Certainly not 150k+ as observed.
Repository: react
Issue: input autoFocus causes focus to be emitted before ref
Labels: Type: Bug,Component: DOM,Difficulty: challenging

https://jsfiddle.net/nnwd2c34/

Can reproduce on Chrome, but not in IE11.
Repository: rust
Issue: Add traits w/ auto-deriving for soundly serializing/inspecting/transforming rustc types.
Labels: C-cleanup,A-metadata,T-compiler

Currently, we're limited to the general-purpose `Eq`, `Ord`, `Hash`, `Encodable` and `Decodable` traits, even though the compiler often has more unconventional desires, involving contexts and custom behaviors.

There are several special-purpose traits already in the compiler, such as AST/HIR `Folder`/`Visitor` and the two-in-one `TypeFoldable` (which also does visiting).

Also, #36551 adds a specialization mechanism in the bundled `rustc_serialize` to work around the fact that `Encodable` and `Decodable` have their methods be generic over the encoder/decoder instead of the trait, but this abuses the yet-unclosed lifetime soundness hole in specialization (#31844):

``` rust
impl<'a, 'tcx> SpecializedDecoder<Ty<'tcx>> for DecodeContext<'a, 'tcx> {...}
```

That `impl` requires that the `'tcx` of the decoded `Ty` match the `'tcx` of the decoder, but this _cannot_ be enforced through specialization as the lifetime relationships do not exist before monomorphization.

A better solution would involve custom traits that can dispatch over the decoder w/o specialization, i.e.:

``` rust
impl<'a, 'tcx> Decodable<DecodeContext<'a, 'tcx>> for Ty<'tcx> {...}
```

To make all of this ergonomic, auto-deriving is necessary, and I believe macros 1.1 (perhaps helped by a permanent switch to rustbuild) can make it happen.

Last but not least, it may be possible to generalize encoding/decoding and visiting/folding/relating into a single (or a pair of) abstraction(s), but I'd have to leave that to someone who understands tree folding, transducers, and perhaps Haskell lenses, although there's no guarantee they map nicely to Rust.

cc @rust-lang/compiler
Repository: kubernetes
Issue: kube-apiserver: limit the size of node objects more than other objects
Labels: priority/important-soon,sig/api-machinery,lifecycle/frozen

Due to the frequency of status updates and the fact that etcd saves the entire object with every heartbeat, Kubernetes is more sensitive to the size of node objects than other objects in the system.

In practice, node objects that are merely 150k are enough to take down a small master.

We should think about what a sane size limit is, what to do when a component like kubelet attempts to violate the size limit, and whether maybe we should start storing the heartbeat time in a separate location to eliminate this class of problems entirely.

We'll probably need to reevaluate this when we start running etcd 3.
Repository: youtube-dl
Issue: Request: playlist thumbnail support
Labels: request

Thumbnails for playlists would be very useful for e.g. albums.
Repository: angular
Issue: Binding to [name] on radio inputs does not provide browser-default tab interaction
Labels: type: bug/fix,freq2: medium,workaround2: non-obvious,area: forms,state: confirmed,forms: directives,P4

**I'm submitting a ...**  (check one with "x")

```
[x] bug report => search github for a similar issue or PR before submitting
```

**Current behavior** 
When the the `name` attribute of a radio input is bound using `[name]='name'`, it appears that the actual name attribute is not set with the bound value.  This causes incorrect tab behavior for groups of radios.  If I have a component with 3 radios, and repeat that component 3 times, then all 9 radios behave as if they had the same name (they collectively act as a single tab stop, and the arrow keys can be used to navigate between all 9 when any radio is focused).  See https://plnkr.co/edit/SXxIxZM1BuMsnAZnN1UF?p=preview

When binding to `[attr.name]`,  tab/arrow key navigation works as expected, but other radios that share the same value are also selected.  I.E. when selecting `Option 1` in group 1, `Option 1` is selected in groups 2 and 3 as well.  However, this appears to not effect the value of the `FormControl`, the selected value and the selected radio become out of sync.
See: https://plnkr.co/edit/5jHshpyQHezLqZEXqz5v?p=preview

When binding to _both_ `[attr.name]` and `[name]` I get the expected behavior, but it seems like I should only need to bind to one or the other.  See: https://plnkr.co/edit/7ZnsSzTCuyiufCdjX5zN?p=preview

**Expected behavior**

Binding to `[name]` should set the input's name attribute so that the correct tab behavior is preserved.  In the above example, each component's 3 radios should act as a single tab stop, and using the arrow keys should cycle between each of the component's 3 radios.

If binding to both `[name]` and `[attr.name]` is required, it should probably be documented, maybe in [FormControlDirective](https://angular.io/docs/ts/latest/api/forms/index/FormControlDirective-directive.html)?

**What is the motivation / use case for changing the behavior?**
My app supports custom radio fields, so the number of fields and their options are all runtime values.  I'm trying to create a reusable `radio-group` which accepts bindings to `name`, `options`, and `formControl`.
- **Angular version:** 2.0.0
- **Browser:** all
Repository: angular
Issue: Support disabling individual radios without disabling control
Labels: feature,state: Needs Design,freq2: medium,area: forms,feature: under consideration

```
<input type="radio" name="food" ngModel disabled>
<input type="radio" name="food" ngModel>
```

Must wait for a minor release to make API changes.
Repository: go
Issue: x/build: record and collect compiler benchmarks
Labels: Builders,NeedsInvestigation

Recently we added a -bench flag to cmd/compile to benchmark compiler phases.  It might be interesting if the builders used this flag and then persisted the output file so we could monitor compiler performance over time.

There's a risk that measuring the standard library compile time is confounded with changes to the standard library, but I think only a couple packages (runtime, net, net/http) still seem under active development.  So it's probably still a decent signal.

/cc @bradfitz @griesemer
Repository: vscode
Issue: Mac: Provide a setting to hide the title bar and inline the window controls
Labels: feature-request,ux,macos,titlebar

Hello there, a lot of the standard apps in recent versions of macOS have started to inline their titlebar into their tabs, menu buttons etc. I assume this is mainly to save vertical space on laptops. However, like all UI trends, apps that don't quite keep up end up feeling old-fashioned 👯 

I started a fork of VS Code that uses the inline style:

![screen shot 2016-09-21 at 12 59 09](https://cloud.githubusercontent.com/assets/49038/18710082/332cefb6-7ffb-11e6-8303-338bee1d6c35.png)

There needed to be a few changes:
- I moved the sidebar width to 76, to fit the traffic lights
- I increased the height of the elements that act as the titlebar by one pixel, mainly so that they align with the centre position of the titlebar items
- Allow mouse dragging via the sidebar, and the title elements

Fork: https://github.com/orta/vscode/tree/inline-titlebar
Changes: https://github.com/orta/vscode/compare/master...mac-titlebar-inline

I realise that VS Code is a cross-platform project, and so these changes should _probably_ only be applied in the context of macOS, which I'm happy to look into with some advice (I don't have a windows/linux machine to hand for example).  

I also know that no-one wants big unexpected UI changes on their OSS projects, so I've not made it as a PR, but I'd love to know if/what I can do to move this upstream?

_Sidenote:_ If someone can tell me how, I'm happy to make a downloadable build for people to try too, I couldn't find a way to do it - I'm still quite fresh to npm projects.