sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: [Bug]: Duplicated control `id` attributes when using multiple `<Controls>` elements on the same docs page
Labels: bug,good first issue,help wanted,addon: docs,sev:S3

### Describe the bug

We are using Storybook in a docs-only mode (e.g we start it with the `--docs` flag).
We usually add multiple stories in a single `*.mdx` docs file and also at least one `<Controls>` docs block to give our users the possibility to play around with the main story.

But as soon as we add such a docs block more than once, we get some `id` and `for` attribute on the page.
We do not use the `<Controls>` element with the same story context more than once, but only add multiple blocks with different story contextes (e.g. `<Controls of={ComponentStories.StoryA} />` and `<Controls of={ComponentStories.StoryB} />`).

This happens because the attribute `id` is only formed from the `args` key and its value and could be avoided by using the story name or even better by using some on-the-fly generated uuid.

Reproduction:
- Open the url given to reproduce below.
- Inside the second `<Controls>` (argsTable) element on the page, click (for example) on the label `Invalid` of the validity control.

Now you should be able to see that the wrong control has been changed (the one in the first `<Controls>` element) and the one you wanted to change (inside the second `<Controls>` element) has remained as it was.

If you inspect the controls in both tables, you clearly see, the ones from the first and the second table have the same `id` attributes.
The same surly applies to the associated label "for" attribute.

### To Reproduce

https://preview-2260--swisspost-design-system-next.netlify.app/?path=/docs/886fabcf-148b-4054-a2ec-4869668294fb--docs#on-dark-background

### System

```bash
System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
  Binaries:
    Node: 18.19.0 - ~\AppData\Local\pnpm\node.EXE
    npm: 10.2.3 - ~\AppData\Local\pnpm\npm.CMD
    pnpm: 8.9.0 - ~\AppData\Local\pnpm\pnpm.EXE <----- active
  Browsers:
    Edge: Chromium (121.0.2277.128)
```


### Additional context

_No response_
Repository: PowerToys
Issue: Mouse without boarders - remote mouse jitters
Labels: Issue-Bug,Needs-Triage,Product-Mouse Without Borders

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Had to reproduce consistently. Basically, I use mouse without boards between two windows 11 machines. Every once in a while, I get erratic mouse movement on my MS Surface Pro. The mouse starts to jitter or jump around sporadically.  The Keyboard and mouse that I am using is on my main machine and the Surface is the secondary that I am remotely hitting. Just clicking the Apply setting in the Mouse without Boarders icon on the System tray is enough to temporarily fix the issue for a few hours. 

### ✔️ Expected Behavior

My expected behavior would be to not have the mouse start to sporadically jump around and have to refresh or click apply which appears to reset the connections between the machines. 

### ❌ Actual Behavior

The mouse and pointer start jumping on the remote machine and you cannot use the mouse on the second machine. Only work around is to click the Apply and refresh the connections. I do not see any connection errors at the time, and I even manually add the IP addresses for both the host and remote machines. Sometimes it works for hours without issue and other time only a few minutes.  I made sure to turn off any power setting (set to performance) . They are using Wired network connected to the same hub.  Most times on my main machine, I only have Outlook open at the time. Most other common thing I have open is a web browser to do searches.
 
![image](https://github.com/microsoft/PowerToys/assets/53840101/99607a8c-e978-4545-9c58-98b798eee1d3)


### Other Software

Both machines are Windows 11 and up to date, both intel processes.
Repository: transformers
Issue: How to get input embeddings from PatchTST with (batch_size, sequence_length, hidden_size) dimensions
Labels: Feature request

### System Info

-

### Who can help?

_No response_

### Information

- [ ] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

The following snippet outputs the last hidden state but it has (batch_size, num_channels, num_patches, d_model) dimensions
`inputs = encoder(
            past_values=series_list, output_hidden_states=True
        ).last_hidden_state`

Here, series_list has (batch_size, sequence_length, num_input_channels) shape.

To incorporate this with [EncoderDecoderModel](https://huggingface.co/docs/transformers/v4.37.2/en/model_doc/encoder-decoder#transformers.EncoderDecoderModel), I want the dimensions of the input embedding to be (batch_size, sequence_length, hidden_size). How do you get that?


### Expected behavior

-
Repository: vscode
Issue: Notebook screen cheese when running follow up command
Labels: bug,notebook-layout

* use `generate` to create a new cell
* it creates a cell, wait for its follow up command to show
* select the follow up command
* 🧀 the input overlays existing cells

<img width="836" alt="Screenshot 2024-02-22 at 15 28 12" src="https://github.com/microsoft/vscode/assets/1794099/5ef850be-4901-4e7b-9670-f80caa996ac7">
Repository: vscode
Issue: Warning indication jumps up/down when scrolling
Labels: polish,notebook-layout

* open `.vscode/notebooks/my-work.github-issues`
* run all
* notice a warning indication rendered on the scrollbar
* scroll
* :bug: the warning indication jumps up and down




https://github.com/microsoft/vscode/assets/1794099/84fb8225-114e-465b-889b-e5a7a9227e1b
Repository: vscode
Issue: Support hyperlinks in problem matchers of task output
Labels: feature-request,tasks

<!-- ⚠️⚠️ 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. -->

This feature request is about the "problemMatcher" feature of tasks:
https://code.visualstudio.com/docs/editor/tasks#_processing-task-output-with-problem-matchers

I would like to use a "problemMatcher" that matches problems of a task output so that they are displayed in the "Problems" tab as well as in the actual source code.
For that, I'd like to be at least able to provide a clickable hyperlink that gives the user guidance on how to resolve the reported problem.
Alternatively, the existing "message" could support Markdown formatting where links could be added.

Currently, the message doesn't seem to support Markdown or HTML links, and also doesn't make URLs clickable for a user.

## Similar solutions

This is expected to be very similar to the ESLint integration in the "Problems" tab, where a user can click on the rule name to see details:
![image](https://github.com/microsoft/vscode/assets/1410947/0f464e2a-d3c6-466c-a636-7eae67a3e846)

And also to the integration in the code editor where the rule can be clicked, but also additional links (in this case to MDN Reference) are available:
![Screenshot 2024-02-22 at 15 52 30](https://github.com/microsoft/vscode/assets/1410947/ec7da310-aa86-4a9d-ab9a-82b0010f90b7)
Repository: godot
Issue: Mouse movement and speed control for freelook camera don't work when using multiple viewports
Labels: bug,topic:editor,usability,topic:input

### Tested versions

- Reproductible in v4.2.1.stable.official [b09f793f5], v4.3.dev3,  v4.3.dev.custom_build [8bad68df1]

### System information

Windows 11

### Issue description

When using the freelook camera with multiple viewports the mouse movement and scroll wheel move and zoom out the other viewport

- With 2 and 3 viewports the only one that works normally is the top one
- With 4 viewport it is the top right one

The only way to get the freelook camera to work normally is to right click once

https://github.com/godotengine/godot/assets/127440499/f3d15b73-d1e5-4273-a806-569fe928c2fa



### Steps to reproduce

- Open a project
- Select "2 Viewports" option
- Use Free Look camera in the bottom viewport
- Move mouse around and scroll

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: Enabling Mouse Highlighter or Pointer Crosshairs breaks TechSmith Snagit
Labels: Issue-Bug,Needs-Triage,Area-App Compat,Product-Mouse Utilities

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Utilities

### Steps to reproduce

- Install TechSmith Snagit Utility
- Set up a Region capture
- Observe that when you over a window title bar, the window is automatically selected as a capture candidate
- Click to capture the entire window (again, using the region selection tool)
- Enable either "Mouse Highlighter" or "Mouse Pointer Crosshairs"
- Try to capture a single window again, using the region capture feature
- Observe that you cannot select an application window for screen capture, only the entire desktop
- Observe that actual "region" capture via drawing on the screen still works

### ✔️ Expected Behavior

Should still be able to capture individual windows in Snagit by simply hovering over their title bar


### ❌ Actual Behavior

- Cannot use Snagit to capture a window by hovering over the title bar
- Can only capture by "drawing" the desired capture area

### Other Software

TechSmith Snagit version 2024.0.4 (Build 1148)
Repository: PowerToys
Issue: Context menu on tray icon of "Report Bug" doesn't do anything
Labels: Issue-Bug,Needs-Repro,Needs-Team-Response,Area-Bug Report Tool

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

System tray interaction

### Steps to reproduce

- Right-Click on tray icon
- Click on "Report Bug"
- Wait for message that says "Bug report .zip file has been created on your Desktop"
- (Note the space before the extension in the message)

### ✔️ Expected Behavior

- A browser or application window to appear to provide bug details, or....
- A "Bug Report.zip" file to be created on the desktop, with instructions inside the zip for how to submit?

### ❌ Actual Behavior

- The pop-up appears showing the message "Bug report .zip file has been created on your Desktop"
- No file created
- Nothing else happens

### Other Software

_No response_
Repository: flutter
Issue: [Proposal] Allow the Material 3 DropdownMenu widget to disable its search field
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### Use case

Developers wanting to use the `DropdownMenu` but without the type-to-search of the Material 3 widget.

### Proposal

I propose that the `enableSearch` flag is also passed to the `readOnly` attribute of the underlying `TextField`. Currently it's only used for the search highlight. If we can disable the I-beam cursor and text selection, that would be good as well.

We can tweak the `effectiveMouseCursor` and the `SelectionContainer` for the text field when it does not allow searching.
Repository: pytorch
Issue: Dark mode please 🙏🏻
Labels: module: docs,triaged,enhancement

### 🚀 The feature, motivation and pitch

Why don't we still have the **dark mode** in pytorch's documentation?

It hurts the eyes. The current alternative is to use `Dark Reader` extension. But, It does not feel natural and rather gives worse experience.

### Alternatives

_No response_

### Additional context

_No response_

cc @svekars @brycebortree
Repository: flutter
Issue: EmbedderTest.CompositorMustBeAbleToRenderKnownSceneWithSoftwareCompositor fails on arm64 mac hardware in CI
Labels: P2,team-engine,triaged-engine

https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20Engine%20Drone/726856/overview

This looks like an ad-hoc pixel test with different results between arm64 and intel.
Repository: terminal
Issue: Intermittently unable to exit pager after `git log`
Labels: Area-Input,Issue-Bug,Product-Terminal

### Windows Terminal version

1.19.240130002

### Windows build number

10.0.22631.0

### Other Software

_No response_

### Steps to reproduce

- create  a git repo
- make about 50 commits so the git log needs to use pager
`mkdir winterm-pager-repro;
cd winterm-pager-repro;
invoke-expression 'git init';
for($i = 0; $i -le 50; $i++) {
echo 'abc' >> testfile.txt; 
invoke-expression 'git add .';
invoke-expression "git commit -m "test commit $i"';
}
`
- run 'git log' on the repo. make sure the pager is invoked and you have an option to enter `q` to exit pager and get back to prompt. please try this  10-15 times. this doesnt happen consistently but its happens consistently when tried multiple times.
- if reproed, after entering 'q', the ':' at the end of page disappears, cursor continues to blink, but prompt wont be available. you will need to open a new tab or instance to continue.

### Expected Behavior

upon hitting 'q', pager should exit and I should be back on the command prompt.

### Actual Behavior

upon hitting 'q' to exit pager, command prompt doesn't reappear. only option is to open a new tab/instance.

in the image below, I should be able to hit q and get back to the prompt
![winterm-cursor-issue-1](https://github.com/microsoft/terminal/assets/375884/633231e0-3d20-413a-8dd6-29e1301ccbf7)

when i hit 'q', the terminal gets stuck. there cursor continues to blink (not captured in screenshot below) but terminal doesnt respond to any key press. it is not frozen because i can select text with my mouse, close/open new tabs.
![image](https://github.com/microsoft/terminal/assets/375884/664c1471-6a07-45e4-b5ad-71c7d3298773)


Few things I have tried to isolate the issue:
- ran powershell without my profile and without loading any other module besides ps-readline, the issue still happens
Repository: go
Issue: x/tools/gopls: redundant diagnostics for initialization cycle
Labels: gopls,Tools

In the following code, gopls produces multiple diagnostics at X:

```go
var X = Y

var Y = Z

var Z = X
```

This is due to the way gopls unpacks the initialization cycle errors returned by go/types.
Minor, but filing this for tracking purposes. If/when we improve structured errors in go/types, we should fix this. We could also add some ad-hoc suppression of the duplicates.
Repository: bitcoin
Issue: rpc method removeprunedfunds should take an array of txids
Labels: Feature,Wallet

### Please describe the feature you'd like to see added.

Currently removeprunedfunds only takes a single txid, however the underlying  `CWallet::RemoveTxs` takes an array. I am trying to clean up some wallets, and each individual removeprunedfunds call is very slow. So it'd be a lot better to just be able to pass in all the transactions at once

### Is your feature related to a problem, if so please describe it.

_No response_

### Describe the solution you'd like

_No response_

### Describe any alternatives you've considered

_No response_

### Please leave any additional context

_No response_
Repository: storybook
Issue: [Bug]: On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
Labels: bug,windows

### Describe the bug

**I followed the documentation and got this error:**

![image](https://github.com/storybookjs/storybook/assets/108765797/efe48945-7531-4623-b5ae-878dc97f5eac)

```
Failed to build the preview
Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
```

### To Reproduce

_No response_

### System

```bash
System:
    OS: Windows 10 10.0.19042
  Binaries:
    Node: 20.9.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.1.0 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers:
    Chrome: master_preferences
    Edge: Spartan (44.19041.1266.0), Chromium (121.0.2277.128) 
  npmPackages:
    @storybook/addon-essentials: ^7.6.17 => 7.6.17
    @storybook/addon-interactions: ^7.6.17 => 7.6.17
    @storybook/addon-links: ^7.6.17 => 7.6.17
    @storybook/blocks: ^7.6.17 => 7.6.17
    @storybook/builder-vite: ^7.6.17 => 7.6.17
    @storybook/test: ^7.6.17 => 7.6.17
    @storybook/vue3: ^7.6.17 => 7.6.17
    @storybook/vue3-vite: ^7.6.17 => 7.6.17
    @storybook/vue3-webpack5: ^7.6.17 => 7.6.17
    storybook: ^7.6.17 => 7.6.17
```


### Additional context

_No response_
Repository: terminal
Issue: Cursor attributes cannot be set with ANSI VT Sequences before any user input
Labels: Area-VT,Issue-Bug,Area-TerminalControl,Product-Terminal,Priority-3

### Windows Terminal version

1.20.10303.0

### Windows build number

10.0.22631.0

### Other Software

N/A (the code in the repro steps should create the effect)

### Steps to reproduce

1. Compile something along the lines of the following C++ code:
```c++
#include <iostream>
int main() {
	std::cout << "\033[2 q";
	std::cin.get();
	std::cout << "\033[2 q";
	std::cin.ignore(99999999, '\n'); // you can use INT_MAX in place of the spammed 9s
        std::cin.get();

	return 0;
}
```
This code sets the new cursor attributes, waits for an ENTER key, sets the new cursor attributes again, and waits for an enter key again.

2. Run it by clicking on the generated executable, NOT from the VS debug console (if using VS)
3. The first time the program requests an ENTER key, there should be the default cursor attributes. Once the ENTER key is pressed, only then should the cursor attributes set.

https://github.com/microsoft/terminal/assets/66303587/93491fa7-daf8-4c87-aea6-e43df0ea6eaf



### Expected Behavior

Cursor attributes should have been set on command before any user input.

### Actual Behavior

Cursor attribute setting was ignored, until user inputted an ENTER character. Only then could any of the necessary cursor attribute VT sequences work (e.g "\033[2 q").
Repository: node
Issue: Attached debugger always stops on first line
Labels: inspector

### Version

21.6.0

### Platform

23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:59 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6030 arm6

### Subsystem

_No response_

### What steps will reproduce the bug?

starting dev server with script  "node --import tsx/esm --inspect ./index.ts"
attaching debugger from vscode/webstorm to port 9229
on break point, debugger stops on first line in file

### How often does it reproduce? Is there a required condition?

happens only on versions 21.6.0+, on older versions everything works fine


### What is the expected behavior? Why is that the expected behavior?

_No response_

### What do you see instead?

debugger always stops in first line of each file where breakpoint located

### Additional information

_No response_
Repository: vscode
Issue: Kernel picker spinner never stops
Labels: bug,notebook-kernel-picker

Follow steps in https://github.com/microsoft/vscode/issues/206006, the spinner never stops but I'm able to run cells just fine

<img width="1329" alt="Screenshot 2024-02-22 at 09 58 49" src="https://github.com/microsoft/vscode/assets/2193314/4ef9b678-3484-416e-abf6-8847cb9c7360">
Repository: vscode
Issue: Git - Deletion of directory '...' failed. Should I try again? (y/n)
Labels: bug,git

<!-- ⚠️⚠️ 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.86.2
903b1e9d8990623e3d7da1df3d33db3e42d80eda
x64
```
- OS Version: 
```
Edition	Windows 10 Enterprise
Version	22H2
OS build	19045.3930
Experience	Windows Feature Experience Pack 1000.19053.1000.0
```

Steps to Reproduce:

1. Configure VS Code as git's editor `git config --global core.editor = 'code --wait --reuse-window --disable-extensions'`
2. start an interactive rebase  `git rebase HEAD~2 -i`
3. Delete all text in the rebase file
4. Save
5. Close visual studio

See error: `Deletion of directory '...' failed. Should I try again? (y/n)`

I'm also using windows terminal with git-bash and this entirely breaks the terminal forcing me to close the tab.

There does appear to be a race condition as leaving visual studio open for a longer period of time does not exhibit the error (i.e. it's inconsistent).