sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: cmd/go: TestScript failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/go" && test == "TestScript" &&
           output !~ `The process cannot access the file because it is being used by another process.`  # tracked in go.dev/issue/71112
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/9b0f9f403e19cf60eb11f8263d21093ca32d1329)):

    vcs-test.golang.org rerouted to http://127.0.0.1:55618
    https://vcs-test.golang.org rerouted to https://127.0.0.1:55619
    go test proxy running at GOPROXY=http://127.0.0.1:55620/mod
    --- FAIL: TestScript (1.26s)
        --- FAIL: TestScript/gotoolchain_loop (5.24s)
            script_test.go:136: 2024-03-15T11:17:42Z
            script_test.go:138: $WORK=/tmp/buildlet/tmp/cmd-go-test-1876406220/tmpdir1229658131/gotoolchain_loop606090653
            script_test.go:160: 
                > env GOTOOLCHAIN=auto
                > env TESTGO_VERSION=go1.21.1
                # Basic switch should work. (1.183s)
                # Toolchain target mismatch should be detected. (0.238s)
                # Toolchain loop should be detected. (3.799s)
                > env TESTGO_VERSION_SWITCH=loop
                > ! go version
                [signal: illegal instruction]
                > stderr -count=10 '^go: switching from go1.21.1 to go1.21.99 \[depth 9[0-9]\]$'
            script_test.go:160: FAIL: testdata/script/gotoolchain_loop.txt:17: stderr -count=10 '^go: switching from go1.21.1 to go1.21.99 \[depth 9[0-9]\]$': found 0 matches for `(?m)^go: switching from go1.21.1 to go1.21.99 \[depth 9[0-9]\]$` in stderr


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: storybook
Issue: [Bug]: TableOfContents doesnt take custom options from .mdx Meta component
Labels: bug,documentation,sev:S2

### Describe the bug

When setting `parameters.docs.toc.headingSelectors` in button.stories.tsx, it gets custom TOC settings for this component.
example (stories/button.stories.tsx in example):
```
export default {
  title: 'components/component',
  component: Component,
  parameters: {
    docs: { toc: { headingSelector: 'h1, h2' } },
  }
} as Meta;
```

But when setting the same way in changelog.mdx stories file, then it doesn't apply for TOC.  (Look under documentation/changelog from example)
```
import { Meta } from '@storybook/blocks';
import { Markdown } from '@storybook/addon-docs';
import ChangelogMDX from '../../../../CHANGELOG.md?raw';

<Meta name="Changelog" title="Documentation/Changelog" parameters={{ docs: { toc: { headingSelector: 'h1, h2' } } }} />

# Changelog

<Markdown>{ChangelogMDX}</Markdown>
```

But according to the [documentation](https://github.com/storybookjs/storybook/blob/next/code/addons/docs/docs/mdx.md#decorators-and-parameters) this should work.

### To Reproduce

https://stackblitz.com/edit/github-gmbd6l?file=CHANGELOG.md

### System

```bash
Storybook Environment Info:
(node:72459) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)

  System:
    OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)
    CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics
    Shell: 5.1.16 - /bin/bash
  Binaries:
    Node: 21.6.1 - ~/.nvm/versions/node/v21.6.1/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v21.6.1/bin/yarn
    npm: 10.5.0 - ~/work-wsl/tehik-react-components/node_modules/.bin/npm <----- active
    pnpm: 8.3.1 - ~/.nvm/versions/node/v21.6.1/bin/pnpm
  Browsers:
    Chrome: 113.0.5672.92
  npmPackages:
    @storybook/addon-a11y: ^8.0.0 => 8.0.0 
    @storybook/addon-docs: ^8.0.0 => 8.0.0 
    @storybook/addon-essentials: ^8.0.0 => 8.0.0 
    @storybook/addon-mdx-gfm: ^8.0.0 => 8.0.0 
    @storybook/blocks: ^8.0.0 => 8.0.0 
    @storybook/builder-vite: ^8.0.0 => 8.0.0 
    @storybook/core-server: ^8.0.0 => 8.0.0 
    @storybook/manager-api: ^8.0.0 => 8.0.0 
    @storybook/preview-api: ^8.0.0 => 8.0.0 
    @storybook/react: ^8.0.0 => 8.0.0 
    @storybook/react-vite: ^8.0.0 => 8.0.0 
    @storybook/theming: ^8.0.0 => 8.0.0 
    eslint-plugin-storybook: ^0.6.12 => 0.6.15 
    storybook: ^8.0.0 => 8.0.0
```


### Additional context

_No response_
Repository: angular
Issue: `ControlValueAccessor` missing `registerOnDisabledStateChanged` method 
Labels: area: forms,forms: ControlValueAccessor

### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

Given that custom form field controls are able to notify listeners of touched/value changes, and the disabled state of a custom form field control can be set using `setDisabledState`, it makes sense that custom form controls should also be able to notify listeners of disabled state changes.

One example is a reusable nested `FormGroup` that can be marked as "skippable".

Another example is a component that is able to stand on its own or be used as part of a form. This component may or may not be associated with a form. If it isn't part of a form (stands alone), the parent component should be able to disable it using an input. Being able to notify listeners of disabled state changes would make implementing form field controls that can also stand on their own more straight forward.

My current impulse is not to allow components intended to be used as custom form field controls to be used as stand alones. Requiring them to be driven by a control instead of having them implement an awkward middle ground where they can be controlled by both a parent component through inputs OR a control.

### Proposed solution

Add a `registerOnDisabledStateChanged` method to the `ControlValueAccessor` interface or a derived interface.

or.

Leave things as they are and continue requiring a control to drive CVAs as we always have.

### Alternatives considered

The bound `NgControl` can be injected into a component and `enable`/`disable` called directly, but this has some quirks, see: https://github.com/angular/angular/issues/29218
Repository: godot
Issue: Unable to Close Debugger Session Tabs
Labels: bug,topic:editor

### Tested versions

v4.2.stable.official [46dc27791]

### System information

Godot v4.2.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1080 Ti (NVIDIA; 31.0.15.5176) - AMD Ryzen 5 5600X 6-Core Processor (12 Threads)

### Issue description

When running multiple instances of a game through the editor for debugging purposes, the debugger creates multiple tabs labeled "Session 1", "Session 2", etc.  If you set the number of sessions back to 1, or even just a lower number of sessions, there are still tabs shown for the previous highest session count.

### Steps to reproduce

Open any project and select "Debug->Run Multiple Instances->Run # Instances" with # > 1.  Then set the # instances back to a lower number, and check the debugger tab.  It will still show the tabs for the higher instance count.  It can be quite confusing to have 1 instance of the game running, yet seeing the error count in the debugger showing a total error count that is quite high since it duplicates the warnings as well.

### Minimal reproduction project (MRP)

N/A
Repository: TypeScript
Issue: Design Meeting Notes, 3/15/2024
Labels: Design Notes

# Make executables thin wrappers around public API

#55326

* Public API of TypeScript is in `typescript.js`
    * Everything in `tsserver.js` depends on the same stuff as the API.
    * Same-ish is true of `typingsInstaller.js`
* Have a PR where these files just import parts of the API from each executable. `tsserver.js` and `typingsInstaller.js` just become <1000 lines of code on top of `typescript.js`.
* Great size reduction for our npm package size and editors that ship their own `tsserver.js` and `typingsInstaller.js`.
* Runtime speed does not seem to be impacted.
* What about `tsc.js`?
    * #57703
    * `tsc.js` is roughly another a entry-point to our API.
    * You can get the same size reduction with this.
    * Significant regressions!
        * It's not just straight runtime, it's also start-up speed because of the extra code.
        * Different implementation of constructors with different orders?
            * It warrants an investigation.

# Instantiation count in baselines

#57730

* We have no way to detect blow-ups of logic in the compiler other than our perf suite.
* But our test suite has a lot of esoteric work integrated into it.
* Idea is record a few metrics (assignability cache size, type count, instantiation count, symbol count) into our baseline outputs.
    * Rounded so that minor changes don't cause noise.
    * Have a threshold for each metric as well so not every test gets it.
* We like it.

🥳
Repository: neovim
Issue: return to previous window when quitting table of contents
Labels: enhancement

### Problem

In help menu:
- If you open the table of contents (gO):
    - quitting the table of contents window returns the cursor to the main window, rather than the help window
for nearly all cases, this is undesirable behavior, and makes little sense

### Expected behavior

when closing the table of contents window (opened with gO from the help docs), the cursor ought to return to the help window.

Thank you!
Repository: vscode
Issue: Forticlient VPN disconnects when Visusal Studio code is opened
Labels: help wanted,confirmation-pending

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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.87.2
- OS Version: Windows 11 Enterprise 23H2

Steps to Reproduce:

1. Connect to SSL VPN using Fortclient 
2. Open Visual Studio Code
3. VPN disconnects
Repository: vscode
Issue: Fonts not loading
Labels: bug,windows,font-rendering,confirmation-pending


Type: <b>Bug</b>

Install a custom font (in this case Roboto Mono) and add it to the new default font theme in VS Code
Open VS Code (font works)
Close VS Code and open again (on another day)
Font does not show

VS Code version: Code 1.87.2 (863d2581ecda6849923a2118d93a088b0745d9d6, 2024-03-08T15:20:17.278Z)
OS version: Windows_NT x64 10.0.22631
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8 x 2112)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|7.80GB (0.18GB free)|
|Process Argv|--crash-reporter-id aae2ab66-21f0-40d6-b3af-1d1d6a2c6dfa|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (26)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-tailwindcss|bra|0.10.5
dart-code|Dar|3.84.0
flutter|Dar|3.84.0
vscode-eslint|dba|2.4.4
prettier-vscode|esb|10.1.0
rest-client|hum|0.25.1
processing-vscode|Luk|2.5.1
csharp|ms-|2.22.3
vscode-dotnet-runtime|ms-|2.0.2
debugpy|ms-|2024.2.0
isort|ms-|2023.10.1
python|ms-|2024.2.1
vscode-pylance|ms-|2024.3.1
cpptools|ms-|1.19.8
vscode-react-native|msj|1.12.3
java|red|1.28.1
LiveServer|rit|5.7.9
svelte-vscode|sve|108.3.2
intellicode-api-usage-examples|Vis|0.2.8
vscodeintellicode|Vis|1.3.1
vscode-java-debug|vsc|0.56.2
vscode-java-dependency|vsc|0.23.5
vscode-java-pack|vsc|0.25.15
vscode-java-test|vsc|0.40.1
vscode-maven|vsc|0.44.0
rnuilib-snippets|wix|1.0.2


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593:30376534
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
2e7ec940:30986170
pythontbext0:30879054
accentitlementsc:30887149
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:30979542
d34g3935:30971562
fegfb526:30981948
bg6jg535:30979843
dsvsc020:30976470

```

</details>

<!-- generated by issue reporter -->
Repository: vscode
Issue: Testing API > Tags Feedback
Labels: feature-request,testing

Tags are commonly used to filter tests in a test suite. Playwright allows for tagging tests. Since we moved tags out of the test-title into an own property in the last release, we rely on the VSCode Testing API / Explorer filtering logic to filter for tagged tests and found two potential DX enhancements

a) Filter by tags without test controller prefix -> right now the test controller ID is required.
b) Use test controller label instead of ID, or accept both. The ID should be internal and is often not user-friendly / readable.

Ideally this could be the case when only one testing provider has been activated.

See the following video which demonstrates both issues:

https://github.com/microsoft/vscode/assets/17984549/5625df39-627c-4a7c-9c65-7fd1da9ace45

search logic code pointer: https://github.com/microsoft/vscode/blob/d5217d288f97297f5990ec602a4a703510a667df/src/vs/workbench/contrib/testing/browser/testingExplorerFilter.ts#L91

cc @connor4312
Repository: godot
Issue: 'Show in File Manager' should be 'Show in Finder' on macOS
Labels: discussion,topic:editor,topic:porting

### Tested versions

4.2.1

### System information

Godot v4.2.1.stable - macOS 14.3.1 - Vulkan (Mobile) - integrated Apple M3 Max - Apple M3 Max (14 Threads)

### Issue description

On macOS, the file explorer is called 'Finder'. It's a term macOS users are used to, so if a context menu in the 'File System' tab of Godot refers to it using a different name ('File Manager'), it is not clear whether that refers to another feature of Godot or the OS. For clarity, it should simply state 'Show in Finder', and every macOS user will know exactly what the option does.

<img width="520" alt="Screenshot 2024-03-15 at 20 34 16" src="https://github.com/godotengine/godot/assets/5611323/6a236d48-9278-47ec-8356-5f2df7b6fc15">

### Steps to reproduce

- Right mouse click on any file in the FileSystem tab of Godot.
- The second to last item is 'Show in File Manager' while 'Show in Finder' would be a lot more clear and intuitive for macOS users.

### Minimal reproduction project (MRP)

n/a
Repository: godot
Issue: Godot crashes when minimizing a subwindow
Labels: bug,topic:editor,crash

### Tested versions

Reproducible in 4.3-dev3, dev4, and dev5

### System information

Godot v4.3.dev4 - Windows 10.0.19045 - GLES3 (Compatibility) - Intel(R) HD Graphics 4600 (Intel Corporation; 20.19.15.5126) - Intel(R) Core(TM) i3-4330 CPU @ 3.50GHz (4 Threads)

### Issue description

Basically I opened the script editor in a subwindow, tried to minimize it, and Godot crashed. Later on I checked if this also happens in normal projects and yes, it does.

**Here's a short video:**

https://github.com/godotengine/godot/assets/136469511/f790186c-0758-4514-8296-9c9d8843bbea



### Steps to reproduce

1. Add a **Window** node to your scene.
2. Make sure to disable this setting **display/window/subwindows/embed_subwindows**.
3. Minimize it.

-- Or within Godot --
1. Go to script editor.
2. Make it floating.
5. Minimize it.

### Minimal reproduction project (MRP)

N/A.
Repository: vscode
Issue: Git - Add an option to display untracked files like git's default behavior, -unormal
Labels: feature-request,git

<!-- ⚠️⚠️ 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. -->

There are multiple issues that requested exactly this. To name a few (there are many more...):

* #128800
* #131020
* #140755

All were closed as resolved yet none actually implement git's default behavior which everyone working with the CLI is familiar with: `-unormal` (or no `-u` option at all).

I understand there may be things to enhance with it but wrapping up the git command to remove `-uall` from `git status -z` actually works pretty well as long as the trailing `/` are removed from the directories. Untracked directories show as untracked and can be added as a whole. Underlying files won't show as untracked, but AFAIK this is no different than with the hidden option, and that's ok as I can see the directory itself is untracked (not the case with hidden).

Please add this option, with a warning if needed, but not seeing untracked files at all as the only other option is very annoying and very unusual for long time git users.
Repository: godot
Issue: The menu is drawn on top of another workspace when it is changed
Labels: bug,platform:linuxbsd,topic:gui

### Tested versions

Reproducible: in 4.2.1-stable, v4.3.dev.custom_build [01152ab66]

### System information

Godot v4.2.1.stable - Debian GNU/Linux 12 (bookworm/testing) 12 - sway 1.8 (XWayland) - GLES3 (Compatibility) - Mesa Intel(R) HD Graphics 520 (SKL GT2) () - Intel(R) Core(TM) i3-6006U CPU @ 2.00GHz (4 Threads)

### Issue description

If I change workspace while the menu is open the menu will be rendered in a new workspace and when I hover mouse on other top bar "buttons", other menus appear

![screen-1710481859](https://github.com/godotengine/godot/assets/97330399/f25f28dc-abda-4974-b6b2-085c555cc0fb)

Godot was open in 6 workspace than I moved to workspace while the menu was open.

Can't check with pure wayland or pure X11 because I don't have X11 and can't run on wayland with errors...

### Steps to reproduce

1. Open project
2. Open one of the menus
3. Move to another workspace

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: Adding functionality to iOS for no-op functions in Feedback
Labels: c: new feature,platform-ios,framework,f: material design,c: proposal,P2,team-ios,triaged-ios

### Use case

It appears that the Feedback class may not have received attention for some time. Upon reviewing the documentation, I noticed that the functions for taps in the Feedback class are described as not providing feedback on iOS: "Calling any of these methods is a no-op on iOS as actions on that platform typically don't provide haptic or acoustic feedback." However, this statement does not accurately reflect the full range of feedback options available on iOS.

For instance, while it is true that certain actions on iOS may not inherently provide haptic or acoustic feedback, it's important to note that the iOS keyboard does offer haptic feedback and audio cues upon tapping. Additionally, there are several other UI elements within the iOS ecosystem where developers may opt to include feedback for user interactions.

In my application, I find it crucial to provide users with haptic and audio feedback for certain buttons to enhance the user experience. This feedback reassures users that their actions have been registered by the application, especially in asynchronous scenarios where immediate visual feedback may not be feasible.

Therefore, I propose enhancing the Feedback class to include options for haptic and audio feedback on iOS. This would empower developers to provide a more cohesive and responsive user experience across platforms, aligning with the evolving standards of user interaction on iOS devices.

Thank you for considering this suggestion. I believe it would greatly contribute to improving the Flutter framework's usability and user satisfaction.



### Proposal

Review latest iOS feedback and adapt the Feedbak class to it, possibly adding parameters to the function call like forTap(BuildContext context, {bool forceAudio = false, bool forceHaptic = false})
Repository: material-ui
Issue: [docs-infra] Add line and word highlighting on code blocks
Labels: new feature,design,scope: docs-infra

### Summary

Sometimes, we may want to draw attention to a specific part of a code snippet. That can be either a small function, a variable, or an entire line. We currently lack a way of doing this "natively" within our docs-infra experience. Here's just a quick preview of what this could look like:

<img width="600" alt="Screenshot 2024-03-15 at 19 28 49" src="https://github.com/mui/material-ui/assets/67129314/7d0e183b-c911-453a-bc46-abe30106876a">

## Benchmark

- @atomiks shared his [rehype-pretty-code](https://rehype-pretty-code.netlify.app/) library that we could potentially use! In terms of DX, I don't think we should deviate too much from how it is done in it.
- [Docusaurus](https://docusaurus.io/docs/markdown-features/code-blocks#line-highlighting) also has its own way of adding this feature that we can be inspired by too.
Repository: next.js
Issue: Web Workers don't budle correctly when using edge
Labels: bug,Runtime,Module Resolution

### Link to the code that reproduces this issue

https://github.com/RobertAron/web-worker-issue

### To Reproduce

`npm run dev`

### Current vs. Expected behavior

The expected behavior is what happens when not using the edge configuration

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 22.6.0: Wed Jul  5 22:21:53 PDT 2023; root:xnu-8796.141.3~6/RELEASE_ARM64_T6020
Binaries:
  Node: 20.5.1
  npm: 9.8.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.1.3
  eslint-config-next: 14.1.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A
```


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

App Router, Middleware / Edge (API routes, runtime), Module resolution (CJS / ESM, module resolving)

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

next dev (local)

### Additional context

<img width="746" alt="Screenshot 2024-03-15 at 5 35 59 PM" src="https://github.com/vercel/next.js/assets/11590571/78873182-569d-454c-9a50-4262786ff28b">
<img width="380" alt="Screenshot 2024-03-15 at 5 36 12 PM" src="https://github.com/vercel/next.js/assets/11590571/6be79237-20f7-4801-86bb-ea0985b1d91c">
<img width="1376" alt="Screenshot 2024-03-15 at 5 36 30 PM" src="https://github.com/vercel/next.js/assets/11590571/8e77bcb0-3961-4898-85f8-3d747c4a3459">


Thanks for all your hard work ❤️