sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Middle mouse button scrolling
Labels: feature-request,windows,editor-scrollbar

- VSCode Version: 1.10

I searched the issues but did not find any such post, so apologies if there is an existing thread that I missed.

I'd like to know if there is any middle mouse click scrolling, planned? That is, clicking the scroll wheel to toggle drag scrolling. It's a useful feature to have when navigating very long files.

And if it isn't, is there any API that would allow this to be enabled via an extension?

Thanks
Repository: angular
Issue: Testing: wait for async tasks started in ng lifecycle hooks (ex. ngOnInit)
Labels: area: testing

As of today `ComponentFixture::whenStable()` won't pick up async tasks started inside ng2 lifecycle hooks, ex.: `ngOnInit`. There are legitimate cases where async tasks are needed inside lifecycle hooks, ex.: using `ComponentResolver` in `ngOnInit`:

``` javascript
@Directive({
  selector: 'template[ngb-alert]'
})
export class NgbAlertDismissible {
  constructor(private _vcRef: ViewContainerRef, private _tplRef: TemplateRef<any>, private _cr: ComponentResolver, private _injector: Injector) {
  }

  ngOnInit() {
    this._cr.resolveComponent(NgbAlert).then((cf: ComponentFactory<NgbAlert>) => {
      var rootNodes = this._tplRef.createEmbeddedView({}).rootNodes;
      this._vcRef.createComponent(cf, 0, this._injector, [rootNodes]);
    });
  }
}
```

At present the only way to write a test for the above component is to use `setTimout`, while the following should work just fine:

``` javascript
fixture.whenStable().then(() => {
    fixture.detectChanges();
    // do the assertions here...
});
```
Repository: bitcoin
Issue: getchaintips doesn't mark headers-only chain as invalid
Labels: Validation

During headers-first downloading, if an invalid block is found, the client stops syncing that branch, but forever lists it as "headers-only". It seems to me it should be marked as "invalid". This is due to the subsequent headers not being marked "BLOCK_FAILED_CHILD".
Repository: go
Issue: cmd/vet: check for concurrent use of T.FatalX and T.SkipX
Labels: help wanted,Analysis

The `testing` package is explicit about the following:

> A test ends when its Test function returns or calls any of the methods FailNow, Fatal, Fatalf, SkipNow, Skip, or Skipf. Those methods, as well as the Parallel method, must be called only from the goroutine running the Test function.

However, this is easy to overlook and it is not immediately obvious that the code below is a bad test:

``` go
func TestFoo(t *testing.T) {
    go func() {
        t.Fatal("fatal") // Called from outside the Test function
    }()
    time.Sleep(1 * time.Second)
}
```

This outputs (what a user expects):

```
--- FAIL: TestFoo (1.00s)
    foo_test.go:10: fatal
```

Giving the user a false sense of having written correct test.

However, when running the test with the `-race` flag, it becomes obvious this is not okay:

```
==================
WARNING: DATA RACE
....
==================
--- FAIL: TestFoo (1.00s)
    foo_test.go:10: fatal
```

Perhaps the `vet` tool can check for these cases.
Repository: flutter
Issue: Don't redirect standard stream to syslog when running on a custom embedder
Labels: c: new feature,platform-ios,engine,P3,team-ios,triaged-ios

The Flutter tools read syslog output for `flutter logs`. To service this, the framework redirects standard stream output to syslog. When Flutter is embedded by third parties, this can cause the engine to redirect the stream anyway. This could be potentially confusing to the user.
Repository: flutter
Issue: Need a way to preload asset images that are resolution aware
Labels: c: new feature,framework,d: api docs,a: assets,P2,team-framework,triaged-framework

In my app, I'm getting flickering because `AssetImage()` tries to load an image, but it's not immediately available because it hasn't been loaded.

There needs to be a way to warm the cache in a resolution-aware manner.
Repository: rust
Issue: method has an incompatible type for trait due to lifetimes has too wide a span
Labels: A-diagnostics,A-lifetimes,A-trait-system,T-compiler,D-confusing,D-terse

[For](https://play.rust-lang.org/?gist=4babb6ed0153e47f82c965a9feafbb28&version=nightly)

``` rust
trait A<'a> {
    fn a<'b>(self) -> Box<A<'b>>;
}

struct C;

impl<'a> A<'a> for C {
    fn a<'b>(self) -> Box<A<'a>>{}
}
```

it would be much more useful if we spanned the offending lifetime rather than the whole method: i.e. like this

```
error: method `a` has an incompatible type for trait:
 expected bound lifetime parameter 'b,
    found concrete lifetime [--explain E0053]
 --> <anon>:8:5
8 |>     fn a<'b>(self) -> Box<A<'a>>{}
  |>                             ^^

```

instead of 

```
error: method `a` has an incompatible type for trait:
 expected bound lifetime parameter 'b,
    found concrete lifetime [--explain E0053]
 --> <anon>:8:5
8 |>     fn a<'b>(self) -> Box<A<'a>>{}
  |>     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```
Repository: go
Issue: cmd/go: schedule cgo compilation early
Labels: ToolSpeed,NeedsInvestigation

From a quick scan of the code, it appears that cgo does not depend on a package's dependencies having been compiled. Given that that is the case, and given that cgo (and the resulting C compiler invocations) are generally very slow, it is probably worth scheduling all invocations of cmd/cgo at the very beginning of a build. (As a corollary, this might also mean scheduling the compilation of cmd/cgo itself early.)

cc @ianlancetaylor for input about whether cgo invocations can be safely pushed to the head of the queue.

One downside: It is unclear whether this is just a poor man's version of #8893, which didn't appear to yield much fruit. That could use more investigation.
Repository: TypeScript
Issue: Type Merging between extends and intersection
Labels: Suggestion,Help Wanted,Effort: Moderate

**TypeScript Version:** 

1.8.10

**Code**

``` ts
interface Foo {
    on(type: 'foo', listener: (event: MouseEvent) => boolean): boolean;
    on(type: string, listener: (event: Event) => boolean): boolean;
}

interface Bar {
    on(type: 'bar', listener: (event: MSGestureEvent) => boolean): boolean;
    on(type: string, listener: (event: Event) => boolean): boolean;
}

interface FooBarA extends Foo, Bar {} // Error: not correctly extended

interface FooBarB extends Foo, Bar {
    on(type: 'foo', listener: (event: MouseEvent) => boolean): boolean;
    on(type: 'bar', listener: (event: MSGestureEvent) => boolean): boolean;
    on(type: string, listener: (event: Event) => boolean): boolean;
}

type FooBarC = Foo & Bar;

let foobar: FooBarC;

foobar.on('foo', (event) => { return false; });
```

**Expected behavior:**

That `FooBarA` would work instead of throwing an error.

**Actual behavior:** 

`FooBarA` complains `Interface 'FooBarA' cannot simultaneously extend types 'Foo' and 'Bar'. Named property 'on' of types 'Foo' and 'Bar' are not identical.`

While that is true in the strictest sense, the "base" override matches, which means in theory the string literal types could be merged and the error should only occur if there is a conflict between a specific string literal type.

Using the intersection type works perfectly fine and the resulting type mirrors the runtime behaviour.  Using the "reimplement all methods" (`FooBarB`) gets really tedious really quickly when you are trying to do something like model event listeners like the above.
Repository: youtube-dl
Issue: Site support request - Canal-u.tv
Labels: site-support-request

Canal-u.tv link not supported :

`youtube-dl -t https://www.canal-u.tv/video/ecole_normale_superieure_de_lyon/gouvernement.3118
[generic] gouvernement: Requesting header
WARNING: Falling back on generic information extractor.
[generic] gouvernement: Downloading webpage
[generic] gouvernement: Extracting information
[generic] gouvernement.3118: Downloading SMIL file
[download] Destination: Gouvernement - Ecole Normale Supérieure de Lyon - Vidéo  - Canal-U-gouvernement.3118.flv
[rtmpdump] 0 bytes

ERROR: rtmpdump exited with code 1`

Thank you for considering my request.
Repository: go
Issue: x/net: Add an eBPF package
Labels: NeedsDecision,FeatureRequest

Forked from #14982 - that issue was originally about adding both a BPF and an eBPF package to x/net.

After researching eBPF more, the virtual machine is _very_ different and more complex, so it makes sense to track the work for eBPF separately from the relatively simple BPF stuff.

Main documentation for eBPF is at https://www.kernel.org/doc/Documentation/networking/filter.txt , although it's described as a diff from "classic" BPF, which is really not a helpful way to specify a machine.
Repository: youtube-dl
Issue: Subtitle tracks order
Labels: request,postprocessors

youtube-dl  ignores --sub-lang languages order and embeds subtitles randomly(?).
Is there some way to embed them in the selected order?

```
D:\youtube-dl.exe --format best --format best --keep-video --sub-lang en,ru --embed-subs --write-sub --write-auto-sub --verbose --output %(title)s.%(ext)s --restrict-filenames "https://www.youtube.com/watch?v=vBpxhfBlVLU"
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'--format', u'best', u'--format', u'best', u'--keep-video', u'--sub-lang', u'en,ru', u'--embed-subs', u'--write-sub', u'--write-auto-sub', u'--verbose', u'--output', u'%(title)s.%(ext)s', u'--restrict-filenames', u'https://www.youtube.com/watch?v=vBpxhfBlVLU']
[debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
[debug] youtube-dl version 2016.05.10
[debug] Python version 2.7.10 - Windows-XP-5.1.2600-SP3
[debug] exe versions: ffmpeg 2.4.git
[debug] Proxy map: {}
[youtube] vBpxhfBlVLU: Downloading webpage
[youtube] vBpxhfBlVLU: Downloading video info webpage
[youtube] vBpxhfBlVLU: Extracting video information
[youtube] vBpxhfBlVLU: Looking for automatic captions
[youtube] vBpxhfBlVLU: Downloading MPD manifest
[info] Writing video subtitles to: Why_do_mirrors_flip_horizontally_but_not_vertically.ru.vtt
[info] Writing video subtitles to: Why_do_mirrors_flip_horizontally_but_not_vertically.en.vtt
[debug] Invoking downloader on u'https://r2---sn-8vap5-3c2s.googlevideo.com/videoplayback?ratebypass=yes&ipbits=0&mime=video%2Fmp4&sparams=dur%2Cid%2Cinitcwndbps%2Cip%2Cipbits%2Citag%2Clmt%2Cmime%2Cmm%2Cmn%2Cms%2Cmv%2Cpl%2Cratebypass%2Crequiressl%2Csource%2Cupn%2Cexpire&expire=1463325036&initcwndbps=2611250&mn=sn-8vap5-3c2s&mm=31&signature=ADCE8371EB7E32D0A131BC1A9B07A0494E6F905E.A13C54F346D41B39120D2B225AB1258BB8E7D897&fexp=9407191%2C9416126%2C9416891%2C9419452%2C9422342%2C9422596%2C9428398%2C9429743%2C9431012%2C9431418%2C9433096%2C9433946%2C9434078%2C9434344%2C9434922%2C9435850%2C9436090%2C9436322%2C9436446%2C9436481&key=yt6&ip=93.74.138.5&requiressl=yes&pl=17&source=youtube&sver=3&dur=227.044&mv=m&mt=1463302590&ms=au&id=o-AH40Dxpb2QCbBCG2x6b8XnI8bnoQG9y9qoCqnYySsSn7&lmt=1428126602563068&itag=22&upn=sFeBRwXcMRQ'
[download] Destination: Why_do_mirrors_flip_horizontally_but_not_vertically.mp4
[download] 100% of 51.10MiB in 00:05
[ffmpeg] Embedding subtitles in 'Why_do_mirrors_flip_horizontally_but_not_vertically.mp4'
[debug] ffmpeg command line: ffmpeg -y -i file:Why_do_mirrors_flip_horizontally_but_not_vertically.mp4 -i file:Why_do_mirrors_flip_horizontally_but_not_vertically.ru.vtt -i file:Why_do_mirrors_flip_horizontally_but_not_vertically.en.vtt -map 0 -c copy -map -0:s -c:s mov_text -map 1:0 -metadata:s:s:0 language=rus -map 2:0 -metadata:s:s:1 language=eng file:Why_do_mirrors_flip_horizontally_but_not_vertically.temp.mp4

```
Repository: rust
Issue: Error E0301 "the parameter type `T` may not live long enough" could explain where the lifetime requirement comes from
Labels: C-enhancement,A-diagnostics,T-compiler,D-confusing,D-papercut

Error E0301 "the parameter type `T` may not live long enough" could explain where the lifetime requirement comes from.

Here's some example code where the `T: 'static` requirement comes implicitly from a `Box<Trait>` trait object (so 'static is invisible).

[playground](https://play.rust-lang.org/?gist=829eb1711d4a426b8dfebbaadcf5e512&version=stable&backtrace=0)

``` rust
trait Funny { }

fn new_funny_handle<T: Funny + Default>() -> Box<Funny> {
    Box::new(T::default())
}
```

``` rust
error: the parameter type `T` may not live long enough [--explain E0310]
 --> <anon>:5:5
5 |>     Box::new(T::default())
  |>     ^^^^^^^^^^^^^^^^^^^^^^
help: consider adding an explicit lifetime bound `T: 'static`...
note: ...so that the type `T` will meet its required lifetime bounds
 --> <anon>:5:5
5 |>     Box::new(T::default())
  |>   
```
Repository: neovim
Issue: Option to show showbreak character at end of the line that is wrapping
Labels: enhancement

### Consider this a feature request
- Neovim version: 0.1.5-dev
- Operating system/version: Ubuntu GNOME 15.10
- Terminal name/version: GNOME Terminal 3.16
- `$TERM`: xterm-256color
### Actual behaviour

![2016-05-15_23-25-03_687x283](https://cloud.githubusercontent.com/assets/10473142/15275867/a6828f82-1af4-11e6-93a4-1dfdc2100b8e.png)

The glyphs appear on the next line. I have to use `set cpo+=n` and `set showbreak=↪\ \ \` to keep the character from overlapping with the text. This works ok as long as I have files < 4 digit lines. Then I need to add another space in `showbreak` which breaks it in places where line number is only 3 digits.
### Expected behaviour

![External](http://dailydotnettips.com/wp-content/uploads/2011/04/image8.png)
This is a configurable option in Visual Studio. It looks a little cleaner and doesn't make the user deal with the number of spaces in showbreak.
**NOTE:** The glyph doesn't have to be drawn in the last column (but it would be great if it could).
Repository: You-Dont-Know-JS
Issue: "ES6 & Beyond", ch3, section "Modules -> Moving forward" - unclear sentence
Labels: for second edition

First of all, huge respect for the books, they are amazing!

In the **Moving Forward** subsection, there is a sentence that seems somewhat unclear (uses being accustomed to something):

> Some **uses are accustomed to being able to provide** dynamic API definitions, where methods can be added/removed/replaced in response to runtime conditions. Either these **uses will have to change** to fit with ES6 static APIs, or they will have to restrain the dynamic changes to properties/methods of a second-level object.

Maybe there should be **users** instead of **uses**?
Repository: TypeScript
Issue: Bug: Accessing private statics in a class via its derived class is allowed
Labels: Suggestion,Breaking Change,Help Wanted,Effort: Moderate

**TypeScript Version:** 

1.8.X

**Code**

``` ts
class FooBase {
    private static privateStatic: string = "";

    testBase(): void {
        console.log(FooBase.privateStatic);

        // Should error, but doesn't
        console.log(Foo.privateStatic);
   }
}

class Foo extends FooBase {
    test() {
        // Should error, and does
        console.log(Foo.privateStatic);
    }
}
```

**Expected behavior:**
Accessing `Foo.privateStatic` shouldn't be allowed, regardless of the context it's called in.

**Actual behavior:** 
`FooBase` is allowed to do this.

_(thanks @sethbrenith for deducing this)_
Repository: go
Issue: spec: clarify method sets and recursive promotions
Labels: Documentation,NeedsFix

My reading of the Go spec is that this is valid:

```
package p

type S1 struct { *S2 }
type S2 struct { *S1 }

func (*S1) M() {}

var _ = S1.M
```

Rationale:
1. Because of `func (*S1) M() {}`, `M` is a member of `*S1`'s method set.
2. Because of the `*S1` embedding into `S2`, `M` is also a member of `S2` and `*S2`'s method sets.
3. Because of the `*S2` embedding into `S1`, `M` should also be a member of `S1`'s method set.

However, cmd/compile, gccgo, and gotype all reject it.

/cc @griesemer @ianlancetaylor
Repository: go
Issue: cmd/compile: poor error message when invoking method on embedded type
Labels: NeedsFix,compiler/runtime

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

go1.6.2
1. What operating system and processor architecture are you using (`go env`)?

The playground
1. What did you do?

https://play.golang.org/p/hsjwmQwtsb

Relevant snippet:

``` go
func TestFoo(t *testing.T) {
    t.Fail("what?")
}
```
1. What did you expect to see?

```
prog.go:14: too many arguments in call to t.Fail
```
1. What did you see instead?

```
prog.go:14: too many arguments in call to t.common.Fail
```

The `.common` bit is unexpected and an implementation detail. Running `godoc testing Fail` shows a simple method `func (c *T) Fail()`, and the fact that `testing.T` embeds `testing.common` does not seem useful.
Repository: kubernetes
Issue: Umbrella issue for various swagger related improvements
Labels: priority/backlog,sig/api-machinery,area/swagger,lifecycle/frozen

Summarizing all our swagger related issues here:

Improving the spec:
- [ ] Represent Enum types: right now, we represent them as strings and put the possible values in comments. Want to represent them as enum types and use the list of valid values for validation: https://github.com/kubernetes/kubernetes/issues/24562
- [x] Represent strategic merge patch policy in swagger: https://github.com/kubernetes/kubernetes/issues/24560 (need to figure out how to represent it)
- [x] Fix the return type for /versions: https://github.com/kubernetes/kubernetes/issues/17176 (super simple one line change)
- [x] *versioned.Event model should not be a pointer: https://github.com/kubernetes/kubernetes/issues/24240 (looks like a bug in go-restful)
- [x] Get swagger spec validation to pass: https://github.com/kubernetes/kubernetes/issues/16748 (requires change to swagger-tools most probably)
- [x] Figure out a way to represent IntOrString: We represent them as string right now which fails when we return int: https://github.com/kubernetes/kubernetes/issues/14190
- [x] Fix responseModel for pods/log: https://github.com/kubernetes/kubernetes/issues/14071
- [ ] Document all possible status codes and returned object types: https://github.com/kubernetes/kubernetes/issues/6167
- [x] Represent maps as maps (right now we represent them as `"type": "object"` which is the generic type we use for all our custom types): https://github.com/kubernetes/kubernetes/issues/4700 (requires moving to 2.0)
- [x] Represent unversioned.Time correctly in swagger spec: https://github.com/kubernetes/kubernetes/issues/2968 (should be a simple change)
- [x] intOrString #2971
- [ ] deletion response is incorrect #30537

Making it easy to use:
- [x] Serve it as JSON at kubernetes.io: https://github.com/kubernetes/kubernetes/issues/15571
- [x] Validate on each commit to ensure valid spec at HEAD: https://github.com/kubernetes/kubernetes/issues/5356

Doing things on top of spec:
- [ ] Generate client libraries in multiple languages: We can use client-gen swagger tool to use the swagger to spec to auto generate client libraries in multiple languages: https://github.com/kubernetes/kubernetes/issues/22405

Advanced:
- [x] Move to swagger spec 2.0: https://github.com/kubernetes/kubernetes/issues/13414 (we are using go-restful to generate swagger spec 1.2 right now).
- [ ] Move all internal components to use OpenAPI (swagger spec 2.0): https://github.com/kubernetes/kubernetes/issues/38637
Repository: You-Dont-Know-JS
Issue: "ES6 & Beyond", ch4, section "Review" - possible typo
Labels: for second edition

> Right now, we can manage these interactions with the aid**e** of various async libraries’ runners, but JavaScript is eventually going to support this interaction pattern with dedicated syntax alone!

As I just learned, [aide](http://dictionary.cambridge.org/dictionary/english/aide) is a valid English word, but it seems to refer to a person, which would make it incompatible with "with the aide of runners" construct.

If you confirm a typo, I would gladly fix it and create a pull request.
Repository: kubernetes
Issue: Store logs from hooks and probes in separate log files
Labels: priority/backlog,sig/node,kind/feature,lifecycle/frozen,needs-triage

As of now kubelet inlines log files from probes. #25681 inlines logs from hooks.
Inlining such logs makes it difficult to identify them and also pollutes kubelet logs.
Ideally, these logs should be either inlined into container logs. That is not possible today with the default docker logging driver.
An alternative is to store hooks and prober logs into separate container logs that the kubelet can manage.
Repository: opencv
Issue: [Bug] Different description result for a keypoint with ORB and cuda::ORB
Labels: category: gpu/cuda (contrib),RFC

### Please state the information for your system
- OpenCV version: 3.1
- Host OS: Linux (Ubuntu 16.04) 
### In which part of the OpenCV library you got the issue?

Examples:
- features2d(ORB) and cudafeatures2d(cuda::ORB)
- different description results for same key-points 
### Problem description

Find key-points and describe using cv::cuda::ORB::detecetAndCompute() with useProvidedKeypoints = false (to be able to detect key-points)
Describe key-points that we just detect using cv::ORB::detectAndCompute with useProvidedKeypoints = true which will use given key-points to describe.
Compare two description and expect them to be exactly the same.   
### Expected behavior

Expecting exactly identical description result for a key-point on same image using both cv::ORB and cv::cudaORB.
### Actual behavior

Different description results for same key-points between cv::ORB and cv::cuda::ORB
### Code example to reproduce the issue / Steps to reproduce the issue

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

```
#include <opencv2/core/cuda.hpp>
#include <opencv2/core.hpp>
#include <opencv2/cudafeatures2d.hpp>
#include <opencv2/imgcodecs.hpp>
#include <opencv2/imgcodecs/imgcodecs_c.h>
#include <iostream>

using namespace cv;
using namespace std;

int main() {
    cv::Mat img_cpu = cv::imread("lena.png", CV_LOAD_IMAGE_GRAYSCALE);
    cv::cuda::GpuMat img_gpu(img_cpu);

    cv::cuda::GpuMat desc_gpu;
    cv::Mat desc_cpu;

    vector<KeyPoint> keypoints;

    cv::Ptr<cv::ORB> orb_cpu = cv::ORB::create(15);
    cv::Ptr<cv::cuda::ORB> orb_gpu = cv::cuda::ORB::create(15);

    orb_gpu->detectAndCompute(img_gpu, noArray(),keypoints,desc_gpu, false);
    orb_cpu->detectAndCompute(img_cpu,noArray(),keypoints,desc_cpu,true);

    cv::Mat donwloaded_desc_gpu(desc_gpu);

    cout <<"Description result for GPU" << endl << donwloaded_desc_gpu << endl << "Description result for CPU" << endl << desc_cpu << endl;

    return 0;
}
```

I run this code like this:

> g++ -c issue.cpp
> g++ -L/usr/local/lib -o "issue" ./issue.o -lopencv_core -lopencv_cudafeatures2d -lopencv_features2d -lopencv_imgproc -lopencv_imgcodecs
> ./issue
Repository: kubernetes
Issue: Audit all APIs for selector fields, ensure documented semantics when nil or empty.
Labels: priority/backlog,help wanted,sig/architecture,lifecycle/frozen

Service.spec.selector comments say "If empty, all pods are selected, if not specified, endpoints must be manually specified".

As far as I can tell this is not implemented, though.  While Go understands the different between a nil slice and a non-nil slice with no elements, JSON does not.  With an `omitempty` field, we get the field dropped in either case.

To actually achieve this semantic, we need the type to be a pointer, so omitempty applies to a nil pointer but not an empty map.  But at least protobuf codegen does not support this, either.  I think the right fix is to change the documentation.

@bgrant0607 @smarterclayton