sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: wiki doc: @template reference re: jsdoc (and old usejsdoc.org reference)
Labels: Help Wanted,Docs,PursuitFellowship

<!-- 🚨 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:**  N/A

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** docs, template, wiki

**Code**

N/A

**Expected behavior:**

`@template` is not a recognized tag per https://jsdoc.app/ , even if could be compatible as a custom tag. I think your docs at https://github.com/Microsoft/TypeScript/wiki/JSDoc-support-in-JavaScript should make clear that while the other items in the list of jsdoc tags are standard jsdoc, the particular tag `@template` is an exception and is not standard jsdoc.

Also, the reference to "usejsdoc.org" should be changed to its new site: jsdoc.app. (See https://github.com/jsdoc/jsdoc/issues/1642 on the lack of a working redirect.)

**Actual behavior:**

1. https://github.com/Microsoft/TypeScript/wiki/JSDoc-support-in-JavaScript seems to imply that `@template` is a valid, standard jsdoc tag or at least doesn't clarify that it is a custom tag and not one with behaviors compatible with jsdoc.
2. The docs link to usejsdoc.org

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

N/A

**Related Issues:** <!-- Did you find other bugs that looked similar? -->

None found.

@sandersn
Repository: vue
Issue: Regular slot and scoped slot with same name shouldn't be allowed
Labels: contribution welcome,feature request,warnings

### Version
2.6.10

### Reproduction link
[https://codepen.io/lee88688/pen/jjPpBm?editors=1010](https://codepen.io/lee88688/pen/jjPpBm?editors=1010)







### Steps to reproduce
as seen in codepen,  "hello" component have only one slot. but rendered 2 div tag at last. I have a look at Vue's code [renderSlot ](https://github.com/vuejs/vue/blob/530ca1b2db315fbd0e360807b2031d26665c5d3d/src/core/instance/render-helpers/render-slot.js#L8) which seems renderSlot function would treat the normal slot as scoped slot. why it would be like this?

the following code is render function of hello component which is compiled by Vue.compile. _t is renderSlot function. when normal slot and scoped slot in same component the problem above will be present.
```javascript
(function anonymous() {
    with (this) {
        return _c('div', [_t("default"), _v(" "), _t("default", null, {
            "x": x
        })], 2)
    }
}
)
```

### What is expected?
render just one slot.

### What is actually happening?
render one slot twice.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: create-react-app
Issue: use axios is not working in ie9-ie11 
Labels: issue: needs investigation

**### Environment**
node version: 11.12.0,
npm version: 6.7.0
create-react-app:3.0.1
This problem is specific for IE11 running on Windows 10

**index.js below:**
```
import 'react-app-polyfill/ie9';
import 'react-app-polyfill/ie11';
import 'react-app-polyfill/stable';
import 'es6-promise/auto'
```

**server.js below:**
```
export  function  getBlockLists(para){
	let url = `/tk/block/query/blockList`;
	let result =  myAxios.get(url, {params:para})
	console.log(result,33398)
	return result;
}
```

**component below:**
```
getLists_block(){
    console.log(this.state.page,111)
    getBlockLists(this.state.page)
      .then(({data})=>{
        console.log(data,222)
      })
      .catch((res)=>{
        console.log(res,333)
      })
  }

  componentDidMount(){
    this.getLists_block();
}
```
**but in ie11 ,not request ;error below:**
![QQ20190613-1](https://user-images.githubusercontent.com/23735606/59418461-a5d4b880-8dfb-11e9-93e9-d4d7ae25deff.jpg)
Repository: TypeScript
Issue: Separate directories for map files
Labels: Suggestion,Awaiting More Feedback

Hi!
I find it rather odd that the option mapRoot exists without a corresponding option which outputs the map files to said directory. I have to manually move them after transpiling, which is annoying (AND keep the same directory structure).

Here is a SO question which is valid for my case aswell: https://stackoverflow.com/questions/43052200/can-i-place-webpack-source-maps-and-source-code-files-in-seprate-folders

I guess it's kinda related to: https://github.com/microsoft/TypeScript/issues/6723
Repository: rust
Issue: `error[E0275]: overflow evaluating the requirement` from type inference
Labels: T-compiler,A-inference,C-bug

Example:

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2015&gist=03db32f00662d579ef0d91306b7c2ef5

If the trait type is listed explicitly instead of using type inference, then the error goes away. Likewise, if the recursive implementation for `Vec` is commented out, the error goes away.

This seems like something which should work, but the compiler gets stuck looking at the implementations for `Vec`, when there is a readily available implementation for `&Bar` which would work just fine.
Repository: pytorch
Issue: Improve multithreaded random number generation (RNG)
Labels: module: cpu,triaged,module: random,module: multithreading

We received some internal reports (for FB employees: https://fb.workplace.com/groups/329222650990087/permalink/438424466736571/) that multithreaded processing with RNG performs poorly. This is probably because the majority of our CPU code takes out a lock (locking) for the entirety of the kernel in question.

@syed-ahmed do any of your upcoming plans for RNG fix this problem?
Repository: flutter
Issue: Ability to disable Dismissible's clipper
Labels: c: new feature,framework,f: material design,c: proposal,has reproducible steps,P3,workaround available,team-design,triaged-design,found in release: 3.16,found in release: 3.18

Dismissible implements a [_DismissibleClipper](https://github.com/flutter/flutter/blob/f31fc1bd0faa9b706468cd4fed58b55e7d8eb509/packages/flutter/lib/src/widgets/dismissible.dart#L557) which prevents the background widget from displaying overflowing content beyond the current sliding state.
This causes widgets that are not perfectly square (For example, Cards with rounded corners) to incorrectly hide the background.

[Example video](https://i.imgur.com/q28z3oA.mp4)

## Steps to Reproduce

Create the default example project
Replace the two `Text` in the column by
```dart
            Container(
              height: 200,
              child: Dismissible(
                key: ValueKey("hi"),
                child: Card(
                  child: Text("hi"),
                ),
                background: Card(
                  color: Colors.red,
                ),
              ),
            )
```

```
[✓] Flutter (Channel master, v1.7.4-pre.74, on Linux, locale en_US.UTF-8)
    • Flutter version 1.7.4-pre.74 at /opt/flutter
    • Framework revision 75b5ceccd9 (20 hours ago), 2019-06-12 14:03:56 -0400
    • Engine revision ab5c14b949
    • Dart version 2.3.3 (build 2.3.3-dev.0.0 3166bbf24b)
```
Repository: vscode
Issue: Breakpoint moves with copy line up/down action
Labels: editor-contrib,under-discussion

**Version:**
- VSCode Version: 1.35.0
- OS Version: Windows 10.0.17134.799

**Steps to Reproduce:**
1. Create a new code file (of any supported language).
2. Write a few lines of code.
3. Place a break-point on a line.
4. Copy the line using _Copy Line Up_ or _Copy Line Down_ actions.

**Bug:**
The break-point moves with the copied line. It should stay.

**Does this issue occur when all extensions are disabled?** Yes
Repository: youtube-dl
Issue: ProgramCode from Page Source as filename?
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 2019.06.08. 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 **2019.06.08**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## 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.
-->
I'm downloading videos from UFC FIGHT PASS and they use a weird file label where there's a subtitle (for example the title of the PPV but not the 'UFC 2' part of the title), if I go on the webpage and click on View Page Source (on Firefox) and search for "UFC 2" I see that it's under ProgramCode. Is there a way this can be included in YouTube-DL so I can use in my file label? 

That way it can be (ProgramCode) %(title)s.%(ext)s

Here's an example

view-source:https://www.ufc.tv/video/no-way-out

Search for ProgramCode and you'll see what I mean.
Repository: TypeScript
Issue: Add a new type PublicOf
Labels: Suggestion,In Discussion

## Suggestion

Add the `PublicOf` type suggested in this [issue's comment](https://github.com/microsoft/TypeScript/issues/471#issuecomment-381842426) by @DanielRosenwasser 

## Use Cases

Implement a `class` public properties/methods without the need to implement private/protected ones.

## Examples
```typescript
// type to add
type PublicOf<T> = {
    [P in keyof T]: T[P]
}
```
```typescript
// use case
class C {
    private foo();

    public bar();
}

// No need to implement private method foo !
class D implements PublicOf<C> {
    public bar() {}
}
```

## 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: pytorch
Issue: symbol lookup error: libmkl_intel_lp64.so: undefined  symbol: mkl_blas_dsyrk (binaries built with static linking -DBUILD_SHARED_LIBS=OFF fail due to dynamic linker problem)
Labels: module: build,triaged,module: static linking,module: third_party,has workaround

Steps to reproduce:

```
mkdir build
(cd build && cmake -DBUILD_CAFFE2_OPS=OFF -DBUILD_SHARED_LIBS=OFF -DUSE_CUDA=OFF -DUSE_MKLDNN=OFF -DPYTHON_EXECUTABLE=$(which python) -DBUILD_BINARY=ON  .. && make -j)
```

Try to run one of the built binaries, e.g., `caffe2_benchmark`. It fails with:

```
build/bin/caffe2_benchmark: symbol lookup error: /scratch/ezyang/pytorch-tmp-env/lib/libmkl_intel_lp64.so: undefined symbol: mkl_blas_dsyrk 
```

The cause of this problem is that the binaries are being linked with mkl, but they aren't being linked with `-Wl,--no-as-needed` and so the static library that contains `mkl_blas_dsyrk` is being pruned too. I made a little stub application like:

```
add_executable(example-app "example-app.cpp")
target_include_directories(example-app PRIVATE ${ATen_CPU_INCLUDE})
target_link_libraries(example-app PRIVATE caffe2 -Wl,--no-as-needed caffe2::mkl )
set_property(TARGET example-app PROPERTY CXX_STANDARD 11)
```

and this solved the problem
Repository: go
Issue: cmd/go: add a new flag to disable unzipping after go mod download
Labels: NeedsInvestigation,FeatureRequest,GoCommand,modules

The `go mod download` caches the module files into the `$GOPATH/pkg/mod/cache/download` by default and extracts them into the `$GOPATH/pkg/mod` after the downloads are complete. This's fine. But today I encountered a problem that reminds me that we may need to disable the unzipping operation at some point.

---

So, I ran a program similar to the following using a non-root user:

```go
package main

import (
	"io/ioutil"
	"log"
	"os"
	"os/exec"
)

func main() {
	tempDir, err := ioutil.TempDir("", "foobar")
	if err != nil {
		log.Fatalf("failed to create temp dir: %v", err)
	}

	cmd := exec.Command("go", "mod", "download", "-json", "golang.org/x/text@latest")
	cmd.Env = append(os.Environ(), "GO111MODULE=on", "GOPATH="+tempDir)
	cmd.Dir = tempDir
	if err := cmd.Run(); err != nil {
		log.Fatalf("failed to download module: %v", err)
	}

	if err := os.RemoveAll(tempDir); err != nil {
		log.Fatalf("failed to remove temp dir: %v", err)
	}
}
```

Then I got the following failed output:

```bash
2019/06/14 01:03:21 failed to remove temp dir: unlinkat /var/folders/j6/2330_fdx4tn9t9tx4y117w700000gn/T/foobar128162500/pkg/mod/golang.org/x/text@v0.3.2/codereview.cfg: permission denied
exit status 1
```

Actually, I just need to download the module files and save them somewhere else (not in the `$GOPATH/pkg/mod/cache/download`), then clear the download history after the download is complete. But I got stuck in that `unlinkat` operation.

In my scenario, I don't actually need the `go` command to extract the zip files I downloaded into the `$GOPATH/pkg/mod`, but the `go` command doesn't ask me if it can do that. This not only caused unnecessary computing, but also causes problems such as the inability to remove the unzipped files if you don't have enough permissions.

So I think we should probably add a new flag like `-disable-unzip` to `go mod download` to disable the unzipping operation.
Repository: pytorch
Issue: torch.save also saves docstrings into pickle for some reason
Labels: module: serialization,triaged

Steps to reproduce:
1. Run:

```
from torch import nn
import torch
torch.save(nn.Conv2d(1, 1, 1, 1), 'moo.pt')
```

2. Open `moo.pt` in your editor

Expected result: a bunch of unintelligible binary gobbeldygook

Actual result: I see a docstring!!!

```
<80>^B<8a>
lü<9c>Fù j¨P^Y.<80>^BMé^C.<80>^B}q^@(X^P^@^@^@protocol_versionq^AMé^CX^M^@^@^@little_endianq^B<88>X
^@^@^@type_sizesq^C}q^D(X^E^@^@^@shortq^EK^BX^C^@^@^@intq^FK^DX^D^@^@^@longq^GK^Duu.<80>^B(X^F^@^@^@moduleq^@ctorch.nn.modules.conv
Conv2d
q^AX7^@^@^@/data/users/ezyang/pytorch-tmp/torch/nn/modules/conv.pyq^BX¸^[^@^@class Conv2d(_ConvNd):
    r"""Applies a 2D convolution over an input signal composed of several input
    planes.

    In the simplest case, the output value of the layer with input size
    :math:`(N, C_{\text{in}}, H, W)` and output :math:`(N, C_{\text{out}}, H_{\text{out}}, W_{\text{out}})`
    can be precisely described as:

...
```
Repository: rust
Issue: annotate-snippet emitter: Include suggestions in output
Labels: C-enhancement,A-diagnostics,T-compiler,E-help-wanted

Part of https://github.com/rust-lang/rust/issues/59346

In order for the new `AnnotateSnippetEmitterWriter` to include suggestions in the output, we essentially have to pass `&db.suggestions` to `emit_messages_default` and deal with a couple of edge-cases.

Relevant `FIXME`:

https://github.com/rust-lang/rust/blob/57a3300c2538fd1044ce45d9ef3b82182acb57ae/src/librustc_errors/annotate_snippet_emitter_writer.rs#L35-L36

`emitter.rs` equivalent:

https://github.com/rust-lang/rust/blob/0e4a56b4b04ea98bb16caada30cb2418dd06e250/src/librustc_errors/emitter.rs#L84-L115

* The tricky part is figuring out the first half of the conditional. We probably need it in the new emitter, too. Is it enough to just copy it over? Maybe extract that code so that the code is shared in both emitters?
* Otherwise it's just passing `&db.suggestions` through
* Should take into account the MAX_SUGGESTIONS value somewhere (add a UI test for this) 


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->
This issue has been assigned to @phansch via [this comment](https://github.com/rust-lang/rust/issues/61809#issuecomment-526804971).
<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"phansch"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: Semantics for Material Date picker emits unnecessary semantics nodes
Labels: framework,f: material design,a: accessibility,P2,team-design,triaged-design

This may not be a bug with DatePicker, but rather with the semantics compiler.

Reproduction:

With semantics enabled, open a DatePicker and dump the tree.

You'll see several `SemanticsNode`s for the weekday header (each one is actually an `ExcludeSemantics`), and for each empty container  for days of the week that are part of the previous month.

The tree should not include these nodes - they do not effect anything meaningful and make for extra time in tree operations.
Repository: flutter
Issue: Fix semantics offset rect for inline widgets
Labels: framework,a: accessibility,a: typography,P2,team-framework,triaged-framework

In `Paragraph.assembleSemanticsNode`, we are not properly including the offset of the placeholder rect in the semantics rect for the placeholder.

We should fix this, and fix that tests regarding this. See https://github.com/flutter/flutter/pull/34368
Repository: kubernetes
Issue: Remove the /cluster directory
Labels: area/test,sig/scalability,area/provider/gcp,sig/cluster-lifecycle,kind/feature,sig/testing,priority/important-longterm,lifecycle/frozen,sig/cloud-provider,area/code-organization,needs-triage

For years we have publicly stated that the /cluster directory is deprecated and not maintained.  However every cycle it is updated and there are bugs found+fixed by sig-cluster-lifecycle.  

I'd like to enumerate what needs to get done in order for us to wholesale remove the /cluster directory. 

/assign @dims @spiffxp @justinsb @timothysc  
/cc @liggitt @neolit123
Repository: flutter
Issue: Determine if iOS's rapid render upon app switch is vsync'ed
Labels: team,platform-ios,engine,P2,team-ios,triaged-ios

Determine if iOS's rapid render upon app switch is vsync'ed
Repository: terminal
Issue: If setting change requires restart, notify user
Labels: Area-Settings,Product-Terminal,Issue-Task

# Summary
If a setting is changed that requires the Terminal to restart in order for the setting change to take effect, consider displaying a message to the user prompting them to restart their Terminal.

Also, consider making it easier to identify settings that require a Terminal restart if changed, perhaps using an emoji/visual glyph of some kind?

# Related
This feature is related to #1252 suggesting that the Terminal should support restart/resume.

# Proposed technical implementation details (optional)

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: vue
Issue: Add context to warn message when adding reactive properties to an instance at runtime
Labels: improvement,warnings

### What problem does this feature solve?
The  ` [Vue warn]: Avoid adding reactive properties to a Vue instance or its root $data at runtime - declare it upfront in the data option.` message doesn't provide any insight about the component being affected or the property being set. Having those in place would make the deubbing way more easier.

### What does the proposed API look like?
` [Vue warn]: Avoid adding reactive properties to a Vue instance or its root $data at runtime - declare it upfront in the data option. Property being added: 'propertyName'.
<component trace>`

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: rust
Issue: Projecting to an associated constant fails but with wrong reason
Labels: A-type-system,E-needs-test,A-associated-items,T-compiler,C-bug,A-lazy-normalization,T-types

When you have:

```rust
trait Tr {
    const C: usize = 0;
    fn fun(x: [u8; Self::C]) -> [u8; 0] { x }
}
```

you get the usual problem:

```
error[E0599]: no associated item named `C` found for type `Self` in the current scope
 --> src/lib.rs:3:26
  |
3 |     fn fun(x: [u8; Self::C]) -> [u8; 0] { x }
  |                          ^ associated item not found in `Self`
  |
  = help: items from traits can only be used if the trait is implemented and in scope
  = note: the following trait defines an item `C`, perhaps you need to implement it:
          candidate #1: `Tr`
```

That this errors is *right*. However, it fails for the wrong reason.

What should happen here is that `Self::C` is seen as an opaque constant the value of which you don't get to assume in `fun`'s body. Therefore you should get a type error:

```

error[E0308]: mismatched types
 --> src/lib.rs:L:C
  |
L |     fn fun(x: [u8; Self::C]) -> [u8; 0] { x }
  |                                           ^ expected [u8; 0], found [u8; Self::C]
  |
  = note: expected type `[u8; 0]`
             found type `[u8; Self::C]`
```

cc https://github.com/rust-lang/rust/pull/61812
cc https://github.com/rust-lang/rust/issues/29661
Repository: pytorch
Issue: [FR] faster reduce sum on expanded/unfolded tensors
Labels: module: performance,triaged,module: linear algebra,function request

`bmm`, `tensordot`, and `einsum` all do some sort of `reshape` followed by one or more `mm`s. This makes doing reduction over arbitrary dimensions of large expanded/unfolded tensors slow, as the `reshape`s copy the data. 

In a real research project, we have a case where one wants to do `'bshk,bhksc->bhsc'`, where the second input tensor has a huge `k` but `sc` is unfolded from a single contiguous tensor (e.g., a custom 1d conv via unfold + reduce sum). Then all three options wants to permute and reshape to perform a matmul, and end up copying the 2nd input tensor, and could lead to OOM.

But that isn't necessary, if only we have kernels to do general dot product.

cc @jianyuh @nikitaved @pearu @mruberry @heitorschueroff @walterddr @IvanYashchuk @xwang233 @Lezcano @VitalyFedyunin @ngimel @vincentqb @vishwakftw