sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: os/signal: No access to the siginfo_t struct
Labels: help wanted,FeatureRequest,compiler/runtime

The siginfo_t struct that is delivered with signals contains various useful information about the signal. In some cases, this information is necessary to implement the kernel API of various features. For example, fcntl(F_SETLEASE) requires that your process receive a SIGIO when the lock is broken, and the si_fd field in the siginfo_t struct tells you what filehandle the kernel is notifying your process about.

Please provide an interface that will allow Go code to access the information in the siginfo_t struct.
Repository: TypeScript
Issue: Report error if code precedes /// reference
Labels: Bug,Help Wanted

a.ts:

``` ts
'use strict'
/// <reference path='b.d.ts'/>

var x: Foo;
```

b.d.ts:

``` ts
interface Foo { x: string; }
declare module "b" {
        export = Foo;
}
```

```
D:\test\refs\a> tsc a.ts
a.ts(4,8): error TS2304: Cannot find name 'Foo'.
```

There's no mention in section 11.1.1 of the spec that /// references must be the first thing in a file in order to work, although I do remember us deciding that was the case at one point. If that is the rule we should update the spec appropriately. We should also add an error to the compiler or else you may spend awhile trying to figure this out since we don't provide much (read: anything) in the way of diagnostics for debugging reference resolution.
Repository: You-Dont-Know-JS
Issue: "this & object prototypes": update appendix A `class` syntax to spec
Labels: for second edition

- `super.foo()` instead of just `super()` in non-constructors.
- `toMethod(..)` has gone away entirely, so no way to rebind `[[HomeObject]]`
Repository: rust
Issue: The compiler should report publicly exported type names if possible
Labels: E-hard,C-enhancement,A-diagnostics,A-resolve,P-medium,T-compiler,D-newcomer-roadblock

If a private type is reexported at some public location, the Rust compiler will report the private location when referring to the type. It'd be more helpful if the compiler reported the public alias for it.

This was reported by Coda Hale on Twitter.

----

Update by pnkfelix: here is a standalone bit of code illustrating the problem. ([play](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=ba6fa8cd0b3b03f756ebc8cbd95597a4)):

```rust
mod a {
    mod m { pub struct PrivateName; }
    pub use m::PrivateName as PublicName;
}

fn main() {
    // a::m::PrivateName; // would error, "module `m` is private"
    a::PublicName;
    a::PublicName.clone();
}
```

As of nightly 2019-06-17, this issues the diagnostic:

```
> error[E0599]: no method named `clone` found for type `a::m::PrivateName` [...]
                                                        ^^^^^^^^^^^^^^^^^
                                                                 |
             (author of `fn main` wants to see `a::PublicName` here)
```
Repository: youtube-dl
Issue: Failed for flash video from `erlang-factory.com`
Labels: site-support-request

Complete log: 

```
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-twci', '--console-title', '--verbose', 'http://www.erlang-factory.com/conference/London2009/speakers/SimonPeytonJones']
[debug] Encodings: locale UTF-8, fs utf-8, out None, pref UTF-8
[debug] youtube-dl version 2014.11.21
[debug] Python version 2.7.6 - Darwin-14.1.0-x86_64-i386-64bit
[debug] exe versions: none
[debug] Proxy map: {}
WARNING: Falling back on generic information extractor.
ERROR: Unsupported URL: http://www.erlang-factory.com/conference/London2009/speakers/SimonPeytonJones; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  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/bin/youtube-dl/youtube_dl/extractor/generic.py", line 609, in _real_extract
    doc = parse_xml(webpage)
  File "/usr/local/bin/youtube-dl/youtube_dl/utils.py", line 1339, in parse_xml
    tree = 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 280, column 139
Traceback (most recent call last):
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 536, in extract_info
    ie_result = ie.extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 240, in extract
    return self._real_extract(url)
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/generic.py", line 996, in _real_extract
    raise ExtractorError('Unsupported URL: %s' % url)
ExtractorError: Unsupported URL: http://www.erlang-factory.com/conference/London2009/speakers/SimonPeytonJones; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
```
Repository: go
Issue: encoding/xml: Unmarshal does not properly handle NCName in XML namespaces
Labels: NeedsFix,early-in-cycle

Example:
type A struct {
  XMLName xml.Name `xml:"a:B"`
}
Struct A is marshaled to "<a:B></a:B>", as expected.
However if we run 
a := A{}
xml.Unmarshal([]byte("<a:B></a:B>"), &a)

It results in an error saying "unexpected error: expected element type <a:B> but have <B>"
Repository: TypeScript
Issue: Go to definition includes results from other entity spaces
Labels: Bug,Help Wanted,Domain: Symbol Navigation

``` ts
Symbol.for("foo");
```

Go to definition on `Symbol`.
Expected: Only the var in lib.es6.d.ts is found.
Actual: Both the var and the interface are found

This is bad because Visual Studio only goes to the definition if there exactly one definition. By saying there are two definitions, VS does not navigate accordingly.
Repository: You-Dont-Know-JS
Issue: "this & object prototypes": cover `__proto__` in object literals
Labels: for second edition

ES6 now allows:

``` js
var Foo = { .. };

var Bar = {
   __proto__: Foo,
   ..
};
```

This is obviously now much preferable in OLOO style, though of course it is ES6 only and requires some sort of transpilation to work backwards.
Repository: rust
Issue: Treatment of regions in trait matching is perhaps too simplistic
Labels: C-enhancement,A-lifetimes,A-trait-system,T-lang,T-compiler,T-types

Not sure why I didn't see this coming. Until now, the treatment of regions in trait matching has intentionally ignored lifetimes (in the sense of, it did not consider lifetime constraints when deciding what impl to apply -- once an impl is selected, the constraints that appear on it naturally are enforced). The reason for this is that lifetime inference is a second pass that uses a much more flexible constraint-graph solving algorithm, in contrast to the bulk of type inference which uses something much closer to unification. A side-effect of this is that you cannot easily get a "yes or no" answer to the question "does `'x : 'y` hold?" One must see wait until all the constraints have been gathered to know.

However, this leads to problems when you have multiple predicates in the environment that reference lifetimes. This is easy to see in the following example, but one does not need where clauses to get into this situation:

``` rust
trait Foo {
    fn foo(self);
}

fn foo<'a,'b,T>(x: &'a T, y: &'b T)
    where &'a T : Foo,
          &'b T : Foo
{
    x.foo(); 
    y.foo();
}

fn main() { }
```

this winds up failing to compile because it can't really distinguish the two predicates here, since they are identical but for the specific lifetimes involved. This doesn't arise much in practice because it's unusual to have two requirements like that, usually you either have a more universal requirement (e.g., `for<'a> &'a T : Foo`), or just one particular lifetime you are interested in. I observed this problem however when experimenting with [implied bounds](http://smallcultfollowing.com/babysteps/blog/2014/07/06/implied-bounds/), because it is common for multiple indistinguishable bounds of this kind to be generated as part of that proposal.

I'm not really sure how best to solve this at the moment.
Repository: go
Issue: x/build: detect leftover temporary files?
Labels: Builders,FeatureRequest

Could the builders detect that there isn't any leftover temporary
files in $TMPDIR after testing each repo? (We need to whitelist
a few, for example gopath-api-*)

Ideally this should be treated a build failure and reported back
to the CL that triggered this.

Each time I logged into the netbsd-386 builder, I find a lot
temporary files in /tmp. However, as I don't know which build
generated them, I have to manually check if the bug is still
there.
Repository: rust
Issue: Rustdoc links to std library types can bypass the facade
Labels: T-rustdoc,C-bug,A-cross-crate-reexports

As an example, generate documentation for this:

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

pub trait Trait { }

impl<T> Trait for Vec<T> { }
```

On the docs for the `Trait` trait, there will be an Implementors section like this:

<ul class="item-list" id="implementors-list">
    <li><a class="stability Unmarked" title="No stability level"></a><code>impl&lt;T&gt; <a class="trait" href="../foo/trait.Trait.html" title="foo::Trait">Trait</a> for <a class="struct" href="http://doc.rust-lang.org/nightly/collections/vec/struct.Vec.html" title="collections::vec::Vec">Vec</a>&lt;T&gt;</code></li>
</ul>


Note that the `Vec` link goes to docs for the _`collections`_ crate and not to docs for `std`. Since the 1.0 release will not host documentation for crates behind the facade, this will lead to broken documentation links for third-party crates.
Repository: nvm
Issue: default install method didn't patch my bashrc/bash_profile files
Labels: installing node,needs followup,installing nvm: profile detection

`curl https://raw.githubusercontent.com/creationix/nvm/v0.23.3/install.sh | bash`

```
$ echo $HOME
/home/username

$ uname -a
Linux ashes 3.2.0-4-amd64 #1 SMP Debian 3.2.63-2+deb7u2 x86_64 GNU/Linux

$ bash --version
GNU bash, version 4.2.37(1)-release (x86_64-pc-linux-gnu)

$ echo $PROFILE
(empty) 
```
Repository: rust
Issue: Rustdoc should indicate variance on lifetime/type parameters
Labels: T-rustdoc,C-feature-request,A-variance

This has come up a few times in IRC and I think it's a nice idea. It's already important for lifetime parameters, where variance is important today, and could be useful for type parameters as well if rust-lang/rfcs#738 is accepted.


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"danielhenrymantilla"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: TypeScript
Issue: Support column limit in formatter
Labels: Suggestion,Help Wanted

Currently, running the formatter
(eg via the compiler API: https://github.com/Microsoft/TypeScript/wiki/Using-the-Compiler-API#pretty-printer-using-the-ls-formatter)
produces code which is arbitrarily wide, for statements which are nested, complex, etc.

Our style guide requires a maximum columns, which means the formatter should take a configuration for how wide this is.
Line breaks should probably be added at the highest point in the AST on the long line.
Repository: TypeScript
Issue: Formatter: allow continuation indent different from nested indent
Labels: Suggestion,Help Wanted

The Google style guide
http://google-styleguide.googlecode.com/svn/trunk/javascriptguide.xml#Code_formatting
requires indenting by two spaces for nested code, but by 4 spaces when continuing a statement or declaration on the next line.
This configuration doesn't seem to be possible.
Repository: go
Issue: runtime: TestGdbLoadRuntimeSupport fails on non intel platforms
Labels: NeedsInvestigation

`runtime.TestGdbLoadRuntimeSupport` does not pass on linux/arm or linux/ppc64le. In both cases the error is the same

```
--- FAIL: TestGdbLoadRuntimeSupport (1.98s)
    runtime-gdb_test.go:59: warning: Missing auto-load scripts referenced in section .debug_gdb_scripts
        of file /tmp/go-build302202449/a.exe
        Use `info auto-load python-scripts [REGEXP]' to list them.
FAIL
FAIL    runtime 64.538s
```
Repository: nvm
Issue: Use package.json engines version?
Labels: feature requests

Run `nvm use` will read local package.json's engines.node and change version accordingly.
Or anyway that auto switch the version.
Repository: go
Issue: x/tools/imports: fill in missing type information in composite literals
Labels: NeedsInvestigation

Idea from campoy + discussions with crawshaw.

The spec now permits some types to be elided from composite literals: "Within a composite literal of array, slice, or map type T, elements that are themselves composite literals may elide the respective literal type if it is identical to the element type of T. Similarly, elements that are addresses of composite literals may elide the &T when the element type is *T."

Struct literals must still specify the types for each element, since without them the literals are difficult to understand.  But these types are fully determined by the outermost type of the literal expression and the field names.  So it should be possible to fill them in automatically.  Since goimports is already processing the AST and adding missing imports, let's see whether it can also fill in these missing types.

For example:

```
goimports <<EOF
func main() {
  fmt.Println(image.Rectangle{Min: {X: 2}})
}
EOF
should output:
package main

import (
  "fmt"
  "image"
)

func main() {
  fmt.Println(image.Rectangle{Min: image.Point{X: 2}})
}
```
Repository: youtube-dl
Issue: --sleep-interval not working without video download
Labels: bug

For example, downloading just the subs from a playlist.

This is the type of situation where sleeping is actually useful because downloading a video takes time anyway.
Repository: kubernetes
Issue: Scheduler input should be taken when reducing replicas
Labels: priority/backlog,sig/scheduling,area/controller-manager,kind/feature,sig/apps,lifecycle/frozen

When the replica count is increased, the new pod(s) are assigned to hosts by the scheduler based on policies defined by the selected predicates/priorities. However, during scale-down (reducing the replica count), the scheduler does not come into the picture potentially resulting in a violation of the scheduling policies. It is irrelevant whether the scale-down is automatic or manual.

Consider the case that there are 5 pods being spread across 3 machines, with 2 pods on each of the two machines and 1 pod on the third machine. If the replica count is reduced to 4, we shouldn't remove the single pod from the third machine (assuming the scheduler policy is to achieve greatest possible spread). To address this, we need to involve the scheduler in the workflow to figure out which pod(s) to get rid of. 

Also, see https://github.com/GoogleCloudPlatform/kubernetes/issues/3948 for some other concerns related to determining which pods are removed when the replica count is reduced.

I do not have a proposed solution for this would like to invite some discussion and feedback on this issue.
Repository: rust
Issue: assoc types: type inference works with UFCS but not with method calls
Labels: A-type-system,A-associated-items,T-compiler,A-inference,C-bug,T-types

### STR

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

trait Tuple {
    type Array: Toa<Item=Self>;
}

trait Toa {
    type Item;

    fn push(&mut self, Self::Item);
    fn with_capacity(usize) -> Self;
}

#[cfg(not(works))]
fn f<T: Tuple>(t: T) -> T::Array {
    let mut toa = Toa::with_capacity(1);
    toa.push(t);  //~ error: the type of this value must be known in this context
    toa
}

#[cfg(works)]
fn g<T: Tuple>(t: T) -> T::Array {
    let mut toa = Toa::with_capacity(1);
    Toa::push(&mut toa, t);
    toa
}
```
### Version

```
rustc 1.0.0-nightly (134e00be7 2015-02-09 19:01:37 +0000)
```

cc @nikomatsakis 

(Deja Vu, I feel like I've reported/seen a similar problem before, but it didn't involve associated types)
Repository: rust
Issue: Output of independent artefacts might differ depending on unrelated options
Labels: I-needs-decision,T-compiler,C-bug

Existence or lack of `--crate-type=bin` may influence output of other `crate-type` outputs. In general `libfoo.a` output by `--crate-type=bin,staticlib` and `--crate-type=staticlib` might be completely different.

For example using [this `foo.rs`](https://gist.github.com/nagisa/61edd3b202c6baf5404f#file-foo-rs), [this](https://gist.githubusercontent.com/nagisa/61edd3b202c6baf5404f/raw/1182045434b606ee2fa3362d2c89828c91d4e9de/libfoo-bin.a) is the list of a few first symbols when built with `--crate-type=bin,staticlib` and [this](https://gist.githubusercontent.com/nagisa/61edd3b202c6baf5404f/raw/e3ebb8e32a7c1e8ad8c7e88c95c1fd0cbb656569/libfoo.a), when `bin` crate-type is absent.

This is a quirk in rust’s entry point semantics and how current `middle/entry.rs` is implemented.
Repository: rust
Issue: Deref coercion not working for `Box<Trait>`
Labels: A-trait-system,T-compiler,C-bug

The following fails to compile:

``` rust
trait Trait {}

fn takes_ref(t: &Trait) {}
fn takes_box(t: Box<Trait>) {
    takes_ref(&t)
}
fn main() { }
```

with

```
<anon>:5:15: 5:17 error: the trait `Trait` is not implemented for the type `Box<Trait>` [E0277]
<anon>:5     takes_ref(&t)
                       ^~
```

despite the `Deref` implementation [here](https://github.com/rust-lang/rust/blob/master/src/liballoc/boxed.rs#L284-L288).

I believe this should work based on the [RFC](https://github.com/rust-lang/rfcs/pull/241).
Repository: youtube-dl
Issue: [rtp] Add support for playlists
Labels: request

It seems not be possible to download from rtp.pt, the videos on one page, as we can do in a youtube playlist.

I tried and get this:

D:\Downloads>youtube-dl -f 22/17/18 --verbose -o ./%(playlist_title)s/%(playlist_index)s-%(title)s.%(ext)s http://www.rtp.pt/play/p831/a-quimica-das-coisas
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['-f', '22/17/18', '--verbose', '-o', './%(playlist_title)s/%(playlist_index)s-%(title)s.%(ext)s', 'http://www.rtp.pt/play/p831/a-quimica-das-coisas']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2015.02.11
[debug] Python version 2.7.8 - Windows-8-6.2.9200
[debug] exe versions: rtmpdump 2.3
[debug] Proxy map: {}
[RTP] a-quimica-das-coisas: Downloading webpage
ERROR: requested format not available
Traceback (most recent call last):
  File "youtube_dl\YoutubeDL.pyo", line 644, in extract_info
  File "youtube_dl\YoutubeDL.pyo", line 690, in process_ie_result
  File "youtube_dl\YoutubeDL.pyo", line 1137, in process_video_result
ExtractorError: requested format not available
Repository: neovim
Issue: undo: collapse identical contiguous edits
Labels: enhancement

When a change is undone, then a new change is made, if the new change is identical to the previously undone change (the next node in the current tree branch), just set the state of the undo history back to that next node instead of creating a new tree branch.
Repository: go
Issue: x/build: trybots should rebase when testing
Labels: Builders,Friction

Currently with the trybot code, if Go's master is A and we have pending CLs B and C on A, currently we test B-on-A and C-on-A, but then when B is merged, we're still testing C on A, instead of C-on-B.

We should do:

https://gerrit-review.googlesource.com/Documentation/rest-api-changes.html#rebase-change

... which will add a patch set to the change, rebased. It could get spammy, though.  Shawn says "don't complain when you have patch set 85 on a trivial one line change".  So maybe we want to be careful when we do it. Maybe only for auto-submit.
Repository: youtube-dl
Issue: append 3 on the script name
Labels: request

I don't know but i'm the only one here which wants to user youtube-dl on a machine with 2 python versions: 2 and 3?
So as pip i think it's a good idea to generate a script with a "-3" at the end to indicate we are accessing the bin folder of python 3.
I really don't know if it's trivial or easy, but if not just disregard the request. Thanks for the great app/tool
Repository: go
Issue: proposal: spec: direct reference to embedded fields in struct literals
Labels: LanguageChange,Proposal,LanguageChangeReview

Consider

```
type E struct {
    A int
}

type T struct {
    E
}
```

This works:

```
T{E: E{A: 1}}
```

This does not:

```
T{A: 1}
```

Makes some struct literals more verbose than they need be, and makes them asymmetrical to their usage (where you can access the embedded struct's fields directly).

Can we allow it?

(cc @bradfitz)
Repository: go
Issue: runtime: dead Gs cause span fragmentation
Labels: compiler/runtime

Once we allocate a G, it is allocated forever.  We have no mechanism to free them.
We should free dead Gs if they sit in the global free queue for long enough.  Or maybe free all of them at each GC?

I noticed this while debugging #8832.  The stacks for dead Gs **are** freed at GC time.  This leads to a fragmented heap because spans for G storage and stack storage alternate in the heap.  When only the stacks are freed, the resulting free spans won't coalesce because the spans for storing the Gs aren't freed.
Repository: rust
Issue: Public items re-exported publicly in the same crate could have inlined docs
Labels: T-rustdoc,C-feature-request

As an example of what I mean, see this page: http://doc.rust-lang.org/syntax/parse/lexer/index.html

There is a re-exports section:

``` rust
pub use ext::tt::transcribe::{TtReader, new_tt_reader, new_tt_reader_with_doc_flag};
```

All of those items are public and reachable, so they're documented in `ext::tt::transcribe`. But `lexer::new_tt_reader`, for example, does not appear in the search index and (less seriously) it's a little annoying to have to jump through another set of links to another page to read the docs for that function.

When a private item is re-exported publicly in the same crate, or a public item from another crate is re-exported, the docs are inlined and an entry is created in the search index. I think it would be reasonable to do the same for public intra-crate re-exports.