sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Add a flag to flutter doctor to let it automatically fix/install things?
Labels: tool,t: flutter doctor,P3,team-tool,triaged-tool

I'm currently setting flutter up on a new Mac and for the last 30-60 minutes it's pretty much been:

- run `flutter doctor`
- copy a command from the output, paste it and run
- do something productive on another machine and check back in 10 minutes

It's really great that `doctor` gives the exact commands for many things, but I help but think that if it just did these things for me (stopping if there's a non-zero exit code on anything) it'd save me a bunch of time/babysitting.

(I may have raised this before - it sounds like the sort of thing I would do, but if I did I can't find it now)
Repository: rust
Issue: Add a way to generate function symbols with predictable hashes
Labels: C-enhancement,T-compiler,A-CLI

To debug one of the issues, I wanted to use `llvm-diff` to diff between old and new LLVM-IR. Alas, the attempt didn’t provide any meaningful outcome and all the diff tool could output was:

```
function @_ZN33_$LT$alloc..arc..Arc$LT$T$GT$$GT$9drop_slow17h14f39cee67cb7a45E exists only in left module
function @_ZN33_$LT$alloc..arc..Arc$LT$T$GT$$GT$9drop_slow17h3a4d1cb4bf1c206cE exists only in right module
...
```

@michaelwoerister, is it possible to make rustc use *less* inputs into its hash algorithm?
Repository: go
Issue: sync: eliminate global Mutex in Pool operations
Labels: Performance,compiler/runtime

In the review for https://golang.org/cl/101715 (“regexp: use sync.Pool to cache regexp.machine objects”), @ianlancetaylor notes:

>  A similar change was made in https://golang.org/cl/44150043, by [@bradfitz].  It was rolled back in  https://golang.org/cl/48190043. [@dvyukov] said: "The remaining concern is: Are there cases where a program creates lots of local short-lived regexps (one-shot), and it's not possible to replace them with global ones? For this case we've introduced a global contended mutex."

I'm guessing that comment refers to `allPoolsMu` here:
https://github.com/golang/go/blob/2e84dc2596f5ca655fd5716e1c277a801c868566/src/sync/pool.go#L242

----

It strikes me as odd that `sync.Pool` should have a global `Mutex` at all. After all, `sync.Pool` explicitly cooperates with the garbage collector (and will likely cooperate even more after #22950), and the garbage collector will trace all of the live `sync.Pool` instances in the course of a normal garbage collection.

The `allPools` slice appears to exist so that the garbage collector can clear all of the `sync.Pool` instances before tracing them. We have to identify `Pool`s before tracing them so that we don't over-retain pooled objects, but it seems like we could do that without acquiring global locks beyond the usual GC safepoints.

For example, we could add newly-allocated pools to a per-G list, and move that list to the global list only when the thread running that G acquires the scheduler lock.

If we happen to miss a new `Pool` on the current GC cycle (for example, because its goroutine wasn't descheduled until near the end of the cycle), that's ok: we'll just wait until the next GC cycle to clear it.

That could make `sync.Pool` substantially more efficient for objects that tend to be long-lived but are sometimes short-lived too (such as compiled regexps).
Repository: TypeScript
Issue: Implement interface should not add optional properties
Labels: Suggestion,Awaiting More Feedback,Domain: Quick Fixes

From https://github.com/Microsoft/vscode/issues/46286

**TypeScript Version:**  2.8.0-dev.20180320

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** 
- implement interface
- quick fix 
- code action
- optional property

**Code**

```ts
interface IFoo {
    x?: number
    y: number
}

class Foo implements IFoo {

}
```

Trigger `implement interface` on `Foo`

**Expected behavior:**
Only required properties required:

```ts
interface IFoo {
    x?: number
    y: number
}

class Foo implements IFoo {
    y: number;
}
```

**Actual behavior:**
Both required and optional properties added:

```ts
interface IFoo {
    x?: number
    y: number
}

class Foo implements IFoo {
    x?: number;
    y: number;
}
```
Repository: rust
Issue: unused_assignments warning: false negative for dead stores in struct fields
Labels: C-enhancement,A-lints,A-diagnostics,T-compiler,L-unused_assignments

code like this causes a proper warning
```` rust
fn main() {
	let mut a;
	let b = 4;
	let c = 5;

    	a = b;
    	a = c;

	println!("{}", a);
}
````
=>
````
warning: value assigned to `a` is never read
 --> src/main.rs:6:5
  |
6 |     a = b;
  |     ^
  |
  = note: #[warn(unused_assignments)] on by default
````

however if a is a struct field, I get no warning at all.
```` rust
struct Foo {
    x: i32,
}

fn main() {
	let mut strct = Foo {
	    x: 0, // maybe warn here, too?
	};
	let b = 4;
	let c = 5;

  	strct.x = b; // please warn!
   	strct.x = c;

	println!("{}", strct.x);
}
````

playground:  https://play.rust-lang.org/?gist=c904ff202754b2691e2968977620fd7a&version=nightly

I ran into bugs in my code that could have been prevented by warning about this :(
Repository: TypeScript
Issue: transpileModule doesn't emit correct metadata of return type for async function
Labels: Bug,Help Wanted,Domain: Decorators

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 -->
<!--
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the CONTRIBUTING guidelines: https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
-->

<!-- If you have a QUESTION:
   THIS IS NOT A FORUM FOR QUESTIONS.
   Ask questions at http://stackoverflow.com/questions/tagged/typescript
    or https://gitter.im/Microsoft/TypeScript
-->

<!-- If you have a SUGGESTION:
  Most suggestion reports are duplicates, please search extra hard before logging a new suggestion.
  See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md
-->

<!-- If you have a BUG:
  Please fill in the *entire* template below.
-->
I got a problem when using `transpileModule` with `emitDecoratorMetadata` flag on, the result is inconsistent with what I got from command line tsc.

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  2.8.0-dev.20180321

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** 
experimentalDecorators transpileModule emitDecoratorMetadata

**Code**
```js
'use strict';

const tsc = require("typescript");
const result = tsc.transpileModule(`
class Foo {
    @AnyDecorator()
    public async foobar(): Promise<void> {

    }
}
`, {
    compilerOptions: {
        emitDecoratorMetadata:true,
        experimentalDecorators:true,
        lib: ["lib.es2015.d.ts"]
    }
});

console.log(result.outputText);
```

**Expected behavior:**
This should decorate the function foobar with the return type `Promise`, like:
```js
__decorate([
    AnyDecorator(),
    __metadata("design:type", Function),
    __metadata("design:paramtypes", []),
    __metadata("design:returntype", Promise)
], Foo.prototype, "foobar");
```

**Actual behavior:**
```js
__decorate([
    AnyDecorator(),
    __metadata("design:type", Function),
    __metadata("design:paramtypes", []),
    __metadata("design:returntype", Object)
], Foo.prototype, "foobar");
```

However, if I remove the return type from foobar's signature:
```js
'use strict';

const tsc = require("typescript");
const result = tsc.transpileModule(`
class Foo {
    @AnyDecorator()
    public async foobar() {

    }
}
`, {
    compilerOptions: {
        emitDecoratorMetadata:true,
        experimentalDecorators:true,
        lib: ["lib.es2015.d.ts"]
    }
});

console.log(result.outputText);
```
everything is correct, and return type is `Promise`.
Repository: vscode
Issue: Spacing or Horizontal lines in custom VS Code grammar
Labels: feature-request,api

I just worked into grammar creation with Atom and now VS code and i'm currently developing an own grammar in VS code. In the text file i canot insert extra spacings, but i would like to separate logical blocks with an Bigger spacing or an horizontal line. But i don't now how zto achieve this, because as far as i figured out none of the VS Code templates scopes allows such a style.

Could someone tell me how i can achieve this? As far as i figured out i will need to add a custom scope to each ued template?

Yours sincerely, Markus
Repository: vue
Issue: <transition-group> and v-show triggers move transition on enter
Labels: bug,has PR,transition

### Version
2.5.16

### Reproduction link
[https://jsfiddle.net/chrisvfritz/845Lee66/](https://jsfiddle.net/chrisvfritz/845Lee66/)

### Steps to reproduce
1. Open the fiddle
2. Click the "Toggle" button
3. Watch the `move` transition trigger on enter

### What is expected?
Just like with `v-if`, move transitions should not be triggered on enter (note that it is already _not_ triggered on leave). 

### What is actually happening?
I haven't checked in the source yet, but I'm guessing that since elements with `display: none` still technically have coordinates:

```
DOMRect { x: 0, y: 0, width: 0, height: 0, top: 0, right: 0, bottom: 0, left: 0 }
```

The `move` transition is triggered on enter. I'm not sure why it wouldn't also occur on leave though. 

---
This may be connected to [#5800](https://github.com/vuejs/vue/issues/5800). Also, special thanks to @rachelnabors for finding this bug!

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: rust
Issue: CI: We should be able to complete a build in 3 hours even without Docker image cache
Labels: C-enhancement,T-bootstrap,T-infra

Our CI builders (except macOS and Windows) use Docker, and we'll cache the Docker repository on Travis. Thanks to the cache, normally the `docker build` command only takes a few seconds to complete. However, when the cache is invalidated for whatever reason, the Docker image will need to be actually built, and this may take a very long time. 

Recently this happened with #49246 — the Docker image cache of `dist-x86_64-linux alt` became stale and thus needs to be built from scratch. One of the step involves compiling GCC. The whole `docker build` command thus takes over 40 minutes. Worse, the `alt` builders have assertions enabled, and thus all stage1+ `rustc` invocations are slower than their normal counterpart. Together, it is impossible to complete within 3 hours. Travis will not update the cache unless the build is successful. Therefore, I need to exclude RLS, Rustfmt and Clippy from the distribution, to ensure the job is passing.

I don't think we should entirely rely on Travis's cache for speed. Ideally, the `docker build` command should at most spend 10 minutes, assuming good network speed (~2 MB/s on Travis) and reasonable CPU performance (~2.3 GHz × 4 CPUs on Travis). 

In the `dist-x86_64-linux alt` case, if we host the precompiled GCC 4.8.5 for Centos 5, we could have trimmed 32 minutes out of the Docker build time, which allows us to complete the build without removing anything.
Repository: go
Issue: cmd/link: document default flags passed to extld
Labels: Documentation,NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?
master


### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOCACHE="/localdisk/itocar/gocache/"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/localdisk/itocar/gopath/"
GORACE=""
GOROOT="/localdisk/itocar/golang"
GOTMPDIR=""
GOTOOLDIR="/localdisk/itocar/golang/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build748215444=/tmp/go-build -gno-record-gcc-switches"
```

### What did you do?
 go build -ldflags="-extld=/path/to/ld.hugetlbfs -linkmode=external" foo.go
I was trying to map code section to huge pages.

### What did you expect to see?
Everything works.

### What did you see instead?
Linker didn't recognize -m64 option.

Looks like we pass a bunch of gcc/clang specific flags to any external linker. 
I worked around this by passing -extld=gcc -extldflags="-B /path/to/ld.hugetlbfs", to use gcc as a linker that recognizes -m64 and calls ld.hugetlbfs without passing -m64, but this behavior was surprising to me and should be documented somewhere (in extld documentation?)
Repository: rust
Issue: Argument-position `impl Trait` requires a named lifetime
Labels: C-enhancement,T-compiler,A-impl-trait,D-confusing

This function produces an "expected lifetime parameter" error:

```rust
fn foo(_: impl Iterator<Item = &u8>) {}
```

This code should instead be accepted and bound the `impl Trait` parameter by the elided lifetime.

cc https://github.com/rust-lang/rust/issues/34511
Repository: react-native
Issue: iOS: Multiple animations which use "useNativeDriver" do not work if preceded by a delay.
Labels: Platform: iOS,Help Wanted :octocat:,API: Animated,Priority: Low,Bug

- [x] I have reviewed the [documentation](https://facebook.github.io/react-native)
- [x] I have searched [existing issues](https://github.com/facebook/react-native/issues)
- [x] I am using the [latest React Native version](https://github.com/facebook/react-native/releases)

On iOS, if attempting to animate a text component and a view component in parallel, preceded by an Animated.delay (or setTimeout), the text component will not animate:

```javascript
doAnimate = () => {
    Animated.sequence([
      // Removing the delay here will fix the issue.
      Animated.delay(1000),
      Animated.parallel([
        Animated.timing(this.squareAnimation, { toValue: 1, useNativeDriver: true, duration: 3000 }),
        // If you remove "useNativeDriver" below, the animation works.
        Animated.timing(this.textAnimation, { toValue: 1, useNativeDriver: true, duration: 3000 }),
      ])
    ]).start();

    // This also fails to animate the text component:
    // setTimeout(() => {
    //   Animated.parallel([
    //     Animated.timing(this.squareAnimation, { toValue: 1, useNativeDriver: true, duration: 3000 }),
    //     Animated.timing(this.textAnimation, { toValue: 1, useNativeDriver: true, duration: 3000 }),
    //   ]).start();
    // }, 1000);
}

  componentDidMount() {
    setTimeout(this.doAnimation, 3000);
  }

  render() {
    return (
      <View style={styles.container}>
        <Animated.Text style={[styles.textContainer, {
          opacity: this.textAnimation
        }]}>
          Welcome to React Native!
        </Animated.Text>
        <Animated.View style={[styles.squareContainer, {
          opacity: this.squareAnimation
        }]}>
        </Animated.View>
      </View>
    );
  }
```

If you remove "useNativeDriver" from the "textAnimation", the animation works. Also, making the textAnimation interpolate from viewAnimation does not work (that's how my code originally worked, but I broke them out into separate animations to test what was going wrong).

## Environment
Environment:
  OS: macOS High Sierra 10.13.3
  Node: 8.9.4
  Yarn: 1.5.1
  npm: 5.6.0
  Watchman: Not Found
  Xcode: Xcode 9.2 Build version 9C40b
  Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
  react: ^16.3.0-alpha.1 => 16.3.0-alpha.3
  react-native: 0.54.2 => 0.54.2

## Steps to Reproduce

See code snippet above, alternatively you can check out my example repo:

```sh
git clone https://github.com/dannycochran/animationBug
cd animationBug
yarn install
react-native run-ios
```

## Expected Behavior

The animations for both the View and Text component work, as they do on Android.

## Actual Behavior

The text opacity never animates.
Repository: rust
Issue: `impl Trait` Associated Types Do Not Leak Auto Traits
Labels: T-lang,C-feature-request,A-impl-trait

While auto trait impls of `impl Trait` types leak, the auto trait impls of their associated types do not:

```rust
#![feature(conservative_impl_trait)]

trait Foo {
    type Bar;
}

fn require_bar_send<F>(_: F) where F: Foo, F::Bar: Send {}

fn foo() -> impl Foo {
    struct Fooey;
    impl Foo for Fooey {
        type Bar = ();
    }
    Fooey
}

fn main() {
    require_bar_send(foo()); // ERROR
}
```

This can be fixed by writing `impl Foo<Bar=impl Send>`, but this can get annoying quickly: async traits, whose methods each return a separate associated type implementing `Future`, need to have a `Bar=impl Send` for each method:

```rust
trait Foo {
    type FooFut: Future<...>;
    fn foo(&self) -> Self::FooFut;

    type BarFut: Future<...>;
    fn bar(&self) -> Self::BarFut;

    type BazFut: Future<...>;
    fn baz(&self) -> Self::BazFut;
}

fn foo() -> impl Foo<FooFut=impl Send, BarFut=impl Send, BazFut=impl Send> { ... }
```

This isn't a bug, but I'm interested in seeing if there're ways we can improve here-- should associated type auto traits leak? I can see that becoming a huge problem since you'd then want the associated types of associated types auto traits to leak, etc, but there's not an obvious solution to me. I really just want an "everything you care about here is thread-safe" button, but I don't know how to supply that easily.
Repository: go
Issue: image/jpeg: Decode is slow
Labels: Performance,help wanted,NeedsInvestigation

Mac OS Sierra
go version go1.10 darwin/amd64
CPU 3,5 GHz Intel Core i7

I noticed that the use of decode jpeg is very slow.

decode image jpeg 1920x1080

I test github.com/pixiv/go-libjpeg/jpeg and native jpeg

go 1.10 jpeg.decode  ≈ 30 ms cpu ≈ 15 %
libjpeg  jpeg.decode  ≈ 7  ms cpu  ≈ 4 %

will it ever go as fast as other libraries?
is it possible that in the next versions the native implementation will become faster?
Repository: TypeScript
Issue: Abstract classes that implement interfaces shouldn't require method signatures
Labels: Suggestion,Needs Proposal

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 -->
<!--
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the CONTRIBUTING guidelines: https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
-->

<!-- If you have a QUESTION:
   THIS IS NOT A FORUM FOR QUESTIONS.
   Ask questions at http://stackoverflow.com/questions/tagged/typescript
    or https://gitter.im/Microsoft/TypeScript
-->

<!-- If you have a SUGGESTION:
  Most suggestion reports are duplicates, please search extra hard before logging a new suggestion.
  See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md
-->

<!-- If you have a BUG:
  Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  2.7

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** abstract class implements interface

**Code**

```ts
interface FooFace {
    foo();
}
abstract class FooClass implements FooFace {
    //         ^^^^^^^^
    // Class 'FooClass' incorrectly implements interface 'FooFace'.
    //   Property 'foo' is missing in type 'FooClass'.
    //
    // unless the following is uncommented:
    //abstract foo();
}

// contrast:
abstract class BarClass {
    abstract bar();
}
abstract class BarSubClass extends BarClass {
    // no `abstract bar();` required
}
```

**Expected behavior:**
Abstract classes that implement interfaces don't need to define abstract type definitions to satisfy interface.

**Actual behavior:**
They do.

[**Playground Link**](http://www.typescriptlang.org/play/#src=interface%20FooFace%20%7B%0D%0A%20%20%20%20foo()%3B%0D%0A%7D%0D%0Aabstract%20class%20FooClass%20implements%20FooFace%20%7B%0D%0A%20%20%20%20%2F%2F%20%20%20%20%20%20%20%20%20%5E%5E%5E%5E%5E%5E%5E%5E%0D%0A%20%20%20%20%2F%2F%20Class%20'FooClass'%20incorrectly%20implements%20interface%20'FooFace'.%0D%0A%20%20%20%20%2F%2F%20%20%20Property%20'foo'%20is%20missing%20in%20type%20'FooClass'.%0D%0A%20%20%20%20%2F%2F%0D%0A%20%20%20%20%2F%2F%20unless%20the%20following%20is%20uncommented%3A%0D%0A%20%20%20%20%2F%2Fabstract%20foo()%3B%0D%0A%7D%0D%0A%0D%0A%2F%2F%20contrast%3A%0D%0Aabstract%20class%20BarClass%20%7B%0D%0A%20%20%20%20abstract%20bar()%3B%0D%0A%7D%0D%0Aabstract%20class%20BarSubClass%20extends%20BarClass%20%7B%0D%0A%20%20%20%20%2F%2F%20no%20%60abstract%20bar()%3B%60%20required%0D%0A%7D)

**Related Issues:**
- #19847, where typescript fails to see that a superclass _does_ implement a method (contrast this ticket, where typescript fails to see that a class _need not_ implement a method)
Repository: pytorch
Issue: LBFGS always give nan results, why
Labels: needs reproduction,module: numerical-stability,module: optimizer,triaged

I use the LBFGS alogorithm, and found that if maxiter is larger enough, i.e., maxiter >10, the optimizer always give nan results. Why?
Repository: flutter
Issue: flutter_driver's finders should have the equivalent of flutter_test's Finder.evaluate()
Labels: a: tests,c: new feature,framework,t: flutter driver,c: proposal,P3,team-framework,triaged-framework

## Steps to Reproduce
Using flutter_driver in the QA environment. Options feels quite limited currently. I am trying to check if an element exists or not, perhaps a function on the like of finder.IsEmpty or something like IfExists in Appium which the skips the element if it doesn't exist and doesn't necessarily throw an exception.

## Logs
Application runs fine. Just looking for more functionalities of flutter driver.

## Flutter Doctor
```
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel beta, v0.1.5, on Microsoft Windows [Version 6.1.7601], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[!] Android Studio (version 2.3)
    X Unable to find bundled Java version.
[√] Android Studio (version 3.0)
[√] VS Code (version 1.21.1)
[√] Connected devices (1 available)

! Doctor found issues in 1 category.
```