sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Window dimensions are limited by wrong monitor
Labels: bug,topic:porting

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.1-alpha 8068d02


**OS/device including version:**
Linux Mint 19 Cinnamon x64 (Muffin window manager)

**Issue description:**
I have two displays: one that is 2560x1440, and one that is 1280x1024. They have this layout:
![image](https://user-images.githubusercontent.com/27100585/46502792-57364e00-c86c-11e8-882f-f5ddcfad1ce2.png)

Note that the larger monitor is set as the "primary" monitor.

The problem is that any Godot window, upon being spawned, will have its size capped to the dimensions of the smaller, secondary monitor. This includes the Godot editor itself, if forced to open windowed. 

For example, I created a project with a window size of 2000x1200:
![image](https://user-images.githubusercontent.com/27100585/46502491-a039d280-c86b-11e8-83d2-9149398d0919.png)

The window should fit on the 2560x1440 monitor. Just to be sure, the editor settings for window placement are configured for Monitor 1 (the primary monitor, being the larger one):
![image](https://user-images.githubusercontent.com/27100585/46502654-06bef080-c86c-11e8-998e-79b11ce4fe51.png)

The project itself just displays the window size:
![image](https://user-images.githubusercontent.com/27100585/46503123-44704900-c86d-11e8-8031-45de010bc10d.png)

When running the project, the window size will always be capped to 1280x1024, the size of the second monitor:
![image](https://user-images.githubusercontent.com/27100585/46503171-6cf84300-c86d-11e8-86d1-b9375a7838cd.png)

cc @Calinou, maybe you're able to help diagnose the problem.


**Minimal reproduction project:**
This is the project I used: [multiple monitor window size bug.zip](https://github.com/godotengine/godot/files/2448151/multiple.monitor.window.size.bug.zip)
It doesn't do much, and you might have to modify the window size to match your monitors, so this might not be too useful...
Repository: go
Issue: net/http: can't set Transfer-Encoding explicitly on outgoing Request
Labels: NeedsDecision

`httputil.DumpRequestOut` does not currently print anything w.r.t. `Transfer-Encoding` (TE) even though the information is printed via `DumpRequest`. In addition, there is special logic for handling TE that seems like maybe it hasn't been extracted out so the logic is hard-coded into `DumpRequest` which means that it could drift from what is actually done when sending the request.

I've not spent too much time looking at possible solutions but the Transfer-Encoding definitely seems to be a special case and its not particularly intuitive whats going on to your request if you set the header field manually or if you set the request.TransferEncoding.

The docs say that `DumpRequest` is for server side debugging whereas `DumpRequestOut` is for clientside, but I'm not familiar with why they couldn't/shouldn't be more similar (or the same).

Not sure if this logic should be put into `DumpRequestOut`, if not, why? And I'd like to get a bit of feedback if this is a known issue that maintainers would like to have cleaned up.
 
### What version of Go are you using (`go version`)?
Go playground, any go version as far as I'm aware.

### Does this issue reproduce with the latest release?
Yes.

### What operating system and processor architecture are you using (`go env`)?
Just using the playground as an example.

### What did you do?
https://play.golang.org/p/vW7oNw0Jjz6

### What did you expect to see?
The same information for Transfer-Encoding available on both `Dump...` outputs.

### What did you see instead?
Transfer-Encoding is printed during `DumpRequest` but not `DumpRequestOut`
Repository: TypeScript
Issue: Problem returning union of promises in `then` callback
Labels: Suggestion,Needs Proposal

**TypeScript Version:**  3.2.0-dev.20181004

**Code**

```ts
function f(b: boolean, pn: Promise<number>, ps: Promise<string>) {
 return Promise.resolve().then(() => b ? pn : ps);
}
```

**Expected behavior:**

No error.

**Actual behavior:**

Pyramid of doom error message:
```
src/a.ts:2:35 - error TS2345: Argument of type '() => Promise<string> | Promise<number>' is not assignable to parameter of type '(value: void) => string | PromiseLike<string>'.
  Type 'Promise<string> | Promise<number>' is not assignable to type 'string | PromiseLike<string>'.
    Type 'Promise<number>' is not assignable to type 'string | PromiseLike<string>'.
      Type 'Promise<number>' is not assignable to type 'PromiseLike<string>'.
        Types of property 'then' are incompatible.
          Type '<TResult1 = number, TResult2 = never>(onfulfilled?: ((value: number) => TResult1 | PromiseLike<TResult1>) | null | undefined, onrejected?: ((reason: any) => TResult2 | PromiseLike<TResult2>) | null | undefined) => Promise<...>' is not assignable to type '<TResult1 = string, TResult2 = never>(onfulfilled?: ((value: string) => TResult1 | PromiseLike<TResult1>) | null | undefined, onrejected?: ((reason: any) => TResult2 | PromiseLike<TResult2>) | null | undefined) => PromiseLike<...>'.
            Types of parameters 'onfulfilled' and 'onfulfilled' are incompatible.
              Types of parameters 'value' and 'value' are incompatible.
                Type 'number' is not assignable to type 'string'.

2     return Promise.resolve().then(() => b ? pn : ps);
```

**Related Issues:** #20531
Repository: TypeScript
Issue: Excess property errors reported on overloads report errors on the wrong overload
Labels: Bug,Domain: Error Messages

<!-- 🚨 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.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.2.0-dev.201xxxxx

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
declare function badError(x: { x: number }): string;
declare function badError(x: { y: number }): number;

badError({ x: 12, foob: "ok" });
```

**Expected behavior:**
```
Argument of type '{ x: number; foob: string; }' is not assignable to parameter of type '{ x: number; }'.
  Object literal may only specify known properties, and 'foob' does not exist in type '{ x: number; }'.
```

**Actual behavior:**
```
Argument of type '{ x: number; foob: string; }' is not assignable to parameter of type '{ y: number; }'.
  Object literal may only specify known properties, and 'x' does not exist in type '{ y: number; }'.
```

I noticed this while refactoring JSX to use the same excess property checking the rest of our call resolution does. Our JSX checking doesn't exhibit the same problem right now because it does strange things for "arity" checking that involve matching up properties, and so tosses the overload with no matching properties from the list of possible ones.
Repository: flutter
Issue: Need a way to read Android /res assets from Flutter
Labels: platform-android,engine,a: existing-apps,customer: crowd,P2,team-android,triaged-android

Internal: b/117228933

Flutter app cannot access assets under res/** for Android (or an arbitrary bundle on iOS), unless the asset is copied to the Flutter managed bundle. This is not ideal; we should provide a way to reuse platform assets.

It is worth noting that we support the other way around: https://flutter.io/assets-and-images/#sharing-assets-with-the-underlying-platform

Ideally, we should leverage the platform's mechanism for picking the right asset too. For instance, instead of grabbing `res/drawable-hhdpi/some_asset.png`, we should access the asset via `R.drawable.some_asset` so that the right scaled version is picked.
Repository: flutter
Issue: Hero Animation Improvements
Labels: c: new feature,framework,a: animation,P3,team-framework,triaged-framework

Would be good and useful if the Hero animation also move some Object with him. Like, if I'm moving an Text widget, they should move the String inside that Text widget, so that on the other side Hero just show the same data, without re-populate with a new data.
Repository: create-react-app
Issue: Disabling code splitting in CRA2
Labels: issue: proposal,issue: question

How can I disable the code splitting in CRA 2?
Repository: rust
Issue: Bad error messages with wrong generator yield type
Labels: A-type-system,C-enhancement,A-diagnostics,T-compiler,A-coroutines,T-types

This is reduced code:

```
#![feature(generator_trait, generators)]
use std::ops::{Generator, GeneratorState};

fn generator_to_iterator<G>(g: G) -> impl Iterator<Item = G::Yield>
where G: Generator<Return = ()> {
    struct It<G>(G);

    impl<G: Generator<Return = ()>> Iterator for It<G> {
        type Item = G::Yield;

        fn next(&mut self) -> Option<Self::Item> {
            unsafe {
                match self.0.resume() {
                    GeneratorState::Yielded(y) => Some(y),
                    GeneratorState::Complete(()) => None,
                }
            }
        }
    }

    It(g)
}

fn foo() -> impl Iterator<Item=u32> {
    generator_to_iterator(|| {
        yield 1_i32;
        yield 2_u32;
    })
}

fn main() {
    for _ in foo() {}
}
```

It gives two error messages, both bad:

```
error[E0308]: mismatched types
  --> ...\test.rs:27:15
   |
28 |         yield 2_u32;
   |               ^^^^^ expected i32, found u32

error[E0271]: type mismatch resolving `<impl std::iter::Iterator as std::iter::Iterator>::Item == u32`
  --> ...\test.rs:24:13
   |
25 | fn foo() -> impl Iterator<Item=u32> {
   |             ^^^^^^^^^^^^^^^^^^^^^^^ expected i32, found u32
   |
   = note: the return type of a function must have a statically known size

error: aborting due to 2 previous errors

Some errors occurred: E0271, E0308.
```

I'd like instead a single error message like:

```
error[E0308]: mismatched types
  --> ...\test.rs:26:15
   |
28 |         yield 1_i32;
   |               ^^^^^ expected u32, found i32
```
Repository: rust
Issue: Truncated backtraces on OS X
Labels: A-runtime,O-macos,T-libs-api,T-compiler,C-bug,T-release

The original report is here: https://bugzilla.mozilla.org/show_bug.cgi?id=1496503

Apparently backtraces (sometimes?) get truncated on OS X as seen here:
```
++DOMWINDOW == 3 (0x116c70800) [pid = 89605] [serial = 3] [outer = 0x10bd5a200]
thread '' panicked at 'assertion failed: texture.state() == TextureState::Uninitialized', gfx/webrender/src/device/gl.rs:1177:9
stack backtrace:
   0:        0x10edc78bf - std::sys::unix::backtrace::tracing::imp::unwind_backtrace::hdfdb4ba75a1dcb88
   1:        0x10eda034a - std::sys_common::backtrace::print::h5823bdde4d2f8639
   2:        0x10edd00c3 - std::panicking::default_hook::{{closure}}::h06fc925781e26cfe
   3:        0x10edcfe4c - std::panicking::default_hook::hdfdcc6f72e7aec0a
   4:        0x10edd07b7 - std::panicking::rust_panic_with_hook::h28749c6c929f49fc
Redirecting call to abort() to mozalloc_abort

Hit MOZ_CRASH() at /files/mozilla/mc/q/memory/mozalloc/mozalloc_abort.cpp:35
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: Receive IPC close with reason=AbnormalShutdown (t=1.3491) Hit MOZ_CRASH(Aborting on channel error.) at /files/mozilla/mc/q/ipc/glue/MessageChannel.cpp:2662
Hit MOZ_CRASH(MachExceptionHandler: Failed to forward to the previous handler!) at /files/mozilla/mc/q/js/src/ds/MemoryProtectionExceptionHandler.cpp:671
```

Is this a known issue? 

cc @bholley
Repository: go
Issue: cmd/go: does not verify existence of replace directory
Labels: NeedsDecision,modules

Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
```
go version go1.11.1 linux/amd64
```

### Does this issue reproduce with the latest release?
yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/myname/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/myname/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/myname/Downloads/test/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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build816763754=/tmp/go-build -gno-record-gcc-switches"
```

### What did you do?
create this `go.mod` file;
```sh
module aha

require (
	github.com/davecgh/go-spew v1.1.1 // indirect
	github.com/gin-contrib/sse v0.0.0-20170109093832-22d885f9ecc7 // indirect
	github.com/gin-gonic/gin v1.3.0 // indirect
	github.com/golang/protobuf v1.2.0 // indirect
	github.com/json-iterator/go v1.1.5 // indirect
	github.com/mattn/go-isatty v0.0.4 // indirect
	github.com/modern-go/concurrent v0.0.0-20180306012644-bacd9c7ef1dd // indirect
	github.com/modern-go/reflect2 v1.0.1 // indirect
	github.com/pmezard/go-difflib v1.0.0 // indirect
	github.com/rs/cors v1.5.0
	github.com/stretchr/testify v1.2.2 // indirect
	github.com/ugorji/go/codec v0.0.0-20180927125128-99ea80c8b19a // indirect
	golang.org/x/net v0.0.0-20181005035420-146acd28ed58 // indirect
	golang.org/x/sync v0.0.0-20180314180146-1d60e4601c6f // indirect
	golang.org/x/sys v0.0.0-20181004145325-8469e314837c // indirect
	gopkg.in/go-playground/assert.v1 v1.2.1 // indirect
	gopkg.in/go-playground/validator.v8 v8.18.2 // indirect
	gopkg.in/yaml.v2 v2.2.1 // indirect
)

replace github.com/rs/cors/wrapper/gin => ../nonexistentDirectory/AntherDirectoryThatDoesNotExist
```
and this `main.go` file;
```go
package main

import (
	"fmt"

	"github.com/rs/cors/wrapper/gin"
)

func main() {
	fmt.Println(gin.Options{})
}
```
then run;
```bash
go mod tidy && \
go mod verify && \
go run main.go
```


### What did you expect to see?
a failure with a nice error message pointing out that the path `../nonexistentDirectory/AntherDirectoryThatDoesNotExist` does not exist.

### What did you see instead?
```bash
all modules verified
{[] <nil> [] [] [] 0 false false false}
```
Repository: rust
Issue: Regression: "temporary value does not live long enough" in a `static` item in Servo
Labels: C-enhancement,A-diagnostics,A-borrow-checker,T-compiler

Reduced test case:

```rust
#![feature(const_fn)]
const fn require_static<T>(_: &'static T) {}
const fn foo() -> u32 { 0 }
pub static A: () = require_static(&foo());
```

rustc 1.31.0-nightly (5597ee8a6 2018-10-03): OK

rustc 1.31.0-nightly (8c4ad4e9e 2018-10-04):

```rust
error[E0597]: borrowed value does not live long enough
 --> a.rs:4:36
  |
4 | pub static A: () = require_static(&foo());
  |                                    ^^^^^- temporary value only lives until here
  |                                    |
  |                                    temporary value does not live long enough
  |
  = note: borrowed value must be valid for the static lifetime...

error: aborting due to previous error
```

Commit range: https://github.com/rust-lang/rust/compare/5597ee8a6...8c4ad4e9e. https://github.com/rust-lang/rust/pull/53851 seems relevant. @oli-obk, should we use `#[rustc_promotable]` in unstable code, despite the `rustc_` prefix in its name?
Repository: node
Issue: N-API: Need SharedArrayBuffer api
Labels: feature request,node-api

needed feature :
napi_create_external_sharedarraybuffer
napi_get_sharedarraybuffer_info
napi_is_sharedarraybuffer

Since V8 api supports external sharedarraybuffer creation, it would be nice if n-api implements this.
Repository: go
Issue: x/exp/shiny: hebrew keyboard not supported
Labels: NeedsInvestigation

#### What did you do?
I have created a program that logs the `key.Event` from the window, then I tried to type Hebrew rune in my keyboard and the program loged 
```
key = key.Event{(CodeUnknown), key.Modifiers(), Press}
key = key.Event{(CodeUnknown), key.Modifiers(), Release}
```

the program 
```golang
package main

import (
	"fmt"
	"log"

	"golang.org/x/exp/shiny/driver"
	"golang.org/x/exp/shiny/screen"
	"golang.org/x/mobile/event/key"
	"golang.org/x/mobile/event/lifecycle"
)

func main() {
	driver.Main(func(s screen.Screen) {
		w, err := s.NewWindow(&screen.NewWindowOptions{
			Title: "~",
		})
		if err != nil {
			log.Fatal(err)
		}
		defer w.Release()
		for {
			e := w.NextEvent()
			switch e := e.(type) {
			case key.Event:
				fmt.Println("key =", e)
			case lifecycle.Event:
				if e.To == lifecycle.StageDead {
					return
				}
			}
		}
	})
}

```
#### What did you expect to see?
I have expected the `key.Event` to contain the Unicode of the character I pressed.
And the log should be like 
```
key = key.Event{'א' (CodeUnknown), key.Modifiers(), Press}
key = key.Event{'א' (CodeUnknown), key.Modifiers(), Release}
```


#### What did you see instead?
the Unicode was -1.

#### Does this issue reproduce with the latest release (go1.11.1)?
yes

#### System details

```
go version go1.10.1 linux/amd64
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/user/Desktop/go"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="/usr/bin/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-build633916952=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.10.1 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.10.1
uname -sr: Linux 4.18.0-8-generic
Distributor ID:	Ubuntu
Description:	Ubuntu Cosmic Cuttlefish (development branch)
Release:	18.10
Codename:	cosmic
/lib/x86_64-linux-gnu/libc.so.6: GNU C Library (Ubuntu GLIBC 2.28-0ubuntu1) stable release version 2.28.
gdb --version: GNU gdb (Ubuntu 8.2-0ubuntu1) 8.2
```
Repository: flutter
Issue: PlatformView API should be simplified
Labels: platform-android,engine,a: existing-apps,a: platform-views,P2,team-android,triaged-android

This is the minimum amount of code currently required to setup the plumbing for platform views on Android:

```java
Registrar registry = flutterView.getPluginRegistry().registrarFor("FlutterWithPlatformViewActivity");
registry
    .platformViewRegistry()
    .registerViewFactory(
        "myImageView",
        new PlatformViewFactory(StandardMessageCodec.INSTANCE) {
          @Override
          public PlatformView create(Context context, int viewId, Object args) {
            return new PlatformView() {
              @Override
              public View getView() {
                ImageView view = new ImageView(context);
                view.setImageResource(R.drawable.ic_launcher);
                return view;
              }

              @Override
              public void dispose() {}
            };
          }
       });
```

- There should not be a need to register a plugin to use the platform view. I should be able to access the platform view registry directly from FlutterView (or FlutterEngine).
- We should cover the common use cases in a simpler way. E.g. provide an option `SimplePlatformViewFactory` that just has a single method to return the Android view.

Ideally this can be boiled down to:

```java
getPlatformViewRegistry().registerViewFactory(
        "myImageView",
        new SimplePlatformViewFactory() {
          @Override
          public View createView(Context context, int viewId, Object args) {
              ImageView view = new ImageView(context);
              view.setImageResource(R.drawable.ic_launcher);
              return view;
           }
        }
});
```
Repository: angular
Issue: ngValue ignored in ng-content and ng-template
Labels: feature,freq2: medium,area: forms,feature: under consideration

<!--
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 -->
[ ] Performance issue
[x] 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>

This issue was previously reported at https://github.com/angular/angular/issues/22374, which was closed as a support request even though I don't believe it was intended to be one.

## Current behavior

`ngValue` is ignored if (1) the `<option>`s are provided via `<ng-content>` to a component (even if the component simply wraps a vanilla `<select>`) or (2) if the `<option>`s are in an `<ng-template>`.

## Expected behavior

`ngValue` should work the same in these cases as it does when using a plain `<select>` with directly nested `<option>`s.

## Minimal reproduction of the problem with instructions

Please see https://codesandbox.io/s/2z2n2v0pjp .

Here is a screenshot of the reproduction:

<img width="741" alt="image" src="https://user-images.githubusercontent.com/1591879/46542699-4ab9f180-c87c-11e8-93c5-85e06eb2dc61.png">

## What is the motivation / use case for changing the behavior?

Many applications require a custom-styled `<select>` component that allow the caller of the component to provide their own `<option>`s.

## Environment

<pre><code>
Angular version: 6

Browser:
- [x] All
</code></pre>