sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: yt-dlp
Issue: pyinstaller temp files are not cleaned up when using yt-dlp.exe with mpv
Labels: external issue

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm asking a question and **not** reporting a bug or requesting a feature
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar questions **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Please make sure the question is worded well enough to be understood

![temp](https://github.com/yt-dlp/yt-dlp/assets/76743591/0678952e-e622-4c74-97b2-927a86768c37)

as far as I understand the files in the %temp% folder generated by yt-dlp.exe are supposed to automatically delete themselves, however only some of them do and most remain on my pc taking up gigabytes of space

I think this happens most often when I'm running an mpv playlist as I haven't noticed them not being deleted when running a single streamed mpv video but I'm not entirely sure about that

what can I possibly do here? what could be the cause and what is the solution? I'm looking for a more in-depth explanation rather than just a workaround like creating a batch file to remove these files and running it on startup

UPDATE: after further observations I came to believe that this problem only occurs when I skip to the next video before current one ends its startup loading - perhaps the cleaning function gets stopped because of it?

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: ui
Issue: [bug]: DropdownMenuSub is not responsive on small devices.
Labels: bug

### Describe the bug

The DropdownMenuSub is not responsive on small devices. I believe the content should be centered or positioned in a way that it won't be hidden.

### Affected component/components

DropdownMenuSub

### How to reproduce

1. Increase DropdownMenuContent width. 

2. Resize the window to the size of the DropdownMenuContent.

3. Hover over/click(on mobile) DropdownMenuSub.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Browser: Mozilla Firefox Snap for Ubuntu
OS: Ubuntu 22.04
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: tauri
Issue: [bug] [v2] undo and redo shortcuts don't work in popular editor on MacOS
Labels: type: bug,platform: macOS,status: needs triage,scope: unstable flag

### Describe the bug

In tauri v2-beta, the undo and redo shortcuts don't work in popular editor on MacOS. (Focus the editor, then press enter key, then undo, you will see the bug without any error message.) 

I also test on windows 10,  they work fine. Then I test on MacOS with lastest tauri v1, they also work fine.

> ps: I notice this issue #9426, but it doesn't help for me. 

Here is the test demo.  https://github.com/percy507/test-tauri-v2/tree/undo-redo-donot-work-in-editor

```bash
# v2-beta on MacOS
textarea                works
contenteditable         works
the rest editors        doesn't work
```

<img width="467" alt="image" src="https://github.com/tauri-apps/tauri/assets/18365078/7fd02174-5099-4841-8f52-9ebbbc9024e4">

### Reproduction

https://github.com/percy507/test-tauri-v2/tree/undo-redo-donot-work-in-editor

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 13.2.1 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 20.7.0
    - pnpm: 8.3.1
    - yarn: 1.22.21
    - npm: 10.1.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.22
    - tauri-build [RUST]: 2.0.0-beta.17
    - wry [RUST]: 0.40.1
    - tao [RUST]: 0.28.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.13
    - @tauri-apps/cli [NPM]: 2.0.0-beta.20

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: React
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: vscode
Issue: add Peek to definition to focus on open files
Labels: feature-request,editor-symbols

<!-- ⚠️⚠️ 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. -->
Can vscode redirect me to another open window when I spliited a project open into 2 open windows. (same as move to new window functionality)
Precision: I open my project in a VS Code window, then open a new empty window not binded to a folder or project and just drag and drop desired files onto it.
Currently my "peek to definition" on a function or class will open the owner file of the class/function in another tab instead of focusing on an already open one in the other window ot even if the file is open in the side tab of the current window.

Thank you.
Repository: terminal
Issue: wt split-pane -D overwrites command line command with profile command
Labels: Issue-Bug,Product-Terminal,Area-Commandline

### Windows Terminal version

1.20.11381.0

### Windows build number

10.0.19045.0 

### Other Software

_No response_

### Steps to reproduce

Hello,

I made a function that is called to open 6 panes under Windows Terminal and which will connect automatically to several hosts.
I've done it thiw way because I was not able to find on the documentation a cleaner way. 

This script is working but I've found that the command split-pane : 
* With the parameter -H the following command is executed 
* With the parameter -D the following command **isn't** executed


**Working** 👍
```
wt.exe --maximized -p NoProfile pwsh -wd ~ -nop -noexit -command "connect $($Hosts[0])" ; split-pane -s .33 pwsh -nop -noexit -command "connect $($Hosts[2])" -D
wt.exe --maximized -p NoProfile pwsh -wd ~ -nop -noexit -command "connect $($Hosts[0])" ; split-pane -s .33 -H pwsh -nop -noexit -command "connect $($Hosts[2])
```

**Not working** 👎 
```
wt.exe --maximized -p NoProfile pwsh -wd ~ -nop -noexit -command "connect $($Hosts[0])" ; split-pane -s .33 -D pwsh -nop -noexit -command "connect $($Hosts[2])
```


My workaround like posted here is to move the parameter -D at the end of the command, this way it works.

```
if ($null -ne $Hosts) {
        # Open 6 panes with 6 servers
        wt.exe --maximized -p NoProfile pwsh -wd ~ -nop -noexit -command "connect $($Hosts[0])" `; `
        split-pane -s .33 pwsh -nop -noexit -command "connect $($Hosts[2])" -D `; move-focus first `; split-pane -s .5 pwsh -wd ~ -nop -noexit -command "connect $($Hosts[1])" -D `; `
        split-pane -s .5 -H pwsh -wd ~ -nop -noexit -command "connect $($Hosts[4])" `; move-focus left `; split-pane -s .5 -H pwsh -wd ~ -nop -noexit -command "connect $($Hosts[3])" `; move-focus right  `; move-focus right `; split-pane --tabColor `#f59218 --title 'DBAPatching' -s .5 -H pwsh -wd ~ -nop -noexit -command "connect $($Hosts[5])"
}
```

### Expected Behavior

I would like to be able to use the same positional argument -D or -H on the same spot or at least have indication on the reference doc about this.

### Actual Behavior

When using -H then command -> command executed
When using -D then command -> command not executed
Repository: rust
Issue: rustdoc: add link prefix which would allow overwriting explicit links with item links
Labels: T-rustdoc,C-feature-request,A-rustdoc-ui,A-rustdoc-js

Many crates use `#![doc = include_str("../README.md")]` to reduce doc duplication. Unfortunately, it means that we have provide explicit item links:
```md
This crate provides the [`foobar`] function.

[`foobar`]: https://docs.rs/foobar/latest/foobar/fn.foobar.html
```

It works fine when README is rendered on GitHub or crates.io, but when docs generated by rustdoc we get external item links, which causes a number of issues (e.g. when docs generated offline).

It would be nice if rustdoc recognized a special link prefix which would allow it to overwrite explicit links with auto-generated item links. For example:
```md
This crate provides the [`foobar`][rustdoc:foobar] function.

[rustdoc:foobar]: https://docs.rs/foobar/latest/foobar/fn.foobar.html
```

`[link][rustdoc:item]` would be translated to `[link](link-to-item)` and `[rustdoc::item]: explicit-link` would be ignored by rustdoc.
Repository: kubernetes
Issue: Allow authorization webhooks to request SARs in proto format
Labels: kind/feature,sig/auth,triage/accepted

Now that we have structured authorization configuration, a useful option for authorization webhooks would be to receive SARs in proto format for efficiency

/kind enhancement
/sig auth
/assign
Repository: kubernetes
Issue: container finished log does not include pod name - this makes it difficult to identify out of memory kills
Labels: priority/backlog,sig/node,kind/feature,triage/accepted

### What would you like to be added?

When a container dies due to OOMKill, there are these types of logs generated:

kubelet.go:2447] "SyncLoop (PLEG): event for pod" pod="<namespace/pod template hash>"

generic.go:334] "Generic (PLEG): container finished" podID="<podid....>" containerID="<containerid...>" exitCode=137

Would it be possible to consistently log the pod name (namespace/template hash) in the container finished log message (https://github.com/kubernetes/kubernetes/blob/57645002432c52aa743e69739613ca337616441a/pkg/kubelet/pleg/generic.go#L334) ?

From the definition of the Pod struct it appears that this information would also be available in generic.go



### Why is this needed?

This would make the log messages more consistent and make it easier to find OOM kills by pod name. Currently it involves having to find the podID which makes it difficult to find these messages.
Repository: animate.css
Issue: transition-timing-function should be animation-timing-function
Labels: bug

### Describe The Bug

bounce keyframe contains `transition-timing-function`, I think this should be `animation-timing-function`. I don't think `transition-timing-function` is supported in a keyframe

https://github.com/animate-css/animate.css/blob/3f8ab233dbbd9d2fe577528d2296382954be3d1a/source/attention_seekers/bounce.css#L22

### Steps To Reproduce

_No response_

### Expected Behavior

_No response_

### Screenshots

_No response_

### Desktop

_No response_

### Smartphone

_No response_

### Additional Context

_No response_
Repository: angular
Issue: Angular Devtools throw errors due to unsafe property accesses
Labels: area: devtools

### Is this a bug report or a feature request?

- [X] Bug Report
- [ ] Feature Request

### Please provide the steps to reproduce the issue [Bug Report only]

[stackblitz](https://stackblitz.com/edit/stackblitz-starters-eanrmy?file=src%2Fmain.ts)

Consider this accessor in a directive:

```ts
  foo: { bar: number } | undefined;

  get bar(): number {
    return this.foo!.bar;
  }
```

Before accessing the getter myself, I can make sure that `foo` is actually defined. The devtools don’t do that and try to access the `bar` property of the undefined `foo` when evaluating the `bar` accessor.

This prevents any debugging info about the selected component from rendering. (Note: the inspector panel still shows ‘No selected Element’, even though I did select the app-root, resulting in the error.)

### Please provide the expected behavior vs the actual behavior you encountered [Bug Report only]

At the very least, reading getters should happen in a try…catch block, so the error is caught. It is expected (in the example application) that `bar` cannot be accessed ‘blindly’, i.e. without prior checks.

I find that the devtools should not invoke getters at all automatically, since that may trigger unintended side-effects. I propose that getters only get evaluated upon demand, like the Chrome devtools do:

![image](https://github.com/angular/angular/assets/92570274/6eeccecf-5cbe-4bc5-855a-02af4a4837ff)


### Please provide a screenshot if possible [Bug Report only]

![image](https://github.com/angular/angular/assets/92570274/29513eae-3442-481c-86ae-509a48c24c4b)


### Please provide the exception or error you saw [Bug Report only]

```true
Uncaught TypeError: Cannot read properties of undefined (reading 'bar')
    at get bar (main.ts:14:22)
    at ft (state-serializer.ts:85:32)
    at state-serializer.ts:115:20
    at Array.forEach (<anonymous>)
    at ut (state-serializer.ts:111:18)
    at c (component-tree.ts:131:16)
    at kn (component-tree.ts:149:5)
    at client-event-subscribers.ts:148:19
    at n (same-page-message-bus.ts:46:21)
    at _ZoneDelegate.invokeTask (zone__js.js?v=4bf4bc0c:326:171)
```


### Is this a browser-specific issue? If so, please specify the device, browser, and version. [Bug Report only]

_No response_

### Description [Feature Request only]

_No response_

### Proposed solution [Feature Request only]

_No response_

### Alternatives considered [Feature Request only]

_No response_
Repository: vscode
Issue: TreeError [FileExplorer] Data tree node not found: ExplorerItem: base
Labels: bug,file-explorer

What I did:

1. Click vs\base (this was in the xterm.js codebase, experimenting with pulling some vscode sources in)
2. Ctrl+x
3. Click common (vs\base\common)
4. Ctrl+x, :bug: error

![Image](https://github.com/user-attachments/assets/018c208b-80ca-4124-837f-7cd75044dc69)
Repository: vscode
Issue: Cut node fade applies to all inline folders
Labels: bug,file-explorer

✅ What a single cut item looks like:



![Image](https://github.com/user-attachments/assets/368e431c-0f37-42f6-8e63-1e4b2e739d48)

🐛 What a condensed cut item looks like:

![Image](https://github.com/user-attachments/assets/ff682369-6132-4cc1-ad5d-2511e82483f9)

It should only fade `base` in this case, not `vs \`
Repository: godot
Issue: [Core] `Array` and `Dictionary` read only behavior is unsafe
Labels: bug,discussion,topic:core

### Tested versions

N/A

### System information

N/A

### Issue description

For example:
* https://github.com/godotengine/godot/pull/93636

You also have that, in C++, the following is broken, for example:
```cpp
Array tmp;
tmp.push_back(1);
tmp.push_back(2);
tmp.make_read_only();
assert(tmp[0] != tmp[1]);
```

All due to the fact that the return from the subscript operator and `Array::get` return a reference to a single internal `read_only` value

This would also cause problems in cases like:
```cpp
const Variant &first_value = arr[0];

for (int i = 1; i < arr.size(); ++i) {
    // Do something involving access to `arr`, if the array is read-only it will change the value in `first_value`.
}
```

The main problem is that the non-const subscript operator has to return a non-const reference, if this wasn't necessary we could safely return `const Variant &` for the const operator and just trust that no one messes with it with casting, just like the const operator for `LocalVector`, but since we might be working with a non-const but read-only `Array` reference we can't reasonably error or crash when accessing the non-const operator.

---

A possible temporary improvement would be to remove the use of the read-only data in the const access cases (this is already the case in `Dictionary`), that would reduce the impact somewhat, but the non-const case is more tricky.

### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: autoSurround fails for white-space only selections
Labels: bug,editor-autoclosing

Type: <b>Bug</b>

## STR

0. Ensure `editor.autoSurround` is enabled (by default it is enabled).
1. Create file and set syntax to MarkDown.
2. Type a space.
3. Select the space.
4. Press `[`.

## Expected outcome

`[ ]` (a.k.a. "Markdown checkbox") produced.

## Actual outcome

`[` Produced. I.e. the selected space is simply overwritten, instead of surrounded by a bracket pair, like any other non-white-space selection is.

---

// Anecdotally, I am not fond much about this pref since I am more used to overwrite selections instead of deleting them, and I am constantly running into this feature when my intention is to replace selection with **single** bracket and then end up with the text being selected and surrounded instead. I'm just testing if I will get used to enabled `editor.autoSurround`, and paradoxically, maybe I'd appreciate the white-space autoSurround more than non-whitespace.

---
VS Code version: Code 1.90.2 (5437499feb04f7a586f677b155b039bc2b3669eb, 2024-06-18T22:34:26.404Z)
OS version: Windows_NT x64 10.0.19045
Modes:


<!-- generated by issue reporter -->
Repository: ui
Issue: [bug]:  Combobox inside Form Component in docs is not working as expected.  
Labels: bug

### Describe the bug

When clicking the combobox the error in the console is.

TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at Function.from (<anonymous>)
    at O (69016-e46275a046c77977.js:1:8485)
    at M (69016-e46275a046c77977.js:1:7484)
    at 69016-e46275a046c77977.js:1:6256
    at 69016-e46275a046c77977.js:1:14852
    at Map.forEach (<anonymous>)
    at 69016-e46275a046c77977.js:1:14841
    at aI (eb2a38ac-8c1a930f3b668d8a.js:1:72883)
    at aU (eb2a38ac-8c1a930f3b668d8a.js:1:72943)
    at aV (eb2a38ac-8c1a930f3b668d8a.js:1:73382).

### Affected component/components

Combobox

### How to reproduce

1. Go to combobox component in the docs
2. The final example, a combobox inside form component.
3. Click the combobox

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))
    at Function.from (<anonymous>)
    at O (69016-e46275a046c77977.js:1:8485)
    at M (69016-e46275a046c77977.js:1:7484)
    at 69016-e46275a046c77977.js:1:6256
    at 69016-e46275a046c77977.js:1:14852
    at Map.forEach (<anonymous>)
    at 69016-e46275a046c77977.js:1:14841
    at aI (eb2a38ac-8c1a930f3b668d8a.js:1:72883)
    at aU (eb2a38ac-8c1a930f3b668d8a.js:1:72943)
    at aV (eb2a38ac-8c1a930f3b668d8a.js:1:73382)
```


### System Info

```bash
Browser
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Accessibility:  "Dark high contrast theme" cursor disappears and stops blinking after a time
Labels: accessibility,under-discussion

I am using VSCode in MS Edge. I have eyesight issues so I need to use dark mode. When I use the "Dark high contrast theme" the cursor is not visible. When I first click in the code I see the cursor blinking, but then that stops and I have no idea where the cursor is.

People using the high contrast themes are usually doing it because they find it difficult to see, and the cursor is particularly difficult to see anyway.

Please can these themes be made more accessible. It would be a lot better if the cursor was a thicker line. It is good that the cursor is a bright colour such as bright white. In fact, making the cursor thicker (and brighter if it's not already) would be good, not just on the high contrast themes but on the other themes too (especially the dark themes).

Cursor on the screenshot is at the end of line 12 but there is no way of knowing because it's not visible.

![image](https://github.com/microsoft/vscode/assets/21264690/4d6189ad-fb93-4855-9070-deb6fa291c9f)

Version: 1.90.2
Commit: 5437499feb04f7a586f677b155b039bc2b3669eb
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Edg/126.0.0.0
Embedder: vscode.dev

<!-- generated by web issue reporter -->
Repository: godot
Issue: Meshes with a negative scale have incorrect normals when using `cull_disabled` and `cull_front` render modes
Labels: bug,topic:rendering,topic:3d

### Tested versions

- Reproducible in 4.1, 4.2.1, 4.3-beta 2, using the forward+ renderer.
- Haven't tested other builds

### System information

Godot v4.2.2.stable - Arch Linux #1 SMP PREEMPT_DYNAMIC Fri, 21 Jun 2024 19:49:19 +0000 - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 6950 XT (RADV NAVI21) () - AMD Ryzen 7 3700X 8-Core Processor (16 Threads)

### Issue description

The following render modes cause incorrect normals to meshes with a negative scale:
- `cull_disabled`
- `cull_front` 

`cull_back` works as expected, and `ensure_correct_normals` does not fix the issue.


The capsule on the left have a scale of (-1, 1, 1). The capsule on the right has the default scale.

![image](https://github.com/godotengine/godot/assets/52043844/135ace1a-2ebe-4f2b-a305-fcd005a9c912)


Using `cull_back`: 

![image](https://github.com/godotengine/godot/assets/52043844/b6682707-0d80-4c8a-9db9-13115075696c)






### Steps to reproduce

+ Create a mesh
+ Set its scale to a negative one
+ Apply the following shader:

```glsl
shader_type spatial;
render_mode unshaded, cull_disabled; // Same happens with cull_front. cull_back works as expected.

void fragment() {
	ALBEDO = NORMAL;
}
```

### Minimal reproduction project (MRP)

- MRP: [negative_scale.zip](https://github.com/user-attachments/files/16033514/negative_scale.zip)
Repository: flutter
Issue: The `Image` widget `image` parameter is misnamed
Labels: framework,a: images,c: proposal,P3,team-framework,triaged-framework

### Steps to reproduce

N/A

### Expected results

N/A

### Actual results

N/A

### Code sample

When using a provider with the `Image` widget, the code looks like this:

```dart
Image(image: HttpImage(...))
```

The parameter name `image` doesn't provide a clue that it is providing the data for the image.

A better name would be `provider`.



### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

N/A
Repository: ollama
Issue: Support for Snapdragon X Elite NPU & GPU 
Labels: feature request,windows

Hi all.

I just got a Microsoft laptop7, the AIPC, with Snapdragon X Elite, NPU, Adreno GPU. It is an ARM based system.

But I found that NPU is not running when using Ollama.

Would it be supported by Ollama for the NPU and GPU?