sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Menu widget rendered in greyscale
Labels: bug,help wanted,font-rendering,menus,chromium,lcd-text-rendering

Version: 1.35.1 (user setup)
Commit: c7d83e57cd18f18026a8162d042843bda1bcf21f
Date: 2019-06-12T14:30:02.622Z
Electron: 3.1.8
Chrome: 66.0.3359.181
Node.js: 10.2.0
V8: 6.6.346.32
OS: Windows_NT x64 10.0.18362

I also double checked that the problem is on the Insider's Build.

**Steps to Reproduce:**

1. Observe text on screen. It should have gray subpixel rendering.
![1](https://user-images.githubusercontent.com/14015672/59582781-56b2b000-90a7-11e9-9883-77a1524f9e91.png)
2. Open menu bar.
3. Observe text on screen. It should have RGB subpixel rendering.
![2](https://user-images.githubusercontent.com/14015672/59582788-5c0ffa80-90a7-11e9-9a32-7ece84eda963.png)

This issue occurs on all text (except the menu bar submenus). I noticed it, because the text rendering looks better, but only when the menu bar was open! I would prefer all of it to use RGB subpixel rendering, like my other applications.

**Does this issue occur when all extensions are disabled?:** Yes
Repository: vscode
Issue: Make proxy settings machine scoped
Labels: debt,proxy,under-discussion

I believe the proxy settings we have are scoped to machine and so they should be tagged as Machine scoped.
Repository: create-react-app
Issue: Console clearing removes CRA’s own warnings
Labels: issue: proposal

react-scripts start continuous scrollback clearing (#2495) clears the warnings CRA itself prints. Here is a visual demonstration slowed down:

![blink](https://user-images.githubusercontent.com/113721/59586938-bda68800-90ec-11e9-9a4e-203815fc52f6.gif)

On a faster setup it is near impossible to read the warning before it disappears.

Platform: node 10.15.3, npm 6.9.0
Search terms: clear, console, warning, 2495.

### Steps to Reproduce

1. npx create-react-app my-app foo --typescript 
2. cd foo
3. Delete allowSyntheticDefaultImports option in tsconfig.json
4. npm start

### Expected Behavior

Ideally react-scripts would not clear the scrollback (#2495) and let the user see the logs of what happened in the past. Given the resolution of that issue this is unlikely.

Alternatively, react-scripts should take a lot of care to not clear its own warnings.
Repository: godot
Issue: Tile Painting UI Icon not highlighted
Labels: enhancement,topic:editor,usability

**Godot version:**
3.1.1

**Issue description:**
When I flip the tile, there is no indicator that the tile is already flipped.

This is shown be default
<img width="164" alt="Screen Shot 2019-06-17 at 3 48 42 PM" src="https://user-images.githubusercontent.com/2648571/59591096-9f09b680-9117-11e9-9b93-ebff3da3e047.png">

This is shown when I flipped
<img width="158" alt="Screen Shot 2019-06-17 at 3 48 47 PM" src="https://user-images.githubusercontent.com/2648571/59591150-b21c8680-9117-11e9-840f-d23d9711d7a1.png">

I guess the flip icon should be highlighted like 3.0
Repository: vscode
Issue: Extensions using the "type" command (for ex. Vim) have poor performance due to being single-threaded with other extensions
Labels: feature-request,VIM,perf

I don't know if this is a known/accepted issue, but I've had a number of users complain of poor performance in the editor when using my extension along with the Vim extension.

This appears to be because the Vim extension uses the `type` command to handle keypresses (in the extension host). This means if pressing a key triggers a command that blocks in another extension (for example the first character press can trigger code completion, which if the list is 20,000 items can block the thread for a little while while they're build + serialised) the typing in the editor is really sluggish.

You can easily reproduce this by making an extension that blocks for 1s when asked for completions:

```ts
context.subscriptions.push(vscode.languages.registerCompletionItemProvider({ scheme: "file" }, {
	provideCompletionItems(document: vscode.TextDocument, position: vscode.Position, token: vscode.CancellationToken, context: vscode.CompletionContext): vscode.ProviderResult<vscode.CompletionItem[] | vscode.CompletionList> {
		console.log('Completion request');
		var start = Date.now();
		let i = 0;
		while (Date.now() < start + 10000) {
			// Block for a second...
			i++;
		}
		return [new vscode.CompletionItem(`aaaItem (${i} iterations)`)];
	},
}));
```

If you run this and enabled the Vim plugin, when you start typing on a newline (which triggers completion), the characters you type won't appear for a while.

Of course, extensions should try to avoid blocking the extension host as much as possible, but sometimes it's unavoidable (for ex. assembling and serialising a huge number of completion items). It's not clear where users should raise bugs, since in isolation neither extension is really doing anything wrong.

I don't know what the fix is (separate extension host for type-handling extensions might work, but that might also be a huge task), but I couldn't find any issues discussing this and figured it was worth some discussion (even if only to have the information described in one place we can point people to that hit these issue).
Repository: storybook
Issue: context.parameters.fileName is different in static build
Labels: bug,core

**Describe the bug**
When using `context` the `parameters.fileName` is the actual path (e.g. /folder/Button-story.js) in development but will switch to a number (e.g. 1021) in static production build.

**To Reproduce**
Steps to reproduce the behavior:
Output context in production build.

**Expected behavior**
context should be the same in development and production

**Code snippets**
```javascript
export const withNotes = makeDecorator({
  wrapper: (context) => {
    console.log(context.parameters.fileName);
});
```

**System:**
 - Version: 5.1.8
Repository: scrcpy
Issue: [Suggestion] Put user-friendly name of device in window name
Labels: feature request

For testing purpose
`shell getprop ro.product.model` returns models as **SM-G960F** (Galaxy S9) for samsung devices.
Things like Motorola return readable user-friendly names, i.e. **Motorola E4 Plus**.
But sometimes they don't: **XT1635-02** (Motorola Z Play).
I remember all models which i work with by heart. But eye catches easily when you have window named **Samsung Galaxy S6 Edge+ (SM-G928F)**
`shell settings get secure bluetooth_name` returns almost on every device (Galaxy S4 mini is still GT-9195. But it's initially called like that so doesn't matter) its name if it wasn't changed by user.
**How reasonable is getting the name from settings?** 
It's kind of slow. Or maybe i'm doing that wrong. Because if you make loop which gets info about all connected devices
```
#!/bin/bash
for serial in $(adb devices | awk 'NR>1{print $1}');
	do
		echo  $(adb -s $serial shell settings get secure bluetooth_name | sed "s/\\r//g")
	done
```

it would work significantly slower than
```
#!/bin/bash
for serial in $(adb devices | awk 'NR>1{print $1}');
	do
		echo  $(adb -s $serial shell getprop ro.product.model | sed "s/\\r//g")
	done
```
Repository: create-react-app
Issue: [Documentation] --use-npm & --scripts-version 
Labels: issue: proposal,tag: documentation

- [X] I have checked the issues & could't find the mentioned below.

There should be mention of the following;

- `--use-npm` in the documentation, if someone want's to opt out of `yarn` to use `npm` instead.
- How to use `--scripts-version` when over-riding with your own custom react-scripts.

> npx create-react-app `--scripts-version` CUSTOM_SCRIPT_PATH my-project-name `--use-npm`

I am more than happy to make a PR for this. (I would need some guideance though :))
Repository: pytorch
Issue: Batch Normalization axis
Labels: triaged,module: batching,function request,module: norms and normalization

## 🚀 Feature
Make it possible to specify the axis on which to perform Batch Normalization.

## Motivation
Right now batch normalization is geared towards convolution layers which have typically a  layout of NxCxWxH (in the context of 2D batch normalization). But there are other scenarios possible (for example to apply BN to a RNN) where the features are located at a different axis. The current solution doesn't cater for those scenarios.

## Pitch
Adding the axis makes batch normalization more generic applicable to a wide variety of use cases and is inline with other ML frameworks. Default could still be axis=1 so NxCxWxH is handled as is currently the case but other cases are now also supported.

## Alternatives
The only workaround right now it to shift the different axis before the BN and then move them back again after. Not the most elegant solution.
Repository: create-react-app
Issue: Uncaught TypeError: Super expression must either be null or a function, not undefined
Labels: issue: needs investigation

<!--
  PLEASE READ THE FIRST SECTION :-)
-->

### Is this a bug report?

Yes

### Did you try recovering your dependencies?

Yes

### Which terms did you search for in User Guide?

Yes i do

### Environment

  System:
    OS: macOS 10.14.5
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
  Binaries:
    Node: 8.11.3 - /usr/local/bin/node
    Yarn: 1.15.2 - /usr/local/bin/yarn
    npm: 5.7.1 - /usr/local/bin/npm
  Browsers:
    Chrome: 74.0.3729.169
    Firefox: 64.0.2
    Safari: 12.1.1
  npmPackages:
    react: ^16.8.6 => 16.8.6
    react-dom: ^16.8.6 => 16.8.6
    react-scripts: 3.0.1 => 3.0.1
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to Reproduce

1. Create the build for production
2. Server the build with serve 
3. Enter on the url that serve give for my


### Expected Behavior

Server the build with a normal behave ( normal means the same that i have on a development build )

### Actual Behavior

<!--
  Did something go wrong?
  Is something broken, or not behaving as you expected?
  Please attach screenshots if possible! They are extremely helpful for diagnosing issues.
-->

Yes, the app give a this error:

**Uncaught TypeError: Super expression must either be null or a function, not undefined**

![Screenshot 2019-06-14 at 11 30 56](https://user-images.githubusercontent.com/7295597/59499576-f699ef00-8e97-11e9-9c70-4d591d318723.png)

Here inside the error:
![Screenshot 2019-06-14 at 11 37 21](https://user-images.githubusercontent.com/7295597/59499969-cc94fc80-8e98-11e9-92f1-6db8461a1ceb.png)

### Reproducible Demo

1. Create a react app with cra
2. Install this library https://github.com/dexma/ui-components
3. Make a build to production
4. Server the build with serve npm package

COMMENT: 

I solved this problem putting _**keep_fnames: true**_ on the minimizer plugin TerserPlugin options.

If you pass true to keep_fnames you prevent the compressor from discarding function names. Useful for code relying on Function.prototype.name
Repository: node
Issue: http2: sessionError vs aborted
Labels: http2

A little confusion regarding the 'sessionError' on http2 servers.

I'm getting a lot of `sessionError`s with `ECONNRESET`. This feels more like clients killing their connections, i.e. `aborted` rather than an server/session error? 

I believe currently we are handling most cases where a incoming connection is unexpectedly closed we emit `aborted` events rather than `error`?

Or is there something else that could cause such an error?

Is this a potential bug?
Repository: youtube-dl
Issue: Support for MédiaKlikk (HU)
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2019.06.08. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.06.08**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://www.mediaklikk.hu/video/izorzok-toalmas/
- Single video: https://www.mediaklikk.hu/video/honfoglalo-2019-06-03-i-adas/
- Single video: https://www.mediaklikk.hu/video/eletkerek-2019-04-19-i-adas/
- Playlist/show page: https://www.mediaklikk.hu/musor/izorzok/

## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

MédiaKlikk is the free VOD video platform of MTVA.
MTVA (Media Services and Support Trust Fund) is Hungary's state-owned national public-service broadcasting organization, and it's the successor of MTV (state television service) and MR (state radio service).
The programs are available without a registration, and I don't know if the site uses georestriction.
Repository: TypeScript
Issue: Tooltips / IntelliSense: Don't resolve type aliases (aka "semantic sugar") set explicitly
Labels: Suggestion,Experience Enhancement

We have defined a bunch of "semantic sugar" type aliases like:
![image](https://user-images.githubusercontent.com/4144388/59620493-4b09cc80-912d-11e9-858d-4e79a77622c0.png)

**Status quo (bad):** VS Code is resolving these along the alias chain in tooltips and IntelliSense suggestions (which kinda makes non-sense of the type alias in the first place)
![image](https://user-images.githubusercontent.com/4144388/59620716-d7b48a80-912d-11e9-8a4d-0a3de8ff8cb8.png)(c.f. hovered tooltip over `this.url` at bottom)

**Better:** Let VS Code show `UrlString` as type here instead of `string` to aid developers with semantic sugar as of what type of string to expect.

**Alternative:** Show both, i.e. `BufferingWebSocket.url: UrlString (= string)`.
Repository: rust
Issue: Mention editions when emitting 2015 exclusive errors
Labels: C-enhancement,A-lints,A-diagnostics,T-compiler,A-docs,WG-epoch,A-edition-2018

The difference between edition defaults for new projects between `cargo` and `rustc` can lead to confusion, particularly for newcomers. All errors that would only happen on one edition should mention the discrepancy. We made an effort to have lints for 2015 to 2018 migration, but we were more lax on clarifying diagnostics when following 2018 guides when `rustc` is ran under 2015. Things like nll discrepancies (seen in https://github.com/rust-lang/rust/issues/61855, moot point once we enable nll in 2015) come to mind, while things like `let async = 6;` (pass in 2015, "error: expected pattern, found reserved keyword `async`" without any mention of editions in 2018) which do not mention editions at all (it should recommend using `r#raw_idents` always, explain it was accepted in 2015 edition but it's being run in 2018).
Repository: flutter
Issue: Allow postMessage to return a JS promise to send a message from JS running in a WebView to the application's Dart code
Labels: c: new feature,customer: dream (g3),p: webview,package,c: proposal,team-ecosystem,P2,triaged-ecosystem

Internal: b/343558780

Currently the way to send a message from JS running in a WebView to the application's Dart code is by calling t [JavaScriptChannel](https://pub.dev/documentation/webview_flutter/latest/webview_flutter/WebView/javascriptChannels.html)'s `postMessage` method which has no return value. A response can be sent back from the Dart code to the JS code by calling [evaluateJavascript](https://pub.dev/documentation/webview_flutter/latest/platform_interface/WebViewPlatformController/evaluateJavascript.html).

User's have expressed interest in making it easier to get a response from a `postMessage`, the propose solution would be to have the `postMessage` return a javascript promise and have some convenient wrapper code on the Dart side that takes and return value and calls `evaluateJavascript` to complete the returned promise.

Not having this feature isn't blocking any use case(users can still explicitly call `evaluateJavascript` to "return" a value, and users an even implement the mechanism described above externally to the webview plugin).

#### Availability of JS Promise
According to https://caniuse.com/#feat=promises promise is available starting iOS 8.0 which is what Flutter supports, and starting Android API 20(which is what webview currently support, though technically we can make it support API 19).
Repository: TypeScript
Issue: Issues with Pick causes tsc (on Node12/Win10?) to hang.
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.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.5.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** Pick, mapped types

**Problem:** Unfortunately, I've not been able to reproduce outside my project in small whittled down samples, but the problem causes `tsc` to ***hang*** and as a result really needs to be investigated.  The idea is as follows:  I have an interface `StoreState` which has (among other properties some of which use mapped types) a property called `windows`.  Therefore, the type `Pick<StoreState, 'windows'>` should be equivalent to `{ windows: StoreState['windows'] }`.  Within the content of one of my files, I cast a variable as the latter type and it works like a charm.

```
const { windows } = state as { windows: StoreState['windows'] };
```

However if instead I try to clean the code up by using the `Pick`, it causes the tsc process (and VS code if it's open to that file and I attempt to hover) to hang, take up tons of memory (node/tsc were at over 2gb before I killed it) and never complete the compilation.  

Stranger still is that within the same project, but in a different file, I write the following with no issue.

```
const { windows }: Pick<StoreState, 'windows'> = ...
```

Due to corporate rules I can't simply upload this project to github, however if someone directly from microsoft (i.e. @RyanCavanaugh) sends me a private message, I could send them a zip file of the source, pointing out where to find the issue.  I'm well aware that no one in this forum is interested in my app (especially at this nascent phase in its buildout), but I'm not risking getting fired in order to file a bug when I have an acceptable workaround.
Repository: pytorch
Issue: nn.TransformerLayer
Labels: feature,module: nn,triaged

A generic pytorch transformer layer 

## 🚀 Feature
input: 

a 2-dim Tensor [x_{00}, x_{01},  ... x_{0m_1}, x_{10}, ... x_{1m_1}, ... x_{km_k}]; each x is a vector.

and either (or both, but they should match):
* a 1-dim Tensor of offsets [o_0, ..., o_k ]
* or a list of square 2-dim Tensors [ A_{m_0}, .... A_{m_k}] of attention masks


output: 
a 2-dim Tensor [h_{00}, h_{01},  ... h_{0m_1}, h_{10}, ... h_{1m_1}, ... h_{km_k}]

The inputs follow the arrangement of nn.EmbeddingBag.  Each offset corresponds to the start of a set of inputs x (and the whole input is a set of these sets).    If attention masks are input, they are pointwise multiplied by the attention inner products before the softmax.


## Motivation

This is a generic transformer formulation, and can be used for text, vision, graphs, etc.
Repository: flutter
Issue: Mixing RTL and LTR text bugs
Labels: a: text input,framework,engine,a: typography,customer: crowd,P2,team-engine,triaged-engine

We are seeing strange behavior when mixing RTL and LTR text.

Notably:

- Type arabic, Type chinese, Type arabic, switch to chinese keyboard, delete. The arabic will delete all at once.
- Emojis work strangely when mixing with RTL and LTR.
- Caret positioning is not consistent.

There are a few other minor issues that I am not clear on how to describe.
Repository: TypeScript
Issue: Type narrowing based on iterator `done` value?
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.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.4.0-dev.201xxxxx

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
interface MyIterator<T> {
    next():
      | {
          done: false;
          value: T;
        }
      | {
          done: true;
          value: undefined;
        };
    [Symbol.iterator](): MyIterator<T>;
}

interface Item { name: string }

function m(iter: MyIterator<Item>) {
    for (const it of iter) {
        console.log(it.name);           // Error here complaining about 'it': Object is possibly 'undefined'.ts(2532)
    }
}
```

**Expected behavior:**

**Actual behavior:**

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->
https://typescript-play.js.org/?downlevelIteration=true#code/JYOwLgpgTgZghgYwgAgLIE8CSkpzAeygB4AVAPmQG8AoZO5ECADzAAoBKALlvroB8qPXrwAm+Rp2TwANgGcIAbiHC6ANzjSArhEkklKugF9l-QQfpiJyMFG37zydVp3JNIERBigII+yuO8fsgA2gDK6AC2AEb40gB0wDh4hAC6HJIY2NDJxORKxtSgOPBIyFkRVAxwES6yNqAA5sgFMG4IYMDiyBGsidAZWEkExOVk7Gb0MITIrAjidciJyPgwizjjNOZzILKxEHHS+A29YHEg1RDsCg50APS3yACiUFDTABbQKHMRAA7ScKBGsg4DFNGBkAByRIQyQAeSiACsIO1FrJkD98LJZMAotJ0JC3B4vIwRBC4mBZKwAEwAVgAzFT2NRlMZDEA

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
https://github.com/microsoft/TypeScript/issues/11450 seems related. but here even with `--strictNullChecks` same error is reported here.