sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/compile: don't copy static array in range statement
Labels: Performance,NeedsFix,early-in-cycle

```
func f() {
    for _, b := range [...]byte{1, 2, 3, 4, 5, 6, 7, 8, 9, 10} {
        println(b)
    }
}
```

The compiled code starts off with copying the static array to the stack, then using the stack copy to do the iteration.  The static data is read-only, we could use the static data directly.

```
    0x0013 00019 (tmp1.go:4)    MOVQ    "".statictmp_1(SB), AX
    0x001a 00026 (tmp1.go:4)    MOVQ    "".statictmp_1+2(SB), CX
    0x0021 00033 (tmp1.go:4)    MOVQ    AX, "".autotmp_3+30(SP)
    0x0026 00038 (tmp1.go:4)    MOVQ    CX, "".autotmp_3+32(SP)
    0x002b 00043 (tmp1.go:4)    MOVQ    $0, AX
    0x002d 00045 (tmp1.go:4)    LEAQ    "".autotmp_3+30(SP), CX
    ...use CX to load the bytes...
```
Repository: rust
Issue: Weird integer inference failure
Labels: A-type-system,T-compiler,A-inference,C-bug,T-types

``` rust
const K: u64 = 8;
const P0: [u64; 6] = [2, 3, 7, 9, 10, 14];

fn main() {
    let mut ps = Vec::from(&P0 as &[_]);
    // Fixup P0 if necessary.
    for p in &mut ps {
        if *p == K {
            if *p == 2 || *p == 9 {
                *p -= 1;
            } else {
                *p += 1;
            }
        }
    }
    println!("{:?}", ps);
}
```

fails to compile, despite compiler figuring out that `ps: Vec<u64>`, but explicit annotation of the vector type is necessary for integers to be inferred correctly:

```
…
    // either works
    let mut ps: Vec<u64> = Vec::from(&P0 as &[_]);
    let mut ps = Vec::from(&P0 as &[u64]);
…
```

I would expect all the code snippets to be equivalent and compile.
Repository: vscode
Issue: [css/less/scss] var should be a suggestion in intellisense
Labels: feature-request,css-less-scss

#6656

CSS

![image](https://cloud.githubusercontent.com/assets/2193314/15514746/71e0cde6-219f-11e6-87d6-93248b160ffb.png)

Sass

![image](https://cloud.githubusercontent.com/assets/2193314/15514735/60b93152-219f-11e6-8160-2fa520763423.png)

Less

![image](https://cloud.githubusercontent.com/assets/2193314/15514763/83fb48bc-219f-11e6-876e-35c41f0bf489.png)
Repository: vscode
Issue: [css] show all variable definitions for Go To definition
Labels: feature-request,css-less-scss

In this example, the variable has 3 definitions:

![image](https://cloud.githubusercontent.com/assets/2193314/15515198/d4f68c8e-21a1-11e6-99b4-5a28395190af.png)
Repository: vscode
Issue: Auto closing brackets should try to balance brackets
Labels: feature-request,editor-autoclosing

- VSCode Version: 1.1.0-alpha
- OS Version: Windows 10

Steps to Reproduce:
1. Open launch.json or create one
2. Delete the opening bracket { under configurations
3. Re-type the opening bracket

Auto-complete adds in a closing bracket when the closing bracket at the end of the config is showing an error. It would make sense that bracket auto-complete would know that there is an open bracket and to not add the closing bracket at the top.
Repository: flutter
Issue: RenderIntrinsicHeight should be more graceful when its child has an infinite intrinsic height
Labels: c: new feature,c: crash,framework,a: error message,P3,team-framework,triaged-framework

Specifically, it should complain that that's a violation of the intrinsic height protocol, and try to pin point which class messed up.

(ditto widths)
Repository: youtube-dl
Issue: Randomly select an available IP address for --source-address (was: ipv6 selection)
Labels: request

I see there is an option --force-ipv6 to use ipv6, does it choose a random ipv6 ip from my range ?

Thanks!
Repository: TypeScript
Issue: Some comments are removed
Labels: Bug,Help Wanted

**TypeScript Version:** 

1.7.5

**Code**

```
export function lex(source: string): Array<string>
{//validation and tokenization
}
```

``` ts
// A self-contained demonstration of the problem follows...

The comment after the beginning curly brace is discarded.

```

**Expected behavior:**

After being compiled the comment is not discarded.

**Actual behavior:** 
The comment _is_ discarded.
Repository: nvm
Issue: Installing on Alpine Linux
Labels: installing node,feature requests

Hi

First off, thanks for NVM - I use it frequently and see it being used everywhere and it's been great. To that end, I'd really like to use NVM on my current project which is basically a CI running via Docker - i'd like to be able to use Alpine Linux as the base image.

I can get NVM to install on Alpine by doing:

```
apk add bash
wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.31.1/install.sh | bash
```

Which is great. But then the resulting Node binary won't run and I believe from doing a little reading that this is likely to be because Alpine needs musl rather than GCC built binaries. 

I tried using the `-s` flag in `nvm install` but that tells me it is not usable for Node > 1.

I see Alpine and other busybox-based distros gaining a lot of traction as they're so fast, perfect for containerised use - hence my interest.

So my question is...Do you think the above is correct and if so (or if similar), can I offer help in perhaps providing Alpine-compatible binaries? I can perhaps script a compilation of all the existing versions of Node source - though it'd take some time to run - then upload them somewhere e.g. S3.

If the above is of any interest, please let me know as I am keen to help wherever necessary.

Cheers
Neil
Repository: TypeScript
Issue: DefinitionResponse selects full type range
Labels: Suggestion,Help Wanted,API

When sending a `definition` request to the tsserver, the response contains a range selection of the whole type. For UX proposes it would be better to either select only the identifying portion, like a type name, or additional include such an identifying range.

See https://github.com/Microsoft/vscode/issues/6772 for some background.
Repository: opencv
Issue: Opencv3 / C-API: Undefined *VERSION*  macros
Labels: wontfix

### Please state the information for your system
- OpenCV version: 3.1 and also dev version
- Host OS: Linux (Ubuntu 16.04-64 bits)
- Compiler & CMake: GCC 5.3.1 & CMake 3.5.1
### In which part of the OpenCV library you got the issue?

Opencv3 C-API doesn't defines CV_*_VERSION 
### Expected behaviour

ALL CV_*_VERSION macros should be defined
### Actual behaviour

Compilation error:

```
main.c: In function ‘main’:
main.c:5:17: error: ‘CV_MAJOR_VERSION’ undeclared (first use in this function)
   printf("%d\n",CV_MAJOR_VERSION);
```
### Code example to reproduce the issue / Steps to reproduce the issue

Please try to give a full example which will compile as is.

```
#include <stdio.h>
#include "opencv/cv.h"
int main()
{
    printf("version %d\n", CV_MAJOR_VERSION);
    )return 0;
}
```

Compilation line:

```
gcc -Wall main.c -o main -I/usr/local/include/opencv -I/usr/local/include -L/usr/local/lib  -lopencv_imgproc -lopencv_core -lm
```
Repository: rust
Issue: "Unexpected end of macro invocation" error in nested macro has misleading span, doesn't specify which macro
Labels: C-enhancement,A-diagnostics,A-macros,T-compiler

The following code (based on a test case by @apoelstra):

``` rust
macro_rules! check_enum {
    ($e:ident, $($var:ident),*) => ({
        $(assert_eq!(0 == $e::$var);)*
    })
}

fn main() {
    check_enum!(Foo, Bar, Baz);
}
```

generates this error message:

```
error: unexpected end of macro invocation
 --> test.rs:9:25
9 |>     check_enum!(Foo, Bar, Baz);
  |>                         ^
```

The problem is that `assert_eq!` is expecting a comma.  This is very hard to decipher though, because the span points to the outer macro invocation.  (This may be related to #26615.)  If a better span can't be found, it would be useful to at least include the name of the macro in the error message, e.g. "unepected end of `assert_eq!` invocation."
Repository: TypeScript
Issue: TypeScript's ecosystem of self-bundled typings does not work with npm
Labels: Suggestion,Needs Proposal

When npm dependencies have same packages of different versions, tsc throws duplicate identifier errors. TypeScript's ecosystem of packages is weaker than npm, and does not have compatibility with npm. I believe this is a large problem. And this will be a popular problem because npm always install an exact version in resolving dependencies. For example, when depending `a@^0.0.2` and `a@^0.0.1` as another package's dependency, its project has `a@0.0.1` and `a@0.0.2`. npm can resolve these different versions, but TypeScript cannot. 

**TypeScript Version:** 

1.9.0-dev.20160526
Repository: go
Issue: runtime: pprof should report non-heap memory
Labels: NeedsFix,FeatureRequest,compiler/runtime

pprof currently only reports heap-allocated memory. However, pprof is meant to help with debugging memory footprint and sometimes an application's memory footprint comes from non-heap sources, such as stacks or GC memory (the latter usually indicates a bug such as #15319, but it's currently hard to track down such bugs).

Hence, pprof should report the other sources of memory footprint somehow, such as showing them as isolated boxes or simply showing them in the info box. This information is already recorded in profiles, though it's in "comments".
Repository: electron
Issue: CSS cursor not honored when element in header with titleBarStyle="hidden"
Labels: platform/macOS,bug :beetle:

If you place an element with a css cursor style at the top of the page where the title bar would be with titleBarStyle="hidden", the cursor always displays as default.  A simple example would be a link.
Repository: angular
Issue: [feat] Take advantage of passive event listeners
Labels: feature,state: Needs Design,area: core,hotlist: google,core: event listeners,feature: under consideration

/ref https://github.com/WICG/EventListenerOptions

It's a way to declare that `preventDefault()` is not called by handler and make scrolling smoother.

Needs more investigation if support would be useful in Angular.
Repository: opencv
Issue: Wrong Documentation for cvtColor on HSV_FULL variants
Labels: feature,category: documentation

Documentation says that RGB2HSV conversion gives the H channel between 0 and 180 and RGB2HSV_FULL gives H channel between 0 and 360. This confuses people because they think that for 8-bit images they need to convert to 16-bit or 32F before converting to HSV_FULL in order to to make room for the >255 values. I had to look at the code to discover that HSV_FULL variants produces H channel between 0 and 255 instead.
Repository: kubernetes
Issue: Speed up getting pod statuses in PLEG when there are many changes
Labels: priority/backlog,area/kubelet,sig/scalability,sig/node,kind/feature,lifecycle/frozen,needs-triage

Forked from https://github.com/kubernetes/kubernetes/issues/23591#issuecomment-203042820
Creating a new issue so I won't forget.

PLEG serially gets status for every pod, where at least one container has encountered a state transition. This becomes the bottleneck if a lot of containers changed in one relist period. We were aware of this problem and had come up with a few options before:
1. Add a new GetPodStatus variant to bypass the `docker ps -a` call since pleg already have this information. The downside is that this is a very docker-specific optimization and doesn't make sense for other runtimes.
2. Parallelize the process.
3. Do nothing. Assume docker is busy and process slowly.

I think we can do (2) with a small number of goroutines (e.g., 2) to speed up the time.
Repository: go
Issue: runtime: unexpected fault address 0xffffffffffffffff (and other more innocent addresses)
Labels: compiler/runtime

After updating the go version from 1.5.1 to 1.6.2 our application crashed right after startup in production. 
We run it with start-stop-daemon and use the '-u' flag to change the user. This is relevant because changing this to sudo-ing the start-stop-daemon to the user instead of using the flag the crash vanished. We figured this out trough experimentation.

```
# this crashes
start-stop-daemon -u user --start golang-cool-api-v2000 
```

```
# this doesn't crash
sudo -u user start-stop-daemon --start golang-cool-api-v2000 
```
1. What version of Go are you using (`go version`)?
   1.6.2
2. What operating system and processor architecture are you using (`go env`)?
   Linux 3.2.12-gentoo 64bit
3. What did you do?
   Update to golang 1.6.2 from 1.5.1
4. What did you expect to see?
   No difference :)
5. What did you see instead?

```
unexpected fault address 0xffffffffffffffff
fatal error: fault
[signal 0xb code=0x1 addr=0xffffffffffffffff pc=0xffffffffffffffff]

goroutine 19 [running]:
runtime.throw(0x9a3280, 0x5)
        /usr/local/go/src/runtime/panic.go:547 +0x90 fp=0xc82002aed8 sp=0xc82002aec0
runtime.sigpanic()
        /usr/local/go/src/runtime/sigpanic_unix.go:27 +0x2ab fp=0xc82002af28 sp=0xc82002aed8
runtime.call32(0x0, 0xc820109d20, 0xc820bea000, 0x1000000010)
        /usr/local/go/src/runtime/asm_amd64.s:472 +0x3e fp=0xc82002af50 sp=0xc82002af28
runtime.runfinq()
        /usr/local/go/src/runtime/mfinal.go:200 +0x299 fp=0xc82002afc0 sp=0xc82002af50
runtime.goexit()
        /usr/local/go/src/runtime/asm_amd64.s:1998 +0x1 fp=0xc82002afc8 sp=0xc82002afc0
created by runtime.createfing
        /usr/local/go/src/runtime/mfinal.go:139 +0x60
```

the address isn't the same between crashes

```
unexpected fault address 0xc8206fdd4a
fatal error: fault
[signal 0xb code=0x2 addr=0xc8206fdd4a pc=0xc8206fdd4a]

goroutine 18 [running]:
runtime.throw(0x9a3280, 0x5)
        /usr/local/go/src/runtime/panic.go:547 +0x90 fp=0xc82002e6d8 sp=0xc82002e6c0
runtime.sigpanic()
        /usr/local/go/src/runtime/sigpanic_unix.go:27 +0x2ab fp=0xc82002e728 sp=0xc82002e6d8
runtime.call32(0x0, 0xc820c4a040, 0xc820c5c000, 0x1000000010)
        /usr/local/go/src/runtime/asm_amd64.s:472 +0x3e fp=0xc82002e750 sp=0xc82002e728
runtime.runfinq()
        /usr/local/go/src/runtime/mfinal.go:200 +0x299 fp=0xc82002e7c0 sp=0xc82002e750
runtime.goexit()
        /usr/local/go/src/runtime/asm_amd64.s:1998 +0x1 fp=0xc82002e7c8 sp=0xc82002e7c0
created by runtime.createfing
        /usr/local/go/src/runtime/mfinal.go:139 +0x60
```

This stacktrace doesn't contain any relevant information for me. All the stackframes of the other goroutines don't seem the same between crashes.
 It might be relevant (given the mfina.go in the stack) that this happened two times after the 9th gc and once after the 7th gc (GODEBUG="gctrace=2" is set)
Repository: go
Issue: cmd/link: GOARM=7 output has no ARM attribute section, confusing readelf
Labels: NeedsFix,compiler/runtime

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

Go 1.6
#2. What operating system and processor architecture are you using (`go env`)?

GOOS=android \
GOARCH=arm \
CC=$GOMOBILE/android-ndk-r10e/arm/bin/arm-linux-androideabi-gcc \
CXX=$GOMOBILE/android-ndk-r10e/arm/bin/arm-linux-androideabi-g++ \
CGO_ENABLED=1 \
GOARM=7 \
go build -p=4 -pkgdir=$GOMOBILE/pkg_android_arm -tags="" -v -x -i -gcflags=-shared -ldflags=-shared \
-buildmode=c-shared
1. What did you do?
   If possible, provide a recipe for reproducing the error.
   A complete runnable program is good.
   # A link on play.golang.org is best.
   
   Any gomobile build or bind can reproduce it.
#4. What did you expect to see?

when use “arm-linux-androideabi-readelf -A xxx.so” cmd, I hope something like this

Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "**ARM v7**"
  Tag_CPU_arch: **v7**
  Tag_CPU_arch_profile: Application
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-2
  Tag_FP_arch: VFPv3-D16
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_enum_size: int
  Tag_ABI_HardFP_use: SP and DP
  Tag_ABI_optimization_goals: Aggressive Speed
  Tag_CPU_unaligned_access: v6
  Tag_DIV_use: Not allowed
#5. What did you see instead?

But output like this：

Attribute Section: aeabi
File Attributes
  Tag_CPU_name: "**5TE**"
  Tag_CPU_arch: **v5TE**
  Tag_ARM_ISA_use: Yes
  Tag_THUMB_ISA_use: Thumb-1
  Tag_FP_arch: VFPv2
  Tag_ABI_PCS_wchar_t: 4
  Tag_ABI_FP_denormal: Needed
  Tag_ABI_FP_exceptions: Needed
  Tag_ABI_FP_number_model: IEEE 754
  Tag_ABI_align_needed: 8-byte
  Tag_ABI_enum_size: int
  Tag_ABI_optimization_goals: Aggressive Speed

which much like a **armv5te** so file...
Repository: youtube-dl
Issue: Site Request: Deadspin.com
Labels: site-support-request

## Please follow the guide below
- You will be asked some questions and requested to provide some information, please read them **carefully** and answer honestly
- Put an `x` into all the boxes [ ] relevant to your _issue_ (like that [x])
- Use _Preview_ tab to see how your issue will actually look like

---
### Make sure you are using the _latest_ version: run `youtube-dl --version` and ensure your version is _2016.05.21.2_. 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.05.21.2**
### Before submitting an _issue_ make sure you have:
- [X ] At least skimmed through [README](https://github.com/rg3/youtube-dl/blob/master/README.md) and **most notably** [FAQ](https://github.com/rg3/youtube-dl#faq) and [BUGS](https://github.com/rg3/youtube-dl#bugs) sections
- [X ] [Searched](https://github.com/rg3/youtube-dl/search?type=Issues) the bugtracker for similar issues including closed ones
### What is the purpose of your _issue_?
- [ ] Bug report (encountered problems with youtube-dl)
- [X ] Site support request (request for adding support for a new site)
- [ ] Feature request (request for a new functionality)
- [ ] Question
- [ ] Other

---

---
### 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**):
- http://fittish.deadspin.com/pro-cyclist-crashes-spectacularly-into-snowbank-costs-1779152408
- http://theconcourse.deadspin.com/bear-catches-belly-rays-1779158981
- http://deadspin.com/russell-westbrook-tells-us-how-he-really-feels-about-st-1779124655
- Playlist: n/a

---

Thanks
Ringo
Repository: rust
Issue: Unable to achieve aligned writes
Labels: A-LLVM,I-slow,C-enhancement,T-compiler

I am trying to implement an efficient memory move operation for a specific usage pattern: https://play.rust-lang.org/?gist=6ddd4e11d7f7b0f6503ddd398f0e665f&version=nightly&backtrace=1

In release mode, the loop in move_items() in the above example is compiled into a series of unaligned reads followed by unaligned writes, despite my efforts to have the writes aligned.
Repository: opencv
Issue: Make python binding generator more generic
Labels: feature,category: python bindings

The current python binding generator gen2.py makes a great job for creating python bindings of the core opencv library. Unfortunately it fails to help in the creation of third party library python bindings that link to the python opencv library. An example of a such a third party library that would benifit from a python binding is http://opencvblobslib.github.io/opencvblobslib/ .

There are two issues involved:
- 1. The python binding generator does not create .h files that a third party library can use. E.g. lets say that we have a library Foo wrapped into the python module PyFoo. We also have a library Bar with a python module PyBar(). For PyBar to access PyFoo, we need an h-file similar to the below. This allows a third party both to receive and decompose python objects as well as constructing new ones as return values.

```
#ifndef PYFOO_H
#define PYFOO_H

#include <Python.h>
#include <Foo.h>

PyObject *PyFoo_FromFoo(Foo foo);

typedef struct {
    PyObject_HEAD;
    Foo *foo;
} PyFoo;

#define PyFoo_Check(op) \
    PyObject_TypeCheck(op, &PyFooType)

extern PyTypeObject PyFooType;
#endif
```

(This corresponds to the `pyopencv_from()` and `pyopencv_to()` functions that need to be made visible in the h-files. I'm not sure that I like the idea of having public API that rely on template instantiated functions. Why not just create a mangled name that contains the type of the from and to?)
- 2. Make `gen2.py` able to generate modules with a user chosen module name. This involved adding command line parameters for lots of hardwired module names in gen2.
Repository: youtube-dl
Issue: [Podbay.fm] Support show pages
Labels: site-support-request

Successfully used youtube-dl on podbay.fm to download .mp3s. 

example show link: http://podbay.fm/show/507135865
example mp3 link: http://podbay.fm/show/507135865/e/1463976000?autostart=1

`[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-v']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2016.02.22
[debug] Python version 2.7.11+ - Linux-4.4.0-22-generic-x86_64-with-Ubuntu-16.04-xenial
[debug] exe versions: avconv 2.8.6-1ubuntu2, avprobe 2.8.6-1ubuntu2, ffmpeg 2.8.6-1ubuntu2, ffprobe 2.8.6-1ubuntu2, rtmpdump 2.4
[debug] Proxy map: {}`
Repository: rust
Issue: Trailing semicolon silently ignored in expr macro
Labels: A-macros,C-bug

```
fn main() {
    macro_rules! a {
        ($e:expr) => { $e; }
    }
    a!(true)
}
```

Error: Expected `()`, found `bool`

But:

```
fn main() {
    macro_rules! a {
        ($e:expr) => { $e; }
    }
    a!(true);  // <-- semicolon
}
```

does not warn that the `;` is ignored.

So either
- there should be a warning that the `;` has no effect in the macro, or
- the `;` inside the macro should turn the expression into `()`.
Repository: youtube-dl
Issue: pluralsight "skill"
Labels: request,account-needed

It would be awesome if also the "skills" url could be grabbed

The "skills" are a group of courses.

Link sample https://app.pluralsight.com/paths/skill/docker
Repository: rust
Issue: Cannot create function reference with parameters that don't have to outlive the functions lifetime
Labels: A-lifetimes,C-bug,T-types

List of things tried (that I remember):
- Using the same lifetime for both the closure reference and it's parameters renders the reference uncallable: https://is.gd/CpXw0w
- Using different lifetimes for the closure reference and it's parameters fails to compile, since the parameters must _outlive_ the closure itself: https://is.gd/q5mJly
- Using [Higher-Rank Trait Bounds](https://doc.rust-lang.org/nomicon/hrtb.html) works, but is infeasible since it requires the parameter references types to be defined directly where the closure reference itself is defined: https://is.gd/genxSf

Since anything is better than `unsafe { transmute(parameter_reference) }`, I'd appreciate any comments on how to properly implement this.