sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: resolving multiple tasks with type npm and same script fails
Labels: bug,tasks,polish


Issue Type: <b>Bug</b>

Create 2 tasks with "type": "npm" and same "script"

Expected both tasks to be resolved by their label

- VsCode will list only one of those tasks when listing available tasks with "Tasks: Run Task".
- Depending tasks will fail with "Couldn't resolve dependent task 'x' in workspace folder 'y'" in the "Tasks" output.

**tasks.json:** 

```json
{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "start_both",
            "type": "shell",
            "dependsOn": [
                "start_nr_1",
                "start_nr_2"
            ],
            "problemMatcher": []
        },
        {
            "label": "start_nr_1",
            "type": "npm",
            "script": "start",
            "problemMatcher": []
        },
        {
            "label": "start_nr_2",
            "type": "npm",
            "script": "start",
            "options": {
                "env": {
                    "SOME": "option"
                }
            },
            "problemMatcher": []
        },
    ]
}
```

**package.json:**

```json
{
  "scripts": {
    "start": "echo running 'start' script"
  }
}
```

VS Code version: Code 1.43.1 (fe22a9645b44368865c0ba92e2fb881ff1afce94, 2020-03-18T07:01:20.184Z)
OS version: Windows_NT x64 10.0.19041

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (8 x 3592)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>viz_display_compositor: enabled_on<br>viz_hit_test_surface_layer: disabled_off_ok<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|15.92GB (8.47GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter -->
Repository: vscode
Issue: [rename on type] strange behavior with auto indent in closing tag
Labels: bug,editor-synced-region

Issue Type: <b>Bug</b>

Ref #88424

Set `"editor.autoIndent": "full"` (default) and `"editor.renameOnType": true`

Code for test
```html
<!DOCTYPE html>
<html lang="en">
<head>
    <title>Document</title>
</head>
<body>
    <span>
        content
    </span> <!-- is initial cursor position is between `span` and `>`-->
</body>
</html>
```

1. Set cursor to the end of `span` inside of closing tag
1. Use <kbd>Backspace</kbd> to remove `span`
    Open and closed tags are `<>` and `</>` respectively
1. Start to typing `div`
    1. After typing `d` open tag is still `<>`, closed tag is moved to the start of the line and has `</d>`
    1. After typing `iv` it would be `<iv>` and `</div>`

Setting `"editor.autoIndent": "advanced"` doesn't have this problem.

Looks like wrong indent for closing tag might be related to #32871 but looks strange that `d` is lost in opening tag but other characters added after that.

/cc @octref


VS Code version: Code - Insiders 1.44.0-insider (c0eea2a712471a4d242d15704cfa968241d63280, 2020-03-19T09:27:54.357Z)
OS version: Windows_NT x64 10.0.18363

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz (12 x 3192)|
|GPU Status|2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>protected_video_decode: enabled<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>viz_display_compositor: enabled_on<br>viz_hit_test_surface_layer: disabled_off_ok<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|31.72GB (18.08GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter -->
Repository: node
Issue: rewrite bind function in prototype with console inside causes Maximum call stack size exceeded
Labels: console

Version: v12.4
Platform:Darwin Kernel Version 18.6.0

my issue code is quite simple:

```js
Function.prototype.bind = function () {
  console.log(1)
}

const fn = function () {}
fn.bind()
```

![image](https://user-images.githubusercontent.com/10890665/77067657-4b1e5c00-6a20-11ea-8798-ffe3a0ae21d0.png)

it works well in chrome, I don't know if it'a a feature or bug in nodejs

thanks
Repository: godot
Issue: Spatial 'look_at' strange behaviour
Labels: topic:core

**Godot version: 3.2.1**

**OS/device including version: Windows 10**

**Issue description: See example project**

**Steps to reproduce: See example project**

**Minimal reproduction project: https://github.com/Albatros53113/Turn-Zylinder/tree/master**

The issue is best described by looking at the example project 'readme'. Sorry if this is not an issue and I missunderstood some concepts, but seems like 'look_at' changes the axis it looks with.
Repository: vscode
Issue: Minor UI inconsistencies: Input theme references
Labels: ux,settings-editor,under-discussion

I expected that the overall search input in the UI preferences view is styleable via `settings.textInputBackground` and `settings.textInputForeground`. But currently it is styled via `input.background` and `input.foreground` only.

Please take a look at the attached screenshot. And you may want to use this setting snippet for further debugging.

<img width="1280" alt="vscode-input-theme-references" src="https://user-images.githubusercontent.com/3532570/76908802-e640f580-68a9-11ea-9c7e-c2644cf3dc85.png">

```
    "workbench.colorCustomizations": {
        "input.background": "#0000ff",
        "input.border": "#ffff00",
        "input.foreground": "#ffffff",
        "settings.textInputBackground": "#00ff00",
        "settings.textInputForeground": "#000000",
        "settings.textInputBorder": "#ff0000",
    },
```
Repository: pytorch
Issue: Rename Dispatcher::findSchema to Dispatcher::findOperator
Labels: triaged,module: dispatch

https://github.com/pytorch/pytorch/pull/34456#discussion_r393886732
Repository: pytorch
Issue: Deprecate and remove RegisterOperators
Labels: triaged,module: dispatch

Once the new operator registration api lands, it will be profitable to remove the old API so we can tighten up internal invariants related to how many times a def can happen. Deprecation strategy:

1. Migrate all uses we have direct control over to the new API
2. Make it invalid to mix new-style with old-style registration, but preserve multiple defs for old api. This will break anyone who overrides PyTorch methods, but will not break anyone who defines new ops with the old api
3. Make it invalid to use default alias analysis kind in default api. I don't think this will break anyone. If they are broken they can just migrate to new API.
4. Delete the old API entirely, at which point def can only happen once.

I don't know how long it will take to get to the last step though.
Repository: pytorch
Issue: Make operator registrations truly commutative using priority
Labels: triaged,module: dispatch

Static initializers may run in arbitrary order; we must design static initialization so that no matter what order they run you get the same result. This is not currently true for cases where you override a kernel with another (currently done to support Jupyter notebooks). Let's make this case commutative too, by associating registrations with priority, and then always taking higher priority. Reloads of kernels increment a "Jupyter" priority which makes overrides in this case chronological.

Priority is an "enum", but with a reserved space of sequential identifiers for chronological Jupyter identifiers.
Repository: flutter
Issue: [pigeon] Codegen can accidentally use reserved keywords
Labels: package,team-ecosystem,p: pigeon,P2,triaged-ecosystem

When upgrading video_player to pigeon I ran into 2 different issues where codegen was using symbols which had reserved semantics in the target language:

- A message called "init" - when codegening for the message in objc "init:error:" was generated which has special rules in objc (it should return instancetype, which it wasn't)
- A field called "package" - the java parser is dumb and will get tripped up if you have a field that is named package, reserving that word for top level statements.

We can try to build these rules into the pigeon parser as we find them.

cc @xster
Repository: vscode
Issue: Replace in search Editor
Labels: feature-request,search-editor

Having a replace field in the search editor would permit to quickly replace all occurence without having to manage each occurence.

Bonus point for displaying difference like in search panel
Repository: kubernetes
Issue: Remove prometheus dependencies from k/k codebase
Labels: kind/cleanup,kind/feature,sig/instrumentation,lifecycle/frozen

As part of Metrics Stability KEP we migrated from Prometheus client to Kubernetes Metrics Framework. So we no longer need to depend on promethues client directly.

I configured Bazel to forbid importing prometheus directly. https://github.com/kubernetes/kubernetes/blob/master/hack/verify-prometheus-imports.sh (EDITED)

Example PR that removes reference https://github.com/kubernetes/kubernetes/pull/85289

There are still couple of directories that need to be cleaned up:
* [x] `cluster/images/etcd-version-monitor` (@zhouya0, https://github.com/kubernetes/kubernetes/pull/89413)
* [x] `pkg/master` (@zhouya0)
* [x] `pkg/scheduler/` (@gavinfish, https://github.com/kubernetes/kubernetes/pull/98338)
* [ ] `pkg/volume` (@gavinfish, https://github.com/kubernetes/kubernetes/pull/98729)
* [x] `staging/src/k8s.io/apiserver/pkg/admission/metrics` (@tanjunchen, https://github.com/kubernetes/kubernetes/pull/89285)
* [x] `staging/src/k8s.io/apiserver/pkg/util/flowcontrol/metrics` (@tanjunchen)
* [ ] `test/e2e_node`  (@gavinfish)

/sig instrumentation
/kind cleanup
/cc @logicalhan 

Please volunteer if your interested in working on certain directory.
/help
Repository: vscode
Issue: Snap: Register code as an editor in Debian with update-alternatives
Labels: help wanted,feature-request,install-update,linux,snap

Issue Type: <b>Bug</b>

This is a bug report regarding a feature that was implemented here: https://github.com/microsoft/vscode/issues/3541

1) Install Ubuntu 18.04 LTS
2) Open Snap Store aka "Ubuntu Software"
3) Search for VSCode
4) Click on VSCode
5) Click install
6) Wait for install to complete
7) Open terminal
8) run "update-alternatives --config editor"

Expected: VSCode appears as an option. See https://github.com/microsoft/vscode/issues/3541
Actual: VSCode does not appear as an option

VS Code version: Code 1.43.1 (fe22a9645b44368865c0ba92e2fb881ff1afce94, 2020-03-18T07:17:38.324Z)
OS version: Linux x64 5.3.0-42-generic snap

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz (8 x 3829)|
|GPU Status|2d_canvas: unavailable_software<br>flash_3d: disabled_software<br>flash_stage3d: disabled_software<br>flash_stage3d_baseline: disabled_software<br>gpu_compositing: disabled_software<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>protected_video_decode: disabled_off<br>rasterization: disabled_software<br>skia_renderer: disabled_off_ok<br>video_decode: disabled_software<br>viz_display_compositor: enabled_on<br>viz_hit_test_surface_layer: disabled_off_ok<br>webgl: unavailable_software<br>webgl2: unavailable_software|
|Load (avg)|1, 0, 0|
|Memory (System)|31.27GB (24.04GB free)|
|Process Argv|. --no-sandbox|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter -->
Repository: PowerToys
Issue: Browser Picker
Labels: Idea-New PowerToy

# Browser picker so you can have rule-based default browsers

This is something I've wanted to write, but just haven't had time to do so. I originally considered this a store app, but I think PowerToys is a much better fit because this is more of a power user thing.

Many of us use multiple browsers so we can keep cookies separate. Most apps, however, want to launch just the default browser. In apps that support it, right now, I have to right-click and copy the URL and then paste it into the browser I want to use. That's clumsy.

Instead, it would be great to be able to set up rules for which browser to open. For example:

- Links from app <X> (example: Outlook, or VS Code, or Terminal) always open in browser <Y>
- Links to domain <Z> (example: outlook.com, or localhost) always open in browser <Y>
- Links from app <X> or domain <Z> always prompt for the browser
- Would include protocol handling in there as well
- And you can set a fall-though, which becomes your new effective default browser for when no rules apply. That default may be to prompt.

The browser would be an actual browser on the system, and also options like inprivate/incognito as appropriate.

<!-- 
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

The Browser Picker would be registered as the default browser. It would apply the rules and, if there's a match, open the browser selected. No UI needed in this case.

There would also need to be either a config UI, and/or a well-understood JSON file with the rules.

If no match, the default could be to use a specific browser, or to prompt.
Repository: pytorch
Issue: Options for printing the shape with print(tensor)
Labels: module: printing,triaged

It has been a fairly frequent feature request to print the shape of a tensor when printing the tensor in Python with `print(tensor)` (and it was controversial when we stopped printing the shape awhile ago).

We've been somewhat reluctant to do this because:
1) it doesn't match NumPy
2) it's not usable in the repr
2) the cost is asymmetric.  I.e. printing is worse than not printing because you can't unprint. This can matter in cases like printing a list of 0-dimensional tensors where printing the shape would blow up the total print size.

But, giving users control has advantages.

So, I propose the following:
1) Implement a `shape=` parameter that does "shape checking except when the shape is not expressible".

For the majority of cases, this would just be verifying that the size matches the size of the passed-in data, e.g.:

```
>>> torch.tensor([1, 2, 3, 4, 5], shape=(5,))
tensor([1, 2, 3, 4, 5])

>>> torch.tensor([1, 2, 3, 4, 5], shape=(2, 3))
RuntimeError: BAD SHAPE
```

Note, there is one exception to shape printing which already exists, which is that we print the shape of the tensor when it's not expressible via the `torch.tensor` constructor:

```
>>> torch.randn(0,2,3)
tensor([], size=(0, 2, 3))
```

First, we should change this to `shape` to be consistent with NumPy.  But we should also just make this expressible by supporting shape specification when the shape isn't expressible via the data.

2) Start printing when the data is summarized

In this case, you can't copy the string to the repr anyway

3) Add options to the print options to print the shape (https://github.com/pytorch/pytorch/blob/master/torch/_tensor_str.py)

I'd propose starting with 2 options: 'always', 'default'.
Always always prints.
Default only prints when the string is ambiguous or summarized
Repository: vscode
Issue: Please make it possible to add gutter (margin) before the text area
Labels: feature-request,editor-rendering

Please consider making an option to add gutter before the text area to improve usability.
Currently it is problematic to use the mouse to place the caret in the beginning 
of the line because there is no gutter to trap the mouse selection cursor:
On the screenshot below I try to place the cursor before the dot, and need to be 
pixel-precise to make so.   

![Code_1pplK1AaJt](https://user-images.githubusercontent.com/12515548/77123628-afa5df00-6a51-11ea-948a-abbe1cda9391.png)



Also I find it annoying when something "sticks" to the text/code, whether 
it is folding icons or line numbers (if folding is off) so I personally always want some 
extra margin to the left to improve readability.

The setting could be named something like:

	"editor.leftMargin": 5,

The number would indicate the margin width in characters, I suppose.
In addition, an option to control how the mouse click behaves in this area should be added,
I suggest "line selection" mode or "standard selection" mode.
For "standard selection" a placeholder cursor would be shown just like in text.
For "line selection" pointer cursor would be shown, like by clicking on the line number area.
Repository: flutter
Issue: run web drivers from dev directory
Labels: a: tests,framework,platform-web,P3,team-web,triaged-web

Running web drivers from lib directory is creating a warning in the logs.

Change it to run from dev. Steps:

1) Copy the file to the dev directory
2) Change plugins repo to use it from dev
3) Change flutter repo to use it from dev
4) Change engine repo to use it from dev
5) remove the unused file from lib
Repository: youtube-dl
Issue: Square thumbnails
Labels: request

## Checklist

- [X] I'm reporting a feature request
- [X] I've verified that I'm running youtube-dl version **2020.03.08**
- [X] I've searched the bugtracker for similar feature requests including closed ones

## Description

Feature to crop thumbnail to a sqaure format (1:1 aspect ratio).
e.g.: --embed-thumbnail RATIO
Repository: PowerToys
Issue: Fast Delete
Labels: Idea-New PowerToy,Product-File Explorer,Product-File Actions Menu

# Summary of the new feature/enhancement

<!-- 
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).
-->
If you want to delete a lot of files (large number of files, not large files) thru File Explorer, right now it is a very slow process, compared to doing the same thru the command line.


# Proposed technical implementation details (optional)
I would like to have a power option that enabled me to fast delete a selection of files from Explorer. Pretty much what this provides:
https://www.ghacks.net/2017/07/18/how-to-delete-large-folders-in-windows-super-fast/
Which is pretty much this:
`DEL /F/Q/S *.* > NUL`
That would be much better than typing the command!
Repository: pytorch
Issue: Generator C++ API should match Python API
Labels: module: cpp,triaged,module: random

I tried to do it in #34968 but that PR added c-tor Generator(Device device) to C++ API to match Python API, to avoid code duplication the logic was moved from THPGenerator_pynew to corresponding at::Generator c-tor. Unfortunately it made Generator.h dependent on CPUGenerator.h and CUDAGenerator.h, but this is how our Python API works :(

cc @yf225
Repository: node
Issue: Tracking Issue: enable sanitizers on our CI
Labels: meta,memory

### What are sanitizers?

[Sanitizers](https://github.com/google/sanitizers) are build options which can be used to identify programming errors in C++. They add overhead to the program, which is why it's not recommended to use in releases, but they can be valuable to find memory leaks and other potential crashes on our tests. V8 has [ASAN buildbots](https://ci.chromium.org/p/v8/builders/try/v8_linux64_asan_rel_ng/b8886122785772680448?) which run on every CL, and they are [working on making their code base UBSan compatible](https://bugs.chromium.org/p/v8/issues/detail?id=3770&q=ubsan&can=2) as well.

### Cool, what do we need to make it happen?

Well, first thing, asan has to work on Node.js. We have `--enable-asan` on `configure` today, and the build will work on most computers (it requires a considerable amount of memory). But most of our tests will fail with it, because our code base is not ASAN clean. We might be also missing some ASAN flags: looking at V8 source code and build dependencies, they do one thing or two different.

There's also the memory issue: as of right now, we need a big machine to build with ASAN. GitHub Actions can't run an ASAN build because it "only" has 7Gb. Hopefully there's something we can tune in the build to use less memory. Otherwise, we'll need a custom machine for it (probably on Jenkins).

As for other sanitizers (like UBSan), upstream projects need to support those first, so we are blocked for now.

#### To Do List (ASAN)

- [ ] Investigate huge memory consumption during build
- [ ] Move gengjiawen/node-build to `nodejs/` org
  - [ ] Move repository
  - [ ] Move Docker build to Node.js Docker hub
- [ ] Enable build on our CI (no tests)
	- This will ensure we don't break the build moving forward
- [ ] Fix failing tests
	- [ ] Once everything is working, enable tests on our CI
- [ ] Fix ASAN flags for OS X
- [ ] Fix ASASN flags for Windows

#### To Do List (UBSan)

- [ ] Wait for V8 to be UBSan compatible ([v8:3770](https://bugs.chromium.org/p/v8/issues/detail?id=3770&q=ubsan&can=2))
	- [ ] Enable build on our CI (no tests)
		- This will ensure we don't break the build moving forward
	- [ ] Fix failing tests
		- [ ] Once everything is working, enable tests on our CI


We can list current failing tests here once we get rid of the most noisy ones.
Repository: flutter
Issue: Navigator docs are incomplete
Labels: framework,d: api docs,f: routes,P2,team-framework,triaged-framework

The `Navigator` docs say `A widget that manages a set of child widgets with a stack discipline.`, so this induces us to believe the `Navigator` will add some sort of hierarchy to the pushed Routes, but anyone that tried to get an `InheritedWidget` from inside a new Route will get an error (unless the `InheritedWidget` is on top of the `MaterialApp`).

As [this article](https://medium.com/@mehmetf_71205/inheriting-widgets-b7ac56dbbeb1) shows, one could expect our app to look like this:

```
> School App [App Context]
  > Student [Student Context]
    > Grades
    > Bio
  > Teacher [Teacher Context]
    > Courses
    > Bio
```

But Navigator will actually make it look like this:

```
> School App [App Context]
  > Student [Student Context]
  > Student Grades
  > Student Bio
  > Teacher [Teacher Context]
  > Teacher Courses
  > Teacher Bio
```

This behavior is misleading and induces errors (I spent 2 hours trying to understand why my `Provider` wasn't working once I navigated further), so it should be added to the docs.