helloadhavan/github_issues huggingface dataset:
Repository: vercel/next.js
Pull request: Update Rspack production test manifest

This auto-generated PR updates the production integration test manifest used when testing Rspack.

Changed files:
filename: test/rspack-build-tests-manifest.json
patch: @@ -5776,6 +5776,9 @@
   "test/e2e/app-dir/segment-cache/search-params/segment-cache-search-params.test.ts": {
     "passed": [],
     "failed": [
+      "segment cache (search params) handles rewrites to the same page but with different search params",
+      "segment cache (search params) handles rewrites to the same page but with no search params",
+      "segment cache (search params) stores prefetched data by its rewritten search params, not the original ones",
       "segment cache (search params) when fetching with PPR, does not include search params in the cache key",
       "segment cache (search params) when fetching without PPR (e.g. prefetch={true}), includes the search params in the cache key"
     ],
Repository: ggml-org/llama.cpp
Pull request: ggml : fix dependencies for ggml_set_rows

cont #14274 
ref https://github.com/ggml-org/llama.cpp/pull/16063#discussion_r2385795931

The result of `ggml_set_rows` requires to have a dependency on the destination tensor `a` that we actually modify.

Changed files:
filename: ggml/src/ggml.c
patch: @@ -3687,6 +3687,7 @@ struct ggml_tensor * ggml_set_rows(
     result->op     = GGML_OP_SET_ROWS;
     result->src[0] = b;
     result->src[1] = c;
+    result->src[2] = a; // note: order is weird due to legacy reasons (https://github.com/ggml-org/llama.cpp/pull/16063#discussion_r2385795931)
 
     return result;
 }
Repository: ggml-org/llama.cpp
Pull request: vulkan : make the vulkan.hpp dynamic dispatcher instance private

* don't use VULKAN_HPP_DEFAULT_DISPATCH_LOADER_DYNAMIC_STORAGE which can cause conflicts if application or other libraries do the same
* https://github.com/ggml-org/ggml/pull/1344#discussion_r2371288834 
* https://github.com/ggml-org/llama.cpp/pull/15705#discussion_r2371478105

Changed files:
filename: ggml/src/ggml-vulkan/ggml-vulkan.cpp
patch: @@ -7,12 +7,14 @@
 
 // See https://github.com/KhronosGroup/Vulkan-Hpp?tab=readme-ov-file#extensions--per-device-function-pointers-
 #define VULKAN_HPP_DISPATCH_LOADER_DYNAMIC 1
+// We use VULKAN_HPP_DEFAULT_DISPATCHER, but not VULKAN_HPP_DEFAULT_DISPATCH_LOADER_DYNAMIC_STORAGE
+// to avoid conflicts with applications or other libraries who might use it.
+namespace vk::detail { class DispatchLoaderDynamic; }
+vk::detail::DispatchLoaderDynamic & ggml_vk_default_dispatcher();
+#define VULKAN_HPP_DEFAULT_DISPATCHER ggml_vk_default_dispatcher()
 
 #include <vulkan/vulkan.hpp>
 
-// See https://github.com/KhronosGroup/Vulkan-Hpp?tab=readme-ov-file#extensions--per-device-function-pointers-
-VULKAN_HPP_DEFAULT_DISPATCH_LOADER_DYNAMIC_STORAGE
-
 #include <algorithm>
 #include <cmath>
 #include <iomanip>
@@ -4508,14 +4510,20 @@ static bool ggml_vk_instance_portability_enumeration_ext_available(const std::ve
 static bool ggml_vk_instance_debug_utils_ext_available(const std::vector<vk::ExtensionProperties> & instance_extensions);
 static bool ggml_vk_device_is_supported(const vk::PhysicalDevice & vkdev);
 
+static vk::detail::DispatchLoaderDynamic ggml_vk_default_dispatcher_instance;
+
+vk::detail::DispatchLoaderDynamic & ggml_vk_default_dispatcher() {
+    return ggml_vk_default_dispatcher_instance;
+}
+
 static void ggml_vk_instance_init() {
     if (vk_instance_initialized) {
         return;
     }
     VK_LOG_DEBUG("ggml_vk_instance_init()");
 
     // See https://github.com/KhronosGroup/Vulkan-Hpp?tab=readme-ov-file#extensions--per-device-function-pointers-
-    VULKAN_HPP_DEFAULT_DISPATCHER.init(vkGetInstanceProcAddr);
+    ggml_vk_default_dispatcher_instance.init(vkGetInstanceProcAddr);
 
     uint32_t api_version = vk::enumerateInstanceVersion();
Repository: vercel/next.js
Pull request: Adjusted the warning message to be more descriptive

## Improve warning message for multiple lockfiles detection

### What?
Enhances the warning message when multiple lockfiles are detected to provide clearer guidance to users.

### Why?
The previous warning message was less informative and didn't provide clear instructions on how to resolve the issue. The improved message explicitly mentions:
- That Next.js is inferring the workspace root
- How to silence the warning by setting `turbopack.root` in the Next.js config
- A link to documentation for more information

### How?
Updated the warning text to be more descriptive and helpful, including a link to the relevant documentation.

<img width="1433" height="306" alt="image" src="https://github.com/user-attachments/assets/f92b3dd3-061c-45d0-8135-03b625079256" />


Addresses #81864

Changed files:
filename: packages/next/src/lib/find-root.ts
patch: @@ -35,11 +35,19 @@ export function findRootDir(cwd: string) {
 
   // Only warn if not in a build worker to avoid duplicate warnings
   if (typeof process.send !== 'function' && lockFiles.length > 1) {
+    const additionalLockFiles = lockFiles
+      .slice(0, -1)
+      .map((str) => '\n   * ' + str)
+      .join('')
+
     Log.warnOnce(
-      `Warning: Found multiple lockfiles. Selecting ${lockFiles[lockFiles.length - 1]}.\n   Consider removing the lockfiles at:${lockFiles
-        .slice(0, -1)
-        .map((str) => '\n   * ' + str)
-        .join('')}\n`
+      `Warning: Next.js inferred your workspace root, but it may not be correct.\n` +
+        `We detected multiple lockfiles and selected ${lockFiles[lockFiles.length - 1]} as the root directory.\n` +
+        `To silence this warning, set turbopack.root in your Next.js config, or consider ` +
+        `removing one of the lockfiles if it's not needed.\n` +
+        `  See https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack#root-directory for more information.\n` +
+        `Detected lockfiles:\n` +
+        `${additionalLockFiles}`
     )
   }
Repository: huggingface/transformers
Pull request: Improve `is_wandb_available` function to verify WandB installation

To reproduce:

- Install WandB
- Run an exp
- Uninstall
- check what returns `is_wandb_avaialble()` (returns `True`)


Changed files:
filename: src/transformers/integrations/integration_utils.py
patch: @@ -111,7 +111,14 @@ def is_wandb_available():
             "--report_to flag to control the integrations used for logging result (for instance --report_to none)."
         )
         return False
-    return importlib.util.find_spec("wandb") is not None
+    if importlib.util.find_spec("wandb") is not None:
+        import wandb
+
+        # wandb might still be detected by find_spec after an uninstall (leftover files or metadata), but not actually
+        # import correctly. To confirm it's fully installed and usable, we check for a key attribute like "run".
+        return hasattr(wandb, "run")
+    else:
+        return False
 
 
 def is_trackio_available():
Repository: ggml-org/llama.cpp
Pull request: ggml : fix GGML_F32_VEC_FMA argument order in ggml_vec_mad1_f32

See https://github.com/ggml-org/llama.cpp/pull/16063#discussion_r2385882166

Changed files:
filename: ggml/src/ggml-cpu/vec.h
patch: @@ -610,7 +610,7 @@ inline static void ggml_vec_mad1_f32(const int n, float * y, const float * x, co
         for (int i = 0; i < np; i += GGML_F32_STEP) {
             for (int j = 0; j < GGML_F32_ARR; j++) {
                 ay[j] = GGML_F32_VEC_LOAD(x + i + j*GGML_F32_EPR);
-                ay[j] = GGML_F32_VEC_FMA(ay[j], vs, vb);
+                ay[j] = GGML_F32_VEC_FMA(vb, ay[j], vs);
 
                 GGML_F32_VEC_STORE(y + i + j*GGML_F32_EPR, ay[j]);
             }

filename: tests/test-backend-ops.cpp
patch: @@ -6155,6 +6155,7 @@ static std::vector<std::unique_ptr<test_case>> make_test_cases_eval() {
     test_cases.emplace_back(new test_add1());
     test_cases.emplace_back(new test_scale());
     test_cases.emplace_back(new test_scale(GGML_TYPE_F32, {10, 10, 10, 10}, 2.0f, 1.0f));
+    test_cases.emplace_back(new test_scale(GGML_TYPE_F32, {100, 10, 10, 10}, 2.0f, 1.0f));
     test_cases.emplace_back(new test_softcap(GGML_TYPE_F32, {10, 10, 10, 10}, 50.0f));
     test_cases.emplace_back(new test_silu_back());
Repository: denoland/deno
Pull request: fix(ext/node): fix fs.watchFile trigger

The condition was not working correctly because it compared two Date objects directly, which always results in false even if they represent the same timestamp. The fix uses .getTime() to compare numeric values instead.

Ref: #29421 

Changed files:
filename: ext/node/polyfills/_fs/_fs_watch.ts
patch: @@ -298,7 +298,7 @@ class StatWatcher extends EventEmitter {
         while (true) {
           await delay(interval, { signal: this.#abortController.signal });
           const curr = await statAsync(filename);
-          if (curr?.mtime !== prev?.mtime) {
+          if (curr?.mtime.getTime() !== prev?.mtime.getTime()) {
             this.emit("change", curr, prev);
             prev = curr;
           }

filename: tests/unit_node/_fs/_fs_watch_test.ts
patch: @@ -2,6 +2,7 @@
 import { unwatchFile, watch, watchFile } from "node:fs";
 import { watch as watchPromise } from "node:fs/promises";
 import { assert, assertEquals } from "@std/assert";
+import { spy } from "@std/testing/mock";
 
 function wait(time: number) {
   return new Promise((resolve) => {
@@ -31,11 +32,17 @@ Deno.test({
   name: "watching a file with options",
   async fn() {
     const file = Deno.makeTempFileSync();
+    const spyFn = spy();
     watchFile(
       file,
-      () => {},
+      { interval: 10 },
+      spyFn,
     );
     await wait(100);
+    assertEquals(spyFn.calls.length, 0);
+    await Deno.writeTextFile(file, "something");
+    await wait(100);
+    assertEquals(spyFn.calls.length, 1);
     unwatchFile(file);
   },
 });
Repository: ggml-org/llama.cpp
Pull request: common : fix reasoning before forced tool call via tool_choice = required

*Make sure to read the [contributing guidelines](https://github.com/ggml-org/llama.cpp/blob/master/CONTRIBUTING.md) before submitting a PR*

Hello! This patch allows gpt-oss models to reason before doing a tool call, when `tool_choice` is set to required.

A similar issue, but for Qwen3/Hermes 2: #15247 

Changed files:
filename: common/chat.cpp
patch: @@ -1616,17 +1616,36 @@ static common_chat_params common_chat_params_init_gpt_oss(const common_chat_temp
                 );
             });
 
-            auto recipient_in_role = builder.add_rule("recipient_in_role",
-                "\"
assistant\"? \" to=functions.\" ( " +
-                string_join(tool_rules_recipient_in_role, " | ") + " )"
-            );
-
             auto recipient_in_channel = builder.add_rule("recipient_in_channel",
                 channel + " \" to=functions.\" ( " +
                 string_join(tool_rules_recipient_in_channel, " | ") + " )"
             );
 
-            builder.add_rule("root", recipient_in_role + " | " + recipient_in_channel);
+            if (data.grammar_lazy) {
+                auto recipient_in_role = builder.add_rule("recipient_in_role",
+                    "\"
assistant\"? \" to=functions.\" ( " +
+                    string_join(tool_rules_recipient_in_role, " | ") + " )"
+                );
+
+                builder.add_rule("root", recipient_in_role + " | " + recipient_in_channel);
+            } else {
+                auto not_end = builder.add_rule("not-end",
+                    "[^<] | \"<\" [^|] | \"<|\" [^e] | \"<|e\" [^n] | \"<|en\" [^d] | \"<|end\" [^|] | \"<|end|\" [^>]");
+                auto analysis = builder.add_rule("analysis",
+                    "\"
analysis
\" ( " + not_end + " )* \"
\"");
+                auto commentary = builder.add_rule("commentary",
+                    "\"
commentary
\" ( " + not_end + " )* \"
\"");
+
+                auto recipient_in_role = builder.add_rule("recipient_in_role",
+                    "\" to=functions.\" ( " + string_join(tool_rules_recipient_in_role, " | ") + " )"
+                );
+
+                builder.add_rule("root",
+                    "( " + analysis + " \"
assistant\" )? " +
+                    "( " + commentary + " \"
assistant\" )? " +
+                    "( " + recipient_in_role + " | " + recipient_in_channel + " )"
+                );
+            }
 
             // Trigger on tool calls that appear in the commentary channel
             data.grammar_triggers.push_back({
Repository: nodejs/node
Pull request: lib: graduate error codes that have been around for years

Handful of error messages that have been marked experimental for years... in one case 8 years! I think it's safe to mark them stable.

Changed files:
filename: doc/api/errors.md
patch: @@ -1796,8 +1796,6 @@ time.
 
 ### `ERR_INPUT_TYPE_NOT_ALLOWED`
 
-> Stability: 1 - Experimental
-
 The `--input-type` flag was used to attempt to execute a file. This flag can
 only be used with input via `--eval`, `--print`, or `STDIN`.
 
@@ -3095,17 +3093,13 @@ An invalid or unknown encoding option was passed to an API.
 
 ### `ERR_UNKNOWN_FILE_EXTENSION`
 
-> Stability: 1 - Experimental
-
 An attempt was made to load a module with an unknown or unsupported file
 extension.
 
 <a id="ERR_UNKNOWN_MODULE_FORMAT"></a>
 
 ### `ERR_UNKNOWN_MODULE_FORMAT`
 
-> Stability: 1 - Experimental
-
 An attempt was made to load a module with an unknown or unsupported format.
 
 <a id="ERR_UNKNOWN_SIGNAL"></a>
@@ -3183,8 +3177,6 @@ transformation with [type-stripping][].
 
 ### `ERR_USE_AFTER_CLOSE`
 
-> Stability: 1 - Experimental
-
 An attempt was made to use something that was already closed.
 
 <a id="ERR_VALID_PERFORMANCE_ENTRY_TYPE"></a>
Repository: facebook/react
Pull request: Improve flagging of `React.cache` to remove indirection in bundled code

Uses a better technique for conditionally disabling cache on the client

Changed files:
filename: packages/react/src/ReactCacheClient.js
patch: @@ -10,25 +10,25 @@
 import {disableClientCache} from 'shared/ReactFeatureFlags';
 import {cache as cacheImpl} from './ReactCacheImpl';
 
-export function cache<A: Iterable<mixed>, T>(fn: (...A) => T): (...A) => T {
-  if (disableClientCache) {
-    // On the client (i.e. not a Server Components environment) `cache` has
-    // no caching behavior. We just return the function as-is.
-    //
-    // We intend to implement client caching in a future major release. In the
-    // meantime, it's only exposed as an API so that Shared Components can use
-    // per-request caching on the server without breaking on the client. But it
-    // does mean they need to be aware of the behavioral difference.
-    //
-    // The rest of the behavior is the same as the server implementation — it
-    // returns a new reference, extra properties like `displayName` are not
-    // preserved, the length of the new function is 0, etc. That way apps can't
-    // accidentally depend on those details.
-    return function () {
-      // $FlowFixMe[incompatible-call]: We don't want to use rest arguments since we transpile the code.
-      return fn.apply(null, arguments);
-    };
-  } else {
-    return cacheImpl(fn);
-  }
+export function noopCache<A: Iterable<mixed>, T>(fn: (...A) => T): (...A) => T {
+  // On the client (i.e. not a Server Components environment) `cache` has
+  // no caching behavior. We just return the function as-is.
+  //
+  // We intend to implement client caching in a future major release. In the
+  // meantime, it's only exposed as an API so that Shared Components can use
+  // per-request caching on the server without breaking on the client. But it
+  // does mean they need to be aware of the behavioral difference.
+  //
+  // The rest of the behavior is the same as the server implementation — it
+  // returns a new reference, extra properties like `displayName` are not
+  // preserved, the length of the new function is 0, etc. That way apps can't
+  // accidentally depend on those details.
+  return function () {
+    // $FlowFixMe[incompatible-call]: We don't want to use rest arguments since we transpile the code.
+    return fn.apply(null, arguments);
+  };
 }
+
+export const cache: typeof noopCache = disableClientCache
+  ? noopCache
+  : cacheImpl;
Repository: electron/electron
Pull request: fix: remove `File.path` from types

Backport of #46005

See that PR for details.


Notes: none


Changed files:
filename: docs/api/web-utils.md
patch: @@ -16,7 +16,7 @@ Returns `string` - The file system path that this `File` object points to. In th
 
 This method superseded the previous augmentation to the `File` object with the `path` property.  An example is included below.
 
-```js
+```js @ts-nocheck
 // Before
 const oldPath = document.querySelector('input').files[0].path
 

filename: package.json
patch: @@ -10,7 +10,7 @@
     "@electron/fiddle-core": "^1.3.4",
     "@electron/github-app-auth": "^2.2.1",
     "@electron/lint-roller": "^2.4.0",
-    "@electron/typescript-definitions": "^9.0.0",
+    "@electron/typescript-definitions": "^9.1.2",
     "@octokit/rest": "^20.0.2",
     "@primer/octicons": "^10.0.0",
     "@types/minimist": "^1.2.5",

filename: yarn.lock
patch: @@ -285,10 +285,10 @@
     vscode-uri "^3.0.7"
     yaml "^2.4.5"
 
-"@electron/typescript-definitions@^9.0.0":
-  version "9.0.0"
-  resolved "https://registry.yarnpkg.com/@electron/typescript-definitions/-/typescript-definitions-9.0.0.tgz#1a8d9f36711ad93643af0662eef917189725c354"
-  integrity sha512-sK/e5ewiHZnpy0jzFW2NmH8KATkprwG962JzxJYw/GphxG/V55mP7UPJirmYUPeOA87TWhL910sjp5gdZ1SQmg==
+"@electron/typescript-definitions@^9.1.2":
+  version "9.1.2"
+  resolved "https://registry.yarnpkg.com/@electron/typescript-definitions/-/typescript-definitions-9.1.2.tgz#a9b7bfaed60a528cf1f0ce4a30f01360a27839f2"
+  integrity sha512-BLxuLnvGqKUdesLXh9jB6Ll5Q4Vnb0NqJxuNY+GBz5Q8icxpW2EcHO7gIBpgX+t6sHdfRn9r6Wpwh/CKXoaJng==
   dependencies:
     "@types/node" "^20.11.25"
     chalk "^5.3.0"
@@ -7042,14 +7042,7 @@ stringify-object@^3.3.0:
     is-obj "^1.0.1"
     is-regexp "^1.0.0"
 
-"strip-ansi-cjs@npm:strip-ansi@^6.0.1":
-  version "6.0.1"
-  resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-6.0.1.tgz#9e26c63d30f53443e9489495b2105d37b67a85d9"
-  integrity sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==
-  dependencies:
-    ansi-regex "^5.0.1"
-
-strip-ansi@^6.0.0, strip-ansi@^6.0.1:
+"strip-ansi-cjs@npm:strip-ansi@^6.0.1", strip-ansi@^6.0.0, strip-ansi@^6.0.1:
   version "6.0.1"
   resolved "https://registry.yarnpkg.com/strip-ansi/-/strip-ansi-6.0.1.tgz#9e26c63d30f53443e9489495b2105d37b67a85d9"
   integrity sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==
Repository: denoland/deno
Pull request: fix(ext/os): silently ignore invalid utf-8 characters in os vars

<!--
Before submitting a PR, please read https://docs.deno.com/runtime/manual/references/contributing

1. Give the PR a descriptive title.

  Examples of good title:
    - fix(std/http): Fix race condition in server
    - docs(console): Update docstrings
    - feat(doc): Handle nested reexports

  Examples of bad title:
    - fix #7123
    - update docs
    - fix bugs

2. Ensure there is a related issue and it is referenced in the PR text.
3. Ensure there are tests that cover the changes.
4. Ensure `cargo test` passes.
5. Ensure `./tools/format.js` passes without changing files.
6. Ensure `./tools/lint.js` passes.
7. Open as a draft PR if your work is still in progress. The CI won't run
   all steps, but you can add '[ci]' to a commit message to force it to.
8. If you would like to run the benchmarks on the CI, add the 'ci-bench' label.
-->

Fixes #29475 

Where would be the best place to add tests for this?

Changed files:
filename: ext/os/lib.rs
patch: @@ -183,7 +183,17 @@ fn op_env(
   state: &mut OpState,
 ) -> Result<HashMap<String, String>, PermissionCheckError> {
   state.borrow_mut::<PermissionsContainer>().check_env_all()?;
-  Ok(env::vars().collect())
+
+  Ok(
+    env::vars_os()
+      .filter_map(|(key_os, value_os)| {
+        key_os
+          .into_string()
+          .ok()
+          .and_then(|key| value_os.into_string().ok().map(|value| (key, value)))
+      })
+      .collect(),
+  )
 }
 
 fn get_env_var(key: &str) -> Result<Option<String>, OsError> {
Repository: nodejs/node
Pull request: child_process: move _channel to end-of-life

The `._channel` property has been deprecated for many years now. It's time to remove it.


Changed files:
filename: doc/api/deprecations.md
patch: @@ -2705,6 +2705,9 @@ Node.js versions.
 
 <!-- YAML
 changes:
+  - version: REPLACEME
+    pr-url: https://github.com/nodejs/node/pull/58527
+    description: End-of-Life.
   - version: v13.0.0
     pr-url: https://github.com/nodejs/node/pull/27949
     description: Runtime deprecation.
@@ -2713,7 +2716,7 @@ changes:
     description: Documentation-only.
 -->
 
-Type: Runtime
+Type: End-of-Life
 
 The `_channel` property of child process objects returned by `spawn()` and
 similar functions is not intended for public use. Use `ChildProcess.channel`

filename: lib/internal/child_process.js
patch: @@ -7,7 +7,6 @@ const {
   ArrayPrototypeSlice,
   FunctionPrototype,
   FunctionPrototypeCall,
-  ObjectDefineProperty,
   ObjectSetPrototypeOf,
   ReflectApply,
   StringPrototypeSlice,
@@ -56,7 +55,7 @@ const { TTY } = internalBinding('tty_wrap');
 const { UDP } = internalBinding('udp_wrap');
 const SocketList = require('internal/socket_list');
 const { owner_symbol } = require('internal/async_hooks').symbols;
-const { convertToValidSignal, deprecate } = require('internal/util');
+const { convertToValidSignal } = require('internal/util');
 const { isArrayBufferView } = require('internal/util/types');
 const spawn_sync = internalBinding('spawn_sync');
 const { kStateSymbol } = require('internal/dgram');
@@ -575,27 +574,12 @@ class Control extends EventEmitter {
   }
 }
 
-const channelDeprecationMsg = '_channel is deprecated. ' +
-                              'Use ChildProcess.channel instead.';
-
 let serialization;
 function setupChannel(target, channel, serializationMode) {
   const control = new Control(channel);
   target.channel = control;
   target[kChannelHandle] = channel;
 
-  ObjectDefineProperty(target, '_channel', {
-    __proto__: null,
-    get: deprecate(() => {
-      return target.channel;
-    }, channelDeprecationMsg, 'DEP0129'),
-    set: deprecate((val) => {
-      target.channel = val;
-    }, channelDeprecationMsg, 'DEP0129'),
-    configurable: true,
-    enumerable: false,
-  });
-
   target._handleQueue = null;
   target._pendingMessage = null;
 

filename: test/parallel/test-child-process-fork.js
patch: @@ -18,7 +18,6 @@
 // DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR
 // OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE
 // USE OR OTHER DEALINGS IN THE SOFTWARE.
-// Flags: --no-warnings
 'use strict';
 const common = require('../common');
 const assert = require('assert');
@@ -29,7 +28,6 @@ const debug = require('util').debuglog('test');
 
 const n = fork(fixtures.path('child-process-spawn-node.js'), args);
 
-assert.strictEqual(n.channel, n._channel);
 assert.deepStrictEqual(args, ['foo', 'bar']);
 
 n.on('message', (m) => {