sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Regex Find can cause VS Code to Freeze
Labels: bug,upstream,freeze-slow-crash-leak,editor-find,upstream-issue-linked,terminal-find

<!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode. -->

<!-- Use Help > Report Issues to prefill these. -->
- VSCode Version: 1.14.1
- OS Version: Mac OSX Sierra 10.12.5 (16F73)

Steps to Reproduce:

1. `code --disable-extensions`
1. *File->New File*
1. Paste file from here: [snippets.py](https://raw.githubusercontent.com/GoogleCloudPlatform/python-docs-samples/master/auth/http-client/snippets.py) (it happens with other files, but this is a simple example)
1. Edit->Find  `"""(.*?\n?)+?"""` regex
1. Try to remove the last `?` from the regex.
1. The editor freezes at this point
1. Code Helper goes to 100% CPU.

Result:
![image](https://user-images.githubusercontent.com/3740137/28280643-bcdb1b42-6b24-11e7-81af-649bca4f45c9.png)

<!-- Launch with `code --disable-extensions` to check. -->
Reproduces without extensions: Yes
Repository: flutter
Issue: complex_layout__start_up timeToFirstFrameMicros noise
Labels: a: tests,team,framework,P3,team-framework,triaged-framework

The complex_layout__start_up timeToFirstFrameMicros benchmark is very noisy. We should run it multiple times and average the result.

cc @yjbanov
Repository: go
Issue: runtime: sub optimal gc scalability
Labels: Performance,NeedsInvestigation,compiler/runtime,Scalability

### What version of Go are you using (`go version`)?
go version devel +4e9c86a Wed Jun 28 17:33:40 2017 +0000 linux/amd64

### What operating system and processor architecture are you using (`go env`)?
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/localdisk/itocar/gopath"
GORACE=""
GOROOT="/localdisk/itocar/golang"
GOTOOLDIR="/localdisk/itocar/golang/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build633808214=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"

### What did you do?
Run test/bench/garbage/tree2 on machine with 88 threads (2 sockets, 22 cores per socket, 2 threads per core) 2x Xeon E5-2699 v4
With following options:
 ./tree2  -cpus=88 -heapsize=1000000000  -cpuprofile=tree2.pprof
### What did you expect to see?
runtime.gcDrain taking insignificant amount of time 

### What did you see instead?
runtime.gcDrain  taking about half of all time:
```
Showing top 10 nodes out of 33
      flat  flat%   sum%        cum   cum%
    36.95s 45.03% 45.03%     75.98s 92.59%  runtime.gcDrain /localdisk/itocar/golang/src/runtime/mgcmark.go
    12.38s 15.09% 60.11%     12.38s 15.09%  runtime.(*lfstack).pop /localdisk/itocar/golang/src/runtime/lfstack.go
     7.51s  9.15% 69.27%      7.51s  9.15%  runtime.greyobject /localdisk/itocar/golang/src/runtime/mgcmark.go
     6.28s  7.65% 76.92%     19.49s 23.75%  runtime.scanobject /localdisk/itocar/golang/src/runtime/mgcmark.go
     4.54s  5.53% 82.45%      4.54s  5.53%  runtime.(*lfstack).push /localdisk/itocar/golang/src/runtime/lfstack.go
```
Looking into runtime.gcDrain, I see that almost all time is spent on 
35.66s     35.66s    924:        if work.full == 0 {
 

I couldn't reproduce this behavior on machine with small number of cores.
Looking into cache miss profile shows that this is due to all cores updating head of work.full,
which causes all reads needed for check to miss cache.
Repository: angular
Issue: Height on auto only animates some of the time when the child height changes
Labels: type: bug/fix,area: animations,freq2: medium,P4

## I'm submitting a...
<pre><code>[ ] Regression (a behavior that used to work and stopped working in a new release)
[X] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Feature request
[ ] Documentation issue or request
</code></pre>

## Current behavior
There is a animation on a parent div with height auto.
There is a child element with a height in pixels.
When the child height changes, the parent should animate, but only does so once in a while.

## Expected behavior
The parent should animate its height every time

## Minimal reproduction of the problem with instructions

![Image](http://i.imgur.com/r7hJBiF.gif)

Plunker; http://plnkr.co/edit/pyfrnV?p=preview
Click the buttons a couple of times.

## What is the motivation / use case for changing the behavior?
Image gallery. In my use case the inner element is an image. Below the image are a couple of thumbs the user can click on to change the larger image above it. The images can be all kinds of different sizes, I want a very quick animation on the height when another image is chosen.

## Environment

<pre><code>
Angular version: 4.3.0

Browser:
- [X] Chrome (desktop) version 59
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
Others:
</code></pre>
Repository: TypeScript
Issue: Properties of instances of anonymous classes have type <any> after an instanceof guard.
Labels: Bug

**TypeScript Version:**  2.4.1

**Code**

```ts
function create_my_class<T>() {
    return class {
        value: T;
        constructor(
            value: T
        ) {
            this.value = value;
        }
    }
}
const MyClassWithNumber = create_my_class<number>();
const with_number = new MyClassWithNumber(234);

with_number.value = 10;
// with_number.value = "sdf"; // error, and rightly so

const something: any = with_number;

if(something instanceof MyClassWithNumber) {
    something.value = 20;
    something.value = "sdf"; // not an error, but should be one
}
```

**Expected behavior:**
The last assignment should be marked as a type error by TS.

**Actual behavior:**
The last assignment is not marked as error. This is somewhat surprising, as the line 
```
with_number.value = "sdf";
```
is righteously reported as a type error by TS.

Not a huge issue, but prevented me from using a class factory.
Repository: go
Issue: runtime: cannot run GO in Windows Server 2016
Labels: OS-Windows,NeedsInvestigation

[Issue]
When running go, a problem is encountered

```
C:\Users\Administrator>go
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0

runtime.asmstdcall(0x8fdd8, 0x40ee8d, 0x10f4000, 0x0, 0x100000044f980, 0x20, 0x11, 0x10f4000, 0x44f8c0, 0x10f0000, ...)
        c:/go/src/runtime/sys_windows_amd64.s:60 +0x5e fp=0x8fd80 sp=0x8fd70
rax     0x0
rbx     0xa992c0
rcx     0xab4e20
rdi     0x204000
rsi     0x8fea0
rbp     0x8fe68
rsp     0x8fd68
r8      0x42e36e
r9      0x8fee0
r10     0xc042000000
r11     0xffffffff
r12     0x0
r13     0xffffffee
r14     0x0
r15     0x0
rip     0x0
rflags  0x10293
cs      0x33
fs      0x53
gs      0x2b
```

[Environment]

Version:
Go 1.8.3 From go1.8.3.windows-amd64.msi (newest).
And the issue resists in go1.9beta2 (newest unstable)

OS:
Microsoft Windows Server 2016 Datacenter

Hardware:
ASUSTek COMPUTER INC. Z10PA-D8 Series
Intel(R) Xeon(R) CPU E5-2620 v4 @2.10GHz, Intel(R) Xeon(R) CPU E5-2620 v4 @2.10GHz
128GB RAM
512GB SSD + 2TB HHD + 6TB HHD
Repository: opencv
Issue: Nightly test failure: Features2d_FLANN_Auto.regression
Labels: bug,priority: normal,category: features2d

[Win32 without IPP](http://pullrequest.opencv.org/buildbot/builders/master_noICV-win32-vc14/builds/10160):
```
[ RUN      ] Features2d_FLANN_Auto.regression
C:\build\master_noICV-win32-vc14\opencv\modules\ts\src\ts.cpp(541): error: Failed

	failure reason: Bad accuracy
	test case #-1
	seed: ffffffffffffffff
-----------------------------------
	LOG:
correct_perc = -1580547965
bad accuracy of Find 

-----------------------------------

[  FAILED  ] Features2d_FLANN_Auto.regression (52716 ms)
```

[20170728](http://pullrequest.opencv.org/buildbot/builders/master_noOCL-win32-vc14/builds/10169)
[20170820](http://pullrequest.opencv.org/buildbot/builders/master_noOCL-win32-vc14/builds/10195)
[20190523](http://pullrequest.opencv.org/buildbot/builders/master_noOCL_noICV-win32-vc14/builds/10812)
[20211120](http://pullrequest.opencv.org/buildbot/builders/master_noOCL_noICV_noSSE-win64-vc14/builds/11712)

[ARMv7 20190406](http://pullrequest.opencv.org/buildbot/builders/3_4_ARMv7-lin/builds/345)
Repository: vscode
Issue: Add support for different fonts in the same file
Labels: feature-request,font-rendering

Add support for choosing different font ligatures, than those within the `"editor.fontFamily"` selected font. For example, I would really like to use Operator Mono letters together with [Fira Code ligatures](https://github.com/tonsky/FiraCode). Atom-editor lets you do this.

A hacky workaround is with the `Custom CSS and JS Loader` extension. https://medium.com/@zamamohammed/multiple-fonts-alternative-to-operator-mono-in-vscode-7745b52120a0 @mohammedzamakhan

The `Custom CSS and JS Loader` extension makes vscode think it is corrupted, so I'd really prefer avoiding this hack.

Another custom workaround, which stopped working: https://gist.github.com/Mikeysax/e707e6971d991a7552017b4c00ef6a97

Semi-related: https://github.com/Microsoft/vscode/issues/192

Possibly helpful: https://github.com/tonsky/FiraCode/wiki/VS-Code-Instructions
Repository: go
Issue: proposal: spec: panic on send/receive on nil channel
Labels: LanguageChange,Proposal,LanguageChangeReview

In Go 1 a send or receive operation on a nil channel blocks forever.  This is by analogy with the select statement, in which a case with a nil channel is ignored.  In particular, these four code snippets all block forever:

    var c1 chan int
    <-c1
    
    var c2 chan int
    select {
    case <-c2:
    }
    
    var c3 chan int
    c3 <- 1

    var c4 chan int
    select {
    case c4 <- 1:
    }

However, the fact is that send statements and receive expressions are not the same as select cases.  They look different in the program and they are implemented differently.  While it is nice to have a send or receive operation behave identically to a select statement with a single case that corresponds to that operation, it is not necessary, and I claim that changing that correspondence will not cause confusion.

I claim further that the fact that nil channels block forever is a point of confusion for new Go programmers.  They must learn to call `make` to create a channel.  When learning Go, it is easy to forget that.  This then leads to confusion when programs simply block rather than reporting an error.  Sample comments:

https://groups.google.com/d/msg/golang-nuts/QltQ0nd9HvE/mAb2K4UHWxUJ
https://groups.google.com/d/msg/golang-nuts/JFTymqVDBcs/E8GDJiQFBQAJ
http://devs.cloudimmunity.com/gotchas-and-common-mistakes-in-go-golang/index.html#using_nil_ch

My final claim is that essentially no real programs rely on the current behavior for nil channels.  I have no way to prove this claim, but in general blocking forever is a goroutine leak, and when people do want to block forever anyhow they use `select {}`.

Give the above, I recommend that for Go 2 we change this corner case and make send or receive operations on nil channels panic.  To be clear I am not proposing that we change the behavior of select statements with nil channels, and I am not proposing that we change any aspect of the behavior for closed channels.  In the above four code snippets, the first and third will panic, while the second and fourth will continue to behave as in Go 1.
Repository: go
Issue: x/build/cmd/gopherbot, x/build/maintner: handle non-Go Github issue repos like gddo
Labels: help wanted,Builders

https://github.com/golang/gddo has a separate issue tracker, but gopherbot ("CL X mentions this issue") can only comment on golang/go repos.

We might also need to update parseGithubRefs in maintner/github.go but at first look at that function makes it seem like it is capable of doing the right thing.
Repository: flutter
Issue: NestedScrollView should assert when child scrollables are passed controllers
Labels: framework,f: scrolling,has reproducible steps,P3,found in release: 3.0,found in release: 3.1,team-framework,triaged-framework

Since `NestedScrollView` wants to provide controllers to the children, it should throw a helpful assertion message if it detects that the children already have controllers.

## Steps to Reproduce

```dart
import 'package:flutter/material.dart';

class Demo extends StatefulWidget {
  @override
  DemoState createState() => new DemoState();
}

class DemoState extends State<Demo> with TickerProviderStateMixin {
  ScrollController _scrollController = new ScrollController();

  @override
  Widget build(BuildContext context) {
    ThemeData themeData = Theme.of(context);
    return new ListView.builder(
      controller: _scrollController,
      itemBuilder: (BuildContext context, int index) {
        return new Container(
          child: new Text("Foo $index", style: themeData.textTheme.display2),
        );
      },
    );
  }
}

void main() {
  runApp(new MaterialApp(
    home: new NestedScrollView(
      headerSliverBuilder: (BuildContext context, bool innerBoxIsScrolled) {
        return <Widget>[
          new SliverAppBar(
            title: new Text('NestedScrollView demo'),
            expandedHeight: 300.0,
            pinned: true,
          ),
        ];
      },
      body: new Material(
        child: new Demo(),
      ),
    )
  ));
}
```

The child ListView is scrollable instead of reducing the size of the SliverAppBar.

![screen shot 2017-07-18 at 12 37 10 pm](https://user-images.githubusercontent.com/394889/28336186-d521cba6-6bb5-11e7-8381-2394c0c4692b.png)

/cc @HansMuller
Repository: opencv
Issue: segmentation fault on Mac OSX when opening an .avi file
Labels: priority: low,platform: ios/osx,incomplete

<!--
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).

This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->

##### System information (version)
Process:               Python [7126]
Path:                  /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python
Identifier:            Python
Version:               2.7.10 (2.7.10)
Code Type:             X86-64 (Native)
Parent Process:        zsh [5380]
Responsible:           Python [7126]
User ID:               501

PlugIn Path:             /usr/local/opt/ffmpeg/lib/libavutil.55.dylib
PlugIn Identifier:       libavutil.55.dylib
PlugIn Version:          ??? (0)

##### Detailed description

<!-- your description -->


#### Steps to reproduce
when I ran the code below:
```.python
import cv2 as cv
cap = cv.VideoCapture('my/path/to/the/video/file.avi')
```
I got ```[1]    7533 segmentation fault  python```
<!-- to add code example fence it with triple backticks and optional file extension
    ```.cpp
    // C++ code example
    ```
 or attach as .txt or .zip file
-->
Repository: go
Issue: runtime: before execve, set signal mask according to os/signal functions
Labels: NeedsFix,early-in-cycle,compiler/runtime

If a program calls the os/signal functions `Notify` and `Ignore`, we should reflect those calls in the signal mask that we pass to child processes that we start using the os or os/exec packages.  The code for this is in https://github.com/golang/go/issues/19196#issuecomment-315907446 .
Repository: rust
Issue: Exact same bound check happens twice in loops when processing slices known to be of the same size
Labels: I-slow,C-enhancement

When compiling in release mode, it is possible to move most bound checks out of a loop when processing slices of the same size by asserting beforehand that they really are of the same size. A simple example of that would be:

```rust
fn process_slices(x: &[u32], y: &[u32], z: &mut [u32]) {
    assert!(x.len() == y.len() && x.len() == z.len());
    for i in 0..x.len() {
        z[i] = x[i] + y[i];
    }
}
```

Unfortunately there's a bound check that remains and is obviously redundant since exactly the same registers are compared at the top and at the bottom of the loop. The snippet of assembly for the inside loop of the above function looks like this:

```assembly
.LBB3_4:
	cmpq	%rax, %rsi
	jae	.LBB3_8
	movl	(%rdx,%rsi,4), %ecx
	addl	(%rdi,%rsi,4), %ecx
	movl	%ecx, (%r8,%rsi,4)
	incq	%rsi
	cmpq	%rax, %rsi
	jb	.LBB3_4
```
The LBB3_4 label isn't used anywhere else. It seems that it would make sense to move it two lines down since if we have %rsi < %rax then surely we cannot have %rsi >= %rax right afterwards.

The same also happens for more complicated loops.

[Here's a Rust Playground link for the example.](https://play.rust-lang.org/?gist=7efa9123866972f1c4195bc5973c8080&version=stable&mode=release)
Repository: TypeScript
Issue: Unexpected TS4094 with the build parameter `declaration: true`
Labels: Bug,Domain: Declaration Emit

**TypeScript Version:**  2.4.1

**Code**

```ts
var Foo = class Foo {
    private _message = "Hi";
    hi() { return this._message; }
}
```

`tsc test.ts -t es2017 -d`

**Expected behavior:** `-d` should not cause this message: `test.ts(1,5): error TS4094: Property '_message' of exported class expression may not be private or protected.`

**Actual behavior:** It does.

There should at least be a suppression parameter to ignore this error.
Repository: TypeScript
Issue: Unexpected type listing for `keyof T` on declaration file
Labels: Bug,Domain: Declaration Emit

**TypeScript Version:**  2.4.1
**Code**

```ts
var Foo = class Foo {
    method<T extends keyof ElementTagNameMap>() {};
}

class Bar {
    method<T extends keyof ElementTagNameMap>() {};
}
```

`tsc test.ts -t es2017 -d`

**Expected behavior:** Both should use `keyof ElementTagNameMap`

**Actual behavior:**

```ts
declare var Foo: {
    new (): {
        method<T extends "symbol" | "object" | "track" | "progress" | "a" | "applet" | "area" | "audio" | "base" | "basefont" | "blockquote" | "body" | "br" | "button" | "canvas" | "caption" | "col" | "colgroup" | "data" | "datalist" | "del" | "dir" | "div" | "dl" | "embed" | "fieldset" | "font" | "form" | "frame" | "frameset" | "h1" | "h2" | "h3" | "h4" | "h5" | "h6" | "head" | "hr" | "html" | "iframe" | "img" | "input" | "ins" | "isindex" | "label" | "legend" | "li" | "link" | "listing" | "map" | "marquee" | "menu" | "meta" | "meter" | "nextid" | "ol" | "optgroup" | "option" | "output" | "p" | "param" | "picture" | "pre" | "q" | "script" | "select" | "source" | "span" | "style" | "table" | "tbody" | "td" | "template" | "textarea" | "tfoot" | "th" | "thead" | "time" | "title" | "tr" | "ul" | "video" | "x-ms-webview" | "xmp" | "circle" | "defs" | "desc" | "ellipse" | "filter" | "g" | "image" | "line" | "marker" | "mask" | "path" | "metadata" | "pattern" | "polygon" | "polyline" | "rect" | "svg" | "stop" | "switch" | "tspan" | "text" | "use" | "view" | "abbr" | "acronym" | "address" | "article" | "aside" | "b" | "bdo" | "big" | "center" | "cite" | "clippath" | "code" | "dd" | "dfn" | "dt" | "em" | "feblend" | "fecolormatrix" | "fecomponenttransfer" | "fecomposite" | "feconvolvematrix" | "fediffuselighting" | "fedisplacementmap" | "fedistantlight" | "feflood" | "fefunca" | "fefuncb" | "fefuncg" | "fefuncr" | "fegaussianblur" | "feimage" | "femerge" | "femergenode" | "femorphology" | "feoffset" | "fepointlight" | "fespecularlighting" | "fespotlight" | "fetile" | "feturbulence" | "figcaption" | "figure" | "footer" | "foreignobject" | "header" | "hgroup" | "i" | "kbd" | "keygen" | "lineargradient" | "mark" | "nav" | "nobr" | "noframes" | "noscript" | "plaintext" | "radialgradient" | "rt" | "ruby" | "s" | "samp" | "section" | "small" | "strike" | "strong" | "sub" | "sup" | "textpath" | "tt" | "u" | "var" | "wbr">(): void;
    };
};
declare class Bar {
    method<T extends keyof ElementTagNameMap>(): void;
}
```
Repository: rust
Issue: GDB pretty printers incorrectly print Path slices
Labels: A-debuginfo,T-compiler,C-bug

Given this source file:

```rust
use std::path::Path;

fn main() {
    let a = Path::new("a/b");
    let b = a.parent().unwrap();
    let c = "a/b";
    let d = &c[..1];

    let e = 3;
}
```

When compiled and run through `rust-gdb` it yields:

```
$ rustc -g foo.rs
$ cat cmds
break foo.rs:9
run
print *a
print *b
print c
print d
quit
$ rust-gdb ./foo -x cmds
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./foo...done.
Breakpoint 1 at 0x7c8c: file /home/alex/code/cargo/foo.rs, line 9.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, foo::main () at /home/alex/code/cargo/foo.rs:9
9	    let e = 3;
$1 = Path = {inner = OsStr = {inner = Slice = {inner = 0x555555590c80 <str> "a/b"}}}
$2 = Path = {inner = OsStr = {inner = Slice = {inner = 0x555555590c80 <str> "a/b"}}}
$3 = "a/b"
$4 = "a"
A debugging session is active.

	Inferior 1 [process 31595] will be killed.

Quit anyway? (y or n) [answered Y; input not from terminal]
```

The variable `b` was printed as `a/b` instead of `a`, although string slices appear to work!
Repository: go
Issue: x/build/maintner: store Github pull request data
Labels: Builders

If we want this to be a tool for wider use (and I think it would be good to do that), we need to store Github pull request data for projects.

Furthermore, we currently get Git commits from Gerrit CL's, we'll need to allow people to specify Github as their primary Git upstream and fetch commits from Github instead of Gerrit, and also to read some of the metadata from Github's API that we currently parse out of the Git commits in Gerrit.
Repository: go
Issue: x/build/maintner: load tokens from XDG config dir
Labels: Builders

Right now we hardcode the file to get Github tokens from as `$HOME/.github-issue-token`. If a user has XDG_CONFIG_HOME specified we should try to load tokens from there too.
Repository: go
Issue: x/build: rewrite Hg hashes in issue tracker
Labels: help wanted,Builders,NeedsFix

Some old issues refer to mercurial hashes in their issue tracker. There is a mapping at https://golang.org/change/XXXXX and the git commits have this data too (as a golang-hg header in the commit), but if you don't know that it can be hard to track down. 

Instead of people having to know this, one could rewrite all codesite URLs in the issue tracker to become googlesource.com URLs.

example:  https://github.com/golang/go/issues/2516 mentions http://code.google.com/p/go/source/detail?r=4e38cad33649.