sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: bug(animations) nested animations don't work properly when switching between states
Labels: type: bug/fix,area: animations,freq2: medium,P3

## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:
</code></pre>

## Current behavior
Nested animations don't work properly when switching between states

## Expected behavior
Nested animations should always work.

## Minimal reproduction of the problem with instructions
Working (without swithing between states ; with *ngIf): 
https://stackblitz.com/edit/angular-sev2pq?file=src%2Fapp%2Fapp.component.html

Not working (switching between states): 
https://stackblitz.com/edit/angular-skyqmo?file=src%2Fapp%2Fapp.component.html

## What is the motivation / use case for changing the behavior?

## Environment

<pre><code>
Angular version: X.Y.Z
<!-- Check whether this is still an issue in the most recent Angular version -->

Browser:
- [x] Chrome (desktop) version 68
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX

Others:
<!-- Anything else relevant?  Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
Repository: vue
Issue: Typescript - Component's property types are not correct
Labels: typescript

### Version
Vuejs: 2.5.16
Typescript: 2.8.1

### Reproduction link
[https://stackblitz.com/edit/typescript-rrnw8z?file=index.ts](https://stackblitz.com/edit/typescript-rrnw8z?file=index.ts)

### Steps to reproduce
- Use typescript
- Create a component with at least one property

### What is expected?
If your property of type `X` is not required, its type should be `X | undefined`

### What is actually happening?
If your property of type `X` is not required, its type is still `X`

---
More dangerous: The properties are not required by default and you can easily write code that will fail at runtime.

Note: The stackblitz above won't show the error because the types are not correctly assumed and `this` is assumed as `any`

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: pytorch
Issue: RNN gradients in eval mode in pytorch 0.4
Labels: module: nn,module: rnn,triaged

I need to be able to compute the gradients of an RNN with dropout temporarily turned off. In earlier versions if pytorch, it was possible to do this just by setting model.eval() and calling loss.backward(), but in pytorch 0.4 I get this error message:

```
Traceback (most recent call last):
  File "dynamiceval.py", line 271, in <module>
    gradstat()
  File "dynamiceval.py", line 137, in gradstat
    loss.backward()
  File "/opt/conda/envs/pytorch04/lib/python3.6/site-packages/torch/tensor.py", line 93, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "/opt/conda/envs/pytorch04/lib/python3.6/site-packages/torch/autograd/__init__.py", line 90, in backward
    allow_unreachable=True)  # allow_unreachable flag
RuntimeError: cudnn RNN backward can only be called in training mode
```

Is there or could there be any work around that allows for dropout to be temporarily turned off, and still allow for gradients to be computed?

Thanks!
Repository: pytorch
Issue: Upgrade Caffe2 Hypothesis
Labels: caffe2

Currently, we are pegged on Hypothesis 3.59.0 as per https://github.com/pytorch/pytorch/pull/9830

This is bad, we should endeavor to take updates of the versions of our dependencies on a timely basis.

Unfortunately, the new version of Hypothesis has some behavior changes which cause previously stable tests to start flaking. Known cases: https://github.com/pytorch/pytorch/issues/9854 https://github.com/pytorch/pytorch/issues/9853 https://github.com/pytorch/pytorch/issues/9833 https://github.com/pytorch/pytorch/issues/9832

These need to be fixed before we can upgrade.
Repository: flutter
Issue: Improved Image Widget
Labels: c: new feature,framework,a: images,P3,team-framework,triaged-framework

The current Image implementations has a series of disadvantages that should be improved:

- Image.network if the URL isn't available there is no chance to react on that. We should offer an errorBuilder that fills the image space if an loading error occurs or at least offer an error place holder Image that will be dispalyed in that case. a general Builder would be more flexible.

- There is no loading placeholder which could optimal be a builder too so it could even play some animation during image load time.
- We should be able to define how long images are cached and if on disk or in memory
- I don't know how it is currently implemented but are images scaled down before caching? 

As an inspiration I can only recommend https://github.com/luberda-molinet/FFImageLoading  an awesome Xamarin image library
Repository: flutter
Issue: Code samples for how to use tabBar with flexibleSpace in an AppBar
Labels: team,framework,f: material design,d: api docs,d: examples,P2,team-design,triaged-design

The AppBar documentation doesn't show how to get these fields to interact well: FlexibleSpace shows 'behind' the TabBar, so it can make more sense to put the TabBar into the FlexibleSpace.

We should add a code sample to the AppBar documentation that illustrates how to do this.
Repository: rust
Issue: Variadic C function calls don't decay references to pointers as other function types do
Labels: A-FFI,T-lang,C-bug

It seems like calling a variadic C function doesn't hold the exact same rules for reference to pointer conversions as does calling a regular function:

```rust
fn bar(_a: *mut i32, _b: *mut i32) {}
extern "C" fn bar2(_a: *mut i32, _b: *mut i32) {}

extern crate libc; // 0.2.42

extern "C" {
    #[no_mangle]
    fn sscanf(_: *const libc::c_char, _: *const libc::c_char, ...) -> libc::c_int;
}

fn main() {
    let mut i: libc::c_int = 1i32;
    let k: *mut libc::c_int = &mut i;
    let mut l: [libc::c_int; 2] = [0; 2];

    unsafe {
        sscanf(k as *const libc::c_char,
               b"%u,%u\x00" as *const u8 as *const libc::c_char,
               &mut l[0usize],
               &mut l[1usize]); // Err
    }

    let mut x = 1;
    bar(&mut x, &mut x); // Ok
    bar(&mut l[0], &mut l[1]); // Ok
    bar2(&mut l[0], &mut l[1]); // Ok
}
```

([Playground](https://play.rust-lang.org/?gist=caa2db63af71f98f07b969e272a844fe&version=stable&mode=debug&edition=2015))

Errors:

```rust
   Compiling playground v0.0.1 (file:///playground)
error[E0499]: cannot borrow `l[..]` as mutable more than once at a time
  --> src/main.rs:20:21
   |
19 |                &mut l[0usize],
   |                     --------- first mutable borrow occurs here
20 |                &mut l[1usize]);
   |                     ^^^^^^^^^- first borrow ends here
   |                     |
   |                     second mutable borrow occurs here

error: aborting due to previous error

For more information about this error, try `rustc --explain E0499`.
error: Could not compile `playground`.

To learn more, run the command again with --verbose.

```

In this example, calls to `bar` (rust fn) and `bar2` (extern "C" fn) will convert the mutable references to pointers implicitly, and so they succeed at compiling even though they would not normally if the signature took mutable references per rust's standard rules.

Obviously because `sscanf` is variadic, it doesn't specify pointer types in its signature. I nevertheless expected the call to compile because `sscanf` is extern "C" and rust references should decay to C pointers.

The work around is to explicitly cast the `sscanf` references to pointers.
Repository: go
Issue: cmd/gofmt: unfinished else statement followed by if statement should maybe have indentation
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

```
go version go1.10.2 darwin/amd64
```

### Does this issue reproduce with the latest release?

Yep

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/matt/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/matt/Dev"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/d4/3d8k5bgd62v9h2c5f05xkyx80000gn/T/go-build921281437=/tmp/go-build -gno-record-gcc-switches -fno-common"
```

### What did you do?

Started writing an `else` statement but got distracted fixing an issue elsewhere in the program and didn't finish the statement. Definitely my bad! However, gofmt [made this bug a little harder to find](https://twitter.com/mholt6/status/1023663407323467776):

https://play.golang.org/p/AdIDE1dT9Sd

Notice that the next statement is an `if`, with a comment between them. Because of the comment. `go fmt` didn't move the `if` up to the line with the `else`. That seems correct, however, since it is technically a continuation of the `else`, indenting the `if` would have been helpful for catching it.

### What did you expect to see?

```
...
	} else

		// unfinished statement above
		if b == 2 {
			fmt.Println("b is 2")
		}
...
```

### What did you see instead?

```
...
	} else

	// unfinished statement above
	if b == 2 {
		fmt.Println("b is 2")
	}
...
```

This is just a proposed enhancement -- not urgent, and definitely still my fault for not finishing a line I started -- but if `gofmt` could figure this out and cue me in by indenting, that would be helpful. :)


Edit: Seems similar to https://github.com/golang/go/issues/20562 -- at least one of the comments there mentions the same issue, it looks like. Feel free to close if you think this is a duplicate. I can't quite tell if that's a separate formatting issue originally...
Repository: go
Issue: net/http: PUT: DefaultClient significantly slower than DefaultTransport when network is slow
Labels: Performance,NeedsInvestigation

**What version of Go are you using (go version)?**
go version go1.10.3 darwin/amd64

**Does this issue reproduce with the latest release?**
yes

**What operating system and processor architecture are you using (go env)?**
GOARCH="amd64"
GOBIN="/Users/test/go/bin"
GOCACHE="/Users/test/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/test/go"
GORACE=""
GOROOT="/usr/local/Cellar/go/1.10.3/libexec"
GOTMPDIR=""
GOTOOLDIR="/usr/local/Cellar/go/1.10.3/libexec/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/76/trlnwqwj0bs5003x850kzpg00000gn/T/go-build781190647=/tmp/go-build -gno-record-gcc-switches -fno-common"

**Scenario:**
I have a network with Download speed :400kbit/s Upload:400kbit/s RTT:200ms
I have http client developed in Golang. 
Wanted to transfer 1MB file to a web server.

**What did you expect to see?**
File upload must almost be same to curl or other web clients.

**What did you see instead?**
Curl took ~28s
Go client took ~42s


**More Information on environment, tools:**
How does Go react when there are issues with network.
To mimic network delay - https://github.com/sitespeedio/throttle

web server : https://github.com/sashgorokhov/docker-nginx-webdav

Source Code
```go

package main

import (
  
   "io/ioutil"
   "time"
   "fmt"
   "net/http"
   "strings"
  
)

func main() {

   client := &http.Client{}
   url := "http://localhost:9080/file.txt"
   rb, _ := ioutil.ReadFile("file1mb.txt")
   request, err := http.NewRequest("PUT", url, strings.NewReader(string(rb)))
   //request.ContentLength = int64(len(string(rb)))
   sTime := time.Now()
   response, err := client.Do(request)
   eTime := time.Since(sTime)
   fmt.Println(eTime.String())
   if err != nil {
      fmt.Println(err)
   } else {
      fmt.Println(request.Header)
      defer response.Body.Close()
      fmt.Println(response.Status)
    }
}

```

Tried with and without Content-Length header(chunked encoding) in the http request.


My concern is for 1mb file I see a difference what if file size is 100MB+?
Repository: godot
Issue: Unable to Force Update 2D UI Controls before Next Frame
Labels: enhancement,topic:gui

**Godot version:**
3.0.5

**OS/device including version:**
All

**Issue description:**
Other game engines have a way to force components to update after new data is set.  Godot seems unable to do this.  

For example: setting text in a wordwrapped Label and finding the new vertical size, adding children to VBoxContainer.  Then, using that new size to position the control (for example, moving a VBoxContainer based on it's size).

If we have to wait for the next frame to find out what new sizes/etc our controls are, then we have one frame of visual glitchiness to contend with.  And that can be multiplied for however many times you need to be changing controls.  On some systems the framerate is so fast I can't see the glitches, but on most devices I've used they are very apparent.  I've had to resort to hacks, like taking parts of the background, and pasting them again to hide the glitches, keeping an hidden clone and switching back and forth, but this shouldn't need to be done and eventually becomes cumbersome.

All of this can be fixed by have a means to force a cascading update.
Repository: pytorch
Issue: Sparse tensor use cases
Labels: module: sparse,feature,triaged

We are working on to increase supports for sparse tensor. Currently we have [summarized current state of sparse tensor](https://github.com/pytorch/pytorch/issues/9674) and listed out [sparse ops to support](https://github.com/pytorch/pytorch/issues/8853). We would like to collect sparse tensor use cases to facilitate the design decisions and prioritize TODO list according. It will be very helpful if you can post your use cases and desired sparse ops here or at the [PyTorch Forum](https://discuss.pytorch.org/t/sparse-tensor-use-cases/22047). Thanks! 

I find these questions useful when writing use cases:
- Where do I need sparse tensor? During training deep learning model?
- Do I need autograd support for the sparse ops?

A possible example will be:

I am training model that has `mul(Sparse, Dense)` ops. I would like to have its forward and backward. I know there will be a dense gradient at the backward of `mul`, so here I am asking for a special kind of `mul` ops (called `sparse_mul`) that returns a sparse grad tensor and only keep the nnz's gradients.
Repository: TypeScript
Issue: type.isLiteral() returns false for boolean literals
Labels: Bug,Help Wanted,API

**TypeScript Version:** 3.1.0-dev.20180728 (new in 3.0.1)

**Search Terms:** isLiteral()

**Code**

1. Create a boolean literal in the compiler api.
2. Call `isLiteral()` on it.

Change seems to be done here:

https://github.com/Microsoft/TypeScript/commit/e46d214fceb72cc76145779543bf871ce9ff66b0#diff-233e1126c0abc811c4098757f9e4516eR428

**Expected behavior:** `true` for a boolean literal type (`true` or `false`)

**Actual behavior:** `false`

I have a few tests for assumptions about the compiler api in ts-simple-ast and this one started failing. Maybe it's not a bug, but I thought I would log it anyway to find out why this behaviour changed.

Is it because it doesn't have the `Unit` flag while string and number literals do?  For what it's worth, in *checker.ts* it will internally return `true` for boolean literals in `isLiteralType`.
Repository: opencv
Issue: timestamp = cap.get(CV_CAP_PROP_POS_MSEC) always returns the same timestamp.
Labels: category: videoio,incomplete,needs reproducer,needs investigation

OpenCV 3.40
Centos 7
GCC compiler

I am trying to fetch the video timestamp but it is always giving me 40 and does not change as i move in frames. Is this a bug ?

```
                width = cap.get(CV_CAP_PROP_FRAME_WIDTH);//1280
                height = cap.get(CV_CAP_PROP_FRAME_HEIGHT);//720
                timestamp = cap.get(CV_CAP_PROP_POS_MSEC);//always 40
                fps = cap.get(CV_CAP_PROP_FPS);//25
```
Repository: TypeScript
Issue: comments before imports are stripped in AMD output unless there's a blank line after them
Labels: Bug,Domain: Comment Emit

**TypeScript Version:**  3.0.1

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** preserve comments removes comments

**Code**
Compile the following with `--module amd`

```ts
// foo
import 'foo';

console.log('hi');
```

**Expected behavior:**
output contains `// foo`

**Actual behavior:**
output does not contain `// foo`.

If a newline is added between `// foo` and the `import 'foo'`, the comment will then show up in the output.  If the file is compiled with `--module commonjs`, the comment will also show up in the output, in that case regardless of the whitespace.

**Playground Link:** https://www.typescriptlang.org/play/#src=%2F%2F%20foo%0D%0Aimport%20'foo'%3B%0D%0A%0D%0Aconsole.log('hi')%3B%0D%0A

**Related Issues:** this looks most similar to #6399
Repository: kubernetes
Issue: Eviction should be able to request eviction asynchronously
Labels: priority/backlog,sig/node,kind/feature,sig/apps,lifecycle/frozen

**Is this a BUG REPORT or FEATURE REQUEST?**:
/kind feature

**What happened**:
`kubectl drain` got stuck because we had PodDisruptionBudget (PDB) with `spec.minAvailable: 1` and the deployment only had one replica -> allowed disruptions was always 0.

**What you expected to happen**:
Instead of `kubectl drain` getting stuck, it should activly start a new pod on a different node if the deployment allows for it (deployment.spec.strategy.rollingUpdate.maxSurge). This should be built into to eviction API.
If a missconfiguration of PodDisruptionBudget prevents a drain, `kubectl drain` or the eviction API should warn about it.

**How to reproduce it (as minimally and precisely as possible)**:
- Create a deployment with `spec.replicas: 1`
- Create PDB with `spec.minAvailable: 1` and select the pod of the deployment
- Try to evict the pod from its node via eviction api or `kubectl drain`

**Environment**:
- Kubernetes version (use `kubectl version`): 1.10.5
Repository: rust
Issue: Should std::{f32,f64}::NAN be a QNAN or SNAN ?
Labels: T-libs-api,A-docs,A-floating-point

Right now, whether they are a QNAN or an SNAN depends on the architecture. Currently, they are an SNAN on MIPS (EDIT: r5 and older) at least, and a QNAN on most others.

It probably makes sense to offer consistent behavior here independently of whether LLVM preservers payloads, signaling/quietness, etc.

cc @rkruppe @draganmladjenovic
Repository: vscode
Issue: Disable undo menu item when there is no more history available
Labels: feature-request,menus,undo-redo

From #55389

**Feature request**
Disable the undo menu item if there is no undo history available. 

(same for redo if there is no more forward history)
Repository: go
Issue: cmd/gofmt: Remove redundant parenthesis in foo = (1 << 42)
Labels: NeedsInvestigation,FeatureRequest

go version go1.10.3 linux/amd64

Reviewing CLs showed lists of const bit-masks that were foo = 1 << 42, etc., all had redundant parenthesis around the (1 << 42).  The author said they were copying similar ones in existing source.  gofmt doesn't remove them.  It does remove the outer pair of double ones, i.e. ((1 << 314)) in https://play.golang.org/p/V6jz7iKHJwt

I think simple cases like foo = (1 << 42) can always have them removed.  That's the style followed by most of the stdlib, but not all.  Having pointed it out on the CL, Martin Möhrmann is fixing those other cases that influenced the author, e.g. https://go-review.googlesource.com/126775, but it would be nice if gofmt avoided the possibility.
Repository: flutter
Issue: URL_Launcher OnDismiss Callback or Listener
Labels: c: new feature,p: url_launcher,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

There currently isn't a way to tell when the SFSafariViewController is dismissed. It seems necessary when certain actions need to be carried out afterwards.
Repository: pytorch
Issue: UnicodeDecodeError while loading caffe2 model
Labels: caffe2

If you have a question or would like help and support, please ask at our
[forums](https://discuss.pytorch.org/).

If you are submitting a feature request, please preface the title with [feature request].
If you are submitting a bug report, please fill in the following details.

## Issue description

Provide a short description.

## Code example

Please try to provide a minimal example to repro the bug.
Error messages and stack traces are also helpful.

## System Info
Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```

- PyTorch or Caffe2:
- How you installed PyTorch (conda, pip, source):
- Build command you used (if compiling from source):
- OS:
- PyTorch version:
- Python version:
- CUDA/cuDNN version:
- GPU models and configuration:
- GCC version (if compiling from source):
- CMake version:
- Versions of any other relevant libraries:
Repository: go
Issue: cmd/doc: add example support
Labels: Proposal-Accepted,NeedsFix,FeatureRequest

To go along with #25443, #25595, and #18807, it would be nice to get support for `godoc`'s `-ex` flag in `go doc`.
Repository: go
Issue: cmd/go: add a facility to peek into the module cache
Labels: NeedsDecision,FeatureRequest,modules

cc: @rsc @bcmills @suzmue @ianthehat

To work with modules, a tool like goimports should be aware of the set of modules in the module cache. Then, it could suggest packages that haven't been required in go.mod or imported by a package or its deps. At the least, it should be able to list the latest version of each module in the user's module cache. (And if `GOPROXY` is set, it should be able to list the latest version of the modules served by the proxy.) 

Currently there doesn't seem to be a way for a tool like goimports to suggest packages outside the transitive module dependencies of the current module without guessing the module cache directory (which is changing: [golang.org/cl/126755](golang.org/cl/126755)) and then crawling through the directories. It seems like the directory layout may be stable but finding the directory is a bit dodgy. And we'd need to handle `goproxy` manually too.

go/packages has been using `go list` to find metadata about packages, so ideally we could use `go list` or maybe `go mod` to get at this information. But maybe there's a better way to get at it.