sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: specs::test::worker_large_output is flaky
Labels: flaky

https://github.com/denoland/deno/actions/runs/9071453760/job/24925194323

```
---- specs::test::worker_large_output ----
command C:\a\deno\deno\target\release\deno.exe test main.js
command cwd C:\a\deno\deno\tests\specs\test\worker_large_output
output path C:\a\deno\deno\tests\specs\test\worker_large_output\main.out
-- OUTPUT START --
running 1 test from ./main.js
workerOutput ...
------- output -------
Booting worker
fatal runtime error: I/O error: operation failed to complete synchronously
----- output end -----
workerOutput ... ok (98ms)

-- OUTPUT END --
-- EXPECTED START --
[WILDCARD]

ok | 1 passed | 0 failed ([WILDCARD])


-- EXPECTED END --
-- DEBUG START --
<WILDCARD />
==== COULD NOT FIND SEARCH TEXT ====


ok·|·1·passed·|·0·failed·(
==== MAX FOUND ====


==== NEXT ACTUAL TEXT ====
unning·1·test·from·./main.js
workerOutpu[TRUNCATED]
-- DEBUG END --

panicked at tests\specs/mod.rs:357:12:
pattern match failed
Test file: C:\a\deno\deno\tests\specs\test\worker_large_output\__test__.jsonc
```
Repository: tauri
Issue: [bug] App icons are blurry and app name has weird hash inside parenthesis for AppImages only.
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

The app icons are blurry in window view and in the dock for .AppImage only. The icon is crisp on the applications section though.
Dock:
![image](https://github.com/tauri-apps/tauri/assets/51436631/b3585198-dd3f-4440-adf7-4e5203b260c9)

Window viewer:
![image](https://github.com/tauri-apps/tauri/assets/51436631/b7467779-a3c4-4a1b-befd-ac533ab30727)

Applications:
![image](https://github.com/tauri-apps/tauri/assets/51436631/4604737a-ff3b-4ed9-ac3f-4a6993acf3f3)
 
App name has some kind of  hash:
![image](https://github.com/tauri-apps/tauri/assets/51436631/c3427d3b-7dc9-48f8-b0e4-9a20f64d68cc)


### Reproduction

https://github.com/niraj-khatiwada/tauri-nextjs

### Expected behavior

- The app icons must be crisp on all packaging.
- The app name must be exact what it has been specified in `tauri.conf.json`

### Full `tauri info` output

```text
https://github.com/niraj-khatiwada/tauri-nextjs
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: deno
Issue: `parallel/test-fs-read-stream.js` hangs
Labels: flaky

```
test node_compat_tests has been running for over 60 seconds
'Node.js compatibility' has been running for over (1m0s)
  Node.js compatibility "parallel/test-util-inspect-long-running.js" ... ok (15s)
'Node.js compatibility' has been running for over (2m0s)
------- output -------
Test is running slow: /Users/runner/work/deno/deno/tests/node_compat/test/parallel/test-fs-read-stream.js
'Node.js compatibility' has been running for over (4m0s)
'Node.js compatibility' has been running for over (8m0s)
Test ran far too long, terminating with extreme prejudice: /Users/runner/work/deno/deno/tests/node_compat/test/parallel/test-fs-read-stream.js
"parallel/test-fs-read-stream.js" failed:



You can repeat only this test with the command:

  ./target/debug/deno test -A tests/node_compat/test.ts -- parallel/test-fs-read-stream.js

----- output end -----
  Node.js compatibility "parallel/test-fs-read-stream.js" ... FAILED (10m0s)
Node.js compatibility ... FAILED (due to 1 failed step) (10m38s)
checkConfigTestFilesOrder ... ok (0ms)

 ERRORS 

Node.js compatibility ... Node.js compatibility "parallel/test-fs-read-stream.js" => ./tests/node_compat/test.ts:58:11
error: AssertionError: Failed assertion: "parallel/test-fs-read-stream.js" failed:



You can repeat only this test with the command:

  ./target/debug/deno test -A tests/node_compat/test.ts -- parallel/test-fs-read-stream.js

    throw new AssertionError(msg);
          ^
    at assert (file:///Users/runner/work/deno/deno/tests/util/std/assert/assert.ts:17:11)
    at fail (file:///Users/runner/work/deno/deno/tests/util/std/assert/fail.ts:16:3)
    at fn (file:///Users/runner/work/deno/deno/tests/node_compat/test.ts:142:9)
    at eventLoopTick (ext:core/01_core.js:168:7)
    at async innerWrapped (ext:cli/40_test.js:191:5)
    at async Object.outerWrapped [as fn] (ext:cli/40_test.js:134:14)
    at async TestContext.step (ext:cli/40_test.js:492:22)
    at async runTest (file:///Users/runner/work/deno/deno/tests/node_compat/test.ts:58:3)

 FAILURES 

Node.js compatibility ... Node.js compatibility "parallel/test-fs-read-stream.js" => ./tests/node_compat/test.ts:58:11
```

https://github.com/denoland/deno/actions/runs/9306465111/job/25615735025?pr=24052

https://github.com/denoland/deno/actions/runs/9079901193/job/24950107176
Repository: PowerToys
Issue: [Peek] Annoying link confirmation window
Labels: Idea-Enhancement,Needs-Triage,Product-Peek

### Description of the new feature / enhancement

Please add an option in the settings that allows the user to choose whether he wants to be alerted each time he clicks on a link. Currently, it's annoying to have to confirm every time.
Thanks!

### Scenario when this would be used?

![screen](https://github.com/microsoft/PowerToys/assets/45882853/9f3b56c5-da2e-4f7f-bf33-afd1708fce0d)

### Supporting information

_No response_
Repository: TypeScript
Issue: Error: Debug Failure when importing `AssertionError` from `node:assert/strict`
Labels: Bug,Help Wanted

### 🔎 Search Terms

Error: Debug Failure

### 🕗 Version & Regression Information

Happened when using tsc v5.4.5 with `@types/node`. Wasn’t an issue before (older tsc and older `@types/node` v20.12.12).

### ⏯ Playground Link

https://github.com/rauschma/tsc-debug-failure

### 💻 Code

```ts
import { AssertionError } from 'node:assert/strict';
```

Some of my compilerOptions in tsconfig:

```json
"module": "NodeNext",
"moduleResolution": "NodeNext",
"isolatedModules": true,
"verbatimModuleSyntax": true,
"resolveJsonModule": true,
```

### 🙁 Actual behavior

```
Error: Debug Failure.
    at getTypeOfVariableOrParameterOrPropertyWorker (/usr/local/lib/node_modules/typescript/lib/tsc.js:53005:11)
    at getTypeOfVariableOrParameterOrProperty (/usr/local/lib/node_modules/typescript/lib/tsc.js:52974:20)
    at getTypeOfSymbol (/usr/local/lib/node_modules/typescript/lib/tsc.js:53306:14)
    at getTypeOfAlias (/usr/local/lib/node_modules/typescript/lib/tsc.js:53226:358)
    at getTypeOfSymbol (/usr/local/lib/node_modules/typescript/lib/tsc.js:53318:14)
    at getNarrowedTypeOfSymbol (/usr/local/lib/node_modules/typescript/lib/tsc.js:67681:18)
    at checkIdentifier (/usr/local/lib/node_modules/typescript/lib/tsc.js:67808:16)
    at checkExpressionWorker (/usr/local/lib/node_modules/typescript/lib/tsc.js:76261:16)
    at checkExpression (/usr/local/lib/node_modules/typescript/lib/tsc.js:76216:32)
    at checkNonNullExpression (/usr/local/lib/node_modules/typescript/lib/tsc.js:70497:29)
```


### 🙂 Expected behavior

No exception (normal operation)

### Additional information about the issue

Possibly helpful:

* I initially couldn’t tell what the problem was (in my rather large repo) but Nathan Shively-Sanders suggested I change line `tsc.js:53005` as follows. That told me that this problem was about `AssertionError`.

```diff
- Debug.assertIsDefined(symbol.valueDeclaration);
+ Debug.assertIsDefined(symbol.valueDeclaration, Debug.formatSymbol(symbol));
```
Repository: puppeteer
Issue: [Bug]: An Error Occurred on the Page Due to Code Execution
Labels: bug,upstream,confirmed,P3

### Minimal, reproducible example

```TypeScript
const puppeteer = require("puppeteer-core");
const localExecutablePath = "C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe"
async function main() {
  const browser = await puppeteer.launch({
    //ignoreDefaultArgs: ["--enable-automation"],
    args: [],
    executablePath: localExecutablePath,
    headless: false
  });
  console.log("Browser is created.");
  const pages = await browser.pages();
  const page = pages[0];
  page.on('popup', async (popup) => {
    console.log(await popup.url());
    await popup.close();
  });
}
main();
```


### Error string

Crash Page: STATUS_ACCESS_VIOLATION

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Background

Chrome: windows x64 124.0.6367.201 
```javascript
 const f = document.createElement("iframe");
                f.src = "data:text/html;charset=utf-8,<p></p>",
                document.body.appendChild(f),
                console.log("fire"),
                f.contentWindow.open("", "", "top=9999,left=9999,width=100,height=100")
``` 
When the above code is running, it causes a crash on the page.

### Expectation

It was supposed to write the popup address to the console and then close it.

### Reality

Unfortunately, crashes occurred on both the page and the popup, and the popup listener did not function as intended.

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22.8.1

### Node version

v21.7.1

### Package manager

npm

### Package manager version

10.6.0

### Operating system

Windows
Repository: storybook
Issue: [Bug]: Storybook sees arrow function properties as string properties
Labels: bug,angular,block: argstable,docgen

### Describe the bug

Storybook sees arrow function properties as string properties

### To Reproduce

Create a component with an arrow function

![image](https://github.com/storybookjs/storybook/assets/84519004/a49241b2-611c-4a64-8b51-daee7bc8c5e0)

Create a stories with it

Observe that the input has `Set string` instead of `Set object`

![image](https://github.com/storybookjs/storybook/assets/84519004/dc25f02e-10c1-44c1-86de-900bbddc88f1)



### System

```bash
Storybook Environment Info:

  System:
    OS: Windows 11 10.0.22631
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz
  Binaries:
    Node: 18.20.2 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.4.2 - C:\Program Files\nodejs\npm.CMD <----- active
  Browsers:
    Edge: Chromium (123.0.2420.97)
  npmPackages:
    eslint-plugin-storybook: ^0.8.0 => 0.8.0
```


### Additional context

_No response_
Repository: next.js
Issue: [Middleware] Locale in NextResponse.rewrite(...) path ignored for dynamic routes when basepath is set and skipMiddlewareUrlNormalize is true
Labels: bug,Middleware,Pages Router

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/localized-slugs-y6fgq8

### To Reproduce

Set the following in `next.config.js` to add basepath, enable path based localization, and to set `skipMiddlewareUrlNormalize` to `true`.

```js
const nextConfig = {
  basePath: "/basepath",
  i18n: {
    defaultLocale: "en-US",
    locales: ["en-US", "es", "fr"],
  },
  skipMiddlewareUrlNormalize: true,
};

module.exports = nextConfig;
```

Next  create middleware with a rewrite to a different `locale` (I've setup the middleware here to read  a query param to override the locale):

```js
const { NextResponse } = require("next/server");

const SKIP = /^\/(basepath\/)?(_next).*/;

export function middleware(request) {
  if (SKIP.test(request.nextUrl.pathname)) return NextResponse.next();

  const locale = request.nextUrl.searchParams.get("lang");
  if (!locale) return NextResponse.next();

  const url = request.nextUrl.clone();
  if (!url.pathname.startsWith(`/${locale.toLowerCase()}`)) {
    url.pathname = `/${locale.toLowerCase()}${url.pathname}`;
  }

  console.log("rewrite to:", url.href);

  return NextResponse.rewrite(url);
}
```

Next create a dynamic page such as `pages/test/[slug].tsx`, and print out the locale:

```tsx
import Link from "next/link";
import { useRouter } from "next/router";

const Page = () => {
  const router = useRouter();
  return (
    <>
      {router.pathname}: {router.locale}
    </>
  );
};

export default Page;
```

Go to that page with the `lang` param set to a different locale: `/basepath/test/dynamic?lang=fr`, you'll see that the redirect url logs correctly as `/basepath/fr/test/dynamic`, but the page loads with the router reporting `en-US` as the local.

Try these same steps for a non dynamic route, and you'll see that it does work in that case.

Pinning to `~13.3.0` fixes the issue, but no newer version resolves the issue.

### Current vs. Expected behavior

I expect dynamic routes to respect rewrites the same as non-dynamic routes, where currently in the above scenario, that is not the case.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 8198
  Available CPU cores: 4
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.4
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Middleware, Pages Router

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

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: vscode
Issue: Model is disposed!
Labels: error-telemetry

```javascript
Error: Model is disposed!
at V.ib in src/vs/editor/common/model/textModel.ts:416:10
at V.validateRange in src/vs/editor/common/model/textModel.ts:1062:8
at V.tb in src/vs/editor/common/model/textModel.ts:1251:9
at V.ub in src/vs/editor/common/model/textModel.ts:1262:21
at V.applyEdits in src/vs/editor/common/model/textModel.ts:1416:28
at i.$onVirtualDocumentChange in src/vs/workbench/api/browser/mainThreadDocumentContentProviders.ts:88:11
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=dc96b837cf6bb4af9cd736aa3af08cf8279f7685&bH=4eff9e3b-4271-0907-32e2-4afa346d5cef)
Repository: PowerToys
Issue: White rectangle in the middle of screen
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.80.1

### Installation method

WinGet

### Running as admin

No

### Area(s) with issue?

ColorPicker

### Steps to reproduce

Possible to turn off screen and turn back on.
Opening color picker removes white rectangle.
color picker has this:
![image](https://github.com/microsoft/PowerToys/assets/24793462/3572d88e-bb3c-4035-89ba-ea9928558b62)


[PowerToysReport_2024-05-14-19-33-20.zip](https://github.com/microsoft/PowerToys/files/15311474/PowerToysReport_2024-05-14-19-33-20.zip)
Sorry for so little information.



### ✔️ Expected Behavior

no rectangle

### ❌ Actual Behavior

White rectangle over all apps.
![Screenshot_3](https://github.com/microsoft/PowerToys/assets/24793462/08d6637d-2002-455f-a6e1-3517b622027b)

### Other Software

_No response_
Repository: flutter
Issue: Flutter tool misses early log messages
Labels: tool,P2,team-tool,triaged-tool

I added some log messages that are printed during the startup of the engine and flutter tool doesn't show them.

Looking at `adb logcat` I can see the log messages.

This is extremely confusing.
Repository: flutter
Issue: If Flutter app crashes on launch tool just says "Installing"
Labels: tool,team-tool

```
$ flutter run ...
...
Running Gradle task 'assembleDebug'...                              7.2s
✓ Built build/app/outputs/flutter-apk/app-debug.apk
Installing build/app/outputs/flutter-apk/app-debug.apk...           5.7s
```

If the application crashes at launch the tool just sits there saying 'Installing'.

1) It should properly report that the application has crashed.
2) It should show relevant log lines and exit.
Repository: vscode
Issue: Illegal value for lineNumber
Labels: error-telemetry

```javascript
Error: Illegal value for lineNumber
at V.getLineFirstNonWhitespaceColumn in src/vs/editor/common/model/textModel.ts:862:10
at r.n in src/vs/editor/contrib/gotoSymbol/browser/link/goToDefinitionAtPosition.ts:242:38
at r.m in src/vs/editor/contrib/gotoSymbol/browser/link/goToDefinitionAtPosition.ts:233:29
at <anonymous> in src/vs/editor/contrib/gotoSymbol/browser/link/goToDefinitionAtPosition.ts:215:31
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=dc96b837cf6bb4af9cd736aa3af08cf8279f7685&bH=ca6821fb-2b27-4989-e138-2adc33444ba2)
Repository: storybook
Issue: [Bug]: vite image assets imported but causes fetch imported module error
Labels: bug,needs triage

### Describe the bug

When using vites static asset import ( "vite": "^5.2.11",), i get this error when trying to import images with vite static assets.

```
Failed to fetch dynamically imported module: components/MyModule.tsx
```

MyModule.tsx looks like this:
```
import myImage from "/images/myImage.png?url"

export function MyModule() {
   return <img src={myImage} alt="" />;
}
```

The console has this error:

```
Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "image/png". Strict MIME type checking is enforced for module scripts per HTML spec.
```

it seems to be trying to load this as a script/module but its actually an image, the browser throws an error and then storybook crashes and cannot import the entire module.

Happens for svgs, images, etc 


### To Reproduce

Unable to reproduce in stackblitz, but showed example above in the description.

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.4.1
    CPU: (10) arm64 Apple M1 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v20.9.0/bin/npm <----- active
  Browsers:
    Chrome: 124.0.6367.207
    Edge: 124.0.2478.97
    Safari: 17.4.1
  npmPackages:
    @storybook/addon-actions: ^8.1.0 => 8.1.0
    @storybook/addon-essentials: ^8.1.0 => 8.1.0
    @storybook/addon-interactions: ^8.1.0 => 8.1.0
    @storybook/addon-links: ^8.1.0 => 8.1.0
    @storybook/blocks: ^8.1.0 => 8.1.0
    @storybook/manager-api: ^8.1.0 => 8.1.0
    @storybook/node-logger: ^8.1.0 => 8.1.0
    @storybook/preview-api: ^8.1.0 => 8.1.0
    @storybook/react: ^8.1.0 => 8.1.0
    @storybook/react-vite: ^8.1.0 => 8.1.0
    @storybook/theming: ^8.1.0 => 8.1.0
    eslint-plugin-storybook: ^0.8.0 => 0.8.0
    msw-storybook-addon: ^2.0.2 => 1.10.0
    storybook: ^8.1.0 => 8.1.0
    storybook-addon-pseudo-states: ^3.1.1 => 3.1.0
    storybook-addon-remix-react-router: ^3.0.0 => 3.0.0
```


### Additional context

Does not happen in the vite app, only in storybook with vite.
Repository: go
Issue: cmd/go: list -m -json often missing .Origin
Labels: NeedsFix,GoCommand,modules

### Go version

go version go1.22.3 darwin/arm64

### Output of `go env` in your module/workspace:

```shell
GO111MODULE=''
GOARCH='arm64'
GOBIN='/Users/josh/bin'
GOCACHE='/Users/josh/Library/Caches/go-build'
GOENV='/Users/josh/Library/Application Support/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='arm64'
GOHOSTOS='darwin'
GOINSECURE=''
GOMODCACHE='/Users/josh/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='darwin'
GOPATH='/Users/josh'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/Users/josh/go/1.22'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='auto'
GOTOOLDIR='/Users/josh/go/1.22/pkg/tool/darwin_arm64'
GOVCS=''
GOVERSION='go1.22.3'
GCCGO='gccgo'
AR='ar'
CC='clang'
CXX='clang++'
CGO_ENABLED='1'
GOMOD='/dev/null'
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 arm64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -ffile-prefix-map=/var/folders/vm/htvrhp4177v2dfhdjlvl0pqh0000gn/T/go-build2633414260=/tmp/go-build -gno-record-gcc-switches -fno-common'
```


### Bug report

This is a regression. With Go 1.22.3:

```
$ go list -m -json golang.org/x/tools@latest
{
	"Path": "golang.org/x/tools",
	"Version": "v0.21.0",
	"Query": "latest",
	"Time": "2024-05-06T16:54:44Z",
	"GoMod": "/Users/josh/pkg/mod/cache/download/golang.org/x/tools/@v/v0.21.0.mod",
	"GoVersion": "1.19"
}
```

Note that there is no Origin field.

With Go 1.21.10:

```
$ go list -m -json golang.org/x/tools@latest
{
	"Path": "golang.org/x/tools",
	"Version": "v0.21.0",
	"Query": "latest",
	"Time": "2024-05-06T16:54:44Z",
	"GoMod": "/Users/josh/pkg/mod/cache/download/golang.org/x/tools/@v/v0.21.0.mod",
	"GoVersion": "1.19",
	"Origin": {
		"VCS": "git",
		"URL": "https://go.googlesource.com/tools",
		"Ref": "refs/tags/v0.21.0",
		"Hash": "cc29c91ba3acb47c1793da56d919cc40def4ea41"
	}
}
```

Given the conversation in https://github.com/golang/go/issues/57051, it is clear that the intent is that the Origin field be present.

Relevant to https://github.com/golang/go/issues/18387.
Repository: ollama
Issue: BUG: Custom System Prompt not loading
Labels: bug

### What is the issue?

# Bug Report

## Description
If I use any LLava models ([LLava-Phi-3](https://ollama.com/library/llava-phi3)), the custom System prompt ist working fine. 

But if I upload an Picture at the start of the Conversation, the System Prompt is not Loading and if I continue the Conversation it still not have the custom System Prompt.

Only if I start the new Chat with only text as an Input, the System prompt is loading correctly.

**Bug Summary:**
Custom System Prompt not loading

**Steps to Reproduce:**
[Outline the steps to reproduce the bug. Be as detailed as possible.]
1. Load an LLava Model
2. Create a Custom System Prompt in Settings or in Modelfile
3. Upload a Picture and ask something about the Picture, and no Custom System Prompt loaded!!!
4. Continue conversation, but still there is no Custom System Prompt loaded!!!

## Environment

- **Open WebUI Version:** [0.1.124]
- **Ollama (if applicable):** [e.g., 0.1.37]

- **Operating System:** [Ubuntu 20.04]
- **Browser:** [Chrome]

### OS

Linux

### GPU

_No response_

### CPU

AMD

### Ollama version

0.1.37
Repository: puppeteer
Issue: [Bug]: The popup listener can't catch popups.
Labels: bug,upstream,confirmed,P3

### Minimal, reproducible example

```TypeScript
const puppeteer = require("puppeteer");
async function main() {

  const browser = await puppeteer.launch({
    //ignoreDefaultArgs: ["--enable-automation"],
    args: [],
    //executablePath: localExecutablePath,
    headless: false,
  });
  console.log("Browser is created.");
  const pages = await browser.pages();
  const page = pages[0];
  page.on('popup', async (popup) => {
    console.log(await popup.url());
    await popup.close();
  });
}
main();
```


### Error string

no error

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Background

Popup1:
```javascript
    const c = document.createElement("a")
                  , d = document.createEvent("MouseEvents");
                c.href = "https://example.com/test/7",
                d.initMouseEvent("click", !1, !0, window, 0, 0, 0, 0, 0, !0, !1, !1, !0, 0, null),
                c.dispatchEvent(d)
``` 
Popup2:
```html
 <a href="https://example.com/test/12" id="id4"></a>
``` 
```javascript
document.getElementById("id4").dispatchEvent(new MouseEvent("click",{
                        button: 1
                    }));
``` 
The two popups mentioned above are not being detected. I conducted the tests on the following website: https://webbrowsertools.com/popup-blocker/.

### Expectation

It was expected that the popups would show their URLs and then close.

### Reality

The popup listener isn't working.

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

22.8.1

### Node version

v21.7.1

### Package manager

npm

### Package manager version

10.6.0

### Operating system

Windows