sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Screen readers cannot list or move focus to elements outside of the current viewport
Labels: framework,a: accessibility,platform-mac,platform-windows,platform-web,P2,customer: castaway,team-web,triaged-web

### Steps to reproduce

<p>NVDA, JAWS, and VoiceOver Screen readers cannot list or move focus to elements outside of the current viewport. Any elements that have scrolled out of view or haven't yet been scrolled into view will NOT be reachable via screen reader basic keyboard commands for reading and navigating web content.</p>
<p>Examples:</p>
<div class="table-wrap">

Function | JAWS Shortcut | NVDA Shortcut | VoiceOver Shortcut
-- | -- | -- | --
Next Heading | H, 1-6 for heading level | H, 1-6 for heading level | Control Option Command H
List Headings | Insert F6 | Insert F7 to open Elements list, Select the "Headings" radio button | Control Option U, Press left/right arrow keys until the "Heading" menu is displayed
Next Link | U for unvisited link, V for visited link | K for link, U for unvisited, link V for visited link | Control Option Command L for link, Control Option Command V for visited link
List Links | Insert F7 | Insert F7 to open Elements list, Select the "Links" radio button | Control Option U, Press left/right arrow keys until the "Links" menu is displayed
Next Button | B | B | N/A
List Buttons | Control Insert B | Insert F7 to open Elements list, Select the "Buttons" radio button | Control Option U, Press left/right arrow keys until the "Form Controls" menu is displayed
Next Form Control | F | F | Control Option Command J
Next Table | T | T | Control Option Command T
Next Landmark | R | D | N/A
Next List | L | L | Control Option Command X


</div>

### Expected results

- The "Next" keyboard shortcuts should move the screen reader focus to the next element of that type which exists on the page, not just the elements displayed in the current viewport
- The lists should contain all elements of that type which exist on the page, not just the elements displayed in the current viewport

### Actual results

- The "Next" keyboard shortcuts only move the screen reader focus to the next element of that type which is displayed in the current viewport
- The lists only contain elements of that type which are displayed in the current viewport

### Code sample

N/A

### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

`Flutter (Channel beta, 3.27.0-0.1.pre, on macOS 14.5 23F79 darwin-arm64, locale en-US)`
Repository: godot
Issue: `Area2D` `monitorable`, `monitoring` and `area_enter` logic flaw
Labels: topic:physics,topic:2d

### Tested versions

v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.22621 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU (NVIDIA; 31.0.15.2887) - 13th Gen Intel(R) Core(TM) i7-13700H (20 Threads)

### Issue description

There are two area2d,we call them A and B, make A can check B. make A's area_enter connect to a function to observe.

When they are overlaping, turn A' monitoring(true -> false -> true), A' area_enter will emit. (It is right)

However, turn B' monitorable(true -> false -> true), A' area_enter wouldn't emit. ( I think it should emit)

Additionally, every change on B's monitoring (true -> false or false -> true) will makes A' area_enter  emit.  ( I think it shouldn't emit according to the principle)

I hope that a appropriate change will happen on there and make them liked described.

### Steps to reproduce

1. open the function "display collision area"
2. press "D" until the small area overlap with the big .
3. change B'monitoring and monitorable,then oberve

### Minimal reproduction project (MRP)

[test.zip](https://github.com/user-attachments/files/18120274/test.zip)
Repository: ant-design
Issue: Input 存在 suffix 的情况下 Popover 弹出位置错乱
Labels: 🐛 Bug,help wanted

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/ji-ben-shi-yong-antd-5-22-4-forked-wq79lt?workspaceId=ws_UGUVoYEGqyRdAXEjC2LGE2)

### Steps to reproduce

看重现链接中代码

### What is expected?

Popover 弹出框始终以 Input 元素的包装 dom 节点的位置对其

### What is actually happening?

Popover 弹出框跟Input 内部的原生 input 元素对齐了

| Environment | Info |
| --- | --- |
| antd | 5.22.4 |
| React | 18.3.1 |
| System | MacOS最新 |
| Browser | Chrome最新 |

---
初步猜测存在 suffix 的情况下 Input 组件 ref 的 nativeElement 值不是 Input 的最外层包装节点，而是内部的原生 input 节点

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Add the 'preview' flag to vscode.window.createWebviewPanel
Labels: feature-request,api,webview

<!-- ⚠️⚠️ 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. -->
Add `preview: boolean` to `vscode.window.createWebviewPanel`'s `showOptions `parameter so we can create preview panels that will be automatically closed when another preview editor is opened.

Also needed on:
`WebviewPanel.reveal`

While you're at it, it'd be nicer to have a proper interface rather than having the properties listed in-line:

```
interface ShowOptions {
	readonly viewColumn?: ViewColumn;
	readonly preserveFocus?: boolean;
	readonly preview?: boolean;
}

```
...and then have `TextDocumentShowOptions `and `NotebookDocumentShowOptions` extend that.
Repository: ant-design
Issue: 使用px2remTransformer时，css变量中的px没有被转化
Labels: 🐛 Bug

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/sandpack-project-forked-3zrwyk?file=%2Fapp.tsx)

### Steps to reproduce

![image](https://github.com/user-attachments/assets/9d934c4f-2891-442f-bd1f-2a4b2e4040b8)


见复现链接，我找到了几个相关的issue，但是基本上都被close掉或者没有人回复，这个问题挺影响使用的，希望官方能支持一下或者提供修复方案我可以尝试帮助修复一下
https://github.com/ant-design/ant-design/issues/47748
https://github.com/ant-design/cssinjs/issues/203
https://github.com/ant-design/cssinjs/issues/180

### What is expected?

css变量中的px也能被转化

### What is actually happening?

css变量中的px未能被转化

| Environment | Info |
| --- | --- |
| antd | undefined |
| React | 18 |
| System | ubuntu |
| Browser | Chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: kubernetes
Issue: watcher always terminal
Labels: kind/bug,needs-sig,needs-triage

### What happened?

when is use 
https://xxxxxx/api/v1/pods?timeoutSeconds=10000&watch=true

watcher will terminal

we have 100000 pods

i see #13969

this param will return all pods event

(c *cacheWatcher) processInterval  will exec process func when initEvents send to result success,but is took 5s-6s.
if process func not be exec,watcher  input chan will not have comsumer.

then watcher will be blockedWatcher,when etcd have changed
the func watcher.add(event, timer) will timeout and kill my watcher.

### What did you expect to happen?

watcher keep to timeoutSecond

### How can we reproduce it (as minimally and precisely as possible)?

https://xxxxxx/api/v1/pods?timeoutSeconds=10000&watch=true
100000 pods

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</details>
1.30

### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: kubernetes
Issue: add `matchLabelKeys: ["pod-template-hash"]` in the default `ScheduleAnyway` topology spread
Labels: sig/scheduling,kind/feature,sig/apps,needs-triage

We recently added `matchLabelKeys` feature at [pod topology spread](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/).

Pod topology spread has the [Cluster-level default constraints](https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/#cluster-level-default-constraints);

```yaml
defaultConstraints:
  - maxSkew: 3
    topologyKey: "kubernetes.io/hostname"
    whenUnsatisfiable: ScheduleAnyway
  - maxSkew: 5
    topologyKey: "topology.kubernetes.io/zone"
    whenUnsatisfiable: ScheduleAnyway
```

I was wondering, when it comes to the pods owned by a replicaset controller, would it make sense to consider `matchLabelKeys: ["pod-template-hash"]` there? (I guess such change in the default behavior is allowed, am I right?)

/cc @kubernetes/sig-scheduling-misc @macsko @dom4ha 
/sig scheduling
/kind feature
Repository: deno
Issue: mutation testing
Labels: suggestion,testing

Deno's testing and code coverage support are great and continue to improve. Sometimes developers write code and don't realize their tests don't assert certain things. Sometimes they write tests and they pass but don't realize that they wouldn't fail even if the code under test were changed. We can "test our tests" using methods like [mutation testing](https://en.m.wikipedia.org/wiki/Mutation_testing).

I've seen some tools that automate this for JavaScript (e g. [Stryker](https://stryker-mutator.io/)) but I think these solutions rely on things that don't apply in a Deno context: Babel, CommonJS, etc.

I'd love to see support for mutation testing built-in to Deno or a way to plug in to add the capability. This might be something that would be beneficial to write in Rust (for quickly generating the different code variations, etc.). I could see using code coverage from individual tests to intelligently only run tests that could possibly kill the mutation and not running tests that clearly wouldn't.

If this isn't something worth exploring being built into Deno then I would be interested in getting some pointers on how to build a 3rd partly library to achieve this. I'm imagining the following flow:

- run all tests collecting code coverage for each individual test (not aggregating coverage from all tests)
- if any tests are already failing then there's no point in continuing (although I suppose mutation testing could still be done for code covered by passing tests)
- have a default set of mutation operators to apply to the source code yielding mutants
- for each mutant, re-run the tests that covered the statement before mutation, if any test fails then the mutant is killed and we have coverage otherwise the mutant survives and we don't have meaningful assertions for the statement before mutation
- collect how many mutants survive and report a mutation score of survived vs. generated along with more detailed reporting like code coverage to be able to inspect mutation coverage and understand uncovered code

Additional options would be helpful to expose. Here are some ideas:
- mutation operators: to enable or disable different operators than the default set
- include/exclude filters for code to mutate
- include/exclude filters for tests to run

I think having this built-in (perhaps as an option to `deno test` itself) would provide opportunities to make it perform very well and ease adoption. Code coverage only tells us what code was executed during testing while mutation coverage tells us what code was actually asserted. This can then provide developers much more confidence in their code.
Repository: svelte
Issue: Nested Destructuring of $props()
Labels: feature request

### Describe the problem

I often find myself destructuring $props. In cases such as
```ts
const { index } = $props()
```
This is, as shown, simple and clean. But what if the prop we are destructuring is in itself an object?
```ts
const { suggestion: { id } } = $props()
```
The above does not work, and gives the following error:
> `$props()` assignment must not contain nested properties or computed keys
https://svelte.dev/e/props_invalid_pattern

Instead, we have to destructure in another line, like so:
```ts
const { suggestion } = $props()
const { id } = suggestion
```

### Describe the proposed solution

I would love to know the reasoning behind this not being supported currently. If the issue is reactivity, I believe reactivity can be achieved using $derived or $state and $effect, like so:
```ts
const { suggestion } = $props()
const { id } = $derived(suggestion)
```
which is how it could work under the hood.

So, to state the obvious, my proposed solution is to...allow nested destructuring from $props().

```ts
const { suggestion: { id } } = $props()
```

It can be done in other parts of svelte, albeit without reactivity, and would make a few people's lives a fair bit easier.

### Importance

would make my life easier
Repository: ant-design
Issue: Autocomplete dropdown not moving to next line when there is a textarea with multiple lines
Labels: improvement


### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/h7r72q)

### Steps to reproduce

Look at the Customize Input Component for Autocomplete.

When you type in the next line of the textarea - the dropdown of the Autocomplete stays for the top line. 

### What is expected?

We need to adjust the dropdown underneath the cursor area.

### What is actually happening?

The dropdown stays for the top line

| Environment | Info |
| --- | --- |
| antd | 5.22.4 |
| React | 18.0.0 |
| System | Mac 15.0.1 (24A348) |
| Browser | Chrome Version 131.0.6778.139 (Official Build) (arm64) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: Compiled Autograd + Activation Checkpointing/Offloading
Labels: triaged,oncall: pt2,module: compiled autograd,activation-checkpointing

### 🚀 The feature, motivation and pitch

There's been many issues interested in this topic, so I'm going to use this issue to track the current status.

## Full support
- Checkpointing inside of compiled region i.e. `torch.compile(checkpoint(fn))`
- Reentrant i.e. `checkpoint(fn, use_reentrant=True)` on 2.6+

## Partial support
Eager region checkpointing i.e. `checkpoint(fn)` outside of a torch.compile wrapper
- Non-reentrant i.e. `checkpoint(fn, use_reentrant=False)`: Doesn't error, but no memory savings expected
- Selective i.e. `checkpoint(fn, context_fn=create_selective_checkpoint_contexts(...))`: Doesn't error >2.6.0, but no memory savings expected

## Unsupported
Disk offloading i.e. defining pack_hooks/unpack_hooks using torch.save and torch.load
CPU offloading i.e. defining pack_hooks/unpack_hooks using .cuda() and .cpu()

### Alternatives

_No response_

### Additional context

_No response_

cc @chauhang @penguinwu @yf225
Repository: PowerToys
Issue: Keyboard manager is not working
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.86.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I use Dvorak keyboard layout. So, I map Ctrl-J to Ctrl-C  and Ctrl-K to Ctrl-V.
It would work half of the time and half of other time it just not doing anything.

### ✔️ Expected Behavior

It should always work. And when I pressed Ctrl-J it should do the copy to clipboard as Ctrl-C would

### ❌ Actual Behavior

Ctrl-J still acting like Ctrl-J

### Other Software

Vivaldi | 7.0.3495.26 (Stable channel) (64-bit)
Repository: tauri
Issue: [bug] window randomly restarts and freezes, possibly WASM related
Labels: type: bug,status: upstream,platform: macOS,status: needs triage

### Describe the bug

I am working on an application that uses whisper from transformers.js (which downloadss wasm files), in electron and the browser this issue doesn't exist.

I am not seeing any error messages in the console or in the terminal. 

What I am seeing is that the page randomly refreshes, and sometimes just freezes or freezes to gray, which has me thinking it crashes for an unknown reason. Inspect element is also freezing then.

### Reproduction


```
import { pipeline } from '@huggingface/transformers';
const transcriber = await pipeline('automatic-speech-recognition', 'onnx-community/whisper-base', {
            // dtype: {
            //     encoder_model: 'fp32',
            //     decoder_model_merged: 'fp32',
            // },
            // device: 'webgpu' // not supported in MacOS
    });
```


Just this and wait 10 - 60 seconds, and the app window freezes or restarts.

### Expected behavior

No restarts / crashes

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 15.2.0 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.82.0 (f6e511eec 2024-10-15)
    ✔ cargo: 1.82.0 (8f40fc59f 2024-08-21)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 22.7.0
    - yarn: 1.22.22
    - npm: 10.8.2

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.2
    - tao 🦀: 0.30.8
    - @tauri-apps/api : 2.1.1
    - @tauri-apps/cli : 2.1.0

[-] Plugins
    - tauri-plugin-shell 🦀: 2.2.0
    - @tauri-apps/plugin-shell : 2.2.0
    - tauri-plugin-fs 🦀: 2.2.0
    - @tauri-apps/plugin-fs : 2.2.0
    - tauri-plugin-dialog 🦀: 2.2.0
    - @tauri-apps/plugin-dialog : 2.2.0

[-] App
    - build-type: bundle
    - CSP: default-src 'self' ipc: http://ipc.localhost; img-src 'self' asset: http://asset.localhost; media-src 'self' asset: http://asset.localhost
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

```text
none
```


### Additional context

```
"dependencies": {
    "@huggingface/transformers": "^3.1.2",
    "@tauri-apps/api": "^2",
    "@tauri-apps/plugin-dialog": "~2",
    "@tauri-apps/plugin-fs": "~2",
    "@tauri-apps/plugin-opener": "^1.0.0",
    "@tauri-apps/plugin-shell": "^2",
    "axios": "^1.7.7",
    "tauri-plugin-serialplugin": "^2.4.11",
    "vue": "^3.3.4",
    "vue-router": "^4.4.5"
  },
  "devDependencies": {
    "@tauri-apps/cli": "^2",
    "@vitejs/plugin-vue": "^5.0.5",
    "sass": "^1.81.0",
    "typescript": "^5.2.2",
    "vite": "^5.3.1",
    "vue-tsc": "^2.0.22"
  }
```
Repository: vscode
Issue: SCM - The version-control comment is not DevContainer-specific
Labels: bug,scm

- VS Code Version: 1.69.0 | 92d25e35d9bf1a6b16f7d0758f25d48ace11e5b9 | x64
- OS Version: Linux | 5.15.0-40-generic | 43-Ubuntu SMP | x86_64 GNU/Linux

Steps to Reproduce:

1. Install Remote Development extension
2. Set a `name` for the `devcontainer.json`
3. Get inside the DevContainer
4. Make a commit comment
5. Switch to another DevContainer with a different `name`
6. The same comment for the first container is shown here for the 2nd one

I'm assuming that this is **not** the expected behavior since the `name` is technically identifying the container...
Repository: ant-design
Issue: form.setFieldsValue don't work when trigger twice
Labels: 📝 Documentation

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-jztmdz)

### Steps to reproduce

1. 点击 setValue 按钮
2. Select 选择 2
3. 再次点击 setValue 按钮

### What is expected?

list 的值应该是 1


### What is actually happening?

list 仍然是 2

| Environment | Info |
| --- | --- |
| antd | 5.22.4 |
| React | 18.x |
| System | macOS |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: create-react-app
Issue: Bug: creation reactjs new project latest so v19
Labels: needs triage,issue: bug report

see issue and solution on https://github.com/facebook/react/issues/31701
Repository: godot
Issue: The value format of `_spawnable_scenes` property of `MultiplayerSpawner` in .tscn is different between 4.4.dev3 and 4.4.dev6
Labels: discussion,topic:multiplayer

### Tested versions

- Reproducible in 4.4.dev6 official and 4.4.dev3 official

### System information

Godot v4.4.dev3 - Windows 10.0.22631 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Ti (NVIDIA; 32.0.15.6094) - 13th Gen Intel(R) Core(TM) i5-13600KF (20 threads)

### Issue description

When use 4.4.dev3 and set the property in Node `MultiplayerSpawner`'s `Auto Spawn List`, the saved value in .tscn is like:
```
[node name="Slot1Spawner" type="MultiplayerSpawner" parent="."]
_spawnable_scenes = PackedStringArray("res://player_head.tscn")
```

When use 4.4.dev6 and do the same, the saved value in .tscn is like:
```
[node name="Slot1Spawner" type="MultiplayerSpawner" parent="."]
_spawnable_scenes = PackedStringArray("uid://docb3aisq4txw")
```

Is this supposed to happen? A bug or not? I think using PackedStringArray("res://player_head.tscn") is better than using PackedStringArray("uid://docb3aisq4txw") but I'm not so sure. 

Can an older version Godot understand `_spawnable_scenes = PackedStringArray("uid://docb3aisq4txw")` ? This behavior might **breaks compatibility** which is not mentioned before.

![Image](https://github.com/user-attachments/assets/bb5000ef-de38-4fb3-a730-158d42e69748)


### Steps to reproduce

1. using 4.4.dev3, create a project
2. create a scene
3. add a `MultiplayerSpawner` node
4. edit it's property `Auto Spawn List` then add an element, then choose another scene.
5. save and see the value saved in .tscn file
6. Do the same in 4.4.dev6 and compare .tscn file.

### Minimal reproduction project (MRP)

NA
Repository: ollama
Issue: ollama : /usr/lib64/libstdc++.so.6: version GLIBCXX_3.4.25 not found - Kylin Linux glibc++ version incompatible with official builds 
Labels: bug,linux

### What is the issue?

when run ollama  the error has happend as follow:
ollama : /usr/lib64/libstdc++.so.6: version GLIBCXX_3.4.25 not found

### OS

_No response_

### GPU

_No response_

### CPU

_No response_

### Ollama version

_No response_
Repository: angular
Issue: docs: `HttpRequest` is missing constructor information.
Labels: area: docs-infra

### Describe the problem that you experienced

An API entry like `HttpRequest` should have its constructor signatures (overloaded) display on the API docs. 

ex: https://angular.dev/api/common/http/HttpRequest
Repository: three.js
Issue: NodeMaterial support in Loader
Labels: Loaders

### Description

Add support to NodeMaterial in GltfLoader/Loader in general.

### Solution

Assign node material directly instead of legacy material in Loaders.

### Alternatives

Pass an option to the LoaderManager to return the node or legacy material version ( ex: StandardNodeMaterial / StandardMaterial) . 
Then inside the loader we call this option to get the material class. This way the change can be effective for all loaders quite fast.

### Additional context

From my understanding we're going to an all node material world in threejs. 
In this sense it would be nice to directly got nodeMaterial when loading a 3d model.
I can open a PR if you think it's a good idea.
Repository: excalidraw
Issue: arrow binding indicator should scale with zoom
Labels: bug,Arrow Binding

The binding area indicator when binding an arrow to a shape should scale with zoom. Meaning, on zoom <> 100% it should be visibly identical to 100%.

![Image](https://github.com/user-attachments/assets/bb08a6f7-d1ef-46b7-af41-8a2c1fb4b14d)

incorrect:

![Image](https://github.com/user-attachments/assets/1778078f-1d9a-4934-b47b-fad5b48da5bb)