sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Walkthrough doesn't truncate steps properly
Labels: polish,getting-started

See "Command Pale."

![Image](https://github.com/user-attachments/assets/058552ba-67d5-41ed-a654-eac047340cb2)

It should say "Command Pal..." or "Command..." (to align padding with when you click it.

![Image](https://github.com/user-attachments/assets/94b94a39-25cd-4ee3-a015-36d85c66d0e0)
Repository: vscode
Issue: "No accounts requested yet..." disabled menu item?
Labels: bug,polish,authentication

On a new install I see this entry at the bottom of the accounts menu:

![Image](https://github.com/user-attachments/assets/b6a6b7b1-8b0b-4629-a159-ae4abbdc12fa)

On my main instance I don't see a menu item at the bottom, so why do we need/want a disabled item there?
Repository: react
Issue: [React 19] [bug] SVG with dangerouslySetInnerHTML content does not trigger first click
Labels: Type: Bug,React 19

## Summary

Hi all,

Here is the scenario that we found out while testing with both the latest rc and the beta that works correctly with React 18.
We have an SVG element that does not trigger its first click if it is focusable (or positioned inside a focusable element) that changes some state on focus.

**Steps to reproduce:** 
Open the Stackblitz example and open its console
Click 1 time on the triangle svg element
**Expected**:
'svg click' message is logged
**Current**: 
no message is logged

(On the second and all next clicks the message is shown as expected - only the first click is not triggered)
**Here are the stackblitz examples where the issue can be observed:**
rc: https://stackblitz.com/edit/react-vsxt51-w3ktmp?file=app%2Fapp.tsx - not working
beta: https://stackblitz.com/edit/react-vsxt51-ssqptj?file=app%2Fapp.tsx - not working
**And here is how it is working in React 18:**
React 18: https://stackblitz.com/edit/react-vsxt51-xsg1yu?file=app%2Fapp.tsx - working


**Code**:

```
const App = () => {
  const [focused, setFocused] = React.useState(false);
  const handleFocus = () => {
    setFocused(true);
  };

  return (
    <svg
      onFocus={handleFocus}
      tabIndex={1}
      onClick={() => {
        console.log('svg click');
      }}
      viewBox="0 0 512 512"
      dangerouslySetInnerHTML={{
        __html: '<path d="M256 352 128 160h256z" />',
      }}
    ></svg>
  );
};
```
Repository: opencv
Issue: DNN config file (Caffe, Darknet) are not downloaded with download_modeles.py
Labels: bug,category: samples

### System Information

OpenCV 5.x, dnn samples

### Detailed description

Current download_models.py implementation + alias strategy in dnn samples allows not touch model files, but download models and run them automatically. It does not work for yolov4, for example. download_models.py loads just weights, but not config. I propose to download config with download_models.py too.

### Steps to reproduce

-

### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: pytorch
Issue: Compatibility with numpy 2 __array__ interface
Labels: triaged,module: numpy

### 🐛 Describe the bug

PyTorch Tensors do not implement all features of the `__array__` interface introduced in NumPy 2, resulting in deprecation warnings for simple operations. For example, running the below code:
```python
import numpy as np
import torch

x = torch.tensor([1, 2, 3])
y = np.array([1, 2, 3])
z = np.array(x)
x + y
```
results in:
```console
> python test.py
test.py:6: DeprecationWarning: __array__ implementation doesn't accept a copy keyword, so passing copy=False failed. __array__ must implement 'dtype' and 'copy' keyword arguments.
  z = np.array(x)
test.py:7: DeprecationWarning: __array_wrap__ must accept context and return_scalar arguments (positionally) in the future. (Deprecated NumPy 2.0)
  x + y
```
These kinds of interactions are required for other libraries like matplotlib to smoothly plot tensors, among other things.

@rgommers 

### Versions

* torch: 2.4.1
* numpy: 2.1.1

cc @mruberry @rgommers
Repository: tauri
Issue: [bug] Titlebar shows when it should not
Labels: type: bug,platform: Windows,status: needs triage

### Describe the bug

tauri v2 with Nuxt v3

so I want to create full monitor confetti:

somewhere in the code:
```ts
const webview = new WebviewWindow('confetti', {
  url: '/confetti',
  transparent: true,
  decorations: false,
  alwaysOnTop: true,
  focus: false,
  fullscreen: true,
  shadow: false,
  skipTaskbar: true,
})
```

confetti.vue:
```vue
<template>
</template>

<script lang="ts" setup>
import { getCurrentWindow } from "@tauri-apps/api/window";

definePageMeta({
  layout: false,
});

const { proxy } = useScriptNpm({
  packageName: 'js-confetti',
  file: 'dist/js-confetti.browser.js',
  version: '0.12.0',
  scriptOptions: {
    //@ts-ignore
    use: () => typeof window.JSConfetti !== 'undefined' && new window.JSConfetti()
  },
})

getCurrentWindow().setIgnoreCursorEvents(true)

onMounted(async () => {
  proxy.addConfetti({
    confettiRadius: 6,
    confettiNumber: 500,
  })

  setTimeout(() => {
    getCurrentWindow().close()
  }, 3000);
})
</script>
```

but as soon as I "interact" with the window (obviously I click through (tested this) and even if something on another monitor is interacted with) this happens:

https://github.com/user-attachments/assets/788f4d39-3e44-4f99-a9f3-815e009af870

the "titlebar" appeared as soon as I clicked (titlebar is not interactable)


### Reproduction

Create a tauri app with nuxt and paste in the code from above (`@nuxt/scripts` package is required)

### Expected behavior

No titlebar it should just stay invisible

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22635 x86_64 (X64)
    ✔ WebView2: 128.0.2739.79
    ✔ MSVC:
        - Visual Studio Build Tools 2022
        - Visual Studio Community 2022
    ✔ rustc: 1.80.1 (3f5fd8dd4 2024-08-06)
    ✔ cargo: 1.80.1 (376290515 2024-07-16)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default) 
    - node: 20.10.0
    - pnpm: 9.0.2
    - npm: 10.8.3
    - bun: 1.1.27

[-] Packages
    - tauri 🦀: 2.0.0-rc.15
    - tauri-build 🦀: 2.0.0-rc.12
    - wry 🦀: 0.43.1
    - tao 🦀: 0.30.0

[-] Plugins
    - tauri-plugin-sql 🦀: 2.0.0-rc.2

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:3000/
```


### Stack trace

_No response_

### Additional context

support on discord said I should open a ticket
Repository: PowerToys
Issue: Can't extract text from Snip and Sketch screengrab
Labels: Issue-Bug,Needs-Triage,Product-Text Extractor

### Microsoft PowerToys version

0.84.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

TextExtractor

### Steps to reproduce

Open a Snip and Sketch screengrab
Win+Shift+t  a selection to extract the text and the popup menu does not go away, you can't extract the text from the screengrab

### ✔️ Expected Behavior

Pop up menu disappears and extracted text is in the clipboard

### ❌ Actual Behavior

Pop up menu stays

### Other Software

Snip and Sketch 10.2008.3001.0
Repository: PowerToys
Issue: PowerToys Window Masking
Labels: Needs-Triage

### Description of the new feature / enhancement

This feature would allow users to mask specific windows from being captured by screen recording, screenshot, and screen sharing tools.

### Scenario when this would be used?

PowerToys Window Masking would enable users to selectively hide windows from capturing tools by:

- Window Name Matching: Users can define specific window names or parts of names to mask. This allows for flexibility in masking windows with dynamic names (e.g., "Untitled - Notepad" or "Discord - [Username]").

- Hotkeys: Users can assign hotkeys to instantly mask or unmask specific windows. This allows for quick and easy control during live screen sharing or recording.

### Supporting information

PowerToys Window Masking provides users with increased privacy and control over their on-screen activities:

- Protecting Sensitive Information: Mask windows containing personal data, passwords, or other sensitive information during screen recordings or screen shares.

- Hiding Distractions: Mask irrelevant windows during live screen sharing to focus on the important content.

- Maintaining Privacy during Collaboration: Mask windows containing private projects or communications during screen sharing with colleagues.

- Controlling Personal Information: Mask windows displaying personal messages or chats during screen recording.

This feature allows users to confidently share their screen while ensuring privacy and maintaining control over what is visible to others.
Repository: rust
Issue: Tracking issue for unsafe binder types
Labels: T-lang,C-tracking-issue,B-experimental

This is a tracking issue for unsafe binder types. See https://hackmd.io/@compiler-errors/HkXwoBPaR for an initial design proposal.

The feature gate for the issue is `#![feature(unsafe_binders)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.  They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.  A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.  Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

- [x] Approve as lang experiment.
  - We accepted this in the lang triage meeting on 2024-09-18.
- [ ] Accept an RFC.
- [ ] Implement in nightly.
  - https://github.com/rust-lang/rust/pull/130514
- [ ] Add documentation to the [dev guide][].
  - See the [instructions][doc-guide].
- [ ] Add documentation to the [reference][].
  - See the [instructions][reference-instructions].
- [ ] Add formatting for new syntax to the [style guide][].
  - See the [nightly style procedure][].
- [ ] Stabilize.
  - See the [instructions][stabilization-instructions].

[dev guide]: https://github.com/rust-lang/rustc-dev-guide
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[edition guide]: https://github.com/rust-lang/edition-guide
[nightly style procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md
[reference]: https://github.com/rust-lang/reference
[reference-instructions]: https://github.com/rust-lang/reference/blob/master/CONTRIBUTING.md
[stabilization-instructions]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[style guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions

TODO.

### Related

TODO.

cc @compiler-errors @rust-lang/lang
Repository: stable-diffusion-webui
Issue: [Bug]: Some malicious extension is getting installed automatically after making 10K+ calls to Stable diffusion model through the API.
Labels: bug-report


[sd.txt](https://github.com/user-attachments/files/17046338/sd.txt)
[sd.txt](https://github.com/user-attachments/files/17046338/sd.txt)
### Checklist

- [ ] The issue exists after disabling all extensions
- [ ] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [ ] The issue exists in the current version of the webui
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

When we made 10K calls to generate different images we observed that a new extension with URL "http://77.90.22.129:3000/WCZMKQKVIQ/na8672" is getting installed.
![SD Extensions](https://github.com/user-attachments/assets/c866289f-0582-4eb1-9adf-05af79d9ad16)


### Steps to reproduce the problem

1. Install Stable Diffusion.
2. Install following Extensions:
   A. https://github.com/Mikubill/sd-webui-controlnet
   B. https://github.com/AUTOMATIC1111/stable-diffusion-webui-nsfw-censor
   C. https://github.com/w-e-w/sd-webui-nudenet-nsfw-censor
3. Try making 10K calls to Stable diffusion using the endpoint: sdapi/v1/txt2img

### What should have happened?

The malicious extension shouldn't have been installed automatically.

### What browsers do you use to access the UI ?

Google Chrome

### Sysinfo

[sysinfo-2024-09-18-15-03.json](https://github.com/user-attachments/files/17046063/sysinfo-2024-09-18-15-03.json)


### Console logs

```Shell
Attached in files section.
```


### Additional information

We have deployed it on K8s on a pod using a Dockerfile.
Repository: deno
Issue: deno run + tab does not offer file autocompletion using zsh
Labels: bug,needs info

Related https://github.com/denoland/deno/issues/13593
Version: Deno 1.46.3

In a shell type:

`deno run` and hit tab and you will see something like this:

![image](https://github.com/user-attachments/assets/c06926fe-24e9-4f37-8115-3a16ff6b6228)
Repository: pytorch
Issue: [triton x pt2] Dynamo should trace data_ptr accesses
Labels: triaged,oncall: pt2,module: dynamo,module: user triton

internal xref: https://fb.workplace.com/groups/1075192433118967/permalink/1505159356788937/

The motivation is that people commonly pack data ptrs into a tensor and then pass the tensor to a triton kernel. This pattern is used to implement triton kernels that take in variable-length lists.

Dynamo graph breaks on data_ptr calls and FakeTensor chokes on it if it gets past Dynamo.

Our options are:

1) add a get_data_ptrs operator to construct said variable-length list
2) get Dynamo to trace code involving data_ptr access

cc @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @rec @oulgen @aakhundov
Repository: deno
Issue: Adopt GB18030-2022
Labels: feat,web,fix available

If you implement gb18030/GBK, see https://github.com/whatwg/encoding/pull/336.
Repository: node
Issue: Adopt GB18030-2022
Labels: icu,web-standards

If you implement gb18030/GBK, see https://github.com/whatwg/encoding/pull/336.
Repository: pytorch
Issue: AOTDispatcher debug mode
Labels: triaged,oncall: pt2,module: aotdispatch,module: pt2-dispatcher

(from discussion with @bdhirsh and @ezyang)

Motivation: AOTDispatcher (and it's interaction with HOPs) is generally difficult to understand. The claim is that the complexity is around the PyTorch dispatcher applying successive transforms: we apply Autograd, subclass handling, Functionalization, in that order, but "all at the same time": it materializes one FX graph where these transforms have been applied. Developers who work with AOTDispatcher need to understand the sequence of dispatch and keep it around in their heads.

Pitch: Instead, we should offer a debug mode that applies each transform to a graph. For example:
- we would trace out a joint graph that operates on Tensor subclasses
- then we would re-trace that graph to produce another joint graph that doesn't involve Tensor subclasses
- next we would re-trace the previous graph to produce a joint graph that is functionalized.
- finally we would apply the decomposition table.

The presence of the intermediate graphs lets developers see how the successive transforms work improve debuggability. An analogy is that in TORCH_LOGS, we let people see the FX graph at different stages of torch.compile; it would be difficult to debug if the only graph we materialized was Inductor's output_code.


cc @ezyang @chauhang @penguinwu @bdhirsh
Repository: pytorch
Issue: Please offer `<version>+cpu`-versioned packages for MacOS and linux ARM CPU-only builds
Labels: oncall: releng,triaged

### 🚀 The feature, motivation and pitch

This is a duplicate of this issue: https://github.com/pytorch/pytorch/issues/110004 , which was closed as implemented w/ a note that it should be reopened if we continue to see issues.

Apologies if there is already an open issue for this, I searched around but wasn't able to find one.

Currently the behavior when trying to use the CPU-only builds hosted at https://download.pytorch.org/whl/cpu with Poetry is as follows:

If I declare a torch dependency in my `pyproject.toml` as follows:
```toml
[tool.poetry.dependencies]
torch = { version = "2.4.1", source = "torch-cpu" }

[[tool.poetry.source]]
name = "torch-cpu"
url = "https://download.pytorch.org/whl/cpu"
priority = "explicit"
```
Running `poetry install` will fail on MacOS and Linux machines using an ARM processor saying it cannot find an installation candidate. What happens is that when poetry resolves dependencies with `poetry lock`, it will only resolve one version. When it looks at the pytorch CPU builds index, it finds `2.4.1+cpu` and treats it as the highest version, and does not consider `2.4.1` as the same version. However, when I look at the actual files in the index, they look like:
```
torch-2.4.1+cpu-cp310-cp310-linux_x86_64.whl
torch-2.4.1+cpu-cp310-cp310-win_amd64.whl
...
torch-2.4.1-cp310-cp310-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
torch-2.4.1-cp310-none-macosx_11_0_arm64.whl
...
```
So the wheels are available for these two platforms, they just don't have the `+cpu` portion appended to the version number and so poetry treats them as different, and in fact cannot resolve the mac and arm linux ones because it always finds `*+cpu` to be the highest version number and doesn't consider the other files to be part of that version.

Obviously part of this is a few pieces of less than ideal behavior from poetry, but there have been a bunch of discussions in their repo related to this and it doesn't sound like any behavior change is forthcoming that will help.

It's also possible that I'm not totally understanding the initial resolution in the issue I linked to above. That indicates that this should work after torch 2.1, but looking back at the CPU wheels I don't see any time when the macos and arm linux wheels were published with `+cpu` so it's possible that I'm missing some existing way of making this work (though it's definitely not for lack of trying)

### Alternatives

The alternative is to use direct URLs to the wheels for each platform needed. This isn't too bad, but it would be really nice to be able to upgrade without needing to go copy and paste several URLs (especially when using multiple packages e.g. `torch` and `torchvision`)

### Additional context

_No response_
Repository: PowerToys
Issue: Mouse Without Borders loses 'wrap mouse' state after disable/enable
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Config MWB with 2 machines
Disable Wrap mouse feature
Disable MWB using On/Off toggle
Re-enable MWB
Wrap mouse will functionally be enabled however will display as disabled
(toggling 'wrap mouse' works around)

### ✔️ Expected Behavior

Wrap mouse will functionally match the displayed state, and match the previous state before disable toggline MWB

### ❌ Actual Behavior

Wrap mouse will functionally be enabled however will display as disabled

### Other Software

_No response_
Repository: excalidraw
Issue: Quick switch between shapes (rect <-> circle, etc.)
Labels: UX/UI

Add the ability to switch between different shapes quickly, keeping the original shape style and bound text size.

The current way of doing this includes a lot of manual steps:

- turn on snapping and create a new shape of a similar size
- copy the styles from the original shape and paste the style into the new shape
- unbind text from the original shape and bind it to the new shape (usually the size of the bound text is different than the built-in size)

Instead, changing from rect <-> circle/diamond should be doable with a single user action, for all the selected elements.

Related discussion #8277
Repository: storybook
Issue: [Bug]: ToolbarMenuListItem.tsx is missing __suppressDeprecationWarning for <Icons>
Labels: bug,needs triage

### Describe the bug

This line of code:
` const Icon = icon && <Icons style={{ opacity: 1 }} icon={icon} />;`

Should have been:
` const Icon = icon && <Icons style={{ opacity: 1 }} icon={icon} __suppressDeprecationWarning={true} />;`

Like in `ToolbarMenuButton.tsx`:
` {icon && <Icons icon={icon} __suppressDeprecationWarning={true} />} ` 

Otherwise I get a very annoying warning in my console, like this:

![image](https://github.com/user-attachments/assets/041b3264-716c-41aa-ad59-c106aed4cb3e)


### Reproduction link

https://github.com/storybookjs/storybook/blob/next/code/addons/toolbars/src/components/ToolbarMenuListItem.tsx

### Reproduction steps

Go to this file: https://github.com/storybookjs/storybook/blob/next/code/addons/toolbars/src/components/ToolbarMenuButton.tsx

Read the comment:
```
// We can't remove the Icons component just yet because there's no way for now to import icons
// in the preview directly. Before having a better solution, we are going to keep the Icons component
// for now and remove the deprecated warning.
```

Read the code:
```
{icon && <Icons icon={icon} __suppressDeprecationWarning={true} />}
```

Go to this file:
https://github.com/storybookjs/storybook/blob/next/code/addons/toolbars/src/components/ToolbarMenuListItem.tsx

There is no comment to read.
And the code is:
```
const Icon = icon && <Icons style={{ opacity: 1 }} icon={icon} />;
```

It's missing the `__suppressDeprecationWarning`.

### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 10 10.0.19045
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i7-1360P
  Binaries:
    Node: 20.13.1 - C:\Program Files\nodejs\node.EXE
    npm: 10.8.3 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers:
    Edge: Chromium (127.0.2651.74)
  npmPackages:
    @storybook/addon-a11y: ^8.3.1 => 8.3.1
    @storybook/addon-essentials: ^8.3.1 => 8.3.1
    @storybook/addon-toolbars: ^8.3.1 => 8.3.1
    @storybook/react-vite: ^8.3.1 => 8.3.1
    @storybook/theming: ^8.3.0 => 8.3.1
    storybook: ^8.3.0 => 8.3.1
```


### Additional context

_No response_