sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: yt-dlp
Issue: [Feature Request] Add expiry date to applicable extractors' metadata
Labels: site-enhancement

## Checklist

- [x] I'm reporting a feature request
- [x] I've verified that I'm running yt-dlp version **2021.08.02**
- [x] I've searched the bugtracker for similar feature requests including closed ones

## Description

When certain extractors download the metadata of a video, they sometimes provide a url that will expire in a certain amount of time. For example, the links the youtube extractor provides expire after 6-ish hours (21598 ± 1 seconds, if the video link's "expire" parameter is accurate) and unless you parse the output url then it is impossible to gauge when this would occur. All I would like to see is, when applicable, a simple unix timestamp on when a videos link would expire provided when you extract the metadata of a video.

Ex.
```jsonc
{
  "title": "Example Video",
  "url": "https://example.com/v?id=12345&expires=1627919375",
  // The new feature 
  "expiry_date": 1627919375,
  "formats": [
    // ...
    {
      // ...
      "url": "https://example.com/v?id=12345&expires=1627919375",
      // The new feature 
      "expiry_date": 1627919375,
    }
  ]
}
```
Repository: go
Issue: doc/tutorial/create-module: describe use of multiple packages within the same module
Labels: Documentation,NeedsInvestigation,modules

The tutorial at https://golang.org/doc/tutorial/create-module starts by creating a package within one module, then (in https://golang.org/doc/tutorial/call-module-code) uses that package from within another module.

However, for most user projects we want to encourage users to develop all of their own packages within a _single_ module — the dependency management is much simpler that way, and having multiple modules is only really an advantage if the user needs to release packages from within those modules on independent schedules.

It isn't entirely trivial to figure out how to use one package from another in the same module (see, for example, https://stackoverflow.com/q/68616619).

I think the “Create a Go module” tutorial should demonstrate the use of multiple packages within the same module before the (much more advanced) multi-module workflow.

CC @stevetraut @jayconrod @matloob
Repository: vscode
Issue: the default value of `editor.autoClosingDelete` should be "always"
Labels: under-discussion,editor-autoclosing

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
The new setting `editor.autoClosingDelete` has been introduced for several months now. It can be set to `auto`, `always` or `never`.

For years, the default behavior was `always`, but since this feature was added, the default for new users became `auto`. After months of testing, I've come to the conclusion that `always` is a better candidate for default, because `auto` is not smart enough, for several reasons:

1. When a pair is created by auto-insert, then I move the cursor away, then come back and delete, the program no longer remember it was auto-inserted, so auto-delete won't happen. 
2. After auto-insert, if I keep the cursor in place, but switch to a different tab and switch back, the program no longer remember it was auto-inserted, so auto-delete won't happen. 
3. Not to mention the case when I close a file and revisit it later.
3. When you highlight a piece of text `foo`, then press a key to "auto surround" it, making it `"foo"` or `(foo)` or `[foo]`,  the pair is not considered auto inserted, and auto delete won't happen even if you delete immediately.
4. When you see a string like `"bar"`, and you double click it to highlight, then try to `backspace×2`  to delete it, it won't work.
3. In snippets, say you have a snippet called "arrow", which is somethin like `(|) => {|}`, the pairs are not considered auto inserted, so when you tab through them and delete, auto delete won't happen.
1. Generally, whenever you have a cursor in between brackets like `{|}` then press `backspace`, human brains expect a consistent outcome every time. Since human brains don't remember whether the pair of brackets was auto-inserted, the current behavior always feel inconsistent and not intuitive.

1-6 happens a lot, especially 1 and 2 happens so often, that in 90% cases auto delete won't happen, so the new default settings is mostly equal to "never", which is wasting a nice feature for new users. In the rest 10% cases when auto delete does happen, it's even worse, due to the inconsistency in 7.
Repository: youtube-dl
Issue: Get preview thumbnail
Labels: duplicate,question

<!--

######################################################################
  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:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

Is there a way to generate or extract sprite+vtt( preview on progress bar) pf youtube or other videos?
Repository: terminal
Issue: Strange behavior of buffer of CJK letters?
Labels: Area-Output,Issue-Bug,Product-Terminal,Priority-2

### Windows Terminal version (or Windows build number)

1.9.1942.0

### Other Software

fzf

### Steps to reproduce

Run `fzf` in folders with many files with CJK names, and search anything.

### Expected Behavior

Display correctly. (Maximize then restore can also make it correct.)

### Actual Behavior

<img width="857" alt="屏幕截图 2021-08-03 010223" src="https://user-images.githubusercontent.com/75518399/127898645-b368adfe-7d96-442c-847d-5c00b76d6eed.png">
Repository: pytorch
Issue: static library kineto_LIBRARY-NOTFOUND not found.
Labels: triaged,module: build warnings

## 🐛 Bug

Noisy build spam

```
CMake Warning at /usr/local/google/home/silvasean/.local/lib/python3.9/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:22 (message):
  static library kineto_LIBRARY-NOTFOUND not found.
Call Stack (most recent call first):
  /usr/local/google/home/silvasean/.local/lib/python3.9/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:127 (append_torchlib_if_found)
```

## To Reproduce

Steps to reproduce the behavior:

1. See setup instruction at https://github.com/llvm/mlir-npcomp
1. Configure

## Expected behavior

I would expect the build to be quiet or fail here.

## Environment

Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
PyTorch version: 1.10.0.dev20210802+cpu
Is debug build: False
CUDA used to build PyTorch: Could not collect
ROCM used to build PyTorch: N/A

OS: Debian GNU/Linux rodete (x86_64)
GCC version: (Debian 10.2.1-6+build2) 10.2.1 20210110
Clang version: 11.0.1-2
CMake version: version 3.18.4
Libc version: glibc-2.31

Python version: 3.9.2 (default, Feb 28 2021, 17:03:44)  [GCC 10.2.1 20210110] (64-bit runtime)
Python platform: Linux-5.10.40-1rodete2-amd64-x86_64-with-glibc2.31
Is CUDA available: False
CUDA runtime version: 10.1.243
GPU models and configuration: GPU 0: Quadro P5000
Nvidia driver version: 460.56
cuDNN version: /usr/local/cuda-10.1/targets/x86_64-linux/lib/libcudnn.so.7.6.4
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.19.5
[pip3] torch==1.10.0.dev20210802+cpu
[pip3] torchvision==0.11.0.dev20210802+cpu
[conda] _pytorch_select           0.2                       gpu_0  
[conda] blas                      1.0                         mkl  
[conda] cudatoolkit               10.1.243             h6bb024c_0  
[conda] mkl                       2020.1                      217  
[conda] mkl-include               2020.2                      256  
[conda] mkl-service               2.3.0            py38he904b0f_0  
[conda] mkl_fft                   1.1.0            py38h23d657b_0  
[conda] mkl_random                1.1.1            py38h0573a6f_0  
[conda] numpy                     1.18.5           py38ha1c710e_0  
[conda] numpy-base                1.18.5           py38hde5b4d6_0  
[conda] numpydoc                  1.1.0                      py_0  
[conda] pytorch                   1.6.0           py3.8_cuda10.1.243_cudnn7.6.3_0    pytorch
[conda] torchvision               0.7.0                py38_cu101    pytorch
```
Repository: node
Issue: `pause` is not emitted when `data` listener is removed
Labels: stream

### Version

v16.6.0

### Platform

Linux solus 5.13.6-190.current #1 SMP PREEMPT Fri Jul 30 17:08:12 UTC 2021 x86_64 GNU/Linux

### Subsystem

stream

### What steps will reproduce the bug?

```js
const {Readable} = require('stream');

const r = new Readable({
    read() {}
});

const nop = () => {};

r.on('resume', () => {
    console.log('resumed');
    r.off('data', nop);
});

r.on('pause', () => {
    console.log('paused');
});

r.on('data', nop);
```

### How often does it reproduce? Is there a required condition?

Always.

### What is the expected behavior?

```
resumed
paused
```

### What do you see instead?

```
resumed
```

### Additional information

_No response_
Repository: vscode
Issue: Middle Click for Fast Scroll Notebook
Labels: feature-request,notebook-layout

## Environment data

-   VS Code version: 1.58 (june 2021)
-   Jupyter Extension version (available under the Extensions sidebar): v2021.8.1054968649
-   Python Extension version (available under the Extensions sidebar): v2021.7.1060902895
-   OS (Windows | Mac | Linux distro) and version: Windows 10: 21H1
-   Python and/or Anaconda version: 3.9.6
-   Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
-   Jupyter server running: Local | Remote | N/A: Local and remote

## Expected behaviour

- Before the last release I was able to "middle click" in order to scroll by moving the mouse back and forward.
**This option is very useful**, especially with long notebooks outputs and was very appreciated !
I use VSCode Insiders

## Actual behaviour

Right now, nothing happens for scrolling when I middle click. (except i have the "little white hand" for drag and drop that shows off)

## Steps to reproduce:

Middle Click (on the scroll wheel), pointing the mouse on the very left side of a cell in a *Jupyter Notebook inside VSCODE*
Repository: TypeScript
Issue: Inferred type parameter does not satisfy constraint
Labels: Bug

# Bug Report

### 🔎 Search Terms

generic constraint, inference, invalid, specified, manually, explicitly, invalid

### 🕗 Version & Regression Information

- This changed between versions 3.3 and 3.5

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.3.5#code/CYUwxgNghgTiAEAzArgOzAFwJYHtVIB4AVAGngFV4QAPDEVYAZ3iID4AKMAIwC553kfcgEp4AXlYthQgFAyweRhngA3cUgHjJAImrbhAbhkB6Y-AWolqvmgDWqHAHd8BALSv4jqFgxlHACygMAH4TMxR0bDxCJRgsVABzMjsHZw5uPgEbVHsnVFEJeFj4hOl4FLy5RAJixOSc1NQOZC14XX0DeFMqGBgcGDIcRHMcZBhGEDD4dxnJAD8FxbmpogBPAAcEAHIK5y34YBwQZgdlRiCsRkRV+Ax-BAtY71RlLdqErYA6IA)

### 💻 Code

```ts
declare function f<T, U extends T>(cb: (u: U) => T): U

const v = f(u => "x");
// const v: unknown <-- wait, what?
// function f<string, unknown>(cb: (u: unknown) => string): unknown

f<string, unknown>(u => "x"); // error, of course
// -----> ~~~~~~~
// Type 'unknown' does not satisfy the constraint 'string'.
```

### 🙁 Actual behavior

In TS3.5+, the type parameter `T` is inferred to be `string`, and `U` is inferred to be `unknown` in the first call to `f()`.  But then `U extends T` is not met; you couldn't even manually specify `T` and `U` like this when calling `f()`, as shown in the second call to `f()`.  

(In TS3.3, `T` and `U` are both inferred as `{}`.)

### 🙂 Expected behavior

Either I'd expect both `T` and `U` to be `string`, or I'd expect an error where the compiler says it cannot find a suitable candidate for `U`.   Presumably the compiler has not inferred `T` before it needs to infer `U`, and so it constrains `U` to `T`'s constraint which is implicitly `unknown`, and then falls back to that.  But it never circles back to make sure that such a fallback actually works for `U extends T`.

----

I came upon this while looking for an answer to [this SO question](https://stackoverflow.com/q/68625995/2887218).  This behavior is weird, right?  I haven't found an existing issue for it.
Repository: flutter
Issue: [Documentation]: In detail explanation on what options can be used in buildTypes{} in build.gradle
Labels: platform-android,d: api docs,a: quality,P3,team-android,triaged-android

## Steps to Reproduce

I'm not sure whether this is the right type of issue but it was the one that sounded the best.

1. I'm trying to figure out how to change the name of only the debug-app.
2. While doing so, I didn't manage to find any helpful resources.
3. Here's a list of (some but not all) websites I went trough:
https://developer.android.com/studio/build/build-variants
https://developer.android.com/reference/tools/gradle-api/4.1/com/android/build/api/dsl/BuildType
https://stackoverflow.com/questions/64479401/gradle-add-applicationidsuffix-depending-on-buildtype-for-a-specific-productfl
https://proandroiddev.com/android-set-a-default-build-type-flavor-a1cdcd1c15fa
https://medium.com/meeve/build-variants-in-flutter-for-multiple-backend-environments-7e139128949b
https://flutter.dev/docs/testing/build-modes

**I'd like to suggest adding a proper documentation that explains what options can be used in `buildTypes{}` in build.gradle.**

(Additionally, I would appreciate it if someone knew how to solve my problem)
Repository: youtube-dl
Issue: Plz add playhydrax.com? 
Labels: site-support-request


## Example URLs



- Single video: https://playhydrax.com/?v=JpOX4gel82
- 
- html embed: [https://minhdang1202.github.io/my-film/#/film/phimchieurap&H%C3%A0o%20Quang%20%C4%90%C3%A1nh%20C%E1%BA%AFp%20-%20DIVA&49](https://minhdang1202.github.io/my-film/#/film/phimchieurap&H%C3%A0o%20Quang%20%C4%90%C3%A1nh%20C%E1%BA%AFp%20-%20DIVA&49)
Repository: pytorch
Issue: Unexpected `is_training` after using `train` in a JIT Module
Labels: oncall: jit

## 🐛 Bug

Calling `.train` in a JIT Module seems to have no effect in the value returned by `is_training()`.

## To Reproduce

```
#include <torch/torch.h>
#include <iostream>

int main() {
    auto cu = std::make_shared<torch::CompilationUnit>() ;
    auto v = torch::jit::Module("test", cu);
    std::cout << v.is_training() << std::endl;
    v.train(false);
    std::cout << v.is_training() << std::endl;
}
```

Returns:

```
❯ ./test
1
1
```

## Expected behavior

I expected `is_training` to return 0 in the second call.

## Environment

The issue happens with both LibTorch 1.9 and todays nightly.

## Additional context

In our usage we create jit Modules and add traced methods to them. I don't expect this to have too much practical usage but feels weird when a traced module doesn't have the same `is_training()` value as the model it represents. See eg: https://github.com/mlverse/torch/issues/632


cc @gmagogsfm
Repository: pytorch
Issue: Guidance on where to add documentation
Labels: module: docs,triaged

## 📚 Documentation

As more docs are added to PyTorch, wondering if there's a clear guidance on structuring and where to add documentation given its context.

So far, we have

- pytorch/pytorch root README.md
- pytorch/pytorch sub-directory README.md
- Wiki https://github.com/pytorch/pytorch/wiki
- Docs Website https://pytorch.org/docs

cc @brianjo @mruberry
Repository: vscode
Issue: datalist popup isn't positioned correctly when used within a webview
Labels: bug,upstream,macos,webview,electron,confirmed,upstream-issue-pending

Trying to make a lightweight combo box using `input` and `datalist`. I have the following HTML:

![image](https://user-images.githubusercontent.com/2193314/127923384-0bc4fc0b-6856-479d-885a-612de82733f0.png)

It shows up correctly in the input element:

![image](https://user-images.githubusercontent.com/2193314/127923441-a6bd6aac-8abe-45b2-9542-cc7a84d2fc89.png)

But when I hit the arrow it's positioned wrong:

![image](https://user-images.githubusercontent.com/2193314/127923482-7441ea2f-3a01-44ba-8b93-873de6f12adf.png)

It should show right below the `input`.
Repository: create-react-app
Issue: [v5] Replace CaseSensitivePathsPlugin with eslint import/no-unresolved rule
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

The CaseSensitivePathsPlugin  is expensive, would be better for performance to use eslint rule https://github.com/import-js/eslint-plugin-import/blob/master/docs/rules/no-unresolved.md#casesensitive

referece: https://github.com/facebook/create-react-app/pull/11201#discussion_r681096819

### Describe the solution you'd like

https://github.com/facebook/create-react-app/pull/11201/commits/a2c859a522ba6cde5d4cd3b9f5b2e9f21423d1eb

### Describe alternatives you've considered

### Additional context

https://github.com/facebook/create-react-app/pull/11201#pullrequestreview-720369833
Repository: TypeScript
Issue: Consider adding setting that only shows inlay hint parameter names for simple literals (string, number, bool)
Labels: Suggestion,Awaiting More Feedback

# Suggestion

<!--
  Please fill in each section completely. Thank you!
-->

## 🔍 Search Terms
- inlay hints
- parameter names
- typescript.inlayHints.parameterNames.enabled

## ✅ Viability Checklist

N/A, tooling related

## ⭐ Suggestion

Add a new setting that only shows inlay hints for simple literals. This would include:

- string
- number
- bool
- regexp literal?
- null?
- undefined?

Currently the `"typescript.inlayHints.parameterNames.enabled": "literals"` setting also shows parameter name hints for function, array, and object literals

I imagine this new setting would be called something like:  `"typescript.inlayHints.parameterNames.enabled": "simpleLiterals"`, although better names welcome
Repository: TypeScript
Issue: `tsc` with `--target ESNext` fails but the same configuration succeeds on the playground.
Labels: Needs Investigation,Rescheduled

# Bug Report

`tsc` causes errors for  `--target ESNext` for some order of initialized variables and variables initialized in the constructor.

Why does the code produce errors for `ESNext` and no error for any other target?

### 🔎 Search Terms

- ESNext

### 🕗 Version & Regression Information

The command line fails on the code where the playground succeeds.

### ⏯ Playground Link

You have to set the `--target` to `ESNext` for this script [Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.3.5#code/GYVwdgxgLglg9mABAdwE4ygUwGoEMA2AFLgFyJggC2ARpqgDSLVm5gCeAlGRTXYgN4AoRCMQQEAZzj5MAOnxwA5oQDkaDDgIrGuRtQ4BuYaNSYoIVElxGAvoIj5cEiYgAqmCVADCj5wOMipORUtKhGoogADiDU+DAQTIgAvCjoWHhEAEyMUAAWMBKyAF6GEQFiklCoINBwqITRsfGIRdwhdBz+ERF5BbK4yakaGYQAjDn5hSXhonYRjXEJCSnq6QSEAMwTfdOCNkA)

### 💻 Code

Compiling this code with

`./node_modules/.bin/tsc --target ESNext x.ts`



```ts
function writeVal(a: number, b: any): number {
    console.log(‘writeVal’, a, b);
    return a;
}
class TestClass {
    a: number;
    public b = writeVal(2, this.z);    
    constructor(public z: number) {
        this.a = writeVal(1, this.z);
    }
    public c = writeVal(3, this.z);
}
```

I get the following error:

```
x.ts:7:33 - error TS2729: Property ‘z’ is used before its initialization.

7     public b = writeVal(2, this.z);
                                  ~

  x.ts:8:17
    8     constructor(public z: number) {
                      ~~~~~~~~~~~~~~~~
    ‘z’ is declared here.

x.ts:11:33 - error TS2729: Property ‘z’ is used before its initialization.

11     public c = writeVal(3, this.z);
                                   ~

  x.ts:8:17
    8     constructor(public z: number) {
                      ~~~~~~~~~~~~~~~~
    ‘z’ is declared here.


Found 2 errors.
```
### 🙁 Actual behavior

Running the code above in the playground there is no error, but `tsc` throws errors and fails to compile.

### 🙂 Expected behavior

Playground and the compiler should produce the same errors.
Repository: pytorch
Issue: LazyTensor recomputes intermediate tensor in fragmented computation
Labels: triaged,LazyTensor_nvfuser_integration,module: lazy

## 🚀 Feature

Intermediate tensors are currently re-computed instead of re-used in fragmented computation. This could cause regression comparing to eager, which reuses tensor and avoids wasted re-computation. 

## Motivation

toy example below:
https://github.com/jjsjann123/ltc_examples/blob/main/custom_kernel_fragmentation/repro.py

Two causes of fragmentation are demonstrated in the example above:
1. Towards the end of forward graph, we run into in-compatible operations (loss function), which causes computational graph to fragment.
2. Our example above uses a custom cuda kernel, which could also cause LazyTensor fragmentation.

In the logged IR: https://github.com/jjsjann123/ltc_examples/blob/907d4a4ccec5925a478525e13c7638c77024583f/custom_kernel_fragmentation/file#L584-L652
We notice that aten::softmax is called on forward graph, as well as backward graph. This means the output of softmax is recomputed instead of reused.
Repository: pytorch
Issue: LazyTensor cuda fallback
Labels: triaged,LazyTensor_nvfuser_integration,module: lazy

## 🚀 Feature

We currently only have `xla` device to access LazyTensor. Since we are extending LazyTensor support to GPUs, it's not necessary to fallback on CPU when we run into LTC-incompatible operations while we can continue the execution on eager GPU  instead of copying everything back to CPU.

We can start marking `cuda_lazy` and `cpu_lazy` to differentiate tensors' residing device.
Repository: pytorch
Issue: LazyTensor support for fuser integration investigation
Labels: triaged,LazyTensor_nvfuser_integration,module: lazy

## 🚀 Feature

Opening this issue to track requests:

- [ ] intermediate tensor reuse instead of re-computation #62614 
- [x] fp16 support #62440
- [ ] dynamic shapes #62675
- [ ] opaque operators with implicit shape
- [x] lowering rule for missing operations #62431
- [x] aten fallback on CUDA device instead of CPU #62616 
- [x] initialize cuda context  #65073