sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: yt-dlp
Issue: [youtube] 120-hour limit, imposed on live streams is wrong
Labels: site-enhancement,triage

### 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 requesting a feature unrelated to a specific site
- [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 issues **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)

### Provide a description that is worded well enough to be understood

Please, make it at least 168 hours or do some actual probing for available timestamps. This hard limit is definitely not flexible and not everyone could patch their youtube.py, especially, Windows users.

### Provide verbose output that clearly demonstrates the problem

- [X] 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
- [X] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

```shell
[debug] Command-line config: ['-vU']
Deprecated Feature: Support for Windows 7/Server 2008 R2 has been deprecated. See  https://github.com/yt-dlp/yt-dlp/issues/10086
  for details.
                    You may stop receiving updates on this version at any time!
[debug] Encodings: locale cp1251, fs utf-8, pref cp1251, out utf-8 (No VT), error utf-8 (No VT), screen utf-8 (No VT)
[debug] yt-dlp version nightly@2024.09.29.232819 from yt-dlp/yt-dlp-nightly-builds [6328e2e67] (win_exe)
[debug] Python 3.8.10 (CPython AMD64 64bit) - Windows-7-6.1.7601-SP1 (OpenSSL 1.1.1k  25 Mar 2021)
[debug] exe versions: ffmpeg git-2024-09-22-a577d31-ffmpeg-windows-build-helpers (fdk,setts), ffprobe git-2024-09-22-a577d31-ffm
peg-windows-build-helpers
[debug] Optional libraries: Cryptodome-3.20.0, brotli-1.1.0, certifi-2024.08.30, curl_cffi-0.5.10, mutagen-1.47.0, requests-2.32
.3, sqlite3-3.35.5, urllib3-2.2.3, websockets-13.1
[debug] Proxy map: {}
[debug] Request Handlers: urllib, requests, websockets, curl_cffi
[debug] Loaded 1838 extractors
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp-nightly-builds/releases/latest
Latest version: nightly@2024.09.29.232819 from yt-dlp/yt-dlp-nightly-builds
yt-dlp is up to date (nightly@2024.09.29.232819 from yt-dlp/yt-dlp-nightly-builds)
```
Repository: go
Issue: proposal: slices: funcs `CollectKeys` and `CollectValues` to collect from an iter.Seq2
Labels: Proposal

### Proposal Details

The `slices` package currently has `Collect()` to perform `iter.Seq[T] -> []T`, but it doesn't have similar helper functions for collecting the keys or values from an `iter.Seq2[K, V]`.

I propose to add the following two functions to `slices`:

```go
func CollectKeys[K, V any](seq iter.Seq2[K, V]) []K {
	var s []K
	for k := range seq {
		s = append(s, k)
	}
	return s
}

func CollectValues[K, V any](seq iter.Seq2[K, V]) []V {
	var s []V
	for _, v := range seq {
		s = append(s, v)
	}
	return s
}
```
Repository: PowerToys
Issue: Workspaces error on streamdeck
Labels: Issue-Bug,Needs-Triage,Product-Workspaces

### Microsoft PowerToys version

0.84.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Workspaces

### Steps to reproduce

Hi everyone, I created a workspace and created a shortcut icon on the desktop, when I try to add that file to my streamdeck and try to run that file it gives me this error: Incorrect command line arguments

if I run the file with a double mouse click it works, why doesn't it work when I try to use the same file but via streamdeck? Is it possible to solve it? It's easier for me to manage the workspaces via streamdeck.

thanks

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: ollama
Issue: Error: llama runner process has terminated: error loading modelvocabulary: cannot find tokenizer merges in model file
Labels: bug

### What is the issue?

time : 09/30/2024
script:
```
FROM "./model-quant.gguf"
TEMPLATE """{{- if .System }}

system {{ .System }}

{{- end }}

user
{{ .Prompt }}


assistant
"""

SYSTEM """"""

PARAMETER stop 

PARAMETER stop 

```
The creation was successful, but the operation failed

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

ollama version is 0.3.12
Repository: godot
Issue: Android Editor [4.4.dev2]: Heavy Lag and Glitches during editing mash and mertarial. 
Labels: performance

### Tested versions

4.4.dev2

### System information

Android 10 - Godot 4.4.dev2 - Compatibility Renderer 

### Issue description

Editor is glitching and lagging too much when editing mash and mertarial in android editor. Need to optimize. 


https://github.com/user-attachments/assets/d1e0913f-c4ce-4e77-a4b2-1b932fad1427
Repository: ui
Issue: [bug]: Unexpected token < in JSON at position 0
Labels: bug

### Describe the bug

# Bug Report: Error when adding v0.dev block to shadcn-ui
![GYsfOF4aoAAciwy](https://github.com/user-attachments/assets/ab2d9949-6679-47a2-bf94-d69476cf3b7a)


## Description
When attempting to add a block from v0.dev to a shadcn-ui project, an error occurs during the execution of the `npx shadcn add` command.

## Steps to Reproduce
1. Start in a directory without a `package.json` file
2. Run the command: `npx shadcn add https://MYURL.v0.build/`
3. Follow the prompts to create a new Next.js project
4. The process fails at the "Checking registry" step

## Expected Behavior
The command should successfully add the v0.dev block to the shadcn-ui project.

## Actual Behavior
The process fails with the following error:
```
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Unexpected token < in JSON at position 0
```

## Environment
- Operating System: macOS
- npm version: 10.8.3 (after update)
- Node.js version: v18.18.2

## Additional Information
- The issue persists after updating npm to the latest version (10.8.3)
- The error occurs during the "Checking registry" step

## Possible Cause
The error message "Unexpected token < in JSON at position 0" typically indicates that the response received is not valid JSON. This could be due to:
1. Network issues causing an HTML error page to be returned instead of JSON data
2. The registry endpoint returning an invalid response
3. A problem with the URL or the content at `https://MYURL.v0.build/`


### Affected component/components

Published Blocks in v0

### How to reproduce

1. Start in a directory without a `package.json` file
2. Run the command: `npx shadcn add https://MYURL.v0.build/`
3. Follow the prompts to create a new Next.js project
4. The process fails at the "Checking registry" step

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
M2 MacBook Air, 14.6.1 (23G93)
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: PowerToys
Issue: Multi-Desktop Powertoy FancyZone settings would change from existing settings after rebooting computer
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

FancyZones

### Steps to reproduce

Multi-Desktop Powertoy FancyZone settings would change from existing settings after rebooting computer

For example 

My settings
Multi-Desktop1: Monitor1 = A, Monitor2 = B 
Multi-Desktop2: Monitor1 = C, Monitor2 = D

After rebooting 
Multi-Desktop1: Monitor1 = one of the default templates, Monitor2 = one of the default templates
Multi-Desktop2: Monitor1 = A, Monitor2 = B

It looks like this. Could you please fix this so that the settings are preserved after a reboot?



### ✔️ Expected Behavior

Keep existing settings



### ❌ Actual Behavior

Different settings




### Other Software

_No response_
Repository: node
Issue: Require of cached modules is not working after a while
Labels: loaders

### Version

18.20.4

### Platform

```text
Linux b3fb3508-30f0-4ff0-4220-0bc8 5.15.0-117-generic #127-Ubuntu SMP Fri Jul 5 20:13:28 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```


### Subsystem

-

### What steps will reproduce the bug?

The issue we face happens as following:
During the runtime of our backend, we happen to need some code extensions which we basically download and save on the disk ( on demand ofc ), and after we got them in place we require them in the code using the filePath that is being returned by the function which does the download & save on disk. [Yes we know thats not safe, but that works for us right now]

Now, after some weeks or days even of the backend running, these demanded files that are can be found in the require.cache ( once we require the file the first time ) are getting somehow lost, or module.exports of that specific module gets lost.

### How often does it reproduce? Is there a required condition?

Usually, we encounter this issue once every two weeks or similar. ( But from what our users report, its not always the same case )

### What is the expected behavior? Why is that the expected behavior?

We expect the require(filePath) to return the actual functions and other things exposed via module.exports.

### What do you see instead?

Instead, we basically see the following:
<img width="1333" alt="image" src="https://github.com/user-attachments/assets/1d2d3080-4160-4ce7-b460-b46f7f59c5b3">
we also tried to see somehow the require(file)'s keys
<img width="650" alt="image" src="https://github.com/user-attachments/assets/091745a1-20d7-4e75-b676-769458217541">
----

The strange thing is, the file is on the disk, and actually has content in it ( even if in the following picture we dont actually see any module.exports, trust me, those are there ) 
<img width="1685" alt="image" src="https://github.com/user-attachments/assets/06c7c4ac-07d4-4973-ae11-48e281965161">

While debugging, even if the file itself is on the disk, the debugger does not show it:
<img width="900" alt="image" src="https://github.com/user-attachments/assets/d78ed093-0259-4d89-8e57-4e563ceccf28">

----

as for the require.cache here it is:
![image](https://github.com/user-attachments/assets/d8bea7aa-b4a7-44a1-bb77-576465c51f63)


### Additional information

I have to mention that usually, using delete require.cache(that require) and downloading the file again solves the issue, or just restarting the server itself.
Repository: kubernetes
Issue: add tests for scheduler-perf itself
Labels: kind/cleanup,sig/scheduling,needs-triage

/sig scheduling
/kind cleanup

[scheduler-perf](https://github.com/kubernetes/kubernetes/tree/master/test/integration/scheduler_perf) has few tests for itself at the moment; we roughly check the behavior with `-tags performance, short` or `-tags integration-test, short`, which could miss some potential issues with it.
scheduler-perf right now serves a crucial role for the scheduler to keep our targets in various metrics, and we're adding more and more features into it. Unless we have proper testing for it, the more features we add into it, the more likely we could break some existing parts without noticing it since the reviewing would get more and more difficult.

So, this issue aims to add tests for it. I guess it also requires some refactoring, especially around [`runWorkload`](https://github.com/kubernetes/kubernetes/blob/1bbe775d5ffb131636193fe0bc15a8fcc0cd6fd6/test/integration/scheduler_perf/scheduler_perf.go#L1270), which is currently huge.

/cc @alculquicondor @macsko @dom4ha
Repository: PowerToys
Issue: FancyZones: Set colour/opacity/blur for certain zones/inactive zones
Labels: Needs-Triage

### Description of the new feature / enhancement

Set either certain zones, or the option for unused zones, to have a colour/opacity/blur level.

E.g., on a wide monitor, you have a large zone in the middle, and one on each side. Right now, the two either side are transparent when not used.

There could be options to:-

1. Not allow the zones on the left and right to be used, and then set their blur/colour/opacity levels.
2. When unused, the zones will blur/go a colour/change their opacity levels, until they are used.

This will allow you to create a "focus" window in the middle, and remove distractions on the left and right.

### Scenario when this would be used?

This will allow you to have focused zones that are used, as the disallowed/unused zones blur/change colour/go more opaque.

### Supporting information

_No response_
Repository: material-ui
Issue: [docs] Icons aren't searchable anymore in Algolia
Labels: bug 🐛,docs,package: icons,regression,scope: docs-infra

See https://github.com/mui/material-ui/pull/41330#issuecomment-2323517472

Icons used to be searchable in [v4](https://v4.mui.com/components/material-icons/#material-icons)

![image](https://github.com/user-attachments/assets/ed08080e-b29d-4cd6-9e5f-0ac76ad34b29)


But even after [reverting](https://github.com/mui/material-ui/pull/43569) the icons virtualization, they still aren't searchable.

<img width="951" alt="Screenshot 2024-09-30 at 09 54 56" src="https://github.com/user-attachments/assets/76b0b206-423e-4ecc-a757-0eb88845bc7c">


**Search keywords**:
Repository: node
Issue: `require.resolve` cannot find module after calling `require.resolve` and installing dependencies 
Labels: loaders,v20.x

### Version

v20.17.0

### Platform

```text
Darwin P03694NWF5 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct  9 21:32:11 PDT 2023; root:xnu-10002.41.9~7/RELEASE_ARM64_T6030 arm64
```


### Subsystem

require

### What steps will reproduce the bug?

1. Init an emty project
```
npm init
```

2. Add a package. e.g. lodash
```
npm install lodash
```

3. Execute this script, the `pkg` can be any dependencies that are not installed in the global environment and current project. e.g. rollup
```javascript
const { exec } = require('child_process');
const pkg = 'rollup';

try {
  console.log(require.resolve(pkg));
} catch (e) {
  console.log(e);
}

const child = exec(
  `npm install ${pkg}`,
  () => {
    console.log(require.resolve(pkg));
  }
);

// sync log from child_process to main process
child.stdout?.on('data', (data) => {
  process.stdout.write(data);
});

child.stderr?.on('data', (data) => {
  process.stderr.write(data);
});
```
The output shows twice `Error: Cannot find module 'rollup'`, the first one is expected; But the second one seems to be a bug.

### How often does it reproduce? Is there a required condition?

Emerge necessarily.

The required condition is the first `require.resolve` call. Without it, the script works fine.

### What is the expected behavior? Why is that the expected behavior?

Output the resolve path correctly after installing the package

### What do you see instead?

```
Error: Cannot find module 'rollup'
Require stack:
- /Users/Documents/test/index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
    at Function.resolve (node:internal/modules/helpers:190:19)
    at Object.<anonymous> (/Users/Documents/test/index.js:5:23)
    at Module._compile (node:internal/modules/cjs/loader:1469:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
    at Module.load (node:internal/modules/cjs/loader:1288:32)
    at Module._load (node:internal/modules/cjs/loader:1104:12)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12)
    at node:internal/main/run_main_module:28:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/Users/Documents/test/index.js' ]
}

added 3 packages, and audited 5 packages in 1s

found 0 vulnerabilities
node:internal/modules/cjs/loader:1228
  throw err;
  ^

Error: Cannot find module 'rollup'
Require stack:
- /Users/Documents/test/index.js
    at Module._resolveFilename (node:internal/modules/cjs/loader:1225:15)
    at Function.resolve (node:internal/modules/helpers:190:19)
    at /Users/Documents/test/index.js:13:25
    at ChildProcess.exithandler (node:child_process:414:7)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [ '/Users/Documents/test/index.js' ]
}
```

### Additional information

_No response_
Repository: transformers
Issue: Improve image processing time
Labels: Feature request,Vision,optimization,Processing

### Feature request

Optimize Transformers' image_processors to decrease image processing time, and reduce inference latency for vision models and vlms.

### Motivation

The Transformers library relies on PIL (Pillow) for image preprocessing, which can become a major bottleneck during inference, especially with compiled models where the preprocessing time can dominate the overall inference time.

![image](https://github.com/user-attachments/assets/10e19b7a-5e48-4bef-84a1-430458e17586)
![image-1](https://github.com/user-attachments/assets/be4f06f3-befd-44b7-b743-10f09471fa58)


In the examples above, the RT-DETR preprocessing necessitates only to resize the image, while the DETR one involves resize+normalize. 
In eager mode, image preprocessing takes a big part of the total inference time for RT-DETR, but is not the main bottleneck. However, with a compiled RT-DETR, image preprocessing takes up the majority of the inference time, underlining the necessity to optimize it. This is even clearer for DETR, where image preprocessing is already the main bottleneck in eager mode.

However, alternative libraries exist that leverage available hardware more efficiently for faster image preprocessing.
[OptimVision](https://github.com/yonigozlan/OptimVision) uses such libraries to get much better results compared to Transformers.

Much more details on OptimVision and image processing methods comparison are available on this [Notion page](https://www.notion.so/huggingface2/OptimVision-Optimize-preprocessing-time-10f1384ebcac8091a12debb87fe5f591?pvs=4).

### Your contribution

OptimVision is an experiment playground to optimize the different steps involved in inferring/training with vision models.
The current fast image preprocessing in OptimVision is a proof of concept and is not yet ready to be merged into Transformers, but that this the ultimate goal :).
Repository: PowerToys
Issue: Seamless Night Light
Labels: Needs-Triage

### Description of the new feature / enhancement

Instead of one setting for the night light which often seems too strong/soft at sunset/sunrise time it would be awesome to transition seamlessly and according to the actual daytime.

### Scenario when this would be used?

Every-Day Use and especially for people who tend to work very early or late.

### Supporting information

_No response_
Repository: ui
Issue: [bug]: useFormField can be used without being nested within FormField
Labels: bug

### Describe the bug

useFormField has a check that should prevent it from being used when it is not called within a FormField component.
This error is not thrown because empty objects (the default of the context when it is not wrapped in a provider) are true when checking in the if condition.

### Affected component/components

Form

### How to reproduce

1. Render any component that uses useFormField within a Form without being inside of a FormField component.
2. Don't see the error.

### Codesandbox/StackBlitz link

https://stackblitz.com/edit/vitejs-vite-za3zz1?file=src%2FApp.tsx

### Logs

_No response_

### System Info

```bash
MacOS, Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Conflict resolver worked not expected when I click accpect incoming or current
Labels: bug,merge-conflict

Edit from @hediet: 

When accepting conflict 1 and 2 fast enough, the edit for conflict 2 does not take into account the (still ongoing) edit for conflict 1.

---

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.93.1 (system setup)
- OS Version: Windows_NT x64 10.0.22631

Steps to Reproduce:
1. Some time I tried to resolve conflict in vscode. It worked ok when there was only on conflict, if two conflict came up, the first one could been resolved smooth by clicking accept incoming or current button. But the second will failed, after clicking one accept button, it didn't work.  
2. Then I pressed ctrl+z to undo, and clicked the button again, it worked ok .

![ezgif-1-e8312ec3ca](https://github.com/user-attachments/assets/7b1ff00a-2609-42df-8680-0dd46f123d5a)
Repository: PowerToys
Issue: new feature
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

You hold down some button
While you hold the button keyboard layout switches to the selected one
You release the button 
The keyboard layout switches to the original one


### Scenario when this would be used?

write very quickly on the Russian keyboard #
for example RightAlt+Shift+3 give us # on the Russian layout
or the № on the English layout switching to Russian



### Supporting information

_No response_
Repository: vscode
Issue: Screen reader box incorrectly positioned when selecting multiple lines 
Labels: bug,editor-input

The screen reader box incorrectly positioned when selecting multiple lines when using MacOS voice over
This is because the edit context hidden element is incorrectly positioned on multi-line selections

https://github.com/user-attachments/assets/3992fe5b-71ca-4a59-919e-10e27dc9f1ae
Repository: ollama
Issue: Warn users when input is longer than supported context
Labels: bug

### What is the issue?

Hi thanks for the great library! It would be great if there could be a warning when input is longer than supported context. Otherwise, if the text is silently truncated, the behavior can be confusing.

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_