sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: TS2377 reported for constructors that unconditionally throw or use return override
Labels: Suggestion,Awaiting More Feedback

## TypeScript Version:
3.7.0-dev.2019-10-10

## Search Terms:
- TS2377
- TS 2377
- TS2377 throw
- TS 2377 throw

## Code

Code like this is also generated by [`webidl2js`](https://www.npmjs.com/package/webidl2js):

```ts
class Foo extends Object {
	constructor () {
		throw new TypeError("Illegal constructor");
	}
}
```

Same with

```ts
class Foo extends Object {
	constructor () {
		return Object.create(new.target.prototype);
	}
}
```

### Expected behavior:
No error

### Actual behavior:
```
error TS2377: Constructors for derived classes must contain a 'super' call.

2     constructor() {
      ~~~~~~~~~~~~~~~
3         throw new TypeError();
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4     }
  ~~~~~
```

and

```
error TS2377: Constructors for derived classes must contain a 'super' call.

2     constructor() {
      ~~~~~~~~~~~~~~~
3         return Object.create(new.target.prototype);
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
4     }
  ~~~~~
```

### Playground Link:
[🔗](https://www.typescriptlang.org/play/?ssl=1&ssc=25&pln=1&pc=19#code/MYGwhgzhAEBiD29oFMAeAXZA7AJjA8gEYBWyw60A3gLABQ0D0w8WE6ATgK7nzsAUASip1Go6OgAW7eAHdoWZHIAqATwAOyAKLtp-AQG4RjAL51TtIA)

## Related Issues:
- #3696
Repository: flutter
Issue: [webview_flutter] Allow programmatic scroll control 
Labels: c: new feature,customer: crowd,p: webview,package,team-ecosystem,P3,triaged-ecosystem

Per https://github.com/flutter/plugins/pull/2107 users are interested in programmatically scrolling webviews and listening to current scroll positions.
Repository: vue
Issue: when <select> model and the option list changed at the same time, model may incorrectly set to `undefined`
Labels: bug,has workaround

### Version
2.6.10

### Reproduction link
[https://jsfiddle.net/4fyrj95L/](https://jsfiddle.net/4fyrj95L/)







### Steps to reproduce
set model binded to select element and the array that iterated the option list at the same time

make sure the new model value do not match any of the new options

the model will be set to `undefined`

### What is expected?

model value to be set to `1`

### What is actually happening?
model's value set to `undefined`

---
This bug only appears when model and the options changed at the same and the new model value does not match any option, other situations behaves correctly as far as I tested.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: pytorch
Issue: Documentation makefile should include torchvision
Labels: module: docs,triaged,module: doc infra

We should ideally be able to build all the docs in a single command. Right now we build the docs for pytorch and torchvision separately and "copy and paste" the docs for torchvision into pytorch. This is not very efficient and it's easy to forget this last step. 

cc @ezyang
Repository: flutter
Issue: [google_maps_flutter] Sometimes requires the WAKE_LOCK permission
Labels: c: crash,platform-android,p: maps,package,dependency: android,e: OS-version specific,P2,team-android,triaged-android

This was uncovered as part of debugging #42349. 

Occasionally Maps requests the WAKE_LOCK permission when the virtual display is resized with a default `GoogleMap`. It's most likely coming from the Google Maps SDK, but there isn't any obvious reason why this should be. There are a few cases I could find in maps that require that permission, but none of them seem to be related to a default map being resized. 

- There's a wearable version of maps that allows for an "ambient mode" that requires WAKE_LOCK.
- I'm also seeing a [`GeoFenceHadrwareImpl`](https://android.googlesource.com/platform/frameworks/base/+/master/core/java/android/hardware/location/GeofenceHardwareImpl.java) class in AOSP that also requires a wake lock, but I don't know if that itself is referenced anywhere with Maps. I don't think our plugin should be using either of those, but we are deferring to the SDK so it's hard to really tell.

In addition this reproduces extremely flakily, around 2% of the time in my testing. It's also only seen on Q, implying that it's the Maps SDK interacting with Android somehow.

The plugin should ideally avoid whatever code path requires this permission or at least alert developers to it and ask them to add it to their manifests.
Repository: TypeScript
Issue: Poor error recovery when `enum` is used as a parameter name
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.6.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** expression expected reserved word

**Code**

```ts
function converter<Enum>(values: string[], enums: Enum[]): Map<Enum, string> {
	return new Map<Enum, string>(
		enums.map((enum: Enum, index: number) => [ enum, values[index] ])
	);
}
```

**Expected behavior:**
After some confusion why this displays so many red curlies, the error should make it clear to me that the reserved word `enum` is accidentaly being used as an argument name. An error is given on `enum` saying something along the lines of *You cannot use enum as a variable/argument because it is a reserved word*.

**Actual behavior:**
After a LOT of confusion, one realizes that the reserved word `enum` is accidentally being used as an argument name. An error is given on several parts in the above code, where the most helpful one is *Expression expected (ts1109)*, which is just unnecesarily confusing.

**[Playground Link](https://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=2&pc=22#code/GYVwdgxgLglg9mABBBA3ApgJylgPAUTBAFsA+AClQEMAbEdAZwC5EGpMYwBzAbQF0ANInRFizRIRL8AlCwCyVAA4FRQth26lEAbwBQASEzooITEjDoA7ogXLJxNe05cKB-SJIMAdMSXlyHsQs9kKcACboAB4sogBGWNKIALxaPMKqiNR0jDzhUXyIfNIG0gDcugC+QA)** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
None that seem related.
Repository: rust
Issue: Formatting of std::backtrace::Backtrace
Labels: C-enhancement,T-libs-api,E-medium,PG-error-handling

I'd like to propose some changes to formatting of the `Backtrace` type introduced in https://github.com/rust-lang/rust/issues/53487.

- Don't include newlines in the default `Debug` output. I personally find it pretty jarring when looking at the debug output of an error where everything is on the same line except the backtrace, and then any additional properties are printed way down on the last line.

  I'd suggest instead printing a "list" of "maps", such that it'd look like `[{ function: "errors::new", file: "./src/new.rs", line: 21 }, ...]`.
- Allow passing the "precision" format flag to limit how many frames are printed. The most relevant frames are normally near the top, but deciding exactly how many depends on the app. Then a user could write `println!("short trace: {:.5}", trace)` to see just 5 frames.
- Remove `stack backtrace:\n` prefix entirely. When formatting, I'd think a user would pick their own prefix, like `println!("Call stack:\n{}", trace)`.
Repository: thefuck
Issue: Support `source ~/.bashrc` when installing
Labels: enhancement,help wanted,hacktoberfest

When you first install thefuck, you get this nice message.

```
$ fuck
Seems like fuck alias isn't configured!
Please put eval "$(thefuck --alias)" in your ~/.bashrc and apply changes with source ~/.bashrc or restart your shell.
Or run fuck second time for configuring it automatically.
More details - https://github.com/nvbn/thefuck#manual-installation

$ fuck
fuck alias configured successfully!
For applying changes run source ~/.bashrc or restart your shell.
```

Which is great and I love it, however, when I run `fuck` again, I get the same message.

```
$ fuck
fuck alias configured successfully!
For applying changes run source ~/.bashrc or restart your shell.
```
Seems like an oversight. It should suggest running `source ~/.bashrc`.
Repository: terminal
Issue: Touch Zoom with two fingers don't work on Touch screen (but it works on Touch Pad)
Labels: Help Wanted,Issue-Bug,Area-TerminalControl,Product-Terminal,Priority-2

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

When I use two finger to zoom in or out (actually making text bigger or smaller), it works on my touch pad. But it actually don't work on my touch screen.

I think the experience would be much smoother if it worked the same on the touch pad and the touch screen.

What I also get is, if I scroll with finger on the touch screen it works. If I try to scroll with two fingers it flickers, as if the program doesn't realize I using two fingers and tries to read both inputs.

So the case with multiple fingers should probably be detected and handled specifically.

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)

If I use two fingers on the touch screen and move them together or away from each other the font size should decrease or increase respectively, exactly as it is now if I do that on the touch screen.

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: godot
Issue: Script editor minimap is not exactly aligned when dragging the region
Labels: bug,topic:editor,confirmed

Godot 3.2 alpha1

When the edited script is long enough to make the minimap scroll while dragging it, the dragged area will actually drift away from the mouse.
Note: turning off "scroll past end of file" doesn't affect this.

![image](https://user-images.githubusercontent.com/1311555/66607283-c0e9e600-ebab-11e9-97b5-e822758ad463.png)
Repository: flutter
Issue: Reland "Test child isolates are terminated when root is shutdown" after test fix.
Labels: team,engine,P2,team-engine,triaged-engine

This patch was reverted in https://github.com/flutter/engine/pull/13067 due to LUCI failures.
Repository: flutter
Issue: gradle_jetifier_test fails on macOS Cirrus
Labels: a: tests,platform-android,tool,platform-mac,t: gradle,P2,team-android,triaged-android

```
[gradle_jetifier_test] [STDOUT] Executing: find /usr/local/share/android-sdk -name dexdump
[gradle_jetifier_test] [STDOUT] "find" exit code: 0
[gradle_jetifier_test] [STDERR] Task failed: Exception: Couldn't find a dexdump executable.
```

Currently this test is disabled on Cirrus by virtue of the shard not being included on macOS; I turn that shard on in one of my PRs but I'm going to disable the test for now.
Repository: node
Issue: Refactor Worker and NodeMainInstance class to reuse code
Labels: process

Opening an issue to discuss about how to refactor the `Worker` and `NodeMainInstance` class to reuse code.

My current plan is to create a base class `NodeInstance` and try to strip out common code in `WorkerData`/`Worker` as well as `NodeMainInstance` in there, and then make `Worker` and `NodeMainInstance` inherit from `NodeInstance`.

This is useful in adding support for startup snapshots in workers and ContextifyContext - otherwise we need to repeat e.g. snapshot availability detection code in multiple places which can be tricky to maintain.

Refs: https://github.com/nodejs/node/issues/29842
Repository: react
Issue: mouseEnter behaves like mouseOver when using ReactDOM.render() to mount a child element
Labels: Component: DOM,Type: Needs Investigation

<!--
  Note: if the issue is about documentation or the website, please file it at:
  https://github.com/reactjs/reactjs.org/issues/new
-->

**Do you want to request a *feature* or report a *bug*?**
Bug

**What is the current behavior?**
When using `ReactDOM.render()` to mount a child element, `mouseEnter` behaves like `mouseOver` (`mouseLeave` behaves like `mouseOut`).  you can see the demo, and when my cursor moves between the red and blue blocks, it will repeatedly trigger mouseEnter and mouseLeave.
https://codepen.io/sen-dream/pen/VwwvGbm

**What is the expected behavior?**
https://codepen.io/sen-dream/pen/WNNQgoy

**Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?**
Testes with React 16.8 on Chrome/macOS. It didn't work in previous versions.
Repository: flutter
Issue: Add-to-app Flutter build script fails when Podfile is in different directory from Xcode project
Labels: platform-ios,tool,a: existing-apps,P3,team-ios,triaged-ios

We found that there is `Run Flutter Build Script` in flutter 1.9. 
```
flutter_export_environment_path = File.join('$SRCROOT', relative, 'flutter_export_environment.sh');
  script_phase :name => 'Run Flutter Build Script',
    :script => "set -e\nset -u\nsource \"#{flutter_export_environment_path}\"\n\"$FLUTTER_ROOT\"/packages/flutter_tools/bin/xcode_backend.sh build",
    :input_files => [
      File.join('$SRCROOT', flutter_application_path, '.metadata'),
      File.join('$SRCROOT', relative, 'App.framework', 'App'),
      File.join('$SRCROOT', relative, 'engine', 'Flutter.framework', 'Flutter'),
      flutter_export_environment_path
    ],
    :execution_position => :before_compile
```
Under normal circumstances can meet our normal use. However, **if our `Podfile` is not in the `.xcodeproj` directory, ie the `Podfile` is not in the `$SRCROOT` directory,** then this place is faulty.

`File.join('$SRCROOT', flutter_application_path, '.metadata'),` 
`File.join('$SRCROOT', relative, 'App.framework', 'App')` 
` File.join('$SRCROOT', relative, 'engine', 'Flutter.framework', 'Flutter')` 
` File.join('$SRCROOT', relative, 'flutter_export_environment.sh')` these paths are **not exists**.

## Suggestion:
I suggest that we can add a parameter `pod_path`.

in `Podfile`:
```
pod_path = current_Podfile_path
```
```
install_all_flutter_pods(flutter_application_path, pod_path)
```

in `podhelper.rb`:
```
pod_path ||=flutter_application_path
```
```
flutter_export_environment_path = File.join(pod_path, relative, 'flutter_export_environment.sh');
  script_phase :name => 'Run Flutter Build Script',
    :script => "set -e\nset -u\nsource \"#{flutter_export_environment_path}\"\n\"$FLUTTER_ROOT\"/packages/flutter_tools/bin/xcode_backend.sh build",
    :input_files => [
      File.join(pod_path, flutter_application_path, '.metadata'),
      File.join(pod_path, relative, 'App.framework', 'App'),
      File.join(pod_path, relative, 'engine', 'Flutter.framework', 'Flutter'),
      flutter_export_environment_path
    ],
    :execution_position => :before_compile
```
[podhelper.rb.txt](https://github.com/flutter/flutter/files/3716635/podhelper.rb.txt)
Repository: node
Issue: Http2Stream emit connection related 'error' after receiving all data of stream.
Labels: stream,http2

The following conditions cause an error event on `http2stream`, even though `http2stream` received all data and RST_STREAM from a client.
1) `http2stream` is not destroyed(does not consume all data)
2) goaway frame is not received
3) socket error happens
4) `http2stream` received all data and RST_STREAM


Socket error without goaway frame causes a `http2session.destroy(err)`.
https://github.com/nodejs/node/blob/81bc7b3ba5a37a5ad4de0f8798eb42e631d55617/lib/internal/http2/core.js#L2678-L2688

`http2session.destroy(err)` propagate error to `http2stream.destroy(err)`.
https://github.com/nodejs/node/blob/81bc7b3ba5a37a5ad4de0f8798eb42e631d55617/lib/internal/http2/core.js#L1298-L1323

I thought that `http2stream` got RST_STREAM means that there is no error about processing data. So, I thought if `http2stream` is closed by RST_STREAM, connection error should not cause `http2stream` error.

The codes to reproduce.
```js
'use strict';

const common = require('../common');
const fixtures = require('../common/fixtures');
const http2 = require('http2');
const fs = require('fs');
const net = require('net');

const tmpdir = require('../common/tmpdir');
tmpdir.refresh();
const loc = fixtures.path('person-large.jpg');

const server = http2.createServer();
let session_;
server.on('session', (session)=>{
  session_ = session;
});
server.on('stream', common.mustCall((stream) => {
  let sum = 0;
  stream.pause();
  const slowRead = ()=>{
    setTimeout(()=>{
      const data = stream.read(stream._readableState.highWaterMark/10);
      sum += data ? data.length: 0;
      console.log('read:' + sum + ' soc:' + socket.bytesWritten + ' closed:' + stream.closed + ' destroyed:' + stream.destroyed);
      if(stream.closed){ // Got RST_STREAM and stream was closed but all data isn't processed.
        socket.destroy(); // destroy connection without goaway frame.
        try{
          session_.ping(()=>{}); // activate read.
        }catch(err){
          console.log(err);
        }
      }
      slowRead();
    }, 10)
  };
  slowRead();
  stream.respond();
  stream.end();
  stream.on('error', (err)=>{
    // Stream allready closed, but error event happens.
    console.log(err);
  });
}));

let socket;
server.listen(0, common.mustCall(() => {
  const options = {
    createConnection: (authority, options) => {
      socket = net.connect(server.address().port, 'localhost');
      return socket;
    }
  }
  const client = http2.connect(`http://localhost:${server.address().port}`, options);
  const req = client.request({ ':method': 'POST' });

  req.on('response', common.mustCall());
  req.resume();
  const str = fs.createReadStream(loc);
  str.on('end', common.mustCall());
  str.pipe(req);
}));
```
Repository: flutter
Issue: Developing Flutter with VSCode and WSL2
Labels: c: new feature,tool,platform-windows,P3,team-tool,triaged-tool

Since I mostly develop Web, using nginx, PHP and MySQL, I have ported my WebDev-environment entirely to WSL2. 
Since performance is very important, all my web-related projects reside on the WSL2-vhdx file `/home/user/Projects/Web`. In WSL2 I've installed all my necessary tools for a nice and neat Linux-like experience, Docker, GIT, etc.. This combined with VSCode remote integration works very well.

Now, I'm digging into building Flutter-Apps, and my Flutter-environment is installed on the Windows side. My Flutter-related projects reside on `D:\Projects\Flutter` which is a partition, and **NOT USED** in WSL2 in any way. Building Flutter-apps with flutter-windows-sdk and VSCode works neatly. 

But, the problem is: Now I've my project files scattered all across my computer. Web-stuff in a WSL2-vhdx-file and Flutter-stuff on the D-partition.

Is there a way to build flutter-apps with Flutter, while having the project-files stored on a WSL2-vhdx-file, in combination with VSCode-remote and an Android-emulator?

I tried creating a test Flutter-project on the `\\wsl$` network mount, which didn't work.
Repository: electron
Issue: Child window's previous maximized/minimized state isn't restored when minimizing and restoring the parent window
Labels: platform/windows,bug :beetle:,status/confirmed,5-0-x,component/BrowserWindow,7-1-x,10-x-y

### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:** 5.0.7
* **Operating System:** Windows 10

### Expected Behavior
If I open a child window and maximize it, then press Windows+D to hide all the windows, and press it again to undo that, I expect the previous visibility state of the window to be restored, and the window should be maximized like before.

Same thing for minimizing the parent window and unminimizing it.

### Actual Behavior
The window isn't maximized and appears to be restored to the normal bounds from before the maximized/minimized state change.

Same thing with minimizing the window.

This doesn't occur if the window isn't set up as a child window the main window.

### To Reproduce
```
const { app, BrowserWindow } = require('electron')

async function createWindow() {
	const mainWindow = new BrowserWindow();
	const childWin = new BrowserWindow();
	childWin.setTitle("Child");
	childWin.setParentWindow(mainWindow); // commenting this out will fix the issue
}

app.on('ready', createWindow)
```
Repository: vscode
Issue: Extension proxy doe not tunnel https to http
Labels: bug,proxy

<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.39.1
- OS Version: Ubuntu 18.04.3 LTS

Steps to Reproduce:

1. Run VS Code behind a proxy with HTTPS_PROXY set to an http url
2. Use the Atlascode or any extension that makes https calls

Expected: the requests work
Actual: the requests fail. Most of the time the error reported is "socket hang up"

I believe the chromium proxy stuff internally handles tunneling https to http when running behind an http proxy, However, I don't think VS Code handles this when it rewrites the https module for extension proxy support.

We've been able to get around this by adding this to our axios requests when behind a proxy:

```
const [host, port] = getProxyHostAndPort();

                let numPort = undefined;
                if (host.trim() !== '') {
                    if (port.trim() !== '') {
                        numPort = parseInt(port);
                    }
                    agent = {
                        httpsAgent: tunnel.httpsOverHttp({
                            proxy: {
                                host: host,
                                port: numPort
                            }
                        }), proxy: false
                    };
                }
```

It would be ideal if VS Code just handled this for extensions.