sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: Animations jump around during router-outlet transitions
Labels: type: bug/fix,area: animations,freq1: low,P4

<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.

ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->

## 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 -->
[ ] 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
</code></pre>

## Current behavior
<!-- Describe how the issue manifests. -->
When switching router pages by clicking navigation links(Projects<-->Users), the leaving component instantly teleports below where the entering component would be, creating a disjointing appearance during animation.

## Expected behavior
<!-- Describe what the desired behavior would be. -->
The leaving component should leave from its current position and not teleport anywhere unless specified in the animations metadata. The desired behavior is to create a seamless transition. 

## Minimal reproduction of the problem with instructions
<!--
For bug reports please provide the *STEPS TO REPRODUCE* and if possible a *MINIMAL DEMO* of the problem via
-->
https://stackblitz.com/edit/angular-fjxwoq?file=styling-assignment%2Fapp.component.ts

## What is the motivation / use case for changing the behavior?
<!-- Describe the motivation or the concrete use case. -->
To create a seamless transition for animating between router pages.

## Environment

<pre><code>
Angular version: 5.2.8
Angular Animations: 5.2.9
<!-- Check whether this is still an issue in the most recent Angular version -->

Browser:
- [X ] Chrome (desktop) version XX
- [ ] 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
 
For Tooling issues:
- Node version: 9.5.0 
- Platform:  Windows 7 
</code></pre>

Others:
<!-- Anything else relevant?  Operating system version, IDE, package manager, HTTP server, ... -->
I've tried using position:'fixed' in the hosting components and while the the disjointing is fixed, the end state results in a disappearing component.  If I add style({transform:'translateY(-100%)'}) to the leaving component, leaving users page appears smooth but that means leaving another page(Servers) with a greater height looks terrible.
Repository: flutter
Issue: Add a performance watchdog / diagnosis tool
Labels: c: new feature,tool,framework,c: performance,P2,team-framework,triaged-framework

Some sort of low-invasiveness profile runtime tool like https://developers.google.com/speed/pagespeed/insights/ that can print hints to console or to a formatted file. 

Example outputs:

- Widget subtree descendent of widget X exceeded 5ms during build time. `build()` call site: Y. Widget subtree: Z. 
- The same widget subtree was rebuilt X times consecutively and hasn't changed. Call site: Y. Consider avoiding unnecessary rebuilds.
- Widget rebuilds exceeding 2ms was triggered more than X consecutive times as result of a ScrollNotification listener or while laying out a RenderViewport subclass. Consider Y
- The same render object subtree was repainted X times consecutively and hasn't changed its content of Y complexity. Consider using a RepaintBoundary at Z or use W. 

etc etc.
Repository: flutter
Issue: Document how centerSlice works, and how to use .9.png images with Flutter, with samples
Labels: c: crash,framework,d: api docs,customer: alibaba,a: images,P2,team-framework,triaged-framework

## Steps to Reproduce
I'm trying to use a .nine picture:
![image](https://user-images.githubusercontent.com/454020/38142129-d3e1c10c-346d-11e8-82af-78a1f75849d8.png)

The Code:
```dart
return new Stack(children: <Widget>[
      new Positioned(
          child: new Image.asset("images/label_bg_left_9.png",
              fit: BoxFit.fill,
              centerSlice: new Rect.fromLTRB(6.0, 1.0, 17.0, 49.0)),
          left: 0.0,
          right: 0.0,
          top: 0.0,
          bottom: 0.0),
      new Container(
          child: new Text("#" + label.text,
              style: new TextStyle(fontSize: 12.0, color: Colors.white),
              textAlign: TextAlign.center),
          padding: const EdgeInsets.fromLTRB(2.0, 2.0, 32.0, 2.0))
    ]);
```

I got an wrong image like this, the right side was expanded:
![image](https://user-images.githubusercontent.com/454020/38142209-10528a5e-346e-11e8-88bc-37f98591d756.png)
Do you know why I got this problem?

The expected result should be like this:
![image](https://user-images.githubusercontent.com/454020/38142239-2a04633c-346e-11e8-88ed-25ce61d14771.png)


## Flutter Doctor
The flutter is modified by myself, forked from the Flutter beta branch v0.1.5. The modifications I made may not affect this problem, only for my compile errors.

```
[✓] Flutter (Channel unknown, v0.1.6-pre.24, on Mac OS X 10.12.6 16G1212, locale zh-Hans-HK)
    • Flutter version 0.1.6-pre.24 at /Users/guoyou/projects/fwn_idlefish/flutter
    • Framework revision 14b5b6f63a (15 hours ago), 2018-03-30 08:08:43 +0800
    • Engine revision ead227f118
    • Dart version 2.0.0-dev.28.0.flutter-0b4f01f759

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/guoyou/Library/Android/sdk
    • Android NDK at /Users/guoyou/Library/Android/sdk/ndk-bundle
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)

[✓] iOS toolchain - develop for iOS devices (Xcode 9.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.1, Build version 9B55
    • ios-deploy 1.9.2
    • CocoaPods version 1.3.0

[✓] Android Studio (version 3.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b08)

[✓] IntelliJ IDEA Community Edition (version 2017.2.3)
    • Flutter plugin installed
    • Dart plugin version 172.3968.27

[!] Connected devices
    ! No devices available
```
Repository: rust
Issue: Salvage clone shim cleanup and carry it to completion
Labels: C-cleanup,A-codegen,I-compiletime,T-compiler,A-MIR,WG-llvm

Cc @rust-lang/wg-codegen @rust-lang/wg-compiler-performance 

#48063
Repository: rust
Issue: Add compiler-internal lints
Labels: A-lints,E-mentor,T-compiler,E-help-wanted,C-tracking-issue,A-contributor-roadblock,S-tracking-impl-incomplete

There are various "patterns" we don't want in the compiler out of one reason or another. I'm using this issue to collect them and create lints for detecting those patterns. The lints will only be available while building the compiler via a -Z flag. The flag will be enabled by the bootstrap script, so we don't have to worry about accidentally running them for users.

* [x] forbid uses of `HashSet` or `HashMap` (suggest `FxHash*`)
* [ ] suggest using `TyCtxtAt` over `TyCtxt` + `Span` as arguments
* [ ] calling `clone` on `Copy` types (https://github.com/rust-lang/rust/issues/27266)
* [ ] do not use `features_untracked` when a tcx is in scope
* [x] do not use `TyKind::Foo`, use `ty::Foo` instead
* [x] do not use `TyKind` as a type outside the `sty` module, use `Ty` instead
* [ ] don't use `TyS` outside `rustc::ty::sty`
* [ ] don't use `Vec::new()` use `vec![]`
* [x] don't use `==` for span contexts, use `eq_ctxt` instead (https://github.com/rust-lang/rust/pull/116787)
* [ ] prefer `param_env_reveal_all_normalized` over `parram_env(did).with_reveal_all_normalized()` (https://github.com/rust-lang/rust/pull/121387#issuecomment-1963666972)
* [ ] require `'tcx` to be the last lifetime in generic args of type decls, functions and impls (see #130294) https://github.com/rust-lang/rust/labels/E-easy
* [ ] forbid storing a `TyCtxt` and a `Session` in the same struct or use both in function args. Only use tcx  https://github.com/rust-lang/rust/labels/E-easy
Repository: rust
Issue: doctests marked with 'no_run' permit ICEs
Labels: T-rustdoc,C-bug,A-doctests

irc discussion: https://botbot.me/mozilla/rust-docs/2018-03-30/?msg=98430464&page=1

run this example: https://doc.rust-lang.org/nightly/std/fs/fn.read_string.html

at the time of writing it ICEs, but doctests don't catch it because it's marked `no_run`
Repository: pytorch
Issue: Test suite should test implementations
Labels: module: tests,triaged

This issue was prompted by #6132. To explain the situation, let us consider the situation of convolution.

Today, we have a number of tests for convolution. The majority of these tests go through the "official" convolution interface, which is what all of our users use. However, inside the implementation of convolution, there are a large number of if-statements which specify which particular implementation we use, depending on some settings. This too, is also a good idea, because we want our users to get the best kernels without thinking about it.

However, when it comes time to test these kernels, we now have some very ugly code:

```
                # test that forwards of module runs correctly without cuDNN
                if self.cudnn:
                    with torch.backends.cudnn.flags(enabled=False):
                        module(input)
                        for p in module.parameters():
                            test_case.assertIsInstance(p, torch.cuda.FloatTensor)
                            test_case.assertEqual(p.get_device(), 0)
```

Essentially, we need to *indirectly* force the dispatch code one way or another, to make sure we test all of the actual kernel implementations. This makes it very easy to miss test configurations where you (a) forget to toggle between implementations or (b) the toggling code is wrong and you're not exercising a codepath that you actually wanted to test.

The basic situation is that there are two orthogonal things we want to test:

1. An integration test: we want to test that the actual function all of our users use for convolution actually works.
2. An implementation test: we want to test that each of our individual kernels is correct.

The current test suite conflates the two. It would be good if it did not.
Repository: pytorch
Issue: [feature request] SIGNUM an optimizer that takes the sign of gradient or momentum.
Labels: module: optimizer,triaged

The SIGNUM is an optimizer that takes the sign of gradient or momentum.
Please see the detailed description of SIGNUM in the original paper at: https://arxiv.org/abs/1802.04434

I would like to start the process of a feature request if accepted by the community.And I am willing to create a pull request and implement the code after discussion.

cc @vincentqb
Repository: rust
Issue: macros can observe raw identifier state [discuss]
Labels: A-macros,T-compiler,C-feature-request,WG-epoch

In https://github.com/rust-lang/rust/pull/48942, @Lymia landed raw identifiers; "equality" in this implementation includes observing the "raw" state. Therefore, macros can observe if `r#foo` was used or not:

```rust
#![feature(raw_identifiers)]

macro_rules! foo {
    (a) => {
        1
    };
    
    (r#a) => { 2 };
}

fn main() {
    println!("{}", foo!(a));
    println!("{}", foo!(r#a));
}
```

This makes a certain measure of sense, but also makes me nervous, and I wanted to open an issue to discuss. For example, @Manishearth proposed making identifiers "raw" in macros when they are serialized, thus ensuring consistent interpretation as we cross editions. 

I'm not entirely sure of the implications of this but it does make me nervous for users to be able to distinguish `foo` and `r#foo`.
Repository: rust
Issue: Error message gives a (depreciated/unimplemented) -Z flag
Labels: C-enhancement,A-diagnostics,T-compiler,T-cargo,D-confusing

Currently, when a macro fails, it gives this error:

```
note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
```

However, when running this:

```
cargo run -Z external-macro-backtrace
```

This error is given:

```
error: unknown `-Z` flag specified: external-macro-backtrace
```

version: 1.26.0-nightly (2018-03-19)
Repository: rust
Issue: Suboptimal inlining decisions
Labels: C-enhancement,A-codegen,T-compiler,WG-llvm

I suspect this can happen in more cases, but here is how I observed this:
```rust
pub fn foo() -> Box<[u8]> {
    vec![0].into_boxed_slice()
}
```

This compiles to:
```asm
  sub rsp, 56
  lea rdx, [rsp + 8]
  mov edi, 1
  mov esi, 1
  call __rust_alloc@PLT
  test rax, rax
  je .LBB2_1
  mov byte ptr [rax], 0
  mov edx, 1
  add rsp, 56
  ret
.LBB2_1:
  (snip oom handling)
```

Which is pretty much to the point.

Now duplicate the function, so that you now have two functions calling `into_boxed_slice()`, and the compiler decides not to inline it at all anymore. Which:
- adds the full blown `Vec::into_boxed_slice` implementation (63 lines of assembly)
- adds `ptr::drop_in_place`
- and changes the function above to:
```asm
  sub rsp, 56
  lea rdx, [rsp + 8]
  mov edi, 1
  mov esi, 1
  call __rust_alloc@PLT
  test rax, rax
  je .LBB4_1
  mov byte ptr [rax], 0
  mov qword ptr [rsp + 8], rax
  mov qword ptr [rsp + 16], 1
  mov qword ptr [rsp + 24], 1
  lea rdi, [rsp + 8]
  call <alloc::vec::Vec<T>>::into_boxed_slice
  add rsp, 56
  ret
.LBB4_1:
  (snip oom handling)
```

The threshold to stop inlining seems pretty low for this particular case, and even if it might make sense for some uses across the codebase to not be inlined, when the result of inlining is clearly beneficial, it would be good if we could still inline the calls where it's a win.
Repository: nvm
Issue: nvm says 'no .nvmrc file found' when the problem is that the version inside of said .nvmrc is not installed.
Labels: bugs,pull request wanted

 
- Operating system and version:
CentOS 7, nvm latest version
- `nvm debug` output:
<details>
<!-- do not delete the following blank line -->

```sh
$SHELL: /bin/bash
$HOME: /home/kenny
$NVM_DIR: '$HOME/.nvm'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 4.2.46(2)-release (x86_64-redhat-linux-gnu)'
uname -a: 'Linux 3.10.0-693.21.1.el7.x86_64 #1 SMP Wed Mar 7 19:03:37 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux'
OS version:
curl: /bin/curl, curl 7.29.0 (x86_64-redhat-linux-gnu) libcurl/7.29.0 NSS/3.28.4 zlib/1.2.7 libidn/1.28 libssh2/1.4.3
wget: /bin/wget, GNU Wget 1.14 built on linux-gnu.
git: /bin/git, git version 1.8.3.1
grep: alias grep='grep --color=auto'
        /bin/grep (grep --color=auto), grep (GNU grep) 2.20
awk: /bin/awk, GNU Awk 4.0.2
sed: /bin/sed, sed (GNU sed) 4.2.2
cut: /bin/cut, cut (GNU coreutils) 8.22
basename: /bin/basename, basename (GNU coreutils) 8.22
rm: /bin/rm, rm (GNU coreutils) 8.22
mkdir: /bin/mkdir, mkdir (GNU coreutils) 8.22
xargs: /bin/xargs, xargs (GNU findutils) 4.5.11
nvm current: v9.10.1
which node: $NVM_DIR/versions/node/v9.10.1/bin/node
which iojs: which: no iojs in ($NVM_DIR/versions/node/v9.10.1/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:$HOME/.local/bin:$HOME/bin)
which npm: $NVM_DIR/versions/node/v9.10.1/bin/npm
npm config get prefix: $NVM_DIR/versions/node/v9.10.1
npm root -g: $NVM_DIR/versions/node/v9.10.1/lib/node_modules

```
</details>

- `nvm ls` output:
<details>
<!-- do not delete the following blank line -->

```sh
         v9.7.0
->      v9.10.1
default -> node (-> v9.10.1)
node -> stable (-> v9.10.1) (default)
stable -> 9.10 (-> v9.10.1) (default)
iojs -> N/A (default)
lts/* -> lts/carbon (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.14.1 (-> N/A)
lts/carbon -> v8.11.1 (-> N/A)

```
</details>

- How did you install `nvm`? (e.g. install script in readme, Homebrew):
`wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.8/install.sh | bash`
 
nvm says 'no .nvmrc file found' when the problem is that the version inside of said .nvmrc is not installed.

I have a systemd service that calls nvm like this.

`/home/kenny/.nvm/nvm-exec nodemon ./src/index.js`

the output was: 
`Mar 31 21:06:00 vm5 start.sh[3021]: No NODE_VERSION provided; no .nvmrc file found`

the contents of the .nvmrc file are: 
`v9.7.0`

The error disappeared after running `nvm install 9.7.0 --reinstall-packages-from=node`

I got the thing to work but I want to inform you that the error message is wrong it should say that the version inside the `.nvmrc` is not installed, not that there is no `.nvmrc` file.
Repository: material-ui
Issue: Implement theme level states design tokens
Labels: umbrella

Material Design provides a page: https://material.io/design/interaction/states.html#usage on how to style the different states. States are visual representations used to communicate the status of a component or an interactive element.

The components to handle:

- [x] Pagination
- [x] Select
- [x] TreeView 
- [x] Chip #24915
- [x] Autocomplete #23323
- [ ] Button 
- [ ] List
- [ ] Switch
- [ ] Radio
- [ ] Checkbox
- [ ] IconButton
- [ ] Accordion
- [ ] Rating
- [ ] Slider
- [ ] Tabs

Related issues:

- #5186: list states
- #19343: disabled state
- #17493: button states
Repository: neovim
Issue: infercase for command mode?
Labels: enhancement,completion

I don't believe this behavior can be implemented with a plugin (though I've been wrong pretty much every time I've said that when it comes to vim), but it would be helpful to have an `infercase`-like option that would enable tab completion for command mode, but without turning off case sensitivity.

Currently, `infercase` can be used together with `wildignorecase` to enable smart-case tab completion for regular completions but not for vim commands, while `ignorecase` can be used to enable case-insensitive tab completions for both commands and regular completions, but additionally makes `/` searches case-insensitive.

The easiest option is to have either `infercase` or `wildignorecase` (or both together) enable case-insensitive or smart-case tab completion for command mode commands as well, but I don't want to suggest something that some may be vehemently opposed to. If it's any consolation, I don't see (which _probably_ only means I'm wrong and I'm showing my ignorance here) how this can break any scripts or plugins since this would affect TTY behavior only.
Repository: rust
Issue: Incorrect error message about enum variant when trying to call a Result
Labels: A-diagnostics,T-compiler,D-papercut

Test case [(playground link)](https://play.rust-lang.org/?gist=2fdc42baa9d1920ebc04d4a253418354&version=nightly):
```rust
fn foo() -> Result<i32, i32> {
    Ok(42)
}

fn main() {
    foo()();
}
```

The real issue is an extra set of parentheses after `foo()`, which should produce an error because `Result<i32, i32>` is not a function.  However, rustc (stable and current nightly) produces this error message:

```
error[E0618]: expected function, found enum variant `foo()`
 --> src/main.rs:6:5
  |
6 |     foo()();
  |     ^^^^^^^ not a function
help: `foo()` is a unit variant, you need to write it without the parenthesis
  |
6 |     foo();
  |     ^^^^^
```

- The first line is confusing and semi-incorrect: although `foo()` does evaluate to a value of enum type, it's not a specific variant, and "found enum variant `foo()`" makes it seem like `foo` itself is an enum.
- The line after `help:` is incorrect: neither of the variants of the `Result` enum is a unit variant.
- The suggested fix is correct, which is nice :)
Repository: neovim
Issue: Add new literal arguments mode to :command
Labels: enhancement

This is a suggestion for an additional command mode like `<f-args>` and `<q-args>` (let's say `<l-args>`) that would provide all arguments as-is to the command, without any interpretation or expansion and without any reserved characters requiring escaping.

The number of characters that need to be escaped while trying to pass a regex expression to a command that has its own quoting policy can be both incredibly verbose.

This would ideally even apply to characters like `\` or `%`, so it would need to be used extremely carefully, obviously.
Repository: pytorch
Issue: Note about unusual stride situations in dev docs / make it easier to test for this in the library
Labels: module: docs,triaged,module: memory format

On its face, strides are pretty simple: given strides `s`, the memory location of the indices `x` is `sum(s[i] * x[i] for i in dim)`. It's also fairly simple to say when strides are contiguous: that is when `s[i] == product(s[j] for j in range(0, i))`. And then the standard application of strides is to let you get non-contiguous views into an underlying contiguous tensor.

But there are also some weirder, less obvious stride situations:

Broadcasting is achieved by having zero strides. So, e.g., 

```
>>> torch.tensor(range(0,3)).expand(2,3)

 0  1  2
 0  1  2
[torch.LongTensor of size (2,3)]
>>> torch.tensor(range(0,3)).as_strided(size=(2,3), stride=(0,1))

 0  1  2
 0  1  2
[torch.LongTensor of size (2,3)]
```

And the technical definition of strides permits weird, overlapping striding, e.g.,

```
>>> torch.tensor(range(0,7)).as_strided(size=(2,2,2), stride=(3,2,1))

(0 ,.,.) = 
  0  1
  2  3

(1 ,.,.) = 
  3  4
  5  6
[torch.LongTensor of size (2,2,2)]
```

It would be good to have a developer doc describing all of this, as well as adding functions making it easier to test for certain stride situations, to make it easier to work with external libraries and specialized kernels. An example is in the cuFFT interface https://github.com/pytorch/pytorch/pull/6118 where only non-overlapping striding is supported.

CC @SsnL 

cc @jlin27 @mruberry @VitalyFedyunin @jamesr66a @ppwwyyxx
Repository: go
Issue: x/build/cmd/coordinator: store CL number in the query parameters
Labels: Builders

If the build completes, you get this message:

> TryBot result not found (already done, invalid, or not yet discovered from Gerrit). Check Gerrit for results.

If we stored the CL number in the URL (for example `commit=deadbeef&cl=123456`), and we couldn't find the commit number, we could assume the build is complete and either redirect you back to it, or provide a link to the right CL from the complete farmer build.