sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: bitcoin
Issue:  Cannot figure out how to use std::atomic error for MacOS Sequoia 15.2
Labels: macOS,Build system

Fails to compile when running `cmake -B build -DWITH_BDB=ON`
Attempted the build process on two different laptops with identical specifications and encountered the same error.

Build Output:
```
-- Performing Test STD_ATOMIC_LINKS_WITHOUT_LIBATOMIC
-- Performing Test STD_ATOMIC_LINKS_WITHOUT_LIBATOMIC - Failed
-- Performing Test STD_ATOMIC_NEEDS_LINK_TO_LIBATOMIC
-- Performing Test STD_ATOMIC_NEEDS_LINK_TO_LIBATOMIC - Failed
CMake Error at cmake/module/TestAppendRequiredLibraries.cmake:90 (message):
  Cannot figure out how to use std::atomic.
Call Stack (most recent call first):
  cmake/introspection.cmake:29 (test_append_atomic_library)
  CMakeLists.txt:391 (include)
```



Laptop Specifications
- OS: macOS Sequoia 15.2
- Compiler: Apple Clang version 16.0.0 (clang-1600.0.26.6)
-- Target: arm64-apple-darwin24.2.0
-- Thread model: posix
-- InstalledDir: /Library/Developer/CommandLineTools/usr/bin
Repository: svelte
Issue: `const` type paremeter `svelte(js_parse_error)`
Labels: blocked by upstream

### Describe the bug

`const` type parameters are a feature added in Typescript 5.0.
However, trying to use them in a .svelte or .svelte.ts file results in `Unexpected keyword 'const' https://svelte.dev/e/js_parse_error`

This is presumably a missing feature in `acorn-typescript`, and as such blocked by #13439 

### Reproduction

```svelte
<script lang=ts>
  function test<const T>(value: T) {
    return value;
  }
</script>

<h1>Hello {test("World")}!</h1>
```

### Logs

_No response_

### System Info

```shell
System:
    OS: Linux 6.12 Arch Linux
    CPU: (16) x64 AMD Ryzen 7 7840U w/ Radeon  780M Graphics
    Memory: 17.86 GB / 30.66 GB
    Container: Yes
    Shell: 5.2.37 - /bin/bash
  Binaries:
    Node: 23.4.0 - ~/.nvm/versions/node/v23.4.0/bin/node
    npm: 10.9.2 - ~/.nvm/versions/node/v23.4.0/bin/npm
  npmPackages:
    rollup: ^4.29.1 => 4.29.1
```


### Severity

annoyance
Repository: stable-diffusion-webui
Issue: [Feature Request]: prepare host for specific gpu (needed for containers) without starting api/ui
Labels: asking-for-help-with-local-system-issues

### 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 ?

It would be nice to have some option to initializen the current installation for a specific gpu
right now I exploit the script to "simulate" my amd gpu

```
root@ollama:~/ollama# cat Dockerfile.automatic1111
FROM rocm/pytorch:rocm6.3_ubuntu22.04_py3.10_pytorch_release_2.4.0

WORKDIR /automatic1111

# install packages
RUN apt update \
 && apt install google-perftools bc -y --no-install-recommends \
 && apt clean

# clone repo
RUN mkdir -p /data \
 && git clone https://github.com/AUTOMATIC1111/stable-diffusion-webui .

# prepare environment (exploits webui.sh)
RUN --mount=type=cache,target=/root/.cache/pip \
    sed 's/start()/# start()/g' launch.py >_init.py \
 && bash -ec "function lspci { echo '03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] XXXXXX'; } \
 && export -f lspci \
 && LAUNCH_SCRIPT=_init.py ./webui.sh -f --data-dir /data --skip-torch-cuda-test" \
 && rm -rf /data/* _init.py

EXPOSE 7860

VOLUME /data

CMD ["/automatic1111/webui.sh", "-f", "--api", "--listen", "--skip-prepare-environment", "--data-dir", "/data", "--precision", "full", "--no-half" ]
```

### Proposed workflow

maybe a separate script or argument would be nice

### Additional information
if someome is interessted this is my docker-compose.yml
```
services:
  ollama:
    image: ollama/ollama:rocm
    ports:
      - "11434:11434"
    volumes:
      #- ./ollama:/root/.ollama
      - /usr/share/ollama/.ollama:/root/.ollama
    restart: unless-stopped
    devices:
      - /dev/kfd
      - /dev/dri
    group_add:
      - 44
      - 993

  open-webui:
    image: ghcr.io/open-webui/open-webui:main
    restart: unless-stopped
    volumes:
      - ./open-webui:/app/backend/data
    ports:
      - "8080:8080"
    environment:
      OLLAMA_BASE_URL: http://ollama:11434
      AUTOMATIC1111_BASE_URL: http://automatic1111:7860
      ENABLE_OLLAMA_API: true
      ENABLE_OPENAI_API: false
      YOUTUBE_LOADER_LANGUAGE: de
      ENABLE_RAG_WEB_SEARCH: true
      RAG_WEB_SEARCH_ENGINE: duckduckgo
      ENABLE_IMAGE_GENERATION: true
      IMAGE_GENERATION_ENGINE: automatic1111
      IMAGE_GENERATION_MODEL: v1-5-pruned-emaonly.safetensors [6ce0161689]
      SCARF_NO_ANALYTICS: true
      DO_NOT_TRACK: true
      ANONYMIZED_TELEMETRY: false

  automatic1111:
    build:
      context: .
      dockerfile: Dockerfile.automatic1111
    volumes:
      - ./automatic1111:/data
    restart: unless-stopped
    ports:
      - "7860:7860"
    group_add:
      - 44
      - 993
    devices:
      - /dev/kfd
      - /dev/dri
```
Repository: electron
Issue: Can't access audio output on MacOS with NSAudioCaptureUsageDescription
Labels: platform/macOS,bug :beetle:,33-x-y

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

33.3.0

### What operating system(s) are you using?

macOS

### Operating System Version

MacOS Sequoia 15.2

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

I expect to be able to access Apples CoreAudio API's through Electron using `systemPreferences.askForMediaAccess`, in order to record sound on MacOS, using the newer `NSAudioCaptureUsageDescription` (MacOS 14.4 and later) permission. Right now only `NSMicrophoneUsageDescription` and `NSCameraUsageDescription` seem supported by the `systemPreferences` API.

### Actual Behavior

No option to record sound is featured by Electron right now. Currently the only approach I've found to record sound with Electron, is to spawn a CLI app as child process, made with Swift that handles the sound recording. This gives rise to a host of problems, which I haven't been able to solve in order to successfully record audio through a child process.

### Testcase Gist URL

_No response_

### Additional Information

The following reddit thread outline the solution I've mentioned above, which is a clunky way of solving it, and one that I haven't been able to solve fully at this time: https://www.reddit.com/r/electronjs/comments/1d9bjh9/recording_system_audio_on_macos
Repository: next.js
Issue: loading.tsx not affecting sub-routes in some cases
Labels: Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/jovial-shockley-7yn8kf?workspaceId=ws_RG1nRyxTaV3usxvsfBToRH

### To Reproduce

1. Click the link to go to the other route, notice it is delayed until the page appears
2. Click the link go to back home, it also will delay until home appears
3. If you manually refresh the page on either route, the Loading.tsx file will display properly

However, if you move the `(groupA)/page.tsx` up into the `app/` folder, it works properly, *including* for the `/other/[slug]` route.

### Current vs. Expected behavior

Current: `loading.tsx` only shows on page refresh, not client side navigations.
Expected: Loader should "trickle" down to the routes below.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Home
  Available memory (MB): 32703
  Available CPU cores: 8
Binaries:
  Node: 20.11.0
  npm: 9.8.1
  Yarn: N/A
  pnpm: 9.15.1
Relevant Packages:
  next: 15.1.2 // There is a newer version (15.1.3) available, upgrade recommended!
  eslint-config-next: 15.1.2
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
Next.js Config:
  output: N/A
 ⚠ There is a newer version (15.1.3) available, upgrade recommended!
```


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

Navigation

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

next dev (local), next build (local), Vercel (Deployed)

### Additional context

CSB is on latest canary
Repository: ant-design
Issue: Form.Item.useStatus() 返回的 errors 不能按照预期更新
Labels: unconfirmed

### Reproduction link

[https://github.com/tgxpuisb/form-item](https://github.com/tgxpuisb/form-item)

### Steps to reproduce

根据上面仓库用vite启动server，将右侧select设置为9，触发表单验证，再将右侧select选择为8触发表单验证，此时两次的error应该不同，但是 `Form.Item.useStatus()` 并未返回最新的验证信息

通过浏览器 `react component` 插件可以看出 `StatusProvider`的值有更新，但是 `FormItemInputContext.Provider`的值没有更新，由此可以初步得出可能是 `node_modules/antd/es/form/FormItem/StatusProvider.js` 中的 `formItemStatusContext`中的 `useMemo` 并为将 errors 的变化作为更新依赖导致，修改此处代码可以解决此问题

如果确定是bug，并且可以修复，请尽快发布一个修复的小版本

### What is expected?

右侧select设置为9时 error提示 from must not equal to，再次选择为8时 error 提示为 from must not large than to

### What is actually happening?

右侧select设置为9时 error提示 from must not equal to，再次选择为8时 error 提示为 from must not equal to，没有正常更新

| Environment | Info |
| --- | --- |
| antd | 5.22.2 |
| React | react |
| System | 所有版本 |
| Browser | 所有浏览器 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: test case got killed file_based_local_timer_test.py test_get_timer_recursive
Labels: module: tests,triaged

### 🐛 Describe the bug

test case get killed when running test file_based_local_timer_test.py::FileTimerTest::test_get_timer_recursive
output 
```
python  file_based_local_timer_test.py -k 'test_get_timer_recursive'
Killed

```

### Versions

main

cc @mruberry @ZainRizvi
Repository: TypeScript
Issue: static block on unnamed class produces invalid javascript
Labels: Bug,Help Wanted

### 🔎 Search Terms

- class
- invalid
- codegen
- static

### 🕗 Version & Regression Information

- This changed after version 4.4
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about classes, static members of classes
- I was unable to test this on prior versions because static blocks where introduced in typescript 4.4


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.8.0-dev.20241229#code/KYDwDg9gTgLgBAE2AMwIYFcA28DGnUDOBA3gFBwVwEyowCWOiwAthAFwB26zARsFAG5ylarQZwylKXBgALOgQB0SVnAC8cAIxCpAX1K6gA

### 💻 Code

```ts
export default class{
    static demo:number;
    static {
        this.demo = 1;
    }
}
```


### 🙁 Actual behavior

TypeScript produces an invalid output where the code references an undefined `default_1`
I'm assuming the empty class is meant to be assigned to this.

example output:
```js
var _a;
class {
}
_a = default_1;
(() => {
    _a.demo = 1;
})();
export default default_1;
```

### 🙂 Expected behavior

I would expect typescript to assign the class to the generated default_1

### Additional information about the issue

TypeScript has been exhibiting this behavior since support for static blocks was introduced as far as I can tell, prior to version 4.4.4 in the playground produces a different set of invalid code where it just moves the block outside of the class with no modification.

this still technically happens without the export default but typescript does have a warning.
Repository: go
Issue: x/net/route: ParseRIB fail to parse utun up InterfaceMessage
Labels: NeedsFix,FixPending

### Go version

go version go1.22.6 darwin/amd64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE='on'
GOARCH='amd64'
GOBIN=''
GOCACHE='/Users/ruokeqx/Library/Caches/go-build'
GOENV='/Users/ruokeqx/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='amd64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/ruokeqx/go/pkg/mod'
GOOS='darwin'
GOPATH='/Users/ruokeqx/go'
GOPROXY='https://goproxy.cn,direct'
GOROOT='/usr/local/opt/go1.22'
GOSUMDB='off'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/usr/local/opt/go1.22/pkg/tool/darwin_amd64'
GOVCS=''
GOVERSION='go1.22.6'
GCCGO='gccgo'
GOAMD64='v1'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -arch x86_64 -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/d8/c7cqtvp515v7tn7xmvv6v2m00000gn/T/go-build3070326303=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### What did you do?

try parse message from AF_ROUTE socket.

`unix.Socket(unix.AF_ROUTE, unix.SOCK_RAW, unix.AF_UNSPEC)` 
`msgs, err := route.ParseRIB(route.RIBTypeRoute, data[:n])`

### What did you see happen?

ParseRIB skip Interface message that indicate utun interface up

```golang
// data fetch from AF_ROUTE socket
data := []byte{112, 0, 5, 14, 0, 0, 0, 0, 81, 128, 0, 0, 28, 0, 0, 0, 1, 0, 0, 0, 0, 0, 0, 0, 220, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 237, 0, 107, 103, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0}
```

since no RTA_IFP flag

```golang
func (w *wireFormat) parseInterfaceMessage(_ RIBType, b []byte) (Message, error) {
...
	if attrs&syscall.RTA_IFP == 0 {
		return nil, nil
	}
...
}
```

not sure if it is intended

### What did you expect to see?

should return InterfaceMessage with Index and flags?
Repository: godot
Issue: Cannot connect signal in InstancePlaceHolder
Labels: discussion,topic:core,documentation

### Tested versions

Tested version: Godot_v4.3-stable_mono_win64


### System information

Godot v4.3.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1650 (NVIDIA; 31.0.15.3168) - Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 Threads)

### Issue description

Scene reference as InstancePlaceHolder. From the Node we can see the signals of this InstancePlaceHolder, connect the signal to a method, then run the project,  Godot editor reports error.

### Steps to reproduce

Save a Button as Scene,  set InstancePlaceholder is selected,  then connect it press signal with some method.
Run project, Godot Editor report error:
E 0:00:01:0027   connect: In Object of type 'InstancePlaceholder': Attempt to connect nonexistent signal 'pressed' to callable 'Control::queue_free'.
  <C++ Error>    Condition "!signal_is_valid" is true. Returning: ERR_INVALID_PARAMETER
  <C++ Source>   core/object/object.cpp:1390 @ connect()



### Minimal reproduction project (MRP)

[placeholderconnect.zip](https://github.com/user-attachments/files/18272501/placeholderconnect.zip)
Repository: vscode
Issue: [Accessibility, Mouse]: When navigating with the mouse, the content in the editor is not reported to the screen reader.
Labels: bug,accessibility


Type: <b>Bug</b>

This issue has existed for a long time and I am not sure if it is difficult to improve it because of the design.

## Steps to Reproduce

1. Run NVDA and turn on mouse tracking.
2. Install the Mouse enhancement Add-on in the Add-on Store to fix mouse tracking in Electron
3. Open the source file
4. Use the mouse to view the contents in the editor

## Actual Behavior

Does not report what is under the mouse (excluding hover panels)

## Expected Behavior

Reports content under the mouse

VS Code version: Code - Insiders 1.97.0-insider (89f808979a5151bd91324e65d4f7ab1b62896983, 2024-12-20T05:04:19.167Z)
OS version: Windows_NT x64 10.0.26100
Modes:

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

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-12700 (12 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<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|63.71GB (31.77GB free)|
|Process Argv|--crash-reporter-id d541528f-f74e-45c1-9b59-00b32f6da504|
|Screen Reader|yes|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: PowerToys
Issue: Workspace takes wrong version of Access
Labels: Issue-Bug,Needs-Triage,Product-Workspaces

### Microsoft PowerToys version

0.87.1

### Installation method

GitHub

### Running as admin

None

### Area(s) with issue?

Workspaces

### Steps to reproduce

Installing both MS Access 365 & MS Access Runtime 2010,
Opening MS Accesss 2010 adp file.
Saving Workspace.
Editing workspace to include CLI argument as path to ADP file.

Close all apps.
Launch workspace.

### ✔️ Expected Behavior

Launching MS Access Runtime 2010.
And opening the proper ADP file.

### ❌ Actual Behavior

Launching MS Access 365 instead of runtime 2010

### Other Software

MS Access Runtime 2010
MS Access 365
Repository: vscode
Issue: Relative file link in Terminal not clickable
Labels: terminal-links

<!-- ⚠️⚠️ 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. -->
Version: 1.96.2 (user setup)
Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f
Date: 2024-12-19T10:22:47.216Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.22631

Steps to Reproduce:

The integrated terminal file link works for absolute path (e.g.: `/usr/x/proj/_snapshot/snapshot-1.png`),
and relative files that are not ignored (e.g.: `src/index.ts`).

But if the file/folder is gitignored (e.g.: `./_snapshot/snapshot-1.png` while `_snapshot` is ignored in `.gitignore`), 
it doesn't work (clicking on shows `No matching results`)

Originally asked in: https://discord.com/channels/470167643710816277/1320179380315623494/1320179380315623494
Repository: vscode
Issue: [Accessibility, Mouse]: When using the mouse to navigate a menu, the content behind the menu is reported to the screen reader.
Labels: bug,accessibility


Type: <b>Bug</b>

This issue has existed for a long time.

## Steps to Reproduce

1. Run NVDA and turn on mouse tracking.
2. Install the Mouse enhancement Add-on in the Add-on Store to fix mouse tracking in Electron
3. On non-editor pages, use the mouse to navigate the help menu

## Actual Behavior

will report the contents of the back of the menu.

## Expected Behavior

Does not report the contents of the back of the menu.

## screenshot

https://github.com/user-attachments/assets/7f23b8a1-c77a-466c-bb76-c7aae7c938a9

VS Code version: Code - Insiders 1.97.0-insider (89f808979a5151bd91324e65d4f7ab1b62896983, 2024-12-20T05:04:19.167Z)
OS version: Windows_NT x64 10.0.26100
Modes:

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

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-12700 (12 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<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|63.71GB (35.80GB free)|
|Process Argv|--crash-reporter-id d541528f-f74e-45c1-9b59-00b32f6da504 --crash-reporter-id d541528f-f74e-45c1-9b59-00b32f6da504|
|Screen Reader|yes|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: ant-design
Issue: 支持给 RangePicker 两个 input 元素单独指定 id 和 className 等属性
Labels: unconfirmed

### What problem does this feature solve?

在自动化测试中，我们经常需要精准定位到 input 并填充内容，通常需要 id 或 className 或 data-testid 之类的属性。然而目前 RangePicker 组件无法轻松地添加这些属性，除非自定义整个 input 组件，成本有点高。

### What does the proposed API look like?

```jsx
<DatePicker.RangePicker
  startInputProps={{ className: 'event-start-date' }}
  endInputProps={{ className: 'event-end-date' }}
/>
```

或者

```jsx
<DatePicker.RangePicker
  classNames={{ startInput: 'event-start-date', endInput: 'event-end-date' }}
/>
```
<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: node
Issue: vm.runInContext Function Prototype Issue
Labels: feature request

### What is the problem this feature will solve?

I'm having an issue with the vm module in Node.js.The function prototypes defined within a script using vm.runInContext do not match Function.prototype.

```javascript
const vm = require('vm');

const context = vm.createContext({
    console,
    Function: Function
});

const script = new vm.Script(`
    function test() {
        return "Hello, World!";
    }
    console.log(test.prototype === Function.prototype); // Expected: true, Actual: false
`);

script.runInContext(context);

```

### What is the feature you are proposing to solve the problem?

Tried using proxies, manual prototype setting, custom constructors, but none worked.

### What alternatives have you considered?

_No response_