sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [web] better document the value of multi-threaded rendering; provide examples in the cookbook
Labels: engine,platform-web,c: proposal,P2,e: web_skwasm,team-web,triaged-web

### Use case

I was looking at game engines like Unity and Godot recently, and I noticed that when these engines target the web, they _require_ some technologies, such as `SharedArrayBuffer` (and the associated Cross Origin Isolation). From what I understand, these technologies enable efficient WASM multithreading. (A good primer on this tech is [in this Godot Engine article](https://godotengine.org/article/progress-report-web-export-in-4-3/#single-threaded-web-export).)

Requiring things like `SharedArrayBuffer` brings a problem: they are disabled by default on most servers, and they will probably stay disabled. The thing is, when SharedArrayBuffer is enabled on a page, some pretty basic web things stop working. For example, embedding (such as embedding a YouTube video or an ad). Also, even if you decide to enable it, it's non-trivial on localhost (needs SSH), and hard to impossible on some popular hosting platforms (e.g. GitHub Pages doesn't have that option).

So, on one hand, the fact that Flutter _isn't_ using `SharedArrayBuffer` is great, because you can have Flutter apps and games running on any page, using almost any server config. This could even be a competitive advantage in the casual web game space.

On the other hand, `SharedArrayBuffer` and multithreading might be a low-hanging fruit for optimization that Flutter is currently not using. There's probably a reason why both Unity and Godot require it.

// cc @zoeyfan 

(For context, here are two previous issues mentioning SharedArrayBuffer: https://github.com/flutter/flutter/issues/126351 and https://github.com/flutter/flutter/issues/124334.)

### Proposal

As a developer, I'd like to have the ability to make my Flutter apps/games go faster on the web. Maybe there can be a flag that enables these technologies, so I can make the trade-off decision myself. 

If the Flutter team decides not to explore `SharedArrayBuffer` et al. for the time being, then it would be good to know. At the very least, for games there's the competitive advantage of running anywhere on the web (in contrast to Unity and, [to a lesser extent](https://godotengine.org/article/progress-report-web-export-in-4-3/), Godot), and without the need to configure the server.
Repository: next.js
Issue: Module incorrectly persists between hot updates (HMR) in the browser
Labels: bug,Runtime,linear: next

### Link to the code that reproduces this issue

https://github.com/mswjs/examples/pull/101

### To Reproduce

1. Clone the repo, check out the PR's branch.
2. `pnpm install`.
3. `cd examples/with-next`.
4. `pnpm dev`
5. Open the application URL in the browser.
6. Open the DevTools, select the "Console" tab.
7. Click the "Fetch movies" button on the page. See the list of fetched movies (these are coming from mocks). See _a single_ log output from MSW about the intercepted GraphQL query.
8. Go to `src/mocks/handlers.ts`. Change the payload of the `graphql.query()` handler (e.g. remove any word from a movie title). 
9. Save the changes.
10. Back in the browser, click "Fetch movies" again. 
11. See _two_ logs for the same GraphQL request. 

### Current vs. Expected behavior

## Current behavior

The entire `MovieList` component gets re-rendered a bunch of times on hot update to `handlers.ts`. Re-rendering is expected, but it looks like Next.js re-applies event listeners to the same button multiple times. 

**This is not an MSW issue**. You can log something in the `MovieList` component manually, and see that it re-renders quite a lot. I suspect during those re-renderings, the `onClick` listener gets applied more than it needs to. 

The number of times the listener is excessively applied is directly proportionate to the number of HMR changes issued (e.g. 1 change = 2 listeners; 2 changes = 3 listeners; etc).

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64
  Available memory (MB): 65536
  Available CPU cores: 16
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: 1.22.10
  pnpm: 9.6.0
Relevant Packages:
  next: 15.0.0-canary.121 // Latest available version is detected (15.0.0-canary.121).
  eslint-config-next: N/A
  react: 19.0.0-rc-14a4699f-20240725
  react-dom: 19.0.0-rc-14a4699f-20240725
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Developer Experience, Runtime

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

next dev (local)

### Additional context

_No response_
Repository: pytorch
Issue: `torch.quantile`: `nan` instead of `inf`
Labels: triaged,module: python frontend

### 🐛 Describe the bug

Hello, I stumbled upon this problem with `quantile`:
```pycon
>>> t = torch.tensor([0, torch.inf])
>>> q = torch.tensor([.4, .6])
```
```pycon
>>> for interpolation in ["linear", "lower", "higher", "nearest", "midpoint"]:
...  print(interpolation, ":", t.quantile(q, interpolation=interpolation))
... 
linear : tensor([inf, nan])
lower : tensor([0., 0.])
higher : tensor([inf, inf])
nearest : tensor([0., inf])
midpoint : tensor([nan, nan])
```

One could argue that the last line is "ok" if we decide to make the mid point between `0` and `inf` to be `nan` (which I personally feel is wrong, I would prefer `inf`). But in any case, I think there's no logical reason for the `"linear"` interpolation to change behaviour between `.4` and `.6` quantile.

What do you think?

Cheers!
Elie



### Versions

```pycon
>>> torch.__version__
'2.3.0+cu121'
```

cc @albanD
Repository: yt-dlp
Issue: [YouTube] Better handling of missing channel tabs, and the videos tab specifically
Labels: incomplete,site-enhancement,site:youtube

### 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 reporting that yt-dlp is broken on a **supported** site
- [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 checked that all provided URLs are playable in a browser with the same IP and same login details
- [X] I've checked that all URLs and arguments with special characters are [properly quoted or escaped](https://github.com/yt-dlp/yt-dlp/wiki/FAQ#video-url-contains-an-ampersand--and-im-getting-some-strange-output-1-2839-or-v-is-not-recognized-as-an-internal-or-external-command)
- [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)
- [X] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required

### Region

USA

### Provide a description that is worded well enough to be understood

If you download an empty playlist (with 0 videos), yt-dlp doesn't throw an error. I think that makes the most sense and that behavior should also be used for when a channel doesn't have a tab specified in a URL. So when trying to download `<channel URL>/shorts` on a channel that doesn't have a shorts tab, it shouldn't throw an error and just consider it successfully downloaded... since you technically did successfully download all 0 shorts that were available. A warning could optionally be output to console as well.

Another more specific issue is that Topic channels don't have a videos tab, but they still can have uploaded videos. In this instance, I think yt-dlp should instead try to download the channel's uploads playlist. [Here's a comment describing how a playlist of a channel's uploads can be found](https://github.com/yt-dlp/yt-dlp/issues/9673#issuecomment-2298830799). 

### Provide verbose output that clearly demonstrates the problem

- [X] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [X] 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
This bug is related to the semantics/behavior of yt-dlp
```
Repository: PowerToys
Issue: button to close all tasks instead of doing it one by one for Locksmith
Labels: Needs-Triage

### Description of the new feature / enhancement

In addition to closing tasks one by one, it would also be useful and practical to close all tasks at once with a single button.

### Scenario when this would be used?

Every time you want to move or delete a file and you have to close the associated tasks one by one, this is slow, it will be faster by implementing this option.

### Supporting information

![image](https://github.com/user-attachments/assets/6c4c16a7-92f8-46fc-847a-b6a5fc54f534)
as you can see in this case, closing one by one is tedious and annoying, you could close all tasks with a single button.
Repository: electron
Issue: [Bug]: -webkit-app-region: drag has no effect
Labels: platform/windows,bug :beetle:,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.4.0

### What operating system(s) are you using?

Windows

### Operating System Version

Windows 11

### What arch are you using?

x64

### Last Known Working Electron version

30.4.0

### Expected Behavior

When creating a window with `titleBarStyle: 'hidden'` and an area having the css property `-webkit-app-region: drag;` I expect that the window is draggable on this region.

### Actual Behavior

With version 31.4.0 the window is no longer draggable within this region. It behaves as if the css property was not set.

### Testcase Gist URL

[Git repo with testcase for reproduction](https://github.com/2WeltenChris/electron-draggable-testcase) (see comment below for further information)

### Additional Information

Might be related to #41212.
Repository: pytorch
Issue: associative_scan not composable with vmap in eager-mode
Labels: triaged,module: vmap,oncall: pt2,module: functorch,module: higher order operators,module: pt2-dispatcher

It uses torch.compile(backend=inductor) in eager-mode:
https://github.com/pytorch/pytorch/blob/36376efd06e286ee9514e374b0d5f88c206447b9/torch/_higher_order_ops/associative_scan.py#L79-L83 and we have a limitation that vmap over torch.compile doesn't work unless the backend is "eager"


cc @Chillee @samdow @kshitij12345 @janeyx99 @ydwu4 @penguinwu @bdhirsh @ezyang @chauhang
Repository: PowerToys
Issue: Numbering of windows in use always visible in keyboard shortcut guide
Labels: Product-Shortcut Guide,Needs-Triage

### Description of the new feature / enhancement

the numbering of keyboard shortcuts for the windows that are in use is very useful and practical, but it is necessary to keep the Win key after this always visible, although you could customize the location so that it does not interfere with visibility

### Scenario when this would be used?

For those who use the keyboard a lot to manage between windows is useful the shortcut alt + tab but to be faster and knowing the workflow of each one is better Win + # (number of the window). 

### Supporting information

![image](https://github.com/user-attachments/assets/bb9c2ed1-8eaa-428f-967b-b7af9b814e1f)
Here is an example of how it could look, without having to hold down the key, that is, always in active state
Repository: vscode
Issue: Git - VS Code doesn't show "Merge branch" commits in "Timeline" and shows incorrect diffs for subsequent commits
Labels: bug,git,confirmed

Type: <b>Bug</b>

Here's how I was able to reproduce this.

1. Create a basic HTML document. I left out the `<head>` element for simplicity.

```
<!DOCTYPE html>
<html lang="en">
<body>
</body>
</html>
```

2. Initialize a repository and make the initial commit.
3. Create a branch, switch to that branch, add a `<main>` element, and commit.

```
<!DOCTYPE html>
<html lang="en">
<body>
    <main></main>
</body>
</html>
```

4. Switch to the main branch, add a `<header>` element, and commit.

```
<!DOCTYPE html>
<html lang="en">
<body>
    <header></header>
</body>
</html>
```

5. Merge the main branch with the other branch. Resolve the conflict by putting the `<header>` above the `<main>`. Commit with the default message (`Merge branch 'BRANCH_NAME'`).

```
<!DOCTYPE html>
<html lang="en">
<body>
    <header></header>
    <main></main>
</body>
</html>
```

6. Delete the other branch.
7. Add a `<footer>` element and commit.

```
<!DOCTYPE html>
<html lang="en">
<body>
    <header></header>
    <main></main>
    <footer></footer>
</body>
</html>
```
Two problems appear here.
1. VS Code doesn't show the commit you made after resolving the conflict in "Timeline" in the left sidebar, while `git log` shows it.
2. If you click on the last commit in "Timeline," VS Code says you added `<main>` and `<footer>`, while you actually only added `<footer>`. Running `git diff COMMIT_1 COMMIT_2` returns the correct diffs.

VS Code version: Code 1.92.2 (fee1edb8d6d72a0ddff41e5f71a671c23ed924b9, 2024-08-14T17:29:30.058Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz (8 x 2419)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|7.80GB (1.12GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (18)</summary>

Extension|Author (truncated)|Version
---|---|---
ruff|cha|2024.42.0
vscode-eslint|dba|3.0.10
css-property-sorter|Enz|1.2.3
prettier-vscode|esb|11.0.0
vscode-htmlhint|HTM|1.0.5
rainbow-csv|mec|3.12.0
debugpy|ms-|2024.10.0
python|ms-|2024.12.3
vscode-pylance|ms-|2024.8.1
autodocstring|njp|0.6.1
sourcery|sou|1.22.0
vscode-stylelint|sty|1.4.0
errorlens|use|3.20.0
intellicode-api-usage-examples|Vis|0.2.8
vscodeintellicode|Vis|1.3.1
vscode-icons|vsc|12.8.0
five-server|yan|0.3.1
html-css-class-completion|Zig|1.20.0


</details>
<!-- generated by issue reporter -->
Repository: vscode
Issue: Unable to pass `target: Workspace`  to `workbench.action.openSettings2` command
Labels: bug,settings-editor,confirmation-pending

I'm like to pop open the settings editor for a specific setting, but for the current workspace. Eg, this view:

![image](https://github.com/user-attachments/assets/b337286a-ba19-466e-b47b-e700084c85f8)

I'm using the `workbench.action.openSettings2` command (to force the UI regardless of user settings) and passing a `query`. I'm also passing a `target` (which I found in `ISettingsEditorOptions` alongside `query`), however it seems to be ignored and just opens at the user settings:

```ts
await vs.commands.executeCommand("workbench.action.openSettings2", {
	query: settingName,
	target: vs.ConfigurationTarget.Workspace,
});
```

![image](https://github.com/user-attachments/assets/ee281b05-7e96-47e2-a73b-3caa9da3bff9)

I also tried passing `5` instead of `vs.ConfigurationTarget.Workspace,` because there's another `ConfigurationTarget` enum inside VS Code defined as:

```ts
export const enum ConfigurationTarget {
	APPLICATION = 1,
	USER,
	USER_LOCAL,
	USER_REMOTE,
	WORKSPACE, // 5
	WORKSPACE_FOLDER,
	DEFAULT,
	MEMORY
}
```

However, nothing works. I saw there as a new `vscode://settings/xxx` handler in the latest VS Code, but it doesn't seem to have any option for workspace settings.

Is this a bug? Is there a way to do the equiv of "Open Workspace Settings" and force the UI, and provide a query?
Repository: transformers
Issue: StoppingCriteria for Repetition
Labels: Feature request

### Feature request

similar to repetition_penalty for generation config, but as a stopping criteria.


### Motivation

(small?) models tend to generated endless loops of the same few tokens, or a combination where they only increase like a single digit.  (could not find any similar FRs)

I run into this quite a lot when doing evaluation runs (with greedy decoding) for code completion tasks. here is a screenshot of multiple generations saved to a file. the blocks of repetition can easily be spotted. 
![image](https://github.com/user-attachments/assets/305123b0-5623-4c83-af2c-ab0ff16dd494)

Having a stopping criterion that detects such behaviour would massively speed up evaluation runs, since generation could stop early and not reach the `max_new_token` set. Some parameters might be helpful to expose like number of repetitions, and n-gram overlap for example.

### Your contribution

I am happy to contribute with a PR myself, but will not find the time to do so in the next ~6-8 weeks. It doesn't look straight forward, but I am also not too familiar with the deeper parts of the generation code - so it might take me a while.
Repository: ant-design
Issue: The step element does not highlight on scrollIntoViewOptions: { behavior: 'smooth'}
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/antd-reproduce-5x-kxkrzf?file=demo.tsx)

### Steps to reproduce

The tour component does not highlight the step that is using { behavior: 'smooth'} in scrollIntoViewOptions. It is scrolling to the element but not highlighting the step area.

### What is expected?

The step area should not have the mask over.

### What is actually happening?

The step area is having a mask over.

| Environment | Info |
| --- | --- |
| antd | 5.20.2 |
| React | react |
| System | ubantu 22 |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: `--emit metadata` produces less error messages with some targets
Labels: A-testsuite,A-metadata,T-compiler,C-bug,A-atomic

Hello. I was looking into a UI test failure with the `aarch64-unknown-nto-qnx710` target. (but this is not a QNX specific issue as noted below)

The test is question is [`/tests/ui/structs-enums/enum-rec/issue-17431-6.rs`](https://github.com/rust-lang/rust/blob/a971212545766fdfe0dd68e5d968133f79944a19/tests/ui/structs-enums/enum-rec/issue-17431-6.rs). The contents of the file have been copied below for your convenience.

``` rust
//@ ignore-apple: cycle error does not appear on apple

use std::sync::Mutex;

enum Foo { X(Mutex<Option<Foo>>)  }
//~^ ERROR recursive type `Foo` has infinite size
//~| ERROR cycle detected

impl Foo { fn bar(self) {}  }

fn main() {}
```

The UI test expects the compiler to produce TWO error messages (see `ERROR` comments in the code) but the compiler only produces ONE when the compilation target is `aarch64-unknown-nto-qnx710`.

**NOTE** The issue can also be reproduced without a QNX toolchain on a Linux host using the `aarch64-apple-darwin` target.

I have narrowed down the issue to `compiletest`'s internal use of the `--emit metadata` flag. In other words, `rustc --emit metadata --target aarch64-apple-darwin issue-17431-6.rs` produces ONE error; whereas `rustc --target aarch64-apple-darwin issue-17431-6.rs` (no `--emit` flag) produces the TWO error messages that the UI test expects.

I'm not sure why `--emit metadata` triggers the issue but I suspect that `Mutex` having OS / platform specific implementations (i.e. `cfg`-style conditional compilation is involved) is part of the problem. After all, the error that's not reported is about a cycle being found when computing the layout of `Foo`; the error includes `note`s that list all the types beneath `Foo`: that is `Mutex`, `UnsafeCell`, etc.

A workaround that fixes the UI test (when target = QNX) is to replace the `Mutex` type with `UnsafeCell`, that is

``` rust
use std::cell::UnsafeCell;

enum Foo { X(UnsafeCell<Option<Foo>>)  }
```

This change may let you drop the `ignore-apple` compiletest attribute from the test but I haven't tested this change with an apple target.

Again, I suspect that this modified version does not run into the problem because `UnsafeCell` does NOT have a target specific implementation / layout.

### Meta

`rustc --version --verbose`:
```
rustc 1.82.0-nightly (636d7ff91 2024-08-19)
binary: rustc
commit-hash: 636d7ff91b9847d6d43c7bbe023568828f6e3246
commit-date: 2024-08-19
host: x86_64-unknown-linux-gnu
release: 1.82.0-nightly
LLVM version: 19.1.0
```
Repository: vscode
Issue: Explorer not graying out .gitignore'd files if ignored folders (that are symlinks) are open in the workspace
Labels: bug,file-explorer

<!-- ⚠️⚠️ 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.92.2
- OS Version: Windows 11 23H2

Steps to Reproduce:

1. Open a workspace that has a gitignore'd folder expanded that is also a symlink
2. .gitignore graying out will not apply
3. If you close the folder and re-open the workspace, graying out is applied
Repository: kubernetes
Issue: Default standard request headers for aggregation
Labels: sig/auth,triage/accepted

> In the future (kube-apiserver 1.32+) we can consider making kube-apiserver also include the standard username/groups/extra/uid headers the aggregator uses (which are not configurable) in the configmap it publishes containing auth config, so that aggregation works even if kube-apiserver only set non-standard requestheader flag options

_Originally posted by @liggitt in https://github.com/kubernetes/kubernetes/pull/115834#discussion_r1595742906_

Note: the earliest is now v1.33 because #115834 will not merge until v1.32.