sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: runtime: helloworld net/http asks 700MB VSS on mips32
Labels: NeedsInvestigation,compiler/runtime

### What version of Go are you using (`go version`)?

<pre>
go version go1.15 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Not sure

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/lshaw/.cache/go-build"
GOENV="/home/lshaw/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/lshaw/.gvm/pkgsets/go1.15/global/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/lshaw/.gvm/pkgsets/go1.15/global"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/lshaw/.gvm/gos/go1.15"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/lshaw/.gvm/gos/go1.15/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
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-build821697598=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

I build a helloworld net/http using : `GOOS=linux GOARCH=mips GOMIPS=softfloat go build -ldflags="-s -w"` and run it on a mips32 board, use top to notice its VSS is 700MB and RSS is 4MB. run multiple of them in parallel will cause 'out of memory' when I set overcommit_memory to 2 very quickly. I have 128MB RAM

The code I use:

```
package main

import (
	"fmt"
	"math/rand"
	"net/http"
	"strconv"
	"time"
)

func main() {
	min := 8080
	max := 60000

	s1 := rand.NewSource(time.Now().UnixNano())
	r1 := rand.New(s1)

	http.HandleFunc("/", func(w http.ResponseWriter, r *http.Request) {
		fmt.Fprintf(w, "Fosiao you had youre request: %s\n", r.URL.Path)
	})

	port := ":" + strconv.Itoa(r1.Intn(max-min))
	//fmt.Println(port)
	http.ListenAndServe(port, nil)
}

```

### What did you expect to see?

I would expect a much smaller VSS on a 128MB 32-bit system, to compare my C/C++ http process only need about 4MB for VSS and 1MB  for RSS

### What did you see instead?

700MB VSS and easily 'out of memory' errors.
Repository: storybook
Issue: JSDoc/TSDoc make Markdown jump line instead of inlining
Labels: feature request,block: description

Is there a way to configure the Markdown TSDoc/JSDoc to jump lines?

```tsx
  /**
   * Prefetch the page in the background.
   * Any <Link /> that is in the viewport (initially or through scroll) will be preloaded.
   * Prefetch can be disabled by passing prefetch={false}.
   * Pages using Static Generation will preload JSON files with the data for faster page transitions.
   *
   * @default true
   */
  prefetch?: boolean;
```

I'd like the above to jump line. Current behavior is to put all in one line.

```tsx
  /**
   * Prefetch the page in the background.
   * 
   * Any <Link /> that is in the viewport (initially or through scroll) will be preloaded.
   * 
   * Prefetch can be disabled by passing prefetch={false}.
   * 
   * Pages using Static Generation will preload JSON files with the data for faster page transitions.
   *
   * @default true
   */
  prefetch?: boolean;
```

I'd need to write the above to jump line, but it takes a lot of space and isn't really better.

Shouldn't the default behaviour be changed?
Repository: godot
Issue: AnimationPlayer.play results in noop when called from animated setget variable
Labels: bug,topic:core

**Godot version:**
3.2.3

**OS/device including version:**
Ubuntu Linux 20.04

**Issue description:**
When animating a script variable (ie. an `export`ed variable) with a `setget`, it is possible that calling `play` on the `AnimationPlayer` from the setter method won't do anything.

This can easily be worked around by using `call_deferred("play", ...)` from the setter instead, but I reckon it'd be worth printing a warning if the animation is currently processing (which I presume is causing this problem).

**Steps to reproduce:**
* Export a `setget` variable
* Animate it using an `AnimationPlayer`
* Note that the setter method runs (eg. use a breakpoint) but that `play` doesn't do anything

**Minimal reproduction project:**
[animation.zip](https://github.com/godotengine/godot/files/5816300/animation.zip)

When running the above, note that the textbox shows 'A' continuously. Uncomment the `call_deferred` line in `Node2D.gd` and you'll note it changes to B.
Repository: flutter
Issue: Different default font color on mobile/desktop versus web
Labels: engine,platform-web,has reproducible steps,P2,found in release: 2.5,found in release: 2.6,team-web,triaged-web

Given the following snippet of code that renders text with an unspecified color on a black background.

```dart
import 'package:flutter/material.dart';
import 'package:flutter/widgets.dart';

void main() {
  runApp(Container(color: Colors.black, child: Text('Hello, World', textDirection: TextDirection.ltr)));
}
```

On windows desktop, this appears as white text on a black background. On web, it appears as a black text on a black background.


Web (Html, but same behavior in CK):

![image](https://user-images.githubusercontent.com/8975114/104641054-20ac2800-565e-11eb-9687-f620d793d19e.png)

Desktop:

![image](https://user-images.githubusercontent.com/8975114/104641140-3de0f680-565e-11eb-8621-485890edb72b.png)
Repository: vscode
Issue: Git - Discarding changes on open file error
Labels: bug,help wanted,git

Hi,
In the source control view, using Git, if I try to discard changes on a file that is currently open (specifically, a CSV file open in Excel), I get an error message that is about arguments being wrong. I would imagine it should give me a file is open error instead of something about arguments.
Repository: create-react-app
Issue: Unexpected token '}'
Labels: needs triage,issue: bug report

Hi there,

When I create a react app using `npx create-react-app my-blog`, this error is showed.

Environment Info:

  current version of create-react-app: 4.0.1
  running from /usr/lib/node_modules/create-react-app

  System:
    OS: Linux 5.8 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  Binaries:
    Node: 15.5.1 - /usr/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 7.3.0 - /usr/bin/npm
  Browsers:
    Chrome: 87.0.4280.141
    Firefox: 84.0.2
  npmPackages:
    react: ^17.0.1 => 17.0.1 
    react-dom: ^17.0.1 => 17.0.1 
    react-scripts: 4.0.1 => 4.0.1 
  npmGlobalPackages:
    create-react-app: 4.0.1

What's wrong?

Best regards.
Repository: create-react-app
Issue: Unexpected token '}'
Labels: needs triage,issue: bug report

Hi there,

When I create a react app using `npx create-react-app my-blog` and then `npm start` this error is showed.

Environment Info:

  current version of create-react-app: 4.0.1
  running from /usr/lib/node_modules/create-react-app

  System:
    OS: Linux 5.8 Ubuntu 20.04.1 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
  Binaries:
    Node: 15.5.1 - /usr/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 7.3.0 - /usr/bin/npm
  Browsers:
    Chrome: 87.0.4280.141
    Firefox: 84.0.2
  npmPackages:
    react: ^17.0.1 => 17.0.1 
    react-dom: ^17.0.1 => 17.0.1 
    react-scripts: 4.0.1 => 4.0.1 
  npmGlobalPackages:
    create-react-app: 4.0.1

What's wrong?

Best regards.
Repository: pytorch
Issue: test_fn_grad_fft_fftn_cpu_complex128 and test_fn_grad_fft_rfftn_cpu_float64 are failing under TSAN
Labels: module: tests,triaged,module: sanitizers,module: fft

Corresponding internal task number: 82355837.

We should probably just skip these tests when using TSAN. 

cc @mruberry @peterbell10 @walterddr @VitalyFedyunin
Repository: electron
Issue: I can open windows to data URLs and have html execute in the window unlike in Chrome
Labels: platform/windows,bug :beetle:,11-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:** Electron 11.2.0
* **Operating System:** Windows 10

### Expected Behavior
In Chrome, if I open a window to a data URL, a window to about:blank opens with the error message
Not allowed to navigate top frame to data URL: data:text/html,<div>Hello world!</div>

This seems to be the case since Chrome 60 ([source](https://developers.google.com/web/updates/2017/06/chrome-60-deprecations#remove_content-initiated_top_frame_navigations_to_data_urls))

### Actual Behavior
In Electron, in a particular case, a window is actually opened to whatever html I put in my data URL.

### To Reproduce
1. start main.js
2. click the open window button
3. see that the html is executed and put into the window

This happens every time in my app, but seems kind of inconsistent in the minimal example.
It seems like sandboxing the window is required to repro this, but sometimes I can repro without that.

Clicking the button multiple times will trigger navigations and then you will see the errors that Chrome logs in the window's devtools.

main.js:
```
const { join } = require("path");
const { app, BrowserWindow } = require('electron')

async function createWindow() {
    const mainWindow = new BrowserWindow({ webPreferences: { nativeWindowOpen: true }});
    await mainWindow.webContents.loadFile(join(__dirname, "index.html"));

    mainWindow.webContents.on("new-window", (e, url, frameName, disp, opts) => {
        opts.webPreferences.sandbox = true;

        e.preventDefault();
        const win = new BrowserWindow(opts);
        e.newGuest = win;
        win.webContents.loadURL(url);
    });

    app.on("browser-window-created", (e, win) => {
        win.webContents.openDevTools();
    });
}

app.on('ready', createWindow)
```

index.html:
```
<!DOCTYPE html>
<html>
  <body>
    <input id="i" />
    <button id="b">Open window</button>

    <script src="./renderer.js"></script>
  </body>
</html>
```

renderer.js:
```
const urlField = document.getElementById("i");
urlField.value = "data:text/html,<script>alert(1)</script>";

document.getElementById("b").onclick = () => {
	const url = urlField.value;
	window.open(url, "a");
};
```
Repository: rust
Issue: .debug_gdb_scripts is being loaded into memory
Labels: A-linkage,A-debuginfo,T-compiler,C-bug,I-heavy

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

If I build:
```rust
fn main() {}
```
with `rustc -g --crate-type bin --emit obj -o t.o t.rs`, and look at the output of `readelf -St t.o` I see:
```
  [27] .debug_gdb_scripts
       PROGBITS               PROGBITS         0000000000000000  0000000000000270  0
       0000000000000022 0000000000000001  0                 1
       [0000000000000032]: ALLOC, MERGE, STRINGS
```

According to https://github.com/rust-lang/rust/pull/41627, this is not supposed to be an alloc section (ie, loaded into memory), but only present in the object file.

Having this section loaded isn't a huge problem in itself, but when combined with `--link-arg -Wl,--strip-all` (or `--strip-debug`) it triggers a crash in lld: https://bugs.llvm.org//show_bug.cgi?id=44878

~There are lld fixes pending (https://reviews.llvm.org/D74510, https://reviews.llvm.org/D91291)~ (lld is already fixed), but it still seems like making .debug_gdb_scripts alloc is unintended.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.49.0 (e1884a8e3 2020-12-29)
binary: rustc
commit-hash: e1884a8e3c3e813aada8254edfa120e85bf5ffca
commit-date: 2020-12-29
host: x86_64-unknown-linux-gnu
release: 1.49.0
```

cc @eddyb @ayermolo
Repository: TypeScript
Issue: Split TypedArray overload into separate overloads
Labels: Suggestion,Awaiting More Feedback

# lib Update Request

## Configuration Check

My compilation *target* is `ESNext` and my *lib* is `the default`.

## Missing / Incorrect Definition

All TypedArrays have five overloads, one of which is the following:
```ts
TypedArray(buffer: ArrayBuffer, byteOffset?: number, length?: number);
```

I believe that this should be split into three separate overloads:
```ts
new TypedArray(buffer: ArrayBuffer);
new TypedArray(buffer: ArrayBuffer, byteOffset: number);
new TypedArray(buffer: ArrayBuffer, byteOffset: number, length: number);
```
or
```ts
new TypedArray(buffer: ArrayBuffer, byteOffset?: number);
new TypedArray(buffer: ArrayBuffer, byteOffset: number, length: number);
```

## Sample Code

I came across something vaguely like this:
```ts
declare function getOffset(): undefined;

const offset = getOffset();

new Uint8Array(new ArrayBuffer(0), offset, 0);
```
and thought that their code definitely had a bug, but, it turns out that undefined-ish values were allowed for the second parameter, because the type was of `number | undefined`.

This would break code, but I believe that this will break little to no code in practice.

## Documentation Link

N/A: no new additions
Repository: flutter
Issue: Document usage of `licenses` key in pubspec.yaml
Labels: tool,d: api docs,P3,team-tool,triaged-tool

This can allow the tool to automatically bundle supplementary LICENSE files (in addition to the root LICENSE/NOTICES) file.
Repository: go
Issue: net: TestReadTimeout failures with "EOF"
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "net" && test == "TestReadTimeout" && `timeout_test.go:\d+: .*EOF`
```

```
--- FAIL: TestReadTimeout (0.31s)
    timeout_test.go:348: #1/1: EOF
FAIL
FAIL	net	47.085s
```

[2021-01-13T23:37:31-7eb31d9/dragonfly-amd64-5_8](https://build.golang.org/log/f06d4d4c72f08845df66e808561d72c6189a480e)
[2020-11-06T19:42:05-362d25f/freebsd-arm-paulzhol](https://build.golang.org/log/d0a3b72d5f80808071c28b9fd3d6e9ebb09e1010)

These failures seem to be quite rare, but the failure mode is not exactly [useful](http://golang.org/wiki/CodeReviewComments#useful-test-failures). It's not clear to me what's going on here.

CC @bradfitz @ianlancetaylor
Repository: pytorch
Issue: Enhance supported fill value type for constant pad in functional.pad
Labels: module: nn,triaged,enhancement,needs design,module: padding

## 🚀 Feature
Support fill value as list/tuple (Sequence) for constant padding in `nn.functional.pad()`.

## Motivation

In torchvision we need to support fill value as list/tuple (Sequence) for constant padding an Tensor image where we rely on torch's pad function. Currently only float is supported in pytorch.
https://github.com/pytorch/vision/issues/3227
https://github.com/pytorch/vision/issues/3224

## Alternatives

We can do some workaround to support it in torchvision, but it would be highly inefficient.

I can try implement this myself if somebody can give me some guidance on how a feature like this is implemented. Since I've not contributed to this repo before.

cc @albanD @mruberry @jbschlosser @datumbox
Repository: terminal
Issue: WM_NCHITTEST returns HTCAPTION for client area and tabs
Labels: Help Wanted,Issue-Bug,Area-UserInterface,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
Please consider placing the tabs into the client area instead of the title bar. Right now the tabs are in the correct place only with setting `"showTabsInTitlebar": false,`. This will cause problems with softwares that utilize the title bars.

![Snipaste_2021-01-14_22-36-17](https://user-images.githubusercontent.com/22566267/104679562-f25d3580-56bb-11eb-9901-41be78851300.png)
Default settings

![Snipaste_2021-01-14_22-32-35](https://user-images.githubusercontent.com/22566267/104679573-f7ba8000-56bb-11eb-9fe5-9e96149a8d3f.png)
`"showTabsInTitlebar": false,`

<!-- 
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)
Take a look at Edge browser. Edge used to place everything in the title bar as well, but now it has been fixed.

![Snipaste_2021-01-14_22-39-10](https://user-images.githubusercontent.com/22566267/104679588-fee18e00-56bb-11eb-9e4d-5f5a4bf787c0.png)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: flutter
Issue: Strange behavior in showTimePicker dialog in keyboard input mode
Labels: platform-android,framework,f: date/time picker,a: internationalization,P2,team-design,triaged-design

A user of my app who has a Samsung Galaxy S20 FE (Android 11) is reporting that the `showTimePicker` input dialog is behaving strangely. The locale is English (United Kingdom). In keyboard entry mode, the input dialog is not accepting what should be a valid 24-hour time. A validation error message "Enter a valid time" is shown when pressing OK button for hours 13 to 23 (pm time). For am hours though, the input was accepted. Dial time picker entry mode seems to be working correctly.

![timepicker](https://user-images.githubusercontent.com/1127628/104683057-1c9d0a80-5731-11eb-8b07-669f72ebeb85.png)

I have asked the user to download the Flutter Gallery app and try out the demo time picker. The results were the same i.e. validation failed for hours 13 to 23 in keyboard mode.

The issue is not reproducible on the Android 11 emulator and on my Android 10 Mi A2 phone. I wonder if this issue only affects certain Android 11 devices (e.g. Samsung Galaxy S20 FE), or if there is a conflicting setting on the device.

## Steps to Reproduce

<!-- You must include full steps to reproduce so that we can reproduce the problem. -->

1. Language on device is set to `English (United Kingdom)`.
2. Launch **Flutter Gallery** app.
3. Navigate to **Material > Pickers > Time Picker**.
4. Open the time picker.
5. Dial the time to a pm time e.g. `20:00`. Tap the keyboard icon to switch to keyboard input mode.
6. The keyboard entry dialog appears, showing `20:00`; Tap **OK** without touching the time boxes.

**Expected results:** <!-- what did you want to see? -->
Time accepted on pressing OK. Dialog is closed.

**Actual results:** <!-- what did you see? -->
`Enter a valid time` validation error message in red appears (even though `20:00` is a valid 24-hour time). Dialog remains opened. Tapping on the input text box to edit causes the app to crash/close.

Note: In the case of my app, the time picker did not crash the app (probably due to different Flutter SDK version?). My app in production is running on Flutter 1.22.3 stable.
Repository: deno
Issue: Use cached cert and key
Labels: public API,suggestion

In Deno one must provide a `certFile` and in some cases `keyFile` whenever dealing with TLS. It should be possible to read the certificate and key data into memory from Deno and send that data to the rust-side of things instead of the rust code reading the files. This can be used to cache the certificate and key data instead of in some instances make multiple IO calls.

Functions that this feature should be implemented on.

https://doc.deno.land/builtin/unstable#Deno.startTls
https://doc.deno.land/builtin/stable#Deno.connectTls
https://doc.deno.land/builtin/stable#Deno.listenTls

I suggest adding a `cert` and `key` properties where it is applicable that can be used instead of the file one. If both cached and file properties are defined I suggest that the cached one takes precedence over the file path one.
Repository: create-react-app
Issue: Misdetection of vim as opened code editor while nvim is running
Labels: needs triage,issue: bug report

There is a [line of code](https://github.com/facebook/create-react-app/blob/7e4949a20fc828577fb7626a3262832422f3ae3b/packages/react-dev-utils/launchEditor.js#L242), where CRA tries to auto-decect which editor is open, and since there is an `indexOf('vim')` invocation, it matches nvim as a vim instance, which behavior is incorrect.

I suggest either add nvim to the editors list, since it's quite popular editor nowadays, or try to respect old good approach to set editors [not as last resort ](https://github.com/facebook/create-react-app/blob/7e4949a20fc828577fb7626a3262832422f3ae3b/packages/react-dev-utils/launchEditor.js#L250) but as at least one of the first before magic happens.

## Expected Behavior

- If any of `EDITOR` or `VISUAL` env-variables are defined, and there is no `REACT_EDITOR` env with a specific editor for CRA, relay on this variables to detect editor and do not perform the magic.
- If there are no `EDITOR` or `VISUAL` and nvim is opened, do not mismatch nvim as vim.
Repository: storybook
Issue: (Vue) Cannot get array prop values from validator or JSDoc
Labels: feature request,vue,block: argstable

**Describe the bug**
Storybook does not extract values for an array prop (Vue).

**To Reproduce**

```js
    /**
     * My prop description
     */
    category: {
      type: String,
      default: 'primary',
      validator: (v) => ['primary', 'secondary', 'white'].includes(v),
    },
```

(for the record, I also tried the `@values small, normal, large` JSDoc comment with no luck).

I haven't been able to make it work, and storybook keeps rendering a text input control with no information about the available types.

I checked, and looks like vue-docgen-api is properly extracting values from a definition such as the ones above.

**Expected behavior**
I expected control addons to display a Select with several options, one for each value of the prop.

**Screenshots**
This is what I get:

![image](https://user-images.githubusercontent.com/9197791/104698175-3f1f2b80-5711-11eb-9e69-a87d9faac93f.png)

Instead, I expect something similar to what documentation shows:

![image](https://user-images.githubusercontent.com/9197791/104698341-84435d80-5711-11eb-9111-5bfcc3195db0.png)


**Code snippets**
If applicable, add code samples to help explain your problem.

**System**
```
  System:
    OS: macOS 10.15.6
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
  Binaries:
    Node: 14.15.0 - ~/.nvm/versions/node/v14.15.0/bin/node
    Yarn: 1.22.10 - ~/.nvm/versions/node/v14.15.0/bin/yarn
    npm: 6.14.11 - ~/Code/(path-to-my-package)/node_modules/.bin/npm
  Browsers:
    Chrome: 87.0.4280.141
    Firefox: 84.0.2
    Safari: 13.1.2
  npmPackages:
    @storybook/addon-a11y: ^6.1.14 => 6.1.14 
    @storybook/addon-actions: ^6.1.14 => 6.1.14 
    @storybook/addon-essentials: ^6.1.14 => 6.1.14 
    @storybook/addon-knobs: ^6.1.14 => 6.1.14 
    @storybook/addon-links: ^6.1.14 => 6.1.14 
    @storybook/addon-viewport: ^6.1.14 => 6.1.14 
    @storybook/vue: ^6.1.14 => 6.1.14 
```


Thank you, folks!