sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: TUI: cursor shape not correctly initialized and restored
Labels: enhancement,tui,has:plan

- Neovim version: v0.1.3-293-g576c5f7
- Operating system: Ubuntu Xenial beta
- Terminal emulator: vte/gnome-terminal (git master)

I have configured my gnome-terminal (in its Profile Preferences dialog) to use an I-Beam cursor. It also inherits from my global Gnome settings that the cursor is blinking.

I have NVIM_TUI_ENABLE_CURSOR_SHAPE=1, so that supposedly the cursor is a rectangle in command mode, and I-Beam in insert mode.

This is true for the main lifetime of neovim, but is neither initialized correctly on startup, nor reverted correctly on exit.

When I start up neovim, the cursor remains what it was before. That is, nvim (incorrectly) assumes it was a solid block, and does not issue the escape sequence that changes it to a block. The fix should be straightforward: initialize the cursor shape when neovim starts up.

Upon exit I'm left with a solid block, and that's not what I want to have there, I'd like to get back to my generally preferred cursor shape. The fix here is trickier. There's no way to query or save/restore the cursor shape. In xterm it's probably impossible, since according to http://invisible-island.net/xterm/ctlseqs/ctlseqs.html (-> "Set cursor style (DECSCUSR, VT520)") you can only choose from 6 different modes, numbered from 0 to 6, whereas 0 and 1 are the same.

VTE (gnome-terminal et al) intentionally differs here from xterm. Numbers 1-6 work just as in xterm: select a particular mode. However, number 0 means to revert to the terminal emulator's default, as specified in its profile preferences.

Of course there's still no guarantee that someone didn't modify the cursor shape by some escape sequence prior to starting up neovim. However, setting mode 0 upon exit would be a nice step towards restoring the previous value in gnome-terminal, whereas it wouldn't hurt xterm. (Note: the parameter 0 can be omitted, "\e[ q" and "\e[0 q" are the same.)
Repository: go
Issue: x/build: add automated notifications for missing builders to its owner and/or golang-dev
Labels: help wanted,Builders,NeedsInvestigation,FeatureRequest

Should the dashbaord send an email to the builder's owner
and/or golang-dev when a builder stops sending results for
more than some time?

The linux/arm64 builder is currently missing, from Feb 24,
so is netbsd/386 builder.

At the very least, the builder dashboard should show which
builders are missing on the web page.
Repository: go
Issue: x/tools/go/gcimporter15: simplify handling of float constants
Labels: Tools

The `(*exporter).float(constant.Value)` method of `golang.org/x/tools/go/gcimporter15` is excessively complex and does not handle extreme cases correctly because the abstract `constant.Value` API provides no easy way to access the big.Rat or big.Float that a `Value` contains.

The API should make it possible to obtain a big.Float from a constant.Value without thinking about arithmetic.  As a side effect, the incorrect cases would go away.
Repository: kubernetes
Issue: RFE: Improve ability to associate a resource to its namespace lifetime
Labels: sig/api-machinery,lifecycle/frozen

An OpenShift user requested the following

> > Is there any way to tie resources (pod, pvc, secrets, bc, etc) to it's belonging namespace without looking for namespace's lifetime?
> > Today I can do it by watching and recording the create and delete events for a namespace, then associate any resources to that namespace, but it doesn't seams to be the best approach. Namespaces can be destroyed and recreated by a different user with same name.
> > I'm looking for something like automatically adding an annotation containing namespace's uid to all resources created inside it (some sort of primary key), as soon as the resource is created.

The use cases was to facilitate their ability to build a billing back-end around container and pvc usage.

The request was to add something akin to a `metadata.namespaceUid` in a well defined part of every namespaced object so they could differentiate objects across the life of a namespace.

@bgrant0607 @smarterclayton - thoughts?  to me, it seems like a reasonable request.
Repository: go
Issue: x/mobile/cmd/gomobile: init doesn't allow for android NDK platform selection
Labels: NeedsFix,mobile

## The Problem

I'm working on a prototype android google cardboard app that will need to use OpenGL ES 3.0/3.1 and most of the application is written in Go. I had a prototype up and running using OpenGL ES 2.0 but when I made the switch to ES 3.0 I found that I needed to write my own wrappers. I used the following block at the beginning of the wrapper to include the gl3.h header file:

```
/*
#cgo LDFLAGS: -lGLESv3  -lEGL
#include <stdlib.h>
#include <GLES3/gl3.h>
#include <GLES3/gl3ext.h>
#include <GLES3/gl3platform.h>
*/
import "C"
```

What happened was that I would get error messages when compiling in Android Studio with the gomobile bind portion of the process stating that it couldn't find the `<GLES3/glh3.h>` file.

When I investigated, it turns out that `gomobile init` for android arm always uses platform-15 from the NDK -- this platform version doesn't include the GLES3 headers because it doesn't support OpenGL ES 3.0 (requires platform 18+, per http://developer.android.com/guide/topics/graphics/opengl.html)
## The Hack

1) I changed `mobile/cmd/gomobile/env.go` ndkConfig to point to platform-19.
2) I changed `mobile/cmd/gomobile/init.go` useStrippedNDK to `false` so that it would download the full NDK as the stripped version doesn't have the platform minimum I needed.

With these changes a fresh `gomobile init` caused me to have the right platform headers in `$GOPATH/pkg/gomobile/android-ndk-r10e/arm/sysroot/usr/include` as well as the right libs in the parallel lib directory. From there I was able to compile the OpenGL ES 3.0 wrapper I was making and run the compiled app on my phone using specific gles3 shaders and functions.
## What I Wanted To See

After I found the problem to be that `gomobile init` always uses the same platform, I think the best solution for me would be to have a flag for `gomobile init` to specify the platform level to support and another flag to control whether or not the full NDK is downloaded so that you don't have to modify the source code.
## System Details 

go version go1.6 windows/amd64
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:/gocode
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set GO15VENDOREXPERIMENT=1
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
Repository: go
Issue: cmd/compile: type checking fails in cycle involving recursive struct and unsafe.Sizeof
Labels: NeedsFix,compiler/runtime

package p

```
import "unsafe"

type hdr struct {
    next *msg
}

type msg struct {
    hdr
    pad [1024-hdrsize]uint8
}

const hdrsize = unsafe.Sizeof(hdr{})
```

This should type check but does not:

```
$ go tool compile /tmp/x.go
/tmp/x.go:14: invalid type for composite literal: hdr
/tmp/x.go:14: invalid expression unsafe.Sizeof(hdr literal)
```

Looks like the compiler gets confused by the not-quite-cycle in the definition.

http://play.golang.org/p/Hbmv1j_UrR

/cc @RLH
Repository: vscode
Issue: Ctrl-K must cut up to the end of the line into the clipboard
Labels: feature-request,macos,editor-commands

Currently Ctrl-K deletes from cursor to the end of line. Ctrl-K must cut into the clipboard.
Repository: go
Issue: cmd/link: traverse the symbol table less
Labels: ToolSpeed

@ianlancetaylor commented in CL 20165:

> The single slowest operation a linker can do is traverse the symbol table and look at every symbol.  The single biggest improvement in link time in the gold linker was changing the number of symbol table traversals from about 25 to about 3.  Yet cmd/link traverses the entire symbol table all the time.  It's not good.

@crawshaw replied:

> Agreed. There are a couple of other not good features:
> - LSym has a Type word, but it's not filled out until some nebulous intermediate pass, so lots of code (like this) ends up string matching on the symbol name prefix.
> - dodata does some odd build-a-linked-list, then sort-the-linked-list-into-segments game.
> 
> I think these problems and the many traversals could be fixed by the object file reader assigning Type and building useful link-wide slices when a symbol is read in. But it is pretty major surgery I'm not ready to perform.

I've moved this to an issue, since folks look for work and ideas in issues.

cc @mwhudson who likes object files. :)
Repository: go
Issue: go/ast: CommentMap should try to update comment positions
Labels: NeedsFix

When updating nodes in a comment map, comments after that node may have position information that leads to wrong placement. Try to update position information if possible.
Repository: flutter
Issue: Toolbar should automatically make an overflow menu
Labels: c: new feature,framework,f: material design,P3,team-design,triaged-design

Right now you have to manually determine what to put on the toolbar vs what to put in a popup menu on the toolbar. We could make the toolbar just take a list of menu items with icons and automatically turn some into buttons and the rest into a menu button.
Repository: vscode
Issue: Hover message/tooltip on ruler when defining decorators
Labels: feature-request,api,editor-scrollbar

Is there a way to define message/tooltip to be displayed in the `overviewRuler` that is defined when you create a decorator (`createTextEditorDecorationType`)?

I found a way to display a `hoverMessage` when you add the decorator itself (`TextEditor.setDecorations`), but the message is displayed at the left side (between the gutter and the text), not in the ruler.

This could be an easy way to get information from other places of the document, without scrolling the file. Just move the mouse over the ruler and get the information. Maybe even becoming a _magnifying glass_ :smile: 

Thanks in advance
Repository: go
Issue: runtime: add softfloat for mips64?
Labels: compiler/runtime

It seems most mips64 hardware don't have FPU, yet one of
our tests test/bench/go1 is very heavy on floating point, so
even on a 2GHz mips64 core, that test needs >10mins alone,
whereas the whole all.bash completes in ~30mins. The problem
is that we're using kernel to trap and emulate every single FP
instruction, which has extremely large overhead.

I'm wondering if we should introduce softfloat for MIPS64 like
what we did for GOARM=5.

Implementation problems aside, the biggest question is how
to enable or disable softfloat on the toolchain level? Should we
introduce a GOMIPS environment variable? Or should we just
always use insert calls to _sfloat before any consecutive FP
instructions, and make _sfloat does nothing if the system has
a FPU? I don't like the way GOARM works and I think it confuses
more than it helped. (Esp. modern ARM chips usually contain
FPU whereas very few MIPS64 chips contain FPU.)

/cc @cherrymui
Repository: go
Issue: compress/gzip: Reader unable to parse headers with long comments
Labels: NeedsDecision

Using `go1.6`

RFC 1952 for gzip does not specify a length for the comment and name fields.

> If FCOMMENT is set, a zero-terminated file comment is
> present.  This comment is not interpreted; it is only
> intended for human consumption.  The comment must consist of
> ISO 8859-1 (LATIN-1) characters.  Line breaks should be
> denoted by a single line feed character (10 decimal).

The current implementation is inconsistent:
- `gzip.Writer` permits the writing of any length comment/name string in `gzip.Header`.
- `gzip.Reader` fails to read any comment/name string in `gzip.Header` longer than 511 bytes.

Playground example: https://play.golang.org/p/Zvjf8Q7jXe
Change 512 to 511 in the example, and it works again.

This causes issues reading gzip files produced by [GZinga](https://github.com/eBay/GZinga), which produces syntactically valid gzip files, but abuses the comment field to store meta data.

Update: I have no intention of fixing this unless there is someone who needs this functionality. Whatever fix we do will need to be careful that we don't introduce a potential vector for DOS attacks since gzip is a common `Transfer-Encoding` in HTTP. We don't want an infinitely long comment to cause a server to allocate an infinite amount of memory.
Repository: TypeScript
Issue: Expose API for getting JSDoc nodes in TypeScript files
Labels: Suggestion,In Discussion,API

Closure adds various semantic JSDoc annotations that aren't currently modeled by TypeScript, such as @export (unrelated to TS export) and @nosideeffects.
https://developers.google.com/closure/compiler/docs/js-for-compiler#overview

As part of our tool chain to run TypeScript through Closure we'd like to be able to munge these via the TypeScript API.  It appears TypeScript gathers JSDoc comments when parsing JavaScript -- is there a good reason to not gather these in TypeScript as well?

Specifically, I believe my suggestion amounts to removing the "if" statement in the below code (though I'm not certain this is the right place) in `parser.ts`:

``` js
        function addJSDocComment<T extends Node>(node: T): T {
            if (contextFlags & NodeFlags.JavaScriptFile) {
                ...all of the code is in here...
            }
        }
```
Repository: nvm
Issue: Don't auto-default when system is present?
Labels: installing node,feature requests,pull request wanted

Perhaps the new "auto-default on nvm install when no default is set" should avoid this assumption when `nvm_has_system_node`. (per discussion with @jfhbrook).

In the meantime, `nvm alias default system` prevents it.
Repository: TypeScript
Issue: Inconsistent import behavior would cause `.d.ts` to break.
Labels: Suggestion,Needs Proposal

# TL;DR;

The current inconsistent import behavior in different module mode (`system` or `commonjs`) would cause `.d.ts` to break (1.8 included).
# Potential Solution
- Add a "module {system,commonjs}" directive and so that the `.d.ts` file will be processed correctly
- Unify the import/export syntax and behavior
- `.d.ts` uses a module agnostic import/export syntax
# Context

The context of this problem is about module mapping (such as what `jspm` and `typings` supports).

Basically saying any module can be referenced by a different name to avoid module name collision. e.g. in a project that use two versions of `jquery`, one would be imported normally (`import $ from 'jquery'`), one would be imported with a different name (`import $old from 'jquery@1.6'`).

In `1.8`, with the support of `allowSyntheticDefaultImports` enables the behavior become similar (but if the user set it to `false` could still diverge). However the behavior of `import * as A from 'abc';` and `import dr = require('domready');` are still different.
# Problem

The current (1.8) `module` support is working fine when creating package in TypeScript and distributing it as `.js`.

However it does not work if the package is distributed in `.ts` or with `.d.ts`.

The reason is that when distributing in the compiled form, the `module` mode used by the package author is captured in the `.js` file. When distributing `.ts` and `.d.ts` it relies on the consumer to use the same `module` mode as the package author intended.

This means if the package authors (including all typings authors) create the package using one `module` mode, and the consuming application/package use a different `module` mode, the system will fail.

It is worse if the consuming application/package uses multiple packages with disagreeing `module` mode.

Here are the original discussion:
https://github.com/typings/typings/issues/149

This is closely related to:
https://github.com/Microsoft/TypeScript/issues/7125

Please let me know if there are any confusion or missing information / context.
Repository: go
Issue: x/mobile: graphics quality with OpenGL ES
Labels: mobile

Please answer these questions before submitting your issue. Thanks!
1. What version of Go are you using (`go version`)?
   go version go1.6 linux/386
   gomobile version +0ee7f82 Thu Mar 3 05:14:23 2016 +0000 (android); androidSDK=/home/startek/android-sdk/platforms/android-23
2. What operating system and processor architecture are you using (`go env`)?
   GOARCH="386"
   GOBIN=""
   GOEXE=""
   GOHOSTARCH="386"
   GOHOSTOS="linux"
   GOOS="linux"
   GOPATH="/home/startek/go/dev"
   GORACE=""
   GOROOT="/home/startek/go"
   GOTOOLDIR="/home/startek/go/pkg/tool/linux_386"
   GO15VENDOREXPERIMENT="1"
   CC="gcc"
   GOGCCFLAGS="-fPIC -m32 -pthread -fmessage-length=0"
   CXX="g++"
   CGO_ENABLED="1"
3. What did you do?
   (Use play.golang.org to provide a runnable example, if possible.)
   Draw arc with OpenGL ES.
4. What did you expect to see?
   Smooth arc.
5. What did you see instead?
   Unsmooth arc.

Please, change configuration of context creation. From this in android.c (also in x11.c and others):

``` c
const EGLint RGB_888[] = {
    EGL_RENDERABLE_TYPE, EGL_OPENGL_ES2_BIT,
    EGL_SURFACE_TYPE, EGL_WINDOW_BIT,
    EGL_BLUE_SIZE, 8,
    EGL_GREEN_SIZE, 8,
    EGL_RED_SIZE, 8,
    EGL_DEPTH_SIZE, 16,
    EGL_CONFIG_CAVEAT, EGL_NONE,
    EGL_NONE
};
```

to:

```
const EGLint RGB_888[] = {
    EGL_RENDERABLE_TYPE, EGL_OPENGL_ES2_BIT,
    EGL_SURFACE_TYPE, EGL_WINDOW_BIT,
    EGL_BLUE_SIZE, 8,
    EGL_GREEN_SIZE, 8,
    EGL_RED_SIZE, 8,
    EGL_DEPTH_SIZE, 16,
    EGL10.EGL_SAMPLE_BUFFERS, 1,
    EGL10.EGL_SAMPLES, 4,  // This is for 4x MSAA.
    EGL_CONFIG_CAVEAT, EGL_NONE,
    EGL_NONE
};
```

I know, some devices may not support this configuration - but many devices on Android uses modern hardware, and now supports OpenGL ES 3.0.
Repository: vscode
Issue: Add setting to automatically hide the side bar
Labels: feature-request,ux,layout

Would it be possible to add a option to automatically hide the files explorer after a configurable duration ?
Repository: kubernetes
Issue: RC and RS controllers should cap number of outstanding actions, not wait for all to complete
Labels: priority/backlog,sig/scalability,area/controller-manager,sig/apps,lifecycle/frozen

Once the controllers track creation and deletion of individual objects, they should just cap the number of outstanding actions rather than await all outstanding actions to complete. That would allow new actions to be initiated as previous ones complete, rather than create stair-stepping behavior due to fixed batch sizes.

Deletion tracking is being added by #22579, but robust creation tracking would require pod name generation by the controller.

cc @bprashanth
Repository: youtube-dl
Issue: Site support: amebafresh.tv
Labels: site-support-request

Used by, at least, Capcom for Japanese announcement streams.

They use the same URL structure for both live videos and VODs (instant VODs).
Example: https://amebafresh.tv/capcomchannel/6806
Repository: go
Issue: cmd/compile: performance of embedded interfaces
Labels: compiler/runtime

Please answer these questions before submitting your issue. Thanks!
1. What version of Go are you using (`go version`)?
   `go version devel +6bd63ca 2016-03-06 16:12:33 +0000 linux/amd64`
2. What operating system and processor architecture are you using (`go env`)?

```
➜ go env
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/oneofone/code/go"
GORACE=""
GOROOT="/usr/src/go"
GOTOOLDIR="/usr/src/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build035989829=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
```
1. What did you do?
   (Use play.golang.org to provide a runnable example, if possible.)
   http://play.golang.org/p/paUFpqwntQ
2. What did you expect to see?
   embedded interfaces being as fast as assigning them to a field.

`struct { sort.Interface } vs struct { a sort.Interface }`
1. What did you see instead?

```
BenchmarkEmbeded-8           100          22515496 ns/op          802944 B/op          6 allocs/op
BenchmarkEmbededPtr-8         50          22651711 ns/op          802896 B/op          6 allocs/op
BenchmarkField-8             100          16229781 ns/op          802875 B/op          4 allocs/op
```
Repository: flutter
Issue: We should document font-family mapping conventions
Labels: framework,engine,d: api docs,a: typography,P3,team-engine,triaged-engine

- [ ] Document the conventions in `dart:ui`. What names are considered special, what do they mean.
- [ ] Document the conventions in our porting guide. What names should be supported, where should it be implemented.
- [ ] Document the conventions in the framework `TextStyle` class dartdocs.
Repository: rust
Issue: Include images in rustdoc output
Labels: T-rustdoc,C-feature-request

As written by Luthaf over here

https://users.rust-lang.org/t/include-images-in-rustdoc-output/3487

"Hi rustaceans!

Images in documentation can be really useful to provide some insight on algorithms or modules organisation.

It is already possible to insert a link to an image in documentation comment

```
/// ![Alt version](url://for/this/image.png)
```

But using this method, we only get to include images already available in some place of Internet.

Is it a way to make rustdoc copy some files to the target/doc folder, so that it is easy to include specific images in the documentation? The same could go for other static files, like specific CSS or JS.

Is it possible yet? If not, do you think it is worth it?"

I this this would be awesome to include as sometimes using images is much easier when explain something than showing text.
Repository: go
Issue: x/mobile/misc/androidstudio: establish gradle plugin release process
Labels: help wanted,mobile

https://plugins.gradle.org/plugin/org.golang.mobile.bind is a gradle plugin
to integrate gomobile bind execution in android project build. 
The source code is located in misc/androidstudio directory.
Testing before release is manually done, which doesn't scale and isn't reliable.

The release process should include
- testing/canarying
- version management

Unfortunately this doesn't involve Go programming.
Repository: kubernetes
Issue: API and sufficient OpenAPI info to translate metadata, object names/references, and selectors to relative API URIs
Labels: priority/important-soon,area/api,area/client-libraries,sig/api-machinery,area/ecosystem,priority/important-longterm,lifecycle/frozen

Forked from #22511

Even with the discovery API, clients need complicated code to translate between kind, apiVersion, namespace, name, etc. and URL paths. We should provide a server-side endpoint to perform this translation. People shouldn't have to reverse-engineer our complicated client libraries in order to figure out how to write a client properly.

Related to #12143

cc @deads2k @lavalamp @smarterclayton
Repository: go
Issue: os/user: add illumos getgroups support
Labels: NeedsFix,OS-illumos

Solaris is broken after the os/user groups change:

http://build.golang.org/log/26a14fbc0126ab1ed65eaeffe18362689b13a54f

```
...
net
os/user
# os/user
Undefined           first referenced
 symbol                 in file
getgrouplist                        $WORK/os/user/_obj/lookup_unix.cgo2.o
ld: fatal: symbol referencing errors. No output written to $WORK/os/user/_obj/_cgo_.o
collect2: error: ld returned 1 exit status
crypto/x509
net/textproto
log/syslog
...
```

Let me know if you need help testing on Solaris. It's not yet a trybot, due to lack of time.
Repository: react
Issue: onResponderGrant called before onResponderTerminate
Labels: Type: Bug,Component: DOM

When a responder captures the active responder, it seems that `onResponderTerminate` is not called until after `onResponderGrant`. This seems like the wrong thing to do. Are there reasons for this behavior?
Repository: nvm
Issue: README file should explain what the software is
Labels: pull request wanted

README files conventionally begin with a brief description of what the software is.  There is no such description in the README file for nvm, which is unfriendly for beginners.