sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Keyboard Manager: Unable to select specific app for remapping shortcut
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.77.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

When remapping a shortcut, nothing populates if you try to type into the target app field.

### ✔️ Expected Behavior

A list of apps to show as I type, like an active filter for me to select the app.

### ❌ Actual Behavior

The field is focused, and I am able to type into it, but nothing happens.
<img width="1046" alt="keyboard-manager" src="https://github.com/microsoft/PowerToys/assets/28600190/d6cf6c07-2829-46df-9198-a47989566c6f">


### Other Software

_No response_
Repository: transformers
Issue: Add [VMamba] model
Labels: New model

### Model description

VMamba is a visual foundation model proposed in https://arxiv.org/pdf/2401.10166.pdf.

It is inspired by the recent advances in state stace models and in particular Mamba. The proposed architecture is computationally more efficient than vision transformer architectures because it scales linearly with growing resolution. It introduces a Cross-Scan Module (CSM) to have context from all directions (4 directions, starting in each corner and traversing in a horizontal or vertical direction). Evaluation on vision perception tasks shows promising capabilities.

Model weights will become available in a few days according to the repo of the authors.

1.  [x] (Optional) Understood theoretical aspects

2.  [x] Prepared transformers dev environment

3.  [x] Set up debugging environment of the original repository

4.  [x] Created script that successfully runs forward pass using
    original repository and checkpoint

5.  [x] Successfully opened a PR and added the model skeleton to Transformers

6.  [x] Successfully converted original checkpoint to Transformers
    checkpoint

7.  [x] Successfully ran forward pass in Transformers that gives
    identical output to original checkpoint

8.  [x] Finished model tests in Transformers

9.  [ ] ~~Successfully added Tokenizer in Transformers~~

10. [x] Run end-to-end integration tests

11. [x] Finished docs

12. [ ] Uploaded model weights to the hub

13. [x] Submitted the pull request for review

14. [ ] (Optional) Added a demo notebook


I am opening the issue to avoid duplicate work. My main motivation for porting this model is to learn a bit more about it (and about the internals of 🤗 Transformers). Some of you probably know this library much better than me, so feel free to write your own implementation if you can do it better or quicker. Otherwise, don’t hesitate to build on top of my fork.

### Open source status

- [X] The model implementation is available
- [x] The model weights are available

### Provide useful links for the implementation

- Original repo: https://github.com/MzeroMiko/VMamba
- Paper: https://arxiv.org/pdf/2401.10166.pdf
- implementation in progress: 
- youtube vmamba vs vision mamba: https://www.youtube.com/watch?v=RtHDu6kFPb8
- vision mamba paper (similar idea): https://arxiv.org/pdf/2401.09417.pdf
Repository: storybook
Issue: [Documentation]: JSDocs Props comments are not shown in canvas in Mono repository
Labels: documentation,angular,argtypes

### Describe the problem

Having an angular mono repository like this

```
root: Containing storybook in node-modules folder
|-> projects/my-library: Containing library code with the js doc component
|-> projects/my-storybook: Containing storybook stories

```

The Description and Default values are not visible in docs.



### Additional context

Solution: Make sure that the `.storybook/tsconfig.json` includes also the library folder: 

```
  "include": ["../projects/my-storybook/src/**/*", "./preview.ts", "../projects/my-library/src/**/*"],
```


We should document that somewhere.
Repository: pytorch
Issue: torch.combinations dies with "numel: integer multiplication overflow"
Labels: triaged,module: int overflow

### 🐛 Describe the bug

The follow code:
```
import torch
torch.combinations( torch.arange(26), r=22 )
```
Dies with the following error:
```
RuntimeError: numel: integer multiplication overflow  
```
This has to be due to inefficient implementation as the number of combinations is actually not that large (only around 15K) and the following code which produces the same combinations but inverted works without any problem:
```
import torch
torch.combinations( torch.arange(26), r=4 )
```


### Versions

Latest Stable 2.1.2 includes this problem, and the bug dates back at least until 1.13
Repository: vscode
Issue: Zero width character highlighting broken for emojis containing ZWJs
Labels: under-discussion,unicode-highlight

Type: <b>Bug</b>

In the following snippet, VS Code reports no ZWJ characters.

```js
"🧑‍🦰"
```
In this snippet, VS Code reports an invisible char (ZWJ) right in front of the emoji.

```js
"🧑‍🦰1"
```

Really, either both should report the ZWJ (bad), or neither (good). In both cases the ZWJ is part of a valid emoji sequence (Person + ZWJ + Red Hair).

![image](https://github.com/microsoft/vscode/assets/7829205/772e372b-2265-4248-8396-0e9ff259af86)


VS Code version: Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:47:11.635Z)
OS version: Linux x64 6.6.6-76060606-generic
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 9 5900X 12-Core Processor (24 x 3738)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<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>video_decode: enabled<br>video_encode: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|1, 1, 1|
|Memory (System)|62.71GB (32.39GB free)|
|Process Argv|--unity-launch --crash-reporter-id a03fc28b-9e8b-4dad-84b3-98190fa0feef|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|pop|
|XDG_CURRENT_DESKTOP|Unity|
|XDG_SESSION_DESKTOP|pop|
|XDG_SESSION_TYPE|x11|
</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
vsclangdc:30486549
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30933248
pythongtdpath:30769146
i26e3531:30792625
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019acf:30933242

```

</details>

<!-- generated by issue reporter -->
Repository: PowerToys
Issue: FancyZones - Zone behavior enhancements : mouse button rebinding, and initial mode selection
Labels: Idea-Enhancement,Product-FancyZones,Cost-Medium

### Description of the new feature / enhancement

### Mouse button rebinding

For the options "Use non-primary mouse button to toggle zone activation" and "Use middle-click mouse button to toggle multiple zones spanning", allow users to rebind these keys arbitrarily, or just swap them around, so as to (de)activate zones with middle mouse button, and (de)activate multizone spanning with the right mouse button.

### Initial mode selection

Add the option to activate zones as soon as any window starts to move, instead of having to press the right mouse button or hold down shift to activate. In this event, the right mouse button would toggle as normal, and the shift button would turn off zones while being held down, the inverse of the current behavior.

### Scenario when this would be used?

For the second part, personally, the vast majority of window move and resize operations land on a zone, and i rarely if ever move windows without wanting them in a particular zone. This would simplify this workflow by eliminating an additional buttonpress every time a window is moved. 

It would also free up the right mouse button for the first part:

by splitting the workspace into a, for example, 12x2 grid of zones, we can span to any arbitrary setup, which is what the spanning feature was intended for. 
My problem with it is that the middle mouse button is awkward to press while holding the left mouse button, since i usually do both with the index finger, so have to use my middle finger, which is very uncomfortable and almost painful.
Being able to switch the spanning and zone toggle buttons would make the action much more ergonomic, especially if zones autoactivate (no need to hold down Shift)

### Supporting information

_No response_
Repository: PowerToys
Issue: FancyZones - Allow separate opacity values for each fill color when in custom color mode
Labels: Needs-Triage

### Description of the new feature / enhancement

In FancyZones, Zone appearance submenu, there is a single slider determining the opacity of both Highlight and Inactive colors. Split this slider into two separate ones, each governing its own fill color.

### Scenario when this would be used?

The current design disallows the common pattern of inactive items being (nigh-)transparent, and activated items being noticeably more opaque. Currently, the closest thing the system allows is to slightly darken inactive zones and slightly lighten highlighted zones (low-ish opacity, black inactive, bright highlight).

My preferred layout would be 0% opacity inactive zones, with a middling opacity white highlight color, so i can clearly see which windows are currently open and where, without having to look through the fog of a low opacity black layer on top of the open windows

### Supporting information

_No response_
Repository: next.js
Issue: Compilation error for Next 14.1.0 and p5.js 1.9.0
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/dry-tree-rnzjq9

### To Reproduce

1. access the `sandbox`. The code will run and a page will appear.


### Current vs. Expected behavior

Expected result: 

- a page with a 400x400 canvas where a little ball bounces off the walls

Observed:

- a compilation error:

```sh
$ next dev
   ▲ Next.js 14.1.1-canary.1
   - Local:        http://localhost:3000

 ✓ Ready in 2.2s
 ○ Compiling / ...
 ⨯ ./node_modules/p5/lib/p5.min.js
Module parse failed: Identifier 'o' has already been declared (7314:37)
|                             if (g ? x || (d = !0, w(), x = !0) : d = Boolean(o.first), t = Math.max(0, Math.floor(t)), r = Math.max(0, Math.floor(r)), d) {
|                                 if (!a) throw new Error("First frame must include a { palette } option");
>                                 var [o, h, f, p, m = 8] = [
|                                     v,
|                                     t,

Import trace for requested module:
./node_modules/p5/lib/p5.min.js
./app/p5-error.tsx
 ⨯ ./node_modules/p5/lib/p5.min.js
Module parse failed: Identifier 'o' has already been declared (7314:37)
|                             if (g ? x || (d = !0, w(), x = !0) : d = Boolean(o.first), t = Math.max(0, Math.floor(t)), r = Math.max(0, Math.floor(r)), d) {
|                                 if (!a) throw new Error("First frame must include a { palette } option");
>                                 var [o, h, f, p, m = 8] = [
|                                     v,
|                                     t,

Import trace for requested module:
./node_modules/p5/lib/p5.min.js
./app/p5-error.tsx
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: ENOENT: no such file or directory, rename '/workspace/.next/cache/webpack/client-development-fallback/0.pack.gz_' -> '/workspace/.next/cache/webpack/client-development-fallback/0.pack.gz'
```

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
> NOTE: this is a CodeSandbox machine

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 14.1.1-canary.1
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


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

Not sure

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

next dev (local), next build (local)

### Additional context

The error only appeared with the `14.1.0` and the `canary` versions. 

Version `14.0.4` was fine.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Inpaint color correct original image
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

When using the inpaint color correction setting, it matches the inpainted area to the source image. However, sometimes it's useful (especially when inpainting "Not maked area") to use the generated image as source, and color match the part kept from the original image.

### Proposed workflow

1. Use img2img
2. Use inpaint
3. Have toggle "Match colors of the source image to those of the generated image.
4. Generated image


### Additional information

_No response_
Repository: storybook
Issue: [Bug]: cursor jumps to end of input when editing, when using `useArgs`
Labels: bug,args,addon: controls,sev:S3

### Describe the bug

When using `useArgs` in a story, with the `value` prop of a simple `<input>` in the `args`, editing the input in the middle causes the cursor to move to the end.

Using `React.useState` instead `useArgs`, the cursor behaves normally. (but then the SB controls won't be updated when editing the input field.)

Also on the Docs page, the non-primary stories' `<input>` fields cannot be edited _at all_. 

### To Reproduce

https://stackblitz.com/edit/github-4dcmyf?file=src%2Fstories%2FTextField.stories.jsx&preset=node

```jsx
export const TextField = (props) => <input {...props} />;

export const UseArgs = {
  render: () => {
    const [args, setArgs] = useArgs();
    return (
      <TextField
        {...args}
        onChange={(e) => setArgs({ value: e.target.value })}
      />
    );
  },
  args: { value: 'test' },
};


```

### System

Reproduced on 8.0.0-alpha.11 and 7.6.10.

### Additional context

_No response_
Repository: opencv
Issue: cv::cartToPolar does not support inplace processing
Labels: optimization,priority: low,category: core

### Describe the feature and motivation

Currently, [`cv::cartToPolar()`](https://github.com/opencv/opencv/blob/4.x/modules/core/src/mathfuncs.cpp) does not support in-place processing, there is a specific assert
```
void cartToPolar( InputArray src1, InputArray src2,
                  OutputArray dst1, OutputArray dst2, bool angleInDegrees )
{
    CV_INSTRUMENT_REGION();

    CV_Assert(src1.getObj() != dst1.getObj() && src1.getObj() != dst2.getObj() &&
              src2.getObj() != dst1.getObj() && src2.getObj() != dst2.getObj());

```

However, I can't see a reason to disallow in-place processing here.
Since the doc tells that input and output must be of the same size and type, and that this is a pixel-per-pixel operation, it should just work.
Is there any strong reason that I missed ?

### Additional context

_No response_
Repository: vscode
Issue: Word wrap indicator
Labels: feature-request,editor-wrapping

<!-- ⚠️⚠️ 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. -->
Hi. I find the word wrap feature too subtle in terms of knowing where it is being applied or not. 
I think it would be a good improvement if there was some special indicator on where word wrap occurs or just setting possible to make that changes color of line, something, please.
Repository: vscode
Issue: improve discoverability of merge editor features
Labels: feature-request,accessibility,merge-conflict,merge-editor

When in a merge editor, it's unclear to a SR user how to take action according to @jooyoungseo. We should include commands that can be taken in the editor help dialog and consider adding a keybinding to resolve the conflict etc. so users don't have to `shift+tab` to the toolbar.

cc @hediet 

![Screenshot 2024-01-19 at 8 41 30 AM](https://github.com/microsoft/vscode/assets/29464607/ea8e9c04-6c03-468e-b715-ed7f765aae04)
Repository: vscode
Issue: SCM Input - Allow contributing editor context menus
Labels: feature-request,scm

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

The `editor/context` contribution point lets extensions add context menus in editors. I'd also like to contribute a context menu item to the editor used in SCM input. There currently doesn't seem to be a way to do this
Repository: flutter
Issue: Add Documentation on the Cache recipe that is part of the engine_v2 functionality
Labels: team-infra,P2,triaged-infra

### Type of Request

infra task

### Infrastructure Environment

Recipes, specifically engine_v2 cache recipe.

### What is happening?

We need to add some documentation to the repo for the cache.py recipe that is part of engine_v2. It came a little after the original implementation of engine_v2 and need some documentation.

### Steps to reproduce

NA

### Expected results

We should have documentation describing the purpose and functionality of the cache.py recipe.
Repository: material-ui
Issue: [material-ui][Tabs] End scroll button overlaps last tab when it is the initial value
Labels: bug 🐛,component: tabs,package: material-ui,regression

### Steps to reproduce

Link to live example: https://codesandbox.io/p/sandbox/nostalgic-fog-9z6fzy

Steps:
1. Observe the end scroll button overlapping the initially focused tab.


### Current behavior

When the initial `value` is the last tab of a `Tabs` component with a `scrollable` variant the end scroll button overlaps the focused tab.

- With `react-dom` `^18.0.0` using `ReactDOM.createRoot` api (concurrent rendering), this happens but MUCH more intermittently. Hitting refresh on the sandbox demo page a few times will eventually make it happen.
- With `react-dom` `^17.0.0` using legacy `ReactDOM.render` it happens every time.

It seems like it is a race condition between when the scrolling happens and when the scroll buttons are rendered into the dom.

### Expected behavior

The end scroll button shouldn't overlap the focused tab on initial render.

### Context

I am trying to make the UX of Tabs better. It has made it awkward for users to know the tab is even focused.

Pretty confident it was introduced in [5.14.2](https://github.com/mui/material-ui/blob/master/CHANGELOG.md#muimaterial5142) by either:
https://github.com/mui/material-ui/pull/36071
or 
https://github.com/mui/material-ui/pull/38133

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: tabs scrollable focus
Repository: go
Issue: x/build: time out on LUCI Linux/PPC64x builder
Labels: Builders,NeedsFix,arch-ppc64x

```
#!watchflakes
post <- builder ~ `(gotip|go1\.\d\d)-linux-ppc64` && (`test timed out` || `SIGQUIT` || `context deadline exceeded` || `running too slowly` || status == "ABORT") && test != "TestServerReadAfterWriteHeader100Continue/h1"
```
Repository: pytorch
Issue: tanh does not output in range [-1, 1]
Labels: needs reproduction,triaged

### 🐛 Describe the bug

tanh does not output in range [-1, 1]

### Versions

PyTorch version: 2.1.2+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 11 Pro
GCC version: Could not collect
Clang version: Could not collect
CMake version: version 3.27.7
Libc version: N/A

Python version: 3.11.7 (tags/v3.11.7:fa7a6f2, Dec  4 2023, 19:24:49) [MSC v.1937 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.22631-SP0
Is CUDA available: True
CUDA runtime version: Could not collect
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 3070 Laptop GPU
Nvidia driver version: 546.33
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture=9
CurrentClockSpeed=2300
DeviceID=CPU0
Family=198
L2CacheSize=10240
L2CacheSpeed=
Manufacturer=GenuineIntel
MaxClockSpeed=2301
Name=11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
ProcessorType=3
Revision=

Versions of relevant libraries:
[pip3] numpy==1.26.3
[pip3] torch==2.1.2+cu121
[pip3] torchaudio==2.1.2
[pip3] torchvision==0.16.2+cu121
[conda] Could not collect

![image](https://github.com/pytorch/pytorch/assets/12774409/d5bdaf57-a1cc-46b6-af68-4d5ce96563ba)
Repository: svelte
Issue: Svelte 5: Add property change hook
Labels: feature request

### Describe the problem

It was already a pain to enforce consistent internal component state in v4, it's now even harder with v5 because `$effect` will cause infinite loop issues.

`$derived` is _**not**_ going to solve this, it serves a different function entirely.

### Describe the proposed solution

Add a hook that runs on *external* changes to the props, the callback inside will not be an effect so any changes to or normalization of internal state or props should not cause the handler to re-run. E.g.

```js
import { onPropChange } from 'svelte';

let { values, disabled, maxLength } = $props();

onPropChange(e => {
  if (disabled)
    values = [];

  values = values.slice(0, maxLength); // would loop in $effect
});
```

The event object could be supplied with the name of the property that was changed, and maybe even old and new values.

### Importance

would make my life easier
Repository: PowerToys
Issue: After deactivating and reactivating display on multi-monitor machine, some screens are skipped until connections are refreshed.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.77.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

I have a multi-PC multi-monitor set-up with 4 PCs and each multi-monitor PC has one or two to its right as illustrated here:

[1a][1b] [2] [3a][3b][3c] [4]

I notice this most between PC's 2 and 3 above.

For some reason the monitors on PC 3 sometimes lose connection and hibernate - usually one, sometimes both.  In these cases, after turning the monitor(s) on again, PC 3 recognizes them and goes back to 3-screen mode where monitor 3b is the primary (with system tray).

After doing this, if I move the mouse past the left side of 3b, instead of going to 3a as expected, it goes to PC 2.  It's as if screen 3a doesn't exist to MWB.

Opening **PowerToys > Mouse Without Borders > Device layout** and pressing **[ Refresh connections ]** fixes the issue.

### ✔️ Expected Behavior

When I move from screen 3b to 3a, I'd expect the cursor to move to 3a.

### ❌ Actual Behavior

When I try to move the cursor from 3b to 3a, the cursor skips 3a and goes to 2.

When moving back, the cursor moves from 2 to 3b.

### Other Software

_No response_