helloadhavan/github_issues huggingface dataset:
Repository: vercel/next.js
Pull request: Development: Only require loadJsConfig when using webpack

## What?

Don't require/call loadJsConfig when using Turbopack, as it's handled internally. loadJsConfig is one of the places where TypeScript gets loaded. There's still the TS verify as well, this narrows the amount of places where TypeScript gets loaded to make it easier to remove that loading of TypeScript in a future PR.

Closes PACK-5435

Changed files:
filename: packages/next/src/server/lib/router-utils/setup-dev-bundler.ts
patch: @@ -19,7 +19,6 @@ import * as Log from '../../../build/output/log'
 import { setGlobal } from '../../../trace/shared'
 import type { Telemetry } from '../../../telemetry/storage'
 import type { IncomingMessage, ServerResponse } from 'http'
-import loadJsConfig from '../../../build/load-jsconfig'
 import { createValidFileMatcher } from '../find-page-file'
 import {
   EVENT_BUILD_FEATURE_USAGE,
@@ -763,14 +762,22 @@ async function startWatcher(
           ])
         }
         let tsconfigResult:
-          | UnwrapPromise<ReturnType<typeof loadJsConfig>>
+          | UnwrapPromise<
+              ReturnType<typeof import('../../../build/load-jsconfig').default>
+            >
           | undefined
 
-        if (tsconfigChange) {
-          try {
-            tsconfigResult = await loadJsConfig(dir, nextConfig)
-          } catch (_) {
-            /* do we want to log if there are syntax errors in tsconfig while editing? */
+        // This is not relevant for Turbopack because tsconfig/jsconfig is handled internally.
+        if (!hotReloader.turbopackProject) {
+          if (tsconfigChange) {
+            try {
+              const loadJsConfig = (
+                require('../../../build/load-jsconfig') as typeof import('../../../build/load-jsconfig')
+              ).default
+              tsconfigResult = await loadJsConfig(dir, nextConfig)
+            } catch (_) {
+              /* do we want to log if there are syntax errors in tsconfig while editing? */
+            }
           }
         }
Repository: vercel/next.js
Pull request: Development: Make 'ready in' 195ms faster

## What?

The Watchpack instance created defaulted to `aggregateTimeout: 200` which causes 200ms of dead time during bootup, affecting the `ready in`  logline.

Before:

```
 ✓ Starting...
 ✓ Ready in 583ms
```

After: 
```
 ✓ Starting...
 ✓ Ready in 355ms // -39.1%
```

Next up:
- `~50ms`: Remove loading webpack when Turbopack is used (it still gets required currently for `next.config.js`)
- `~110ms`: Figure out how to avoid loading TypeScript which is used to check `tsconfig.json` options. 

Closes PACK-5437

Changed files:
filename: packages/next/src/server/lib/router-utils/setup-dev-bundler.ts
patch: @@ -333,6 +333,8 @@ async function startWatcher(
     files.push(...tsconfigPaths)
 
     const wp = new Watchpack({
+      // Watchpack default is 200ms which adds 200ms of dead time on bootup.
+      aggregateTimeout: 5, // Matches webpack-config.ts.
       ignored: (pathname: string) => {
         return (
           !files.some((file) => file.startsWith(pathname)) &&
Repository: electron/electron
Pull request: fix: Linux `visibleOnAllWorkspaces` property

Backport of #46850

See that PR for details.


Notes: Fixed the `visibleOnAllWorkspaces` property on Linux.

Changed files:
filename: shell/browser/native_window_views.cc
patch: @@ -1522,6 +1522,13 @@ void NativeWindowViews::SetVisibleOnAllWorkspaces(
 }
 
 bool NativeWindowViews::IsVisibleOnAllWorkspaces() const {
+  // NB: Electron >= 37 has a better long-term fix, but it also has an edge
+  // case which is a breaking change. The code here is dirtier (e.g. accessing
+  // a method marked as private) to avoid that edge case. More info @
+  // https://github.com/electron/electron/pull/46834#issuecomment-2836287699
+  if (const auto* view_native_widget = widget()->native_widget_private())
+    return view_native_widget->IsVisibleOnAllWorkspaces();
+
 #if BUILDFLAG(IS_LINUX)
   if (IsX11()) {
     // Use the presence/absence of _NET_WM_STATE_STICKY in _NET_WM_STATE to

filename: spec/api-browser-window-spec.ts
patch: @@ -5407,8 +5407,7 @@ describe('BrowserWindow module', () => {
       });
     });
 
-    // FIXME: enable this test on Linux as well.
-    ifdescribe(process.platform === 'darwin')('visibleOnAllWorkspaces state', () => {
+    ifdescribe(process.platform !== 'win32')('visibleOnAllWorkspaces state', () => {
       describe('with properties', () => {
         it('can be changed', () => {
           const w = new BrowserWindow({ show: false });
Repository: denoland/deno
Pull request: fix(types): add [Symbol.iterator]() to NodeListOf (fixes #31382)

fix(types): add`[Symbol.iterator]()` to `NodeListOf`

This PR adds missing iterable support to `NodeListOf<TNode>` in the DOM
typings. Without this method, TypeScript raises error TS2488:

```ts
for (const child of div.childNodes) {}
// TS2488: NodeListOf<ChildNode> must have a [Symbol.iterator]() method
```

This brings Deno’s DOM types in line with upstream `lib.dom.d.ts`, where
`NodeListOf` is defined as iterable.


## Related Issue

Fixes #31382


## Details

The following method was added to `NodeListOf<TNode>`:

```ts
[Symbol.iterator](): IterableIterator<TNode>;
```

This is a type-only change and does not affect the runtime behavior of Deno.
The fix allows idiomatic iteration over `NodeListOf`, such as:

```ts
for (const child of element.childNodes) {
  console.log(child);
}
```






Changed files:
filename: cli/tsc/dts/lib.dom.d.ts
patch: @@ -21993,6 +21993,7 @@ interface NodeListOf<TNode extends Node> extends NodeList {
     item(index: number): TNode;
     forEach(callbackfn: (value: TNode, key: number, parent: NodeListOf<TNode>) => void, thisArg?: any): void;
     [index: number]: TNode;
+    [Symbol.iterator](): IterableIterator<TNode>;
 }
 
 interface NonDocumentTypeChildNode {
Repository: ollama/ollama
Pull request: fix docker doc to point to hub

there is a link that should point to dockerhub which is the best place to understand docker

Changed files:
filename: docs/README.md
patch: @@ -12,7 +12,7 @@ Import models using source model weights found on Hugging Face and similar sites
 
 Installing on Linux in most cases is easy using the script on Ollama.ai. To get more detail about the install, including CUDA drivers, see the **[Linux Documentation](./linux.md)**.
 
-Many of our users like the flexibility of using our official Docker Image. Learn more about using Docker with Ollama using the **[Docker Documentation](./docker.md)**.
+Many of our users like the flexibility of using our official Docker Image. Learn more about using Docker with Ollama using the **[Docker Documentation](https://hub.docker.com/r/ollama/ollama)**.
 
 It is easy to install on Linux and Mac, but many users will choose to build Ollama on their own. To do this, refer to the **[Development Documentation](./development.md)**.
Repository: electron/electron
Pull request: fix: Linux `visibleOnAllWorkspaces` property

#### Description of Change

Fix the broken `visibleOnAllWorkspaces` property on Linux and enable the related tests.

#45887 is the right long-term fix and is what we're using in Electron 37; however, it can't be backported because it has an edge case that counts as a breaking change.

This PR isn't as clean or maintainable, but it does fix the same bug in a nonbreaking way. So it's not here to supersede 45887, just to patch the older maintenance branches.

All reviews welcomed. CC @codebytere who wrote 45887.

#### Checklist

- [x] PR description included and stakeholders cc'd
- [x] `npm test` passes
- [x] tests are [changed or added](https://github.com/electron/electron/blob/main/docs/development/testing.md)
- [x] [PR release notes](https://github.com/electron/clerk/blob/main/README.md) describe the change in a way relevant to app developers, and are [capitalized, punctuated, and past tense](https://github.com/electron/clerk/blob/main/README.md#examples).

#### Release Notes

Notes: Fixed the `visibleOnAllWorkspaces` property on Linux.

Changed files:
filename: shell/browser/native_window_views.cc
patch: @@ -1538,6 +1538,13 @@ void NativeWindowViews::SetVisibleOnAllWorkspaces(
 }
 
 bool NativeWindowViews::IsVisibleOnAllWorkspaces() const {
+  // NB: Electron >= 37 has a better long-term fix, but it also has an edge
+  // case which is a breaking change. The code here is dirtier (e.g. accessing
+  // a method marked as private) to avoid that edge case. More info @
+  // https://github.com/electron/electron/pull/46834#issuecomment-2836287699
+  if (const auto* view_native_widget = widget()->native_widget_private())
+    return view_native_widget->IsVisibleOnAllWorkspaces();
+
 #if BUILDFLAG(IS_LINUX)
   if (IsX11()) {
     // Use the presence/absence of _NET_WM_STATE_STICKY in _NET_WM_STATE to

filename: spec/api-browser-window-spec.ts
patch: @@ -5408,8 +5408,7 @@ describe('BrowserWindow module', () => {
       });
     });
 
-    // FIXME: enable this test on Linux as well.
-    ifdescribe(process.platform === 'darwin')('visibleOnAllWorkspaces state', () => {
+    ifdescribe(process.platform !== 'win32')('visibleOnAllWorkspaces state', () => {
       describe('with properties', () => {
         it('can be changed', () => {
           const w = new BrowserWindow({ show: false });
Repository: ggml-org/llama.cpp
Pull request: gitignore : be more specific about ignored stuff

Noticed that all `/src/models/*` were accidentally being ignored

Changed files:
filename: .gitignore
patch: @@ -20,52 +20,40 @@
 *.so
 *.swp
 *.tmp
+*.DS_Store
 
 # IDE / OS
 
-.cache/
-.ccls-cache/
-.direnv/
-.DS_Store
-.envrc
-.idea/
-.swiftpm
-.vs/
-.vscode/
-nppBackup
+/.cache/
+/.ccls-cache/
+/.direnv/
+/.envrc
+/.idea/
+/.swiftpm
+/.vs/
+/.vscode/
+/nppBackup
 
 
 # Coverage
 
-gcovr-report/
-lcov-report/
+/gcovr-report/
+/lcov-report/
 
 # Build Artifacts
 
-tags
-.build/
-build*
-release
-debug
-!build-info.cmake
-!build-info.cpp.in
-!build-info.sh
-!build.zig
-!docs/build.md
+/tags
+/.build/
+/build*
+/release
+/debug
 /libllama.so
 /llama-*
 /vulkan-shaders-gen
-android-ndk-*
-arm_neon.h
-cmake-build-*
-CMakeSettings.json
-compile_commands.json
-ggml-metal-embed.metal
-llama-batched-swift
 /rpc-server
-out/
-tmp/
-autogen-*.md
+/out/
+/tmp/
+/autogen-*.md
 
 # Deprecated
 
@@ -74,44 +62,38 @@ autogen-*.md
 
 # CI
 
-!.github/workflows/*.yml
+!/.github/workflows/*.yml
 
 # Models
 
-models/*
-models-mnt
-!models/.editorconfig
-!models/ggml-vocab-*.gguf*
-!models/templates
+/models/*
+/models-mnt
+!/models/.editorconfig
+!/models/ggml-vocab-*.gguf*
+!/models/templates
 
 # Zig
-zig-out/
-zig-cache/
-
-# Logs
-
-ppl-*.txt
-qnt-*.txt
-perf-*.txt
+/zig-out/
+/zig-cache/
 
 # Examples
 
-examples/jeopardy/results.txt
-tools/server/*.css.hpp
-tools/server/*.html.hpp
-tools/server/*.js.hpp
-tools/server/*.mjs.hpp
-tools/server/*.gz.hpp
-!build_64.sh
-!examples/*.bat
-!examples/*/*.kts
-!examples/*/*/*.kts
-!examples/sycl/*.bat
-!examples/sycl/*.sh
+/examples/jeopardy/results.txt
+/tools/server/*.css.hpp
+/tools/server/*.html.hpp
+/tools/server/*.js.hpp
+/tools/server/*.mjs.hpp
+/tools/server/*.gz.hpp
+!/build_64.sh
+!/examples/*.bat
+!/examples/*/*.kts
+!/examples/*/*/*.kts
+!/examples/sycl/*.bat
+!/examples/sycl/*.sh
 
 # Server Web UI temporary files
-node_modules
-tools/server/webui/dist
+/tools/server/webui/node_modules
+/tools/server/webui/dist
 
 # Python
 
@@ -147,8 +129,8 @@ poetry.toml
 # Local scripts
 /run-vim.sh
 /run-chat.sh
-.ccache/
+/.ccache/
 
 # IDE
-*.code-workspace
-.windsurf/
+/*.code-workspace
+/.windsurf/
Repository: nodejs/node
Pull request: src: add cache to nearest parent package json

### Motivation

Fixes #58126. 
My benchmark was based on the example app shared by @BridgeAR 

### Description

In PR #50322, moving the `package_json_reader` cache from JS to C++ preserved the heavy JSON parsing in native code but removed the original JS level cache. As a result, the resolution logic now invokes the C++ binding more frequently.

The worst offender is `modulesBinding.getNearestParentPackageJSON` called ≈ 102 000 times during a typical run.

1. **Initial run (current main branch):**

   ```bash
   time ./node test.js 
   # ≈4.5s
   ```
2. **With a C++ side cache:**

   * Cache stats: 270 misses, \~101 700 hits
   * Run time `≈4.5s`, showing the bridge overhead remains.
  
3. **With a JS side cache:**

   ```bash
   time ./node test.js 
   # ≈0.5s
   ```


Introducing a JS level cache for `getNearestParentPackageJSON` to avoid repeated C++ crossings eliminates most of the overhead and reducing run time from `≈4.5s` to `≈0.5s`


Changed files:
filename: lib/internal/modules/package_json_reader.js
patch: @@ -5,6 +5,7 @@ const {
   JSONParse,
   ObjectDefineProperty,
   RegExpPrototypeExec,
+  SafeMap,
   StringPrototypeIndexOf,
   StringPrototypeSlice,
 } = primordials;
@@ -28,6 +29,8 @@ const path = require('path');
 const { validateString } = require('internal/validators');
 const internalFsBinding = internalBinding('fs');
 
+const nearestParentPackageJSONCache = new SafeMap();
+
 /**
  * @typedef {import('typings/internalBinding/modules').DeserializedPackageConfig} DeserializedPackageConfig
  * @typedef {import('typings/internalBinding/modules').PackageConfig} PackageConfig
@@ -131,13 +134,21 @@ function read(jsonPath, { base, specifier, isESM } = kEmptyObject) {
  * @returns {undefined | DeserializedPackageConfig}
  */
 function getNearestParentPackageJSON(checkPath) {
+  if (nearestParentPackageJSONCache.has(checkPath)) {
+    return nearestParentPackageJSONCache.get(checkPath);
+  }
+
   const result = modulesBinding.getNearestParentPackageJSON(checkPath);
 
   if (result === undefined) {
+    nearestParentPackageJSONCache.set(checkPath, undefined);
     return undefined;
   }
 
-  return deserializePackageJSON(checkPath, result);
+  const packageConfig = deserializePackageJSON(checkPath, result);
+  nearestParentPackageJSONCache.set(checkPath, packageConfig);
+
+  return packageConfig;
 }
 
 /**
Repository: vercel/next.js
Pull request: cna: fix typo

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the PR.
- Read the Docs Contribution Guide to ensure your contribution follows the docs guidelines: https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See: https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. (A discussion must be opened, see https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added (https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to understand the PR)
- When linking to a Slack thread, you might want to share details of the conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

## Summary

This PR fixes a typo in `packages/create-next-app/templates/app-api/ts/gitignore`. I fixed it from `commiting` to `committing`.
https://github.com/vercel/next.js/blob/8657188505ada96024068b44c6caa5ebd89f3867/packages/create-next-app/templates/app-api/ts/gitignore#L32

Changed files:
filename: packages/create-next-app/templates/app-api/ts/gitignore
patch: @@ -29,7 +29,7 @@ npm-debug.log*
 yarn-debug.log*
 yarn-error.log*
 
-# env files (can opt-in for commiting if needed)
+# env files (can opt-in for committing if needed)
 .env*
 
 # vercel
Repository: facebook/react
Pull request: [Fiber] clarify entry condition for suspensey commit recursion

Previously Suspensey recursion would only trigger if the ShouldSuspendCommit flag was true. However there is a dependence on the Visibility flag embedded in this logic because these flags share a bit. To make it clear that the semantics of Suspensey resources require considering both flags I've added it to the condition even though this extra or-ing is a noop when the bit is shared

Changed files:
filename: packages/react-reconciler/src/ReactFiberWorkLoop.js
patch: @@ -126,6 +126,7 @@ import {
   MountLayoutDev,
   DidDefer,
   ShouldSuspendCommit,
+  MaySuspendCommit,
 } from './ReactFiberFlags';
 import {
   NoLanes,
@@ -1185,7 +1186,13 @@ function commitRootWhenReady(
 ) {
   // TODO: Combine retry throttling with Suspensey commits. Right now they run
   // one after the other.
-  if (finishedWork.subtreeFlags & ShouldSuspendCommit) {
+  const BothVisibilityAndMaySuspendCommit = Visibility | MaySuspendCommit;
+  const subtreeFlags = finishedWork.subtreeFlags;
+  if (
+    subtreeFlags & ShouldSuspendCommit ||
+    (subtreeFlags & BothVisibilityAndMaySuspendCommit) ===
+      BothVisibilityAndMaySuspendCommit
+  ) {
     // Before committing, ask the renderer whether the host tree is ready.
     // If it's not, we'll wait until it notifies us.
     startSuspendingCommit();
Repository: huggingface/transformers
Pull request: Read config pattern for Qwen3Next

# What does this PR do?

If it's present on the hub config, and layer_types is not, it will be read

Changed files:
filename: src/transformers/models/qwen3_next/configuration_qwen3_next.py
patch: @@ -243,8 +243,10 @@ def __init__(
 
         self.layer_types = layer_types
         if self.layer_types is None:
+            interval_pattern = kwargs.get("full_attention_interval", 4)
             self.layer_types = [
-                "linear_attention" if bool((i + 1) % 4) else "full_attention" for i in range(self.num_hidden_layers)
+                "linear_attention" if bool((i + 1) % interval_pattern) else "full_attention"
+                for i in range(self.num_hidden_layers)
             ]
         layer_type_validation(self.layer_types)
Repository: ollama/ollama
Pull request: Cleaup stale submodule

If the tree has a stale submodule, make sure we clean it up first

Changed files:
filename: llm/generate/gen_common.sh
patch: @@ -18,6 +18,11 @@ git_module_setup() {
         echo "Skipping submodule initialization"
         return
     fi
+    # Make sure the tree is clean after the directory moves
+    if [ -d "${LLAMACPP_DIR}/gguf" ]; then
+        echo "Cleaning up old submodule"
+        rm -rf ${LLAMACPP_DIR}
+    fi
     git submodule init
     git submodule update --force ${LLAMACPP_DIR}
Repository: electron/electron
Pull request: fix: run `visibleOnAllWorkspaces` tests on the right platforms

Backport of #46815

See that PR for details.


Notes: none.

Changed files:
filename: spec/api-browser-window-spec.ts
patch: @@ -5406,6 +5406,27 @@ describe('BrowserWindow module', () => {
         expect(w.webContents.isLoadingMainFrame()).to.be.true('isLoadingMainFrame');
       });
     });
+
+    // FIXME: enable this test on Linux as well.
+    ifdescribe(process.platform === 'darwin')('visibleOnAllWorkspaces state', () => {
+      describe('with properties', () => {
+        it('can be changed', () => {
+          const w = new BrowserWindow({ show: false });
+          expect(w.visibleOnAllWorkspaces).to.be.false();
+          w.visibleOnAllWorkspaces = true;
+          expect(w.visibleOnAllWorkspaces).to.be.true();
+        });
+      });
+
+      describe('with functions', () => {
+        it('can be changed', () => {
+          const w = new BrowserWindow({ show: false });
+          expect(w.isVisibleOnAllWorkspaces()).to.be.false();
+          w.setVisibleOnAllWorkspaces(true);
+          expect(w.isVisibleOnAllWorkspaces()).to.be.true();
+        });
+      });
+    });
   });
 
   ifdescribe(process.platform !== 'linux')('window states (excluding Linux)', () => {
@@ -5446,26 +5467,6 @@ describe('BrowserWindow module', () => {
       });
     });
 
-    describe('visibleOnAllWorkspaces state', () => {
-      it('with properties', () => {
-        it('can be changed', () => {
-          const w = new BrowserWindow({ show: false });
-          expect(w.visibleOnAllWorkspaces).to.be.false();
-          w.visibleOnAllWorkspaces = true;
-          expect(w.visibleOnAllWorkspaces).to.be.true();
-        });
-      });
-
-      it('with functions', () => {
-        it('can be changed', () => {
-          const w = new BrowserWindow({ show: false });
-          expect(w.isVisibleOnAllWorkspaces()).to.be.false();
-          w.setVisibleOnAllWorkspaces(true);
-          expect(w.isVisibleOnAllWorkspaces()).to.be.true();
-        });
-      });
-    });
-
     ifdescribe(process.platform === 'darwin')('documentEdited state', () => {
       it('with properties', () => {
         it('can be changed', () => {
Repository: nodejs/node
Pull request: test: update WPT for urlpattern to 84b75f0880

This is an automated update of the WPT for urlpattern to https://github.com/web-platform-tests/wpt/commit/84b75f08801c8cfe407c25614c49132075b8afab.

Changed files:
filename: test/fixtures/wpt/README.md
patch: @@ -29,7 +29,7 @@ Last update:
 - resources: https://github.com/web-platform-tests/wpt/tree/1e140d63ec/resources
 - streams: https://github.com/web-platform-tests/wpt/tree/bc9dcbbf1a/streams
 - url: https://github.com/web-platform-tests/wpt/tree/9504a83e01/url
-- urlpattern: https://github.com/web-platform-tests/wpt/tree/3ffda23e5a/urlpattern
+- urlpattern: https://github.com/web-platform-tests/wpt/tree/84b75f0880/urlpattern
 - user-timing: https://github.com/web-platform-tests/wpt/tree/5ae85bf826/user-timing
 - wasm/jsapi: https://github.com/web-platform-tests/wpt/tree/cde25e7e3c/wasm/jsapi
 - wasm/webapi: https://github.com/web-platform-tests/wpt/tree/fd1b23eeaa/wasm/webapi

filename: test/fixtures/wpt/urlpattern/urlpattern-constructor.html
patch: @@ -0,0 +1,14 @@
+<!DOCTYPE html>
+<script src="/resources/testharness.js"></script>
+<script src="/resources/testharnessreport.js"></script>
+<script>
+test(() => {
+  assert_throws_js(TypeError, () => { new URLPattern(new URL('https://example.org/%(')); } );
+  assert_throws_js(TypeError, () => { new URLPattern(new URL('https://example.org/%((')); } );
+  assert_throws_js(TypeError, () => { new URLPattern('(\\'); } );
+}, `Test unclosed token`);
+
+test(() => {
+  new URLPattern(undefined, undefined);
+}, `Test constructor with undefined`);
+</script>

filename: test/fixtures/wpt/versions.json
patch: @@ -76,7 +76,7 @@
     "path": "url"
   },
   "urlpattern": {
-    "commit": "3ffda23e5af7c59590b17c2710a22efd22dd4973",
+    "commit": "84b75f08801c8cfe407c25614c49132075b8afab",
     "path": "urlpattern"
   },
   "user-timing": {