sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: c10 List API hard to use
Labels: module: internals,triaged

There isn't any way to access the values of Generic List except as a reference. When writing ops this makes you do:
```
auto val = pop(stack);
auto list = val.toGenericListRef();
```

instead of:
```
auto list = pop(stack).toGenericList();
```
If you try to do the latter: 
```
auto input_list = pop(stack).toGenericList();
for (const auto& input : input_list) {
    auto tup = input.toTuple()
}
```
then you get the following error:
> ‘const class c10::impl::ListElementReference<c10::IValue, __gnu_cxx::__normal_iterator<c10::IValue*, std::vector<c10::IValue, std::allocator<c10::IValue> > >, c10::IValue>’ has no member named ‘toTuple’

This makes it difficult to use GenericList as a value instead of a reference.
Repository: godot
Issue: Translation keys on control nodes are very inconsistent
Labels: bug,confirmed,topic:gui

**Godot version:**
3.1.1 stable

**OS/device including version:**
Linux Mint 19.2

**Issue description:**
Putting translation keys on Controls is very inconsistent. Normally, nodes are supposed to shrink to fit the text, but all sorts of things break that and cause it to be large enough to fit the full translation key.

For example, the key `ui_options_quit_without_saving` has the text `Quit Without Saving`, which is obviously shorter. Immediately after creation it shrinks properly, but doing various different things seem to make it keep the full size of the key.

**Steps to reproduce:**
Open the reproduction project. Run the game; the top-left button will fit the text, but the bottom-right won't. Moving the top-left button at all will make it stop working properly too.

**Minimal reproduction project:**
[GodotIssue.zip](https://github.com/godotengine/godot/files/3607742/GodotIssue.zip)
Repository: TypeScript
Issue: navto does not include jsdoc @typedef symbols
Labels: Suggestion,Experience Enhancement

<!-- 🚨 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 `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.7.0-dev.20190911

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
- navTo
- workspace symbol search

**Code**
For the js file:

```ts
/**
 * Describes a duck
 * @typedef {{rubber: boolean, color: string}} Duck
 */
```

1. Do a workspace symbol search

**Expected behavior:**
`Duck` is returned in `navto ` response

**Actual behavior:**
No result for `Duck` included

```
[Trace  - 5:52:43 PM] <semantic> Sending request: navto (103). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/san/main.js",
    "searchValue": "Duck"
}
[Trace  - 5:52:43 PM] <semantic> Response received: navto (103). Request took 49 ms. Success: true 
Result: []
```
Repository: terminal
Issue: Audit uses of the screen buffer/alternate buffer, or come up with a design that makes this not an issue
Labels: Product-Conhost,Area-VT,Issue-Task

Is this indicative of a larger problem? Should we file an outstanding work item to audit all sites of manipulating the active buffer and/or somehow change the design such that the methods cannot accidentally be called without resolving which one is the active one first?

For the latter, my proposal would be to hide all the verbage methods off the base class and implement some sort of interface that holds them that is only returned when/if someone has correctly queried for the active one first. I'd accept competing proposals, though.

_Originally posted by @miniksa in https://github.com/microsoft/terminal/pull/2729#issuecomment-530923095_
Repository: flutter
Issue: Benchmark complex_layout_scroll_perf__memory needs better metrics to avoid reporting phantom regressions
Labels: team,engine,c: performance,perf: memory,P3,team-engine,triaged-engine

The main issue (after some discussion) is that this benchmark is not reporting metrics that exactly match its concern and so situations such as those described below can cause it to indicate a regression when a change simply affects its underlying assumptions instead. We need to develop better metrics for it to measure so that it only flags when we have an actual memory regression.

Until then the benchmark acts mostly as a "canary" that will often see a change that might negatively affect app performance, but sometimes in cases that don't really impact real-world performance. Changes in the benchmark should be noted, but more investigation will determine if the change in reported metrics really represents a regression.

**Originally reported issue:**

I'm investigating the historic slowdowns in the complex_layout_scroll_perf__memory benchmark. It looks like we were at around 5000 in late July and since then we've been stuck around 9000+.

It appears that commit 9b150f134b9b6ba103ec305f489645b5fee905d2 is responsible for that change. Here are 3 runs of the benchmark on a Moto G4 first running on commit 0d0af31598f5ee0552529bfd3fdc35be1d8fe176 (which is just before the indicated commit) and then on commit 9b150f134b9b6ba103ec305f489645b5fee905d2

```
Stats for hash 0d0af3

On G4:

  "data": {
    "start-min": 34210,
    "start-max": 40838,
    "start-median": 39220,
    "end-min": 44052,
    "end-max": 46190,
    "end-median": 45034,
    "diff-min": 4464,
    "diff-max": 11980,
    "diff-median": 5033
  },
  "data": {
    "start-min": 35164,
    "start-max": 41233,
    "start-median": 40473,
    "end-min": 44973,
    "end-max": 45653,
    "end-median": 45321,
    "diff-min": 4125,
    "diff-max": 10322,
    "diff-median": 4487
  },
  "data": {
    "start-min": 32907,
    "start-max": 40356,
    "start-median": 39693,
    "end-min": 44393,
    "end-max": 48066,
    "end-median": 44879,
    "diff-min": 4099,
    "diff-max": 15159,
    "diff-median": 4907
  },

Stats for hash 9b150f:

On G4:

  "data": {
    "start-min": 31106,
    "start-max": 33471,
    "start-median": 31184,
    "end-min": 40494,
    "end-max": 45019,
    "end-median": 40980,
    "diff-min": 7793,
    "diff-max": 11548,
    "diff-median": 9319
  },
  "data": {
    "start-min": 31144,
    "start-max": 32886,
    "start-median": 31240,
    "end-min": 40506,
    "end-max": 41104,
    "end-median": 40906,
    "diff-min": 7932,
    "diff-max": 9798,
    "diff-median": 9690
  },
  "data": {
    "start-min": 30958,
    "start-max": 32838,
    "start-median": 31365,
    "end-min": 40332,
    "end-max": 41224,
    "end-median": 40892,
    "diff-min": 8054,
    "diff-max": 9874,
    "diff-median": 9501
  },
```
Repository: TypeScript
Issue: Type variables in TypedPropertyDescriptor cause compilation errors when using decorator
Labels: Needs Investigation

**TypeScript Version:**  3.6.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** TypedPropertyDescriptor, MethodDecorator, TS2345, Types of property 'value' are incompatible.

**Code**

```ts
type MyDynamicDescriptor = <T>(input: T) => T
type MyStaticDescriptor = (input: number) => number

function dynamicDecorator(foo: string) {
  return (_: any, __: any, descriptor: TypedPropertyDescriptor<MyDynamicDescriptor>) => {
    console.log('foo:', foo)
    console.log('descriptor.value:', descriptor.value)
  }
}

function staticDecorator(foo: string) {
  return (_: any, __: any, descriptor: TypedPropertyDescriptor<MyStaticDescriptor>) => {
    console.log('foo:', foo)
    console.log('descriptor.value:', descriptor.value)
  }
}

class myClass {
  @dynamicDecorator('bar')
  myMethod(input: number): number {
    return input + 42
  }

  @staticDecorator('bar')
  myOtherMethod(input: number): number {
    return input + 42
  }
}
```

**Expected behavior:**
No compilation errors for both `dynamicDecorator` and `staticDecorator`.

**Actual behavior:**
Compilation errors for `dynamicDecorator`:
```
error TS2345: Argument of type 'TypedPropertyDescriptor<(input: number) => Promise<number>>' is not assignable to parameter of type 'TypedPropertyDescriptor<MyDynamicDescriptor>'.
  Types of property 'value' are incompatible.
    Type '((input: number) => Promise<number>) | undefined' is not assignable to type 'MyDynamicDescriptor | undefined'.
      Type '(input: number) => Promise<number>' is not assignable to type 'MyDynamicDescriptor'.
```

[**Playground Link**](http://www.typescriptlang.org/play/?experimentalDecorators=true#code/C4TwDgpgBAsiAiIB2BDAtgSwMbwgZywCcMxgB7QqAXigB4AVAPgAoMkwBXYALinoEpqjPgChQkWCADKwFMGy4CxUhWpRW7LryQc0AIwiFBVYTv2GRIgGYckWeWSRQAJsnQKIWCnIrMrZMl48YGIkAHNBAG8RKChCCGAOQidmAH1eFCQQABooVPSoTJyXfCISckJeenAIZwAFQjJIQlBFMpVCWjhEVEwcUuUKxmNhaNjYryQ8MgAbCAA6GbIw5gByf0DV3I3+GPHJ6bnF5bXnAfKKeYA3FBmOCG4tkqULwmvb+93YgF8RX+tbPYMI4oME5B4vIQfIQ-AEgiE2BEoGM4gkkikCkVcvkMllcmcXh0qjV6o1mq1zh0utJZPJ+oShiNkXsJo5Dgslit1nCnjsWVADrMOSdVgT2hV3ncHk8xYNLjcpV8oL9-lgZig8HgoGgQABhdWa5mxAACrl6EO8FTWehQhFWSp1MASAAsyM4NJweFAzAYjNpdL6jeN4olklA2J6oABqKAAFgATHt-iawXTcJDodbbfa9jqAPLAZ2GJ2Ft0erTegOGfj+8yUFGxEPo8OaYDRuOJn5-ERAA)
Repository: flutter
Issue: Image loading can make widget tests flakey
Labels: a: tests,framework,a: images,c: proposal,P3,team-framework,triaged-framework

We had a widget test that succeeded when run in isolation, but failed when run with others in a group.

This was because we had an image without an explicit size. If the image had been previously loaded in another test and so was cached in memory, the image widget received the correct sizing.

However if the test was run in isolation, the image wasn’t loaded in time, making the layout different.

This was very difficult to debug.


Possible fixes:

1. I would expect that `pumpAndSettle` would wait for images to load and the layout to be complete, this doesn’t seem to be the case.
2. Flutter could clear the in-memory cache at the start of every widget test: `imageCache.clear()`



<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
[✓] Flutter (Channel stable, v1.9.1+hotfix.2, on Mac OS X 10.14.6 18G95, locale en-GB)
    • Flutter version 1.9.1+hotfix.2 at /Users/tom/dev/flutter
    • Framework revision 2d2a1ffec9 (6 days ago), 2019-09-06 18:39:49 -0700
    • Engine revision b863200c37
    • Dart version 2.5.0

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at /Users/tom/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = /Users/tom/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 10.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.3, Build version 10G8
    • CocoaPods version 1.7.1

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 39.0.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.38.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.4.1
```
Repository: three.js
Issue: Editor : Enhancments and Features addition
Labels: Editor

##### Editor Enhancments

Creating this thread to track implementations for the editor enhancments and features like Material Browser.

- [x] TabbedPanel UI Element #17465.
- [x] Listbox UI Element. #17490
- [x] MaterialBrowser Panel in project panel with menu to Create, And Apply Material and store it in the editor. #17556 
- [ ] Open the Selected Material ( in MaterialBrowser ) in Properties editor.
- [ ] Replace the current History panel with the Listbox Element.
- [ ] Refactor Outliner to create a generic simple treeview.
- [ ] Replace the current Outliner for Scene Panel with the new one.
- [ ] Cleanup.

Now that we are implementing this i propose to refactor the Add* commands to not apply a default material while creating objects and adding to the scene.
Repository: flutter
Issue: Enable touch filtering and tapjacking protection
Labels: c: new feature,framework,P3,team-framework,triaged-framework



## Use case
Currently, there is no way to enable touch filtering in buttons like the android feature **setFilterTouchesWhenObscured(true).** This is crucial to protect apps from tapjacking.
## Proposal
A property on ButtonWidgets that will enable touch filtering : 

`
FlatButton(
            child: Text(Strings.ok),
            enableFilterTouchesWhenObscured(true)
            onPressed: () {
              Navigator.of(context).pop();
            },
          )
`
Repository: pytorch
Issue: Memory leak in multithreading environment when loading checkpoint
Labels: high priority,needs reproduction,module: multiprocessing,module: memory usage,triaged,module: multithreading

## 🐛 Bug

I have a problem when loading saved checkpoint for pytorch model in seperate thread. CPU memory keeps increasing and is never released.

Multi-threading version of script increases RAM usage with each iteration and ends with 978 RESV memory (htop output).
Single-threading version holds with 374 RESV memory (htop output).
When I randomly initialize model (without state_dict loading) both versions use the same (smaller) amount of memory.

## To Reproduce

```
import torch
import time
import threading
import torchvision

def create_tensor(index):
    print("Create model {}".format(index))
    resnet50 = torchvision.models.resnet50(pretrained=True)
    del resnet50

def create_tensor_thread(index):
    x = threading.Thread(target=create_tensor, args=(index,))
    x.start()
    x.join()

def run(use_threading=False):
    for index in range(5):
        if use_threading:
            #memory leak observed 
            create_tensor_thread(index) 
        else:
            #no memory leak observed
            create_tensor(index)
        time.sleep(5)

run(True)
```

## Expected behavior

I expect the RAM to be cleared as no reference is being held to created models.

## Additional info

I have traced the issue to  https://github.com/pytorch/pytorch/blob/33221b19acc3dcacb11c38fdbff65d9a6ce90866/torch/nn/modules/module.py#L775
Commenting out this line makes the multi-threading version behave as single-threading one.

## Environment

 - PyTorch Version: 1.2.0
 - OS: Ubuntu 18.04
 - How you installed PyTorch: pip
 - Python version: 3.5.7


cc @ezyang @gchanan @zou3519 @jerryzh168
Repository: vue
Issue: Click Event Triggers on Complex Buttons are ignored in Pale Moon browser
Labels: browser quirks,has PR

### Version
2.6.10

### Reproduction link
[https://jsfiddle.net/ye6vs8h3/](https://jsfiddle.net/ye6vs8h3/)

### Steps to reproduce
Install Pale Moon browser http://www.palemoon.org/
Open the jsfiddle (https://jsfiddle.net/ye6vs8h3/).

When clicking directly on the Vue logo image,  a click is not registered. 
When clicking just next to it, still on the grey background, a click *is* registered correctly.

### What is expected?
When clicking on a nested component, the click should bubble up to the parent element that has a `@click` handler.

### What is actually happening?
The click is not bubbled up, so takes no effect.

---
This issue is similar to several other bugfixes, for Adobe CEP and Mobile Safari:

https://github.com/vuejs/vue/issues/9462
https://github.com/vuejs/vue/issues/10366

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: flutter
Issue: Addd onTabChanging to TabConctroller with interception
Labels: c: new feature,framework,f: material design,f: scrolling,c: proposal,P3,team-design,triaged-design

## Use case

Sometimes you want to prevent that a tab is changed e.g. when not all fields of a Form were filled out or an action hasn't finished.
Currently you only get informed after a change.

## Proposal


I propose to add a new Handler  ` OnTabChangingHandler TabController.onTabChanging`

```Dart
    typedev OnTabChangingHandler = bool Function(int index)
```

if the handler returns `true` the tab is changed if `false` the TabBarView doesn't change.


As a side note, why do we need a Listener to get informed that the tab changed. Couldn't this be made easier by providing an event in the TabBarController?
Repository: neovim
Issue: macOS binary: sign, notarize
Labels: platform:macos,security,distribution

Currently running macOS Catalina and NeoVim fails to start with error:

"“nvim” can’t be opened because its integrity cannot be verified."

That's running: `./nvim-osx64/bin/nvim` after having run install instructions:

> Download nvim-macos.tar.gz
> Extract: tar xzvf nvim-macos.tar.gz
> Run ./nvim-osx64/bin/nvim

Was working in macOS Mojave. Have downloaded and followed the install again but problem persists.

Anyone have any idea why this might be?
Repository: rust
Issue: Higher rank trait bounds cannot genericise across functions with a bound sharing a lifetime with the prototype
Labels: A-lifetimes,A-trait-system,T-compiler,C-bug,A-higher-ranked

The current implementation of higher rank trait bounds does not appear to be able to match on functions which take a bound that uses a lifetime that the function also uses. Case in point:

```rust
pub trait U<T> {}

impl<T> U<T> for () {}

pub fn inner<'a, T>(_: &'a ())
    where T: U<&'a ()>
{
    unimplemented!()
}

fn outer<F>(f: F)
    where F: for<'a> Fn(&'a ()),
{
    unimplemented!()
}

fn foo() {
    outer(inner)
}

```

([Playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=268e418107096468f8588dd9fdecb17c))

Errors:

```
   Compiling playground v0.0.1 (/playground)
error[E0631]: type mismatch in function arguments
  --> src/lib.rs:18:5
   |
5  | / pub fn inner<'a, T>(_: &'a ())
6  | |     where T: U<&'a ()>
7  | | {
8  | |     unimplemented!()
9  | | }
   | |_- found signature of `fn(&()) -> _`
...
18 |       outer(inner)
   |       ^^^^^ expected signature of `for<'a> fn(&'a ()) -> _`
   |
note: required by `outer`
  --> src/lib.rs:11:1
   |
11 | / fn outer<F>(f: F)
12 | |     where F: for<'a> Fn(&'a ()),
13 | | {
14 | |     unimplemented!()
15 | | }
   | |_^

error[E0271]: type mismatch resolving `for<'a> <fn(&()) {inner::<'_, _>} as std::ops::FnOnce<(&'a (),)>>::Output == ()`
  --> src/lib.rs:18:5
   |
18 |     outer(inner)
   |     ^^^^^ expected bound lifetime parameter 'a, found concrete lifetime
   |
note: required by `outer`
  --> src/lib.rs:11:1
   |
11 | / fn outer<F>(f: F)
12 | |     where F: for<'a> Fn(&'a ()),
13 | | {
14 | |     unimplemented!()
15 | | }
   | |_^

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0271`.
error: Could not compile `playground`.

To learn more, run the command again with --verbose.

```

You can get this to compile by swapping out `where T: U<&'a ()>` with `where T: U<()>`.
Repository: TypeScript
Issue: Types for async functions do not handle `void` assignments like normal ones
Labels: Bug

<!-- 🚨 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 `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.4.0-dev.201xxxxx

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
const w: void = "";

const x: () => void = () => "";

const y: () => Promise<void> = async () => "";

function a(): void {
    return "";
}

async function b(): Promise<void> {
    return "";
}

const y2: () => Promise<() => void> =  async () => () => "";

function a2(): () => void {
    return () => "";
}

function b2(): Promise<() => void> {
    return () => "";
}
```

**Expected behavior:**
Generally speaking, all of them should be an error, or all of them shouldn't be.

**Actual behavior:**
We have a special "function returning void" rule that allows `() => ""` to be assignable to `() => void`, but this doesn't carry thru to async scenarios, so a `async () => ""` is _not_ assignable to a `() => Promise<void>`.

[**Playground Link**](http://www.typescriptlang.org/play/#code/MYewdgzgLgBA7gLhgNxASwCYwLwwER4DcAUMaJLAB5IAUAlDgHwrpa71P5GnnQwCetBtmYAFAE4gAtmggBTADypMzXAEMI-MMBgcRXEsQBmAV21Q04GGvpJlWAN7EYLmOLlQT4sAeIBfUg0tHVNzSx8AI1sYCWlZRXtmJ1c3Dy8fAhIAsnA+fgAmIU5YmXkFPWZEnBcg7V1hZgrfYzNgCys1fOim+xhk13dPb3rOTP9SULbwmAiuuiQS+PKGlhU+5wG04aaxgKA)
Repository: vscode
Issue: Ability to disable language features provided by extensions
Labels: feature-request,extensions,under-discussion

Some languages are supported by multiple extensions that provide an overlapping set of language features.

Seems like much effort has been done to support this use case. For some features, the provider's 'score' is used to select which provider to use (e.g. for formatting and syntax highlighting). For other features, results from all providers are merged (e.g. completion, hover, definition, problems, symbols).

My problem is that in some cases I would like to choose which features to use from which extension. For example, I have three extensions that provide overlapping language features for Python: Microsoft's Python, pyright, and mypy extensions. 
 * For hovers, I only like the ones provided by the Python extension (it supports showing documentation while the others don't). Seeing hovers from all three extensions is distracting.
 * For error reporting, I would like to see only the ones from mypy. It is possible to filter the problems view, but it's annoying to filter every time, and filtering just for 'mypy' will ignore errors from other languages I have in my workspace. Without filtering, many duplicate errors are shown.
 * For 'go to definition' and code completion, I would like to use only pyright. By default, results from all three extensions are shown – this requires multiple clicks for every 'go to definition' call because results slightly differ between extensions, so they are shown side by side instead of immediately jumping to the definition.

One solution is to ask every extension author to provide options for disabling some features. This is already done by some extensions but AFAIK not by most. It can be solved centrally by allowing users to selectively disable language features provided by extensions. Something similar has [already been implemented](https://github.com/microsoft/vscode/issues/41882) for formatting, using a dedicated setting. I think it should be extended to other language features. 

Something like:
```json
"languageFeatures.[extension].goToDefinition.enabled": false
```

By default all features from all extensions would be enabled.