sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: Option for auto-deleting thumbnail file if embedding failed
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.
-->

I'm currently downloading a whole bunch of music from YouTube, and I want the best audio available. Also, if possible, I want to embed the thumbnail:
`youtube-dl -if "bestaudio" --extract-audio --embed-thumbnail --add-metadata "https://www.youtube.com/watch?v=..."`

But not every container supports cover art, so I very often get the following error message:
`ERROR: Only mp3 and m4a/mp4 are supported for thumbnail embedding for now.`

My issue is that because the thumbnail couldn't be merged, my downloads folder is completely filled up with these left-over thumbnail files, and manually deleting them can be quite a hassle. Is there a command-line argument  I can pass to automatically delete non-mergeable thumbnails?
Repository: transformers
Issue: Alphafold 2.0
Labels: New model

# 🌟 New model addition

It would be so amazing to have Alphafold model in huggingface. 😍
I don't know if there is any plan to add these kind of models to huggingface repo.

<!-- Important information -->
## Model description


## Open source status

* [x] the model implementation is available: ([github](https://github.com/deepmind/alphafold))
* [] the model weights are available: ([github](https://github.com/deepmind/alphafold))
* [x] who are the authors: (@deepmind)
Repository: terminal
Issue: [19H1/19H2] Directory\Background doesn't work in non-en-US?
Labels: Issue-Bug,Needs-Attention,Product-Terminal,Priority-3,Area-ShellExtension

### Windows Terminal version (or Windows build number)

10.0.18363.1256，1.9.1942.0

### Other Software

_No response_

### Steps to reproduce


In the current file directory, the right-click shortcut cannot open wt

1. Nothing happens when the software is opened in the blank space of the current directory, but it is normal to open the software on the desktop and in the folder.
![GIF 2021-7-17 16-25-20](https://user-images.githubusercontent.com/49548316/126031147-1c95acf6-22e6-45e1-a10b-ddb95e9d28cc.gif)

2. In the case of `shift + right click`, wt can’t be opened either .Cmd and powershell can run normally under the same conditions
![GIF 2021-7-17 17-00-21](https://user-images.githubusercontent.com/49548316/126032043-42221e24-e223-4d72-b140-7683e6fd688f.gif)

3. Right-click on the desktop, you can execute wt
![GIF 2021-7-17 16-53-23](https://user-images.githubusercontent.com/49548316/126031843-1a1843fa-8d50-4470-b142-bce183f1cccf.gif)

By the way, I am not sure if it is caused by incorrect registry information. I want to modify, but I don’t know how to start


### Expected Behavior

_No response_

### Actual Behavior

the right-click shortcut cannot open wt
Repository: flutter
Issue: Support for custom entry point for fl_engine on Linux 
Labels: c: new feature,engine,platform-linux,c: proposal,a: desktop,P3,team-linux,triaged-linux

<!-- 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
-->

## Use case

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->
The basic Flutter API supports running engine from a custom Dart entry point, this is implemented in the `FlutterProjectArgs` structure ([custom_dart_entrypoint](https://github.com/flutter/engine/blob/master/shell/platform/embedder/embedder.h#L1472)). 

Android, Windows, macOS, and iOS implement this capability in the platform API. For example, Windows has a [FlutterWindowsEngine::RunWithEntrypoint](https://github.com/flutter/engine/blob/master/shell/platform/windows/flutter_windows_engine.h#L53) method. Android has a [DartExecutor](https://github.com/flutter/engine/blob/master/shell/platform/android/io/flutter/embedding/engine/dart/DartExecutor.java) class that allows you to run the Flutter Engine using a custom callback dispatcher as an entry point. 

The presence of this feature made it possible to implement the [workmanager](https://pub.dev/packages/workmanager) package, which allows executing Dart code in the background, in a duplicated main Isolate. Without the ability to set a custom entry point, it's impossible to implement this feature in Linux. 

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Add a new `fl_engine_start_with_entrypoint()` method to [fl_engine](https://github.com/flutter/engine/blob/master/shell/platform/linux/fl_engine.cc), or add the `dart_entrypoint` field to the [_FlDartProject](https://github.com/flutter/engine/blob/master/shell/platform/linux/fl_dart_project.cc) structure and the corresponding `fl_dart_project_set_dart_entrypoint()` method.

I think that the implementation will not be difficult, because it's enough to pass the entry point argument to `FlutterProjectArgs` structure.
Repository: rust
Issue: Confusing error: Immutable reference to future is not a future
Labels: A-diagnostics,E-mentor,T-compiler,E-help-wanted,A-async-await,AsyncAwait-Triaged,D-papercut,D-newcomer-roadblock

Given the following code:

```rust
async fn my_async_fn() {}

async fn foo() {
    tokio::select! {
        _ = &my_async_fn() => {},
    }
}
```
[playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=b7adade3c7dd34b220454c8c4a3b5fc8)

The current output is:

```
error[E0599]: no method named `poll` found for struct `Pin<&mut &impl Future>` in the current scope
 --> src/lib.rs:5:5
  |
5 | /     tokio::select! {
6 | |         _ = &my_async_fn() => {}
7 | |     }
  | |_____^ method not found in `Pin<&mut &impl Future>`
  |
  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
```

---

Given the following code:
```rust
async fn my_async_fn() {}

async fn foo() {
    let fut = &my_async_fn();
    tokio::pin!(fut);
    
    fut.await;
}
```
[playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=78cfe7a15e3cbd16ae65d7918743050c)

The current output is:
```
error[E0277]: `&impl Future` is not a future
 --> src/lib.rs:8:5
  |
8 |     fut.await;
  |     ^^^^^^^^^ `&impl Future` is not a future
  |
  = help: the trait `Future` is not implemented for `&impl Future`
  = note: required because of the requirements on the impl of `Future` for `Pin<&mut &impl Future>`
  = note: required by `poll`
```

---

Given the following code:
```rust
async fn my_async_fn() {}

async fn foo() {
    let fut = &my_async_fn();
    
    fut.await;
}
```
[playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=e388bf1a28851e5f3ef57dbaef113ff0)

The current output is:
```
error[E0277]: `&impl Future` is not a future
 --> src/lib.rs:7:5
  |
7 |     fut.await;
  |     ^^^^^^^^^ `&impl Future` is not a future
  |
  = help: the trait `Future` is not implemented for `&impl Future`
  = note: required by `poll`
```

In all three cases, it would be very helpful if the compiler could explicitly call out that an immutable reference to a future is not a future. I see this relatively often in the Tokio discord where people put some extra ampersands in random places and get really confused when the error says "impl future is not future". The ampersand in the error is not enough to clue them in to what the issue is. Especially for the first case.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"rahul-ar"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: godot
Issue: Switching ttys on Linux freezes Godot
Labels: bug,platform:linuxbsd,topic:rendering,confirmed

### Godot version

v4.0.dev.custom_build [60add98a4]

### System information

Linux manjaro 5.12.16-1-MANJARO x86_64 GNU/Linux

### Issue description

Godot freezes when switching tty. This means it needs to be killed.

### Steps to reproduce

1. Open Godot.
2. Switch to another tty.
3. Switch back to the tty with Godot.
4. Godot is now frozen.

### Minimal reproduction project

_No response_
Repository: youtube-dl
Issue: [Request] Site Support Request For Thegay.com (jwplayer based)
Labels: site-support-request


## Checklist

- [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

- Single video: https://thegay.com/videos/754188/nice-bi-for-my-friends/
- Single video: https://thegay.com/videos/754188/nice-bi-for-my-friends/?fr=754188&rp=10


## Description
Site using jwplayer that seems easy enough, but have not been able to get downloads working correctly so far.
Repository: vscode
Issue: [folding] Allow to fold all method bodies
Labels: feature-request,editor-folding

<!-- ⚠️⚠️ 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. -->

When reading the code, it's very useful to fold function and method bodies: this gives you a quick outline of the file, with the ability to easily drill down specific function if you want to. It would be useful to have a "Fold all bodies" action to achieve that, similarly to how we already have "fold all block comments" and "fold all regions". 

To give a specific example:

Unfolded:

![image](https://user-images.githubusercontent.com/1711539/126037439-93d4c392-c3cc-4de0-a43b-27169cbb1bc0.png)

Bodies folded:

![image](https://user-images.githubusercontent.com/1711539/126037458-53ac8960-50f0-4d1d-adb5-164205f7dd1b.png)

Not that this can't be achieved "fold level 2", as not all bodies are at level 2, and not everything that is at level two is a function body. 

API wise, it seems rather straightforward -- just add a "body" fold kind, and then let the language servers fill that out.
Repository: flutter
Issue: Add shape property to ExpansionTile
Labels: c: new feature,framework,f: material design,c: proposal,team-design,triaged-design

## Use case

When you currently put a `ExpansionTile` inside a `Card` the splash effect doesn't respect the borderRadius of the `Card`.

Example: 
![example_border_radius](https://user-images.githubusercontent.com/33162310/126038378-48c8c9b0-723c-400d-bf33-d3f3794cd111.jpg)


## Proposal

Add the property `ShapeBorder? shape` to `ExpansionTile` and pass it along to the underlying `ListTile`.
Repository: react
Issue: React 18 let's make ref.currant to be reactive value
Labels: Type: Discussion,React 18

Let's add this hook as part of the core. Since this is a common need, many people often ask the question "Why does useEffect not sense ref.current changes?"

```js
// approximate implementation
const useReactiveRef = (defaultValue) => {
  const [current, ref] = useState(defaultValue)
  ref.current = current
  return ref
}
```

Usage example:
```js
const Component = () => {
  const ref = React.useReactiveRef()

  useEffect(() => {
    // ref.current now is reactive
    console.log(ref.current)
  }, [ref.current])

  return <div ref={ref}></div>
}
```
Repository: rust
Issue: Include function signature hash in v0 mangled names
Labels: A-linkage,T-compiler

Currently v0 mangled names don't change when the function abi changes unlike legacy symbol names. This makes it easy to use a rust dynamic library with an incompatible abi at runtime when trying to update rust dynamic libraries the same way as C dynamic libraries for example by a distro either by using an incompatible source or an incompatible rustc version. This may work out fine, but it may also cause crashes or exploitable bugs. There is a test for this, but for some reason it is forced to the legacy symbol mangling scheme only and marked as possibly removable once the legacy scheme gets removed.

https://github.com/rust-lang/rust/blob/c78ebb7bdcfc924a20fd069891ffe1364d6814e7/src/test/run-make-fulldeps/a-b-a-linker-guard/Makefile#L7-L8

https://github.com/rust-lang/rust/blob/c78ebb7bdcfc924a20fd069891ffe1364d6814e7/compiler/rustc_symbol_mangling/src/legacy.rs#L118-L123

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"pierwill"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: rust
Issue: Pretty-printing of `Fn*` traits in diagnostics leaks unstable details
Labels: A-diagnostics,T-compiler


```rust
fn f(_: impl Fn(i32, i32) -> i32) {}
fn g() { f(0) }
```

The current output is:

```
error[E0277]: expected a `Fn<(i32, i32)>` closure, found `{integer}`
 --> <source>:2:12
  |
1 | fn f(_: impl Fn(i32, i32) -> i32) {}
  |              ------------------- required by this bound in `f`
2 | fn g() { f(0) }
  |            ^ expected an `Fn<(i32, i32)>` closure, found `{integer}`
  |
  = help: the trait `Fn<(i32, i32)>` is not implemented for `{integer}`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0277`.
Compiler returned: 1
```

<!-- The following is not always necessary. -->
Ideally the output should look like:

Same as above, but `Fn<(i32, i32)>` should be `Fn(i32, i32) -> i32`.

Compare with a fnptr instead of a closure:
```
error[E0308]: mismatched types
 --> <source>:3:13
  |
3 | fn g() { f2(0) }
  |             ^ expected fn pointer, found `usize`
  |
  = note: expected fn pointer `fn(i32, i32) -> i32`
                   found type `usize`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
Compiler returned: 1
```

Seems like it would be straightforward to special case `core::ops::Fn*` et. al., especially since they're lang items. Clearly we already do, since rustc suggests that it should be a closure.
Repository: vscode
Issue: Allow exact and excluded matches in fuzzy search
Labels: feature-request,search,quick-open

<!-- ⚠️⚠️ 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. -->
In fuzzy searches, allow you to require an exact match by using double quotes and exclude terms using a minus sign.  Here are some examples:
- `"abc"` would match `abc`, but not `abac`
- `abc -def` would match `abc`, but not `abcdef`.
Repository: godot
Issue: Vulkan: LightmapGI Environment Min Light property not implemented (unlike BakedLightmap in `3.x`)
Labels: enhancement,topic:rendering,topic:3d

See also https://github.com/godotengine/godot/issues/49935 and https://github.com/godotengine/godot/issues/49968.

### Godot version

4.0.dev (8747f2565)

### System information

Fedora 34, GeForce GTX 1080 (NVIDIA 465.31)

### Issue description

In the `master` branch, baked lightmaps cannot have their darkest areas brightened to match a specific color. This is [available in `3.x`](https://github.com/godotengine/godot/pull/46932) as the **Min Light** property in the Environment section, which works by `max()`ing the resulting color in the lightmap (instead of adding to the lightmap, which would result in brightening it everywhere).

Min Light is not physically accurate, but it can be used to avoid overly dark areas in levels. Of course, it should be set to a relatively low value to avoid making lightmaps too dull.


### Steps to reproduce

Look for a `environment_min_light` property in the `master` branch's LightmapGI node.

### Minimal reproduction project

N/A
Repository: godot
Issue: Vulkan: LightmapGI Use Color property not implemented (unlike BakedLightmap in `3.x`)
Labels: enhancement,topic:rendering,topic:3d

See also https://github.com/godotengine/godot/issues/50570.

### Godot version

4.0.dev (8747f2565)

### System information

Fedora 34, GeForce GTX 1080 (NVIDIA 465.31)

### Issue description

LightmapGI doesn't have a `use_color` property, unlike [BakedLightmap in `3.x`](https://github.com/godotengine/godot/pull/46054). This can be used to decrease the file size of the generated lightmap, which can be important when exporting to mobile and web platforms. The difference between grayscale and colored lightmaps is sometimes only barely noticeable when baking indirect lighting only, so it may not be much of a visual tradeoff.

See https://github.com/godotengine/godot-proposals/issues/2142.

### Steps to reproduce

Look for a `use_color` property in the `master` branch's LightmapGI node.

### Minimal reproduction project

N/A
Repository: godot
Issue: Vulkan: LightmapGI Use Hdr property not implemented (unlike BakedLightmap in `3.x`)
Labels: enhancement,topic:rendering,topic:3d

See also https://github.com/godotengine/godot/issues/50569.

### Godot version

4.0.dev (8747f2565)

### System information

Fedora 34, GeForce GTX 1080 (NVIDIA 465.31)

### Issue description

LightmapGI doesn't have a `use_hdr` property, unlike [BakedLightmap in `3.x`](https://github.com/godotengine/godot/pull/46054). This can be used to decrease the file size of the generated lightmap, which can be important when exporting to mobile and web platforms. The difference between HDR and LDR lightmaps is sometimes only barely noticeable when baking indirect lighting only, so it may not be much of a visual tradeoff.

See https://github.com/godotengine/godot-proposals/issues/2142.


### Steps to reproduce

Look for a `use_hdr` property in the `master` branch's LightmapGI node.

### Minimal reproduction project

N/A
Repository: rust
Issue: Unreachable code warning missing at if expression with false condition
Labels: A-lints,A-diagnostics,T-compiler,L-unreachable_code

Given the following code: https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=6526368602dd7742a2bd1d988fe03f66

```rust
let a: u32 = 3;
if a < a {
    panic!();
}
    
if 3 > 3 {
    panic!(); 
}

if false {
    panic!();
}
```

The current output is: nothing
Can be reproduced on versions 1.55-nightly and 1.53.

Ideally this code should trigger the `unreachable_code` lint at least in the case when an integer variable is compared with itself, to prevent mistakes such as typos.
AFAIK, this code is eliminated when optimizations are turned on, so the warning should follow along.

I'm not sure if the case when the conditional expression is exactly `false` should be considered a warning, since it is probably not a mistake.

@rustbot modify labels: +A-lint
Repository: rust
Issue: Inferred struct lifetime bounds result in bad diagnostics around HRTBs
Labels: A-diagnostics,A-lifetimes,A-closures,A-borrow-checker,T-compiler,D-confusing,D-newcomer-roadblock,A-higher-ranked

Given the following code: https://godbolt.org/z/he33YcxPM

```rust
struct C<'a, 'b>(&'a &'b ());

fn foo<'a>(f: impl FnOnce(&mut C<'_, 'a>)) {}
fn bar<'a>(f: impl FnOnce(&mut C<'_, 'a>)) {
    foo(|x: &mut C<'_, 'a>| f(x))
}
```

The current output is the default borrow check diagnostic.

```
error[E0495]: cannot infer an appropriate lifetime for lifetime parameter in generic type due to conflicting requirements
 --> <source>:5:29
  |
5 |     foo(|x: &mut C<'_, 'a>| f(x))
  |                             ^^^^
  |
note: first, the lifetime cannot outlive the lifetime `'a` as defined on the function body at 4:8...
 --> <source>:4:8
  |
4 | fn bar<'a>(f: impl FnOnce(&mut C<'_, 'a>)) {
  |        ^^
note: ...so that the declared lifetime parameter bounds are satisfied
 --> <source>:5:29
  |
5 |     foo(|x: &mut C<'_, 'a>| f(x))
  |                             ^^^^
note: but, the lifetime must be valid for the anonymous lifetime #2 defined on the body at 5:9...
 --> <source>:5:9
  |
5 |     foo(|x: &mut C<'_, 'a>| f(x))
  |         ^^^^^^^^^^^^^^^^^^^^^^^^
note: ...so that the expression is assignable
 --> <source>:5:31
  |
5 |     foo(|x: &mut C<'_, 'a>| f(x))
  |                               ^
  = note: expected `&mut C<'_, 'a>`
             found `&mut C<'_, '_>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0495`.
Compiler returned: 1
```

This code can be made to compile (ht @Manishearth) by observing that the compiler infers `'b: 'a` for `C<'a, 'b>`:

```rust
struct C<'a, 'b>(&'a &'b ());

fn foo<'b, 'a: 'b>(f: impl FnOnce(&mut C<'b, 'a>)) {}
fn bar<'b, 'a: 'b>(f: impl FnOnce(&mut C<'b, 'a>)) {
    foo(|x: &mut C<'b, 'a>| f(x))
}
```

It would be useful for rustc to suggest this fix, but it looks a bit hard to find. Either way, this one puzzled me for several hours until I poked Manish.

It is unclear if this is a bug, but it seems incorrect for rustc to accept the original code for borrow check at all, since `x` types at `for<'1, '2> C<'1, '2>` in the closure argument, not `for<'1> C<'1, 'a>`, as the user has written. In particular, the following compiles, but should probably be rejected:

```rust
struct C<'a, 'b>(&'a &'b ());

fn foo<'a>(f: impl FnOnce(&mut C<'_, 'a>)) {}
fn bar<'a>(f: impl FnOnce(&mut C<'_, 'a>)) {
    foo(|x: &mut C<'_, 'a>| {})
}
```