sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Exported int variables only display as sliders if their stepsize is set to something other that 1
Labels: bug,topic:editor,confirmed,usability

**Godot version:**
3.2.3.stable


**OS/device including version:**
Windows 10 Pro v.2004 / Inspiron 7373 Core i7-8550U / Intel(R) UHD Graphics 620


**Issue description:**
Exported int variables don't show up as sliders. If you set the step size to something else that 1, they do. For some reason it works to set the step size to a float under 1 and then it will work as an int slider.
![image](https://user-images.githubusercontent.com/4955051/96092425-c36bd380-0ec2-11eb-9a1b-f6605bc7ec2e.png)


**Steps to reproduce:**
Open attached project to see issue


**Minimal reproduction project:**
[export_int_issue.zip](https://github.com/godotengine/godot/files/5383176/export_int_issue.zip)
Repository: godot
Issue: "Align Transform with View" and "Align Rotation with View" only work if the 3D viewport is focused
Labels: bug,topic:editor,usability,topic:3d

**Godot version:** 3.2.3 and `master` (https://github.com/godotengine/godot/commit/0e7e25d488287517d54da221a69a8085b9ecd17d)

**OS/device including version:** Fedora 32, GeForce GTX 1080 (NVIDIA 450.66)

**Issue description:**

The "Align Transform with View" and "Align Rotation with View" 3D viewport menu options only work if the 3D viewport is focused. This is mainly an issue when aligning a node just after creating it, which I often do for camera nodes. Nonetheless, it still takes precious time away :slightly_smiling_face: 

I presume this is yet another issue related to a shortcut being *too* context-specific.

@EricEzaM Do you think we can make this shortcut apply "globally" safely? This way, it would work even if the 3D viewport is not focused.

**Steps to reproduce:**

- Create a new Camera3D node.
- Press <kbd>Ctrl + Alt + M</kbd> immediately after (without moving the mouse). Nothing will happen.
- Move the mouse outside and back in the 3D viewport, press <kbd>Ctrl + Alt + M</kbd> and notice it works as the 3D viewport is focused when the mosue enters it.

**Minimal reproduction project:** Any project will do.
Repository: rust
Issue: E0271 displays wrong span for "required by this bound"
Labels: A-diagnostics,T-compiler,C-bug

When compiling https://github.com/paritytech/polkadot/pull/1795/commits/828048247c644476c0b1e4acdaaf641f09cd49a3 with `cargo check -p polkadot-service`, I (correctly) receive several error messages, one of which is this E0271:

```
error[E0271]: type mismatch resolving `<OverseerSubsystemContext<Box<(dyn polkadot_node_subsystem::messages::ChainApiMessageTrait + 'static)>> as SubsystemContext>::Message == polkadot_node_subsystem::messages::ChainApiMessage<_, _, H256>`
    --> node/service/src/lib.rs:367:2
     |
367  |     Overseer::new(
     |     ^^^^^^^^^^^^^ expected struct `Box`, found enum `polkadot_node_subsystem::messages::ChainApiMessage`
     | 
    ::: /home/coriolinus/Documents/Projects/paritytech/polkadot/node/overseer/src/lib.rs:1057:13
     |
1057 |         CG: Subsystem<OverseerSubsystemContext<CollationGenerationMessage>> + Send,
     |             --------------------------------------------------------------- required by this bound in `Overseer::<S>::new`
     |
     = note: expected type `Box<(dyn polkadot_node_subsystem::messages::ChainApiMessageTrait + 'static)>`
                found enum `polkadot_node_subsystem::messages::ChainApiMessage<_, _, H256>`
     = note: required because of the requirements on the impl of `polkadot_overseer::Subsystem<OverseerSubsystemContext<Box<(dyn polkadot_node_subsystem::messages::ChainApiMessageTrait + 'static)>>>` for `ChainApiSubsystem<_, Arc<RuntimeClient>>`
```

Note that the bound reports a span at line 1057, referring to a `CollationGenerationMessage`. That line is irrelevant to the error. It should be displaying a span at line 1056, referring to a `ChainApiMessage`:

[snippet](https://github.com/paritytech/polkadot/blob/828048247c644476c0b1e4acdaaf641f09cd49a3/node/overseer/src/lib.rs#L1056-L1057):

```rust
CA: Subsystem<OverseerSubsystemContext<Box<dyn ChainApiMessageTrait>>> + Send, //1056
CG: Subsystem<OverseerSubsystemContext<CollationGenerationMessage>> + Send,    //1057
```

### Meta

`rustc --version --verbose`:
```
rustc 1.49.0-nightly (beb5ae474 2020-10-04)
binary: rustc
commit-hash: beb5ae474d2835962ebdf7416bd1c9ad864fe101
commit-date: 2020-10-04
host: x86_64-unknown-linux-gnu
release: 1.49.0-nightly
LLVM version: 11.0
```
Repository: rust
Issue: Error messages suggest lifetime annotations for stack references in some cases (E 106 instead of E 515)
Labels: C-enhancement,A-diagnostics,A-lifetimes,T-compiler,D-newcomer-roadblock

In a training, I was presented with the following code that someone wrote:

```rust
struct Point {
    x: i32,
    y: i32,
}

fn x_diff(a: &Point, b: &Point) -> &i32 {
    let diff = b.x - a.x;
    return &diff;
}

fn main() {
    let a = Point{ x: 1, y: 2 };
    let b = Point{ x: 3, y: 4 };
    let c = x_diff(&a, &b);
}
```

I expected to see this happen:

```
error[E0515]: cannot return reference to local variable `diff`
 --> src/main.rs:8:12
  |
8 |     return &diff;
  |            ^^^^^ returns a reference to data owned by the current function
```

Instead, this happened:

```
error[E0106]: missing lifetime specifier
 --> src/main.rs:6:36
  |
6 | fn x_diff(a: &Point, b: &Point) -> &i32 {
  |              ------     ------     ^ expected named lifetime parameter
  |
  = help: this function's return type contains a borrowed value, but the signature does not say whether it is borrowed from `a` or `b`
help: consider introducing a named lifetime parameter
  |
6 | fn x_diff<'a>(a: &'a Point, b: &'a Point) -> &'a i32 {
  |          ^^^^    ^^^^^^^^^     ^^^^^^^^^     ^^^
```

[Playground link](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=910c6a8a48e31af15d8baccba6837a97)

## Meta

Tested versions: 1.47 and 1.49.0-nightly (2020-10-14 e160e5cb80652bc2afe7).

I personally think those misdiagnoses may lead to learners being sent down the wrong path and interacting with the lifetime feature in places where it is not needed, leading to confusion.
Repository: vscode
Issue: API to trigger a refresh of the OUTLINE (DocumentSymbols)
Labels: feature-request,api,outline

I recreate the issue https://github.com/Microsoft/vscode/issues/71454 because it was closed.

My need is that I have a XML Language Server which supports settings for configuring symbols (like show/hide XML attributes, XML text nodes in the outline). When those settings are saved, I would like to refresh the outline.

If vscode could provide a command to refresh this outline, it should be great!

Thanks!
Repository: pytorch
Issue: GPU memory leak when registering a forward hook with "self" access
Labels: module: cuda,module: memory usage,triaged,has workaround

## 🐛 Bug

First of all, I am not sure if this issue relates to PyTorch or Python. However, since it happens only on GPUs, I am suspecting that it relates to PyTorch. Apologies if this is not a PyTorch problem.

I found a GPU memory leak (or better to say garbage collection issue) when I register a function with `self` access as a forward hook in a module. This problem happened when I was iteratively instantiating my module without even calling the forward function.

## To Reproduce

Steps to reproduce the behavior:

1. Create a module inheriting from `nn.Module`
2. Add some modules (sub-modules) inside (choose memory-hungry ones to see the effect clearly)
3. Define a forward hook function inside the `__init__` (to have the `self` access) and perform some operations using the `self.` your desired module
4. Register the forward hook
5. Iteratively create an instance of your module and put it on GPU (no need to call it)

```python
import torch
import torchvision.models as models
import torch.nn as nn

class LeakyModule(nn.Module):
    def __init__(self):
        super(LeakyModule, self).__init__()
        self.resnet = models.resnet152()
        
        def fw_hook(m, m_in, m_out):
            self.resnet(m_in)

        self.register_forward_hook(fw_hook)

for i in range(1000):
    net = LeakyModule()
    net.to('cuda:0')
    print(f"{torch.cuda.memory_stats('cuda:0')['allocated_bytes.all.current']}")
```

## Expected behavior

If there is no `self` in the hook function, the GPU memory gets freed after each iteration. But in this case, it remains for a longer time in the memory (without any reference). If you force the garbage collector (GC) to collect or transfer your module back to the CPU, there will not be any memory problem. First, I thought it is just a "late" collection by the GC, and I expected that it happens, at the latest when I need the GPU memory. But, I got "cuda out of memory" during my execution, which is not the case if I manually delete the module and call the GC to collect or transfer it to the CPU at the end of each iteration.

## Environment
 - PyTorch Version: 1.6
 - OS: Ubuntu 18.04
 - How you installed PyTorch: conda
 - Python version: 3.7
 - CUDA/cuDNN version: cuda10.1/cudnn7.6.3
 - GPU models and configuration: Nvidia Titan V

cc @ngimel
Repository: youtube-dl
Issue: Select the best quality with a unified extension
Labels: request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2020.09.20. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2020.09.20**
- [x] I've searched the bugtracker for similar feature requests including closed ones (for year 2020 - my search "https://github.com/ytdl-org/youtube-dl/issues?page=3&q=Requested+formats+are+incompatible+for+merge+and+will+be+merged+into+mkv" gives 11 pages)

https://github.com/ytdl-org/youtube-dl/issues/26810, https://github.com/ytdl-org/youtube-dl/issues/25089

## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
-->

Using the bare-bones command line, sometimes it ends up with
https://github.com/ytdl-org/youtube-dl/blob/7947a1f7dbc6ba47a6f22ab67fd330e57c0ef87c/youtube_dl/YoutubeDL.py#L1903
this message. I wonder if there could be a way to get "almost the best video quality" (be that e.g. webm or mp4), without resorting to mkv, and without hardcoding what to get explicitly.

I don't want to use mkv if I will get something like "just 5% better quality".
Repository: TypeScript
Issue: Declaration merging can be inconsistent
Labels: Needs Investigation,Rescheduled

**TypeScript Version:**  4.0.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
- module
- declare
- merging
- declaration

**Code**

_Source_ file `index.ts`:
```ts
import { foo } from "./foo.ts"
console.log(foo({ fooField: "hello" }))
```

_Source_ file `foo.ts`:
```ts
import { Bar } from "bar"

declare module "bar" {
  interface Bar {
    fooField?: string
  }
}

export const foo = (e: Bar) => e.fooField
```

_Compiled_ `index.d.ts`:
```ts
export {};
```
_Compiled_ `foo.d.ts`:
```ts
import { Bar } from "bar"
declare module "bar" {
    interface Bar {
        fooField?: string;
    }
}
export declare const foo: (e: Bar) => string | undefined;
```

**Expected behavior:**
_Compiled_ `index.d.ts` should look like:
```ts
import "./foo"
export {};
```
The declaration merging for module "bar" should be happening when importing `index.d.ts`. More precicely:

The compiler should automatically replace `import { x } from "./foo"` with `import "./foo"` when generating `.d.ts` file, if no type from `foo.d.ts` is used/exposed but importing that file would result in module declarations merging.

**Actual behavior:**
`index.d.ts` does not import `./foo.d.ts`, meaning that the declaration merging does not happen for module `"bar"`.

Now if we do decide to export something from `foo.ts`, then everything just "works" (`./foo.d.ts` gets referenced from `index.d.ts`), which is wrong for several reasons:
- we might not want to expose anything from foo
- compilation errors might start occurring in the importing file (if it relied on `Bar.fooField`), because an unrelated export was removed
- when developing `index.ts`, the dev will "see" the `Bar.fooField` property, and will wrongly assume that any user of that file will "see" it as-well.

The current way of supporting this is to manually `import "./foo"` at the beginning of `index` (in addition to the `import { foo } from './foo'`). But then it means that you need to know the internals of every dependency you have (you only need to explicitly import modules that do declare module definitions to be merged).

The compiler should automatically replace `import { x } from "./foo"` with `import "./foo"` inside `.d.ts` file, even if no type from `foo.d.ts` is used, if importing that file would result in a declaration merging.

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->
https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzgMwhOBfFUIjgIgDoB6VCfAWACgBjCAOwGcIAbAU0JYgHMAKM3ggwBKYdWrFicYMjgkyhKIzh16MAIbAmcZiDZwAJmxot1UdTGAM4eqNy3cANHBgALNgE84AdwYByeAAjfXUwMBZgNgMfd3ppcGhLem4XV2BlZGB2IA

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
N.A.
Repository: flutter
Issue: Ink widget inside ListView is buggy
Labels: framework,f: material design,f: scrolling,c: rendering,has reproducible steps,P2,found in release: 3.3,found in release: 3.6,team-design,triaged-design

I have ListView with Ink widgets which are updating with a little delay. And there is a bug with rendering of the list.
<img width="417" alt="Screenshot 2020-10-15 at 14 11 27" src="https://user-images.githubusercontent.com/5296407/96116076-93d3c000-0ef0-11eb-9168-e77c64e5e6f7.png">

Reproducing example (click fab and wait):
https://dartpad.dev/9241b35be5afed3651ea322e75424bc2

If I change Ink to Container it works fine.

UPD: Wrapping Ink into Material also helps.

```
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      debugShowCheckedModeBanner: false,
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key}) : super(key: key);

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  bool _expanded = false;

  void _changeItem() {
    Future.delayed(const Duration(seconds: 1), () {
      setState(() {
        _expanded = !_expanded;
      });
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: ListView.builder(
        itemCount: 5,
        itemBuilder: (context, index) =>
            Item(index, index == 1 ? _expanded : false),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _changeItem,
        child: Icon(Icons.check),
      ),
    );
  }
}

class Item extends StatelessWidget {
  final int index;
  final bool expanded;

  const Item(this.index, this.expanded, {Key key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return Padding(
        padding: EdgeInsets.all(16),
        child: Ink(
            color: Colors.grey,
            child: Padding(
                padding: const EdgeInsets.all(16),
                child: Column(children: [
                  Text("Row $index"),
                  if (expanded)
                    Padding(
                      child: Text("Expanded"),
                      padding: const EdgeInsets.all(16),
                    ),
                ]))));
  }
}
```
Repository: vscode
Issue: Remote-SSH & WSL: Support trash
Labels: feature-request,WSL,remote,file-io,ssh

<img width="208" alt="Screen Shot 2019-10-31 at 10 15 06 PM" src="https://user-images.githubusercontent.com/20842215/67997768-fd00eb80-fc2b-11e9-9d54-bfcbf705de51.png">
Issue Type: <b>Feature Request</b>

On my vscode remote-ssh (Ubuntu), I can only delete file permanently, which caused many troubles. Could vscode remote-ssh add features to remove file to trash?

On my local env, I can delete files to trash.

VS Code version: Code 1.39.2 (6ab598523be7a800d7f3eb4d92d7ab9a66069390, 2019-10-15T15:33:00.827Z)
OS version: Darwin x64 18.7.0
Remote OS version: Linux x64 4.4.0-165-generic


<!-- generated by issue reporter -->
Repository: godot
Issue: Contrast of lines against environment is minimal
Labels: discussion,topic:editor

**Godot version:**
v3.2.2.stable.mono.official

**OS/device including version:**
Mac OS 10.14 Mojave on Macbook Pro 2013 13"

**Issue description:**
There is very minimal contrast between the lines that define borders of things such as collision shapes and the environment and i cannot seem to find any kind of fix, have asked on Reddit and Discord to no avail.
<img width="637" alt="Screenshot 2020-10-14 at 15 37 57" src="https://user-images.githubusercontent.com/65493086/96120847-135c9180-0ee7-11eb-8bf6-e4ea18d58490.png">
Repository: TypeScript
Issue: Cryptic error message without --noImplicitAny
Labels: Bug

**TypeScript Version:**  4.1.0-dev.20201015

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** noImplicitAny

In the JS mode given the class inheritance hierarchy A -> B -> C, when B code refers to class declaration (e.g. in a `clone()` method) and the class is assigned to an object property (`NS.B = class ...`), an attempt to convert an instance of C to B returns a cryptic error message: `Property <property name> is missing in type 'C' but required in type 'B'`.

**Expected behavior:** This diagnostic isn't helping, maybe omit it?

<!-- Did you find other bugs that looked similar? -->
**Related Issues:**

**Code**
```ts
class A {
	clone() {
		return new A();
	}
}

var NS = {};

NS.B = class extends A {
	constructor(v) {
		super();
		this.val = v;
	}

	//** @returns {NS.B} */  // this jsdoc comment fixes the error
	clone() {
		return new NS.B(this.val);
	}
}

class C extends NS.B {
	constructor() {
		super(1);
	}

	clone() {
		return new C();
	}
}


/** @returns {NS.B} */
function f() {
	return new C(); // error here: Property 'val' is missing in type 'C' but required in type 'B'.
}
```




<details><summary><b>Compiler Options</b></summary>

```json
{
  "compilerOptions": {
    "alwaysStrict": true,
    "esModuleInterop": true,
    "checkJs": true,
    "allowJs": true,
    "declaration": true,
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true,
    "moduleResolution": 2,
    "target": "Latest",
    "jsx": "React",
    "module": "ESNext"
  }
}
```


</details>

**Playground Link:** [Provided](https://www.typescriptlang.org/play?noImplicitAny=false&strictFunctionTypes=false&strictPropertyInitialization=false&strictBindCallApply=false&noImplicitThis=false&noImplicitReturns=false&target=99&ts=4.1.0-dev.20201015&useJavaScript=true#code/MYGwhgzhAECC0G8BQBIUB7AdgUwBQEpFUUAnbAFwFcTNocB3OAgblQF8kOkA3ME6AHIBlaAF5EbVkmEA6AEJjooSDGwAPctkwATGPGRosEciUrBy6Erm6EDKCJQAO2K-lYoU5ABYBLCDN4QRW53LhQAenCAKijoAAEyKhoYBFk5Nmgo8OhoSOhvP2gAKwhtdGAldABbKq1yaAAzHzVsGG9saBcSS1QMHAIiD0TqWgZBIXlcAv9At3ZOJCRlKGgAYU6NLV1x+UHgIxMzC1dB+ycXXABGOZQwvrxbYmGaOmxGVZZ5riRo2ISKEYpNIZLJIBqUTDmHxYRoDAzPUZvNafNhAA)
Repository: rust
Issue: proc-macro receives warnings only when used within `macro_rules!` macros
Labels: A-lints,A-macros,C-bug

A proc-macro that generates code with the partial same span as the input, receive warnings in the generated code only when used within `macro_rules!` macros. (does not receive warnings if used outside `macro_rules!` macros.)

*This originally reported in https://github.com/taiki-e/pin-project/pull/298* ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=fb33b572fc967f70710edb5026083266)).

### Repro:

`Cargo.toml`:

```toml
[package]
name = "repro"
version = "0.0.0"
authors = ["Taiki Endo <te316e89@gmail.com>"]
edition = "2018"
publish = false

[lib]
proc-macro = true

[dependencies]
proc-macro2 = "1"
quote = "1"
syn = { version = "1", features = ["full"] }
```

`src/lib.rs`:

```rust
extern crate proc_macro;

use proc_macro::TokenStream;
use proc_macro2::{Ident, Span};
use quote::quote;

#[proc_macro_attribute]
pub fn repro(_arg: TokenStream, input: TokenStream) -> TokenStream {
    let item: syn::ItemStruct = syn::parse_macro_input!(input);

    let name = format!("{}2", &item.ident);
    let name = Ident::new(&name, Span::call_site());
    let vis = &item.vis;

    TokenStream::from(quote! {
        #item
        // can be avoid by adding `#[allow(missing_debug_implementations)]`
        // or change `vis` to call-site span
        #vis struct #name {
            _f: ()
        }
    })
}
```

`tests/test.rs`:

```rust
#![warn(missing_debug_implementations)]

#[repro::repro] // <- no warning
#[derive(Debug)]
pub struct A {
    _f: (),
}

macro_rules! mac {
    () => {
        #[repro::repro] //~WARN type does not implement `Debug`
        #[derive(Debug)]
        pub struct B {
            _f: (),
        }
    };
}

mac!();
```

This example uses `missing_debug_implementations`, but the same problem occurred with `unreachable_pub`, `variant_size_differences`, `clippy::missing_const_for_fn` etc., so it doesn't seem to be specific to some lint.

### Meta

It can be reproduced at least in 1.31, stable (1.47), beta (1.48), nightly-2020-10-15.

`rustc --version --verbose`:
```
rustc 1.49.0-nightly (e160e5cb8 2020-10-14)
binary: rustc
commit-hash: e160e5cb80652bc2afe74cb3affbe35b74243ea9
commit-date: 2020-10-14
host: x86_64-apple-darwin
release: 1.49.0-nightly
LLVM version: 11.0
```
Repository: svelte
Issue: global css should be removed when component which injected it gets destroyed
Labels: temp-stale

**To Reproduce**
https://svelte.dev/repl/385622e1aa2d4dd1a538a649761ef50a?version=3.29.0

**Expected behavior**
I don't really know if this is working as expected, but in a component oriented context i would expect to work the way i'm describing here: Global CSS injected should be removed after the component that contains it is destroyed.

I say so because in this way i would be allowed to style parent elements conditionally to which child is mounted (like in my repl).
With the actual implementation, i'm stuck to use props or context with store to tell in some way the parent which style should he have.

**Information about your Svelte project:**
Svelte 3.29.0

**Severity**
Anonoying