sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: TUI + guicursor : artifacts on mode-change
Labels: bug,tui,display

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`:
```
NVIM v0.2.3-856-g0848add48
Build type: Release
LuaJIT 2.0.5
Compilation: /usr/local/Homebrew/Library/Homebrew/shims/super/clang -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -I/tmp/neovim-20180318-33096-1djfgu9/build/config -I/tmp/neovim-20180318-33096-1djfgu9/src -I/usr/local/include -I/usr/local/opt/gettext/include -I/usr/include -I/tmp/neovim-20180318-33096-1djfgu9/build/src/nvim/auto -I/tmp/neovim-20180318-33096-1djfgu9/build/include
Compiled by vheon@spark

Features: +acl +iconv +jemalloc +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/local/Cellar/neovim/HEAD-0848add_1/share/nvim"

Run :checkhealth for more info
```
- Vim (version: ) behaves differently?
- Operating system/version:
OSX 10.11.6
- Terminal name/version:
iTerm2 3.1.6
- `$TERM`: xterm-256color

Sorry I could not find a better title. I've trimmed my configuration to a minimal reproducible test case where having gruvbox setted as my colorscheme with the `guicursor` setted as in the `testinit.vim` file I get `f`s whenever I go from one mode to another. It looks like the culprit is actually that specific value of `guicursor` because for example having `set guicursor=v:block-Search,i:block-CtrlPMode2` does not trigger this.


### Steps to reproduce using `nvim -u testinit.vim`

```viml
call plug#begin('/Users/vheon/.vim/bundle')
Plug 'morhetz/gruvbox'
call plug#end()

set termguicolors
colorscheme gruvbox
set guicursor=n:block-lCursor
```

```
nvim -u testinit.vim

:<esc>
```

or

```
nvim -u testinit.vim

V<Esc>
```

### Actual behaviour

![screen shot 2018-05-16 at 22 20 57](https://user-images.githubusercontent.com/90633/40142190-45d6f35e-5958-11e8-88e0-ece5e4950f50.png)

![screen shot 2018-05-16 at 22 30 23](https://user-images.githubusercontent.com/90633/40142432-d9290584-5958-11e8-87f9-26f617508847.png)
Repository: flutter
Issue: Scrollable.ensureVisible is not useful for items scrolled out of view.
Labels: c: new feature,framework,f: scrolling,customer: mulligan (g3),P2,team-framework,triaged-framework

Internal: b/292548523

When a context is thrown out, it's not possible to ensure that it's visible.

To reproduce in the Flutter Gallery: https://github.com/flutter/flutter/compare/master...DaveShuckerow:ensure-visible?expand=1

It would be helpful to have APIs for scrolling a Scrollable in the direction of something even if the context isn't available, as well as to easily check if a widget inside of a scrollable is visible.
Repository: opencv
Issue: imreadmulti cannot read 32-bit
Labels: priority: low,category: imgcodecs

##### System information (version)
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit 
- Compiler => Visual Studio 2017

and

- Operating System / Platform => ubuntu 16.4
- Compiler => gcc-7


##### Detailed description
32-bit image stacks which include several slices but can only be identified as 1 slice.

I attached my project on both Windows and Ubuntu here. There are four images in the attached documents, watershed_solid-8bit(5 slices), test-RGB(3 slices) work well. However, watershed_solid-32bit(5 slices) and test-32-bit (3 slices)  only be recognized as 1 slice.

##### Steps to reproduce


```.cpp
#include <iostream>
#include <vector>
#include <fstream>
#include <opencv2/opencv.hpp>

using namespace std;
using namespace cv;

int main(int argc, char **argv) {
	std::vector<cv::Mat> image;
	/*bool successful = cv::imreadmulti("watershed_solid-32bit.raw", image, cv::IMREAD_ANYDEPTH);*/
	bool successful = cv::imreadmulti("test-32-bit.tif", image, cv::IMREAD_ANYDEPTH);
	cout << "image's size is " << image.front().rows << 'x' <<
		image.front().cols << 'x' <<
		image.size() << endl;
	
	cout << "the size of vector image is " << image.size() << endl;

	system("pause");
	return 0;
}
```

Project attached here
https://drive.google.com/open?id=1Ix04XV3ye0UGLGx9OCVap_esRPPhcHow
Repository: neovim
Issue: call sync() on CursorHold
Labels: enhancement,performance,robustness,io,system

https://github.com/neovim/neovim/pull/8304 changed `nofsync` to be somewhat more robust, in particular swapfiles are fsync'd on CursorHold.

But we could also call [sync()](https://en.wikipedia.org/wiki/Sync_(Unix)) on CursorHold, to reduce dependence on swapfiles. However a small but probably worthwhile optimization would be to only do this if a buffer was written. Need a flag or something like that.

- Additional (low-risk) improvement: modify  [updatescript()](https://github.com/neovim/neovim/pull/8304/files#diff-1c25b3c9884177e3e12380a2ced7d51bR1354) so that `++count >= p_uc` does _not_ trigger unless 'updatetime' (*non*-idle) has elapsed.
    - Rationale: scripted or _batch_ input is not an important data-loss risk in the event of an abrupt OS failure.

---

see also

- https://github.com/vim/vim/issues/8879
Repository: rust
Issue: "#[derive] can't be used on a non-Copy #[repr(packed)] struct" but struct is Copy
Labels: C-bug,A-repr-packed

Reported by @retep998 at https://github.com/rust-lang/rust/issues/46043#issuecomment-389696974, here's a minimal example:
```rust
#[repr(packed)]
#[derive(Debug)]
struct Foo {
    x: usize,
}

impl Clone for Foo {
    fn clone(&self) -> Self {
        Foo { x: self.x }
    }
}
impl Copy for Foo {}
```
[play](https://play.rust-lang.org/?gist=ec60a3f40eaf5cc5f57dd4b206b15fba&version=stable&mode=debug)
Repository: go
Issue: x/cmd/gotype: undeclared name: _Ctype_struct_bpf_program
Labels: NeedsInvestigation

Cgo struct types of the form `_Ctype_struct_` seems to be unknown to `gotype`.

### What version of Go are you using (`go version`)?
go version go1.10.2 linux/amd64

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOOS="linux"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"

### What did you do?
Lint using `gotype` a dummy package which imports `github.com/google/gopacket/pcap`.

`$ go get -u github.com/google/gopacket/pcap`
```
$ cat $GOPATH/src/github.com/google/dummy/dummy.go
package dummy
import _ "github.com/google/gopacket/pcap"
```
`$ gotype dummy.go`

### What did you expect to see?
No output (as in everything is OK).

### What did you see instead?
```
dummy.go:2:10: could not import github.com/google/gopacket/pcap (type-checking package "github.com/google/gopacket/pcap" failed ($GOPATH/src/github.com/google/gopacket/pcap/pcap.go:533:49: undeclared name: _Ctype_struct_bpf_program))
```
Running `gotype` on `github.com/google/gopacket/pcap` directly gives:
```
$ gotype pcap.go
pcap.go:533:49: undeclared name: _Ctype_struct_bpf_program
pcap.go:203:7: undeclared name: _Ctype_struct_bpf_program
pcap.go:661:66: undeclared name: _Ctype_struct_bpf_program
pcap.go:801:34: undeclared name: _Ctype_struct_pcap_addr
pcap.go:401:17: invalid operation: p.pkthdr (variable of type *invalid type) has no field or method ts
pcap.go:403:19: invalid operation: p.pkthdr (variable of type *invalid type) has no field or method ts
pcap.go:406:27: invalid operation: p.pkthdr (variable of type *invalid type) has no field or method caplen
pcap.go:407:20: invalid operation: p.pkthdr (variable of type *invalid type) has no field or method len
pcap.go:425:4: invalid operation: p (variable of type *Handle) has no field or method waitForPacket
pcap.go:488:13: undeclared name: _Ctype_struct_pcap_stat
```
Repository: vscode
Issue: Feature request: Allow Code Outline in Minimap location
Labels: feature-request,outline

I'm using the VS Code insiders build, which has Code Outline built in. I loved this feature from Nuclide, but in its current incarnation it's not as useful as it could be (to me). I have to choose now between file tree (or git or any other of course) sidebar and Code Outline, but I'd prefer to always have it next to my code.

My idea was to allow what is now the Minimap to use different "widgets" (sorry, I've never developed for VS Code so I don't know the correct terminology), so the Code Outline view could live there instead of the (minimally useful Minimap).
Repository: go
Issue: brand: presentation theme: awkward overlap on Quote slide
Labels: NeedsInvestigation

In the second Quote slide of the Go presentation theme (https://golang.org/s/presentation-theme#slide=id.g33148270ac_0_439), the name at the bottom often just barely clips the top of the jellyfish picture (see the letter ‘R’ in the screenshot below).

None of the rest of the text on that slide clips into the pictures, so that one incursion is distracting, and the lower contrast between the text and the jellyfish can make that part of the text more difficult to read.

(CC: @spf13)

<img src="https://user-images.githubusercontent.com/5200974/40189006-4cb5ac1c-59c9-11e8-8566-072685b2e91f.png" width=300px alt="text overlapping jellyfish">
Repository: go
Issue: html/template: does not recognize rgb() as a CSS color
Labels: help wanted,NeedsInvestigation

Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
tip

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
does not matter

### What did you do?
An code fragment to reproduced is here: https://play.golang.org/p/r8LOFN_roBo
Using `string` instead of `template.HTML` produces the same result.

### What did you expect to see?
`color: rgb(10,20,30)`

### What did you see instead?
`color: ZgotmplZ`
Repository: rust
Issue: Warn and eventually forbid transmute::<T, U> for T or U with unspecified (Rust) layout
Labels: A-lints,T-compiler,C-feature-request

It is a fairly commonplace mistake to do a `transmute::<T, U>` for `T` and `U` which are not necessarily compatible, but happen to work at that some particular point in time. These transmutes either change in behaviour when the compiler is updated or stop compiling altogether (because the size of T and size of U are not the same anymore (see e.g. https://github.com/rust-lang/rust/issues/50830)).

The same way we error for mismatching sizes, we can also raise such an error (possibly disable-able by a `#[feature(very_fast_such_dangerous)]`)  for types for which sizes may change over time with future compiler releases. Namely, this would prevent using `transmute` on stable for anything that

1. Does not have one of the whitelisted `#[repr()]` attribute on top of the type declaration;
2. Is not a FFI-safe type in the first place.

If we did that already, the issue linked before would’ve failed, because none of the enums have a `#[repr]` attribute on top of them, making their layout unspecified and therefore not transmutable.
Repository: TypeScript
Issue: Revise whitespace handling in JSDoc
Labels: Bug

Ref #24184

Our JSDoc scanner currently always scans whitespace and newlines as significant - the constant need to skip or ignore these tokens, then fix up node positions to account for them (or ignore them) is a brittle process - especially as the jsdoc scanner is interwoven with the normal scanner for certain parts of jsdoc parsing, which _does_ make whitespace insignificant. The JSDoc scanner should behave more like the normal scanner or JSX scanner where whitespace is insignificant (and never has a token made for it), and comment text has an alternate scan mode that munches on all text until something indicates the comment's end (for capturing descriptions). 
AFAIK, whitespace is captured as a token right now to capture indentation for descriptions; however description start position and the raw text of the description should be sufficient to derive the re-indented value. Descriptions should _probably_ be nodes, like `JSXText`, with a range and a processed value (kinda like an identifier or a literal) - this way the original source text remains available via the range, but also have a processed `value` that's has spare blank lines and indentation stripped away (this would help the classifier quite a bit, as it relies on a bunch of implicit structure in the JSDoc parser and AST to capture them today).
Repository: flutter
Issue: Updated AppBar action button during validate callback in TextFormField
Labels: a: text input,framework,customer: mulligan (g3),has reproducible steps,P2,found in release: 3.3,found in release: 3.5,team-framework,triaged-framework,fyi-text-input

Internal: b/292548353

Requirement: 
When `TextFormField` validate callback detects an error, update the AppBar in the Scaffold to disable an action button. 
I was trying to call setState in the validate callback to trigger another widget.build() call. Unfortunately I get "setState() or `markNeedsBuild()` called during build." error. 

What is the correct way to do this behavior. 

I am doing a work around by attaching an onChange callback inside a Form widget that wraps the `TextFormField`. Call validate() on the `TextFormField`'s FormState and setState that way. 

Since Form is not required for `TextFormField`, this doesn't seem like the correct way of doing this.
Repository: TypeScript
Issue: In JS, prototype-assignment methods can't find method-local type parameters
Labels: Bug,Domain: JSDoc,Domain: JavaScript

```js
/**
 * @constructor
 * @template K, V
 */
var Multimap = function() {
  /** @type {!Map.<K, !Set.<!V>>} */
  this._map = new Map();
};
/**
 * @param {!S} o <------ error here, cannot find name 'S'
 * @template S
 */
Multimap.prototype.lowerBound = function(o) {
};
```

**Expected behavior:**
No error, and `o: S`

**Actual behavior:**
Error on o's param tag: "cannot find name 'S'".

It looks like type resolution on prototype-assignment methods only looks at the class to find type parameters, meaning that method-local type parameters are missed. You can refer to `K` in the above example:

```js
/**
 * @param {!K} object
 * @template S
 */
Multimap.prototype.lowerBound = function(o) {
    return 0;
};
```

And you can refer to `S` on a standalone function: 

```js
/**
 * @param {!S} object
 * @template S
 */
var lowerBound = function(o) {
    return 0;
};
```
Repository: go
Issue: x/build/cmd/gitmirror: lock conversations on GitHub commits
Labels: Builders,Proposal,Proposal-Accepted,NeedsFix,FeatureRequest

Occasionally a GitHub user will post a comment on a commit. Frequently these are spam which leads to nuisance emails generated if you watch the repo. Very occasionally these are requests for help, which currently require a human to reply, reminding the OP to raise an issue. This also generates nuisance emails.

I propose that the bot should blanket lock discussion on all commits in this repo.
Repository: electron
Issue: Feature Request: Add query methods for Visual/Layout ZoomLevelLimits
Labels: enhancement :sparkles:

**Is your feature request related to a problem? Please describe.**


The related PR - Microsoft/vscode#49858 (Issue: Microsoft/vscode#48357) - The UI setting of the zoom level was unbounded, although the actual zoom level has clear limits (`+9` <-> `-8`).

We use the `webFrame` module of `electron` the get the zoom level, but it seems to be unbounded, at least not to reasonable values.

I've looked at the `.d.ts` declaration and at the `web-frame.js` and the `c++` header which defines `WebFrame`, and I can only see a method to `Set` the layout and visual zoom level limits, but not retrieve them.

**Describe the solution you'd like**

I want to be able to logically bind the UI settings the values that `electron` itself bounds, not hard coded values that might be right for one screen/resolution/etc.

Currently in the PR listed above, the bounds are hard-coded, and I enforce them myself, logically, because `webFrame.setZoomLevel` and `webFrame.getZoomLevel` do not match the visual zoom level bounds.

I would want to have methods in [webFrame](https://github.com/electron/electron/blob/4fcd178c368e67e543ee10ee84a0947342412a4c/atom/renderer/api/atom_api_web_frame.h), probably called:

```cpp
v8::Local<v8::Value> GetVisualZoomLevelLimits() const;
v8::Local<v8::Value> GetLayoutZoomLevelLimits() const;
```

Which would be exported to the `js` `webFrame` module, which would in-turn allow me to query for the electron bounds value instead of hard coded ones, specifically [here](https://github.com/Microsoft/vscode/pull/49858/files#diff-c93a0e42070e15efe5973a7aa2f71f53), since currently, `webFrame.getZoomLevel`/`webFrame.setZoomLevel` are not limiting values to the visual zoom level limits.

**Describe alternatives you've considered**

Currently, the PR is not in yet in production, but the workaround was to get the `min`/`max` zoom level limits via trial and error, and hard code those limits.

Thanks a lot for reading, perhaps tho I've just missed the methods which allow to do this in my research. But if not, that could help a lot.

If it's not too complicated, I'd love to PR it as well.
Repository: pytorch
Issue: Caffe2 network exported from ONNX does not initialize the model inputs
Labels: caffe2

## Issue description

When exporting an ONNX model to Caffe2 with the [conversion tool](pytorch/pytorch/blob/master/caffe2/python/onnx/bin/conversion.py), the resulting init net does not initialize the model inputs. When running this network in Caffe2, you therefore get the error `Encountered a non-existing input blob: <name of input blob>`, unless you explicitly create the input blob before running the network.

I would like the network to create the blob automatically, so that I don't have to specify the name and size of the input blob manually (this information should be part of the exported network imho).

This problem was already fixed in onnx/onnx-caffe2#48, but it was later changed again by https://github.com/onnx/onnx-caffe2/commit/ff82dca5551fce84d781bb23719fbe2913b30327. I'm not sure which behavior is actually intended.

This is probably related to #6505, but I'm not sure whether it's the same problem.

## System Info

- PyTorch or Caffe2: Caffe2
- How you installed Caffe2: conda
- OS: Ubuntu 16.04
- Caffe2 version: 0.8.dev
- Versions of any other relevant libraries: onnx 1.1.1 from pip
Repository: vscode
Issue: Git - Support Co-Authored-By
Labels: help wanted,feature-request,git

Issue Type: <b>Feature Request</b>

Github introduced a convention where the commit message contains a list of co-authors, for use when pairing.

Example:

```
commit 032db38255275dd7372f575e3d06947c878ef4c6
Author: Tommy Brunn <foo@gmail.com>
Date:   Thu May 17 10:21:16 2018 +0200

    Encode int64

    Co-Authored-By: Tulio Ornelas <bar@gmail.com>
```

Both Github and Atom then displays both authors whenever they are showing author information. See http://blog.atom.io/2018/04/18/atom-1-26.html#github-package-improvements-1 for an example of what it looks like in Atom.

VS Code version: Code 1.23.1 (d0182c3417d225529c6d5ad24b7572815d0de9ac, 2018-05-10T16:03:31.083Z)
OS version: Darwin x64 16.7.0


<!-- generated by issue reporter -->
Repository: kubernetes
Issue: StatefulSet with long name can not create pods
Labels: kind/bug,sig/apps,lifecycle/frozen,needs-triage

**Is this a BUG REPORT or FEATURE REQUEST?**:

/kind bug

**What happened**:

Creating a StatefulSet with a name containing 57 characters resulted could not start any pods as kubernetes added the label "controller-revision-hash" to the pod which apparently contains the StatefulSet name and a hash appended.
The label is not truncated to 63 characters, therefore the creation of the pod fails with the error message


`statefulset-controller  create Pod long-redacted-statefulset-name-xxxxxxxxxxxxxxxxxxxxxxxxx-0 in StatefulSet long-redacted-statefulset-name-xxxxxxxxxxxxxxxxxxxxxxxxx failed error: Pod "long-redacted-statefulset-name-xxxxxxxxxxxxxxxxxxxxxxxxx-0" is invalid: metadata.labels: Invalid value: "long-redacted-statefulset-name-xxxxxxxxxxxxxxxxxxxxxxxxx-58d5fbb889": must be no more than 63 characters
`

**What you expected to happen**:

The label should be truncated or StatefulSets should enforce shorter names.

**How to reproduce it (as minimally and precisely as possible)**:

Create a StatefulSet with a name longer than 57 characters:

```apiVersion: apps/v1
kind: StatefulSet
metadata:
  labels:
    app: sset
  name: long-redacted-statefulset-name-xxxxxxxxxxxxxxxxxxxxxxxxx
spec:
  serviceName: ""
  replicas: 1
  selector:
    matchLabels:
      app: sset
  template:
    metadata:
      labels:
        app: sset
    spec:
      containers:
        - image: alpine
          name: sset-container
          command: 
            - sleep 
            - "300"
```

**Anything else we need to know?**:

**Environment**:
- Kubernetes version (use `kubectl version`): Server Version: "v1.10.2" 
- Cloud provider or hardware configuration: baremetal
- OS (e.g. from /etc/os-release): CentOS-7.5.1804
- Kernel (e.g. `uname -a`): 3.10.0-862.2.3.el7.x86_64
- Install tools: kubeadm
Repository: godot
Issue: Ragdoll / Physical Bones issue
Labels: bug,confirmed,topic:physics,topic:3d

As described in #11973
I've attached an example project below:
[Ragdoll Test.zip](https://github.com/godotengine/godot/files/2016597/Ragdoll.Test.zip)

Example contains 1 scene with 2 skeletons.
First example - a simple worm skeleton that contorts wildly.
Second Example - Robot from 3D platformer, by default I've set the physics simulation to just his arms. They don't stop moving, as if he's very excited about something.
If you hit Enter (ui_accept) the rest of his bones are activated, and he crumples to the floor in quite an unnatural way, not like in the example posted by Andrea (https://godotengine.org/article/godot-ragdoll-system)
Repository: three.js
Issue: Improved Alpha Testing via Alpha Distributions
Labels: Enhancement

Improved alpha testing in mipmapped texture hierarchies via alpha distributions, rather than averaging.

http://www.cemyuksel.com/research/alphadistribution/
http://www.cemyuksel.com/research/alphadistribution/alpha_distribution.pdf
Repository: rust
Issue: Confusing error message when using Self in where clause bounds errornously
Labels: C-enhancement,A-diagnostics,A-trait-system,T-compiler,D-papercut

The source `trait SelfReferential<T> where T: Self {}` gives the error

```
error[E0411]: expected trait, found self type `Self`
  --> src/main.rs:13:35
   |
13 | trait SelfReferential<T> where T: Self {}
   |                                   ^^^^ `Self` is only available in traits and impls
```

This is confusing because the `Self` is in a trait. It just doesn't seem to be valid to use it as the trait bounds of a type in a where clause.