sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Coloured Android navigation bar not working with Launch Screen
Labels: c: new feature,platform-android,engine,P3,team-android,triaged-android

## Steps to Reproduce

I have a styles.xml file where I am trying to change the colour of the android navigation bar (the system one with three buttons) on the launch screen. The code is:

```
<?xml version="1.0" encoding="utf-8"?>
<resources>
    <!-- Theme applied to the Android Window while the process is starting -->
    <style name="LaunchTheme" parent="@android:style/Theme.Black.NoTitleBar">
        <!-- Show a splash screen on the activity. Automatically removed when
             Flutter draws its first frame -->
        <item name="android:windowBackground">@drawable/launch_background</item>
        <item name="android:navigationBarColor">@android:color/black</item>
    </style>
    <!-- Theme applied to the Android Window as soon as the process has started.
         This theme determines the color of the Android Window while your
         Flutter UI initializes, as well as behind your Flutter UI while its
         running.
         
         This Theme is only used starting with V2 of Flutter's Android embedding. -->
    <style name="NormalTheme" parent="@android:style/Theme.Black.NoTitleBar">
        <item name="android:windowBackground">@drawable/launch_background</item>
        <item name="android:navigationBarColor">@android:color/black</item>
    </style>
</resources>
```

The line `<item name="android:navigationBarColor">@android:color/black</item>` works for the "NormalTheme" changing the bar to black. However, it seems to be ignored for the "LaunchTheme". I can't work out why. The [documentation](https://developer.android.com/reference/android/view/Window#setNavigationBarColor(int)) says that the [FLAG_DRAWS_SYSTEM_BAR_BACKGROUNDS](https://developer.android.com/reference/android/view/WindowManager.LayoutParams#FLAG_DRAWS_SYSTEM_BAR_BACKGROUNDS) has to be set in order for this property to work. Could it be that this is not set for the Flutter launch?

**Expected results:** 
I want to see a differently coloured Android navigation bar when launching the app

**Actual results:**
I saw a white Android navigation bar when launching the app, that transitioned into a black one once it was showing the secondary launch screen it shows when Flutter is initialising.
Repository: rust
Issue: Misleading compilation error message in desugaring of closure with mutable reference
Labels: C-enhancement,A-diagnostics,A-closures,T-compiler,D-confusing

I tried this code:

```rust
struct A(i32);

struct B {
    arr: Vec<A>
}

impl B {
    fn using_iterator(&mut self) -> Vec<&A> {
        (0..2).map(|i| &self.arr[i]).collect()
    }
}
```

I expected to see this happen:
While I understand that because of the mutable reference and how closures are desugared, the code is expected to not compile. But the error message seems misleading.
I expected to receive a compilation error message which explained multiple mutable borrows.
(discussion at - https://users.rust-lang.org/t/lifetimes-in-closures-with-captured-mutable-reference/43721 

Instead, this happened:
Received misleading error message 
```
9 |         (0..2).map(|i| &self.arr[i]).collect()
  |                    ^^^  ---- `self` is borrowed here
  |                    |
  |                    may outlive borrowed value `self`
```
https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=e538deb64a5702e8e13cb5dbf106b130

### Meta
Tried on both stable and nightly
`rustc --version --verbose`:
```
rustc 1.43.0 (4fb7144ed 2020-04-20)
binary: rustc
commit-hash: 4fb7144ed159f94491249e86d5bbd033b5d60550
commit-date: 2020-04-20
host: x86_64-apple-darwin
release: 1.43.0
LLVM version: 9.0
```

```
rustc 1.45.0-nightly (fe10f1a49 2020-06-02)
binary: rustc
commit-hash: fe10f1a49f5ca46e57261b95f46f519523f418fe
commit-date: 2020-06-02
host: x86_64-apple-darwin
release: 1.45.0-nightly
LLVM version: 10.0
```
Backtrace:
Repository: node
Issue: repl: uncomplete expression shouldn't be autocompleted.
Labels: repl,discuss

<!--
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**: v14.4.0, maybe master
* **Platform**: macOS
* **Subsystem**: repl

### What steps will reproduce the bug?
In repl:
```js
> proc // then press `enter` key
```
<!--
Enter details about your bug, preferably a simple code snippet that can be
run using `node` directly without installing third-party dependencies.
-->

### How often does it reproduce? Is there a required condition?
Every time.

### What is the expected behavior?
Throw `Uncaught ReferenceError: proc is not defined`.
<!--
If possible please provide textual output instead of screenshots.
-->

### What do you see instead?
Print the entire `process` object.
<!--
If possible please provide textual output instead of screenshots.
-->

### Additional information
This bug was introduced in recent release.

Maybe /cc @BridgeAR 
<!--
Tell us anything else you think we should know.
-->
Repository: go
Issue: x/crypto/acme: confusing error when ACME CA does not implement pre-authorization flow
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14.4 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
yes (latest version in use)


### 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="/home/[username removed]/.cache/go-build"
GOENV="/home/[username removed]/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY="github.com/[company name removed]/*,[company internal git hosting]/*"
GONOSUMDB="github.com/[company name removed]/*,[company internal git hosting]/*"
GOOS="linux"
GOPATH="/home/[username removed]/go"
GOPRIVATE="github.com/[company name removed]/*,[company internal git hosting]/*"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/[username removed]/dev/certman/webui/webui/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-build840948656=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

Using `golang.org/x/crypto/acme` (`golang.org/x/crypto v0.0.0-20200510223506-06a226fb4e37` in `go.mod`), I register an account with Lets Encrypt's staging v2 API and then call [Client.Authorize()](https://pkg.go.dev/golang.org/x/crypto/acme?tab=doc#Client.Authorize). This fails because [Discover()](https://pkg.go.dev/golang.org/x/crypto/acme?tab=doc#Client.Discover) returns a [Directory](https://pkg.go.dev/golang.org/x/crypto/acme?tab=doc#Directory) with `AuthzURL` set to the empty string indicating the pre-authorization flow is not supported by the CA.

### What did you expect to see?
Some form of `The CA does not implement pre-authorization flow` error message.

### What did you see instead?
An error returned with text `Post "": unsupported protocol scheme ""`
Repository: PowerToys
Issue: FancyZones: Sound event for an accoustic confirmation of a snapped in window
Labels: Idea-Enhancement,Help Wanted,FancyZones-Dragging&UI,Product-FancyZones

# Summary of the new feature/enhancement

Can we please have a Windows sound event which can be set with an individual sound file for an accoustic confirmation of a snapped in window?


# Proposed technical implementation details (optional)

Add a new category in the following Sound dialog, for instance "PowerToys FancyZones" and add a new event "Window snap in complete", which will be triggered when the window is snapped in a new zone.

![grafik](https://user-images.githubusercontent.com/41678833/83640998-324c2e00-a5ad-11ea-8899-9fe83383e6d4.png)
Repository: TypeScript
Issue: Add named type arguments
Labels: Suggestion,Awaiting More Feedback

## Search Terms
generics, type parameters, named parameter, named type parameter, type argument, named type argument

## Suggestion
It should be possible to pass type arguments to a generic by name rather than positionally, eg.
```typescript
interface Foo<T = SomeDefaultType, U> { ... }

// Current syntax
const foo: Foo<SomeDefaultType, string> ...

// Proposed syntax
const foo: Foo<U = string> ...
// yields foo: Foo<SomeDefaultValue, string>
```
This is loosely inspired on python's named arguments:
```python
def foo(bar = "I'm bar", baz):
    ...

foo(baz="I'm baz")
```
## Use Cases

Generics only accept positional type arguments. If you have a generic accepting many type arguments, most or all of which having default values such as:
```typescript
interface Handler<Type = string, TPayload = object, TOutput = void> {
  type: Type
  handle(payload: TPayload): TOutput
}
```
Let's say we have a class which implements the Handler interface but the defaults for `Type` and `TPayload` are fine for us and we only want to specify a type for `TOuput`, currently it is mandatory that we pass type arguments for `Type` and `TPayload`:
```typescript
class Foo implements Handler<string, object, Promise<number>>
```

If it was possible to pass type arguments by name we could use the considerably terser form:
```typescript
class Foo implements Handler<TOutput=Promise<number>>
```

## Examples
[Fastify](https://github.com/fastify/fastify) exposes types generic over many parameters with default values, such as 
```typescript
  interface FastifyRequest<
    HttpRequest = http.IncomingMessage,
    Query = DefaultQuery,
    Params = DefaultParams,
    Headers = DefaultHeaders,
    Body = DefaultBody
  > { ...
```

With the proposed syntax we could create specialized interfaces with much less overhead such as 
```typescript
import * as fastify from 'fastify';

const app = fastify();
app.get('/users/:id', async (req: FastifyRequest<Params = {id: string }>, res: FastifyReply) => {
   // req.params is strongly typed now
})
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: vscode
Issue: Add settings search synonym - password/authentication
Labels: bug,settings-editor,settings-search

https://github.com/microsoft/vscode-remote-release/issues/3109
Repository: vscode
Issue: Tasks: Pick folder for user tasks in multi-root-workspaces
Labels: feature-request,tasks,workbench-multiroot

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
User-Tasks in Multi-Root-Workspaces should ask in which workspace Folder they should be executed. Currently every User-Task will only be executed in the first workspaceFolder.
Repository: vscode
Issue: Allow for "random access" undos
Labels: feature-request,undo-redo

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

Refs: https://github.com/microsoft/vscode/issues/99159

> The undo fails regardless of the change made in the other file. I wonder if VS Code could be smart enough to see that the range effected by the edit/undo wasn't changed, and be able to handle the rename (even line-level detection would probably work)
Repository: rust
Issue: Macro expansion for expr
Labels: A-macros,T-compiler,C-bug

```rust
#![feature(raw_ref_op)]
macro_rules! offset {
    ($ty: tt, $field: expr) => {
        unsafe { &raw const ((*(0 as *const $ty)).$field) } as usize
    };
}

struct Emm {
    a: i32,
    b: u64,
}

fn main() {
    let tmp = offset!(Emm, b);
    let tmp = unsafe { &raw const ((*(0 as *const Emm)).b) } as usize;
}
```
Code below expanded into this result:
```rust
#![feature(prelude_import)]
#![feature(raw_ref_op)]
#[prelude_import]
use std::prelude::v1::*;
#[macro_use]
extern crate std;
struct Emm {
    a: i32,
    b: u64,
}
fn main() {
    let tmp = unsafe { &raw const ((*(0 as *const Emm)), b) } as usize; // Weird
    let tmp = unsafe { &raw const ((*(0 as *const Emm)).b) } as usize;
}
```
Noticing the `, b` in the weird line. After changing the `expr` in `offset!` to `ident`, this problem fixed. Is this a bug? I cannot find any documentation about it. If it's not, I guess we can write about it in the rust reference.
Repository: create-react-app
Issue: Add option `"root": true` to `eslintConfig` in `package.json`
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

https://eslint.org/docs/user-guide/configuring#configuration-cascading-and-hierarchy

> By default, ESLint will look for configuration files in all parent folders up to the root directory.

### Describe the solution you'd like

```diff
 {
   ...
   "eslintConfig": {
+    "root": true,
     "extends": "react-app"
   }
   ...
 }
```
Repository: flutter
Issue: flutter run shows log lines from other Flutter apps on Android
Labels: c: new feature,platform-android,tool,a: debugging,has reproducible steps,P2,found in release: 3.0,found in release: 3.1,team-android,triaged-android

*@Reprevise commented on Jun 3, 2020, 5:02 PM UTC:*

I'm on Dart 2.8.3, and my OS is Windows. I don't know whether to post this in Flutter or here, but it has things to do with logging. Anyways, I was debugging my Flutter application and then I clicked on a notification from one of my other apps. Apparently this app was also built with Flutter and I could see it's debug logs.

Shouldn't logs be limited to my app, and not all of the other apps on my phone built with Flutter? Some of these logs could contain sensitive information.

*This issue was moved by [devoncarew](https://github.com/devoncarew) from [dart-lang/sdk#42175](https://github.com/dart-lang/sdk/issues/42175).*
Repository: node
Issue: ERR_MODULE_NOT_FOUND recommends what I asked it to import
Labels: esm

<!--
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**: v14.4.0
* **Platform**: Darwin L7 19.5.0 Darwin Kernel Version 19.5.0: Thu Apr 30 18:25:59 PDT 2020; root:xnu-6153.121.1~7/RELEASE_X86_64 x86_64
* **Subsystem**: esm modules

### What steps will reproduce the bug?

```sh
mkdir -p node_modules/@broken_imports
echo 'export const lala = 3' > node_modules/@broken_imports/lala.js
echo "import { lala } from '@broken_imports/lala.js'" > test_imports.js
node test_imports.js
```
ok, now, we'll make it a es module package. it'll still say the same error.
```sh
echo '{"name": "test-pkg", "type": "module"}' > node_modules/@broken_imports/package.json
node test_imports.js
```

### How often does it reproduce? Is there a required condition?
always happens for me. should output:
```
internal/modules/run_main.js:54
    internalBinding('errors').triggerUncaughtException(
                              ^

Error [ERR_MODULE_NOT_FOUND]: Cannot find package '@broken_imports/lala.js' imported from /Users/kenny/test/test_imports.js
Did you mean to import @broken_imports/lala.js?
    at packageResolve (internal/modules/esm/resolve.js:620:9)
    at moduleResolve (internal/modules/esm/resolve.js:659:14)
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:752:11)
    at Loader.resolve (internal/modules/esm/loader.js:97:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:242:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:50:40)
    at link (internal/modules/esm/module_job.js:49:36)
```

### What is the expected behavior?
I expected it to import. the docs say: https://nodejs.org/api/esm.html#esm_no_node_path

```
No NODE_PATH#
NODE_PATH is not part of resolving import specifiers. Please use symlinks if this behavior is desired.
```

tried with symlinks too, and couldn't get it to work.
Repository: rust
Issue: Get rid of /rustc/$hash hack
Labels: C-cleanup,P-medium,T-compiler

Spawned off of https://github.com/rust-lang/rust/pull/72767/commits/a8e4236edc1e118ccb6c3f3a8d0139e4cd90b5b8

Right now, `/rustc/$hash` is used as a magic prefix to track paths into libstd source so that it can be remapped to local developer paths when they install the rust-src component.

But, as @eddyb pointed out on PR #72767, once we are willing to actually allocate another entry in the `FileName` enum (or its moral equivalent, splitting the payload of one of its variants into two via a separate `RealFileName` enum), then we should be able to do away with the `/rustc/$hash` prefix hack entirely within the rustc source code.
Repository: pytorch
Issue: JIT test suite has dependencies across tests
Labels: oncall: jit,triaged

Steps to reproduce:
1. Induce a bug by adding more type annotations. https://github.com/ezyang/pytorch/tree/poc/jit-bug is what I was working on when this happened
2. Run these tests:

```
(/home/ezyang/local/pytorch-tmp-env) [ezyang@devvm066.ash0 ~/local/pytorch-tmp] python test/test_jit.py TestScript.test_circular_depend
ency
Couldn't download test skip set, leaving all tests enabled...
.
----------------------------------------------------------------------
Ran 1 test in 0.211s

OK
(/home/ezyang/local/pytorch-tmp-env) [ezyang@devvm066.ash0 ~/local/pytorch-tmp] python test/test_jit.py TestScript.test_attribute_in_init TestScript.test_circular_dependency
Couldn't download test skip set, leaving all tests enabled...
.F
======================================================================
FAIL: test_circular_dependency (__main__.TestScript)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "test/test_jit.py", line 5303, in test_circular_dependency
    self.getExportImportCopy(C())
  File "/data/users/ezyang/pytorch-tmp/torch/jit/__init__.py", line 1581, in init_then_script
    original_init(self, *args, **kwargs)
  File "test/test_jit.py", line 5296, in __init__
    self.foo = torch.nn.Sequential(B())
  File "/data/users/ezyang/pytorch-tmp/torch/jit/__init__.py", line 1587, in init_then_script
    self.__dict__["_actual_script_module"] = torch.jit._recursive.create_script_module(self, make_stubs)
  File "/data/users/ezyang/pytorch-tmp/torch/jit/_recursive.py", line 305, in create_script_module
    concrete_type = concrete_type_store.get_or_create_concrete_type(nn_module)
  File "/data/users/ezyang/pytorch-tmp/torch/jit/_recursive.py", line 264, in get_or_create_concrete_type
    concrete_type_builder = infer_concrete_type_builder(nn_module)
  File "/data/users/ezyang/pytorch-tmp/torch/jit/_recursive.py", line 128, in infer_concrete_type_builder
    assert attr_type.is_interface_type()
AssertionError

----------------------------------------------------------------------
Ran 2 tests in 0.152s

FAILED (failures=1)
(/home/ezyang/local/pytorch-tmp-env) [ezyang@devvm066.ash0 ~/local/pytorch-tmp] python test/test_jit.py TestScript.test_attribute_in_init
Couldn't download test skip set, leaving all tests enabled...
.
----------------------------------------------------------------------
Ran 1 test in 0.047s

OK
```

Individually the tests pass but together they fail.

cc @suo
Repository: rust
Issue: cargo doc output layout improvement for pub const
Labels: T-rustdoc,C-feature-request

<!-- Thanks for filing a 🙋 feature request 😄! -->

**Describe the problem you are trying to solve**
<!-- A clear and concise description of the problem this feature request is trying to solve. -->

The current `cargo doc` output layout is difficult to read. For example, the HTTP status codes on this[ doc page](https://docs.rs/http/0.2.1/http/status/struct.StatusCode.html). As an honest comparison, here is the similar doc on [Python page](https://docs.python.org/3/library/http.html#http-status-codes).  Note that Rust's page has the same info, but with a different layout. The problem is the layout.

**Describe the solution you'd like**
<!-- A clear and concise description of what you want to happen. -->

My request is: change the default layout of `cargo doc` to :
- A clear section for struct's `Consts`, separate from `Methods`.
- Remove duplicated info, for example:  all `pub const` can be in one sub-section titled `pub const` and no need to repeat `pub const` for each value. Also, no need to repeat the struct name for each const value.
- Consider using a table format for `Consts`.

**Notes**
<!-- Any additional context or information you feel may be relevant to the issue. -->
Repository: flutter
Issue: Flutter ellipsis is broken when using a custom font with fontWeight other than normal
Labels: framework,engine,a: typography,has reproducible steps,P2,found in release: 2.0,found in release: 2.3,team-engine,triaged-engine

This does not seem right, the issue is that I have downloaded the "Oxygen-Regular.ttf" from Google Fonts, and added it to my flutter app (as all the other fonts I have in the app). Regarding text 
```
child: Text(
   "some text", 
    overflow: TextOverflow.ellipsis, 
)
```
using this specific font, the ellipsis gets broken (displays a square) whereas other fonts do not. I have looked for the problem and it seems that this specific font does not have the "ellipsis" character (U+2026). My question is, in these cases, when fonts cannot display ellipsis, can it be replaced by three dots? Or, is there any solution to this issue and how can this be solved, even if there is nothing better than putting three dots instead of ellipsis?

Thanks in advance. There is no flutter doctor attached because my question does not attend directly a problem **in** Flutter, I just need some kind of instruction or advice.
Repository: terminal
Issue: The Terminal needs to support `"cursorTextColor": null`
Labels: Area-Rendering,Area-Settings,Product-Terminal,Issue-Task

Follow up from #6337

Spec'd in #6151

Currently, the terminal always draws the cursor on top of text. #6337 is going to change the Terminal to always draw the cursor _underneath_ the text. Before we release a build with #6337 in it, we should add a setting to allow users to return to the current behavior.