sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/trace: grey colour is undocumented in goroutine analysis
Labels: Documentation,NeedsDecision,compiler/runtime

<!-- Please answer these questions before submitting your issue. Thanks! -->

1.13.4

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

not need

### What did you do?
I use go tool trace to analysis goroutines


### What did you expect to see?
display clearly each part of the goroutine time


### What did you see instead?
[unknown part of grey color](https://github.com/RealBar/Blogs/blob/master/images/WeWork%20Helper20191220044708.png)
Repository: opencv
Issue: Support OpenCV Swift for macOS catalina
Labels: feature,platform: ios/osx

At the moment we are supporting latest version of Xcode in iOS, but would be really good to support macOS catalina as it is already compatible with iOS apps
Repository: TypeScript
Issue: Invalid output emited as the result of javascript file compilation: amd, default export, jsdoc
Labels: Bug,Help Wanted

**TypeScript Version:**  3.7.3

**Search Terms:** compile javascript default function

**Code**
./index.js
```js
/**
 * @typedef {Does_Not_Matter} <does.not.matter> does_not_matter
 */
export default function MyClass(){
}
MyClass.data = [];
```

**Expected result:**
./out/index.js
```js
define(["require", "exports"], function (require, exports) {
    "use strict";
    exports.__esModule = true;
    /**
     * @typedef {Does_Not_Matter} <does.not.matter> does_not_matter
     */
    function MyClass() {
    }
    exports["default"] = MyClass;
    MyClass.data = [];
});
```


**Actual result:**
./out/index.js
```js
define(["require", "exports"], function (require, exports) {
    "use strict";
    exports.__esModule = true;
    /**
     * @typedef {Does_Not_Matter} <does.not.matter> does_not_matter
     */
    function MyClass() {
    }
    exports["default"] = MyClass;
    exports.MyClass.data = [];
//  ^^^^^^^ HERE IS THE ERROR! 
//  expecting: MyClass.data = [];
});
```


**Compiler options:**
```json
{ 
  "compilerOptions": {
    "outDir": "./out",
    "allowJs": true,
    "checkJs": false,
    "module": "amd",
  },
  "include": [
    "index.js"
  ]
}
```
Repository: kubernetes
Issue: Upgrades of large clusters should be scalability tested
Labels: kind/bug,priority/important-soon,sig/scalability,lifecycle/frozen

As shown in https://github.com/kubernetes/kubernetes/issues/86483, performance of up-and-running large clusters was fine in 1.17, but upgrade of such cluster has high probability of killing the cluster.

We should add "control plane upgrade" scalability test to release blocking tests.

@kubernetes/sig-scalability-bugs 
@liggitt @mm4tt
Repository: scrcpy
Issue: stop recording option is not available in scrcpy
Labels: feature request

I am trying to build a script that can automatically get video from scrcpy without opening the scrcpy application is there any way i can do this. is there any way so that scrapy can record video for some specific time lets say 5 - 10 seconds and then automatically exit the program. or atleast any command that can close the recording without manual intervention
Repository: TypeScript
Issue: __decorate helper should not use `this` when targeting modules
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 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 the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.7.x-dev.201xxxxx

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** __decorate this module

**Code**

```ts
class Foo {
  @property() x = 1;
}
```

**Expected behavior:**
Top-level `this` reference is not emitted.

**Actual behavior:**

The `__decrate` variable is declared like:
```ts
var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
```

Since top-level `this` is always `undefined` in modules, `(this && this.__decorate) || ` can be omitted. It's only a few bytes, but the presence of top-level `this` also causes warnings in other downstream tools like Rollup.

A few other things could be fixed for an ES6+ helper, btw:

- Use `const` instead of `var` (allows for some VM optimizations)
- Remove `Reflect.decorate`
- Don't use `arguments`

**Playground Link:** https://www.typescriptlang.org/play/?ts=Nightly#code/MYGwhgzhAEBiD29oG8BQ1oAEAOAne2AprgC4CeAFAJTQAe0AvNAIwDcqAvkA

**Related Issues:** None?
Repository: godot
Issue: Opening more than 1 editors at the same time, shows error
Labels: bug,topic:editor,confirmed

**Godot version:**
3.2 beta 4
**OS/device including version:**
Ubuntu 19.10
**Issue description:**

**Steps to reproduce:**
1. Download all repository https://github.com/godotengine/godot-demo-projects
2. Scan it
3. Open ~10 projects at the same time
This error should appear
```
ERROR: move_child: Parent node is busy setting up children, move_child() failed. Consider using call_deferred("move_child") instead (or "popup" if this is from a popup).
   At: scene/main/node.cpp:332.
ERROR: close: Condition ' rename_error != 0 ' is true.
   At: drivers/unix/file_access_unix.cpp:172.
```
Repository: PowerToys
Issue: Add Recycle Bin to Windows Task Bar
Labels: Idea-New PowerToy,Product-Tweak UI Design

I do this manually with every system I configure. Many coworkers and family ask how I manged to get the Recycle Bin into my task bar so it's proven to be very popular! Super handy for dragging files to delete and file recovery. I think every Windows user would love to have this automated.

The PowerToy should have a option which will create a folder containing a link to Recycle Bin and then add that new folder as a toolbar in the Task Bar. 

Settings can control whether the icon is large or small and whether text is shown below the icon. There should also be a setting to remove Recycle Bin from the Desktop if it's currently shown.

![image](https://user-images.githubusercontent.com/424909/71282739-f0943780-232c-11ea-96a5-9dee124f60fc.png)

Here are the manual steps I usually use. I'm hoping you'll automate this.

1. Open Documents, right-click > New Folder. Name it RecycleToolbar.
2. Open RecycleToolbar
3. Drag the recycle bin shortcut from Desktop into RecycleToolbar and close the folder. 
4. Right-click Task Bar and unlock.
5. Right-click Task Bar > Toolbars > New Toolbar...
6. Select your new RecycleToolbar
7. Right-click RecycleToolbar grab handle in the Task Bar and change settings (I prefer): View > Large Icons, View > Show Text (un-check it), View > Show Title (un-check)
8. Right-click Task Bar and Lock.  
9. In Settings, turn off the Recycle Bin on the Desktop, it's visual clutter now.
10. Enjoy!
Repository: kubernetes
Issue: Enable deleting API objects even when storage-level decryption is not working properly
Labels: kind/feature,sig/auth,lifecycle/frozen,needs-triage

<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!

If the matter is security related, please disclose it privately via https://kubernetes.io/security/
-->
**What happened**:
Users are unable to delete secrets when kms provider (which originally encrypted such secrets) can no longer decrypt them. There may be several reasons why kms provider would fail to decrypt secrets, the most common one is that users deleted/disabled the version of the key that was used to originally encrypt secrets.

**What you expected to happen**:
Secrets to be deleted.

**How to reproduce it (as minimally and precisely as possible)**:
1. [Setup](https://kubernetes.io/docs/tasks/administer-cluster/kms-provider/#encrypting-your-data-with-the-kms-provider) a cluster with a kms provider of your choice.
2. Create a secret, [validate](https://kubernetes.io/docs/tasks/administer-cluster/kms-provider/#encrypting-your-data-with-the-kms-provider) that the secret is encrypted 
3. Reboot the cluster (this is required to clear the cache of Key Encryption Keys).
4. Disable the key or key version that was used by the provider to encrypt the key in step 2.
5. Attempt to delete the secret. You should get an internal error that wraps the kms-plugin's specific error (the error will vary based on the plugin).

Note: the issue is probably not unique to kms provider, but will manifest itself in any provider when the key that was used to encrypt the secret is no longer available.
**Anything else we need to know?**:
  I believe that the cause of this behaviour is that fact that objects' metadata needs to be updated prior to deletion, which implies the need to transform from storage. However, such transformation is not possible due to the unavailability of the KEK. 
To address this issue we would need to read the metadata of the object (while processing a delete) even if the KEK is not available - after all, during a delete, we don't care about the payload.
Therefore, to enable this scenario we would need to move away from encrypting the whole object. Concretely, parts of the metadata should remain in cleartext. 
I realize that this opens-up a lot of questions, and I could follow this issue up with a KEP. 

**Environment**:
- Kubernetes version (use `kubectl version`):
  1.14

/cc @liggitt @mikedanese @enj 
/sig auth
Repository: go
Issue: cmd/go: two possible canonical states when go.sum is empty, the file may or may not exist
Labels: NeedsInvestigation,GoCommand,modules

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?
go version go1.13.5 darwin/amd64

### Does this issue reproduce with the latest release?
using latest

### What operating system and processor architecture are you using (`go env`)?
macOS Catalina
GOHOSTARCH="amd64"
GOHOSTOS="darwin"

### What did you do?
- Created simple hello world application without dependencies consisting of main.go and a go.mod file containing:

```
module github.com/stephanwesten/hellojob

go 1.13
```

- Executed go build and noticed that no go.sum was generated (unexpected)

- added a dummy dependency to go.mod, re-ran go build and a go.sum was generated.

- removed dependency from go.mod, so it is back to original above, and re-ran go build and go mod tidy

- go.sum was still there.


### What did you expect to see?
(Note that this is the first time for me using go modules so my formulation might not be 100% accurate)
Either go.sum is removed or it should have been generated with the first go.build. This would give symmetric behaviour. 

I would prefer that go.sum is always generated. The reason why this was a problem for me is that I used a Dockerfile template that assumed a go.sum file to be there. 

### What did you see instead?
see above

BTW I entered 'go bug' to file this issue and I got a github error. Perhaps temporary problem?
Repository: javascript
Issue: Rules for nullish coalescing and optional chaining
Labels: semver-breaking: guide change,needs eslint rule change/addition

I noticed that babel-preset-airbnb added the following stage 4 proposals in [v4.2.0](https://github.com/airbnb/babel-preset-airbnb/blob/master/CHANGELOG.md#420---20191114):

- @babel/plugin-proposal-nullish-coalescing-operator
- @babel/plugin-proposal-optional-chaining

Are there any rules/guidelines for these features?
Repository: godot
Issue: Main screen EditorPlugins don't set the bottom anchor
Labels: topic:plugin,topic:gui

**Godot version:** 
Checked in v3.1.2-stable, and latest master

**OS/device including version:**
linux, 4.19.84-1-MANJARO

**Issue description:**
If you add a GraphEdit node to the panel used in a MainScreen in an EditorPlugin, it won't appear.
Every other node i've tested shows up fine.

**Steps to reproduce:**
1. Make an editorplugin and define that it has mainscreen
2. Instance a panel with a graphedit as a child, optionally with a few graphnodes
3. Switch to the mainscreen and it's not there

**Minimal reproduction project:**
[grapheditplugin.zip](https://github.com/godotengine/godot/files/3990334/grapheditplugin.zip)
Repository: node
Issue: Rscript throws error "missing value where TRUE/FALSE needed" when analyzing benchmarks
Labels: benchmark

* **Version**: master
* **Platform**: Ubuntu
* **Subsystem**: http2

Followed documentation to create [comparison benchmarks](https://github.com/nodejs/node/blob/master/benchmark/writing-and-running-benchmarks.md#comparing-nodejs-versions)

Command run:
```console
$ node benchmark/compare.js --old ../node-master --new ../node-http2-for-of --set benchmarker=wrk http2 > compare-http2.csv
[05:52:54|% 100| 5/5 files | 60/60 runs | 12/12 configs]: Done
```

Output file (rename extension to CSV): [compare-http2.txt](https://github.com/nodejs/node/files/3990451/compare-http2.txt)

I receive the following error when trying to analyze benchmarks:
```console
$ cat compare-http2.csv | Rscript benchmark/compare.R
Error in if (w$p.value < 0.001) { : missing value where TRUE/FALSE needed
Calls: ddply ... llply -> loop_apply -> .Call -> <Anonymous> -> .fun
Execution halted
```
Repository: pytorch
Issue: cuCtxGetDevice error and seg fault with DDP and OpenMPI
Labels: oncall: distributed,module: cuda,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->
When using DistributedDataParallel with OpenMPI+UCX for certain tested models I'm getting this error in the DDP constructor (I believe it's during the model broadcast):

```
0: [1576565271.426514] [cgpu06:45376:0]    cuda_ipc_md.c:62   UCX  ERROR cuCtxGetDevice(&cu_device) is failed. ret:invalid device context
0: [1576565271.426547] [cgpu06:45376:0]       ucp_rkey.c:250  UCX  ERROR Failed to unpack remote key from remote md[4]: Input/output error
0: [cgpu06:45376:0:45523] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x20)
```

I observed this error using a resnet50 model but no error if I instead used a very small single-layer CNN.

## To Reproduce

The script is here:
https://github.com/sparticlesteve/nersc-pytorch-build/blob/911fc67b6667d3c6e3be972169e30e34c1a33af5/test_ddp.py

I submit via slurm a single-node job with 8 MPI ranks for 8 V100 gpus, something like:

`srun --ntasks-per-node 8 -u -l python test_ddp.py --backend mpi`

My full log with stack trace is here:
https://gist.github.com/sparticlesteve/7307694f89329c277e16e452b524fefa

## Environment

PyTorch version: 1.3.1
Is debug build: No
OpenMPI: 4.0.1 with UCX 1.6
CUDA used to build PyTorch: 10.1.168
OS: openSUSE Leap 15.0
GCC version: (GCC) 7.3.0 20180125 (Cray Inc.)
CMake version: version 3.14.0
Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: 10.1.168
GPU models and configuration:
GPU 0: Tesla V100-SXM2-16GB
GPU 1: Tesla V100-SXM2-16GB
GPU 2: Tesla V100-SXM2-16GB
GPU 3: Tesla V100-SXM2-16GB
GPU 4: Tesla V100-SXM2-16GB
GPU 5: Tesla V100-SXM2-16GB
GPU 6: Tesla V100-SXM2-16GB
GPU 7: Tesla V100-SXM2-16GB

Nvidia driver version: 440.33.01
cuDNN version: Could not collect

cc @ngimel @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528
Repository: node
Issue: http2/write.js benchmark throws "ERR_HTTP2_ERROR"
Labels: http2

* **Version**: v10.18.0, v12.14.0
* **Platform**: Ubuntu
* **Subsystem**: http2

Command run:
```console
$ h2load --version
h2load nghttp2/1.41.0-DEV

$ node benchmark/run.js --filter write http2

http2/write.js
http2/write.js benchmarker="h2load" size=100000 length=65536 streams=100: 1,898.23
http2/write.js benchmarker="h2load" size=100000 length=131072 streams=100: 1,038.20
events.js:174
      throw er; // Unhandled 'error' event
      ^

Error [ERR_HTTP2_ERROR]: The user callback function failed
    at Http2Session.onSessionInternalError [as error] (internal/http2/core.js:734:26)
Emitted 'error' event at:
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19)
```
Repository: go
Issue: x/tools/internal/event: improve package documentation
Labels: Documentation,NeedsInvestigation,Tools

I know it's an internal package, but the package doc for internal/telemetry is poorly conceived:

```
Package telemetry provides an opinionated set of packages that cover the
main concepts of telemetry in an implementation agnostic way. As a library
author you should look at...
```

It doesn't say what the package does. It claims that the package is "opinionated' (a passive-agressive way to say, we don't care what you think about the design) but gives no hint at what that opinion leads to. Avoid editorializing, just say what the package does. And it wouldn't hurt to say what "telemetry" is and what it's measuring, and for whom.
Repository: terminal
Issue: TermControl key down handling investigation and refactoring
Labels: Area-TerminalControl,Product-Terminal,Issue-Task

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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!
-->

In current TermControl implementation, KeyDown events are handled by PreviewKeyDown event. It uses Tunneling strategy and key down events will first be sent to XAML root element, which is TermControl. 

SearchBoxControl is a child element of TermControl. Thus, key input events on SearchBoxControl will be sent to TermControl first. Now there is an early return check in TermControl::_KeyDownHandler, which prevents key inputs from Search Box to be processed by TermControl. But this is not a good implementation. 

We need to think about using KeyDown instead of PreviewKeyDown event handler in TermControl, but we need to make sure this change won't break anything.
Repository: godot
Issue: [Modifier + Key] action is fired when pressing Key without modifier
Labels: bug,confirmed,topic:input

Sorry if this should be a duplicate. Its not that easy finding anything in 5000+ open issues tho.

**Godot version:**
3.1.2

**OS/device including version:**
Manjaro with kernel 5.4.2

**Issue description:**
When creating an action with a modifier key `event.is_action_released()` returns `true` when only pressing the key without the modifier.
There are a lot of issues with the opposite problem, but i didn't found one about this way around. 

As seen in the relevant code (https://github.com/godotengine/godot/blob/3.1/core/os/input_event.cpp#L312):
```
bool match = get_scancode() == key->get_scancode() && (!key->is_pressed() || (code & event_code) == code);
```
modifiers are simply ignored when the key isn't pressed (key released).

**Steps to reproduce:**
Create action with an modifier. Ctrl+A for example.
In an `_unhandled_input` function do:
```
if event.is_action_released("my_ctrl_a_action"):
    print("ctrl+a action called")
```
and press "A".
Repository: godot
Issue: C# threads / tasks don't work on the web (async / await)
Labels: enhancement,platform:web,topic:dotnet

**Godot version:**
3.2 beta 4
**OS/device including version:**
Windows 10
**Issue description:**
Threading and tasks don't seem to work at all when exporting mono projects to the web.
**Steps to reproduce:**
1. Create a new project.
2. Create a new thread or task in a c# script that does something ( I tried printing to the console via GD.Print )
3. Export for the web
4. Run the exported project in the web browser.
**Minimal reproduction project:**
https://1drv.ms/u/s!AvsEaC7oMEMagstwXvyFlCMdOOMO2A?e=uuytsD
The label should change text to "it worked" when the program starts.
Repository: vue
Issue: Inline style binding is NOT corporate with web standard
Labels: improvement

### Version
2.6.11

### Reproduction link
[https://codesandbox.io/s/thirsty-heisenberg-elvz6?fontsize=14&hidenavigation=1&theme=dark](https://codesandbox.io/s/thirsty-heisenberg-elvz6?fontsize=14&hidenavigation=1&theme=dark)







### Steps to reproduce
1. open the repo
2. check the style of the green box

### What is expected?
The green div's height should be 101px

### What is actually happening?
the green div's height is 22px, cause inline style didn't work on this component

---
I check the web standard that if I assigned a string to a node's style with either `"node.style.cssText"` or add style directly in devtools with this `"height: 100px; height:" `,  the final height will be 100px. Obviously the invalid "height: " will be abandoned. 
Then I check the source code and find that the function `parseStyleText`  only uses regex to split the string and then assign it to result from value by value, no matter what the value is or if the value is valid. That is why the green box's height is incorrect.
Then I create a PR try to fix this issue in web rendering but not in SSR.

<!-- generated by vue-issues. DO NOT REMOVE -->