sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: JSDocTag width is inconsistent
Labels: Bug,Help Wanted,Effort: Moderate,PursuitFellowship

**TypeScript Version:**  3.8.0-dev.20191128

**Search Terms:** JSDocTag parsing JS doc

**Code**

```ts
import * as ts from "typescript";

console.log(ts.version); // 3.8.0-dev.20191128

const testFilePath = "/file.ts";
const testFileText = `
/**
 * @example Some text.
 * @param someParam - Some text.
 */
function test() {}`;

const testSourceFile = ts.createSourceFile(testFilePath, testFileText, ts.ScriptTarget.Latest, true);
const funcDec = testSourceFile.statements.find(ts.isFunctionDeclaration)!;
const tags = ts.getJSDocTags(funcDec);
const firstTag = tags[0];

console.log(firstTag.getText(testSourceFile)); // "@example"
console.log(firstTag.tagName.getText(testSourceFile)); // "example"
console.log(firstTag.comment); // "Some text."
console.log(firstTag.pos); // 8
console.log(firstTag.end); // 17
console.log(firstTag.getWidth(testSourceFile)); // 9

const secondTag = tags[1];

console.log(secondTag.getText(testSourceFile)); // "@param someParam - SomeText.\n"
console.log(secondTag.tagName.getText(testSourceFile)); // "param"
console.log(secondTag.comment); // "- Some text."
console.log(secondTag.pos); // 31
console.log(secondTag.end); // 62
console.log(secondTag.getWidth(testSourceFile)); // 31
```

![image](https://user-images.githubusercontent.com/1609021/70006095-e525cb80-1539-11ea-99b0-14200705e7e0.png)

![image](https://user-images.githubusercontent.com/1609021/70006105-efe06080-1539-11ea-8dcf-6e1bbe2f8534.png)

**Expected behavior:** The width would act the same for both.

**Actual behavior:** It's inconsistent or I'm missing something about `JSDocParameterTag`.
Repository: youtube-dl
Issue: --exclusion-archive and --error-archive ( the opposite of --download-archive )
Labels: request

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2019.11.28**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## Description

I use youtube-dl to archive YouTube channels. I run the same commands over and over to get new videos. The command I run looks like this (bash variables left in there):

`youtubedl --sleep-interval 60 -i --user-agent '${useragent}' --cookies /data/cookies.txt --download-archive ${directory}/archive.txt --write-info-json --write-description --write-thumbnail --socket-timeout 30 --restrict-filenames -o "${directory}/%(uploader_id)s_%(upload_date)s_%(title)s.%(ext)s" $channelUrl`

There's certain videos that seem to never download, I don't know why. Maybe it's user error. Here are a few examples:

```
[download] Downloading video 92 of 3668
[youtube] zP3IHPlyCqs: Downloading webpage
[youtube] zP3IHPlyCqs: Downloading video info webpage
[info] Writing video description to: /data/youtube/Suspicious0bservers/Suspicious0bservers_20190915_Water_Emergency_Earth_Sun_Galaxy_Electric_Sheets_S0_News_Sep.15.2019.description
[info] Writing video description metadata as JSON to: /data/youtube/Suspicious0bservers/Suspicious0bservers_20190915_Water_Emergency_Earth_Sun_Galaxy_Electric_Sheets_S0_News_Sep.15.2019.info.json
[youtube] zP3IHPlyCqs: Downloading thumbnail ...
[youtube] zP3IHPlyCqs: Writing thumbnail to: /data/youtube/Suspicious0bservers/Suspicious0bservers_20190915_Water_Emergency_Earth_Sun_Galaxy_Electric_Sheets_S0_News_Sep.15.2019.jpg
[download] Sleeping 60 seconds...
[download] Resuming download at byte 161691
```

In my error log, I see things like this regularly:

```
ERROR: unable to download video data: HTTP Error 404: Not Found
ERROR: Did not get any data blocks
```

I would like to have an argument that allows writing the names of error files to a specified file.
`--error-archive`
Any files that fail to download should be written there. I would like for the format of this file to be the same as the `--download-archive` file format, and be acceptable by another new argument: `--exclusion-archive`

The way I see this possibly working is - as CRON runs youtube-dl on schedule, error'd videos get written to the error archive file. Because I would specify the exact same file for `--error-archive` and `--exclusion-archive`, the next time CRON runs, the error'd files would be excluded. This would allow me to not get flagged by YouTube for too many requests, and not waste YouTube API time, and I can figure out what's happening with these videos at a later date instead of youtube-dl trying over and over.
Repository: pytorch
Issue: Dedicated inverse AdaptiveMaxPool1d operation (e.g., AdaptiveMaxUnpool1d)
Labels: module: nn,triaged,module: vision,module: pooling,function request

## 🚀 Feature
Note: I argue in the 1d context, I suspct this is also applicable to 2d / 3d context
There is no specific inverse operation for AdaptiveMaxPool1d. AdaptiveMaxPool1d returns the output and max index positions, and the only way to apply a "correct" inverse (via using the max index position) is to create a MaxUnpool1d layer and use output_size in the forward method. However, MaxUnpool1d requires a kernel_size argument as its constructor, which I currently set to some arbitrary high number with no background to it.

`a = torch.randn(64, 3, 10)`
`max, id = torch.nn.AdaptiveMaxPool1d(output_size=1, return_indices=True)(a)`
`unmax = torch.nn.MaxUnpool1d(kernel_size=1000)(input=max, indices=id,output_size=a.shape)`


## Motivation
the arbitrary nature of the kernel_size argument for MaxUnpool is confusing and unnecessary in an adaptive context.

## Pitch
An AdaptiveMaxUnpool1d function - consumes input and max index position as does traditional unpooling. But does not ask for kernel_size in its constructor. instead only uses output_size in its forward call.


## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @albanD @mruberry @fmassa @vfdev-5
Repository: TypeScript
Issue: refactoring for extracting return type of a function
Labels: Suggestion,Awaiting More Feedback

## Search terms

refactoring extract return type function method interface inferred

## Suggestion

A new refactoring for function expressions that extracts the return type of the function as an `interface` or `type`.

## Use Cases

Imagine a complex function that combines many types of data into a complex object. Compiler can infer the return type, but writing it out by hand takes time. Type needs a name when you want to use it elsewhere in the code (for example as a parameter type for another function).

## Examples

Imagine `A`, `B`, `C`, `D` are non trivial types. (e.g. objects with many properties)

before:
```typescript
function fooFunc(a: A, b: B, c: C, d: D) {
  return {
    ...a,
    ...b,
    foo: {...c, d}
  }
}
```

after:
```typescript
type FooFuncReturn = A & B & { foo: C & D }
// or when possible an interface type with would be even better

function fooFunc(a: A, b: B, c: C, d: D): FooFuncReturn {
  return {
    ...a,
    ...b,
    foo: {...c, d}
  }
}
```

## 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: godot
Issue: Duplicate collision detection when re-instancing Area2D nodes
Labels: bug,discussion,topic:physics

**Godot version:**

3.2 BETA 2

**OS/device including version:**

Windows 10 Pro 64 bit 1909

**Issue description:**

I'm using a `KinematicBody2D` for a "player" node and `Area2D` nodes for "obstacles". The player moves with `move_and_collide` and when it collides with an obstacle, it is game over and the level is reset. At this point, the player node has it's `position` manually set to the spawn point, while the obstacles are re-instanced (In the context of a larger level, where the states of many objects can change, re-instancing the level is preferable to going back and resetting the states of each individual object).

The issue, is that the new `Area2D` obstacles are colliding with the player node that has already moved out of the way. I don't know the inner workings of the Godot engine or how its physics works, but it feels like something is out of sync at some point.

**Steps to reproduce:**

Collide a `KinematicBody2D` with an `Area2D`. If the `KinematicBody2D` is then manually moved away from the obstacle, and the obstacle left as is, the collision happens once as expected. If the `KinematicBody2D` is manually moved away from the obstacle and the obstacle is recreated, the collision fires on the new obstacle even though the player node has been moved.

**Minimal reproduction project:**

I have attached a minimal project to show this behaviour:
[CollisionTest.zip](https://github.com/godotengine/godot/files/3916999/CollisionTest.zip)


I posted this issue on the Discord, but we couldn't figure it out. It does seem strangely simple, so I apologise in advance if this turns out not to be a bug, but I'm just doing something really stupid :)
Repository: kubernetes
Issue: Figure out what to do with webhook authz cache in large clusters
Labels: priority/backlog,sig/scalability,kind/feature,sig/auth,lifecycle/frozen

Some options are:

* Increasing LRU cache size
* Migrate to expiring cache
* Share authorization lookups

/sig auth
Repository: flutter
Issue: [web] need regression testing for package-scheme import fix
Labels: a: tests,framework,platform-web,P3,team-web,triaged-web

To ensure we don't accidentally regress in the future, the test case could use the example application linked in one of the fixed bugs, such as https://github.com/flutter/flutter/issues/44111
Repository: terminal
Issue: Add support for inheriting and overriding another profile's settings
Labels: Issue-Feature,Area-Settings,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement
I would like to make 2 profiles for same WSL, But as I tested, then you cannot put different GUID to make a duplicate with changes. I guess it is something to do with having same GUID and generator approach for the WSL using source field does not let you to have multiple GUIDs for same profile.
<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)
One way would be to let you have different name field for the same GUID and treat them different not merging settings. 
Other one I see is to have generator make a guid GUID to a group of terminals with same source, but then have subitem that could have multiple choices. 
Then to have a submenu for each terminal profile based on it that basically could have custom generated GUID. If there is only one subprofiles item, then it shows only one and not as a submenu.
Profiles.json then could be something like: 
```
    {
      "guid": "{58ad8b0c-3ef8-5f4d-bc6f-13e4c00f2530}",
      "hidden": false,
      "source": "Windows.Terminal.Wsl",
      "subProfiles": [
        {
          "guid": "{58ad8b0c-bc6f-3ef8-5f4d-13e4c00f2531}",
          "name": "Debian Half Dark",
          "useAcrylic": true,
          "fontFace": "Fira Code",
          "acrylicOpacity": 0.2,
          "colorScheme": "One Half Dark",
          "padding": "0, 0, 0, 0",
        },
        {
          "guid": "{58ad8b0c-5f4d-bc6f-3ef8-13e4c00f2532}",
          "name": "Debian Light",
          "useAcrylic": true,
          "fontFace": "Cascadia Code",
          "acrylicOpacity": 0.2,
          "colorScheme": "One Half Light",
          "padding": "0, 0, 0, 0",
        }
      ]
    }
```
<!-- 
A clear and concise description of what you want to happen.
-->
Repository: TypeScript
Issue: Ability to disable TS8010: 'types' can only be used in a .ts file.
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

TS8010
TS 8010
types can only be used in a .ts file
'types' can only be used in a .ts file

## Suggestion

Ability to disable TS8010: 'types' can only be used in a .ts file. Type annotations could simply be ignore by `tsc` when compiling a `.js` file.

## Use Cases

I work in a JS / TS blended codebase. My team uses WebStorm as our IDE, and it supports type annotations in .js files. When a variable/param is typed, it provides type-specific autocompletion. As you can imagine, that's quite powerful when working in a JS environment. Consequently, we have thousands of type annotations throughout our JS files. We would like to add `allowJs:true` to our `tsconfig.json`, however `tsc` throws an error for every type annotation in each JS file.

## 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: Uninstall should (offer to) remove old settings and config
Labels: Idea-Enhancement,Area-Setup/Install

Version	10.0.18363 Build 18363

uninstalled 0.13, rebooted, installed 0.14

When I pressed win+` for the first time I saw my old profiles and "space around zones"-settings.
An uninstaller must either just remove all old settings/make it a checkbox-option to do so/point towards a folder I can delete, to do so myself. Everything else is just brutish and nasty.
Omitting this wholesale is especially rude towards beta-testers.
If I wanted to make sure that certain bugs, behaviours and issues actually are fixed now, I would want to do this from a fresh install. Without any of my old workarounds and coerced-by-bug settings (like me setting "space around zones" to 0).
Now I'm forced to figure out where PowerToys stores its settings. Uninstall again.
Delete those settings and reinstall.
Repository: vscode
Issue: Custom editor webviews should not be recreated on rename
Labels: feature-request,api,api-proposal,custom-editors

From #85991

**Repo**
1. Using the `.abc` editor from  https://github.com/mjbvz/vscode-experimental-webview-editor-extension/
1. Create a file called `x.abc`. Open it
1. With the custom editor for `x.abc` still open, rename `x.abc` file to `y.abc` in the VS Code file explorer

**Bug**
Notice that the editor's webview is destroyed and then recreated. It would be preferable in this webview were kept alive across the rename (although perhaps only if the editor capabilities implement a `rename` method)

You can better confirm this by putting some sort of state into the webview, such as a script consisting of:

```js
let i = 0;
setInterval(() => console.log(++i), 1000);
````
Repository: flutter
Issue: Feature: dependencies for fluttermergebot
Labels: c: new feature,team,engine,team-infra,P3,triaged-infra

The merge bot works pretty well, but it would be nice if we could tell it about dependencies between PRs using text in the description or an issue tag.  For example:  https://github.com/flutter/engine/pull/13986 was auto-merged before https://github.com/flutter/engine/pull/14076 which caused some problems and necessitated further reverts.

Some sort of dependency expression like AFTER: 14076 would have been great here

@liyuqian @dnfield
Repository: TypeScript
Issue: `Object` variable declaration conflicts on commonjs
Labels: Bug

**TypeScript Version:**  3.7.x-dev.20191203

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
export default {}
const Object = {};
```

**Expected behavior:**
```js
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
{
exports.default = {};
const Object = {};
}
```
no error

**Actual behavior:**
```js
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.default = {};
const Object = {};
```
```
VM69:2 Uncaught ReferenceError: Cannot access 'Object' before initialization
    at eval (eval at <anonymous> (main-3.js:1239), <anonymous>:2:1)
    at main-3.js:1239
```
**Playground Link:** http://www.typescriptlang.org/play/index.html?module=1#code/KYDwDg9gTgLgBAE2AMwIYFcA28DeBfAKAGMIA7AZ3gHkAjAK2CPgF458BuIA

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: flutter
Issue: Consider record/replay functionality for tool bug reporting
Labels: c: new feature,tool,a: triage improvements,P3,team-tool,triaged-tool

In https://github.com/flutter/flutter/pull/45999, I'd like to remove the existing record-replay functionality due to bit rot. We should consider if this would be useful for bug reporting in the future, and if so how to add it back in a tested/principled manner.
Repository: flutter
Issue: [web] Text measurement difference in RTL
Labels: framework,a: typography,platform-web,customer: webeap,customer: web10,P2,team-web,triaged-web

There are cases where setting `direction: rtl` on a paragraph element leads to a different width!

Action items:
* Investigate more and see if this can be fixed in `DomTextMeasurementService` (by setting `direction: rtl` in the ruler element).
* Check if the same problem exists in `CanvasTextMeasurementService`.
Repository: vscode
Issue: Suggest widget has greyscale rendering
Labels: feature-request,ux,polish,suggest,lcd-text-rendering

Ref #85143 

Parameter hints doesn't have this issue, but hover and suggest widget suffer from it.

Top to bottom are parameter hint, suggest and hover:

![image](https://user-images.githubusercontent.com/4033249/70094049-82364200-15d6-11ea-95a9-a3eac4a81b77.png)

Version: 1.41.0-insider
Commit: 97855786a014be2440751b038b373c3726e11fe8
Date: 2019-12-03T05:31:49.954Z
Electron: 6.1.5
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Linux x64 4.15.0-55-generic
Repository: vscode
Issue: [scss] provide hover information for at-rules
Labels: feature-request,css-less-scss

Testing #85979

Hovering over any sass rules doesn't render any info even though we show that on completion.

![image](https://user-images.githubusercontent.com/35271042/70094431-59627c80-15d7-11ea-867b-be1caed2d3c4.png)

![image](https://user-images.githubusercontent.com/35271042/70094603-b8c08c80-15d7-11ea-922a-e961bcd0afd4.png)

But we do show additional info on other css properties:

![image](https://user-images.githubusercontent.com/35271042/70094446-61bab780-15d7-11ea-81ba-4c8a238b6c17.png)
Repository: flutter
Issue: SemanticsDebugger should use button flag
Labels: framework,a: accessibility,P2,team-framework,triaged-framework

Currently the SemanticsDebugger marks a thing as a button when it has a tab handler. That's not correct. It should only mark something as a button when it has the button flag set.

/cc @darrenaustin
Repository: pytorch
Issue: [FR] multidim squeeze and flatten
Labels: triaged,function request,module: viewing and reshaping

# squeeze

Previous FR for multidim squeeze: https://github.com/pytorch/pytorch/issues/1951

A PR (https://github.com/pytorch/pytorch/pull/4692) that attempted to implement https://github.com/pytorch/pytorch/issues/1951 was closed because 
> The behavior of this feature is very non-trivial, e.g., when negative and positive indices are mixed. I'm not sure it solves more problems that it adds anymore.

I would argue against that point, particularly for `squeeze`.

For `squeeze`, multidim is perfectly intuitive and defined, i.e., just squeezing the current dimensions the tuple refers. In fact, using a chain of squeeze (as suggested by the comment of https://github.com/pytorch/pytorch/pull/4692) is rather unintuitive. 

If one has a tensor that has size `1` at dims `2` and `3`, which they want to squeeze, it is far more intuitive to write 
```
t.squeeze((2, 3))
```
than to write
```
t.squeeze(2).squeeze(2)
```

Negative indices does not add to complexity or confusion either.

# flatten

Similarly, to merge the dims `1&2` and dims `3&4`, it is far more intuitive to write 
```
t.flatten([(1, 2), (3, 4)])
```
than 
```
t.flatten(1,2).flatten(2,3)
```
Repository: TypeScript
Issue: JSDoc optional argument does not generate an error in strict mode
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.
-->
from https://github.com/microsoft/vscode/issues/85015
<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.8.0-dev.20191203

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**
In a jsconfig project:

```json
{
    "compilerOptions": {
        "strict": true,
        "checkJs": true
    },
    "exclude": [
        "node_modules",
        "**/node_modules/*"
    ]
}
```

```js
// @ts-check

/**
 * @param {object} adventurer Information about the adventurer.
 * @param {string} [adventurer.dog] The adventurer's dog.
 */
export function test(adventurer) {
	return adventurer.dog.split(' ');
}
```

**Expected behavior:**
There should be an error on the call to split since `dog` is potential undefined.

**Actual behavior:**
No error

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** <!-- Did you find other bugs that looked similar? -->