sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/mobile/exp/audio: audio is choppy on Moto X running Android 5.1
Labels: mobile

Steps to reproduce:

1) go install golang.org/x/mobile/example/audio (for a Moto X device running Android 5.1)
2) Run the audio demo on the device

Expected result:

Audio sounds the same as when the audio demo is run on a desktop machine

Observed result:

Audio playback is very "choppy." Getting random pops in the middle and end of the audio sample as the gopher bounces off the walls.
Repository: go
Issue: runtime: Additional Allocator Metrics in `runtime.MemStats`
Labels: compiler/runtime

Hi, I am wondering if it would be amenable to include several additional core metrics in `runtime.MemStats`, namely the following measures:
1. No. of spans pending being released by size class.
   
   This helps server authors understand the discrepancy between reported
   heap reservation/allocation versus process RSS.
2. No. of live spans (with active allocations contained therein) by size class.
   
   Essential corollary for no. 1.
3. Measure of sum of span occupancy by size class.
   
   This helps server and runtime authors understand level of span reuse
   and divine potential problems with heap fragmentation viz-a-viz no. 2.
4. Sum of span allocations by size class (not of inner object allocations).
   
   This helps server authors understand the aggregate throughput of
   memory flow in realtime, a measure of efficiency that is useful to
   capture when comparing releases and automated canary tests.
5. Sum of span releases by size class (not of inner object allocations).
   
   Useful corollary for no. 4.
6. Summary statistics about age for spans by size classes: min, median, average, max.
   
   Throughput in no. 4 and no. 5 is useful, but this takes the level of detail to a
   deeper level.
7. Cumulative sums of individual allocations made for each span size class.
   
   Useful throughput measure for individual allocations.

These would be inordinately beneficial in gross measurement of fleet memory allocator performance as well as offer server authors deeper telemetric insights into the lifecycles of their allocations.  pprof is great for one-off diagnosis but not real-time analytics of the fleet.

I would be happy coming to compromise on these, especially to enhance the language and requirements as well as to possibly volunteer time in the implementation of these representations should we come to agreement.
Repository: TypeScript
Issue: Handle default constructor when extending null
Labels: Bug

From this [comment](https://github.com/Microsoft/TypeScript/issues/3696#issuecomment-122143431), and [bug](https://bugs.ecmascript.org/show_bug.cgi?id=4429.) we would like to provide appropriate handling for the following case: 

``` typescript
class N extends null {}
var n = new N(); 
```

Depended on how ES6 spec handles above case (i.e. fix the calling to `super` or just leave it as is), we will have to make appropriate change into our emitted ES5 and ES6.

If default constructor will not call `super` when extends null,in ES5 we should change our following emitted JS:

``` typescript
// When no constructor is defined:
_super && _super.apply(this, arguments);

// In the presence of an explicit 'super(arg1, arg2, ..., argN)' call:
_super && _super.call(this, arg1, arg2, ... argN);
```

If default contructor will call `super`, we should give an error for not having explicit constructor and possibly leave down-level emitted js as is
Repository: TypeScript
Issue: Variable merging
Labels: Suggestion,Needs Proposal

```
declare var test: (s: string) => void;

declare var test: {
    (s: string) => void;
    tests: any[];
}
```

At the moment TS compiler shows error: `Subsequent variable declarations must have the same type.`
Repository: opencv
Issue: VideoCapture fails when compiled with FFMPEG > 1.2.12 (OpenCV 2.4.11)
Labels: bug,priority: low,category: videoio,affected: 2.4

I'm working with Hollywood-2 video dataset, an example video `actioncliptrain00002.avi` is at my OneDrive: http://1drv.ms/1Mxprmh.

I do sth like:

``` c++
#include <cstdio>
#include <opencv2/highgui/highgui.hpp>

int main()
{
    cv::VideoCapture in("actioncliptrain00002.avi");
    cv::Mat frame;
    for(int i = 1; ; i++)
    {
        bool ok = in.read(frame);
        printf("%d: ok = %s, rows = %d, cols = %d\n", i, ok ? "true" : "false", frame.rows, frame.cols);

        if(!ok)
        {
            printf("Not ok. Breaking.\n");
            break;
        }
    }
}

```

If compiled with ffmpeg 1.2.12, it outputs:

```
1: ok = true, rows = 224, cols = 528
2: ok = true, rows = 224, cols = 528
............
241: ok = true, rows = 224, cols = 528
242: ok = false, rows = 0, cols = 528
Not ok. Breaking.
```

If compiled with any ffmpeg >= 2.0.7 (including the latest 2.7.2), it outputs:

```
[mpeg4 @ 0x169ce40] header damaged
[mpeg4 @ 0x16ded60] Context scratch buffers could not be allocated due to unknown size.
<more ffmpeg errors just like above>
1: ok = false, rows = 0, cols = 0
Not ok. Breaking.
```

My OpenCV/ffmpeg installation script is here: http://pastebin.com/KD4YWpg5

Both ffmpeg 1.2.12 and 2.7.2 are able to do `ffmpeg -i actioncliptrain00002.avi dump/%06d.png` without any errors, which makes me think it's an OpenCV bug in the way it talks to ffmpeg. I have a stable reproducing setup and am happy to provide any further information or help, if needed.

The full Hollywood-2 video dataset is available at ftp://ftp.irisa.fr/local/vistas/actions/Hollywood2-actions.tar.gz
Repository: opencv
Issue: Bayer VNG Pixel Offset
Labels: bug,category: imgproc,priority: low

It appears that the VNG Bayer demosaicing will create a vertical pixel offset in the output imagery.  I have tested the output of all three available algorithms; linear, VNG, and EA.  Only VNG appears to have this problem.

Source Bayer image
![source_crop](https://cloud.githubusercontent.com/assets/13557093/8960618/cde7f6bc-35de-11e5-91c1-874f354bbf6a.png)

Result from COLOR_BAYER_GB2BGR_VNG
![debayer_vng_crop](https://cloud.githubusercontent.com/assets/13557093/8960640/edc7561c-35de-11e5-8ff4-f541ed94a1cf.png)

Difference showing vertical offset
![diff_src_vng](https://cloud.githubusercontent.com/assets/13557093/8960670/1801932a-35df-11e5-8f75-0834e88b09cd.png)
Repository: youtube-dl
Issue: Restart download on error
Labels: request

I usually pipe youtube-dl output to mplayer like this: `./youtube-dl -q -o- https://www.youtube.com/watch?v=... | mplayer -` and sometimes I get this error:

```
ERROR: unable to download video data: [Errno 104] Connection reset by peer
```

After this the download it aborted and I only can continue from the beginning.
It would be great if youtube-dl on fail would try to restart download from the position where it failed before exiting with error message.
Repository: youtube-dl
Issue: Paper cut: Downloading audio - output has media dependant strings
Labels: request

Just a minor paper cut:

So i downloaded some audio only content and saw:

```
[soundcloud:user] irllink: Downloading track page 1
[soundcloud:user] irllink: Downloading track page 2
[soundcloud:user] irllink: End page received
[download] Downloading playlist: irllink
[soundcloud:user] playlist irllink: Collected 21 video ids (downloading 21 of them)
[download] Downloading video 1 of 21
[soundcloud] irllink/take-it-easy: Resolving id
[soundcloud] irllink/take-it-easy: Downloading info JSON
[soundcloud] 216455131: Downloading track url
[soundcloud] 216455131: Checking download video format URL
[soundcloud] 216455131: Checking http_mp3_128_url video format URL
[download] Destination: Take It Easy!-216455131.mp3
[download] 100% of 6.35MiB in 00:12
```

> "Collected 21 video ids" 

and 

> "Checking download video format URL"

So youtube talks about videos when all it is handling is audio. I don't know if there is an easy way to make it site depended. But the easy way is probably to use a media independent word. Like "media":

> Collected 21 media ids
> "Checking download media format URL"

I am sure there are much better solutions. I would like to hear your ideas. :)
Repository: javascript
Issue: `if` statements – one line vs. one expression
Labels: question,needs eslint rule change/addition

Until I started using ESLint with your configuration I saw nothing against the rules in this:

``` js
$ cat if.js
const [one, two] = [1, 2];

if (one !== two) throw new Error(
  'One does not equal two'
);
```

But ESLint does:

``` sh
$ eslint if.js 

if.js
  3:0  error  Expected { after 'if' condition  curly

✖ 1 problem (1 error, 0 warnings)
```

Is this intended? In my opinion the pattern I’ve been using is explicit – and more readable than this:

``` js
if (one !== two) {
  throw new Error(
    'One does not equal two'
  );
}
```

The parens form a visual brace-like block much like in #438.
Repository: neovim
Issue: $NVIM, v:parent
Labels: enhancement,job-control,terminal,channels-rpc

It'd be super cool if Neovim could keep track of whether you're in a terminal or not, and when you _are_ in a terminal change the meaning of the terminal escape sequence (`<c-\><c-n>`) so that it exits from a terminal that you've spawned inside of a child Neovim instance. So, waste deep in Neovims, you'd always be able to escape from the current Neovim terminal with a single escape; always just `<c-\><c-n>` instead of `<c-\><c-\><c-n>` or `<c-\><c-\><c-\><c-n>` or `<c-\><c-\><c-\><c-\><c-n>`.

This would match perfectly with the fact that you can already `-- INSERT --` your way into child Neovims with single strokes of `i`. Navigating in _both_ directions would become extremely easy.

The workflow improvement would be massive.
Repository: javascript
Issue: Consider allowing anonymous function expressions
Labels: question,pull request wanted,needs eslint rule change/addition

At the moment [you forbid](https://github.com/airbnb/javascript/blob/ea093e0373cc4dfa07c69ef7c75d81bd06bdf0c2/packages/eslint-config-airbnb/.eslintrc#L140) unnamed function expressions like `function() {}`. That’s a good thing.

But when using the new function bind syntax with **[trine](https://github.com/jussi-kalliokoski/trine)**-style [libraries](https://github.com/roobie/mori-ext), you can’t use arrow functions because they inherit `this` from the outer scope.

So a good old anonymous function expression:

``` js
[my, collection]::map(function() {
  return !!this;
});
```

…often feels more natural than inventing obscure names:

``` js
[my, collection]::map(function justCastToBoolean() {
  return !!this;
});
```
Repository: kubernetes
Issue: Make sure to warn the user that apiserver won't listen when etcd is screwed up
Labels: area/apiserver,priority/awaiting-more-evidence,sig/api-machinery,lifecycle/frozen

As see in #12085.
Repository: rust
Issue: Correctly handle dllimport on Windows
Labels: A-linkage,O-windows,P-low,T-lang,T-compiler,C-bug

Currently the compiler makes basically no attempt to correctly use `dllimport`. As a bit of a refresher, the Windows linker requires that if you're importing symbols from a DLL that they're tagged with `dllimport`. This helps wire things up correctly at runtime and link-time. To help us out, though, the linker will patch up a few cases where `dllimport` is missing where it would otherwise be required. If a function in another DLL is linked to without `dllimport` then the linker will inject a local shim which adds a bit of indirection and runtime overhead but allows the crate to link correctly. For importing constants from other DLLs, however, MSVC linker requires that dllimport is annotated correctly. MinGW linkers can sometimes workaround it (see [this commit](https://github.com/llvm/llvm-project/commit/eac1b05f1db91097eb37d975e07789ce039cf7f7) description.

If we're targeting windows, then the compiler currently puts `dllimport` on all imported constants from external crates, regardless of whether it's actually being imported from another crate. We rely on the linker fixing up all imports of functions. This ends up meaning that some crates don't link correctly, however (see this comment: https://github.com/rust-lang/rust/issues/26591#issuecomment-123513631).

We should fix the compiler's handling of dllimport in a few ways:
- Functions should be tagged with `dllimport` where appropriate
- FFI functions should also be tagged with `dllimport` where appropriate
- Constants should not always be tagged with `dllimport` if they're not actually being imported from a DLL.

I currently have a few thoughts running around in my head for fixing this, but nothing seems plausible enough to push on.

EDIT: Updated as @mati865 requested [here](https://github.com/rust-lang/rust/issues/27438#issuecomment-665739234).
Repository: three.js
Issue: Blend Trees
Labels: Enhancement

Unity & Unreal Engine use blend trees to blend between different clips in a realistic way.  Details are here:

https://github.com/mrdoob/three.js/issues/6881#issuecomment-126839845

https://github.com/mrdoob/three.js/issues/6881#issuecomment-126890409

/ping @crobi
Repository: go
Issue: runtime: whole span reclaimer is expensive
Labels: compiler/runtime

Objects larger than 32K are handled by a large object allocator (largeAlloc) because they fall outside the size classes for which there are span caches. Currently, in order to control heap growth, the large object allocator sweeps until it reclaims the number of pages being allocated before performing the allocation (mHeap_Alloc_m -> mHeap_ReclaimList). This path is also taken when growing the heap.

However, this process can be quite expensive. It first tries sweeping large object spans. _If_ this succeeds, the process is fairly efficient; it may require looking at a large number of spans that don't have a free object, but it's not clear if it's possible to eliminate this linear constant. However, empirically, this often fails. This may simply be because earlier large allocations swept spans that were larger than they were allocating and they didn't keep track of this credit. In this case, it falls back to sweeping small object spans until it's able to free enough (potentially non-contiguous) pages that way. As a result of this, in the x/benchmarks garbage benchmark, the large object sweeper winds up sweeping ~30 times more bytes than it's trying to allocate.

I believe we can eliminate this entire mechanism if, during marking, the garbage collector also keeps a per span "super mark" that is set if any objects in the span are marked. At the point where we would set this, we already have the span and, assuming we're willing to dedicate a byte per span for this, it can be set with a blind (possibly even non-temporal) write. At the end of GC, after mark termination, we can immediately free these spans (both large object spans and small object spans with no reachable objects). It takes roughly 1ms per heap GB to walk the span list, so even assuming a little more overhead for adding free spans to span lists, it seems very likely this would take less time than we currently spend sweeping these spans. This is also trivially parallelizable, and we probably have to do this walk anyway (#11484). Additionally, this will reduce load on concurrent sweep and coalesce neighboring spans much earlier, making larger regions of memory available for large object allocation immediately.

This idea is based on various (mostly pairwise) discussions between myself, @RLH, @rsc, and @dvyukov.
Repository: opencv
Issue: OpenCV 3.0: Python Stitcher hangs OSX
Labels: priority: low,affected: 3.4,platform: ios/osx,category: 3rdparty

I installed opencv 3.0.0 with homebrew on Macbook Pro (intel) OSX 10.10.4 Yosemite. When I run the following code:

``` python
imgs = []

for i in range(1,6):
    file = 'stitching_img/S%d.jpg'%i
    print file
    im = cv2.imread(file)
    imgs.append(im)

st=cv2.createStitcher()
ret,pano = st.stitch(imgs)

print 'ret',ret

if ret: cv2.imwrite('pano.png',pano)
```

My entire computer locks up after the 6 images are loaded. I originally did a `cv2.imshow(im)` to ensure the images were loaded correctly and they were. I took it out thinking showing an image was what locked up my system and forcing a reboot, however, that didn't help and I sill had to reboot.
Repository: youtube-dl
Issue: Join multiple audio streams into mkv
Labels: request

Following up on #5784. youtube-dl is currently not capable of downloading-and-merging multiple audio tracks (perhaps even video tracks). It already supports merging into MKV containers on some occassions (e.g. "Requested formats are incompatible for merge and will be merged into mkv."), and so it could just go the same route in case of multi-audio/multi-sub.

```
$ ./youtube-dl -f best+en+jp http://www.gdcvault.com/play/1014631/Classic-Game-Postmortem-PAC
[GDCVault] Classic-Game-Postmortem-PAC: Downloading webpage
[GDCVault] Classic-Game-Postmortem-PAC: Downloading XML
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "./youtube-dl/__main__.py", line 19, in <module>
  File "./youtube-dl/youtube_dl/__init__.py", line 410, in main
  File "./youtube-dl/youtube_dl/__init__.py", line 400, in _real_main
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 1504, in download
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 667, in extract_info
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 713, in process_ie_result
  File "./youtube-dl/youtube_dl/YoutubeDL.py", line 1125, in process_video_result
ValueError: too many values to unpack
```
Repository: youtube-dl
Issue: Download comments from Youtube video
Labels: request

Is there any way to download comments from YouTube videos? Can you add a new option for example: --write-comments  like it with description of video? 
I am first on GitHub, and i am not a programmer, so excuse me if i do something wrong.
I found some information about this request, may be it will be useful:
https://finnaarupnielsen.wordpress.com/2009/09/21/getting-comments-from-youtube-via-pythons-gda/
Repository: go
Issue: x/crypto/ocsp: ParseResponse pitfalls
Labels: NeedsInvestigation

There are two pitfalls in the ParseResponse method of "x/cryto/ocsp". The first being that if you forget to pass in an issuer then the response will be parsed but signature verification will not be performed. The second is that some people might assume that when err != nil, Response.Status == Good. I would suggest an additional idiot proof method VerifyResponse which might look a little like this:

https://play.golang.org/p/eTkpQi_gDk
Repository: go
Issue: runtime: reenable TestCgoCallbackGC on dragonfly
Labels: OS-Dragonfly,NeedsFix,compiler/runtime

For example,

```
go test -v -run=TestCgoCallbackGC
=== RUN   TestCgoCallbackGC
--- PASS: TestCgoCallbackGC (175.54s)
PASS
ok      runtime 175.548s
```

Not sure the reason but it perhaps harms the dragonfly buildbot.
Repository: nvm
Issue: Honor .node-version file
Labels: feature requests

Forgive me if this has been discussed before, but I didn't find anything beyond https://github.com/creationix/nvm/issues/110#issuecomment-40525629.

It would be really nice to see the various Node version managing tools coalesce around a common "version config file", analogous to Ruby's `.ruby-version` for RVM and rbenv - `.node-version`. This would basically just be an alias for `.nvmrc`, since that functionality's already been added. Since `n` already supports `.node-version`, this would make it so that regardless of the Node version manager used, there could be some degree of guarantee that the correct version will be used.
Repository: opencv
Issue: cv::gpu::HoughCircles return different result than cv::HoughCircles (Bugfix #3447) 
Labels: feature,priority: low,affected: 2.4,category: gpu/cuda (contrib)

I noticed not transferred, open issue... (btw. I bet Assignee is my mal)

Should it be here? Is there any bug in transfer method?
http://code.opencv.org/issues/3447

I will prepare example image and someone could explain the difference of measuring diameters with it (maybe I will found time), cause I do not know what type of diff's could it be... First part of task is clear for me, I think. If Łukasz shouldn't do it, I will try.

Regards.
Repository: go
Issue: x/mobile: crash in gobind interface call
Labels: mobile

<b>What version of Go are you using (go version)?</b>

go version go1.5beta2 linux/amd64

gomobile version +99196c8 Sat Aug 1 23:05:44 2015 +0000 (android); androidSDK=/usr/local/android-sdk-linux/platforms/android-22

<b>What operating system and processor architecture are you using?</b>

Development: Linux Mint 64bit / Windows 10 64bit on i7 (920)
Phone: Samsung Galaxy note 4 on ARMv7

<b>What did you do?</b>

Created a simple go library:

![untitled](https://cloud.githubusercontent.com/assets/9334433/9074271/55043e16-3b08-11e5-9f1e-d71f6bf8c96a.png)

Compiled a .arr file : gomobile bind {folder path}

Added the .arr file to an Android Studio project.

![untitled2](https://cloud.githubusercontent.com/assets/9334433/9074136/306c2790-3b07-11e5-8a0c-92708ae391ca.png)
<b>*Red box indicates which method call that crashes the application, during runtime.</b>

<b>What did you expect to see?</b>

The instance of the object getting appended correctly to the Go slice, or to show a stack trace / error message.

<b>What did you see instead?</b>

Passing null as parameter, shows a null value exception. 
However, the example above shuts the application down on my phone completely, with no exception or stack trace, even in debug mode.
Try-catch does not help in this situation.
Repository: kubernetes
Issue: Convert all component command-line flags to versioned configuration
Labels: priority/important-longterm,sig/architecture,lifecycle/frozen

Forked from #1627, #5472, #246, #12201, and other issues.

We configure Kubernetes components like apiserver and controller-manager with command-line flags currently. Every time we change these flags, we break everyone's turnup automation, at least for anything not in our repo: hosted products, other repos, blog posts, ...

OTOH, the scheduler and kubectl read configuration files. We should be treating all configuration similarly, as versioned APIs, with backward compatibility, deprecation policies, documentation, etc. How we distribute the configuration is a separate issue -- #1627.

cc @davidopp @thockin @dchen1107 @lavalamp
Repository: go
Issue: runtime: check indirect calls for nosplit
Labels: NeedsInvestigation

See https://go-review.googlesource.com/#/c/10362/.
Is it needed?
Repository: go
Issue: cmd/gofmt: Inconsistent space before open curly brace
Labels: NeedsDecision

Using go1.5beta3.

This is obviously subjective, so feel free to close.

When struct definition is placed on a single line, it removes the space between the `struct` and `{`.

``` go
type Foo struct {
    int
}

type Bar struct{ int }
```

When an anonymous struct is used and instantiated, it lacks a space before the `{` as well.

``` go
for _, x := range []struct {
    b bool
    n int
}{ // There is NO space between '}' and '{'
    {false, 0},
    {true, 2},
    {false, 16},
} { // There IS a space between '}' and '{'
    fmt.Println(x)
}
```
Repository: go
Issue: x/tools/refactor/rename: fails if cgo build would fail
Labels: Tools,Refactoring

I have some CGO_CFLAGS and CGO_LDFLAGS settings I have to use to build a project I have, but gorename inside emacs doesn't have access to those. 

gorename fails on this project (and ones that depend on it) because it cannot find the C headers. However, gorename doesn't support cgo and so doesn't really need to inspect those headers.

It would be nice for rename to not care about cgo so that we didn't have to mess with cgo's env variables for each project (esp since some might, in rare cases, have conflicting needs).