sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: OS specific properties in Tasks.json to overwrite build shell doen't work
Labels: feature-request,tasks

- VSCode Version: 1.39.2
- OS Version: Windows 10

Steps to Reproduce:

1. Set default shell to `bash` so your build tasks fails as VSCode recently started passing incorrect build path to `bash`
2. Set a build shell which is different than default as you want to build your TypeScript project. `powershell` works.
```JSONC
{
    // See https://go.microsoft.com/fwlink/?LinkId=733558 
    // for the documentation about the tasks.json format
    "version": "2.0.0",
    "windows": { // this is the only place where VSCode allows to add `windows`
        "options": {
            "shell": {
                "executable": "C:/Windows/System32/WindowsPowershell/v1.0/powershell.exe"
            }
        }
    },
    "tasks": [
```
3. Run build and see that it is using original shell, not one defined in `.vscode\tasks.json`

Does this issue occur when all extensions are disabled?: Yes

Options to add `windows:{options:shell:{executable:{"......"}}}` is available in VSCode for all Windows, OSX and Linux, however it doesn't affect build task on Windows:
![image](https://user-images.githubusercontent.com/12078150/67441481-fdb1d600-f5ca-11e9-996d-ca89b077b9af.png)
Repository: flutter
Issue: Migrate android_semantics_testing and android_views to the v2 embedding
Labels: platform-android,engine,a: existing-apps,P2,team-android,triaged-android

There are a few cases where access to `FlutterView` is currently needed.

1.  `flutterView.getAccessibilityNodeProvider()` in
https://github.com/flutter/flutter/blob/master/dev/integration_tests/android_semantics_testing/android/app/src/main/java/com/yourcompany/platforminteraction/MainActivity.java#L44

2. Full Flutter view. https://github.com/flutter/flutter/blob/master/dev/integration_tests/android_views/android/app/src/main/java/io/flutter/integration/androidviews/MainActivity.java#L39


These two tests are needed for https://github.com/flutter/flutter/issues/33884
Repository: rust
Issue: Document auto traits implemented by the return types of `async fn`
Labels: T-rustdoc,C-enhancement,A-async-await,AsyncAwait-Triaged

Currently, Rustdoc documents auto-trait impls for types, displaying them along with manually written impls. However, there is currently no way of telling what auto traits are implemented by the `impl Future` type returned by an `async fn`.

I'm not quite sure what the best way of displaying this is. We need to make it clear to users that the auto trait impls apply to opaque return type - not to the function itself, or to the underlying type returned by the future (e.g. the `u8` in `async fn foo() -> u8`).
Repository: flutter
Issue: Create a way to test Engine on its own
Labels: a: tests,engine,P2,team-engine,triaged-engine

We need a way to create tests against Engine directly.  As a shortterm workaround we allow people to call GetEngine() on a Shell which does have test harness code that creates it.  Ideally we could just create the Engine on its own to test.
Repository: youtube-dl
Issue: [theplatform.eu] video from DigitalTheatre.com
Labels: site-support-request

## Checklist

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.10.22**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

- Single video: http://player.theplatform.eu/p/lCpzgC/dt-vp/embed/select/media/bcl_3606

## Description

```
C:\Users\Ardis>youtube-dl -v http://player.theplatform.eu/p/lCpzgC/dt-p/embed/select/media/bcl_3606
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['-v', 'http://player.theplatform.eu/p/lCpzgC/dt-vp/embed/select/media/bcl_3606']
[debug] Encodings: locale cp1252, fs mbcs, out cp437, pref cp1252
[debug] youtube-dl version 2019.10.22
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.18362
[debug] exe versions: none
[debug] Proxy map: {}
[generic] bcl_3606: Requesting header
WARNING: Could not send HEAD request to http://player.theplatform.eu/p/lCpzgC/dt-vp/embed/select/media/bcl_3606: HTTP Error 405: Method Not Allowed
[generic] bcl_3606: Downloading webpage
WARNING: Falling back on generic information extractor.
[generic] bcl_3606: Extracting information
[generic] bcl_3606?autoPlay=false: Requesting header
WARNING: Could not send HEAD request to https://player.theplatform.eu/p/lCpzgC/dt-vp/embed/select/media/bcl_3606?autoPlay=false: HTTP Error 405: Method Not Allowed
[generic] bcl_3606?autoPlay=false: Downloading webpage
WARNING: Falling back on generic information extractor.
[generic] bcl_3606?autoPlay=false: Extracting information
ERROR: Unsupported URL: https://player.theplatform.eu/p/lCpzgC/dt-vp/embed/select/media/bcl_3606?autoPlay=false
Traceback (most recent call last):
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpifszpy0p\build\youtube_dl\YoutubeDL.py", line 796, in extract_info
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpifszpy0p\build\youtube_dl\extractor\common.py", line 530, in extract
  File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmpifszpy0p\build\youtube_dl\extractor\generic.py", line 3353, in _real_extract
youtube_dl.utils.UnsupportedError: Unsupported URL: `https://player.theplatform.eu/p/lCpzgC/dt-vp/embed/select/media/bcl_3606?autoPlay=false
```
Repository: godot
Issue: Disable properties that should not be used (scale/rotation) (or warn the user)
Labels: enhancement,discussion,topic:editor

**Godot version:** 3.2 alpha 2
**OS/device including version:** macOS Mojave
**Issue description:** 
I faced the same issue as #5929, reduz said it's not an issue but a limitation of the physic engine, `scale` must not be used with this node (or a rigid in non static mode) and the issue was closed.

This issue is similar but with the rotation property  #2129

However those fields are accessible in the UI/Code and nothing warn the user of that situation.

I suggest if possible to disable those properties if they can't be used  or at least display a warning/error message to avoid users to face the problem.
Repository: go
Issue: cmd/cgo: calling C code without cgo on aix/ppc64
Labels: NeedsInvestigation,arch-ppc64x,compiler/runtime

In CL 198798, @jpap allows Go asm to call/jump directly to a C function defined in a .syso files. 
The jump is performed like this `JMP Cfunc(SB)`. 
However, on AIX, this JMP doesn't work. A C function has two symbols:
 - `Cfunc`, a data symbol with a pointer to `.Cfunc` and a pointer to the TOC symbol (something similar to GOT stuff with ELF format)
 - `.Cfunc`, a text symbol which the label in `.text` section. 

Therefore, `JMP Cfunc(SB)` is jumping to a data symbol which obviously doesn't work. 
The normal 'AIX' code should be `JMP .Cfunc(SB)`. 
However, there are several problems with that: 
 - GO asm doesn't seem able to parse this "." function. 
 - Special AIX code will be needed for every programs using this stuff. 

What's the policy of Go in this case ? Do we want to match C code (ie using `JMP .Cfunc(SB)`) or do we want to be closer to Go code (ie using  `JMP Cfunc(SB)`) and afterwards changing ASM generated in `cmd/internal`. 

Note that both solution might be added. So people might want to write special ASM code for AIX with "dot" function, etc. While others just want their code to work in all platforms.
Repository: create-react-app
Issue: Include step of adding "ie 11" in package.json developement key when using react-app-polyfill
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

When following instructions on this page: https://github.com/facebook/create-react-app/blob/master/packages/react-app-polyfill/README.md, in my case to make ie11 work in development, I also had to add "ie 11" to my package.json > browserlist> development. This should be documented.

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

In package.json > browserslist > development, add "ie 11" or the appropriate IE version that corresponds to the polyfill in use. You might also, need to delete your node_modules folder and re-install the modules.

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

None.

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

N/A
Repository: svelte
Issue: Prevent multiple style recalculations and improve performance by grouping DOM reads and writes
Labels: perf

**Is your feature request related to a problem? Please describe.**
When requesting `offsetLeft` (or other DOM reads) in the `beforeUpdate` callback the browser has to recalculate styles when the styles are changed in a further update. See below how this looks in dev tools with multiple components (the second one is without the DOM reads, you can see the recalculation is done after every style has been updated).

I've created a REPL: https://svelte.dev/repl/1977c00357cc496eae5ec1f2a9d23675?version=3.12.1

Multiple recalculations because of DOM reads

![Screenshot 2019-10-22 at 11 29 48](https://user-images.githubusercontent.com/1132575/67273923-b7bc1b80-f4bf-11e9-8432-071df389ab29.png)

Single recalculation

![Screenshot 2019-10-22 at 11 30 38](https://user-images.githubusercontent.com/1132575/67273947-c571a100-f4bf-11e9-890c-0076633b341a.png)

This slows down the frame render.


**Describe the solution you'd like**
If we can schedule all reads before the update happens DOM reads are free (the browser has prepared the frame) and don't cause additional style recalculations. This might require setting up a global draw loop so web components created with Svelte all use the same read/write order.


**Describe alternatives you've considered**
I've moved the DOM read to `afterUpdate` while that does group part of the writes we only get the info after the update while we need it before.

![Screenshot 2019-10-22 at 11 39 18](https://user-images.githubusercontent.com/1132575/67274401-a58ead00-f4c0-11e9-8205-5e43bb50200e.png)


**How important is this feature to you?**
Very. It's super useful to be able to access layout information at the start of the frame (it's free at that moment) and this can be used to for example calculate the width of a component and then layout its children accordingly (simulating component queries) without affecting render performance. I use this extensively in [FilePond](https://pqina.nl/filepond/).
Repository: electron
Issue: webContents.reload should accept same options as webContents.loadURL
Labels: enhancement :sparkles:,6-1-x,7-1-x

### Problem Description
[webContents.loadURL](https://github.com/electron/electron/blob/master/docs/api/web-contents.md#contentsloadurlurl-options) lets you add additional options such as `userAgent` and `extraHeaders`, but [webContents.reload()](https://github.com/electron/electron/blob/master/docs/api/web-contents.md#contentsreload) does not use these options.

Any values set with `loadURL` will not be kept with a reload. For `userAgent` we have `webContents.setUserAgent`, but the other options (`extraHeaders`, `httpReferrer` etc) have no such persistent call.

### Proposed Solution

Ideally `webContents.reload()` should keep and re-use the extra options that `loadURL` was last called with.

### Alternatives Considered

Alternatively, `webContents.reload()` could get the same set of options, and it's up to the user to replicate them.
Repository: flutter
Issue: Listing non platform compatible plugins
Labels: c: new feature,tool,P3,team-tool,triaged-tool

## Use case

When I start adding a new platform like web or desktop to my application I want to know the non-compitable plugins with the new platform

## Proposal
Simply by Using a flutter command to list The Plugins which is not compatible with the targeted platform

Sample
`Flutter plugin -check web
`
Result:
```
Dio 2.0.0 Android - iOS 
Suggestion Dio 3.0.0 Android-iOS-Web

```

This command will help too much when a developer investigates to target a new platform too much otherwise he have to search plugin by plugin and debugging.
Repository: rust
Issue: Casting away lifetimes using closures
Labels: A-lifetimes,A-closures,T-lang,C-bug

The following code compiles on stable and nightly. I'm not sure it should as it's effectively casting a `Struct::<'a>` to a `Struct::<'static>` in safe code.

```rust
use std::{any::Any, marker::PhantomData};

fn main() {
    bad();
}

fn bad<'a>() -> Struct<'static> {
    make_static(|| Struct::<'a>(PhantomData))
}

struct Struct<'a>(PhantomData<&'a ()>);

fn make_static<A, B>(a: A) -> B
where
    A: FnOnce0 + 'static,
    B: 'static,
{
    let boxed: Box<dyn Any + 'static> = Box::new(a.call());
    *Box::<dyn Any + 'static>::downcast(boxed).unwrap()
}

trait FnOnce0 {
    type Output;
    fn call(self) -> Self::Output;
}

impl<F, O> FnOnce0 for F
where
    F: FnOnce() -> O,
{
    type Output = F::Output;
    fn call(self) -> Self::Output {
        self()
    }
}

```

([Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=2bfb6a8f538e4a4c79ffc070cb045f98))

It seems lifetime and type parameters that are used in the closure don't affect the lifetime of the closure itself. I stumbled upon this after noticing that `|| T::default()` is `'static` whereas `T::default()` is [not](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=9d8c8da5dcd7f26696149a16a7e8eae1).
Repository: godot
Issue: Hovering over a property in the Inspector for over 1 second causes its tooltip to disappear, then continue to blink on and off [Stardock Fences, Kakaotalk]
Labels: bug,platform:windows,topic:porting,confirmed,topic:thirdparty,topic:gui

___

***Bugsquad note:** This issue has been confirmed several times already. No need to confirm it further.*

___

**Godot version:**
3.1.1 Stable

**OS/device including version:**
Windows 10.0.18362

**Issue description:**
When hovering over a property in the inspector panel, a description pops up for a second, then blinks away, then comes back.  This can't be how it was designed.

**Steps to reproduce:**
Open a blank project.  Hover over any property in the inspector window.  Observe the property description appear for a second, then disappear for a fraction of a second, then reappear.

**Minimal reproduction project:**
Any blank Godot default project.
Repository: fastapi
Issue: Execute dependencies in parallel instead of sequentially awaiting them
Labels: feature,reviewed

**Is your feature request related to a problem? Please describe.**
FastAPI's Dependency injection system, while extremely useful, tends to run into a problem when several long-running dependencies are needed for a single route, such as with the example below.

```py
from fastapi import Depends, FastAPI
from asyncio import sleep as async_sleep

app = FastAPI()

async def get_big_data():
    await async_sleep(5)
    return "𝐃𝐀𝐓𝐀"

async def compute_pi():
    await async_sleep(5)
    return "About 3, I think?"

async def do_nothing_for_a_bit():
    await async_sleep(5)
    return "Gotta let the CPU spin down for a bit, otherwise it could explode."

@app.get("/do_long_thing")
async def do_long_thing(
    big_dep1: str = Depends(get_big_data),
    big_dep2: str = Depends(compute_pi),
    big_dep3: str = Depends(do_nothing_for_a_bit)
):
    return {
        'big': big_dep1,
        'pi': big_dep2,
        'sleep': big_dep3,
    }
```

Running that application and thentrying to access `/do_long_thing` takes 15 seconds to load, even though none of those dependencies are reliant on each other and could very well be ran in parallel.

**Describe the solution you'd like**
Don't await coroutines and threadpools here. Collect them into a list instead and gather them.

https://github.com/tiangolo/fastapi/blob/3f9f4a0f8f7f5db50fbdc3157fe692cf4e68e13f/fastapi/dependencies/utils.py#L442-L456

**Describe alternatives you've considered**
Asking that the user take care of running and gathering those dependencies themselves is pretty much the only solution to this problem available right now (that I can see, anyway, there might be another one), which undermines the usefulness of the dependency injection system.
Repository: go
Issue: x/build/cmd/gopherbot: fix Gerrit reviewer email addresses
Labels: help wanted,Builders,NeedsInvestigation,FeatureRequest

I have three main email addresses (gmail.com, golang.org, google.com), with three corresponding Chrome identities/Google accounts.

So do many others on the Go team. (Or at least two)

And because I've clicked links to Gerrit reviews while signed into each of the three, Gerrit has helpfully signed me in & made an account for me.

Which then means my name shows up in the autocomplete list for "bradfitz" in three ways.

It's distracting when I get reviews to the wrong email account.

This just bit @ianlancetaylor too.

I realized we could just have a mapping table and make gopherbot fix the reviewers if it sees a wrong one added by mistake.

/cc @dmitshur @andybons @bcmills
Repository: TypeScript
Issue: Provide auto-completion on function parameters (TypeScript)
Labels: Bug,Domain: Completion Lists

*TypeScript issue template from @mjbvz*

**TypeScript Version**: 3.7.0-dev.20191021

**search terms**
- parameter hints
- signature help

*original report below*

--- 

<!-- 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.0
- OS Version: Ubuntu 18.04

Steps to Reproduce:

1. Parameter hints do **not work** if `fn` **is optional**

```ts
type fn = (a: string, b: object) => boolean

type obj = {
    fn?: fn
}

const test: obj = {
    fn: (/** parameter hints not working */) => true,
}
```

2. Parameter hints do **work** if `fn` is **not optional**

```ts
type obj = {
    fn: fn
}

const test: obj = {
    fn: (/** parameter hints working */) => true,
}
```

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: **Yes**/No
Repository: pytorch
Issue: Python/C++ API Parity: torch.optim optimizers
Labels: module: cpp,triaged

Currently, `torch.optim` optimizers in PyTorch C++ API behave slightly differently from the Python API. In order to achieve parity, we should check the following aspects of an optimizer:

1. Make sure the C++ optimizer takes the same set of constructor arguments as the Python optimizer.
2. Make sure the C++ optimizer's constructor has the exact same logic as the Python optimizer's `__init__()` function. Particularly, we need to support `param_groups` in C++ optimizers.
2. Make sure the C++ optimizer's `step()` function has the exact same logic as the Python optimizer's `step()` function.
3. Add `state` to all optimizers, which is equivalent to the `state` dict in Python optimizers. In the `serialize` function of each C++ optimizer, make sure to serialize the `state` field into a list of `at::IValue`s, and have tests to make sure we can deserialize the `state` field successfully.
    - You might ask "what should we do with the existing serialization logic in the `serialize` function, and would the change break backward compatibility of the user's existing serialized optimizers?" The answer is that we should put a "version number" in the serialized optimizer, and use that to identify the version - if we find no version number, we know that it's the old version, if we find version number "1.5", we know that it's the second version (aka. the version after our changes). We need to have tests to cover deserialization of the old version as well.

For more detailed discussions on the class structure design, see https://github.com/pytorch/pytorch/pull/29581.

## Optimizers
- [x] Adagrad (https://github.com/pytorch/pytorch/pull/29335)
- [x] Adam (https://github.com/pytorch/pytorch/pull/33730)
- [x] LBFGS (https://github.com/pytorch/pytorch/pull/34564)
- [x] RMSprop (https://github.com/pytorch/pytorch/pull/33450)
- [x] SGD (https://github.com/pytorch/pytorch/pull/32592)
- [ ] Adadelta
- [x] AdamW
- [ ] SparseAdam
- [ ] Adamax
- [ ] ASGD
- [ ] Rprop

cc @yf225
Repository: godot
Issue: TextEdit always clips content (including the focus outline, causing it to be not fully visible)
Labels: bug,discussion,confirmed,topic:gui

**Godot version:**
3564547208030264a28cc55232992aab3cbdad94

**OS/device including version:**
ArcoLinux

**Issue description:**
TextEdit forcibly clips all content, regardless of whether the `Clip Content` box is checked.

![image](https://user-images.githubusercontent.com/28724859/67325878-6faaf200-f4db-11e9-8bde-2ea76b8f37fa.png)
![image](https://user-images.githubusercontent.com/28724859/67325902-78032d00-f4db-11e9-8e1a-2bc4a4a0d35e.png)
Repository: pytorch
Issue: gradient of Dirichlet.log_prob gives nan
Labels: module: distributions,triaged

## 🐛 Bug

Hi there, I am trying to apply backward/grad on the dirichlet.log-prob(x_constrained). The input(i.e x_constrained) is the output of a call to stick-breaking transform. However, grad output includes nan and -inf for the following x_constrained (note that x_constrained may not be precise since it comes from execution of my code) 
x_constrained= tensor([1.7647e-01, 7.2429e-01, 1.1665e-39, 9.9239e-02]

It seems an overflow for log_prob happens since one of the elements of x_constrained is really small. 
## To Reproduce

Here is the code snippet:

```
   print(f"\n x_unconstrained = {x_unconstrained}")
    transform = dist.StickBreakingTransform()
    x_unconstrained.to(dtype=torch.float64)
    x_unconstrained.requires_grad_(True)

    x_constrained = transform._call(x_unconstrained)
    x_constrained.to(dtype=torch.float64)

    print(f"\n x_constrained  = {x_constrained}")
        
    dirirchlet = dist.Dirichlet(tensor([2.5, 10.0, 2.0, 3.0]))
    score1 = dirirchlet.log_prob(x_constrained)
    print(f"\n dir.log_prob {score1}")

    score1_gradient = grad(score1.clone(), x_unconstrained, create_graph=True)[0]
    print("\nscore wrt x", score1_gradient)
    
    
```
Here is its output:
<img width="648" alt="Screen Shot 2019-10-23 at 10 04 20 AM" src="https://user-images.githubusercontent.com/56326968/67416887-85242880-f57c-11e9-8db8-abd614652f61.png">




## Expected behavior

I expect to get the actual derivative for dirichlet.log_prob.




cc @vincentqb @fritzo @neerajprad @alicanb @vishwakftw
Repository: flutter
Issue: flutter create --template plugin should make a federated plugin by default
Labels: tool,P2,a: plugins,team-tool,triaged-tool

Once the federated plugin layout has stabilized (see https://github.com/flutter/plugins/pull/2217) I think we should make it the default in the plugin template.

Making federated the default is better for the ecosystem long term since it improves portability, even though it increases complexity for first-time plugin authors who have to publish multiple packages.

We should ensure that the template includes warnings about making breaking changes to the platform package.  https://flutter.dev/go/platform-interface-breaking-changes