sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: ERROR: Unsupported URL:
Labels: 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.
-->

WRITE QUESTION HERE

Dears,

i am using YouTube-dll for a while but can't use it for the domain "https://online.watchandknow.cz". I have made the free registration, however even with using the parameters -u -p and filling out the desired URL , it fails.

Thanks 

BR,
ASD
Repository: ant-design
Issue: Filter treeNodes in Tree component on search
Labels: help wanted,💡 Feature Request,Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
I'm using a searchable Tree component. I would like to be able to filter treeNodes on search, so that matched treeNodes are shown, and unmatched ones are hidden. There is a `filterTreeNode` prop in API, but it doesn't do anything. At least I couldn't get it to work, you can see my [codesandbox](https://codesandbox.io/s/antd-tree-search-filter-lrv89?file=/index.js:0-3079).

### What does the proposed API look like?
The API should be similar to `filterTreeNode` in TreeSelect as explained here #19997.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: C++ API: Training and inference of torchscript modules on multiple GPU
Labels: oncall: jit

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->
At the moment, `torch::nn::parallel::data_parallel` (in file [data_parallel.h](https://github.com/pytorch/pytorch/blob/master/torch/csrc/api/include/torch/nn/parallel/data_parallel.h) ) only works with native torch modules and cannot handle modules traced with torch.jit. 

Is there any plan to support it in the future? Are there technical limitations explaining why this is not implemented yet?


cc @gmagogsfm
Repository: storybook
Issue: De-dupe glob resolutions before passing to webpack
Labels: configuration babel / webpack,performance issue

_Originally posted by @ndelangen in https://github.com/storybookjs/storybook/issues/3968#issuecomment-709998495_

> Interesting @felipenmoura . So the idea is that when you have multiple globs that resolve to the same story, some race condition is triggered that blows up the startup time?

I'm hoping that in the future, we don't rely on webpack's require.context at all anymore, and we resolve the globs (and can de-dup them) in node before starting webpack.

Sounds that might resolve that issue @shilman ?

> @ndelangen that it would. it might also help with #12771 ?
Repository: opencv
Issue: SVD::compute(E, D, U, Vt);it dont make E = U diag(1,1,0) V
Labels: incomplete

##### System information (version)
<!-- Example
- OpenCV => 4.2
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017
-->

- OpenCV => :grey_question:
- Operating System / Platform => :grey_question:
- Compiler => :grey_question:

##### Detailed description

<!-- your description -->

##### Steps to reproduce

<!-- to add code example fence it with triple backticks and optional file extension
    ```.cpp
    // C++ code example
    ```
 or attach as .txt or .zip file
-->

##### Issue submission checklist

 - [ ] I report the issue, it's not a question
   <!--
   OpenCV team works with answers.opencv.org, Stack Overflow and other communities
   to discuss problems. Tickets with question without real issue statement will be
   closed.
   -->
 - [ ] I checked the problem with documentation, FAQ, open issues,
       answers.opencv.org, Stack Overflow, etc and have not found solution
   <!--
   Places to check:
   * OpenCV documentation: https://docs.opencv.org
   * FAQ page: https://github.com/opencv/opencv/wiki/FAQ
   * OpenCV forum: https://answers.opencv.org
   * OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
   * Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
   -->
 - [ ] I updated to latest OpenCV version and the issue is still there
   <!--
   master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
   OpenCV team supports only latest release for each branch.
   The ticket is closed, if the problem is not reproduced with modern version.
   -->
 - [ ] There is reproducer code and related data files: videos, images, onnx, etc
   <!--
   The best reproducer -- test case for OpenCV that we can add to the library.
   Recommendations for media files and binary files:
   * Try to reproduce the issue with images and videos in opencv_extra repository
     to reduce attachment size
   * Use PNG for images, if you report some CV related bug, but not image reader
     issue
   * Attach the image as archive to the ticket, if you report some reader issue.
     Image hosting services compress images and it breaks the repro code.
   * Provide ONNX file for some public model or ONNX file with with random weights,
     if you report ONNX parsing or handling issue. Architecture details diagram
     from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
   -->in the function below
void cv::decomposeEssentialMat( InputArray _E, OutputArray _R1, OutputArray _R2, OutputArray _t )
{
    Mat E = _E.getMat().reshape(1, 3);
    CV_Assert(E.cols == 3 && E.rows == 3);

    Mat D, U, Vt;
    SVD::compute(E, D, U, Vt);
..........

SVD::compute(E, D, U, Vt);    it dont make E = U diag(1,1,0) V,it can be anything between the  U and V, is it still right for    R , T?
Repository: pytorch
Issue: [META] Assert that expected libraries appear in libtorch
Labels: triaged,module: static linking,enhancement

## 🚀 Feature

We should create an expected list of files to appear in libtorch to test that libtorch was build correctly.

## Motivation

With #44257, we should expect that pytorch_jni libs appear in libtorch bundles on all platforms. This currently doesn't happen because of upstream cmake issues in fbjni.

## Pitch

To make sure that upstream issues don't silently cause issues in libtorch, we should create a post-build test which ensures that expected files appear in the bundle.

## Alternatives

Status quo.
Repository: neovim
Issue: add autocmd-event for setloclist/setqflist
Labels: enhancement,needs:vim-patch,events,quickfix

### Actual behaviour
There is only an event emitted before and after a command as run that Vim considers to be relevant for the quickfix or location list (e.g. `:grep`). But the lists can be set by basically everyone, causing no event the user could listen to.

### Expected behaviour
An event gets thrown when ever `setqflist` or `setloclist` got called.

---

Sorry if this was already discussed once. I was not able to find such conversation. 
I know there should not be an event for every rare use-case. But in fact this event(s) do already exist, just that they do not apply not for everything. Why emitting an event for specific commands only rather than make it more generic?
To finally make an example where this could be useful would be a status segment that highlights if and how much location lists entry exist. So there is no need to automatically open the location list (if such feature is provided), but the user can have a visual feedback if any asynchronous tool is adding location or quickfix list entries.
Thanks for any input!
Repository: pytorch
Issue: Advanced indexing: allow combining Boolean & integer index
Labels: triaged,module: numpy,module: advanced indexing,function request

## 🚀 Feature
In NumPy, this works:
```
>>> a = np.ones((2, 3, 4))
>>> b = np.ones((2, 3), dtype=bool)
>>> a[b, 2] = 1
```

In PyTorch (master branch), it doesn't:
```
>>> a = torch.ones(2, 3, 4)
>>> b = torch.ones(2, 3, dtype=bool)
>>> a[b, 2] = 1
IndexError: The shape of the mask [2, 3] at index 1 does not match the shape of the indexed tensor [2, 4] at index 1
```

It would be great if PyTorch allowed this kind of indexing, to make using PyTorch easier for newcomers familiar with NumPy, and to make this kind of indexing operation more concise.

cc @mruberry @rgommers @heitorschueroff
Repository: TypeScript
Issue: Variadic tuple inference does not work well with generics (e.g. currying array)
Labels: Needs Investigation

**TypeScript Version:**  4.1.0-dev.20201015 (also 4.0.3)

**Search Terms:** variadic tuples, generics, curry, inference

**Code**

```ts
function curry<T extends unknown[], U extends unknown[], R>(f: (...args: [...T, ...U]) => R, ...a: T) {
    return (...b: U) => f(...a, ...b);
}

function _map<T, U>(mapFn: (t: T) => U, array: Array<T>): Array<U> {
  return array.map(mapFn);
}

const map1 = curry(_map);
const map2 = curry(_map, (s: string) => s.length);
const map3 = curry(_map, (s: string) => s.length, ['a', 'bravo'])
```

**Expected behavior:**

- `map1` should resolve to the type `<T, U>(mapFn: (t: T) => U, array: Array<T>) => U`
- `map2` should resolve to the type `<T, U>(array: Array<T>) => U`

**Actual behavior:** 

- `map1` has `_map` unassignable to the first argument, with the error:

    > Argument of type '<T, U>(mapFn: (t: T) => U, array: T[]) => U[]' is not assignable to parameter of type '(...args: unknown[]) => unknown[]'.
    >   Types of parameters 'mapFn' and 'args' are incompatible.
    >     Type 'unknown' is not assignable to type '(t: unknown) => unknown'.

- `map2` has `_map` unassignable to the first argument, with the error:

    > Argument of type '<T, U>(mapFn: (t: T) => U, array: T[]) => U[]' is not assignable to parameter of type '(args_0: (s: string) => number, ...args_1: unknown[]) => number[]'.
    >   Types of parameters 'array' and 'args_1' are incompatible.
    >     Type 'unknown' is not assignable to type 'string[]'.

When inverting the order of `_map` to be data-first, map-function last, it has the same assignability issues ([playground](https://www.typescriptlang.org/play?ts=4.1.0-dev.20201015#code/GYVwdgxgLglg9mABBEAnVBPAPAFUQUwA8p8wATAZ0XAGsw4B3MAbQF0AaRAVQONMupg6jFh0QAlAHwAKYAC5E0gHQqAhqgDmFBcxVKcnPV1YBKRAF5JEw2oU4zAbwCwAKETvEqfFDRJlKgCMFLjNLRGB-JVUbJQCTAG5XAF9XV1BIWAREAH0AW1UABwAhVQgaBnVKXE4uGXVUVQwFAEF0RtxJTnyCgDEwBWkoO1CrEJa27FrEZzdPb19EesalbuluvoTk1JcIBAooRG6igEYLZDRMaTzCkrKK1EpNnb2Do4AmM5R0DCuj0vLKhROMxjpw3pwAMymRLPMD7Q43CGfC4-a7Ff73SjA0GIcGIKGcaRgEaIAAGABIHGAkqSnrs4a8bgAWZHfX43DGA7FgyFiIkKMAgXIBfCoEkUqk0hJAA)).

**Playground Link:** https://www.typescriptlang.org/play?ts=4.1.0-dev.20201015#code/GYVwdgxgLglg9mABBEAnVBPAPAFUQUwA8p8wATAZ0XAGsw4B3MAbQF0AaRAVQONMupg6jFh0QAlAHwAKYAC5E0gHQqAhqgDmFBcxVKcnPV1YBKRAF5JEw2oU4zAbwCwAKETvEqfFDRJlKgCMFLjNLRGB-JVUbJQCTAG5XAF9XV1BIWAREAH0AW1UAB1xOLhl8goAxMAVpKDtQqy5OdVRVDAUAQXQ23EkTTu7sUsRnN09vX0QWtqVy6XKqhOTUlwgECihEcoBGC2Q0TGk8wqXV9c3ygCY9lHQMI-LOaW1EDdQYMA0G16UAG1INFAABanNZgDZbQoAZhuB3uxwKTxebw+XwsVgofwBwM4zAA5Ko8Zw8QFWgA3OB40wrIA

**Related Issues:**

- #39713
- #39244
Repository: go
Issue: math/big: big.Int `fmt.Formatter` implementation should support `%q`
Labels: NeedsInvestigation

I suggest a small quality-of-life improvement to the `*big.Int` type to support printing as a quoted string. `*big.Int` implements `fmt.Formatter` and (contrary to the documentation) supports the `s` verb, printing the integer in decimal format. This allows you to do:

<pre>
fmt.Printf("My int: %s\n", big.NewInt(1))
</pre>

 However, it does not support `q`, which becomes surprising for people accustomed to the special formatting considerations for string formats wherein `q` is implicitly supported for types implementing `fmt.Stringer`. Instead you have to explicitly call the `String()` method:

<pre>
fmt.Printf("My quoted int: %q\n", big.NewInt(1).String())
</pre>

And if you forget?
https://play.golang.org/p/5YiBHW5djUM

I don't imagine there would be a big back-compat concern.

I'm happy to provide the code change if folks are on board.
Repository: TypeScript
Issue: Set esModuleInterop to "true" by default
Labels: Suggestion,In Discussion

## Search Terms

* esModuleInterop

## Suggestion

Change [`esModuleInterop`](https://www.typescriptlang.org/tsconfig#esModuleInterop) from being an opt-in to instead be an opt-out, taking one step further towards deprecating the non-`esModuleInterop` mode and make `esModuleInterop` the only supported mode going forward (which has to be the long term goal).

## Use Cases

When [Typescript 2.7 introduced](https://www.typescriptlang.org/docs/handbook/release-notes/typescript-2-7.html#support-for-import-d-from-cjs-from-commonjs-modules-with---esmoduleinterop) `esModuleInterop` almost 3 years ago it emphasized clearly that:

> We highly recommend applying it both to new and existing projects.

[`esModuleInterop`](https://www.typescriptlang.org/tsconfig#esModuleInterop) is also a _recommended_ option to set in `tsconfig.json` and when one runs `tsc --init` it gets set to `true` automatically.

However, the fact that it still is opt-in makes that non-`esModuleInterop` mode is still very prevalent, which kind of works against the very problems it was meant to fix – as rather than having just the pre-`esModuleInterop` functionality, modules now have to try to make things work across both options – and on top of that increasingly have to work with TS-validated JS.

All in all, that causes problems: https://github.com/fastify/env-schema/pull/17

And is hard to wrap ones head around: https://github.com/fox1t/modules-playground

Even if one really tries: https://github.com/fox1t/modules-playground/pull/3

## Checklist

My suggestion meets these guidelines:

* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
  * It would for all code which haven't yet adopted `esModuleInterop`, but it would make it easier to get TypeScript and JavaScript code to stay compatible with one another
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [ ] This could be implemented without emitting different JS based on the types of the expressions
  * It would emit different JS for all code which haven't yet adopted `esModuleInterop`, but it would make it easier to get TypeScript and JavaScript code to stay compatible with one another
* [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).
  * Apart from `Do not cause substantial breaking changes from TypeScript 1.0.`
Repository: vscode
Issue: Safari/iPadOS: UI affordance for non default cursor style
Labels: ux,under-discussion,safari,ios-ipados

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

On Desktop, we use `cursor: ` CSS rule a lot to change the mouse style for various purposes, but it's not availbale on iOS. However, we still get the `:hover` event when iOS is attached with an external mouse/trackpad. We need to go through all places we modify cursor style to ensure we have a proper fallback for iOS.

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
Repository: flutter
Issue: Linter: Undefined symbol GrDirectContext::MakeVulkan
Labels: team,engine,from: sanitizer,P2,team-engine,triaged-engine

In flutter/vulkan/vulkan_window.cc, the call to `GrDirectContext::MakeVulkan` is undefined when SK_VULKAN is not defined.

If clang-tidy supports runs with a `-D` or similar mechanism for  symbols, we could try running with that defined. Otherwise, we should disable linting immediately at the call site, for that line only.
Repository: flutter
Issue: Lint: undefined symbols {FLUTTER_ENGINE,SKIA,DART}_VERSION
Labels: team,engine,from: sanitizer,P2,team-engine,triaged-engine

In flutter/shell/version/version.cc, `FLUTTER_ENGINE_VERSION`, `SKIA_VERSION`, `DART_VERSION` are defined by the build rules in shell/version/BUILD.gn.

If clang-tidy supports defining symbols via an option like `-D`, we should do that.
Repository: angular
Issue: Expand size-tracking to include first-party Angular libraries
Labels: feature,area: dev-infra,P4

Currently the size tracking only captures holistic metrics (e.g. angular.io) and more granular example apps (hello world). We may want to track more granularly by building cases for:

- [ ] Hello world with forms
- [ ] Hello world with router
- [ ] Hello world with forms + router
- [ ] Hello world with forms + router + Angular Material

Replaces #21268,  #21269, #21270, #21271
Repository: TypeScript
Issue: TS auto-complete does not correctly understand parameter spread
Labels: Bug,Domain: Completion Lists

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.50.1
- OS Version: W10

**Steps to Reproduce**:

Using the following code:

```ts
type NamedRoutes =
  | ['products', { id: number }]
  | ['compare', { ids: number[] }];

function navigate(...params: NamedRoutes): void { }

navigate('compare', {  });
// auto-complete here ^
```

1. Move your cursor to the second parameter of the navigate function call inside the curly braces.
2. Invoke auto-complete (`ctrl`+`space`)
3. Both `id` and `ids` are suggested while `ids` is the only valid option (the other will generate a compiler error).

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

**Screenshot**:
![here](https://i.imgur.com/QWBNT1k.png)
Repository: node
Issue: fs: inconsistent options treatment between rm() and rmdir()
Labels: fs

<!--
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**: 14.14.0 and 15.0.0-pre (master branch)
* **Platform**: macOS
* **Subsystem**: fs

### What steps will reproduce the bug?

Use `/dev/null` as the path like below, or use some other path that will not be removed and force a retry.

This tries, doesn't remove `/dev/null`, and exits with "done" very quickly.

```console
$ node -e 'fs.rmdir("/dev/null", { maxRetries: 42 }, () => { console.log("done"); })'
```

So does this:

```console
$ node -e 'fs.rmdir("/dev/null", { maxRetries: 420 }, () => { console.log("done"); })'
```

This does the same:

```console
$ node -e 'fs.rm("/dev/null", { maxRetries: 1 }, () => { console.log("done"); })'
```

But this takes about 90 seconds to finish, presumably because it is respecting the `maxRetries` option (with a backoff, I imagine) whereas `fs.rmdir()` ignores it if `recursive` is not set:

```console
$ node -e 'fs.rm("/dev/null", { maxRetries: 42 }, () => { console.log("done"); })'
``` 

<!--
Enter details about your bug, preferably a simple code snippet that can be
run using `node` directly without installing third-party dependencies.
-->

### How often does it reproduce? Is there a required condition?

Reproduces every time.

### What is the expected behavior?

I would expect `fs.rm()` and `fs.rmdir()` to treat `maxRetries` the same.  

<!--
If possible please provide textual output instead of screenshots.
-->

### What do you see instead?

`fs.rm()` honors it with or without `recursive` being set, whereas `fs.rmdir()` ignores it unless `recursive` is set.

<!--
If possible please provide textual output instead of screenshots.
-->

### Additional information

<!--
Tell us anything else you think we should know.
-->
Repository: flutter
Issue: Use Fade transitions on Dialog, Snackbar, Menu etc. as per Material Design Spec
Labels: framework,a: animation,f: material design,c: proposal,team-design,triaged-design

## Use case

The Material Design Guidelines say that Dialogs, Snackbars, Menus and FloatingActionButtons should use the [Fade transition](https://material.io/design/motion/the-motion-system.html#fade)
I think [this video](https://kstatic.googleusercontent.com/files/4bf2ddbf50d779f37d88f276b831fad1aad78a23379a87d2b715dbb90d878897d1ad5edcf03385e1814d2ec3f4e9f152fd736ab2727d7f0e0d8b58467eb41057) from the specs is also very expressive.

Right now all the previously named components have their own outdated transitions that don't match the current spec. Especially the Menu / DropdownMenu animations look a bit unpolished.

## Proposal

Update the named widgets to use the official transitions as per material spec.