sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: VSCode ignores JSDoc's @property when specify @typedef type in 1.43.2 and 1.44.0-insider
Labels: Needs Investigation

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 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/ -->

Seems like VSCode ignores `@property` when specify type inside `@typedef` in 1.43.2 and 1.44.0-insider. It cause type hint to show not so correct type information and also not detected inside autocomplete/intellisense.

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.43.2 and 1.44.0-insider
- OS Version: Ubuntu 18.04 x86_64

Steps to Reproduce:

1. Create JSDoc type definition file, for example `types.js`.
2. Import the type into `form.js`.
3. Ensure the type hint for the specified JSDoc is working properly (no `any`) and the type is detected available inside autocomplete/intellisense.

Temporary Solution:

- Remove type from `@typedef`, such us from `@typedef {Object<string, any>} Person` into `@typedef Person`.
- Or, remove `<string, any>` from Object, such us `@typedef {Object<string, any>} Person` into `@typedef {Object} Person`.

Reproduce Repo: https://github.com/jeffryang24/sandbox/tree/master/javascript/vscode-jsdoc-type-hint-issue

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/~~No~~
Repository: nvm
Issue: Ability to configure what rc/profile file nvm installs into
Labels: feature requests,installing nvm

<!-- Thank you for being interested in nvm! Please help us by filling out the following form if you‘re having trouble. If you have a feature request, or some other question, please feel free to clear out the form. Thanks! -->

#### Operating system and version:

Debian/unstable.

#### How did you install `nvm`?
<!-- (e.g. install script in readme, Homebrew) -->
Ran the installer.

#### What steps did you perform?

Installed with the standard install script. Tried to use ansible.

#### What happened?

#2174. Ansible started a non-interactive login shell & did not start nvm.

#### What did you expect to happen?

I would have liked some way to, on install, control how & where nvm installed itself into my shell and/or shells. A supplemental environment variable for the installer that let me specify that I prefer `.zshenv`/`.bash_profile` over the significantly less used/less useful `.zshrc`/`.bashrc` files would have given me an install preference to install nvm in a way that would be useful in more situations, available to more systems, such as Ansible.

This change by nvm would go a long way towards helping users such as those in #2174 make more active use of nvm wherever they need it.

#### Is there anything in any of your profile files that modifies the `PATH`?

Oh heck yes tons of things.
Repository: PowerToys
Issue: [Run][WindowWalker Plugin] Search parent window names
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

# 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).
-->
Trying it out for the first time, I wanted to switch to 'RoyalTS'. The issue is that depending on what tab I have selected, the window title is not actually 'RoyalTS'. In this case it was 'Single Box' so I wasn't able to find it. 


# Proposed technical implementation details (optional)
When searching, search parent window properties as well:

![image](https://user-images.githubusercontent.com/7737834/78072322-cacaf580-7353-11ea-83bc-a92ad6ed5614.png)

<!-- 
A clear and concise description of what you want to happen.
-->
Able to select windows by their parent window name or other metadata details.
Repository: kubernetes
Issue: Propagate context deadline in TokenReview REST handler
Labels: kind/bug,priority/important-soon,sig/auth,lifecycle/frozen

The TokenReview REST handler constructs a new request and passes it through the authentication handler. Any deadline associated with the original context is not passed down.

We should propagate the original context deadline/cancellation, either by wrapping the parent context, or by extracting/propagating the deadline, or by waiting on the original context's Done() channel and propagating a cancellation

/sig auth
/cc @enj @mikedanese
Repository: TypeScript
Issue: Function expressions in a property assignment of a prototype object should be methods, not nested classes
Labels: Bug

```js
/** @class */
module.exports.C = function() {
  this.x = 1
}
module.exports.C.prototype = {
  m1() {
    this.a = 1
  },
  m2: function() {
    this.b = 2
  }
}
var c = new module.exports.C()
c.a
c.b
```

**Expected behavior:**
`c.a` and `c.b` both work.

**Actual behavior:**
Only `c.a` works; `c.b` says that 'd' does not exist on type 'C'. There's also an error on `this.b = 2` when noImplicitThis: true.

bindThisPropertyAssignment needs to understand that function expressions might be part of a property assignment in an object literal. The code to handle this will probably look like this:

```ts
                    // For `{ x: function() }` should modify the object literal's members, not behave like a fresh class (as long as it doesn't have @class on it)
                    if (isPropertyAssignment(thisContainer.parent)) {
                        // wow I hope those parent pointers are set!
                        const containingClass = thisContainer.parent.parent;
                        const symbolTable = containingClass.symbol.members!;
                        if (hasDynamicName(node)) {
                            bindDynamicallyNamedThisPropertyAssignment(node, containingClass.symbol);
                        }
                        else {
                            declareSymbol(symbolTable, containingClass.symbol, node, SymbolFlags.Property | SymbolFlags.Assignment, SymbolFlags.None, /*isReplaceableByMethod*/ true);
                        }
                        break;
                    }
```

I expect this to break a lot of tests, but it didn't. However, I haven't tried it on the user tests yet.
Repository: flutter
Issue: [web] add chrome android support for web installers repo
Labels: a: tests,framework,platform-web,c: proposal,P2,team-web,triaged-web

[web_drivers](https://github.com/flutter/web_installers/tree/master/packages/web_drivers) libraries should be able to, more info on: https://chromedriver.chromium.org/getting-started/getting-started---android 

- [ ] create an emulator
- [ ] run the emulator
- [ ] run the bridge (adb)
- [ ] find the version of chrome on the emulator and install the driver.
Repository: flutter
Issue: Handle the UITouchPhaseRegion enum values.
Labels: platform-ios,engine,t: xcode,P2,team-ios,triaged-ios

The following enum values were added to `UITouchPhase` in iOS 13.4:
* `UITouchPhaseRegionEntered`
* `UITouchPhaseRegionExited`
* `UITouchPhaseRegionMoved`

These [don't seem to be documented](https://developer.apple.com/documentation/uikit/uitouchphase/uitouchphaseregionentered?language=objc) currently. This issue tracks the handling of these new enums. Xcode and/or the iOS SDK will have to be updated before these enums can be used in the engine as well.
Repository: flutter
Issue: Handle the UITouchTypeIndirectPointer enum value.
Labels: platform-ios,engine,t: xcode,P2,team-ios,triaged-ios

The following enum value was added to the `UITouchType` enum in iOS 13.4:
* `UITouchTypeIndirectPointer`

This [doesn't seem to be documented](https://developer.apple.com/documentation/uikit/uitouchtype/uitouchtypeindirectpointer?language=objc) currently. This issue tracks the handling of this new enum value. Xcode and/or the iOS SDK will have to be updated before this enum can be used in the engine as well.
Repository: vscode
Issue: Confusion about how EnvironmentVariableCollection handles multiple extensions changing the same variable 
Labels: bug,terminal-process

Refs #93601

**Repro**
1. In Extension 1, create a persisted `EnvironmentVariableCollection` that calls `.replace('TEST', 'replace')`

1. In extension 2, create a non persisted `EnvironmentVariableCollection` that calls `.append('TEST', 'append')`

1. Install both extensions
1. Activate extension 1. 
1. Then restart VS Code
1. Now activate extension 2
1. Create a new terminal and check the value of `TEST`

**Expected**
I expected `TEST` to be `replaceappend`

This is because I expect the initial value of `TEST` to be `replace` from the persisted collection in extension 1, then when extension 2 is activated it appends on its value.

**Actual**
The value of `TEST` is `replace`
Repository: pytorch
Issue: [jit] Structural typing shouldn't work
Labels: oncall: jit,triaged

This example runs but should throw an error since `SomethingElse` and `Point` should be different types

```python
import torch

@torch.jit.script
class Point(object):
	def __init__(self, x: int, y: int):
		self.x = x
		self.y = y

	def some_method(self):
		return self.x + self.y

class SomethingElse(object):
	def __init__(self):
		self.x = 1
		self.y = 1


@torch.jit.script
def fn(x: Point):
	print(x)
	return x

# Not passing in a Point
fn(SomethingElse())
```

cc @suo
Repository: pytorch
Issue: Python 3 build PyTorch got core dump
Labels: needs reproduction,module: crash,triaged

## ❓ Questions and Help

![pytorch_python3_core_dump_henry_wu](https://user-images.githubusercontent.com/47995124/78096245-f965c200-738d-11ea-8334-1f06978790d3.gif)

### Please note that this issue tracker is not a help form and this issue will be closed.

We have a set of [listed resources available on the website](https://pytorch.org/resources). Our primary means of support is our discussion forum:

- [Discussion Forum](https://discuss.pytorch.org/)
Repository: flutter
Issue: Patch ICU to not violate     -W-implicit-int-float-conversion
Labels: engine,P2,team-engine,triaged-engine

Specifically, https://fuchsia.googlesource.com/third_party/icu/+/refs/heads/master/source/i18n/plurrule.cpp#1664

/cc @chinmaygarde
Repository: flutter
Issue: Patch wuffs to not violate -Wnon-c-typedef-for-linkage"
Labels: engine,P2,team-engine,triaged-engine

Multiple places in //third_party/wuffs/release/c/wuffs-v0.2.c

/cc @chinmaygarde
Repository: pytorch
Issue: Dropout on sparse tensors
Labels: module: sparse,module: nn,triaged,enhancement

## ❓ Questions and Help
I‘d like to know if there is a dropout layer that i can use it on sparse tensor.
I will be appreciate it if you can show me the name? Just like the sparse_dropout in tensorflow!


We have a set of [listed resources available on the website](https://pytorch.org/resources). Our primary means of support is our discussion forum:

- [Discussion Forum](https://discuss.pytorch.org/)


cc @vincentqb
Repository: TypeScript
Issue: Suggestion: Reference expression type during cast
Labels: Suggestion,Awaiting More Feedback

## Search Terms

cast reference expression type

## Suggestion

I would like to be able to reference original type of the expression during cast.
For example:
```typescript
const o = {
    x: { a: 1 } as typeof & { b?: number }
}

// type of o.x is now { a: number; b?: number }
```

I am not attached to `typeof` syntax here, can be anything that makes sense.

## Use Cases

1. Defining optional properties without actually initializing them.
Current approach would require me to do something like:
```typescript
const o = {
    x: { a: 1 } as { a: number; b?: number }
}
```
which is unweildy and repeats all the properties.
It is possible to do through a function, but it has an overhead and is complicated due to partial generics:
```typescript
function extend<T>(T data) {
    return <TExtra>() => data as T & TExtra;
}

const o = {
    x: extend({ a: 1 })<{ b?: number }>()
}
```

2. Adding indexers to object literals:
```typescript
function map1(key: string) {
    return { a: 1, b: 2 }[key] || 3; // does not work due to https://github.com/microsoft/TypeScript/issues/14951
}

function map2(key: string) {
    return ({ a: 1, b: 2 } as { [key: string]: typeof[keyof typeof]|undefined })[key] || 3;
}
```

## Examples

See use cases.

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: PowerToys
Issue: Feature request: stretch and resize windows
Labels: Idea-Enhancement,Product-Window Manager

Three different feature:

1. Stretch windows: 
Allows the user to double click (example) a window edge, that will stretch (resize) the window up to the next window adjacent to the edge clicked.

![snap](https://user-images.githubusercontent.com/50175382/78119396-08da1f00-7411-11ea-92cd-0bc0717ac21c.gif)

2. ~Magnet windows:~ already covered by https://github.com/microsoft/PowerToys/issues/8
~Windows will "snap" (move/jump) into place when reaching a certain distance from another window or a screen edge.~

![magnet](https://user-images.githubusercontent.com/50175382/78119378-011a7a80-7411-11ea-9312-b9e16472aaf8.gif)

3. Window resize:
Allows the user to alt+click and drag(example) two overlapping window edges (of two different adjacent windows) and resize them both at the same time while keeping the edges overlapping.

![resize](https://user-images.githubusercontent.com/50175382/78119429-1394b400-7411-11ea-8b64-299c86d09440.gif)

Included gifs from several other window management programs as examples.

All of those will allow further customization after setting windows in designated zones.
Repository: godot
Issue: Some InputEvents aren't received by custom viewports
Labels: bug,documentation,topic:input

**Godot version:** 

Godot 3.2.1

**OS/device including version:**

Windows 10

**Issue description:**

Custom viewports doesn't receive some input events (like keypresses).

**Steps to reproduce:**

Add a Viewport, a TextureRect with a ViewportTexture attached to it, add a node inside of the viewport with a script using `_input` and a print statement.

**Minimal reproduction project:**

[viewport_test.zip](https://github.com/godotengine/godot/files/4414136/viewport_test.zip)

--------

Maybe there's something to do on my end to pass the input events, but i wasn't able to find anything useful in the documentation or on Google.
Repository: rust
Issue: Add option to set global `no_run` for doc test
Labels: T-rustdoc,C-feature-request,A-doctests

As this [issue](https://github.com/GuillaumeGomez/doc-comment/issues/20).

I want to guarantee all examples in external files can pass compiling, but I would not like to run them.

The main reason not to add no_run for each block is many markdown renders cannot correctly recognize a "rust,no_run" block.

So, could we add a option for `#[doc]` like `#[doc(include = "../README.md", no_run)]`?
Repository: rust
Issue: Associated types expansion issue
Labels: A-trait-system,A-associated-items,T-compiler,C-bug,A-lazy-normalization,T-types,fixed-by-next-solver

Adding an bound on an associated type (`where T::BarOutput: TraitFoo`) causes the compiler to erroneously complain about the original bound:

`the trait bound ``T: TraitBar<u64>`` is not satisfied`

The compiler is able to expand the associated type `BazOutput` enough to generate that error, but not enough to realize it would satisfy that bound.

```rust
pub trait TraitFoo {}

pub trait TraitBar<T> {
    type BarOutput;
}

pub trait TraitBaz {
    type BazOutput;
}
pub trait TraitFum<T> {}

pub struct StructZot;

impl TraitBaz for StructZot {
    type BazOutput = u64;
}

macro_rules! test {
    (1) => {
        impl<T: TraitBar<<Self as TraitBaz>::BazOutput>> TraitFum<T> for StructZot {}
    };
    (2) => {
        impl<T: TraitBar<<StructZot as TraitBaz>::BazOutput>> TraitFum<T> for StructZot {}
    };
    (3) => {
        impl<T: TraitBar<u64>> TraitFum<T> for StructZot {}
    };
    (4) => {
        impl<T: TraitBar<<Self as TraitBaz>::BazOutput>> TraitFum<T> for StructZot where
            T::BarOutput: TraitFoo
        {
        }
    };
    (5) => {
        impl<T: TraitBar<<StructZot as TraitBaz>::BazOutput>> TraitFum<T> for StructZot where
            T::BarOutput: TraitFoo
        {
        }
    };
    (6) => {
        impl<T: TraitBar<u64>> TraitFum<T> for StructZot where T::BarOutput: TraitFoo {}
    };
}

//test!{1} // Works
//test!{2} // Works
//test!{3} // Works
//test!{4} // Fails
test!{5} // Fails
//test!{6} // Works
```

([Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=ff6ba725e845b52ec5106df7a546698b))


I expected to see all 6 versions compile cleanly.


Instead, this happened:
```
error[E0277]: the trait bound `T: TraitBar<u64>` is not satisfied
  --> src/lib.rs:35:9
   |
35 | /         impl<T: TraitBar<<StructZot as TraitBaz>::BazOutput>> TraitFum<T> for StructZot where
36 | |             T::BarOutput: TraitFoo
37 | |         {
38 | |         }
   | |_________^ the trait `TraitBar<u64>` is not implemented for `T`
...
49 |   test!{5} // Fails
   |   -------- in this macro invocation
   |
   = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider further restricting type parameter `T`
   |
36 |             T::BarOutput: TraitFoo, T: TraitBar<u64>
   |                                   ^^^^^^^^^^^^^^^^^^
```
Repository: pytorch
Issue: Add KFAC optimizer
Labels: module: optimizer,triaged,needs research

## 🚀 Feature
Add the [Kronecker-factored Approximate Curvature (KFAC)](https://arxiv.org/abs/1503.05671) optimizer and/or [E-KFAC](https://arxiv.org/abs/1806.03884).

## Motivation
These are both approximate second order methods with promising results in terms of convergence rate. KFAC uses an block-diagonal approximation to the Fisher information matrix to approximate natural gradients. This allows for larger learning rates and thus improved convergence rate. Having a fully features built-in optimizer allows researchers and deep learning engineers to quickly iterate and test.

## Pitch
A KFAC implementation that works out of the box for all supported layers should be added to the built-in optimizers.

## Additional context
[An unmaintained Pytorch implementation](https://github.com/alecwangcq/KFAC-Pytorch)
[The standard TF implementation](https://github.com/tensorflow/kfac)
[KFAC for CNN](https://arxiv.org/abs/1602.01407)
[KFAC for RNN](https://openreview.net/forum?id=HyMTkQZAb)

cc @vincentqb
Repository: create-react-app
Issue: Expose env vars both with and without the REACT_APP_ prefix
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..."
-->
A third party library I'm using leverages a certain env variable, say `XYZ`. Currently there's no way for me to supply that.

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->
I realize it's a good safety measure for CRA to only pick up env vars with the prefix, and I don't object to that. However CRA could populate `process.env` with both keys i.e. both `REACT_APP_XYZ` and `XYZ`. That wouldn't violate the safety in any way, but still allows for code to expect any named env var.
Repository: pytorch
Issue: Hook on input tensor not called when using autograd.grad()
Labels: module: autograd,triaged,actionable

## 🐛 Bug

A backward hook registered on the input Tensor of the output expression is called when gradients are calculated by running `autograd.backward(output)` but not when running `autograd.grad(output, input)`.
In both cases the gradients are calculated and are the same except that `grad()` returns a tuple. 
The documentation of `register_hook()` says 

> The hook will be called every time a gradient with respect to the Tensor is computed.

And for `autograd.grad()`

> Computes and returns the sum of gradients of outputs w.r.t. the inputs.

So is it a bug or did I misunderstand the documentation or functionalities?

## To Reproduce

Steps to reproduce the behavior:
```python
import torch

# backward()
def hook_backward(grad):
    print("backward hook called using backward()")
input = torch.Tensor([2])
input.requires_grad = True
input.register_hook(hook_backward)
output = 5 * input

torch.autograd.backward(output)
print(f"backward() output: {input.grad}")

# grad()
def hook_grad(grad):
    print("backward hook called using grad()")
input = torch.Tensor([2])
input.requires_grad = True
input.register_hook(hook_grad)
output = 5 * input

grad = torch.autograd.grad(output, input)
print(f"grad() output: {grad}")
```

Output:
```
backward hook called using backward()
backward() output: tensor([5.])
grad() output: (tensor([5.]),)
```

## Expected behavior

Both backward hooks are called:
```
backward hook called using backward()
backward() output: tensor([5.])
backward hook called using grad()
grad() output: (tensor([5.]),)
```

## Environment

PyTorch version: 1.4.0
Is debug build: No
CUDA used to build PyTorch: None

OS: Microsoft Windows 10 Enterprise
GCC version: Could not collect
CMake version: Could not collect

Python version: 3.7
Is CUDA available: No
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA

Versions of relevant libraries:
[pip3] numpy==1.15.2
[conda] Could not collect

## Additional context

I wanted to post it in the forum but could not register or use github for login.


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7 @SsnL
Repository: PowerToys
Issue: [Run] Vim (j,k) feature or other keys combinations to navigate items
Labels: Idea-Enhancement,Help Wanted,Product-PowerToys Run,Area-User Interface,Area-Accessibility

# 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).
-->
Many Vim users would love to have `j` and `k` keys to navigate listed items after focusing it with Tab key.

![vim](https://user-images.githubusercontent.com/1015823/78130674-5fc70080-73df-11ea-857c-af5ea8bd5e4d.gif)
Repository: vscode
Issue: Investigate setting Electron's proxy from user setting
Labels: bug,proxy

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 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.43.2
- OS Version: Ubuntu 18.04

Steps to Reproduce:

1. Set proxy from OS, and in settings.json, but still can't browse or install extensions. Looking at log I get ERR_CONNECTION_TIMED_OUT