sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: runtime: re-enable TestGdbPython and TestGdbBacktrace on linux/ppc64 (BE) if/when it gets cgo support
Labels: NeedsFix,compiler/runtime

```
--- FAIL: TestGdbPython (0.30s)
    runtime-gdb_test.go:50: gdb version 7.7
    runtime-gdb_test.go:152: package testing source file: /tmp/workdir/go/src/testing/testing.go
    runtime-gdb_test.go:153: failed to load Go runtime support: "/tmp/go-build613978241/a.exe": not in executable format: File format not recognized
        "/tmp/go-build613978241/a.exe": not in executable format: File format not recognized
        No auto-load scripts.
        No symbol table is loaded.  Use the "file" command.
        Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
        No executable file specified.
        Use the "file" or "exec-file" command.
        BEGIN info goroutines
        Undefined info command: "goroutines".  Try "help info".
        END
        No stack.
        BEGIN print mapvar
        No symbol table is loaded.  Use the "file" command.
        END
        BEGIN print strvar
        No symbol table is loaded.  Use the "file" command.
        END
        No stack.
        BEGIN goroutine 2 bt
        Undefined command: "goroutine".  Try "help".
        END
--- FAIL: TestGdbBacktrace (0.15s)
    runtime-gdb_test.go:50: gdb version 7.7
    runtime-gdb_test.go:264: could not find '#0.*main\.eee' in backtrace
    runtime-gdb_test.go:265: gdb output:
        "/tmp/go-build806889452/a.exe": not in executable format: File format not recognized
        No symbol table is loaded.  Use the "file" command.
        Make breakpoint pending on future shared library load? (y or [n]) [answered N; input not from terminal]
        No executable file specified.
        Use the "file" or "exec-file" command.
        No stack.
        The program is not being run.
FAIL
FAIL    runtime 14.687s
```

I propose we skip these tests there for now so we can see what else is failing. (These tests already skip if gdb is absent anyway)

/cc @dr2chase
Repository: react
Issue: Bypass synthetic event system for Web Component events
Labels: Type: Feature Request,Type: Discussion

To use a Web Component in React, you must directly attach an event listener to the React ref for that WC. We could change the implementation so that when React detects a custom element (tag names with dashes, like `my-component`), it will bypass the synthetic event system (and the whitelist) and just attach the event listener on the element itself.

Why bypass the synthetic event system? Because _anyway_ we already need to bypass it manually when using a Web Component. I'm not so familiar with the React codebase, but this naive approach seems to work. Whoever uses Web Components in React can be responsible for whatever downsides that would cause, maybe in performance, I don't know. They are already having those (supposed) downsides, this issue is just about the convenience of WC usage inside React.

I was about to send a PR for this, but thought of opening an issue. I looked through the issues and didn't see any existing one related to the handling of WC events.

**What is the current behavior?**

A WC custom event (e.g. `flipend`) must be handled by attaching the event listener directly to the element in componentDidMount using a ref.

http://jsbin.com/yutocopasu/1/edit?js,output

React v15.1.0

``` js
class HelloMessage extends React.Component {
  handleHelloClick() {
    this.refs['foo'].toggle();
  }

  handleFlipend(ev) {
    console.log('Handle flip end');
  }

  componentDidMount() {
    this.refs['foo'].addEventListener('flipend', ev =>
      this.handleFlipend(ev);
    );
  }

  render() {
    return (
      <div>
        <div onClick={ev => this.handleHelloClick()}>
          Hello {this.props.name}, click me!
        </div>
        <brick-flipbox class="demo" ref="foo">
          <div>front</div>
          <div>back</div>
        </brick-flipbox>
      </div>
    );
  }
}
```

**What is the expected behavior?**

A WC custom event can be handled with `onMyEvent={ev => this.handleMyEvent(ev)}` on the ReactElement corresponding to the WC.

``` js
class HelloMessage extends React.Component {
  handleHelloClick() {
    this.refs['foo'].toggle();
  }

  handleFlipend(ev) {
    console.log('Handle flip end');
  }

  render() {
    return (
      <div>
        <div onClick={ev => this.handleHelloClick()}>
          Hello {this.props.name}, click me!
        </div>
        <brick-flipbox onFlipend={ev => this.handleFlipend(ev)} class="demo" ref="foo">
          <div>front</div>
          <div>back</div>
        </brick-flipbox>
      </div>
    );
  }
}
```

PS: this snippet above still has the `ref`, but for unrelated reasons. Ideally we wouldn't need refs for handling events of WCs.
Repository: go
Issue: x/mobile/cmd/gomobile: type conversion not working on iOS
Labels: mobile

Hey,

I have a (hopefully small) issue with type conversion related to usage of gomobile:
### What version of Go are you using (`go version`)?

```
go version go1.7.1 darwin/amd64
```

```
gomobile version +6ea0bb5 Wed Oct 5 13:16:13 2016 +0000 (android,ios); androidSDK=/Users/.../Library/Android/sdk/platforms/android-23
```
### What operating system and processor architecture are you using (`go env`)?

```
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
```
### What did you do?
1. Write code with composed interface. Can be something like

``` go
type Car interface {
    WheelCount() int
}
type Limousine interface {
    Car
    Seats() int
    SetSeats(seats int)
}
```

Full go code is available at [Go Code](https://play.golang.org/p/pnVP8_CLqs)
2. Generate go mobile bindings for iOS and android, e.g.
`gomobile bind -target=ios data`
3. Create platform specific app and call a go method which tries to do type conversion. Type conversion may be:

``` go
func PrintCar(car Car) {
    fmt.Println("Car: ", car)
    fmt.Println("Wheels: ", car.WheelCount())

    limousine, ok := car.(Limousine)
    fmt.Println("Limousine cast was ", ok, ", Content:", limousine)
    if ok {
        fmt.Println("Seats: ", limousine.Seats())
    }
}
```

and platform specific code like this for iOS

``` objc
id<GoDataLimousine> car = GoDataNewLimousine();
[car setSeats:5];
GoDataPrintCar(car);
```
1. Execute the program on iOS or Android
### What did you expect to see?

Type conversion from Car to Limousine should be possible if the object fulfills Limousine.
Output of type conversion on Go, iOS and Android:

```
Car:  &{4 5}
Wheels:  4
Limousine cast was  true , Content: &{4 5}
Seats:  5
```
### What did you see instead?

Type conversion is not possible on iOS between interfaces. Output of type conversion Go, Android (as expected):

```
Car:  &{4 5}
Wheels:  4
Limousine cast was  true , Content: &{4 5}
Seats:  5
```

iOS, fails to do type conversion. The limousine is stripped down to fulfill the car interface only and does not fulfill the limousine interface anymore:

```
Car:  &{42}
Wheels:  4
Limousine cast was  false , Content: <nil>
```

So in my understanding type conversion should work on iOS as it does on android and in normal go itself. But using gomobile on iOS, interfaces seem to loose other fulfilled interfaces once they're passed to a method which receives a specific interface only.

Or am I doing something wrong? Otherwise I would like to help solving this issue. Sadly I am new to the go mobile tooling itself. Maybe somebody can point me into the right direction? 

Is this intentionally not working or is it expected to work?

Thanks for your help!
Repository: rust
Issue: Attribute for skipping field of struct in Debug derives?
Labels: C-enhancement,T-lang

Could we have something like this?

``` rust
#[derive(Debug)]
struct Foo {
    pub a: A,
    pub b: B,
    #[skip_derive]
    pub c: C, // especially useful if C : !Debug
}
```

This could also feasibly be applied to other auto-derivations, of course (not just Debug).
Repository: TypeScript
Issue: Move away from Classic module resolution as default for all module kinds
Labels: Suggestion,Help Wanted,Committed,Effort: Moderate

TypeScript's original module resolution strategy (the _Classic_ resolution strategy) has some strange behavior that apparently doesn't actually reflect any other resolution strategy. It seems strange that those using non-CommonJS emit targets get this behavior by default.

_Classic_ resolution also causes many disk probes during the walk up the project root - assuming that this strategy does eventually succeed in most cases, it seems like most uses could be subsumed by:
- Using relative paths.
- Modifying the `baseUrl` and `paths` properties in `tsconfig.json`.

After discussing with @vladima, we think it is worth considering switching the default resolution strategy for all module targets to _Node_.

Here's what needs to be done:

* [ ] Investigate existing `tsconfig.json`s that target esXXXX` and have no explicit/implied resolution strategy.
* [ ] Determine the downstream effects to a change to defaults
* [ ] Determine if this change outweighs the potential breakage
* [ ] Implement if appropriate
Repository: kubernetes
Issue: Server side defaulting of values prevents diff patches from working
Labels: priority/important-soon,area/app-lifecycle,area/kubectl,sig/api-machinery,area/declarative-configuration,lifecycle/frozen,wg/api-expression

Server side defaults are easily differentiated from other values set within the kubernetes system (e.g. DeploymentStatus).  `kubectl apply` records the applied config as an annotation on the objects that it creates so that it can perform a 3-way diff to merge local changes into the live config without erasing other items such as the status.

Steps to reproduce:

Use `kubectl apply -f` to create a deployment using this config:

``` yaml
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: nginx-deployment
spec:
  replicas: 3
  template:
    metadata:
      labels:
        app: nginx
    spec:
      containers:
      - name: nginx
        image: nginx
        ports:
        - containerPort: 80 
```

Update the config spec adding

``` yaml
strategy:
    type: "Recreate"
```

Apply the new config.

Result:

``` sh
The Deployment "nginx-deployment" is invalid.
spec.strategy.rollingUpdate: Forbidden: may not be specified when strategy `type` is 'Recreate'
```

This is caused because the server defaults spec.strategy.rollingUpdate but this is invisible to the client and cannot be differentiated from other changes made by the server that the client should ignore (e.g. status changes).

This can be seen for any field whose default is derived from another field such as Deployment labels and selectors (derived from the PodTemplate labels).

Solving this will require at least some changes on the server side.  One possible solution would be to:
1. Have the server record which derived fields that it adds / updates
2. Have the client then merge these changes into the last-applied-config used by diff patch so they are deleted
3. Have the server re-perform defaulting / normalization on the resulting object from the PATCH

Thoughts / Comments / Suggestions?
Repository: go
Issue: cmd/compile: large arrays cause large binaries and toolchain errors
Labels: NeedsDecision,compiler/runtime

On tip, `go version devel +0db9518 Fri Oct 7 03:46:50 2016 +0000 darwin/amd64`:

```
$ cat j.go 
package main

var x = [1 << 30]byte{0: 1}

func main() {
    println(x[0])
}
$ go build j.go
$ ls -l j
-rwxr-xr-x  1 crawshaw  eng  1074669392 Oct  7 10:34 j
```

Bumping 1<<30 to 1<<31 turns it into a linker error:

```
~$ go build j.go 
# command-line-arguments
main.x: symbol too large (2147483648 bytes)
too much data in section SNOPTRDATA (over 2000000000 bytes)
too much data in section SDATA (over 2000000000 bytes)
too much data in section SBSS (over 2000000000 bytes)
too much data in section SNOPTRBSS (over 2000000000 bytes)
main.init: pc-relative relocation address for main.initdone· is too big: 0x800ad36a
main.init: pc-relative relocation address for main.initdone· is too big: 0x800ad355
runtime.alginit: pc-relative relocation address for runtime.cpuid_ecx is too big: 0x800ac585
runtime.alginit: pc-relative relocation address for runtime.hashkey is too big: 0x800ac72d
runtime.alginit: pc-relative relocation address for runtime.hashkey is too big: 0x800ac70b
runtime.alginit: pc-relative relocation address for runtime.hashkey is too big: 0x800ac700
runtime.alginit: pc-relative relocation address for runtime.hashkey is too big: 0x800ac701
runtime.alginit: pc-relative relocation address for runtime.hashkey is too big: 0x800ac6f6
runtime.alginit: pc-relative relocation address for runtime.hashkey is too big: 0x800ac6f7
runtime.alginit: pc-relative relocation address for runtime.hashkey is too big: 0x800ac6ec
runtime.alginit: pc-relative relocation address for runtime.hashkey is too big: 0x800ac6ed
runtime.alginit: pc-relative relocation address for runtime.hashkey is too big: 0x800ac6e2
runtime.alginit: pc-relative relocation address for runtime.useAeshash is too big: 0x800ac4ea
runtime.alginit: pc-relative relocation address for runtime.algarray is too big: 0x80091a0b
runtime.alginit: pc-relative relocation address for runtime.algarray is too big: 0x80091a0d
runtime.alginit: pc-relative relocation address for runtime.algarray is too big: 0x80091a1f
/Users/crawshaw/go/pkg/tool/darwin_amd64/link: too many errors
```

(Inspired by https://codegolf.stackexchange.com/questions/69189/build-a-compiler-bomb/69193#69193)
Repository: angular
Issue: Query params always purport to be empty on page load even though provided
Labels: type: bug/fix,freq3: high,area: router,P3

**I'm submitting a ...**  (check one with "x")

```
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
```

**Current behavior**
`this.route.queryParams` (with `this.route` being an injected `ActivatedRoute`, when query parameters are present in the URL, will fire once with an empty object, and then again immediately with the query params.

**Expected behavior**
I would expect this to fire only the second time with the provided query params.

**Minimal reproduction of the problem with instructions**

In a component, inject `ActivatedRoute` and call it `route` in the constructor. Then:

``` ts
this.route.queryParams
      .filter((queryParams: any) => {
        // Let's say the query param we're looking for is called "foo"
        return !queryParams.foo;
      })
      .subscribe(() => {
        alert('no query param called "foo"!');
      });
```

Then navigate to the path `/?foo=bar`. You should see the alert, even though the query param `foo` is provided.

This happens both if you run this code in a component's constructor _and_ `ngOnInit`.

**What is the motivation / use case for changing the behavior?**
I have logic in place that appends a query param to the URL when not present. The subscription wrongly tells me there is no query param.

My current workaround is to use `debounceTime`, but this may introduce race conditions.

``` ts
this.route.queryParams
      .debounceTime(500)
      .filter((queryParams: any) => {
        return !queryParams.foo;
      })
      .subscribe(() => {
        alert('no query param called "foo"!');
      });
```

**Please tell us about your environment:**
Operating system: macOS Sierra version 10.12
IDE: Atom 1.10.2
Package manager: NPM
Based on https://github.com/mgechev/angular2-seed
- **Angular version:** 2.0.X
  2.0.0
- **Browser:**
  Chrome version 53.0.2785.143 (64-bit)
  Safari version 10.0 (12602.1.50.0.10)
- **Language:** [all | TypeScript X.X | ES6/7 | ES5]
  TypeScript version 1.8.10
- **Node (for AoT issues):** `node --version` =  
  Not sure what AoT means, but for what it's worth, my Node version is 4.0.0.
Repository: youtube-dl
Issue: Add support for Adobe Pass Auth TV Provider Charter Communications
Labels: tv-provider-account-needed

I'd like to request support for the MSOs under TVEverywhere. There seems to be a relation to watchtveverywhere.com ( #10709), but some providers don't overlap.

Specifically, I'm looking for support for Charter Communications, soon to be Charter/Time Warner/Spectrum. I can provide credentials for this if needed.

http://www.tveverywherenow.com/#get-started-dest
Repository: flutter
Issue: markNeedsLayout(will not affect size)
Labels: c: new feature,framework,c: performance,P3,team-framework,triaged-framework

There are some situations where a render object knows that it needs layout but also knows that the layout will not change its size.  If the parent uses the this object's size in its layout, we can avoid marking the parent as needing layout.

Examples:
- viewports in the new scrolling world
- re-positioning positioned children in a stack

/cc @Hixie
Repository: kubernetes
Issue: Facilitate API orchestration
Labels: area/api,area/app-lifecycle,sig/api-machinery,sig/apps,area/teardown,lifecycle/frozen

Currently, building a general-purpose orchestrator for our API is more challenging than it should be.

Some problems (probably not exhaustive):
- There's no general way to determine when applications and/or services are "ready", such as for cases where applications need other applications to be up in order to start properly, which apparently is the case for some non-cloud-native applications (#1768, kubernetes/kubernetes#29453). Service-level readiness would be useful for a number of purposes. Disruption budget is related.
- There's no general way to determine when operations, such as cascading deletion (#29891), scaling, or deployment, are "done". Deletion is a special case, but most other cases amount to observed state matching desired state (or desired state has subsequently changed again). This is related to generation and observedGeneration.
- There's no general way to determine when operations, such as deployment, "fail". In most cases, I think this amounts to inability to achieve the desired state within an acceptable amount of time.
- There's no general way to hook creation and deletion (though finalizers should address the latter) kubernetes/kubernetes#3585, nor other resource lifecycle events kubernetes/kubernetes#3692.
- There's no general way to query resource inter-dependencies.
- There's no general way to shutdown a cluster without leaking external resources (e.g., external load balancers).

See also:
kubernetes/kubernetes#29453
kubernetes/kubernetes#1899
kubernetes/kubernetes#5164
kubernetes/website#41954
kubernetes/kubernetes#4630
kubernetes/kubernetes#15203
kubernetes/kubernetes#29891
kubernetes/kubernetes#14961
kubernetes/kubernetes#14181
kubernetes/kubernetes#1503
kubernetes/kubernetes#32157
kubernetes/kubernetes#38216

cc @lavalamp @pwittrock @smarterclayton
Repository: vue
Issue: A child components `destroyed` hook is called before its `detached` hook
Labels: 1.x

### Vue.js version

1.0.28
### Reproduction Link

https://jsfiddle.net/w0r85tus/
### Steps to reproduce
- Open the JSFiddle, then open devtools
- Click "show modal" in the result view
- Click "Ok" in the modal
- Observe the console.log statement order
### What is Expected?
- Components should be `detached` before they are `destroyed`.
- The `destroyed` hook should always be the very last hook fired.
### What is actually happening?
- The `destroyed` hook is getting called first, then the `detached` hook later.

Note that it makes no difference if the component has a `transition` applied. You can remove the `transition` attribute from the modal but the hook order stays the same.

When I'm using a tool like [selectize.js](https://github.com/selectize/selectize.js) inside a modal, I want Selectize to stay until the modal is off-screen, then destroy it. If I use the `beforeDestroy` or `destroyed` events, they will fire before the modal has transitioned out and the effect is that you will see a flash of the destroyed Selectize control.
Repository: nvm
Issue: nvm: install v6.7.0 failed!
Labels: OS: ubuntu,installing node,needs followup

I am trying to install a non root instance of node on LINUX Redhat. I do not have sudo privileges. I am getting the following error when i try `nvm install node` :

``` sh
-bash-3.2$ nvm install node
Checksums match! Using existing downloaded archive $NVM_DIR/.cache/bin/node-v6.7.0-linux-x64/node-v6.7.0-linux-x64.tar.xz
tar: invalid option -- J
Try `tar --help' or `tar --usage' for more information.
Binary download failed, trying source.
Checksums match! Using existing downloaded archive $NVM_DIR/.cache/src/node-v6.7.0/node-v6.7.0.tar.xz
tar: invalid option -- J
Try `tar --help' or `tar --usage' for more information.
nvm: install v6.7.0 failed!
```

nvm 0.32.0
tar (GNU tar) 1.15.1
Repository: youtube-dl
Issue: Windows .exe dont start
Labels: cant-reproduce

### What is the purpose of your _issue_?
- [x] Question

---
### Description of your _issue_, suggested solution and other information

I Downloaded the youtube-dl.exe on my Windows Server 2012 i have python 2.7 installed.

When i want now download a Video (over commandline) i get an error by Windows that the Application was not success to start with error code (0x000007d) and than nothing happen
.
Repository: youtube-dl
Issue: TestDownload should allow running all tests for a given extractor
Labels: request

## Please follow the guide below
- [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_?
- [x] Feature request (request for a new functionality)

---
### Description of your _issue_, suggested solution and other information

README/CONTRIBUTING explain:

> 6. Run `python test/test_download.py TestDownload.test_YourExtractor`. This _should fail_ at first, but you can continually re-run it until you're done. If you decide to add more than one test, then rename `_TEST` to `_TESTS` and make it into a list of dictionaries. The tests will then be named `TestDownload.test_YourExtractor`, `TestDownload.test_YourExtractor_1`, `TestDownload.test_YourExtractor_2`, etc.

I have to admit, I read this, wrote one test, and later on went back and added some more tests but had forgotten the final sentence. I did not at first notice that I was only running the first test, and then it took me an embarassingly long time to figure out how to run the other tests.

Why is the code structured this way — shouldn't there be an easy way to run all tests for a given extractor? That would seem to be the common case if you're working on a single extractor?

Or maybe there is a way and I'm just not seeing it?

I haven't really wrapped my head around the testing framework code, so I don't have a patch, but I am a little mystified at the current structure? Thanks. Explanation appreciated.