sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Tracking issue for future-incompatibility lint `invalid_type_param_default`
Labels: A-lints,T-lang,T-compiler,C-future-incompatibility,C-tracking-issue

This is the **summary issue** for the `invalid_type_param_default`
future-compatibility warning and other related errors. The goal of
this page is describe why this change was made and how you can fix
code that is affected by it. It also provides a place to ask questions
or register a complaint if you feel the change should not be made. For
more information on the policy around future-compatibility warnings,
see our [breaking change policy guidelines](https://github.com/rust-lang/rfcs/blob/master/text/1589-rustc-bug-fix-procedure.md).
#### What is the warning for?

Type parameter defaults outside of type declarations were never intended
to be permitted, but some early versions of Rust did accept them. For
example:

``` rust
struct Foo<T=i32> { 
    // the default of `i32` is legal here, since this
    // is a type declaration
}

impl<T=i32> Debug for Foo<T> { .. }
//   ^^^^^ default not legal here, in an impl

fn bar<T=i32>(x: T) { }
//     ^^^^^ default not legal here, in a fn
```
#### When will this warning become a hard error?

At the beginning of each 6-week release cycle, the Rust compiler team
will review the set of outstanding future compatibility warnings and
nominate some of them for **Final Comment Period**. Toward the end of
the cycle, we will review any comments and make a final determination
whether to convert the warning into a hard error or remove it
entirely.
#### Current status
- [x] https://github.com/rust-lang/rust/pull/30724 introduces the `invalid_type_param_default` lint as warn-by-default
- [x] https://github.com/rust-lang/rust/pull/36894 makes the `invalid_type_param_default` lint deny-by-default
- [x] https://github.com/rust-lang/rust/pull/42136 tried to make the `invalid_type_param_default` lint a hard error, but there was still too much breakage
- [ ] https://github.com/rust-lang/rust/pull/127655 tried to make this a hard error, but there was still too much breakage (mostly due to `typemap`), so it was just made to show up in future breakage reports instead
- [ ] PR ? makes the `invalid_type_param_default` lint a hard error
Repository: go
Issue: tour: local tour scripts fail to connect to the local server
Labels: NeedsInvestigation

When running golang tour on local machine (go tool tour) scripts are not executing: after pressing Run 
appears "Waiting for remote server..." (see. picture attached) and nothing happens.
I am running Windows 10.

![golang](https://cloud.githubusercontent.com/assets/20325506/19016993/5e953e66-8833-11e6-8442-ea0f1cc406da.PNG)

Please answer these questions before submitting your issue. Thanks!
### What version of Go are you using (`go version`)?

go1.7.1 windows/amd64
### What operating system and processor architecture are you using (`go env`)?

set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
### What did you do?

If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
### What did you expect to see?

Result of script execution
### What did you see instead?

Waiting for remote server...
Repository: pytorch
Issue: expose backend selection and cudnn settings to the end user
Labels: module: cudnn,feature,triaged,Stale

This is needed for the advanced user, where one might need to choose a specific backend, or a particular algorithm / mode in cudnn.


cc @csarofeen @ptrblck @xwang233
Repository: go
Issue: cmd/compile: add line numbers for values and blocks at HTML SSA output?
Labels: NeedsFix,FeatureRequest

We already have it in the "genssa" section, and it's pretty simplifies understanding what's going on. I propose to do the same for other sections of the output.

Since writing `(sourcefile.go:42)` will make output noisier it would be better to show just line numbers in the left column and make them gray colored and with smaller font size than the code (so it looks like in editors).

If you ok with that I can show my vision of design for approval and then provide CL.
Repository: TypeScript
Issue: Rename inconsistency for default exports
Labels: Bug

**TypeScript Version:**  nightly (2.1.0-dev.20161002)

**Code**
##### a.ts

``` ts
function f() {}
export default f
```
##### b.ts

``` ts
import f from "./a"
f()
```

**Expected behavior:**

Renaming `f` in `a.ts` will rename the use in `b.ts`.

**Actual behavior:** 

It doesn't. However, it _does_ if `a.ts` is written as:

``` ts
export default function f() {}
```
Repository: go
Issue: x/mobile: Windows event handling back-pressure
Labels: OS-Windows,mobile

Using go 1.7.1/Windows 7/amd64. `x/mobile` at 16fd47fa04e0a40c643b41876f91f3d06dded396 + fix from #16991.

This is issue can easily be seen when resizing the window: [basic](https://dl.dropboxusercontent.com/u/4300994/Go/WindowsBufferQueueingBasic.gif) and [centering](https://dl.dropboxusercontent.com/u/4300994/Go/WindowsBufferQueueing.gif).

`theApp` event queue contains an infinite buffer in `x\mobile\app\app.go` and when Windows sends messages at a high rate -- e.g. during a window resize -- the whole interface becomes laggy.

Windows sends events [as fast as you let it](https://blogs.msdn.microsoft.com/oldnewthing/20111219-00/?p=8863) -- but since there is no back-pressure in `x\mobile\app\shiny.go` the queue gets flooded with Paint and Resize events.

_PS: It could become an issue in shiny as well, because it also contains async handling of messages. However ATM there is no infinite queue, at least I couldn't find one, hence it provides some back-pressure which prevents Windows from flooding the queue._
Repository: vscode
Issue: Trim trailing whitespace only on changed lines
Labels: feature-request,editor-commands

Feature Request:

When working with existing old code base it's not ideal to have the whole file trimmed for trailing whitespace. However, it's still a nice feature to have active for changed lines. That way the codebase will be cleaned up as you work on it.
Repository: angular
Issue: [RFC]elements schema: add support for custom schemas
Labels: feature,freq2: medium,area: core,area: security,core: directive matching,cross-cutting: custom elements,P3,feature: under consideration

in `@Compoent`, schemas can currently only use the following values:
- `CUSTOM_ELEMENTS_SCHEMA` -> allow any `custom-tag` with any property,
- `NO_ERRORS_SCHEMA` -> allow any tag and any property

We need to implement a way to defined custom schemas, ie defining all polymer elements and their properties (and events).

@mprobst when would you be available so that we can discuss how to integrate with the security schema ?
Repository: vue
Issue: $refs should be reactive to be able to use them in computed properties
Labels: feature request,discussion

Now that refs are no longer reactive, we need to emit events and payloads from child components.
This is fine and works well, but it becomes hard to maintain in the following scenario:

When you create a custom form input component, that basically wraps an input into it's own re-usable component, we can no longer access the input's value (and other props) reactively in e.g. a computed prop in the parent.

Take the following use-case:

```
<my-input ref="email"></my-input>
<my-input ref="password"></my-input>
<p>This is {{ isValid ? 'valid' : 'invalid' }}</p>
```

Previously we could create a computed prop like this:

```
isValid() {
  return this.$refs.email.isValid && this.$refs.password.isValid
}
```

Since refs don't work reactively anymore, we now need to use `$emit` to inform the parent of changes.
However, these emits are handled by methods, so we need a separate handler per input to deal with the events.

Something like:

```
<my-input @valid="handleValidEmail"></my-input>
<my-input @valid="handleValidPassword"></my-input>

handleValidEmail(value) {
  this.email = value
  this.emailIsValid = true
},

handleValidPassword(value) {
  this.password = value
  this.passwordIsValid = false
}
```

You could refactor this a bit, but it's not a nice way of dealing with this and I'm assuming using forms is quite a common occurence for a lot of devs.

Can we think about a better solution to something like this?
Repository: nvm
Issue: Install notice for unmaintained versions.
Labels: feature requests

With Node 0.10 hitting its [EOL at the end of the month](https://github.com/nodejs/LTS) what do you all think about giving folks a heads up, like a console warning, when an EOL'd version of Node is installed? \@thealphanerd.
Repository: rust
Issue: travis-cargo currently cannot upload / generate code coverage information for documentation tests
Labels: T-rustdoc,C-feature-request

@alexcrichton mentioned in [this issue](https://github.com/rust-lang/cargo/issues/3140) that this might be a bug in `rustdoc --test`. Currently it is not possible to generate code coverage information from documentation tests. This results in either wrong coverage information being generated (when some functionality is tested exclusively in documentation tests). The current workarounds are unfortunately to either duplicate documentation tests into module tests to generate correct code coverage information, or to "accept" wrong code coverage information in e.g. coveralls.
Repository: TypeScript
Issue: JS Doc type intellisense not working when using custom file extension
Labels: Suggestion,Awaiting More Feedback,VS Code Tracked

_From @csvenke on September 30, 2016 20:52_
- VSCode Version: 1.5.3
- OS Version: Windows 10

In a .js file, intellisense provides correct jsdoc types
![js](https://cloud.githubusercontent.com/assets/9643219/19006509/20ad4dec-8760-11e6-9c36-94f46308d147.JPG)

In a custom extension file associated with javascript, types from jsdoc are not provided
![sj](https://cloud.githubusercontent.com/assets/9643219/19006504/1a07fa0a-8760-11e6-9c01-4af978f2e6a6.JPG)
#### Steps to Reproduce:
1. Create a .sj file
2. In settings.json, set "files.associations": { "*.sj": "javascript" }
3. Create a function with jsdoc parameters with types
4. Call function and check if intellisense provides types

_Copied from original issue: Microsoft/vscode#13100_
Repository: neovim
Issue: RPC host should auto-restart if the process dies unexpectedly
Labels: enhancement,api,job-control,channels-rpc

This came up in https://github.com/Shougo/deoplete.nvim/issues/322

As it stands now, there doesn't seem to be any way for a rplugin to resume operation without restarting Neovim altogether if the plugin host disappears for any reason.

So far, I was able to get the host to restart with:

``` diff
diff --git a/runtime/autoload/remote/host.vim b/runtime/autoload/remote/host.vim
index 110f802..03f5652 100644
--- a/runtime/autoload/remote/host.vim
+++ b/runtime/autoload/remote/host.vim
@@ -41,13 +41,36 @@ function! remote#host#Require(name) abort
     throw 'No host named "'.a:name.'" is registered'
   endif
   let host = s:hosts[a:name]
-  if !host.channel && !host.initialized
+  let restart = 0
+  if host.channel && host.initialized
+    try
+      if rpcrequest(host.channel, 'poll') ==# 'ok'
+        return host.channel
+      endif
+    catch /Invalid channel/
+      let restart = 1
+      let host.channel = 0
+      let host.initialized = 0
+    endtry
+  endif
+
+  if !host.initialized
+    if restart
+      call remove(s:hosts, a:name)
+      let plugins = copy(remote#host#PluginsForHost(a:name))
+      let s:plugins_for_host[a:name] = []
+      for plugin in plugins
+        call remote#host#RegisterPlugin(a:name, plugin.path, plugin.specs)
+      endfor
+    endif
+
     let host_info = {
           \ 'name': a:name,
           \ 'orig_name': get(host, 'orig_name', a:name)
           \ }
     let host.channel = call(host.factory, [host_info])
     let host.initialized = 1
+    let s:hosts[a:name] = host
   endif
   return host.channel
 endfunction
```

But, there's a bit of side stepping happening there because there's a few guards that prevent straight-forward restarting.  The plugin needs to detect the dead channel and call for a reload, as well:

```
function! s:rpc(func, args, attempts) abort
  try
    return call(a:func, [g:deoplete#_channel_id] + a:args)
  catch /E475:\|Invalid channel/
    if a:attempts < 3
      delfunction _deoplete
      call remote#host#Require('python3')
      call _deoplete()
      return s:rpc(a:func, a:args, a:attempts + 1)
    endif
  catch
  endtry

  echohl ErrorMsg
  echo "[deoplete] Lost RPC channel"
  echohl None
endfunction

function! deoplete#rpc#request(...) abort
  return s:rpc('rpcrequest', a:000, 0)
endfunction

function! deoplete#rpc#notify(...) abort
  return s:rpc('rpcnotify', a:000, 0)
endfunction
```

Note: Any functions defined in the rplugin needs to be deleted for the above to work correctly.

I wanted to see if there are any thoughts about rewriting how remote plugins are loaded.

Ping @blueyed @Shougo
Repository: neovim
Issue: :terminal improvements
Labels: terminal

List of terminal improvements.

- [ ] vim-patch 8.0.1804: using :normal in terminal window causes problems
- [ ] vim-patch 8.0.1794: duplicate term options after renaming
- [ ] vim-patch 8.0.1743: terminal window options are named inconsistently
- [ ] vim-patch 8.0.1732: crash when terminal API call deletes the buffer
- [ ] vim-patch 8.0.1592: terminal windows in a session are not properly restored
- [ ] vim-patch 8.0.1744: on some systems /dev/stdout isn't writable
- [ ] vim-patch 8.0.1300: file permissions may end up wrong when writing
- [ ] Revisit https://github.com/neovim/neovim/pull/2570
- [ ] `:!` should use `:terminal` internally. Doesn't affect `:read !foo` etc. See #5396. Use cases: #5580.
  > by making `terminal.c` draw directly to the screen (instead of a buffer) https://github.com/neovim/neovim/issues/1496#issuecomment-144346925
    - [ ] `:%term` should work like `:%!`
    - [ ] `:read :term foo` should work like `:read !foo`
    - Related: vim-patch 8.0.1609: shell commands in the GUI use a dumb terminal (https://github.com/vim/vim/commit/135682517bc378cfdb63fe3a6e3553935f69f6ce)
- [ ] `:term` buffers should `setlocal bufhidden=hide` by default. Fixes #3340 #3138 #5122
- [ ] should respect all `'bufhidden'` flags #2368
- [x] `:emenu` in terminal mode #3393
- [ ] `:te` should open in split, similar to `:help`. Or [not?](https://github.com/neovim/neovim/issues/5431#issuecomment-597523991)
  - [x] support `<mods>` (`:vert`, `:tab`) #15427
  - [ ] `:0te` suppresses the split? cf. https://github.com/tpope/vim-fugitive/commit/bf7f05e62b75570d2bde8cbc131bfe25dbcdb427
- [ ] instead of `:bdelete`ing the buffer after process exit, switch to some other buffer? #5176
- [ ] Do not auto-resize. There's [no good choice](https://github.com/neovim/neovim/pull/5045#issuecomment-257878379) about when to resize and it [causes problems](https://github.com/neovim/neovim/issues/5667).
- [ ] Allow folds https://github.com/neovim/neovim/issues/5682 
  - https://github.com/neovim/neovim/pull/2683
- [x] Follow terminal output in normal-mode if cursor is on last line #6142
- [x] `:term` buffer should be `'modifiable'`. #6142
- [x] Enable user to manage 'scrollback' (buffer-local option) #2637 #6142
- [x] handle FN keys #5014
- [x] handle ctrl-space, ctrl-arrow #3101. Closed by #5014 ?
Repository: neovim
Issue: neovim + neovim-qt on Windows and Symantec
Labels: security,platform:windows,distribution,has:plan

Symantec thinks neovim and neovim-qt exes are suspicious.
Does anybody have same problem? Are they viruses ;-) ?

![nvim_1](https://cloud.githubusercontent.com/assets/27386/19102983/50b4519e-8ad4-11e6-93c7-605a9f44cb99.png)
![nvim_2](https://cloud.githubusercontent.com/assets/27386/19102982/50b45c48-8ad4-11e6-8d84-5815d3ec8235.png)
![nvim_3](https://cloud.githubusercontent.com/assets/27386/19102981/50b3325a-8ad4-11e6-8ad0-e1c30a640e4a.png)
Repository: nvm
Issue: Add nvm ls-remote --short (maybe as default)
Labels: feature requests

With option `--short`, `nvm` would return shorter list, like:

```
v0.1.(14-33)
v0.1.(90-104)
v0.2.(0-6)
(...)
v4.(1-5)
v4.6.0 (latest LTS: Argon)
```

Algorithm for joining ranges should notice the change in Node.js versioning convention - before io.js major version changes was on minor position.

Moreover, switch `--without-deprecated` would be useful too.
Repository: kubernetes
Issue: kubectl / kubernetes not 100% compatible with YAML 1.2
Labels: area/kubectl,sig/api-machinery,sig/cli,priority/important-longterm,lifecycle/frozen,triage/accepted

<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.-->

**Is this a request for help?** (If yes, you should use our troubleshooting guide and community support channels, see http://kubernetes.io/docs/troubleshooting/.): No

**What keywords did you search in Kubernetes issues before filing this one?** (If you have found any duplicates, you should instead reply there.): is:issue yaml in:title version 

---

**Is this a BUG REPORT or FEATURE REQUEST?** (choose one): Bug Report

**Kubernetes version** (use `kubectl version`): v1.3.7 (seems to be the same on master)

**What happened**: I tried to apply a yaml file with `kubectl --context=minikube apply -f ./etc/deployment.yaml` and got a validation error. However the yaml is valid 1.2.

The error is:
    error validating "./etc/deployment.yaml": error validating data: expected type string, for field spec.template.spec.containers[2].command[6], got bool; if you choose to ignore these errors, turn validation off with --validate=false

**What you expected to happen**: kubectl should apply the deployment file

**How to reproduce it** (as minimally and precisely as possible):

Try to apply this object file:

```
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: redis
spec:
  replicas: 1
  selector:
    matchLabels:
      name: redis
  template:
    metadata:
      labels:
        name: redis
    spec:
      containers:
        -
          name: redis
          image: 'redis:3.2'
          command:
            - redis-server
            - '--appendonly'
            - no

```

**Anything else do we need to know**:

The "no" is the source of confusion for the program. In previous YAML versions this should be translated to be a boolean value, but in the current, 1.2, it should be a string "no". kubectl is using the older standard and translating this as a bool.

It is not so simple for me as to quote the "no" value like `'no'` - this object file is the output of another library which uses the 1.2 standard. We need to be aware that of course people will use various libraries to consume and produce yaml.

I believe the problem can be traced from this https://github.com/ghodss/yaml to this source library here: https://github.com/cloudfoundry-incubator/candiedyaml/blob/master/resolver.go#L42

Should kubernetes only support YAML 1.2? It seems to me that we'd want to deprecate previous yaml support since YAML is not backwards compatible. YAML spec versions at: http://yaml.org/ - I have noticed that several of the online yaml validators also seem to get this "wrong".
Repository: youtube-dl
Issue: Saavn (saavn.com) support
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.10.02_. 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.10.02**
### 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

Examples:
- Single audio: http://www.saavn.com/s/song/hindi/Ae-Dil-Hai-Mushkil/Ae-Dil-Hai-Mushkil/Cg0AdD0DeQU
- Playlist: http://www.saavn.com/s/featured/hindi/Raghu_Dixit_-_Coke_Studio_Picks/NGesoSZlFG4_
Repository: opencv
Issue: remap() bug - OutputArray dst must be initialized to zero
Labels: bug,category: imgproc,affected: 3.4

##### System information (version)
- OpenCV => 3.0.0
- Operating System / Platform => Ubuntu 15.10
- Compiler => gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
##### Detailed description

When using OpenCV remap() function, keeping all arguments the same, two consecutive calls to the function give two different results.

Indeterministic behaviour was fixed by initializing the argument "OutputArray dst" to zero.

This requirement should be referred in documentation.

Alternatively, the function should be modified to not depend on the initial contents of "OutputArray dst".
##### Steps to reproduce

``` .cpp
       //img0 is an image
       //undistRectROIMaps00 and undistRectROIMaps01 are mapping matrices
       cv::Mat out1, out2;

       cv::remap(img0, out1, undistRectROIMaps00, undistRectROIMaps01, INTER_LINEAR); 
       cv::remap(img0, out2, undistRectROIMaps00, undistRectROIMaps01, INTER_LINEAR); 

       //now print out1 and out2 and you will see they are different.
```
Repository: angular
Issue: Sugar (*) syntax does not support @Output (and exportAs)
Labels: feature,freq1: low,area: core,core: ng-template and *microsyntax,P4,feature: under consideration

**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**
When using sugar syntax I couldn't find a way to register to `@Output`s.
The expression does not handle (output) and it's not possible to put the output on the element itself since that element is not the actual directive.
I would also like to point out that `exportAs` is not supported in \* directives.

**Expected behavior**
Allow to register to events on the directive.

**What is the motivation / use case for changing the behavior?**
Sugared directives should be on par with regular directives (`@Output`, `exportAs`) as it might cause confusion. 
At least support parsing output's on the expression.
- **Angular version:** 2.0.1
Repository: go
Issue: x/mobile/cmd/gomobile: No implementation found | Android
Labels: NeedsInvestigation,mobile

Hi,

My environment :
- go version go1.7.1 darwin/amd64
- gomobile version +6ea0bb5 Wed Oct 5 13:16:13 2016 +0000 (android,ios); androidSDK=/Users/zoolonly/Library/Android/sdk/platforms/android-23
- On mac os x

I made a .aar file with `gomobile bind -target android`, and imported it in my project. 
When I run the app in a simulator or device I get the following error : 

```
 No implementation found for void go.avcl_client_usage.Avcl_client_usage._init() (tried Java_go_avcl_1client_1usage_Avcl_1client_1usage__1init and Java_go_avcl_1client_1usage_Avcl_1client_1usage__1init__)
```

I tried to update go and gomobile but I am stuck. 

Thanks for your help.