sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: upgrade improvement
Labels: request

instead of just saying:

> youtube-dl.exe -U
> Updating to version 2014.06.26 ...

the output could include the version which it is upgrading **from** 
"Updating from version 2014.06.01 to latest version 2014.06.26 ..."
Repository: youtube-dl
Issue: Is user-login possible with escapistmagazine.com?
Labels: account-needed

The escapist has just put its HQ videos behind a membership wall, and so I signed up and paid the $20.  Sadly though, the normal login/password tags for youtube-dl, don't interact properly to log me in.  Is it possible to make a change to allow for this?  Happy to help with testing on it if you want to work on it.

BTW, the setup basically seems to be looking for a login cookie and when it sees it, automatically redirects users to the HQ versions of each page.  BUT without it, will only send them to the SD page.
Repository: react
Issue: Add api for focus management
Labels: Type: Feature Request,Component: DOM,Resolution: Backlog

There are currently a couple of problems with focus management in React.
## current problems
- `this.getDOMElement().focus()`

does not guarantee the node is on a document/visible. visibility can be hard to detect due to other components firing render().
- `this.refs.x.getDOMElement().focus()`

does not guarantee that x has finished any pending renders. if `x` renders, focus is lost.
- `componentDidUpdate`

this fires on the child nodes before parents so in the case of:

```
<ul style="display:none">
  <li><button>can't focus</button></li>
</ul>
```

if we want to show the `<ul/>` and focus the button.

the component of the `<button/>` focusing during componentDidUpdate has no affect because the `<ul/>` is still hidden.
## discussion

if looks like some of the PRs to react are using raf or timeouts to achieve fixes to the problems listed. This can cause race conditions, and can be fixed with a lifeCycle addition, or just a hidden lifeCycle purely for focus management.

The issue comes down to not having a lifecycle able to fire a function after _all_ rendering is done, not just an individual component.

I would suggest we add a simple API of component.blur()/component.focus() that queues the requests and fires them after all rendering is done. The fix is fairly simple, but I wonder how people feel about this.
Repository: nvm
Issue: nvm uninstall fails due to permissions/globally installed modules via sudo
Labels: uninstalling,pull request wanted

Steps to reproduce:
1. `nvm ls` lists: `.nvm`, `v0.10.26`, `->  v0.10.29`
2. `nvm uninstall v0.10.26`

What happens: `v0.10.26` is not removed. `nvm ls`  still lists: `.nvm`, `v0.10.26`, `->  v0.10.29`.

What should happen: `v0.10.26` should be removed.

Platform:

```
node v0.10.29
grunt-cli v0.1.13
grunt v0.4.5 
```
Repository: youtube-dl
Issue: Support for German national parliament TV (bundestag.de)
Labels: site-support-request

Video-Page: http://dbtg.tv/fvid/3594346

URL for video is provided through HTML element `<input type="hidden" name="data-downloadUrl" value="…" />`

The trailing param `?fdl=1` should be removed from the URL, otherwise a mimetype to enforce a file download in browsers will be set.
Repository: nvm
Issue: Update install to install from release tarball instead of a git repo
Labels: installing node,feature requests

Now that we switched to using releases, instead of a simple clone/pull of the master branch, we should think of switching to simply downloading a release tarbal

``` bash
curl https://github.com/creationix/nvm/archive/v0.10.0.tar.gz | \
  tar -xzC ~/.nvm --strip-components=1
```
Repository: TypeScript
Issue: Suggestion: Generate doc comments in emitted JS
Labels: Suggestion,Needs Proposal,VS Code Tracked

Support some level of automatically generating doc comments for non-TypeScript JavaScript consumers.

Need more details on what exactly people would like to see generated.
Repository: rust
Issue: Tracking issue for stmt_expr_attributes: Add attributes to expressions, etc.
Labels: A-grammar,T-lang,B-unstable,B-RFC-implemented,C-tracking-issue,S-tracking-design-concerns,S-tracking-needs-summary,F-stmt_expr_attributes

This is the tracking issue for https://github.com/rust-lang/rfcs/pull/16
The feature gate for the issue is `#![feature(stmt_expr_attributes)]`

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

### Steps

- [x] Implement the RFC
  - https://github.com/rust-lang/rust/pull/29850
- [ ] https://github.com/rust-lang/rust/issues/127436
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Formatting for new syntax has been added to the [Style Guide] ([nightly-style-procedure])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/main/nightly-style-procedure.md 
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions

-

### Implementation history

- https://github.com/rust-lang/rust/pull/29850
- https://github.com/rust-lang/rust/pull/134661
Repository: rust
Issue: rustdoc: do something about reexported items
Labels: T-rustdoc,C-feature-request

**Update:** This issue was first filed with the title "rustdoc shouldn’t document reexports separately", but that might not be the desired solution.

---

For example, the `StrSlice` trait is currently documented in three different places:

http://doc.rust-lang.org/std/str/trait.StrSlice.html
http://doc.rust-lang.org/collections/str/trait.StrSlice.html
http://doc.rust-lang.org/core/str/trait.StrSlice.html

It really is the same trait, but in the documentation they appear as distinct.

I think that, when module `A` contains a `pub use B::C;` statement:
- rustdoc should not create a new documentation page for `A::C`
- Instead, the documentation for `A` should link to the original documentation for `B::C`
- In addition, the documentation for `B::C` should list all the known name it is re-exported as (in this case `A::C`).

It gets more complicated when `A` and `B` are not in the same source repository, but IMO still worth pursuing. Sphinx does [support cross-references to other repos](http://sphinx-doc.org/ext/intersphinx.html).
Repository: three.js
Issue: Remove target from DirectionalLight and SpotLight.
Labels: Enhancement

As far as I'm aware, we should be able to get the same results by just adding a `distance` property to those light types. By removing the target we'll then fix the problems that those lights have in the editor.

@gero3 any interest on tackling this one?
Repository: youtube-dl
Issue: Downloading from aber.ac.uk fails
Labels: site-support-request

$ youtube-dl --verbose http://www.aber.ac.uk/en/graduation/video/2014/2/
[debug] System config: ['--prefer-free-formats']
[debug] User config: []
[debug] Command-line args: ['--verbose', 'http://www.aber.ac.uk/en/graduation/video/2014/2/']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2014.07.15
[debug] Python version 2.7.5 - Linux-3.15.5-200.fc20.x86_64-x86_64-with-fedora-20-Heisenbug
[debug] Proxy map: {}
[generic] 2: Requesting header
WARNING: Falling back on generic information extractor.
[generic] 2: Downloading webpage
[generic] 2: Extracting information
ERROR: Unsupported URL: http://www.aber.ac.uk/en/graduation/video/2014/2/; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
  File "/usr/bin/youtube-dl/youtube_dl/extractor/generic.py", line 456, in _real_extract
    doc = parse_xml(webpage)
  File "/usr/bin/youtube-dl/youtube_dl/utils.py", line 1409, in parse_xml
    return xml.etree.ElementTree.XML(s.encode('utf-8'), **kwargs)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1300, in XML
    parser.feed(text)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1642, in feed
    self._raiseerror(v)
  File "/usr/lib64/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
    raise err
ParseError: mismatched tag: line 17, column 830
Traceback (most recent call last):
  File "/usr/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 516, in extract_info
    ie_result = ie.extract(url)
  File "/usr/bin/youtube-dl/youtube_dl/extractor/common.py", line 168, in extract
    return self._real_extract(url)
  File "/usr/bin/youtube-dl/youtube_dl/extractor/generic.py", line 751, in _real_extract
    raise ExtractorError('Unsupported URL: %s' % url)
ExtractorError: Unsupported URL: http://www.aber.ac.uk/en/graduation/video/2014/2/; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Repository: rust
Issue: rustdoc: reexported type aliases are not preserved in function signatures
Labels: T-rustdoc,C-bug

The recently added `iterate` function uses the `Iterate` type alias as its result type. It is correctly displayed in http://static.rust-lang.org/doc/master/core/iter/fn.iterate.html but not in  http://static.rust-lang.org/doc/master/std/iter/fn.iterate.html.
Repository: three.js
Issue: Picking in a PointCloud with variable size points
Labels: Enhancement

Thanks so much for adding PointCloud support for RayCasting in r.61!  Unless I am missing something, the current implementation assumes that the points are all of the same size.  Is it possible to make the raycaster aware of the gl_PointSize of each point, rather than uniformly using params.PointCloud.threshold?

Thanks,
Mike Cantor
Repository: TypeScript
Issue: Support some non-structural (nominal) type matching
Labels: Suggestion,In Discussion

Proposal: support non-structural typing (e.g. new user-defined base-types, or some form of basic nominal typing). This allows programmer to have more refined types supporting frequently used idioms such as: 

1) Indexes that come from different tables. Because all indexes are strings (or numbers), it's easy to use the an index variable (intended for one table) with another index variable intended for a different table. Because indexes are the same type, no error is given. If we have abstract index classes this would be fixed.

2) Certain classes of functions (e.g. callbacks) can be important to be distinguished even though they have the same type. e.g. "() => void" often captures a side-effect producing function. Sometimes you want to control which ones are put into an event handler. Currently there's no way to type-check them. 

3) Consider having 2 different interfaces that have different optional parameters but the same required one. In typescript you will not get a compiler error when you provide one but need the other. Sometimes this is ok, but very often this is very not ok and you would love to have a compiler error rather than be confused at run-time.

Proposal (with all type-Error-lines removed!): 

```
// Define FooTable and FooIndex
nominal FooIndex = string;  // Proposed new kind of nominal declaration.
interface FooTable {
  [i: FooIndex]: { foo: number };
}
let s1: FooIndex;
let t1: FooTable;

// Define BarTable and BarIndex
nominal BarIndex = string; // Proposed new kind of nominal declaration.
interface BarTable {
  [i: BarIndex]: { bar: string };
}
let s2: BarIndex;
let t2: BarTable;

// For assignment from base-types and basic structures: no type-overloading is needed.
s1 = 'foo1';
t1 = {};
t1[s1] = { foo: 1 };

s2 = 'bar1';
t2 = { 'bar1': { bar: 'barbar' }};

console.log(s2 = s1); // Proposed to be type error.
console.log(s2 == s1); // Proposed to be type error.
console.log(s2 === s1); // Proposed to be type error.

t1[s2].foo = 100; // Gives a runtime error. Proposed to be type error.
t1[s1].foo = 100;

function BadFooTest(t: FooTable) {
  if (s2 in t) {  // Proposed to be type error.
    console.log('cool');
    console.log(t[s2].foo); // Proposed to be type error.
  }
}

function GoodBarTest(t: BarTable) {
  if (s2 in t) {
    console.log('cool');
    console.log(t[s2].bar);
  }
}

BadFooTest(t1); // Gives runtime error;
BadFooTest(t2); // No runtime error, Proposed to be type error.
GoodBarTest(t1); // Gives runtime error; Proposed to be type error.
GoodBarTest(t2);
```
Repository: TypeScript
Issue: Issue a more useful error when attempting to construct non-newable type
Labels: Bug,Help Wanted,Domain: Error Messages

Inspired from http://stackoverflow.com/questions/24923772/raphael-with-typescript-call-signatures-used-in-a-new-expression-must-have-a

``` TypeScript
interface NotNewable {
    (n: number): string;
}

var n: NotNewable;
var t = new n(10);
```

New compiler says

> Only a void function can be called with the 'new' keyword

Old compiler says

> Call signatures used in a 'new' expression must have a 'void' return type.

This error is written as if it's the .d.ts author's fault, not the calling code's fault. A more useful error would be something like "Specified type does not have a signature that can be called with 'new'"
Repository: neovim
Issue: scroll without cursor move (or: remember mark when scrollbar is used?)
Labels: enhancement

A common complaint is that cursor always must be onscreen. The use-case for this could be satisfied by leaving a ~~jumplist entry~~ special mark at the cursor position before it is scrolled out of view using the scrollbars. 

This feature is in Bram's todo.txt:

```
-   STICKY CURSOR: Add a way of scrolling that leaves the cursor where it is.
    Especially when using the scrollbar.  Typing a cursor-movement command
    scrolls back to where the cursor is.
```
Repository: TypeScript
Issue: Don't widen return types of function expressions
Labels: Suggestion,Experimentation Needed,Fix Available

This change courtesy @JsonFreeman who is trying it out

(context elided: widening of function expression return types)

The problem with this widening is observable in type argument inference and no implicit any. For type argument inference, we are prone to infer an any, where we should not:

``` ts
function f<T>(x: T, y: T): T { }
f(1, null); // returns number
f(() => 1, () => null); // returns () => any, but should return () => number
```

So after we get to parity, I propose we do the following. We do not widen function expressions. A function is simply given a function type. However, a function declaration (and a named function expression) introduces a name whose type is the widened form of the type of the function. Very simple to explain and simple to implement.

I’ve been told that this would be a breaking change, because types that used to be any are now more specific types. But here are some reasons why it would be okay:
- In the places where you actually need the type to be any (because there are no other inference candidates), you would still get any as a result
- In places where there was a better (more specific) type to infer, you’d get the better type. 
- With the noImplicitAny flag, you’d get fewer errors because there are actually fewer implicit anys
### Questions:

> Is a principle of design changes going forward to not switch from 'any' to a more precise type because it can be a breaking change?

Going with 'not a breaking change' here because this is unlikely to break working code, but we need to verify this.

> Would this manufacture two types?  

In essence, we already have two types: The original and the widened type. So by that measure this is not really a change

> Has someone tried it?

Jason willing to try it out and report back
Repository: TypeScript
Issue: External interfaces included in IDE symbol space
Labels: Suggestion,Help Wanted,API

#### Overview

Interfaces defined in `.d.ts` files (even if they are not part of the Visual Studio project) are nonetheless included in the IDE symbol space; i.e. they appear in the Navigate To search results.
#### Repro

Add the NuGet package `underscore.TypeScript.DefinitelyTyped` to a project. Ensure that `underscore.d.ts` is not included in the project; however, do put a reference to it in a TypeScript file in the project, e.g.

```
/// <reference path="../Scripts/typings/underscore/underscore.d.ts"/>
```

In Visual Studio, press <kbd>Ctrl</kbd> + <kbd>,</kbd> and type `reduce`. Notice you get lots of listings for methods defined in the underscore interface.
#### Commentary

The repro steps are analogous to adding a reference to `System.Web.Mvc`, hitting <kbd>Ctrl</kbd> + <kbd>,</kbd>, typing `file`, and seeing the `File` methods for `System.Web.Mvc.Controller`, plus who knows what else. Of course, for assembly references this doesn't happen; it would be noise, polluting the IDE symbol space with stuff you rarely want to try to navigate to. Libraries have lots of symbols, often more than our own apps. Those symbols get in the way of navigating quickly within our own app. That's why there's a switch to turn off external items. The same situation applies to JavaScript libraries with TypeScript annotations - not at the same scale as the .NET Framework, but still at enough scale to be a problem.

The bug is that for TypeScript, interfaces and their members in `.d.ts` files always show up. Ideally, they shouldn't show up regardless of whether the `.d.ts` file is referenced with an XML directive or by including the file in the project.

The main use case where it would be helpful to include the identifiers in the IDE symbol space is when developers are actually writing `.d.ts` files.  To serve that need, it would be reasonable to include the symbols if the "Search within external items" option is enabled.
Repository: neovim
Issue: plugin-specific modes (custom / user-defined modes)
Labels: enhancement,input,gsoc,mappings

From https://github.com/neovim/neovim/issues/51#issuecomment-50134195:

> Each new mode has the following properties:
> 1. Identifier of some kind. Should be used to create mappings.
> 2. A set of built-in commands.
> 3. A function that is responsible for processing all input that was not caught by some command from 2. E.g. in insert mode it is “write to buffer”, in normal it is “bell”, etc. Defaults to bell.
> 
> One word about 2.: there is `<C-\><C-n>` command in all modes that allows escaping to normal mode from any other mode. I think that this command should be forced in 2. (i.e. not allowed to be redefined), but still remappable (as it is now).
> 
> Reasoning: there is a number of plugins like Command-T that create their own mode, but they use more or less hacky solutions. And yet they run completely in Vim: no external jobs. They also do not require escaping to normal or command mode.

To make life for Conque_Term easier there also may be fourth point: allow replacing existing modes with newly defined modes buffer-wise, API should use a function that accepts a number of arguments (e.g. for insert mode `start(count=v:count, mode_type : ('insert', 'replace', 'vreplace')='insert')`).

---

Also ref #421: it is not required for implementing this feature, but it will make “supporting plugin-specific modes” be “create a set of bindings for library from #421”.
Repository: TypeScript
Issue: cloneNode should return sub type, not Node
Labels: Bug,Help Wanted,Domain: lib.d.ts

When I do `someElement.cloneNode()`, I want the returned element to be the same type as `someElement`, but right now it's returning type `Node`.
Repository: youtube-dl
Issue: Request for URL support:  http://swrmediathek.de
Labels: site-support-request

[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['--verbose', 'http://swrmediathek.de/tvshow.htm?show=b3700e63-9bdc-11df-b44d-00199916cf68']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2014.07.25.1
[debug] Python version 2.7.5 - Darwin-13.3.0-x86_64-i386-64bit
[debug] Proxy map: {}
[generic] tvshow: Requesting header
WARNING: Falling back on generic information extractor.
[generic] tvshow: Downloading webpage
[generic] tvshow: Extracting information
ERROR: Unsupported URL: http://swrmediathek.de/tvshow.htm?show=b3700e63-9bdc-11df-b44d-00199916cf68; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 456, in _real_extract
    doc = parse_xml(webpage)
  File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 1418, in parse_xml
    return xml.etree.ElementTree.XML(s.encode('utf-8'), **kwargs)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1300, in XML
    parser.feed(text)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
    self._raiseerror(v)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
    raise err
ParseError: mismatched tag: line 58, column 6
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 516, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 169, in extract
    return self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 751, in _real_extract
    raise ExtractorError('Unsupported URL: %s' % url)
ExtractorError: Unsupported URL: http://swrmediathek.de/tvshow.htm?show=b3700e63-9bdc-11df-b44d-00199916cf68; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Repository: TypeScript
Issue: Request to change currentTarget in Event interface for lib.d.ts
Labels: Suggestion,Help Wanted,Domain: lib.d.ts

When using the Event interface from lib.d.ts, and attaching a listener, the callback will get an object of type Event. However, the Event's currentTarget property is of type EventTarget (whereas it's should be of type Element/HTMLElement).