sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: Support for mixlr.com 
Labels: site-support-request

## Please follow the guide below

- You will be asked some questions and requested to provide some information, please read them **carefully** and answer honestly
- Put an `x` into all the boxes [ ] relevant to your *issue* (like that [x])
- Use *Preview* tab to see how your issue will actually look like

---

### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2016.12.22*. If it's not read [this FAQ entry](https://github.com/rg3/youtube-dl/blob/master/README.md#how-do-i-update-youtube-dl) and update. Issues with outdated version will be rejected.
- [x] I've **verified** and **I assure** that I'm running youtube-dl **2016.12.22**

### 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*?
- [ ] Bug report (encountered problems with youtube-dl)
- [x] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other

http://mixlr.com/infomenonitas/showreel/infomenonitas-on-mixlr-160/
Repository: gin
Issue: How remove route ? online!!!
Labels: feature

How can i remove route ? online!!!
Repository: TypeScript
Issue: Extra checks with -d not executed with --noEmit
Labels: Bug

**TypeScript Version:**  2.1.4

**Code**

```ts
class SomeClass {

}

export = new SomeClass();
```

**Actual behavior:**
This code should give an error, as the exported instance is of a private type. The following error is reported when compiling with `-d`, but not without it:
```
error TS4082: Default export of the module has or is using private name 'SomeClass'.
```
The disadvantage of using `-d` is that it generates `.d.ts` files, which should be ignored (because they are auto-generated). I can not add `*.d.ts` to my gitignore, as some of my interfaces are `.d.ts` files.

I tried to resolve this issue by adding `--noEmit` to the compiler options, but this hides the error (as if it was compiled without `-d`).

**Expected behavior:**
Either report the error always, or report it with `-d` and `--noEmit`.
Repository: vscode
Issue: Add extension point for custom "prefix behaviors" in command palette
Labels: feature-request,api

`git`, `task`, `view` prefixes behavior in command palette is really cool, would be really nice if we could extend command palette with custom prefixes. 

https://twitter.com/ErichGamma/status/814149913156186112
CC: @egamma
Repository: TypeScript
Issue: Type parameter constrained to union cannot be exhaustively narrowed to 'never'
Labels: Suggestion,In Discussion

<!-- 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.1.1 (http://www.typescriptlang.org/play/index.html)

**Code**

```ts
type Type = "a" | "b"

function isA(a: any): a is "a" {
    return a === "a"
}

function isB(a: any): a is "b" {
    return a === "b"
}

function assertNever(arg: never) {
    throw new Error("This should never be called")
}

function handleAction<T extends Type>(type: T) {
    if (isA(type)) {
        return type
    } else if (isB(type)) {
        return type
    } else {
        assertNever(type)
    }
}
```

**Expected behavior:**
No compilation error

**Actual behavior:**
Argument of type 'T' is not assignable to type 'never'
Repository: opencv
Issue: OpenGL/OpenCL interop ATI card broken at initializeContextFromGL
Labels: bug,category: ocl

##### System information (version)
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015

##### Detailed description

Opengl/OpenCL interop does not work with ATI graphic cards, e.g. RX 480. 
Specifically, the call to cv::ogl::ocl::initializeContextFromGL(); does crash the program using ATI cards. The program however runs fine using an NVidia card.

The reason seems to be, that the code in opengl.cpp following line 1599 tries to detect the graphic cards extension "cl_khr_gl_sharing" using th CL_PLATFORM_EXTENSIONS, which seems to be the incorrect way to do for ATI cards. I have read, that one needs to iterate the devices rather than the platform to search for extensions.

Commenting out the extension check in lines 1640-1641
 //if (!strstr((const char*)extensionStr, "cl_khr_gl_sharing"))
               // continue;
solves the issue for the ATI card, since the context is generated without explicitly checking if the extension is available. This part probably needs to be replaced with proper extension checking code.

##### Steps to reproduce

Use the following if statement using an AIT card like the RX 480.

if (cv::ocl::haveOpenCL())
{
	cv::ogl::ocl::initializeContextFromGL();
	cv::ocl::setUseOpenCL(true);
}
Repository: three.js
Issue: Allow specifying mipmap bias for textures
Labels: Enhancement

Currently there doesn't seem to be any way to enable mipmap bias for textures. For some uses (eg ground/road textures) a negative mipmap bias is often used to tune blur/aliasing trade-off.

I can hack the bias globally by adding it as a third parameter to `texture2D` in eg. [map_fragment.glsl](https://github.com/mrdoob/three.js/blob/dev/src/renderers/shaders/ShaderChunk/map_fragment.glsl#L3), but unfortunately I have no idea how to nicely implement this for `three.js`.

Below is an example of adding such bias (rendered using `THREE.LinearMipMapLinearFilter` and 16x anisotropy, 3x blowup):
![mipmapbias](https://cloud.githubusercontent.com/assets/1301087/21549576/c6e1c210-cdfb-11e6-8c01-36be4f122ed8.png)
Repository: youtube-dl
Issue: Add support for neoxkidz.com
Labels: geo-restricted

- [x] I've **verified** and **I assure** that I'm running youtube-dl **2016.12.30**
- [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
- [x] Site support request (request for adding support for a new site)

### Description of your *issue*, suggested solution and other information

Please add support for neoxkidz.com.
Example (region locked Spain): http://www.neoxkidz.com/dibujos-series-infantiles/shin-chan/cap-759-voy-con-papa-a-la-piscina_20160623576fc5596584a88907b82451.html
Repository: go
Issue: database/sql: missing escape functions
Labels: Thinking,FeatureRequest

### What version of Go are you using (`go version`)?

go version go1.7.4 linux/amd64

### What operating system and processor architecture are you using (`go env`)?

GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/nefthy/go-test/"
GORACE=""
GOROOT="/usr/lib/go"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
CC="x86_64-pc-linux-gnu-gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/home/nefthy/go-test/tmp/go-build451484149=/tmp/go-build -gno-record-gcc-switches"
CXX="x86_64-pc-linux-gnu-g++"
CGO_ENABLED="1"



### What did you do?

There are situations when strings need to be escaped in queries that can not be done with placeholders. An example the following queries cannot be expressed with ? placeholders:

```sql
SELECT id, ? FROM table
-- Must be escaped as an identifier
SELECT id FROM ?
-- Also identifier quoting
SELECT id FROM table WHERE ? LIKE ?
-- With either the first or second parameter being a column reference
```

Using Sprintf is no option, since the identifiers need to be properly quoted. The quoting and escaping is inherently vendor specific and may even depend on configuration on a per database/connection basis (hello there MySql...).  

### What did you expect to see?

The driver must export Quoting which are passed along by the database/sql Api. As far as I can tell the folling functions are needed

- QuoteString: quotes and escapes a string so it can be used as a string literal (ex: mysql_real_escape_string)
- QuoteIdentifier: quote and escapes a string so it can be used as an identifier*
- QuoteBinary: quote and escapes binary data (ex: PQescapeBytea)

* I am not sure if all identifiers are quoted consistently among all Databases. It might be that separate functions are needed depending on the type of the identifier.

### What did you see instead?

No escaping/quoting functions
Repository: angular
Issue: @angular/language-service ability to quiet errors...
Labels: feature,area: language-service,feature: under consideration

```
[ ] bug report => search github for a similar issue or PR before submitting
[x ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
```

**Current behavior**
```@angular/language-service``` will report every issue and it makes it very hard to adopt at this late stage to new projects.

**Expected behavior**
I would love to be able to quiet errors in templates via something like:
```<!-- NG-IGNORE-ERROR-->``` before the line and 
```<!-- NG-IGNORE-PAGE-ERROR-->``` to ignore entire template / page errors


**Minimal reproduction of the problem with instructions**
none

**What is the motivation / use case for changing the behavior?**
it will make it very hard to move to this awesome project without a ability to quiet errors and slowly enable

**Please tell us about your environment:**
Windows 10 x64

* **Angular version:** 2.0.X
latest all ng2 / ts 2.1

* **Browser:** [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Chrome
 
* **Language:** [all | TypeScript X.X | ES6/7 | ES5]
TS
Repository: rust
Issue: Unable to constrain associated types in trait inheritance
Labels: A-type-system,T-compiler,C-bug,T-types

```rust
struct Foo;
struct Bar;

pub trait Base{
    type F;
    type B;
}
//***************************
// Doesn't work
//pub trait BaseHello: Base
//    where Self::F: Hello,
//          Self::B: Hello{}

pub trait BaseHello: Base{}
impl<B: Base> BaseHello for B
    where B::F: Hello,
          B::B: Hello{}

//***************************
pub trait Hello{
    fn hello(&self);
}

impl Hello for Foo{
    fn hello(&self){
        println!("Foo");
    }
}

struct FooBarBase;
impl Base for FooBarBase{
    type F = Foo;
    type B = Bar;
}

impl Hello for Bar{
    fn hello(&self){
        println!("Bar");
    }
}

struct Test<B: BaseHello>{
    f: B::F,
    b: B::B
}

// doesn't work
impl<B: BaseHello> Test<B>{
    fn hello(&self){
        self.f.hello(); 
        self.b.hello(); 
    }
}

fn main() {
    let test = Test::<FooBarBase>{f: Foo, b: Bar};
    // works
    test.f.hello();
    test.b.hello();
}
```
[Playground](https://play.rust-lang.org/?gist=d3e005df995e2192c582bc135679c2eb&version=stable&backtrace=0)

The main problem is that we can not write

```rust
// Doesn't work
pub trait BaseHello: Base
    where Self::F: Hello,
          Self::B: Hello{}
```

The workaround is to impl the trait explicitly like this

```rust
pub trait BaseHello: Base{}
impl<B: Base> BaseHello for B
    where B::F: Hello,
          B::B: Hello{}
```
But this means that Rust doesn't know the constrains of `BaseHello`, if `BaseHello` is used as a constrain.
```rust
// doesn't work
impl<B: BaseHello> Test<B>{
    fn hello(&self){
        self.f.hello(); 
        self.b.hello(); 
    }
}
```

I couldn't find any related issues. Is this a bug? Are there any workarounds?
Repository: nvm
Issue: `nvm use -` to quickly switch to last active version
Labels: feature requests

This would be to mimic the behaviour of the `-` in either; [`cd -`](http://ss64.com/bash/cd.html) or [`git checkout -`](https://git-scm.com/docs/git-checkout#git-checkout-ltbranchgt).

I'm happy to attempt a PR if this shortcut is a feature worth pursuing.
Repository: vscode
Issue: Expose -webkit-text-stroke (Fonts are too thin on Ubuntu 16.10)
Labels: feature-request,editor-core,font-rendering

- VSCode Version: 1.8.1
- OS Version: Ubuntu 16.10 amd64

I use VS Code on Windows, Mac and since recently Linux, and for some reason text looks much thinner on Linux than on other systems, which makes it a little bit harder to read. Here is a screenshot:

![vscode-fonts](https://cloud.githubusercontent.com/assets/4525736/21577973/542305f2-cfa1-11e6-8e73-821909abeb4b.png)

Font settings:
```
    "editor.fontSize": 14,
    "editor.fontFamily": "Source Code Pro",
    "window.zoomLevel": 0
```

System font settings:
- Antialiasing: RGBA
- Hinting: Slight
- Text scaling factor: 1.00

I've tried various combinations of antialiasing and hinting settings but they all look as bad or worse.
Repository: vscode
Issue: Preserve undo/redo buffer when saving a file "as" or untitled file
Labels: feature-request,undo-redo,workbench-untitled-editors

- VSCode Version: 1.8.1
- OS Version: Windows 10

Steps to Reproduce:

1. Undo last edits.
2. Save As.
3. Try Redo to re-instate last edits, but nothing happens.

This is a workflow I have done in many other editors where I realize I want to keep an old version of something I am working on, just in case I screw up. To my dismay in VSCode it made me lose all my edits.
Repository: TypeScript
Issue: Add a refactoring that annotates an implicit or explicit any with a best guess type inferred from its use sites
Labels: Suggestion,Committed,Domain: Quick Fixes

I would very much appreciate having a codefix (refactoring) that, given an explicit `any` annotation, offers to change it to an `{}` annotation.

For example, given
```ts
function log(x: any) {
  console.log(x);
}
```
a code fix would be offered to change the declared type of `x` to `{}` resulting in
```ts
function log(x: {}) {
  console.log(x);
}
```

However, given
```ts
function log(x: any) {
  console.log(x.name);
}
```
a code fix would be offered to change the declared type of `x` to `{ name: any }` resulting in
```ts
function log(x: {name: any}) {
  console.log(x);
}
```
Repository: rust
Issue: Cannot silence test runner
Labels: T-libs-api,A-libtest,C-feature-accepted

[IRC Logs](https://botbot.me/mozilla/rust/2017-01-01/?msg=78674895&page=5)

```
cargo 0.17.0-nightly (740f9c0 2016-12-29)
```

We should be able to silence the test runner's stdout via `--quiet` like `build` and `clean`'s `--quiet` flag, but alas this is not currently done.

```
tmba:sentinel thill $ cargo test --quiet -- quiet

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured


running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured
```

```
tmba:sentinel thill $ cargo test --quiet

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured


running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured
```

ref: https://github.com/rust-lang/cargo/issues/3482
Repository: create-react-app
Issue: Support Lerna and/or Yarn Workspaces
Labels: tag: new feature

Are there any plans to support Lerna? By default Lerna uses the `packages` directory to store the packages. Right now the content of that folder is not transpiled so it's not possible to use ES6 code in there. It would be nice to have the possibility to use Lerna to create a monorepo application with create-react-app. 

I've tried using the `src` directory with Lerna, but that conflicts with *not* ignoring `node_modules` directory inside the `src` directory, so it gives a ton of lint errors when you do so.
Repository: rust
Issue: Type errors in macros have poor spans
Labels: C-enhancement,A-diagnostics,A-macros,T-compiler

For example, in [this](https://is.gd/GUKFgz) code, it's hard to tell which part of the inputs to the macro has the wrong type. This is obviously a reduced example, but I've seen the same problem in real code.

I suspect this might be a duplicate issue, but couldn't find anything...

```rust
fn main() {
    assert_eq!(10u64, 10usize);
}
```

provides:

```
rustc 1.16.0-nightly (4ecc85beb 2016-12-28)
error[E0308]: mismatched types
 --> <anon>:2:5
  |
2 |     assert_eq!(10u64, 10usize);
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected u64, found usize
  |
  = note: this error originates in a macro outside of the current crate

error: aborting due to previous error
```
Repository: rust
Issue: LLVM error when emitting PTX code with debuginfo
Labels: A-LLVM,T-compiler,O-NVPTX,C-bug

### STR

```
$ cargo new --lib kernel && cd $_

$ edit src/lib.rs && cat $_
```

``` rust
#![feature(lang_items)]
#![feature(no_core)]
#![no_core]  // Just to avoid using Xargo

fn foo() {}

#[lang = "copy"]
trait Copy {}

#[lang = "sized"]
trait Sized {}
````

```
$ edit nvptx64-nvidia-cuda.json && cat $_
```

``` js
{
  "arch": "nvptx64",
  "cpu": "sm_20",
  "data-layout": "e-i64:64-v16:16-v32:32-n16:32:64",
  "llvm-target": "nvptx64-nvidia-cuda",
  "max-atomic-width": 0,
  "os": "cuda",
  "panic-strategy": "abort",
  "target-endian": "little",
  "target-pointer-width": "64"
}
```

```
$ cargo rustc --target nvptx64-nvidia-cuda -- --emit=asm
   Compiling kernel v0.1.0 (file:///home/japaric/tmp/kernel)
warning: function is never used: `foo`, #[warn(dead_code)] on by default
 --> src/lib.rs:5:1
  |
5 | fn foo() {}
  | ^^^^^^^^^^^

All DICompileUnits must be listed in llvm.dbg.cu
LLVM ERROR: Broken module found, compilation aborted!
error: Could not compile `kernel`.
```

### Workaround

Don't try to emit debuginfo:

``` toml
# Cargo.toml
[profile.dev]
debug = false
```
Repository: TypeScript
Issue: Erronous documentation for property decorators?
Labels: Docs

At https://www.typescriptlang.org/docs/handbook/decorators.html

..it reads under "Property Decorators"

```
If the property decorator returns a value, it will be used as the Property Descriptor for the member.

NOTE  The return value is ignored if your script target is less than ES5.
```

I'm running a simple example with target ES6

```typescript
function MyPropDesc() {
  return function (targetProto: Object, propName: string | symbol)   {
    return {
      get: function() { console.log('in getter') }
    }
  }
}

class SomeClass {
  @MyPropDesc()
  someMember;
}
```

However, this doesn't seem to work. Also, when debugging this, my property decorator is being called from Reflect.js's `DecoratePropertyWithoutDescriptor` which ignores the result from the descriptor. And...typescript requires the decorator to return `void` or `any`. Documentation mistake?
Repository: go
Issue: cmd/dist: run all tests unless explicitly disabled on a platform
Labels: help wanted,NeedsFix

Every now and again a test isn't enabled on a platform where it should be (for example: https://github.com/golang/go/commit/161cd34f788ee9c6b61565eb6f865434bc135306). A leading culprit of this is feature checks that only run a test if the GOOS/GOARCH combination is in a list:

```go
pair := t.gohostos + "-" + t.goarch
switch (pair) {
case "android-arm", "darwin-arm", ...:
    // run test
default:
    // don't run test
}
```

If a GOOS/GOARCH combination isn't correctly added to one of the many lists like this, then the related tests simply won't run. This is not always obvious.

I think it would be good to refactor test.go so that it always defaults to running a test unless explicitly told not to for a given platform (preferably with an issue referencing the missing feature). This will make it harder to accidentally forget to enable a test.
Repository: vscode
Issue: Evaluate selected expression on hover while debugging?
Labels: feature-request,debug,typescript

_This is a feature request._

Would it be possible to add the feature of evaluating a highlighted JS expression on hover while debugging? This is something that was recently added to Chrome DevTools and is very useful. It would be nice to have this same feature added to VS Code as well.

### Hovering over a single variable (works in VS Code):
![image](https://cloud.githubusercontent.com/assets/3431954/21621155/62843030-d1bd-11e6-8174-2c6a005e3c93.png)

### Hovering over a highlighted expression (doesn't work in VS Code):
![image](https://cloud.githubusercontent.com/assets/3431954/21621178/79fa08e8-d1bd-11e6-8031-092c64ab4693.png)

Thanks!
Repository: angular
Issue: formControlName could not be used with component transclusion
Labels: feature,state: Needs Design,freq2: medium,area: forms,feature: under consideration

```
[x] bug report => search github for a similar issue or PR before submitting
```

Version: 2.4.1

A component with selector parent-component has this:

```
<form [formGroup]="myFormGroup">
	<ng-content></ng-content>
</div>
```

And it is inserted in another template with:

```
<parent-component>
    <input formControlName="myControl">
</parent-component>
```

Angular says the control is used without a form.
Repository: vscode
Issue: Allow extension commands to define the behaviour when Alt modifier is pressed
Labels: feature-request,api,quick-open

When you declare a `command` for an extension, it appears in `Command Palette` and you can select/use it with `Return Key`/`Mouse Click`. But there are some _core commands_ that has _special behavior_ when you combine with `Ctrl`, like `Open on the Side`.

I would like to have the ability to declare a command and have the _normal_ and _alternative_ behaviors, just like that. 

Thanks in advance
Repository: create-react-app
Issue: RFC: Support for eslint-plugin-compat
Labels: issue: proposal

Recently I've been working on an eslint plugin called [eslint-plugin-compat](https://github.com/amilajack/eslint-plugin-compat/) that lints support for API's by using the caniuse db. [It seems there is demand from the community](https://twitter.com/mxstbr/status/816220545796730880)  for this plugin. Wonder if it has a place in create-react-app. Would a PR for it be welcome?

**Here's a demo of it in action**

![demo of plugin usage](https://raw.githubusercontent.com/amilajack/eslint-plugin-compat/master/eslint-plugin-compat-demo.gif)

Also planning to add integration with `babel-preset-env` and `browserlist`