sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [fuchsia] Have a way to specify the observatory port in Flutter runner
Labels: customer: fuchsia,framework,dependency: fuchsia,platform-fuchsia,P2,team-framework,triaged-framework

I wasn't able to find a canonical example that does this, so I think this is not wired in as of today.

This would require us passing some parameter to the Dart isolate when we construct it.


cc: @kf6gpe
Repository: create-react-app
Issue: all file names lowercase - use hyphens instead of camelcase
Labels: issue: proposal,needs triage

Strange mixture of camelcase and hyphenated files when I used:

```
npx create-react-app . --typescript
```

![Screenshot from 2020-02-12 11-15-19](https://user-images.githubusercontent.com/11139560/74368738-15cf8000-4d89-11ea-99b5-557c2aa0cc55.png)


I would recommend only lowercase filenames - the technical reason is that macos is case insensitive and linux is not. so macos fs won't see file renamings easily when using git etc. people that know will know what I am talking about
Repository: pytorch
Issue: Core dumps being created when running test_c10d.py and test_multiprocessing_spawn.py
Labels: module: tests,triaged

## 🐛 Bug

When running `test/distributed/test_c10d.py` and `test/test_multiprocessing_spawn.py` in Power CI (and when run on my local Power system), some core files appear in the repo even though all the tests pass. I dug a little deeper and it looks like they're being caused by `NcclErrorHandlingTest.test_nccl_errors_blocking_abort` and `ForkTest.test_terminate_signal`. Both of these tests seem to be testing that terminating processes exit when some errors are thrown or a signal is sent. When running in CI, `.jenkins/pytorch/test.sh` checks that the repository is clean every tests are run. Isn't it reasonable to expect that these tests cases would create core dumps sometimes?

I've only seen this on Power. `NcclErrorHandlingTest.test_nccl_errors_blocking_abort` seems to be passing fine on x86 without creating any core dumps, but `ForkTest.test_terminate_signal` isn't run on x86 CI.

## To Reproduce

Steps to reproduce the behavior:

1. Build latest master
2. Run `test/test_multiprocessing_spawn.py` and `test/distributed/test_c10d.py`.
3. These should create core dumps in the directory you ran the tests from.
4. When run in CI with `.jenkins/pytorch/test.sh`, creating core dumps causes the script to fail.

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

Either no core dumps should be created, or if it's okay for those test cases to create core dumps, the `.jenkins/pytorch/test.sh` script should somehow account for that.
Repository: TypeScript
Issue: Preserve type aliases on implement interface
Labels: Suggestion,Experience Enhancement

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

From https://github.com/microsoft/vscode/issues/90061

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.8.1-rc

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
- quick fix 
- implement interface

**Repo**

```ts
export type UrlString = string;
export type UUID = string;

export interface I_IdToUrlMapper {
	mapIdToUrl(id: UUID): UrlString
	mapUrlToId(url: UrlString): UUID
}

export class IdToUrlMapper implements I_IdToUrlMapper {

}
```

Run implement interface on `IdToUrlMapper `

**Expected behavior:**
Type aliases are preserved 

```ts
export class IdToUrlMapper implements I_IdToUrlMapper {
    mapIdToUrl(id: UUID): UrlString {
        throw new Error("Method not implemented.");
    }
    mapUrlToId(url: UrlString): UUID {
        throw new Error("Method not implemented.");
    }
}
```

**Actual behavior:**
Both methods use `string`:

```ts
export class IdToUrlMapper implements I_IdToUrlMapper {
    mapIdToUrl(id: string): string {
        throw new Error("Method not implemented.");
    }
    mapUrlToId(url: string): string {
        throw new Error("Method not implemented.");
    }
}
```

**Related Issues**
- https://github.com/microsoft/TypeScript/issues/34778
Repository: godot
Issue: Scaled CanvasLayer reports wrong area to child nodes
Labels: bug,topic:gui

**Godot version:**
3.2

**OS/device including version:**
Windows 10

**Issue description:**
When a `CanvasLayer` is scaled, it's children get the viewport size when requesting their parent's area size. This means that a scaled `CanvasLayer`'s children will anchor wrong.
![CanvasLayerBug](https://user-images.githubusercontent.com/9751923/74382629-ffd2b700-4daa-11ea-9abe-fc6bb86b545a.gif)

**Steps to reproduce:**
1. Create a `2DNode` scene
2. Add a `CanvasLayer` with `scale` set to `(2,2)`
3. Add a `Control` as a child of the `CanvasLayer` and set it's Layout to `Full Rect`
   Note that the control is now twice the size of the actual viewport.

**Minimal reproduction project:**
https://github.com/cgbeutler/godot_bugs_CanvasLayerScaleAnchorsBug
Repository: rust
Issue: Conflicting error messages for HRTB in `impl Trait`
Labels: A-diagnostics,A-lifetimes,T-compiler,A-impl-trait,C-bug

Rust declares the lifetime `'a` is both undeclared and that it is a shadowing declaration

```rust
#[derive(Debug)]
struct Ctx<'d> {
    phantom: std::marker::PhantomData<&'d ()>   
}
fn map<'c, 'd: 'c>(ctx: &'c mut Ctx<'d>, data: Vec<()>) -> impl for<'a> Iterator<Item = ()> + 'a where 'c: 'a {
    data.into_iter().inspect(|t| println!("{:?}", ctx))
}
```

My more complicated example is trying to use the `&'c mut Ctx<'d>` reference in one of the closures passed to `Iterator::map()` so I need to somehow incorporate the lifetime `'c` into the return type.

Instead I get this confusing error:
```
error[E0261]: use of undeclared lifetime name `'a`
 --> src/lib.rs:5:95
  |
5 | fn map<'c, 'd: 'c>(ctx: &'c mut Ctx<'d>, data: Vec<()>) -> impl for<'a> Iterator<Item = ()> + 'a where 'c: 'a {
  |                                                                                               ^^ undeclared lifetime

error[E0496]: lifetime name `'a` shadows a lifetime name that is already in scope
 --> src/lib.rs:5:69
  |
5 | fn map<'c, 'd: 'c>(ctx: &'c mut Ctx<'d>, data: Vec<()>) -> impl for<'a> Iterator<Item = ()> + 'a where 'c: 'a {
  |                                                                     ^^                        -- first declared here
  |                                                                     |
  |                                                                     lifetime 'a already in scope

error[E0261]: use of undeclared lifetime name `'a`
 --> src/lib.rs:5:108
  |
5 | fn map<'c, 'd: 'c>(ctx: &'c mut Ctx<'d>, data: Vec<()>) -> impl for<'a> Iterator<Item = ()> + 'a where 'c: 'a {
  |                                                                                                            ^^ undeclared lifetime

error: aborting due to 3 previous errors
```

You'll notice the `help` text of the first error says "undeclared lifetime" but the `help` of the second says "first declared here" and then gives a bogus "already in scope" hint.
Repository: flutter
Issue: Failed to extract manifest from APK // aapt.EXE stop working.
Labels: platform-android,tool,t: gradle,P2,team-android,triaged-android

I installed flutter and dart then tried to test the default app of flutter on web and it worked well. Then tried to test the app on my own phone i get that error :

windows [Version 10.0.17763.1039]
(c) 2018 Microsoft Corporation. All rights reserved.

D:\tests\flutter_appd>flutter run
Launching lib\main.dart on STK LX1 in debug mode...
Running Gradle task 'assembleDebug'...
Running Gradle task 'assembleDebug'... Done                       117.9s
√ Built build\app\outputs\apk\debug\app-debug.apk.

After this step i got a message saying that " aapt.EXE stop working "  
then

Failed to extract manifest from APK: ProcessException: The
 command failed
  Command: C:\Users\User\AppData\Local\Android\sdk\build-t
ools\28.0.3\aapt dump xmltree
  D:\tests\flutter_appd\build\app\outputs\apk\app.apk AndroidManifest.xml.
Problem building Android application: see above error(s).

thank you.
Repository: node
Issue: HTTP 1.1 fallback for HTTP 2 client
Labels: http,http2

I discussed this a while back with @jasnell and I forget where it all landed and what was needed.

I’d like to make it so that [`bent`](https://github.com/mikeal/bent) uses HTTP2 when available and falls back to HTTP 1.1 transparently when it’s not available.

This should be possible, the standard was certainly designed that way, but I can’t find any examples of doing this in Node.js and the core http client libraries are totally separate. It could just be a documentation issue but I think there might actually be some missing API in order to make it work.
Repository: TypeScript
Issue: [Breaking Change] Typescript 3.7 converts reference paths to tsconfig specified paths breaking multi-project compiles.
Labels: Needs Investigation

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->
Typescript is replacing part of a relative path with one of the paths specified in tsconfig's path section. This is breaking the projects that rely on this file as they cannot resolve the path.
<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.7 
**Visual Studio Version:**  Community 2017

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
Typescirpt paths tsconfig reference paths alias.

**Code**

In the client project at `folder\folder\file.ts`
```ts
/// <reference path="../../External/Knockout/index.d.ts" />
```

Becomes (in ClientDeclarations) `folder\folder\file.d.ts`:
```ts
/// <reference types="@Client/external/knockout/index" />
```

My tsconfig file (folder names with sensitive information are replaced with `***`)
```json
{
  "compileOnSave": true,
  "compilerOptions": {
    "module": "amd",
    "target": "es6",
    "lib": [ "es6", "dom" ],
    "sourceMap": true,
    "strict": true,
    "build": true,
    "declaration": true,
    "declarationDir": "../ClientDeclarations",
    "baseUrl": "./",
    "paths": {
      "@Common/*": [ "../Common/*" ],
      "@Server/*": [ "../ServerDeclarations/*" ],
      "@Client/*": [ "./*"]
    }
  },
  "include": [
    "./*",
    "./External/***/koco.ts",
    "./External/***/kocss.ts",
    "./External/***/kopath.ts"
  ],
  "exclude": [
    "node_modules"
  ],
  "references": [
    { "path": "../Common" }
  ]
}
```

**Expected behavior:**
The path should not be transformed during output.

**Actual behavior:**
The path is transformed to include an `@Client` reference, which my dependant projects can't resolve. **This did not happen in tsc 3.4**.

Additionally all of the casing is altered - meaning that this path would not resolve on linux machines.

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
I haven't been able to find any - probably because what I'm trying to look for is called a "path" (in tsconfig) which is a highly overloaded term, making searching for anything related to it almost impossible. It would be nice to call it something like a "path alias" so that searching for related issues was easier.
Repository: node
Issue: readline hangs the process on Win10
Labels: readline,windows

<!--
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**: node v13.8.0
* **Platform**: Win 10 64-bit
* **Subsystem**: Git For Windows 2.25.0, mintty 3.1.0 (x86_64-pc-msys)

### What steps will reproduce the bug?

```
#!/usr/bin/env node

const readline = require('readline').createInterface({
    input: process.stdin,
    output: process.stdout
});

readline.question('> ', answer => {
    console.log('answer', answer);
    readline.close();
});
```

Running the above relying on the hash-bang/she-bang, `./readline.js`, will make it hang. 

Running the above using node, `node readline.js`, everything works as expected

### How often does it reproduce? Is there a required condition?

Always

### What is the expected behavior?

The program should exit back to the shell after the user has pressed <kbd>Enter</kbd>

### What do you see instead?

The program hangs and I can't kill it either by Ctrl+D nor Ctrl+C

### Additional information

A workaround is to wrap the `close()` call in a `setTimeout` like so

```
#!/usr/bin/env node

const readline = require('readline').createInterface({
    input: process.stdin,
    output: process.stdout
});

readline.question('> ', answer => {
    console.log('answer', answer);
    setTimeout(() => readline.close());
});
```

This comment is similar, but that one states that it works in Win 10. That is not my experience. 
https://github.com/nodejs/node/issues/17495#issuecomment-414333565
Repository: angular
Issue: QueryList change not emitted when using ChangeDetectionStrategy.OnPush
Labels: type: bug/fix,freq1: low,area: core,state: confirmed,core: queries,core: change detection,P4

# 🐞 bug report

### Affected Package
angular 9.0.1

### Is this a regression?
don't know.

### Description
when OnPush and @ViewChildren('something in ng-template') and the template be used in a sibling component. the QueryList.change won't fire 
![image](https://user-images.githubusercontent.com/8691013/74405947-5f8f9780-4e69-11ea-9964-d5cc4c78cc58.png)


## 🔬 Minimal Reproduction
1. git clone https://github.com/keatkeat87/angular-viewchild-onpush-issue
2. yarn install
3. ng serve --open
4. F12 open console 
5. click "append button" (will see the log 'list.changes', this is correct)
6. go to file 'autocomplete.component.ts'
7. uncomment 'changeDetection: ChangeDetectionStrategy.OnPush'
8. refresh and click "append button" again (list.changes no fire any more, this is incorrect)



## 🌍  Your Environment

**Angular Version:**
Angular CLI: 9.0.2
Node: 12.14.0
OS: win32 x64

Angular: 9.0.1
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.900.2
@angular-devkit/build-angular     0.900.2
@angular-devkit/build-optimizer   0.900.2
@angular-devkit/build-webpack     0.900.2
@angular-devkit/core              9.0.2
@angular-devkit/schematics        9.0.2
@angular/cli                      9.0.2
@ngtools/webpack                  9.0.2
@schematics/angular               9.0.2
@schematics/update                0.900.2
rxjs                              6.5.4
typescript                        3.7.5
webpack                           4.41.2
Repository: go
Issue: x/tools/gopls: support for bazel-based projects
Labels: FeatureRequest,gopls,Tools

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.1 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

n/a

### What operating system and processor architecture are you using (`go env`)?

n/a

### What did you do?

Wrote a project with bazel with .go files and .proto files. The protobufs generate go code, which I'm not sure how to make understandable to gopls. Code completion for this code does not work in VSCode.

### What did you expect to see?

1. Documentation of how to set up a Bazel-based project in the [User guide](https://github.com/golang/tools/blob/master/gopls/doc/user.md).
2. An example project that works and loads in an IDE like VS Code


### What did you see instead?

Scattered information on the level of support and no example projects.

### Related links:

1. https://github.com/bazelbuild/rules_go/issues/512 - main source of updates on gopackagesdriver progress
2. https://github.com/bazelbuild/rules_go/wiki/Editor-and-tool-integration: Design doc for gopackagesdriver - I'm not sure how accurate this is
3. https://github.com/microsoft/vscode-go/issues/2755 - gopls support for GOPACKAGESDRIVER in VS Code
4. https://github.com/bazelbuild/rules_go/issues/393 - editor integration issue for rules_go
5. https://github.com/golang/go/issues/34341 - documentation request for GOPACKAGESDRIVER
6. Code: [jmhodges/rules_go/go/tools/gopackagesdriver](https://github.com/jmhodges/rules_go/tree/a710386e6956baa4a83d73d406c8d0255354818b/go/tools/gopackagesdriver), [gopackagesdriver in rules_go feature branch](https://github.com/bazelbuild/rules_go/tree/feature/gopackagesdriver/go/tools/gopackagesdriver), [tools/go/packages/external.go](https://github.com/golang/tools/blob/master/go/packages/external.go) seems to implement the external packages driver
Repository: go
Issue: testing: when using a custom TestMain, m.Run does not return if one of the tests it runs panics
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.7 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/yury/Library/Caches/go-build"
GOENV="/Users/yury/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/yury/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/yury/go/src/github.com/orlangure/myproject/go.mod"
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/p1/rjgq2gp55pj58ckbsn94yfz80000gn/T/go-build564127360=/tmp/go-build -gno-record-gcc-switches -fno-common"

</pre></details>

### What did you do?

I wrote a function, a test for it, and `TestMain` to perform setup and teardown for testing this function:

main.go
```go
package main

import "fmt"

func main() {
	fmt.Println("vim-go")
}

func p() {
	panic("foo")
}
```

p_test.go
```go
package main

import "testing"

func TestP(t *testing.T) {
	p()
}
```

main_test.go
```go
package main

import (
	"fmt"
	"os"
	"testing"
)

func TestMain(m *testing.M) {
	os.Exit(testMain(m))
}

func testMain(m *testing.M) int {
	setup()
	defer teardown()

	return m.Run()
}

func setup() {
	fmt.Println("setting up")
}

func teardown() {
	fmt.Println("tearing down")
}
```

### What did you expect to see?
I expected to see "setting up" and "tearing down" at some point, and a panic "foo" message with a stack trace.


### What did you see instead?
Only setup and panic output appeared:

```
setting up
--- FAIL: TestP (0.00s)
panic: foo [recovered]
        panic: foo

goroutine 19 [running]:
testing.tRunner.func1(0xc0000b6100)
        /usr/local/go/src/testing/testing.go:874 +0x3a3
panic(0x1111220, 0x116b4d0)
        /usr/local/go/src/runtime/panic.go:679 +0x1b2
akeyless.io/akeyless-main-repo/go/src/t.p(...)
...
FAIL
```

The program probably called `os.Exit` at some point while running the tests, or panicked in a separate go routine with no way for me to recover. I would expect both setup and teardown functions to be called at some point.