sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: yt-dlp
Issue: Cut between keyframes more efficiently (smart cuts)
Labels: enhancement,triage,core:post-processor

### 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

Using --force-keyframes-at-cuts is really slow because it re-encodes the entire video. In the lossless-cut software there is [a feature](https://github.com/mifi/lossless-cut/issues/126) that only re-encodes from the cutpoint to the next keyframe and copies the rest to avoid having to re-encode the whole thing. Is it possible for a similar feature to be implemented in yt-dlp, perhaps as --smart-keyframes-at-cuts?

### 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: electron
Issue: [Bug]: Can't set Windows taskbar jumplist icon
Labels: platform/windows,blocked/need-info ❌,bug :beetle:,has-repro-gist,stale,31-x-y

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

31.6.0

### What operating system(s) are you using?

Windows

### Operating System Version

Windows 11

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

```js
app.setUserTasks([
  iconPath: '<path_to_icon>'
])
```

Setting iconPath for the jumplist menu entry as specified above should work. The included gist don't include an image, as I wasn't able to find a way to upload an image to electron fiddle.

### Actual Behavior

The app icon is shown instead of the specified icon. Tried both packaged and non-packaged bundles.

### Testcase Gist URL

https://gist.github.com/rmartins90/b1b231ddbdabf2b585ab4c705342bf61

### Additional Information

_No response_
Repository: react
Issue: [Compiler Bug]: Performance - `useEffect` without dependencies should be left alone
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEUYCAwgBYCGmA5gmAKIBuCMAngCp4C2CACgCURYAB1iROITA4iAbRbUANgBoiZHADUVAXSIBeEmQDKOajkHDDAPiIBZC5QB0MWgBMIvYUIDcEiSJjBCY0NARcAWsDO3FJIM0dZQFHHBc3TE9vIT9AogBfXMw8mAQcWGIlZX9MfIDMDGx8QmCAdTcABySoBABBMAAlBDRrOKDpTFkiKsNgqloGZjZOHn5hGvGZOVK0WdIEIZGqorz90PDI6Ni8oJ3nOFhSzDkjKo2Ck8lS8phiHZq6pgQPkgA

### Repro steps

I was playing around with a small repo I had and noticed something similar to #30782. (Essentially, I was tracking a variable so that the callback identity could be stable to avoid rapid-fire rerenders of the whole page)

Wrapping it in a useEffect works and probably more correct, but it generates redundant memoization:

```js
function useWrapValueAsRef() {
  const $ = _c(2);
  const val = useChangesEveryTime();
  const ref = useRef(val);
  let t0;
  if ($[0] !== val) {
    t0 = () => {
      ref.current = val;
    };
    $[0] = val;
    $[1] = t0;
  } else {
    t0 = $[1];
  }
  useEffect(t0);
  return ref;
}
```

where I would expect it to just leave everything alone.

Ignoring the contrived source of the variable (in the real app I'm testing with, it probably changes a couple times on page load), it does the check every time, which is redundant because the useEffect will always run the latest closure anyways. I'm not sure if this is because of some sort of optimization in useEffect but I don't see why that would be the case.

I don't imagine this to be a huge issue, but it's technically less performant as the code size is bigger and it uses 2 array slots.

### How often does this bug happen?

Every time

### What version of React are you using?

React Playground (19-RC)
Repository: godot
Issue: Overriding hover_pressed state of the button in custom project theme affects the editor theme
Labels: bug,topic:editor,topic:gui

### Tested versions


- Reproducible in: v3.6.stable.official [de2f0f147]
- Not reproducible in: v3.5.3.stable.official [6c814135b] and v4.3.stable.official [77dcf97d8]

### System information

Windows 11 - Godot v3.6.stable.official [de2f0f147] - GLES2 and GLES3 - dedicated NVIDIA GeForce GTX 1650 (Nvidia, 565.90) - Intel Core i5-9300HF CPU @ 2.40GHz (8 Threads)

### Issue description

By creating a GUI theme with the overridden hover_pressed state of the button (in Styleboxes) and assigning it in the project settings along the "gui/theme/custom" path, it also overrides this button state in the editor theme.

An example is shown in the screenshot below. Here I replaced the hover_pressed state of the button in Styleboxes, assigned it in the project settings, rebooted and moved the cursor to the enabled switch.

![image](https://github.com/user-attachments/assets/0f79e5df-afe1-4bab-8cc5-f7e700e4fcf2)

It is expected that the theme will only affect the GUI inside the project, and the editor theme should be redefined only through the editor settings along the "interface/theme/custom_theme" path.

### Steps to reproduce

1. Create a Theme resource in the project folder
2. Add the Button type for override
3. Go to the Styleboxes section and add the "hover_pressed" state
4. Create any new style for "hover_pressed" (I created StyleBoxFlat with red BG Color)
5. Save the style with the Save button in the theme editor
6. Go to the Project > Project Settings
7. Assign the created theme in the "gui/theme/custom" parameter
8. Restart the editor
9. Open the Theme Editor and hover over the "Show Default" switch or click on the Scene/Project/Debug buttons in the upper panel

### Minimal reproduction project (MRP)

[hover_pressed_mrp.zip](https://github.com/user-attachments/files/17270905/hover_pressed_mrp.zip)
Repository: excalidraw
Issue: Does not open color palette on vertical screen
Labels: bug

Hello, when I try to add text when the screen is horizontal and I type text it works correctly, but when the screen changes the aspect ratio it does not open the color palette, however it does work by selecting the previously created text and then selecting the color

https://github.com/user-attachments/assets/83e30cf3-b7ff-470d-8de6-14e17544f073


Also related to this, would it be possible to add the function of changing the text color of the letters or specific words of each text block, that is, to write text of different colors it is necessary to create a new text block separately, this is useful if you want to teach math
![Image](https://github.com/user-attachments/assets/691eabb3-3250-429b-b12e-ea200a52374b)


or grammar
![Image](https://github.com/user-attachments/assets/49eb6f65-6560-4670-b674-963370243552)


It is more practical and faster to change the text color of each word this way.
Regards.
Repository: pytorch
Issue: Public API comparison between v2.4.1 and v2.5 release branch
Labels: module: binaries,triaged,module: python frontend

Below a comparison of the Public API between v2.4.1 and the v2.5 release branch (https://github.com/pytorch/pytorch/issues/135522) @kit1980 
Most changes are not that exciting, but some might be helpful for writing the release notes.

Removed parameters:

- torch/ao/quantization/observer.py:984: HistogramObserver.__init__: `upsample_rate` removed (set to default of 16)
- torch/autograd/profiler.py:197: profile.__init__: `use_mtia` removed
- torch/fx/experimental/symbolic_shapes.py:4387: ShapeEnv.get_implications: `compute_hint` removed
- torch/fx/experimental/symbolic_shapes.py:5117: ShapeEnv.evaluate_expr: `expect_rational` removed
- torch/export/exported_program.py:663: ExportedProgram.__init__: `verifier` and `tensor_constants` removed

Required parameter added:

- torch/distributed/elastic/rendezvous/etcd_rendezvous.py:152: EtcdRendezvousHandler.__init__: `local_addr`  was added as required (but can be set to `None`). Perhaps set to `None` by default?

Renamed parameters:

- torch/__init__.py:970: typename(o): Parameter `o` was renamed to `obj`
- torch/masked/maskedtensor/core.py:18: is_masked_tensor: Parameter `a` was renamed to `obj`
- torch/autograd/graph.py:172: Node.__subclasshook__: Parameter `C` was renamed to `subclass`

Parameter was changed to positional-only:

- torch/__init__.py:1005: is_tensor(obj)
- torch/__init__.py:1025: is_storage(obj)
- torch/__init__.py:1117: set_default_tensor_type(t)
- torch/__init__.py:1490: set_warn_always(b)
- torch/_tensor.py:1165: Tensor.__contains__(self)
- torch/_tensor.py:1165: Tensor.__contains__(element)

Parameter was changed to keyword-only:

- torch/onnx/__init__.py:137: export(export_params):
- torch/onnx/__init__.py:137: export(verbose)
- torch/onnx/__init__.py:137: export(training)
- torch/onnx/__init__.py:137: export(input_names)
- torch/onnx/__init__.py:137: export(output_names)
- torch/onnx/__init__.py:137: export(operator_export_type)
- torch/onnx/__init__.py:137: export(opset_version)
- torch/onnx/__init__.py:137: export(do_constant_folding)
- torch/onnx/__init__.py:137: export(dynamic_axes)
- torch/onnx/__init__.py:137: export(keep_initializers_as_inputs)
- torch/onnx/__init__.py:137: export(custom_opsets)
- torch/onnx/__init__.py:137: export(export_modules_as_functions)
- torch/onnx/__init__.py:137: export(autograd_inlining)
- torch/onnx/__init__.py:137: export(dynamo)

Removed public objects:

- torch/onnx/__init__.py:0: ONNXProgramSerializer
- torch/onnx/__init__.py:0: InvalidExportOptionsError
- torch/onnx/symbolic_helper.py:0: is_caffe2_aten_fallback
- torch/onnx/errors.py:0: CheckerError
- torch/distributed/distributed_c10d.py:0: ProcessGroupCudaP2P
- torch/distributed/tensor/parallel/style.py:0: SequenceParallel.sequence_dim
- torch/distributed/__init__.py:0: ProcessGroupCudaP2P
- torch/export/__init__.py:0: dynamic_dim
- torch/export/dynamic_shapes.py:0: dynamic_dim


cc @seemethere @malfet @osalpekar @atalman @albanD
Repository: next.js
Issue: History pushState doesn't trigger Interceptor Route
Labels: bug,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/iamJoeTaylor/next-intercept-route

### To Reproduce

1. Using my repro you can `npm run dev` in my-app
2. Click on `Open Modal with history` which uses `window.history.pushState`

To build a reproduction yourself;
1. New NextJS project with App router.
2. Add an Interceptor Route
3. use `window.history.pushState`

This blog mentions pushSate so I'd expect it to work. https://nextjs.org/blog/next-14-1#windowhistorypushstate-and-windowhistoryreplacestate

### Current vs. Expected behavior

Currently the URL changes but the interceptor route is not invoked.

Expect the URL to change, the intercept route to work, and the history item to be present when fetched from `window.history.state`

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 24.0.0: Tue Sep 24 23:37:36 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 12
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 14.2.14 // Latest available version is detected (14.2.14).
  eslint-config-next: 14.2.14
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

next dev (local), Vercel (Deployed)

### Additional context

_No response_
Repository: svelte
Issue: Svelte 5: Dynamic Components do not update correctly after SSR
Labels: needs discussion

### Describe the bug

Dynamic components in Svelte 5 + Sveltekit do not update correctly after SSR. The state updates, but the rendered component doesn't reflect this change:

store.ts:
```tsx
import { browser } from "$app/environment";

const someStore = () => {
  let someCondition = $state(false)

  if(browser){
    someCondition = true
  }

  return {
    get someCondition () {
      return someCondition
    }
  }
}

export const store = someStore()
```
+page.svelte:
```tsx
<script lang="ts">
    import A from './A.svelte'
    import B from './B.svelte'
    import {store} from './store'

    $inspect(store.someCondition)

    const SelectedComponent = $derived(store.someCondition ? A : B)
</script>

<!-- should display A, but displays B -->
<SelectedComponent />

{store.someCondition}
```

$inspect() and {store.someCondition} both show true. SelectedComponent should render A, however it renders B.

its kinda like https://github.com/sveltejs/svelte/issues/12333 just for components.


with this workaround in the store.ts it correctly updates to A:
```tsx
	if (browser) {
		setTimeout(() => {
			someCondition = true;
		}, 0);
	}
```

### Reproduction

in the repl its working correctly. however locally in a fresh sveltekit + svelte 5 project its not.

https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAA4WSwW6DMBBEf2VrRQIkFO4IUkE-IcfSA8LryhWsLdskrRD_XhkISZo0PSEz4-edsQcmZIuWpW8Do7pDlrJCaxYz9639wh6xdchiZlVvGv8ns42R2u0qAgCQnVbGQQHCqA6CbVJs5y3BjV6uevlQH6xTBsfVNS0X5_bTBhXN9o0kq7Fx4WJQHe4VcemkouhsahRZBwdssXHI96rTipAc5LDhaOQR-aPt8AoFpFBGFWXJmrGi7B6UTMLwADJWxGLWKS6FRM5SZ3oc47Xa61iXjj_tdb8VzfN77sH7IYcwgnwHg4_X4ixd5s5hY13tMBR1a3FpQYrQ05WAkySuTvCS5xD0xFFIQh5Ew9zVb5Qf2CvjjDHoekOwmD_uzg6js7Z6bwyzNi7ECYpf040vIZeAa9gwet5g8fxp6pp2RZZM32eY8n9M-SfmffwB1kZLRjYDAAA=

### Logs

_No response_

### System Info

```shell
System:
    OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)
    CPU: (24) x64 AMD Ryzen 9 3900X 12-Core Processor
    Memory: 21.84 GB / 31.26 GB
    Container: Yes
    Shell: 5.9 - /usr/bin/zsh
  Binaries:
    Node: 20.11.1 - /usr/local/lib/nodejs/node-v20.11.1-linux-x64/bin/node
    Yarn: 1.22.22 - /usr/local/lib/nodejs/node-v20.11.1-linux-x64/bin/yarn
    npm: 10.2.4 - /usr/local/lib/nodejs/node-v20.11.1-linux-x64/bin/npm
    bun: 1.1.30 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: 129.1.70.123
    Chrome: 129.0.6668.89
  npmPackages:
    svelte: ^5.0.0-next.1 => 5.0.0-next.262
```


### Severity

annoyance
Repository: ui
Issue: [feat]: Keyboard input for Date Picker
Labels: area: request

### Feature description

It would be great if the [Date Picker](https://ui.shadcn.com/docs/components/date-picker) and [Date Range Picker](https://ui.shadcn.com/docs/components/date-picker#date-range-picker) could support keyboard input like the [Date Picker](https://www.bits-ui.com/docs/components/date-picker) and [Date Range Picker](https://www.bits-ui.com/docs/components/date-range-picker) of Bits UI.

It's often easier to type out a far away date instead of clicking multiple times through the UI.

### Affected component/components

Date Picker, Date Range Picker

### Additional Context

Similar reported issues that were since closed as stale:
#546
#2229
#4171

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: godot
Issue: GPUParticles2D triggering "at end" sub-emitter twice
Labels: bug,topic:particles

### Tested versions

- Reproducible in 4.3 stable, 4.4-dev3
- NOT reproducible in 4.2 stable

### System information

Godot v4.3.stable - macOS 14.4.1 - Vulkan (Forward+) - integrated Apple M1 - Apple M1 (8 Threads)

### Issue description

GPUParticles2D "at end" sub-emitter emits multiple times. This can be illustrated simply by setting "amount at end" to 1 and it will emit 2 particles. Set it to 2, you get two particles and so on. In addition they seem to be split across the location of the particle in its last two frames of life. This is very noticeable for any fast moving particle, once it dies its locations in the last two frames are decently far apart and will show two discrete bursts of particles using the "at end" emitter. 

This does appear to be a regression since in 4.2 I see the correct number of particles in my test project provided below.

### Steps to reproduce

- Create new 2d scene
- Create 2 GPUParticleEffect2D nodes named Parent and Child. Create them as siblings in the scene.
- Set the Child to be the sub-emitter of Parent
- set the Parent sub-emitter settings to:
  - Mode: At End
  - Amount at End: 1
  - Keep Velocity: False
- Configure the Parent and Child to have noticeably different particles that you can count.
- Set the child emitter to have a sufficiently high amount

### Minimal reproduction project (MRP)

[particlebugreport.zip](https://github.com/user-attachments/files/17271181/particlebugreport.zip)
Repository: PowerToys
Issue: Keyboard manager "Sleep" option doesn't work
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I've set any key up to put PC to sleep when pressed, however nothing happens.
![image](https://github.com/user-attachments/assets/2355bd13-5d37-42f7-9530-4634be38fbc8)


### ✔️ Expected Behavior

Press "PAUSE" key to put to Sleep

### ❌ Actual Behavior

Nothing happens

### Other Software

_No response_
Repository: ollama
Issue: Downloading models too slow
Labels: bug,windows,needs more info,networking

### What is the issue?

I have very slow downloads of models since I installed Ollama in Windows 11. No problems running models, etc. it's only the download speeds. 
The terminal seems to report a different speed than shown in my network monitor.
I include screens of two downloads and the network monitor, which report 30Mbps approx. while the Ollama progress bars indicates 1.7-1.9MBps. I've got no problems with firewalls or proxies, and downloads from any other clients of big files work usually at 50-300MBps. My network speed is 600MBps

`PowerShell 7.4.5
PS C:\Users\v6u2mop> ollama pull deepseek-coder-v2:16b
pulling manifest
pulling 5ff0abeeac1d...  32% ▕██████████████████                                      ▏ 2.9 GB/8.9 GB  1.9 MB/s  53m27s `

`PS C:\Users\ruben_v6u2mop> ollama pull qwen2.5-coder
pulling manifest
pulling ced7796abcbb...  69% ▕████████████████████████████                 ▏ 3.2 GB/4.7 GB  1.8 MB/s   13m0s `

![Screenshot 2024-10-06 161819](https://github.com/user-attachments/assets/31420f1d-c6bf-43de-8981-b8f1d9cdd424)


### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.3.12
Repository: PowerToys
Issue: Bug with PowerRename counter syntax (padding)
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

PowerRename

### Steps to reproduce

Have 11+ files with the format of : `1.ext`, `2.ext`, .... , `10.ext`, `11.ext`.....

Then use regex :
```
^(.+)$
```

and use counter syntax as :
```
${padding=2,start=1}
```

### ✔️ Expected Behavior

`10.ext` should be selected and renamed

### ❌ Actual Behavior

`10.ext` is not being selected and renamed

<br>

But `10.ext` is selected and renamed if I set `padding` to `3` instead of `2`
```
${padding=3,start=1}
```

### Padding 2
![2](https://github.com/user-attachments/assets/969f2dbf-5dd1-40eb-b9af-ea7cb351f9e8)

### Padding 3
![3](https://github.com/user-attachments/assets/42a7f8a2-d496-406b-9904-5d8b2a39da0a)

### Other Software

_No response_
Repository: rust
Issue: ICE with `core::iter::adapters::peekable` + recursion + pattern matching on `peek`
Labels: I-ICE,A-trait-system,T-compiler,C-bug,S-bug-has-test

<!--
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.
-->

I tried this code:

```rust
fn main() {
  let mut items = vec![1, 2, 3, 4, 5].into_iter();
  problem_thingy(&mut items);
}

fn problem_thingy(items: &mut impl Iterator<Item = u8>) {
  let mut peeker = items.peekable();
  match peeker.peek() {
    Some(_) => (),
    None => return (),
  }
  problem_thingy(&mut peeker);
}
```

I expected to see this happen: either continuously have the first item be "peeked" at, or return `()` on the final iteration after exhausting other peeks.

Instead, this happened: compiler panicked with an unbearably large error message. I believe this has to do with allocation and pointer safety with `Peekable`, but I could be way off.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.81.0 (eeb90cda1 2024-09-04)                                                  
binary: rustc                                                                        
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c                                
commit-date: 2024-09-04                                                              
host: x86_64-unknown-linux-gnu                                                       
release: 1.81.0                                                                      
LLVM version: 18.1.7        
```

Backtrace and compiler output are unbearably large for this issue, so I've attached them below.

```
thread 'rustc' panicked at /rust/deps/ena-0.14.3/src/snapshot_vec.rs:199:10:
index out of bounds: the len is 0 but the index is 0
```

[bare_build.txt](https://github.com/user-attachments/files/17271473/bare_build.txt)
[backtrace_build.txt](https://github.com/user-attachments/files/17271476/backtrace_build.txt)



</p>
</details>
Repository: Python
Issue: LZ78 compression algorithm is missing
Labels: enhancement

### Feature description

LZ78 compression algorithm is not implemented in compression algorithms.
Repository: Python
Issue: computer_vision README.md link not working
Labels: awaiting triage

### What would you like to share?

this link in computer vision readme is not working
https://www.datarobot.com/blog/introduction-to-computer-vision-what-it-is-and-how-it-works/

### Additional information

the article seems removed from datarobot website. i can't find the actual link.