sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: encoding/asn1: cannot marshal into slice of strings and pass stringtype parameter tags to members
Labels: NeedsDecision

### What version of Go are you using (`go version`)?
go version go1.7.5 linux/amd64

### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GORACE=""
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build372878858=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1

### Issue
I need to be able to marshal into a slice of strings and to be able to specify the string types for the elements in this slice (is5, generalstring, etc)
https://play.golang.org/p/l5id74lMoI
Issue seems to be two fold:
1) Validation does not allow it and you get the error: explicit string type given to non-string member
2) Strings would all be marshaled as the default type - PrintableString

### Suggestion
When struct tags for string types are defined against a slice this should be accepted if the slice is of strings
The struct tag for the string type should be passed down to the marshaling of the members of the slice
Repository: youtube-dl
Issue: Add support for Adobe Pass Auth TV provider Frontier Communications
Labels: tv-provider-account-needed

### Make sure you are using the *latest* version: run `youtube-dl --version` and ensure your version is *2017.01.28*. 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 **2017.01.28**

### 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)
- [ ] Site support request (request for adding support for a new site)
- [X] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other

---

### Description of your *issue*, suggested solution and other information

Would like to request support for Frontier Communications as an Adobe Pass MSO option.  I believe the MSO ID is FRONTIER.
Repository: rust
Issue: Non-upper case constant warning misapplied in patterns
Labels: A-lints,I-needs-decision,T-compiler,C-bug

A constant with `#[allow(non_upper_case_globals)]` applied still generates a warning when used in a pattern, unless the `match` also has the allow attribute. For example:

```rust
#[allow(non_upper_case_globals)]
mod keywords {
    pub const If: u32 = 0;
    pub const While: u32 = 1;
}

fn main() {
    use keywords::*;

    // the warning goes away with this attribute:
    // #[allow(non_upper_case_globals)]
    match 0 {
        keywords::If => println!("if"),
        While => println!("while"),
        _ => println!("<unknown>"),
    }
}
```

[Playground](https://is.gd/jzNZQB)
Repository: pytorch
Issue: Add Peephole connections for LSTMs?
Labels: feature,triaged,Stale

From this [paper](http://www.jmlr.org/papers/volume3/gers02a/gers02a.pdf). Peephole connections seem to help in learning precise timings of events.
Repository: youtube-dl
Issue: Lynda.com: Add support for extraction of "release-date" & "update-date" html elements
Labels: request

[x] I've **verified** and **I assure** that I'm running youtube-dl **2017.01.28**
[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] Feature request (request for a new functionality)

Hi there,

at the moment, youtube-dl is not supporting the output template "release_date" for Lynda.com courses.

It would be very nice if someone could add a support for extraction of a Lynda.com's course release/update date. The html element ids are "update-date" and "release-date".

The output template should then add the newest of those two dates to the folder/path name in descending order.
E.g. for https://www.lynda.com/Java-tutorials/Up-Running-Java-Applications/435790-2.html with above ids (Updated: 8/1/2016, Released: 2/22/2016)
and the usage of the following commands: youtube-dl --output "E:\Downloads\\%%(playlist)s (%%(release_date)s)\\
=> E:\Downloads\Up and Running with Java Applications (2016-8-1)\

Best regards
Repository: go
Issue: x/net/webdav: PROPFIND fails on OpenBSD if the directory has a unix domain socket in it
Labels: OS-OpenBSD

Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?
1.7.4

### What operating system and processor architecture are you using (`go env`)?
openbsd/amd64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="openbsd"
GOOS="openbsd"
GOPATH="/home/stuart/go"
GORACE=""
GOROOT="/home/stuart/.goroot"
GOTOOLDIR="/home/stuart/.goroot/pkg/tool/openbsd_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -fmessage-length=0"
CXX="g++"
CGO_ENABLED="0"

### What did you do?
If possible, provide a recipe for reproducing the error.
1. Make a unix domain socket in a temporary directory 
2. Serve the directory with x/net/webdav
3. Try to list the directory with the socket

Code used to serve directory.
http://play.golang.org/p/ClPtJ4beK4

For the socket, `socat unix-listen:testpipe - & pkill -9 socat` works.

### What did you expect to see?
A listing of the directory contents.

### What did you see instead?
```
dav:/> ls
Listing collection `/': failed:
XML parse error at line 1: junk after document element
```

The problem seems to be in the function `props` in `/x/net/webdav/prop.go`.  It opens every file to get its dead properties.  Unfortunately, on OpenBSD, opening a unix socket (as opposed to connecting to it), returns EOPNOTSUPP.
Repository: pytorch
Issue: Feature Request: NegativeSampling and HierarchicalSoftmax loss functions
Labels: feature,module: nn,module: loss,triaged,Stale,module: primTorch

It's a bit difficult to write a SkipGram word2vec model without these functions.

Not entirely sure, but the Chainer implementations for [NegativeSampling](https://github.com/pfnet/chainer/blob/master/chainer/links/loss/negative_sampling.py) and [HierarchicalSoftmax](https://github.com/pfnet/chainer/blob/master/chainer/links/loss/hierarchical_softmax.py) could be easily ported to pytorch.

I think this could be a useful addition to pytorch. Also, if you need some help in this, I might be able to find some time and submit a PR.

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are @ezyang @ngimel
Repository: youtube-dl
Issue: Please add support for Playstation Vue logins
Labels: tv-provider-account-needed

## 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 *2017.01.29*. 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 **2017.01.29**

### 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)
- [ ] Site support request (request for adding support for a new site)
- [X] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other

---

### The following sections concretize particular purposed issues, you can erase any section (the contents between triple ---) not applicable to your *issue*

---

### Description of your *issue*, suggested solution and other information

If you go to https://www.playstation.com/en-us/network/vue/ you can sign up for a free trial of Playstation Vue if you have a PlayStation Network account, and you just have to remember to cancel it within a week to not get billed for it if you don't want it.  I have read in several places that a Playstation Vue login can be used in place of a cable or satellite provider login on several of the streaming sites, therefore if you could add Playstation Vue to the list of supported MSO's then perhaps youtube-dl would be able to download files from those services without the need for a separate cable or satellite subscription.
Repository: rust
Issue: resolve: improve diagnostics for a single `super` at the crate root
Labels: C-enhancement,A-diagnostics,A-resolve,T-compiler

For example,
```rust
fn main() {
    let super = 0;
    //  ^^^^^ Ideally, the error here would be something like:
    // - "the root module has not parent"
    // - "`super` is not allowed in the crate root"
}
```
Repository: angular
Issue: Ngclass value not updating if form input field has errors. It seems to be one tick behind.
Labels: type: bug/fix,freq3: high,area: forms,state: confirmed,core: change detection,P3

<!--
IF YOU DON'T FILL OUT THE FOLLOWING INFORMATION WE MIGHT CLOSE YOUR ISSUE WITHOUT INVESTIGATING
-->

**I'm submitting a ...**  (check one with "x")
```
[x ] bug report => search github for a similar issue or PR before submitting
[ ] 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**
<!-- Describe how the bug manifests. -->

The ngClass on a surrounding div is not updating correctly if I have an input field with a dynamic min length. The input field itself sets ng-valid or ng-invalid correctly.

**Expected behavior**
<!-- Describe what the behavior would be without the bug. -->
Both the input field and the surrounding div / ngClass should have the same valid / invalid status.

**Minimal reproduction of the problem with instructions**
<!--
If the current behavior is a bug or you can illustrate your feature request better with an example, 
please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
-->

https://plnkr.co/edit/amWsyRTLaHOIQv0x7qYi?p=preview for a preview.
Enter 1 for minimum length.
Enter test for actual input
Without erasing the 1, enter 2 for minimum input so that the min input becomes 12. You'll notice that it'll say Ngclass valid, input ng-invalid. Erase the 2, and then it'll say Ngclass invalid, input ng-valid. Alternate between 1 and 12 for min length, and the input and ngClass valid / invalid will alternate

* **Angular version:** 2.X latest
<!-- Check whether this is still an issue in the most recent Angular version -->
Repository: go
Issue: go/doc: enable grouping of functions with common names and suffix N
Labels: NeedsInvestigation

Suggested by @griesemer in another proposal: https://github.com/golang/go/issues/18616#issuecomment-275761203.

An example of the proposed before and after output, for a series of functions called `TrailingZeros` with integer sizes "N" as a suffix:

Before:

```
// TrailingZeros16 returns the number of trailing zero bits in x.
// The result is 16 if x == 0.
func TrailingZeros16(x uint16) uint

// TrailingZeros32 returns the number of trailing zero bits in x.
// The result is 32 if x == 0.
func TrailingZeros32(x uint32) uint

// TrailingZeros64 returns the number of trailing zero bits in x.
// The result is 64 if x == 0.
func TrailingZeros64(x uint64) uint
```

After:

```
// TrailingZerosN returns the number of trailing zero bits in a uintN value x for N = 16, 32, 64.
// The result is N if x == 0.
func TrailingZeros16(x uint16) uint
func TrailingZeros32(x uint32) uint
func TrailingZeros64(x uint64) uint
```

Seems like a big usability improvement, and would be useful in at least `sync/atomic` as it exists now in the stdlib: https://golang.org/pkg/sync/atomic/.  Would also be useful for some of the proposed APIs for a `math/bits` as discussed here: https://github.com/golang/go/issues/18616
Repository: rust
Issue: Tracking issue: declarative macros 2.0
Labels: B-RFC-approved,A-macros,T-lang,B-unstable,C-tracking-issue,F-decl_macro,S-tracking-design-concerns

Tracking issue for declarative macros 2.0 (aka `macro` aka decl_macro aka macros-by-example).

RFC: https://github.com/rust-lang/rfcs/blob/master/text/1584-macros.md

RFC PR: https://github.com/rust-lang/rfcs/pull/1584

cc @rust-lang/compiler 

---

### 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.

## Tasks

 - [ ] Complete the draft hygiene [prototype](https://github.com/jseyfried/rust/tree/hygiene) and [RFC](https://github.com/jseyfried/rfcs/blob/hygiene/text/0000-hygiene.md).
   - [x] Hygiene for items, explicit imports, lexical scopes, and module scopes.
   - [x] Hygiene for globs and trait methods (w.r.t. extension trait candidates in scope for a method call).
   - [x] Hygiene for type directed name resolutions (i.e. methods, associated types, and fields).
   - [x] Support `macro` in blocks as well as modules.
   - [x] Implement inter-crate hygiene, except for nested `macro`s.
   - [ ] Implement "hygiene bending" for when users want a name from macro def to "escape".
       - Examples: https://github.com/rust-lang/rust/issues/91249, https://github.com/rust-lang/rust/issues/46342
   - [ ] Implement inter-crate hygiene for nested `macro`s (pending macro def encoding).
   - [ ] Make `private_in_public` hygienic?
   - [ ] Make `unsafe` and lints hygienic (if appropriate)?
 - [x] Add variant `ast::ItemKind::MacroDef` for `macro_rules!` items and `macro` items (PR #40220).
 - [x] Encode `macro`s in the crate metadata using `TokenStream`, not `String`.
 - [x] Fix #30476 (`private_in_public` details).
 - [x] Fix span issues #30506 and #39450 (PR #40597).
 - [x] Land `macro` behind a feature gate (PR #40847).
 - [ ] Future-proof matchers (e.g. `$e:expr`) by employing a simpler, more general grammar.
 - [ ] Allow fragments (e.g. `$e` where `$e:expr`) to be parsed in more contexts (c.f. #26361).
 - [ ] Decide whether we want macro invocations in identifier positions and/or eager expansion.
 - [x] ~Remove $:meta matcher (#49629)~

Potentially blocking issues:
- https://github.com/rust-lang/rust/issues/71614
Repository: vscode
Issue: Copy line does not work properly with multi-cursor
Labels: feature-request,editor-multicursor

<!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode -->

- VSCode Version: 1.8.1
- OS Version: OSX El Capitan 10.11.6

Steps to Reproduce:

1 .Invoke the "Insert cursor below" or "Inser cursor above" command.
2. Invoke the "Copy line (empty selection)" command.
3. Paste from the clipboard at some arbitrary place in the document.

Results:

One empty line is appended below the cursor.

Expected behaviour:

The copied lines are appended below the cursor.
Repository: neovim
Issue: Mixed languages in intro-screen: type (engl.) vs Tippe (german)
Labels: localization

![screenshot_20170131_212049](https://cloud.githubusercontent.com/assets/3647083/22483092/0b2c2536-e7fc-11e6-8832-5f9d9615c5db.png)
- `nvim --version`:
NVIM 0.1.7
Build type: Release
Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -Wconversion -O2 -DNDEBUG -DDISABLE_LOG -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -DHAVE_CONFIG_H -D_GNU_SOURCE -I/build/neovim/src/build/config -I/build/neovim/src/neovim-0.1.7/src -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/usr/include -I/build/neovim/src/build/src/nvim/auto -I/build/neovim/src/build/include
Übersetzt von builduser

Optional features included (+) or not (-): +acl   +iconv    +jemalloc +tui      
For differences from Vim, see :help vim-differences

          System-vimrc-Datei: "$VIM/sysinit.vim"
     Voreinstellung für $VIM: "/usr/share/nvim"

- Vim (version: ) behaves differently?
- Operating system/version: archlinux
- Terminal name/version: Konsole 16.12.1
- `$TERM`: xterm-256color = Konsole (Plasma) 

### Actual behaviour

### Expected behaviour

### Steps to reproduce using `nvim -u NORC`

```
nvim -u NORC

```
Repository: TypeScript
Issue: Expose ts.matchFiles as public API to make implementing readDirectory easier.
Labels: Suggestion,Help Wanted,API,Experience Enhancement

Problem:

When implementing a custom host that virtualizes the file system, the `readDirectory` method is cumbersome to implement in a way that matches tsc behavior.

If you look at the hosts within typescript, the `matchFiles` method was added to unify behavior with `readDirectory` between hosts.

While `matchFiles` is exported, it isn't in the type definition files so I'm assuming it is "private" API.

Either the host should be able to provide a `getFileSystemEntries(path: string) => { files: string[], directories: string[] }` to get a `readDirectory` implementation or expose `matchFiles`.

I'm working on improving the `broccoli-typescript-compiler` broccoli plugin to have more parity with tsc and VS Code, but I need to virtualize the FS, since broccoli builds from tmp directory and I want the node_modules/@types discovery, tsconfig extends, etc all to work, I need to pretend the tmp dir is inside the project.

Thanks
Repository: go
Issue: proposal: reflect/v2: make Value uncomparable
Labels: v2,Proposal

Comparing two `Value` type does not do what the user expects. The type is documented as such:

> Using == on two Values does not compare the underlying values they represent, but rather the contents of the Value structs. To compare two Values, compare the results of the Interface method.

However, it is still common to see users accidentally make this mistake. What's worse is that it "seems to work", giving a false sense of security.
```go
s1, s2 := "hello", "goodbye"

v1a := reflect.ValueOf(&s1)
v1b := reflect.ValueOf(&s1)
v2 := reflect.ValueOf(&s2)

fmt.Println(v1a == v1a) // Prints true
fmt.Println(v1a == v1b) // Prints true
fmt.Println(v1a == v2) // Prints false
```
This is because the `Value` struct contains a `flag` field whose value may be different for each `Value` and is entirely an implementation detail of the reflect package.

Perhaps we should add a uncomparable type to prevent this misuse:
```go
type Value struct {
	_ [0]func() // Prevents Value from being comparable and occupies 0 bytes
	typ *rtype
	ptr unsafe.Pointer
	flag
}
```

\cc @ianlancetaylor
Repository: TypeScript
Issue: JSDoc syntax highlight. Not supported type '...*'
Labels: Bug,VS Code Tracked,Domain: JSDoc

_From @IgorNovozhilov on November 9, 2016 11:2_

- VSCode Version:

![image](https://cloud.githubusercontent.com/assets/3082812/20135773/90c6cff4-a682-11e6-966f-848580ab35ba.png)

- OS Version: win7 pro

Steps to Reproduce:

I'm used a Google Closure-Type notation:
https://github.com/google/closure-compiler/wiki/Types-in-the-Closure-Type-System#template-types

![image](https://cloud.githubusercontent.com/assets/3082812/20135975/a625b9d6-a683-11e6-807d-d027ed7b5599.png)

Make JSDoc comments:

Not highlighted type and the argument name:

![image](https://cloud.githubusercontent.com/assets/3082812/20135849/f96b098a-a682-11e6-9222-74c46cf02314.png)

And how it works:

![image](https://cloud.githubusercontent.com/assets/3082812/20135869/14ca28f0-a683-11e6-833b-7535e78390d4.png)

And so:

![image](https://cloud.githubusercontent.com/assets/3082812/20135877/243e41a4-a683-11e6-8035-9f6b51536d08.png)

In the example from Google:

![image](https://cloud.githubusercontent.com/assets/3082812/20136076/156f7ebc-a684-11e6-9de3-3929639ca550.png)

I think `{function(this:T, ...)}` a wrong. Must be `{function(this:T, ...*)}`, but so, too, does not work

![image](https://cloud.githubusercontent.com/assets/3082812/20136156/761a1222-a684-11e6-8aed-4cef9c552aa4.png)

And so, too, does not work

![image](https://cloud.githubusercontent.com/assets/3082812/20136267/e335f5f6-a684-11e6-8fbe-56ac357656b3.png)


_Copied from original issue: Microsoft/vscode#15239_
Repository: rust
Issue: rustdoc: types used in exported type definitions are not documented.
Labels: T-rustdoc,C-bug,A-reachable-priv

When I generate docs via `cargo doc`, types used in type definitions are not documented. This is a problem when a module exports a type definition but not the types on which it is based, because even though the type definition is documented, it is entirely opaque.

For example:
```
pub mod foo {
    mod bar {
        pub struct Foo<T> { ... }
        impl<T> Foo<T> { ... }
    }
    pub type Foo = bar::Foo<i32>;
}
```
None of the methods on `foo::bar::Foo<T>` will be documented, and the documentation for `foo::Foo` will be nothing more than its type definition (and any documentation on the type definition itself).

I've tried removing the `skip-private` pass using the following command, and that still does not document the types used in the type definitions:
```
cargo rustdoc -- --passes=strip-hidden --passes=collapse-docs --passes=unindent-comments
```
Is this the expected behavior? Is there some way to document these types without exporting them?