sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: :terminal should update @. (last insert) register
Labels: enhancement,terminal

Fillin' out this bug-like form, but it's more like a feature request.
- `nvim --version`:

```
NVIM 0.1.4
Build type: RelWithDebInfo
Compilation: /usr/local/Library/ENV/4.3/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -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 -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/build/config -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/src -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/deps-build/usr/include -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/deps-build/usr/include -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/deps-build/usr/include/luajit-2.0 -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/deps-build/usr/include -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/deps-build/usr/include -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/deps-build/usr/include -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/deps-build/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/usr/include -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/build/src/nvim/auto -I/tmp/neovim-20160622-1757-1brid47/neovim-0.1.4/build/include
Compiled by jfelice@C02RP20XFVH6

Optional features included (+) or not (-): +acl   +iconv    +jemalloc 
For differences from Vim, see :help vim-differences

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/0.1.4/share/nvim"
```
- Vim (version: ) behaves differently? N/A
- Operating system/version: Mac OS 10.11.?
- Terminal name/version: Terminal.app
- `$TERM`: screen-256color
### Actual behaviour

`E21: Cannot make changes, modifiable is off.` (sometimes)
<no output> (other times)
### Expected behaviour

Repeat last "insert".
### Steps to reproduce using `nvim -u NORC`

```
nvim -u NORC
:terminal<CR>ls<CR><C-\><C-n>.
```
Repository: go
Issue: x/crypto/ssh/agent: support smartcard keys
Labels: NeedsInvestigation

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

```
go version go1.6.2 darwin/amd64
```
1. What operating system and processor architecture are you using (`go env`)?

```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH=""
GORACE=""
GOROOT="/usr/local/Cellar/go/1.6.2/libexec"
GOTOOLDIR="/usr/local/Cellar/go/1.6.2/libexec/pkg/tool/darwin_amd64"
GO15VENDOREXPERIMENT="1"
CC="clang"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fno-common"
CXX="clang++"
CGO_ENABLED="1"
```
1. What did you do?

This doesn't particularly apply, it's that I want to be able to use the client to add and remove smartcard keys. The agent API for this is pretty simple, but the Go implementation ignores them.
1. What did you expect to see?

an implementation
1. What did you see instead?

an unused variable for the protocol number and that's it.
Repository: neovim
Issue: jobattach() : add handlers to an existing job
Labels: enhancement,job-control

Implement ability to attach `on_stdout`/`on_stderr`/etc handler to an existing job. Something like this:

```
call jobattach({jobid}, {opts})
```

where `{opts}` is a dictionary whose structure is the same as that of `jobstart()`.

In fact I think we should deprecate `jobstart()`, rename it `job()`, and if the first argument of `job()` is a job id, operate on the existing job.
Repository: youtube-dl
Issue: [deezer] Add support for full length songs
Labels: 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.07.09.1_. 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.07.09.1**
### 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_?
- [x] 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

---
### If the purpose of this _issue_ is a _site support request_ please provide all kinds of example URLs support for which should be included (replace following example URLs by **yours**):
- Playlist: http://www.deezer.com/playlist/2008373922
- Maybe albums and single videos too

---
### Description of your _issue_, suggested solution and other information

Current script will only download preview version of 30 seconds of each file and only playlists.

I suggest using this python script I found in Github 
https://github.com/reversing-research/deezer-download/blob/master/deezer-download.py
It works out of the box (pending pull requests can be considered)
Repository: angular
Issue: Angular 2 RC 4 New Animations not supported in Directives
Labels: feature,area: animations,effort2: days,freq3: high,workaround2: non-obvious,feature: under consideration

Hi,

It seems that in current release we can add animations to components only and cannot define them as directives. I mean:

**the below works**

```
@Component({
    selector: "animate-demo",
    animations: [
        trigger('openClose', [
            state('closed, void',
                style({ height: "0px" })),
            state('open',
                style({ height: "*" })),
            transition("* => *", animate(200))
        ])
    ]
})
```

**Whereas the below doesn't work:**

```
@Directive({
    selector: "animate-demo",
    animations: [
        trigger('openClose', [
            state('closed, void',
                style({ height: "0px" })),
            state('open',
                style({ height: "*" })),
            transition("* => *", animate(200))
        ])
    ]
})
```

**And gives compilation error in visual studio:**

"Argument of type '{ selector: string; animations: AnimationEntryMetadata[]; template: string; }' is not assignable to parameter of type '{ selector?: string; inputs?: string[]; outputs?: string[]; properties?: string[]; events?: strin...'.  
"

Usually we might want to have the commonly used animations such as slideDown, sliddeUp, fadeIn, fadeOut defined at one place as a directive and then in components where we want to use them we would just want to import the directive and use the animation instead of redefining animation in each component.
Repository: kubernetes
Issue: kubectl logs should *not* fail while a pod is being started, because it makes for a terrible initial experience
Labels: priority/backlog,area/usability,area/kubectl,sig/node,sig/cli,lifecycle/frozen

Currently the following can fail:

```
$ kubectl create -f pod.yaml 
pod "foo" created
$ kubectl logs -f foo
container "build" in pod "build" is waiting to start: ContainerCreating
```

For real world cases where it may take tens of seconds to pull the image, this is intensely frustrating to users because now they have to guess when the pod is started in order to debug it.

For users who specify `kubectl logs foo`, it may be ok to return immediately (we need to debate this).  `-f` is different because the expectation is to wait to see the results of the pod execution.

We need to fix the kubelet to return errors that allow clients to make the determination (probably by improving the types of errors returned by `validateContainerLogStatus` to include structured API errors) and ensure that the pod log (and other log endpoints, like deploy logs) can properly handle surfacing that.  Then we either need to change the logs endpoint for follow to have that behavior (reasonable) or change the clients (more work, harder to justify).  The other log endpoints should be have consistently.

We need to keep backwards compatibility in account on errors - right now we always return 400 Bad Request, but we could add detail causes.  The GenericHTTPResponseChecker would probably need to be wrapped with a more powerful PossibleAPIOrGenericHTTPResponseChecker that tested for JSON output and did the right thing.
Repository: neovim
Issue: :connect to another Nvim server (dynamic detach/reattach, like screen/tmux)
Labels: enhancement,gui,ui,tui,server,ui-extensibility

With nvim's terminal mode, if it had the ability to detach and reattach, it could serve as a replacement for screen or tmux.

This would require a few additional bits:
- A `:detach` function, to stop running the text UI and daemonize into a --headless instance that will survive the current user session ending.
- A command-line argument to list running nvim instances.
- Command-line arguments to attach to a running nvim instance and start the text UI. These need three variations: one that just fails if the session already has an attached text UI, one that detaches any attached text UI first (like `screen -D -R`), and one that attaches without detaching any other attached text UI (like `screen -x`).  (That last one is optional, but I'd find it quite useful.)

cc @jameysharp
Repository: rust
Issue: `#[may_dangle]`, a refined dropck escape hatch (tracking issue for RFC 1327)
Labels: B-RFC-approved,T-lang,B-unstable,C-tracking-issue,F-dropck_eyepatch,S-tracking-perma-unstable

Tracking issue for https://github.com/rust-lang/rfcs/pull/1327
- [x] Allow attributes on lifetime/type formal parameters (`generic_param_attrs` feature): https://github.com/rust-lang/rust/pull/34764
- [x] Add `#[may_dangle]` attribute for lifetime/type formal parameters on `unsafe impl<...> Drop` (`dropck_eyepatch` feature)
- [x] Replace uses of `#[unsafe_destructor_blind_to_params]` attribute in libstd with `#[may_dangle]` #38664
- [x] Update nomicon to use `#[may_dangle]` instead of `#[unsafe_destructor_blind_to_params]` #39196
- [x] Remove support for `#[unsafe_destructor_blind_to_params]` attribute (with warning cycle before removal).
  - [x] Deprecated in #38970
  - [x] need to replace remaining references (e.g. in test suite) to `#[unsafe_destructor_blind_to_params]` with `[may_dangle]` before we can actually remove the former.

For docs explaining the feature, also see [the forge](https://forge.rust-lang.org/libs/maintaining-std.html#is-there-a-manual-drop-implementation).
Repository: godot
Issue: When error in script and "Open dominant script on Scene change" is checked, related scene shoud be opened
Labels: enhancement,topic:editor,usability

**Operating system or device - Godot version:**

**Issue description** (what happened, and what was expected):
Was avoiding to open this issue for a very long time, mostly because I don't feel like a lot of people would benefit from this, but it's coming back to me constantly, so here we go:
In general I'm not using script panel to much, it's quite confusing for me. As far as I know for people like me there is an option `Open dominant script on Scene change`, when this option is checked for 90% of time the script you are seeing is the script that is related to opened scene and this is cool.
The problem occurs in those remaining 10% of time. The most common case when this happens is simply at the time when there is an error in the script:
![scene_script_relation](https://cloud.githubusercontent.com/assets/6129594/16733524/2e919490-4782-11e6-9c50-b4ee36c89c3b.png)
In this example the error is inside the script that is related to SplashNew.tscn scene, but what I'm seeing when I'm looking at tabs is "BaseBall.tscn" and this is confusing me regularly.  
It would be super nice if Godot could open scene that's linked to script in which error occur.

**Steps to reproduce:**

**Link to minimal example project** (optional but very welcome):
Repository: TypeScript
Issue: New option to remove spaces around braces: insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces
Labels: Bug,Help Wanted,Domain: Formatter,VS Code Tracked

_From @aymone on July 8, 2016 17:59_
- VSCode Version: 1.3
- OS Version: Ubuntu 16.04
- Language: JS

Steps to Reproduce:

1.Create a simple object with functions shorthand like:

``` js
const x = {
    a(){}
};
```

2.Use VSCode auto format (ctrl+shift+i):

``` js
const x = {
    a(){ } // why vscode add this extra space between braces?
};
```

Any way to disable this?

_Copied from original issue: Microsoft/vscode#8965_
Repository: vscode
Issue: support font-size in DecorationRenderOptions
Labels: feature-request,api,editor-api

Feature request: support specifying the font size in `DecorationRenderOptions` and `ThemableDecorationAttachmentRenderOptions`.
Repository: flutter
Issue: control-C does not exit app on iOS device from `flutter run`
Labels: platform-ios,tool,P3,team-ios,triaged-ios

```
Application running.
Type "h" or F1 for help and "q", F10, or ctrl-c to quit.
Type "w" to print the widget hierarchy of the app, and "t" for the render tree.
^CApplication finished.
```

Seems we should either fix the instructions or fix the behavior.  I don't really care which. :)
Repository: TypeScript
Issue: Strict null checks for Map members
Labels: Suggestion,Needs Proposal

<!-- BUGS: Please use this template. -->

<!-- QUESTIONS: This is not a general support forum! Ask Qs at http://stackoverflow.com/questions/tagged/typescript -->

<!-- SUGGESTIONS: See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md -->

**TypeScript Version:**  2.0.0-beta
**Code**

``` ts
export interface INode {
    type: string;
    parentNode?: INode;
}

export interface IIdentifierNode extends INode {
    name: string;
}

public static isIdentifierNode (node: INode): node is IIdentifierNode {
    return node.type === NodeType.Identifier;
}

var namesMap = new Map<string, string>();

// main part
if (Nodes.isIdentifierNode(node) && namesMap.has(node.name)) {
    node.name = namesMap.get(node.name);  //`Type 'string | undefined' is not assignable to type 'string'.`
}
```

**Expected behavior:**
No errors

**Actual behavior:** 
`Type 'string | undefined' is not assignable to type 'string'.`

Looks like here no TypeGuards for Maps?
Repository: TypeScript
Issue: Sourcemap - names array empty for all files
Labels: Suggestion,Help Wanted,Experience Enhancement

**TypeScript Version:**  1.8.34.0
**Module System:** AMD 
**ECMAScript Version:** ECMAScript 5
**VS 2015 Update 3**

All of my map files have the names array empty.  I would expect that to have been populated.
This has been an issue with VS2015 with all updates

**Code**

``` ts
class HomeIndex {

    someVar: number;

    constructor() {
        this.someVar = 0;
    }

    onLoad = () => { 
    };

    dispose() {
    };

}

export = HomeIndex;
```

Generated map

``` js
{
  "version": 3,
  "file": "Index.js",
  "sourceRoot": "",
  "sources": [ "Index.ts" ],
  "names": [],
  "mappings": ";;IAAA;QAII;YAIA,WAAM,GAAG;YACT,CAAC,CAAC;YAJE,IAAI,CAAC,OAAO,GAAG,CAAC,CAAC;QACrB,CAAC;QAKD,2BAAO,GAAP;QACA,CAAC;;QAEL,gBAAC;IAAD,CAAC,AAdD,IAcC;IAED,OAAS,SAAS,CAAC"
}
```

**Expected behavior:**
names array should contain values for members and variables
**Actual behavior:** 
names array empty
Repository: You-Dont-Know-JS
Issue: es6 & beyond: ch2, fix inline code snippet to be less confusing
Labels: for second edition

This text: "...with the `config.options.enable` assignment references."

Change that to "...with the `config.options.XYZ` assignment references."
Repository: react
Issue: Attributes and properties for Custom Components
Labels: Type: Feature Request,Component: DOM

**Do you want to request a _feature_ or report a _bug_?**
Feature
**What is the current behavior?**
Custom component's properties are always set as attribute.
**What is the expected behavior?**
Maybe React should watch at the static `observedAttributes` property  for custom elements (https://w3c.github.io/webcomponents/spec/custom/) and then decide to set an attribute or an instance property. Otherwise, objects and array could be always passed as properties, in order to avoid `<custom-element prop="[object Object]"></custom-element>`.
Repository: vscode
Issue: Double click after curly brace to select the content
Labels: feature-request,editor-bracket-matching

This is a feature-request. 

A common use case for me in Eclipse, is to double click on the right after a brace or a curly brace, to select all the content inside it. It's a fast way to select, indent, remove the content. It's a lot more handy to see the ending curly brace (especially for JS and other functionnally langugage). 

![www gifcreator me_zovlan](https://cloud.githubusercontent.com/assets/3749428/16766721/07e53fda-483c-11e6-91dd-f108628db010.gif)
Repository: TypeScript
Issue: Suggestion: should non-null assert propagate?
Labels: Suggestion,Needs Proposal

I was wondering whether `!` should be taken into account by the dataflow analysis, and I don't see why it shouldn't.

It is like a cast that says "this value is not null", so from this point I guess the compiler could remove undefined/null from future uses.

For example, I use `!` to work around #9631, so I have code that looks like (simplified):

``` ts
protected dataArrayChanged(changes: ChangeRecord[]) {
  // #9631: TS incorrectly infers `change: ChangeRecord | undefined`
  for (const change of changes) {
    for (let i = 0; i < change!.removed.length; i++)
      this.dt.row(i).remove();
    if (change!.addedCount > 0)
      this.dt.rows.add(this.data.slice(change!.index, change!.index + change!.addedCount));
  }
  this.dt.draw();
}
```

Observe how I added 5 `!` to make `change` not null. 
The first one could have been enough. After all, once I say "`change` is not `undefined`", there is no reason to assume it could be until I modify the variable again.

``` ts
// Let's say I know x is not undefined
const x: number | undefined;
// Here x: number | undefined, so x! is required
x!.toString();
// Here x: number because of x! above
x.toString(); // ok
```
Repository: neovim
Issue: Replace the builtin pager
Labels: enhancement,ui,pager

- `nvim --version`: NVIM 0.1.4
### Actual behaviour

When doing e.g. `:map`, nvim uses the old clunky vim pager. Which cannot, for instance, _search text._ 
### Expected behaviour

Totally open - I'd be happy with `:terminal less` or putting the text-to-be-paged into a readonly temporary buffer so that I can stay in Vim interfaces.
### Steps to reproduce using `nvim -u NORC`
1. `runtime mappings.vim`
2. `:map`
3. Try to find the mapping you established years ago to bump the foldlevel
4. Despair
Repository: TypeScript
Issue: String methods should have `this` parameters in `lib.d.ts`
Labels: Suggestion,Help Wanted

``` ts
// @noImplicitThis: true
String.prototype.indexOf = function(substr, start) {
    this./**/
}
```

Expected: Method suggestions. No error.
Actual: Nothing. `this: any` error.

Other types in lib.d.ts should probably also have `this` added too.
Repository: go
Issue: cmd/asm: a flag to dump Prog initialization as Go code
Labels: Proposal,Proposal-Accepted,compiler/runtime

When writing code for compiler backends, we sometimes
need to manual create assembly instructions by initializing
`cmd/internal/obj.Prog` structs directly. Even though
the revamped `Addr` types makes the task much easier than
it was, the process is still very error-prone and any mistakes
made there is pretty hard to diagnose.

I propose that we add an internal mode to cmd/asm that
instead of dumping .o object file, it prints the required
Prog initialization code to stdout.

I first discussed this with @cherrymui and we both liked the
idea.

Ideally, the new mode should be able to accept instruction
either from stdin, or better, from command line, so it is easier
to use from within an editor. This mode might also serve as
documentation for mapping instructions to Prog.

/cc @robpike @randall77 @ianlancetaylor
Repository: gin
Issue: Custom BindWith error managing
Labels: enhancement

Hello @danslimmon, @DennyLoko, @sidbusy, @stxml, @dgsi, @kongfei605, @LeBronoMars and @tsirolnik,

First of all, sorry for delay in answering, I was just a little bit busy with university (final exams).

Regarding all the following issues (#629, #633, #636, https://github.com/danslimmon/gin/pull/1 and #661), here is what I suggest:
- Because Gin now has the API frozen (doesn't allow breaking changes in functions or behavior), I can't change the behavior of `c.BindWith()` (#661, @sidbusy), however I like the idea, so keep reading.
- I'll review and merge the PR #633 with the fix https://github.com/danslimmon/gin/pull/1 (@danslimmon, @DennyLoko).
- I propose to add two function/aliases called:
  - `c.ShouldBindWith()` implementing #661, which will allow custom error managment.
  - `c.MustBindWith()` being an alias of `c.BindWith()` and soft deprecating the last one (just a message via `fmt.Println`), for a future change of behavior, by moving `c.ShouldBindWith()` back to `c.BindWith()`.

Because I'm not a native english speaker, maybe the naming of the two new proposed functions sound strange or completely wrong, so I'm open to suggestion about this, and also about everything else in this message.

Hope I did explained correctly. Tell me your thoughts.
Repository: vscode
Issue: Offer code mark styles and gutter marks
Labels: feature-request,ux

_From @darkred on July 10, 2016 23:30_

_(Using VSCode 1.3.0 in win 10 x64 build 10586 with vscode-eslint extension 1.10.18)._

Currently the code marks(for errors and warnings) appear only as squiggly underline (i.e. as **spellchecker errors** in browsers, e.g. Firefox, Chrome):
_(the error is in red, and the warning is in green)_
![2016-07-11_020259](https://cloud.githubusercontent.com/assets/723651/16716650/b635a444-470b-11e6-82fc-90770e8bea05.png)

My suggestion is to offer more code mark styles (ideally  the **outline** style, as it highlights the errors/warnings the best way -see below- ) and **gutter marks** :
_(with the errors to be in red, and the warnings to be in yellow, as ESLint itself uses these colors - not green)_
![2016-07-11_020203](https://cloud.githubusercontent.com/assets/723651/16737733/59dedc70-479b-11e6-8da9-0789ade17143.png)
([here is another screenshot](https://sublimelinter.readthedocs.io/en/latest/_images/marks-outline-dark.png))

It's more easy to distinguish the errors this way.

Thank you

---

_For reference SublimeLinter3 package offers [five different code mark styles](https://sublimelinter.readthedocs.io/en/latest/mark_styles.html) :_ 
- fill, 
- outline   _(the default style)_,
- solid underline, 
- squiggly underline, and 
- stippled underline

_and two types of gutter marks:_ 
- errors, and 
- warnings

_Copied from original issue: Microsoft/vscode-eslint#99_