sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: Request for adding veo.co 
Labels: site-support-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 2021.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support 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 new site support request
- [X] I've verified that I'm running youtube-dl version **2021.06.06**
- [X] I've checked that all provided URLs are alive and playable in a browser
- [X] I've checked that none of provided URLs violate any copyrights
- [X] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://app.veo.co/matches/20201027-last-period/
- Single video: https://app.veo.co/matches/20200512-p06-bk-forward/
- 
## Description

Does not require authentication to view in a browser, just sharing the URL.
Repository: rust
Issue: Error message becomes worse when lifetime is elided via `'_`
Labels: A-diagnostics,A-lifetimes,T-compiler,D-newcomer-roadblock

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

```rust
fn bar(val: &'_ str) {
    let a: &'static str = val;
}
```

The current output is:

```
error[E0621]: explicit lifetime required in the type of `val`
 --> src/lib.rs:2:27
  |
2 |     let a: &'static str = val;
  |                           ^^^ lifetime `'static` required

error: aborting due to previous error
```

However, if we explicitly name the lifetime:

```rust
fn bar<'a>(val: &'a str) {
    let a: &'static str = val;
}
```

the error message is much better:

```
error[E0312]: lifetime of reference outlives lifetime of borrowed content...
 --> src/lib.rs:2:27
  |
2 |     let a: &'static str = val;
  |                           ^^^
  |
  = note: ...the reference is valid for the static lifetime...
note: ...but the borrowed content is only valid for the lifetime `'a` as defined on the function body at 1:8
 --> src/lib.rs:1:8
  |
1 | fn bar<'a>(val: &'a str) {
  |        ^^

error: aborting due to previous error
```

We should emit the same error message when the lifetime is elided (referring to it as 'this elided lifetime' or something similar).
Repository: pytorch
Issue: [clang-tidy] Add a custom rule for AT_ERROR -> TORCH_CHECK(false, ...)
Labels: triaged

Similar to #59682, we should have an automated way to check things like in https://github.com/pytorch/pytorch/pull/60976#discussion_r661872259

We can implement this as a custom clang tidy check in pytorch/test-infra
Repository: rust
Issue: rustdoc: align .stab to the right on desktop
Labels: T-rustdoc,A-rustdoc-ui

The informative tags/labels/stabs have been moved to the left column to improve the mobile experience.
Now the table feels a bit crammed.

* One possibility is to increase the gaps between the symbol and the tags.
* Another is to align the tags to the right on the desktop.

## Current nightly 2021-06-30

![image](https://user-images.githubusercontent.com/739070/124043946-bc0e3b00-d9fb-11eb-8d07-7aa542ce51b1.png)


## First draft for implementation

One possibility is something like this, but these rules result in stretched out:

![image](https://user-images.githubusercontent.com/739070/124043846-794c6300-d9fb-11eb-803b-e1542aa0aac7.png)

```css
.item-left {
    grid-column: 1;
    /* added */
    display: flex;
    justify-content: space-between;
    flex-flow: row wrap;
    width: 100%;
}
```

Based on: #86725 #86594
CC: @GuillaumeGomez
Repository: storybook
Issue: Numeric literals don't work properly with defaultValue
Labels: bug,help wanted,args

**Describe the bug**
Numeric literals don't work with a `number` `defaultValue` on first load.
I believe this is related to the change to deprecate `argTypes.defaultValue`, but I believe the code in the repro should work as-is. It does work when passing a `string` as a `defaultValue`, even if the type is a numeric literal.

**To Reproduce**
https://github.com/ajosedev/sb-default-value-numeric-repro

**System**

```
Environment Info:

  System:
    OS: macOS 11.4
    CPU: (8) x64 Intel(R) Core(TM) i7-8569U CPU @ 2.80GHz
  Binaries:
    Node: 14.16.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.11 - /usr/local/bin/npm
  Browsers:
    Chrome: 91.0.4472.114
    Firefox: 89.0
    Safari: 14.1.1
```

**Additional context**
I'm unsure if this is a problem with Storybook as it only started happening when upgrading from `6.1.20`, or if it's in the underlying docgen code.

The behaviour only seems to happen on a refresh of the page. Meaning that if you navigate to the page from another story, the `defaultValue` will work even if it's a `number`.

Also of note, you can see the console log for `argTypes.sizeAsNumber.options` is an array of strings.

Let me know if I've set up the repro correctly, haven't done many of these :pray:
Repository: flutter
Issue: [DataTable]: Checkbox doesn't have a FixedWidth
Labels: framework,f: material design,a: quality,has reproducible steps,found in release: 2.2,found in release: 2.3,team-design,triaged-design

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Steps to Reproduce

<!-- You must include full steps to reproduce so that we can reproduce the problem. -->

I've reproduced it in Dart Pad. The first is using a `DataTable`. The one below that uses a `Table` to mimic the behaviour. The `DataTable`'s Checkbox column should remain as Fixed Width like the `Table` Example. 

[Dart Pad](https://dartpad.dev/2216a787b08c715a5d41cf5ca05c253b?null_safety=true)

**Expected results:** <!-- what did you want to see? -->

The checkbox column should have a FixedWidth like the second table in DartPad

**Actual results:** <!-- what did you see? -->

The checkbox column has variable width like the first table in DartPad
Repository: godot
Issue: Shadow rendering is broken in GLES3 when using materials with cull mode set to Disabled
Labels: bug,topic:rendering,topic:3d

### Godot version

3.3.2

### System information

Windows 10

### Issue description

When cull_disable is used in render mode of shader in order to show the back face of geometry, this shadow glitch appears when a directional light is perpendicular to a face. It only happens in GLES3 not in GLES2.

First part of the video without render_mode cull_disable, then with:

https://user-images.githubusercontent.com/24277634/124073221-3fd62080-da18-11eb-80a8-219c7f63939e.mp4



### Steps to reproduce

Add a directional light perpendicular to a side of any geometry.  Rotate the light to better appreciate the problem.
Add a shader to geometry material and include:
shader_type spatial;
render_mode cull_disabled;

### Minimal reproduction project

[GodotGlitchShadow.zip](https://github.com/godotengine/godot/files/6745786/GodotGlitchShadow.zip)
Repository: TypeScript
Issue: Check truthy/falsy-ness for non-primitives to identify unreachable code
Labels: Suggestion,Awaiting More Feedback,Experimentation Needed

# Suggestion

In some cases TypeScript can identify unreachable code and throws an error:

```ts
const isTrue = true;
if (isTrue === false) {
  console.log('Can never be reached.')
}
```

In other cases it is currently not possible, but it would be very helpful. (Maybe even with a suggestion what _could_ have been meant - see array example.)

```ts
const isArray = ['hello'];
if (!isArray) {
  console.log('Can never be reached. You probably meant `if (!isArray.length) {`.')
}

const isObject = {};
if (!isObject) {
  console.log('Can never be reached.')
}
```

## 🔍 Search Terms

- reachable / unreachable
- dead code
- condition
- falsy / truthy
- primitive / non-primitive
- always

## ✅ Viability Checklist

<!--
   Suggestions that don't meet all these criteria are very, very unlikely to be accepted.
   We always recommend reviewing the TypeScript design goals before investing time writing
   a proposal for ideas outside the scope of the project.
-->
My suggestion meets these guidelines:

* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code -> It _can_ break code, but only to show potential bugs.
* [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, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

Throw errors on unreachable code examples.

```
const isArray = ['hello'];
if (!isArray) { // error: This condition will always return false. Did you meant to check `isArray.length`?
  console.log('Can never be reached. You probably meant `if (!isArray.length) {`.')
}

const isObject = {};
if (!isObject) { // error: This condition will always return false.
  console.log('Can never be reached.')
}

// OR:
if (isArray) {
} else {
  console.log('Can never be reached. You probably meant `if (!isArray.length) {`.')
}
```

## 📃 Motivating Example

This week I saw a colleague which could have found a bug way sooner by introducing such a check. ❤️ 

## 💻 Use Cases

Finding bugs.
Repository: PowerToys
Issue: [PowerRename] Undo.
Labels: Idea-Enhancement,Product-PowerRename

### Description of the new feature / enhancement

PowerRename really needs an undo function. 



### Scenario when this would be used?

An undo function would be useful in all cases but especially when multiple files or folders are renamed in error.

### Supporting information

This is a standard feature in, for example, [JoeJoe's Rename Master](https://www.joejoesoft.com/vcms/108/).

JoeJoe's Rename Master is the benchmark tool against we can measure the usefulness of PowerRename generally. Where PowerRename might outshine Rename Master is in keeping the UI simple. But not so simple as to exclude an undo feature. (e.g. shown to the user a simple [Undo] button).
Repository: deno
Issue: `/webstorage/storage_local_setitem_quotaexceedederr.window.html` WPT runs for half a minute
Labels: tests

I assume there is some optimization potential in our localstorage implementation.
Repository: vscode
Issue: Copy&Paste Police: AccessibilityHelpWidget
Labels: debt,editor-contrib

```
Clone found (typescript):
 - src/vs/editor/standalone/browser/accessibilityHelp/accessibilityHelp.ts [166:4 - 224:6] (58 lines, 439 tokens)
   src/vs/workbench/contrib/codeEditor/browser/accessibility/accessibility.ts [132:49 - 189:4]
```

Looks like one `AccessibilityHelpWidget` could extend the other `AccessibilityHelpWidget`
Repository: vscode
Issue: Support using option key on MacOS for Escape-Codes
Labels: help wanted,feature-request,upstream,macos,upstream-issue-linked,terminal-input

<!-- ⚠️⚠️ 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. -->

Since there is `"terminal.integrated.macOptionIsMeta"`, I would like to request the possibility to use the `option` key on MacOS for Escape-Codes, like in iTerm2:

![image](https://user-images.githubusercontent.com/85173861/124117961-0c73b000-da71-11eb-9157-17253a8bb16c.png)

I have a lot of ZSH widgets bound to `opt+X` shortcuts, that don't work in the integrated terminal as long as this feature is not supported.
Repository: PowerToys
Issue: [PowerToys Run - Editor]: Text and icon present under Search Launcher window does not adapt properly on 225% resize mode
Labels: Issue-Bug,Product-PowerToys Run,Area-Accessibility,A11yE+D,A11ySev3,A11yWCAG

### Microsoft PowerToys version

0.41.3

### Running as admin

- [X] Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

**Test Environment:**
OS: Windows 10 Version Dev
App version: 0.41.3
App name: PowerToys
Screen Reader: Narrator
Tool: Accessibility Insight for Windows

**Pre-requisites:**

Open Settings and then Navigate inside 'Accessibility' tab.
In side Display tab, Apply 225% resize.

**Repro Steps:**

1. Launch 'PowerToys' application.
2. Navigate to 'PowerToy Run' tab.
3. Then Open 'PowerToy Run' using defined Shortcut key.
4. Search anything like "WordPad" and Observe the issue.

**User Impact: -> Priority 2**
Low Vision user are impacted here as they will not able to know the full text as its get cropped.

**Guidelines Reference:**
https://www.w3.org/WAI/WCAG21/Understanding/resize-text

![225% resize mode](https://user-images.githubusercontent.com/86594814/124143833-12858300-daa9-11eb-9216-10dc5f3a55dd.png)


### ✔️ Expected Behavior

Search Launcher window should adapt 225% resize mode

### ❌ Actual Behavior

Search Launcher window does not adapt 225% resize mode

### Other Software

_No response_
Repository: node
Issue: Mac M1 (ARM) Elasticsearch access via TLS connection is broken
Labels: tls,macos

<!--
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 output of `"$([Environment]::OSVersion | ForEach-Object VersionString) $(if ([Environment]::Is64BitOperatingSystem) { "x64" } else { "x86" })"` in PowerShell console (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**:  15
* **Platform**: Mac M1
* **Subsystem**: Elasticsearch over TLS

### What steps will reproduce the bug?
Try to connect to an Elasticsearch cluster that is configured with a valid SSL certificate 

<!--
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?
This failure is constant the connection will fail with the following error:

=============== Error start ==============================
node:_tls_common:333
      c.context.loadPKCS12(toBuf(pfx));
                ^
Error: Unable to load PFX certificate
    at Object.createSecureContext (node:_tls_common:333:17)
    at Object.connect (node:_tls_wrap:1614:48)
    at HttpsAgent.createConnection (node:https:137:22)
    at HttpsAgent.createSocket (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/agentkeepalive/lib/_http_agent.js:265:26)
    at HttpsAgent.createSocket (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/agentkeepalive/lib/agent.js:77:11)
    at HttpsAgent.addRequest (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/agentkeepalive/lib/_http_agent.js:239:10)
    at new ClientRequest (node:_http_client:309:16)
    at Object.request (node:https:333:10)
    at HttpConnector.request (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/elasticsearch/src/lib/connectors/http.js:182:23)
    at sendReqWithConnection (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/elasticsearch/src/lib/transport.js:263:35)
    at Object.utils.applyArgs (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/elasticsearch/src/lib/utils.js:188:19)
    at wrapper (/Users/xxxx/yyyy_projects/aaa-dev/zzzzz-service/node_modules/lodash/lodash.js:5255:19)
    at processTicksAndRejections (node:internal/process/task_queues:76:11) {
  code: 'ERR_CRYPTO_OPERATION_FAILED'
=============== Error end ===============================

### What is the expected behavior?
That the connection will succeed

<!--
If possible please provide textual output instead of screenshots.
-->

### What do you see instead?
See above error message.

<!--
If possible please provide textual output instead of screenshots.
-->

### Additional information

<!--
Tell us anything else you think we should know.
-->
Repository: flutter
Issue: Proposal to add built-in pagination option for future builder and stream builder
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

Need pagination option for future builder and steam builder.
Repository: transformers
Issue: Extractive summarization pipeline
Labels: Feature request

# 🚀 Feature request

An extractive summarization pipeline similar to the one for abstractive summarization. 

A central place for researchers to upload new models for others to use, without having to run the code from various git repo's. 

Currently, extractive summarization is the only safe choice for producing textual summaries in practices. Therefore, it seems relevant for Huggingface to include a pipeline for this task. 

This has previously been brought up here:  https://github.com/huggingface/transformers/issues/4332, but the issue remains closed which is unfortunate, as I think it would be a great feature. 

## Motivation

The current abstractive summarization pipeline is certainly very useful, and a great feature for all working on NLG tasks. 

However, given the significant problems with factual consistency in asbtractive summaries (see in example: https://arxiv.org/abs/2104.13346, https://arxiv.org/abs/2104.14839), abstractive summaries are still very risky to use in practice, as even the state of the art models are riddled with factual errors. 

Any thoughts on this? :)
Repository: create-react-app
Issue: 'React' is declared but its value is never read.ts(6133) 
Labels: stale

https://github.com/facebook/create-react-app/blob/64df135c29208f08a175c941a0e94d9a56d9e4af/packages/cra-template-typescript/template/src/App.test.tsx#L1

In React 17 you no longer need to import react when writing JSX
Repository: create-react-app
Issue: In React 17 you no longer need to import react when writing JSX
Labels: stale

https://github.com/facebook/create-react-app/blob/64df135c29208f08a175c941a0e94d9a56d9e4af/packages/cra-template-typescript/template/src/App.test.tsx#L1

In React 17 you no longer need to import react when writing JSX
Repository: vscode
Issue: Call stack decoration: consider using background color and not a decoration
Labels: feature-request,debug

Great points by @bpasero here https://github.com/microsoft/vscode/issues/124169#issuecomment-872219638
Repository: pytorch
Issue: flatten renames in place
Labels: triaged,module: named tensor

## 🐛 Bug

When using flatten with named tensor and a single dimension the input tensor gets renamed as well.

## To Reproduce

Steps to reproduce the behavior:

```
import torch

a = torch.rand(2, 3, names=("a", "b"))
a.flatten(["a"], "c")
print(a.names)
> ('c', 'b')
```

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

input tensor should remain unchanged

<!-- A clear and concise description of what you expected to happen. -->

## Environment

Collecting environment information...
PyTorch version: 1.10.0.dev20210621+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.2 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Clang version: Could not collect
CMake version: version 3.16.3
Libc version: glibc-2.31

Python version: 3.9.5 | packaged by conda-forge | (default, Jun 19 2021, 00:32:32)  [GCC 9.3.0] (64-bit runtime)
Python platform: Linux-5.4.0-77-generic-x86_64-with-glibc2.31
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] functorch==0.0.1a0+9d091e6
[pip3] numpy==1.20.3
[pip3] torch==1.10.0.dev20210621+cpu
[conda] functorch                 0.0.1a0+9d091e6          pypi_0    pypi
[conda] numpy                     1.20.3           py39hdbf815f_1    conda-forge
[conda] torch                     1.10.0.dev20210621+cpu          pypi_0    pypi
Repository: godot
Issue: Can't exit freelook mode properly when using the 2 Viewports (Alt) 3D editor configuration
Labels: bug,topic:editor,confirmed,usability,topic:3d

### Godot version

3.3.2

### System information

arch linux 64 bit

### Issue description

Pressing Shift + F got me into Freelook mode but can't exit this mode by pressing again  Shift + F. Godot stuck in Freelook mode. Also Pressing Escape or holding down the right mouse button is not working to exit freelook mode

### Steps to reproduce

Shift + F  

### Minimal reproduction project

2 viewports (alt) with other one is previewing camera
pressing shift + f  after focusing left viewport  gets into Freelook mode 
can not exit it and mouse cursor is disappeared
Repository: pytorch
Issue: Make copy_ use dispatcher
Labels: module: bootcamp,triaged

Right now `copy_` implementation is a large number of if statements, because of its double dispatch nature. Well, we natively have double dispatch, so this undoubtedly can be cleaned up a bit.