sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: x/exp/shiny: widgets
Labels: NeedsInvestigation

Tracking bug for Shiny Widgets.

| Widget | Assignee | Notes |
| --- | --- | --- |
| [Button](https://www.google.com/design/spec/components/buttons.html) | @nigeltao |  |
| [Cards](https://www.google.com/design/spec/components/cards.html) |  |  |
| [Chips](https://www.google.com/design/spec/components/chips.html) |  |  |
| [Dialogs](https://www.google.com/design/spec/components/dialogs.html) |  |  |
| [Dividers](https://www.google.com/design/spec/components/dividers.html) |  |  |
| [Grid lists](https://www.google.com/design/spec/components/grid-lists.html) |  |  |
| [Lists](https://www.google.com/design/spec/components/lists.html) |  | See also [Lists: Controls](https://www.google.com/design/spec/components/lists-controls.html). |
| [Data tables](https://www.google.com/design/spec/components/data-tables.html) | @crawshaw | Ideally share a data model with lists. |
| [Menus](https://www.google.com/design/spec/components/menus.html) |  |  |
| [Pickers](https://www.google.com/design/spec/components/pickers.html) |  |  |
| [Progress Bar](https://www.google.com/design/spec/components/progress-activity.html) |  |  |
| [Selection controls](https://www.google.com/design/spec/components/selection-controls.html) |  |  |
| [Slider](https://www.google.com/design/spec/components/sliders.html) |  |  |
| [Snackbar](https://www.google.com/design/spec/components/snackbars-toasts.html) |  |  |
| [Stepper](https://www.google.com/design/spec/components/steppers.html) |  |  |
| [Subheader](https://www.google.com/design/spec/components/subheaders.html) |  |  |
| [Tabs](https://www.google.com/design/spec/components/tabs.html) |  |  |
| [Text field](https://www.google.com/design/spec/components/text-fields.html) | @nigeltao |  |
| [Toolbars](https://www.google.com/design/spec/components/toolbars.html) |  |  |
| [Tooltips](https://www.google.com/design/spec/components/tooltips.html) |  |  |
| Scrolling | @nigeltao |  |
| [Flex Layout](https://www.w3.org/TR/css-flexbox-1/) | @crawshaw | [shiny/widget/flex](https://golang.org/x/exp/shiny/widget/flex) |
| GL-in-Shiny | @crawshaw | A widget which contains OpenGL, like [NSOpenGLView](https://developer.apple.com/library/mac/documentation/Cocoa/Reference/ApplicationKit/Classes/NSOpenGLView_Class/). |
| Shiny-in-GL |  | Project a screen into GL scene |
Repository: opencv
Issue: Traincascade tool: reported training time invalid on multicore systems
Labels: feature,category: apps

### Please state the information for your system
- OpenCV version: 3.x --> current master branch
- Host OS: Linux (Ubuntu 14.04) 
### In which part of the OpenCV library you got the issue?

OpenCV's embedded train_cascade tool for building cascade classifiers using the AdaBoost process
### Expected behaviour

When running the tool, the output generate should specify how long the training of each stage took, by outputting the following line after each finished stage:

> Training until now has taken 0 days 0 hours 14 minutes 34 seconds.
### Actual behaviour

Due to the fact that part of the training can be done using multiple cores, when using larger core systems (in my case 24 cores), the difference between the actual processing time and the user time (reported using the embedded linux time tool), differs from the reported time.

> real  11m46.084s
> user  14m18.198s
> sys   0m18.812s

The difference gets bigger if more data is used and if processing takes longer, in the line of hours and days.

I will look into a possible solution, so that the real time is returned instead of the user time generated by counting the clock ticks (which takes into account all the cores available and used).
Repository: kubernetes
Issue: Warn or error when a workload object (eg Deployment) would breach a quota
Labels: priority/backlog,sig/scheduling,sig/architecture,lifecycle/frozen

The quota system, in its current form, doesn't play well with high-level resources such as replication controllers/replica sets/deployments. While quota will correctly not allow my replicaset to scale up to the N pods I have asked for -because N pods may exceed {cpu,memory,pods} quota- the replicaset is blocked in limbo as its desired state has been updated but may never be fulfilled. This has implications for deployments too. A deployment that manages such a replicaset will never complete successfully because the size of the replicaset is not reflecting the reality. It's probably a problem for the user to solve but do we want to do something about it? Can we do something about it?

If this is a dupe of discussion elsewhere, please link it and close this.

@derekwaynecarr @kubernetes/rh-platform-management @bgrant0607
Repository: opencv
Issue: Unable to retrieve depth or points from occipital structure sensor using OpenNI2
Labels: bug,category: videoio,affected: 3.4

### Please state the information for your system
- OpenCV version: 3.1 master from git
- Host OS:  Windows 7
- MSVC 2013 & CMake 3.5
### In which part of the OpenCV library you got the issue?

Examples:
- videoio
### Expected behaviour

Acquisition of depth map and point cloud from sensor
### Actual behaviour

```
Attempted to access nullptr in m_pFrame
    opencv_videoio310d.dll!openni::VideoFrameRef::getWidth() Line 525   C++
>   opencv_videoio310d.dll!getDepthMapFromMetaData(const openni::VideoFrameRef & depthMetaData={...}, cv::Mat & depthMap={...}, int noSampleValue=0, int shadowValue=0) Line 720    C++
    opencv_videoio310d.dll!CvCapture_OpenNI2::retrieveDepthMap() Line 736   C++
    opencv_videoio310d.dll!CvCapture_OpenNI2::retrieveFrame(int outputType=0) Line 876  C++
    opencv_videoio310d.dll!cvRetrieveFrame(CvCapture * capture=0x00000000225427b0, int idx=0) Line 102  C++
    opencv_videoio310d.dll!cv::VideoCapture::retrieve(const cv::_OutputArray & image={...}, int channel=0) Line 630 C++
```
### Additional description

Using an occipital structure sensor (http://structure.io/) with the recommended configuration modification [http://com.occipital.openni.s3.amazonaws.com/Structure%20Sensor%20OpenNI2%20Quick%20Start%20Guide.pdf] I can view the point cloud via the NiViewer, however accessing the camera through the OpenCV interface results in a nullptr access violation.
### Code example to reproduce the issue / Steps to reproduce the issue

``` .cpp
#include "opencv2/videoio.hpp"
#include <iostream>
using namespace std;
using namespace cv;

int main()
{
  cv::VideoCapture cam(1610);
  cv::Mat depth, point_cloud;
  cam.retrieve(depth, CAP_OPENNI_DEPTH_MAP);
  cam.retrieve(point_cloud, CAP_OPENNI_POINT_CLOUD_MAP);
}
```
Repository: kubernetes
Issue: pod status does not reflect 'Reason' codes for failures that one sees when doing kubectl describe pod <podname>
Labels: priority/backlog,sig/scheduling,area/usability,area/kubectl,area/reliability,sig/cli,lifecycle/frozen

When a pod (or rep controller, or service) fails for reason like 'no corresponding docker image' or PodExceedsFreeCPU  we see this when we do  a "pod describe".  I have included the describe output for one of our test runs below.  Notice that the Status for the replication controller is  Pending -- however an event occurred whose corresponding 'Reason' code is FailedScheduling.  

I would argue this is an API usability bug.  The suggested fix would be to add a new enum value to the 'Status' attribute of  resources (like pods, rc's, etc) -- namely  "Failed".

This would make it much easier to manage K8s clusters via REST API's like fabric8.

In fact, I posted a stack overflow question asking how -- using the fabric8 API -- we could find out that a pod (or other resource)  failed to provision correctly. [ http://stackoverflow.com/questions/37020369/best-way-in-kubernetes-to-receive-notifications-of-errors-when-instantiating-res ].     If Kubernetes provided a  "Failed" status, the current implementation of fabric8 API would automatically work better.      And there would be less confusion for users who used kubectl to find out the status of provisioning a resource.

[  PS: we are using k8s version 1.1 ] 

**Describe Output**

```
kubectl describe pod spark-worker-rc-bxkyo
Name:                spark-worker-rc-bxkyo
Namespace:            mervin-mervin-1544803905
Image(s):            ecr.vip.acmec3.com/mousetown/spark-1.5.1:dev
Node:                /
Labels:                name=spark-worker,uses=spark-master
Status:                Pending
Reason:
Message:
IP:
Replication Controllers:    spark-worker-rc (4/4 replicas created)
Containers:
  spark-worker:
    Image:    ecr.vip.acmec3.com/mousetown/spark-1.5.1:dev
    Limits:
      cpu:        4
      memory:        16Gi
    State:        Waiting
    Ready:        False
    Restart Count:    0
Events:
  FirstSeen                LastSeen            Count    From        SubobjectPath    Reason            Message
  Tue, 03 May 2016 12:43:38 -0700    Tue, 03 May 2016 13:38:54 -0700    25    {scheduler }            FailedScheduling    Failed for reason PodFitsHostPorts and possibly others
  Tue, 03 May 2016 12:43:23 -0700    Tue, 03 May 2016 13:40:55 -0700    173    {scheduler }            FailedScheduling    Failed for reason PodExceedsFreeCPU and possibly others 

```
Repository: youtube-dl
Issue: TheVideo.me site support request
Labels: site-support-request

I think that it's a [XFileShare](https://github.com/rg3/youtube-dl/blob/57d8e32a3ec7fe70522edad6fd0c2847b4e00944/youtube_dl/extractor/xfileshare.py) extractor which you can see because it's similar HTML and you can see the form fields (op=download1). I tried it but I couldn't get it work - seems like the `file url` regex does not match. 

Example URL: http://thevideo.me/zo5jqio9my56
Repository: TypeScript
Issue: Overriden class member annotated with a subtype could be a recipe for disaster (by design.. ;) )
Labels: Suggestion,Needs Proposal

**TypeScript Version:** 
`1.9.0-dev.20160505` with both `strictNullChecks` and `noImplicitAny` enabled.

**Code:**

``` ts
class Animal {
    name: string = "Any animal";
}

class Dog extends Animal {
    name: string = "Dog";

    bark() {
        console.log("bark");
    }
}

class AnimalCage {
    member: Animal = new Animal();
}

class DogCage extends AnimalCage {
    member: Dog;
}

let dogCage = new DogCage();

if (dogCage.member != null) { // Yup, it is even checked for null or undefined, 
                              // but it turned out that wasn't enough..
    dogCage.member.bark(); // Bang!
}
```

**Expected behavior:**
Design a language where inheritance actually works.
(_Edit: I was felling very 'passionate' when I wrote this.. sorry :) nothing personal_)

**Actual behavior:** 
By design:

```
    dogCage.member.bark();
                   ^

TypeError: dogCage.member.bark is not a function
    at Object.<anonymous> (C:\X\Documents\Drafts\TypeScript\Code\a.js:38:20)
    at Module._compile (module.js:541:32)
    at Object.Module._extensions..js (module.js:550:10)
    at Module.load (module.js:456:32)
    at tryModuleLoad (module.js:415:12)
    at Function.Module._load (module.js:407:3)
    at Function.Module.runMain (module.js:575:10)
    at startup (node.js:159:18)
    at node.js:444:3
```

**Resolution:**
`tslint` volunteers, for the rescue!
Repository: go
Issue: cmd/compile: support inlining non-escaping closures
Labels: Performance,compiler/runtime

Split out from #9337 and #15537.
Repository: kubernetes
Issue: Kubelet: We should separate status update with SyncPod
Labels: priority/backlog,area/kubelet,sig/node,kind/feature,lifecycle/frozen

As is discussed in https://github.com/kubernetes/kubernetes/issues/19077#issuecomment-216686379.

Now we only update pod status at the beginning of `SyncPod`, so the pod status could never be able to reflect the changes happening in `SyncPod`, for example image pulling progress.

We should separate status update with `SyncPod`, so that we could update pod status whenever we need, and possibly driven by events.

/cc @kubernetes/sig-node
Repository: kubernetes
Issue: Expected behavior for Deployment replicas with HPA during update
Labels: kind/bug,priority/backlog,kind/documentation,area/app-lifecycle,sig/autoscaling,area/workload-api/deployment,sig/cli,lifecycle/frozen

I am seeing unexpected behavior from a user standpoint when `kubectl apply -f mydeployment.yml`

The existing Deployment has an HPA associated with it and the current replica count is 3. When the deployment is accepted, the number of replicas jumps to 9, then scales down to 6, the value in the deployment. Eventually, the new pods info starts flowing in and the HPA does its thing and scales back to satisfaction.

The behavior I expected is that the rollout would use the current replicas from the HPA and the strategy parameters from the Deployment to keep replica count in line with the current target set by the HPA. 

k8s version: 1.2.3

```
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
  name: mydeployment
spec:
  replicas: 6
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxUnavailable: "40%"
      maxSurge: "50%"
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
        - name: myapp
          image: "someimage"
```

```
apiVersion: extensions/v1beta1
kind: HorizontalPodAutoscaler
metadata:
  name: mydeployment
  namespace: default
spec:
  scaleRef:
    kind: Deployment
    name: mydeployment
    subresource: scale
  minReplicas: 3
  maxReplicas: 12
  cpuUtilization:
    targetPercentage: 50
```
Repository: go
Issue: syscall: exec_windows.go: arguments should not be escaped to work with msiexec
Labels: help wanted,OS-Windows,NeedsFix,early-in-cycle

Problem: When I try to run a command in Go on Windows using exec.Command() and then exec.Run(), the arguments are escaped using this logic: https://github.com/golang/go/blob/master/src/syscall/exec_windows.go#L26. That logic escapes the quotes around TARGETDIR="%v" which need to be there. I currently am assigning to Cmd.SysProcAttr manually to get around the escaping.
1. What version of Go are you using (`go version`)?
   Go 1.6.2
2. What operating system and processor architecture are you using (`go env`)?
   Windows 10 Pro x64
3. What did you do?
4. The code is available here, but needs to be run on Windows: https://play.golang.org/p/aU1PlbNTqM
5. Download any MSI. I used https://fastdl.mongodb.org/win32/mongodb-win32-x86_64-2008plus-ssl-3.2.6-signed.msi and renamed it to package.msi.
6. You can run Error() and NoError() to see the difference
7. What did you expect to see?
   I expect to see the MSI say: Completed the ... Setup Wizard.
8. What did you see instead?
   I see the Windows Installer help Windows and when I click it, I get: exit status 1639 which is:
   ERROR_INVALID_COMMAND_LINE 1639 Invalid command line argument. Consult the Windows Installer SDK for detailed command line help.
Repository: rust
Issue: Lint against leading 0 in integer literals
Labels: A-lints,C-feature-request

A literal like `0111` looks like an octal literal in C, but is actually decimal in Rust (octal would be`0o111`). This is [a footgun](http://stackoverflow.com/q/37062143/1256624), and so seems like something that could be trivially checked for.

(I suppose this could be a "clippy" lint, but that seems like it would lose most of the benefit: it seems to me that most people who encounter this will be just starting out, not invested in running external, third-party commands using nightly.)


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"GrigorenkoPV"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: Provide demo of heroes being driven by the transition animation
Labels: c: new feature,framework,f: material design,d: api docs,P3,team-design,triaged-design

![2016-05-05-235622_2560x1440_scrot](https://cloud.githubusercontent.com/assets/551196/15066334/3aae6fb2-131d-11e6-8ce3-d57eac100b20.png)
Repository: go
Issue: cmd/compile: better error message for scoped type error
Labels: NeedsFix,compiler/runtime

1. What version of Go are you using (`go version`)?
   `go version go1.6.2 darwin/amd64`
2. What operating system and processor architecture are you using (`go env`)?

```
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
```
1. What did you do?
   https://play.golang.org/p/pJBsVvubBw
2. What did you expect to see?
   An error message that was clear
3. What did you see instead?
   Spent over an hour figuring out why `type a` was not taking `type a`

I think there should be a better error message for this case, as debugging it was super hard.
Repository: go
Issue: x/build: find new cloud provider for Solaris, Illumos builders?
Labels: help wanted,OS-Solaris,Builders,new-builder

Now that we have SmartOS builders on Joyent in a custom image using the buildlet, let's use the Joyent API and dynamically create the containers as needed. This should be done by creating a new pool type in x/build/cmd/coordinator, similar to the GCE, reverse, and Kubernetes pool types.

This will both be cheaper (run zero when we need zero), but also let us scale from 0 to dozens as needed and let us do sharded builds and let SmartOS be a trybot. (currently we just run 2 containers all the time)

I see lots of joyent stuff at https://godoc.org/?q=joyent 

/cc @davecheney @4ad
Repository: go
Issue: cmd/vet: check for duplicate input to some binary ops
Labels: NeedsDecision,Analysis

[moved from #15570]

@dominikh's [staticcheck](https://github.com/dominikh/go-staticcheck) found some bugs in the standard library -- see #15570. This issue is to consider whether it's worth adding a vet check along the same lines.

The check would be to look for expressions of the form (x BOP x), where:
- x is not of type float
- BOP is one of: & && | || == != - / % ^ &^
- x is a side-effect free expression (see the boolean conditions check)

These expressions are either redundant or have a constant value (with some very rare exceptions, like division and the smallest negative integer), which indicates that they are probably a mistake, and in any case would be better written in another way.

cc @robpike for opinions

cc @valyala in case you are interested in playing with more vet checks :)
Repository: rust
Issue: Unhelpful error message for specialization-related type projection failures.
Labels: C-enhancement,A-diagnostics,T-compiler,F-specialization

Playground: http://is.gd/QMg2a8
Repository: go
Issue: x/net/http2: toggle HPACK dynamic table indexing for header
Labels: FeatureRequest

Often a service will have certain header fields that have no discernible repeatable pattern (or the possible combinations far outnumber the HPACK table slots). It would be good to be able to turn off HPACK for those headers so that these non-repeating values don't use up slots in the dynamic table.

Here's a quote from [Apple's APNs documentation](https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptual/RemoteNotificationsPG/Chapters/APNsProviderAPI.html) touching on this:

> APNs requires the use of HPACK (header compression for HTTP/2), which prevents repeated header keys and values. APNs maintains a small dynamic table for HPACK. To help avoid filling up the APNs HPACK table and necessitating the discarding of table data, encode headers in the following way—especially when sending a large number of streams:
> - The `:path` header should be encoded as a literal header field without indexing,
> - The `apns-id` and `apns-expiration` headers should be encoded differently depending on initial or subsequent POST operation, as follows:
>   - The first time you send these headers, encode them with incremental indexing to allow the header names to be added to the dynamic table
>   - Subsequent times you send these headers, encode them as literal header fields without indexing
Repository: kubernetes
Issue: Requirements for multi-scheduler to graduate to Beta and then v1
Labels: sig/scheduling,lifecycle/frozen

We'd like to graduate multi-scheduler to Beta in 1.4.

Beta
- [ ] Change annotation key from `scheduler.alpha.kubernetes.io/name` to `scheduler.beta.kubernetes.io/name`
- [ ] Make sure we have a rollback story or are sure we won't need to rollback earlier than when feature was first introduced

v1
- [ ] Change annotation key from `scheduler.beta.kubernetes.io/name` to `scheduler.kubernetes.io/name`

The design doc has some suggestions for "next steps" and we should incorporate any of those that we actually want to do into "Beta," but I'm not sure any of them are necessary?

ETA: Previously we had "Implement [MetadataPolicy](https://github.com/kubernetes/kubernetes/blob/master/docs/design/metadata-policy.md)" for Beta and "Use initializer pattern in MetadataPolicy" but I think we can separate that from this feature.

cc/ @HaiyangDING @bgrant0607 

ref/ #17865 #18262
Repository: kubernetes
Issue: Requirements for Affinity to graduate to Beta and then v1
Labels: priority/important-soon,sig/scalability,sig/scheduling,lifecycle/frozen

We'd like to graduate node and pod affinity to Beta in 1.4.

Beta
- [x] Change annotation key from `scheduler.alpha.kubernetes.io/affinity` to `scheduler.beta.kubernetes.io/affinity`
- [x] Make performance of pod affinity acceptable (#26144) (and verify that performance of node affinity is acceptable)
- [x] Better solution for "first pod problem"
- [ ] Last bullet point here https://github.com/kubernetes/kubernetes/pull/22985#issuecomment-216020283
- [ ] Before allowing users to use it, be sure we won't need to roll back to binary version that doesn't support it
- [x] Re-enable/fix all tests (see e.g. #26697, #26698)

v1
- [x] Move Affinity to be a field in PodSpec
- [ ] Implement RequiredDuringExecution
- [ ] Incorporate feedback from users of Beta

Better solution for DoS issues? (or just rely on priority/preemption when we have it?) (see https://github.com/kubernetes/kubernetes/pull/18265#issuecomment-172142482)

cc/ @kevin-wangzefeng @bgrant0607 @wojtek-t 

ref/ #18261 #18265 #24853 #22985 #19758
Repository: youtube-dl
Issue: site support: likeafool
Labels: site-support-request

- [x] I've **verified** and **I assure** that I'm running youtube-dl **2016.05.01**
### 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

---
- Single video: http://www.likeafool.com/video/13799/moose-unexpectedly-gives-birth-to-twins
- http://www.likeafool.com/files/a7f28614a5c01cbb28b62df08871bc19
Repository: TypeScript
Issue: Make default JSX mode "react"
Labels: Suggestion,Help Wanted,Good First Issue

To enable JSX syntax in TypeScript you need two steps:
- add `"jsx": "react"` to `"compilerOptions"` in `tsconfig.json`
- use `.tsx` extension

This is quite troublesome if you want to reuse certain generators/boilerplates/build scripts for us. It is also against the single source of truth principle and can be confusing. I recently stumbled over a bug where we used the `.tsx` extension, but hadn't configured the `tsconfig.json`.

There was a lot of discussion recently about changing the `.js` extension to `.mjs` to introduce ES6 modules to Node and many people are against that and prefer to have an additional flag in the `package.json`.
I'd like to see the same for TypeScript and JSX:
- the `.tsx` extension is purely optional
- only `"jsx": "react"` in `tsconfig.json` is mandatory