helloadhavan/github_issues huggingface dataset:
Repository: electron/electron
Pull request: fix: in `Emit()`, don't leak converted Arg `Local<Values>` into caller's scope

#### Description of Change

The two `Emit(isolate, obj, name, Args&&... args)` methods convert `args` into an array of `Local<Value>s`  to pass to Node/V8. But they don't use a HandleScope, so these temporary handles are leaked into the caller's scopes.

In most calls this is OK since either `args` is empty or since the caller creates a scope right before emission, but not everywhere. It's more reliable to handle this in the `Emit()` functions, so this PR adds `EscapableHandleScope`s to plug the leaks.

#### Checklist

- [x] PR description included and stakeholders cc'd
- [x] `npm test` passes
- [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: none.

Changed files:
filename: shell/common/gin_helper/event_emitter_caller.h
patch: @@ -44,11 +44,13 @@ v8::Local<v8::Value> EmitEvent(v8::Isolate* isolate,
                                v8::Local<v8::Object> obj,
                                const StringType& name,
                                Args&&... args) {
+  v8::EscapableHandleScope scope{isolate};
   internal::ValueVector converted_args = {
       gin::StringToV8(isolate, name),
       gin::ConvertToV8(isolate, std::forward<Args>(args))...,
   };
-  return internal::CallMethodWithArgs(isolate, obj, "emit", &converted_args);
+  return scope.Escape(
+      internal::CallMethodWithArgs(isolate, obj, "emit", &converted_args));
 }
 
 // obj.custom_emit(args...)
@@ -57,11 +59,12 @@ v8::Local<v8::Value> CustomEmit(v8::Isolate* isolate,
                                 v8::Local<v8::Object> object,
                                 const char* custom_emit,
                                 Args&&... args) {
+  v8::EscapableHandleScope scope{isolate};
   internal::ValueVector converted_args = {
       gin::ConvertToV8(isolate, std::forward<Args>(args))...,
   };
-  return internal::CallMethodWithArgs(isolate, object, custom_emit,
-                                      &converted_args);
+  return scope.Escape(internal::CallMethodWithArgs(isolate, object, custom_emit,
+                                                   &converted_args));
 }
 
 template <typename T, typename... Args>
Repository: denoland/deno
Pull request: fix(fmt/markdown): fix regression with multi-line footnotes and inline math

What happened in this specific case was the parser used to actually treat these as code block. Now it treats it as a multi-paragraph footnote and that caused the issue

- https://github.com/dprint/dprint-plugin-markdown/pull/121/files

Changed files:
filename: .dprint.json
patch: @@ -67,9 +67,9 @@
   "plugins": [
     "https://plugins.dprint.dev/typescript-0.91.6.wasm",
     "https://plugins.dprint.dev/json-0.19.3.wasm",
-    "https://plugins.dprint.dev/markdown-0.17.6.wasm",
+    "https://plugins.dprint.dev/markdown-0.17.8.wasm",
     "https://plugins.dprint.dev/toml-0.6.2.wasm",
     "https://plugins.dprint.dev/exec-0.5.0.json@8d9972eee71fa1590e04873540421f3eda7674d0f1aae3d7c788615e7b7413d0",
-    "https://plugins.dprint.dev/g-plane/pretty_yaml-v0.4.0.wasm"
+    "https://plugins.dprint.dev/g-plane/pretty_yaml-v0.5.0.wasm"
   ]
 }

filename: Cargo.lock
patch: @@ -2517,9 +2517,9 @@ dependencies = [
 
 [[package]]
 name = "dprint-plugin-markdown"
-version = "0.17.6"
+version = "0.17.8"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "6ef42762177b1a74b52b98fe946cb88fa4a01f149b56208de72b43d2be0a54c6"
+checksum = "934a8e33f6f373b2fb66c288a468e3dae9a56a6c66bfecd5504fe566131afd3f"
 dependencies = [
  "anyhow",
  "dprint-core",

filename: cli/Cargo.toml
patch: @@ -102,7 +102,7 @@ dissimilar = "=1.0.4"
 dotenvy = "0.15.7"
 dprint-plugin-json = "=0.19.3"
 dprint-plugin-jupyter = "=0.1.3"
-dprint-plugin-markdown = "=0.17.6"
+dprint-plugin-markdown = "=0.17.8"
 dprint-plugin-typescript = "=0.91.6"
 env_logger = "=0.10.0"
 fancy-regex = "=0.10.0"
Repository: vercel/next.js
Pull request: Turbopack: add concurrency limit to effects

### What?

This avoids trying to apply too many effect in parallel.

Closes PACK-4510

Changed files:
filename: turbopack/crates/turbo-tasks/src/effect.rs
patch: @@ -2,6 +2,7 @@ use std::{borrow::Cow, future::Future, mem::replace, panic, pin::Pin};
 
 use anyhow::{anyhow, Result};
 use auto_hash_map::AutoSet;
+use futures::{StreamExt, TryStreamExt};
 use parking_lot::Mutex;
 use rustc_hash::FxHashSet;
 use tracing::{Instrument, Span};
@@ -17,6 +18,8 @@ use crate::{
     CollectiblesSource, NonLocalValue, ReadRef, ResolvedVc, TryJoinIterExt,
 };
 
+const APPLY_EFFECTS_CONCURRENCY_LIMIT: usize = 1024;
+
 /// A trait to emit a task effect as collectible. This trait only has one
 /// implementation, `EffectInstance` and no other implementation is allowed.
 /// The trait is private to this module so that no other implementation can be
@@ -168,17 +171,16 @@ pub async fn apply_effects(source: impl CollectiblesSource) -> Result<()> {
     }
     let span = tracing::info_span!("apply effects", count = effects.len());
     async move {
-        effects
-            .into_iter()
-            .map(async |effect| {
+        // Limit the concurrency of effects
+        futures::stream::iter(effects)
+            .map(Ok)
+            .try_for_each_concurrent(APPLY_EFFECTS_CONCURRENCY_LIMIT, async |effect| {
                 let Some(effect) = ResolvedVc::try_downcast_type::<EffectInstance>(effect) else {
                     panic!("Effect must only be implemented by EffectInstance");
                 };
                 effect.await?.apply().await
             })
-            .try_join()
-            .await?;
-        Ok(())
+            .await
     }
     .instrument(span)
     .await
@@ -251,12 +253,13 @@ impl Effects {
     pub async fn apply(&self) -> Result<()> {
         let span = tracing::info_span!("apply effects", count = self.effects.len());
         async move {
-            self.effects
-                .iter()
-                .map(async |effect| effect.apply().await)
-                .try_join()
-                .await?;
-            Ok(())
+            // Limit the concurrency of effects
+            futures::stream::iter(self.effects.iter())
+                .map(Ok)
+                .try_for_each_concurrent(APPLY_EFFECTS_CONCURRENCY_LIMIT, async |effect| {
+                    effect.apply().await
+                })
+                .await
         }
         .instrument(span)
         .await
Repository: nodejs/node
Pull request: test: enable ts test on win arm64

This should finally work 🥳 

@nodejs/typescript 

Changed files:
filename: test/es-module/test-typescript.mjs
patch: @@ -1,4 +1,4 @@
-import { skip, spawnPromisified, isWindows } from '../common/index.mjs';
+import { skip, spawnPromisified } from '../common/index.mjs';
 import * as fixtures from '../common/fixtures.mjs';
 import { match, strictEqual } from 'node:assert';
 import { test } from 'node:test';
@@ -270,10 +270,7 @@ test('execute a JavaScript file importing a cjs TypeScript file', async () => {
   strictEqual(result.code, 0);
 });
 
-// TODO(marco-ippolito) Due to a bug in SWC, the TypeScript loader
-// does not work on Windows arm64. This test should be re-enabled
-// when https://github.com/nodejs/node/issues/54645 is fixed
-test('execute a TypeScript test mocking module', { skip: isWindows && process.arch === 'arm64' }, async () => {
+test('execute a TypeScript test mocking module', async () => {
   const result = await spawnPromisified(process.execPath, [
     '--test',
     '--experimental-test-module-mocks',
Repository: nodejs/node
Pull request: doc, sqlite: add `--experimental-sqlite` note

Fixes #53906

Changed files:
filename: doc/api/sqlite.md
patch: @@ -6,7 +6,8 @@
 added: v22.5.0
 -->
 
-> Stability: 1.1 - Active development
+> Stability: 1.1 - Active development. Enable this API with the
+> [`--experimental-sqlite`][] CLI flag.
 
 <!-- source_link=lib/sqlite.js -->
 
@@ -314,6 +315,7 @@ exception.
 | `BLOB`    | `Uint8Array`         |
 
 [SQL injection]: https://en.wikipedia.org/wiki/SQL_injection
+[`--experimental-sqlite`]: cli.md#--experimental-sqlite
 [`sqlite3_changes64()`]: https://www.sqlite.org/c3ref/changes.html
 [`sqlite3_close_v2()`]: https://www.sqlite.org/c3ref/close.html
 [`sqlite3_exec()`]: https://www.sqlite.org/c3ref/exec.html
Repository: ggml-org/llama.cpp
Pull request: gguf-py : Fix disconnect-before-connect crash on Kubuntu

This fixes the crash upon load with venvs created with `--system-site-packages` to use `python3-pyside6.qtwidgets=python3-pyside6.qtwidgets=6.6.2-4` from Kubuntu 24.10. Using system Qt is not merely æsthetic; I need Qt to use KDE's file picker so that hidden folders are openable. For users on other platforms, this doesn't change anything or just improves correctness.

# Before

```console
$ gguf-editor-gui
Traceback (most recent call last):
  File "/home/home/CLionProjects/llamacpprocm/gguf-py/gguf/scripts/gguf_editor_gui.py", line 913, in load_file
    self.load_metadata()
  File "/home/home/CLionProjects/llamacpprocm/gguf-py/gguf/scripts/gguf_editor_gui.py", line 948, in load_metadata
    self.metadata_table.itemChanged.disconnect(self.on_metadata_changed)
RuntimeError: Failed to disconnect (<bound method GGUFEditorWindow.on_metadata_changed of <gguf.scripts.gguf_editor_gui.GGUFEditorWindow(0x3fe2f560) at 0x7f5754e84480>>) from signal "itemChanged(QTableWidgetItem*)".
```

# After

I was able to view `gemma-3-4b-it-Q4_K_M.gguf` successfully.

Changed files:
filename: gguf-py/gguf/scripts/gguf_editor_gui.py
patch: @@ -823,6 +823,7 @@ def __init__(self):
         self.modified = False
         self.metadata_changes = {}  # Store changes to apply when saving
         self.metadata_to_remove = set()  # Store keys to remove when saving
+        self.on_metadata_changed_is_connected = False
 
         self.setup_ui()
 
@@ -941,9 +942,11 @@ def load_metadata(self):
             return
 
         # Disconnect to prevent triggering during loading
-        with warnings.catch_warnings():
-            warnings.filterwarnings('ignore')
-            self.metadata_table.itemChanged.disconnect(self.on_metadata_changed)
+        if self.on_metadata_changed_is_connected:
+            with warnings.catch_warnings():
+                warnings.filterwarnings('ignore')
+                self.metadata_table.itemChanged.disconnect(self.on_metadata_changed)
+            self.on_metadata_changed_is_connected = False
 
         for i, (key, field) in enumerate(self.reader.fields.items()):
             self.metadata_table.insertRow(i)
@@ -1021,6 +1024,7 @@ def load_metadata(self):
 
         # Reconnect after loading
         self.metadata_table.itemChanged.connect(self.on_metadata_changed)
+        self.on_metadata_changed_is_connected = True
 
     def extract_array_values(self, field: ReaderField) -> list:
         """Extract all values from an array field."""
Repository: facebook/react
Pull request: Add 4.4.0 release to eslint rules CHANGELOG

Resolves #24233

Looking at what's changed in the `eslint-plugin-react-hooks` package between the 4.3.0 release and Monday's 4.4.0 "release" I see...

```sh
git diff c3f34e4beb67a4ddd85a9456ebc9013d123aa6ee 34aa5cfe0d9b6ec4667e02bf46ab34d83dfb2d6d packages/eslint-plugin-react-hooks/
```

```diff
diff --git a/packages/eslint-plugin-react-hooks/package.json b/packages/eslint-plugin-react-hooks/package.json
index 6bf810a77..1c99c2ffd 100644
--- a/packages/eslint-plugin-react-hooks/package.json
+++ b/packages/eslint-plugin-react-hooks/package.json
@@ -1,7 +1,7 @@
 {
   "name": "eslint-plugin-react-hooks",
   "description": "ESLint rules for React Hooks",
-  "version": "4.3.0",
+  "version": "4.4.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/facebook/react.git",
@@ -10,7 +10,6 @@
   "files": [
     "LICENSE",
     "README.md",
-    "build-info.json",
     "index.js",
     "cjs"
   ],
```

Changed files:
filename: packages/eslint-plugin-react-hooks/CHANGELOG.md
patch: @@ -1,3 +1,7 @@
+## 4.4.0
+
+* No changes, this was an automated release together with React 18.
+
 ## 4.3.0
 
 * Support ESLint 8. ([@MichaelDeBoey](https://github.com/MichaelDeBoey) in [#22248](https://github.com/facebook/react/pull/22248))
Repository: huggingface/transformers
Pull request: [tests, `qwen2_5_omni`] fix flaky tests

# What does this PR do?

cc @zucchini-nlp 

Fixes two `qwen2_5_omni` flaky issues:
1. Typo in the model name in `VLM_CLASS_NAMES` (used to skip tests) -> model was not being skipped -> flaky tests
2. `qwen2_5_omni` has a new config attribute corresponding to a token that can't be used in the output

Changed files:
filename: tests/generation/test_utils.py
patch: @@ -134,7 +134,7 @@
     "mistral3",
     "chameleon",
     "internvl",
-    "qwen2_5_omni",
+    "qwen2_5omni",  # the file is named `qwen2_5_omni`, but the model class is `Qwen2_5Omni`
 ]
 
 
@@ -230,6 +230,7 @@ def _get_logits_processor_kwargs(self, do_sample=False, config=None):
             for key in [
                 "image_token_id",
                 "video_token_id",
+                "audio_token_id",
                 "vision_start_token_id",
                 "audio_start_token_id",
                 "audio_end_token_id",
Repository: nodejs/node
Pull request: benchmark: adjust byte size for buffer-copy

Using bytes 0 doesn't make much sense for this benchmark. Using `32768` also makes it indeterministic. 

Changed files:
filename: benchmark/buffers/buffer-copy.js
patch: @@ -2,7 +2,7 @@
 const common = require('../common.js');
 
 const bench = common.createBenchmark(main, {
-  bytes: [0, 8, 128, 32 * 1024],
+  bytes: [8, 128, 1024],
   partial: ['true', 'false'],
   n: [6e6],
 });
Repository: facebook/react
Pull request: Remove unstable_createMutableSource from experimental build



## Summary

Since we don't have `useMutableSource` in the `experimental` release channel, I don't think we have a use case for `createMutableSource`. 

[`createMutableSource` was removed in #22292](https://github.com/facebook/react/pull/22292/files#diff-ec841d2a7a5da58f2a099b16be22f3f65670a8c3a658a449337b3d99baf8f597L25) which had to be reverted. But when we relanded #22292 in #22664 removal of `createMutableSource` was probably forgotten?

## How did you test this change?

- [x] CI


Changed files:
filename: packages/react/index.experimental.js
patch: @@ -22,7 +22,6 @@ export {
   createContext,
   createElement,
   createFactory,
-  createMutableSource as unstable_createMutableSource,
   createRef,
   createServerContext,
   forwardRef,
Repository: vercel/next.js
Pull request: De-dupe build_and_deploy run for PRs

This aims to avoid running the `build_and_deploy` workflow twice when pushed to the main Next.js repo and also opened as a PR. 

Follow-up to https://github.com/vercel/next.js/pull/78737

Validated against: https://github.com/vercel/next.js/actions/runs/14804173232/job/41569421246?pr=78795

Changed files:
filename: .github/workflows/build_and_deploy.yml
patch: @@ -18,6 +18,7 @@ env:
 
 jobs:
   deploy-target:
+    if: ${{ github.event_name != 'pull_request' || github.event.pull_request.head.repo.fork }}
     runs-on: ubuntu-latest
     outputs:
       value: ${{ steps.deploy-target.outputs.value }}
Repository: nodejs/node
Pull request: meta: move one or more collaborators to emeritus

This PR was generated by the [`find-inactive-collaborators.yml` workflow](https://github.com/nodejs/node/blob/main/.github/workflows/find-inactive-collaborators.yml).

@nodejs/tsc Please follow up with the [offboarding tasks](https://github.com/nodejs/node/blob/main/doc/contributing/offboarding.md).

Changed files:
filename: README.md
patch: @@ -451,8 +451,6 @@ For information about the governance of the Node.js project, see
   **Vladimir Morozov** <<vmorozov@microsoft.com>> (he/him)
 * [VoltrexKeyva](https://github.com/VoltrexKeyva) -
   **Mohammed Keyvanzadeh** <<mohammadkeyvanzade94@gmail.com>> (he/him)
-* [watilde](https://github.com/watilde) -
-  **Daijiro Wachi** <<daijiro.wachi@gmail.com>> (he/him)
 * [zcbenz](https://github.com/zcbenz) -
   **Cheng Zhao** <<zcbenz@gmail.com>> (he/him)
 * [ZYSzys](https://github.com/ZYSzys) -
@@ -707,6 +705,8 @@ For information about the governance of the Node.js project, see
   **Vladimir Kurchatkin** <<vladimir.kurchatkin@gmail.com>>
 * [vsemozhetbyt](https://github.com/vsemozhetbyt) -
   **Vse Mozhet Byt** <<vsemozhetbyt@gmail.com>> (he/him)
+* [watilde](https://github.com/watilde) -
+  **Daijiro Wachi** <<daijiro.wachi@gmail.com>> (he/him)
 * [watson](https://github.com/watson) -
   **Thomas Watson** <<w@tson.dk>>
 * [whitlockjc](https://github.com/whitlockjc) -
Repository: huggingface/transformers
Pull request: fix: remove classmethod from `Qwen2_5OmniConfig.get_text_config`

# What does this PR do?

  - Since the `get_text_config` references an instance variable within the class (`self.thinker_config`), the `get_text_config` method should not be a classmethod.

  - Before this fix, users were getting the following error:

    ''' AttributeError: type object 'Qwen2_5OmniConfig' has no attribute 'thinker_config' '''

  - This commit simply removes the `classmethod` wrapper from the `get_text_config` method

Changed files:
filename: src/transformers/models/qwen2_5_omni/configuration_qwen2_5_omni.py
patch: @@ -1045,7 +1045,6 @@ def __init__(
 
         super().__init__(**kwargs)
 
-    @classmethod
     def get_text_config(self, decoder=False) -> "PretrainedConfig":
         """
         Returns the config that is meant to be used with text IO. On most models, it is the original config instance

filename: src/transformers/models/qwen2_5_omni/modular_qwen2_5_omni.py
patch: @@ -1030,7 +1030,6 @@ def __init__(
 
         super().__init__(**kwargs)
 
-    @classmethod
     def get_text_config(self, decoder=False) -> "PretrainedConfig":
         """
         Returns the config that is meant to be used with text IO. On most models, it is the original config instance
Repository: facebook/react
Pull request: [ReactDebugTools] add custom error type for future new hooks

## Summary

<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->

- In ReactDebugTools, we maintain a list of react's built-in hooks in `Dispatcher`. If react adds more built-in hooks in future releases, and user hasn't upgraded the tool (e.g. devtool extension), this function will throw and might be confusing to users.
- This PR adds a custom error `UnsupportedFeatureError`  in ReactDebugTools. It also exports the name of the error as a string so devtool can show a more friendly message to let users know the issue can be resolved by upgrading.

## Next
This is to unblock https://github.com/mondaychen/react/pull/1 and https://github.com/mondaychen/react/pull/2 so that we can _resolve_ https://github.com/facebook/react/issues/24096


## How did you test this change?

<!--
  Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
  How exactly did you verify that your PR solves the issue you wanted to solve?
  If you leave this empty, your PR will very likely be closed.
-->
I tested it by temporarily removing `useEffect` hook and test in an application that calls it
<img width="1552" alt="Screen Shot 2022-03-25 at 12 34 06 PM" src="https://user-images.githubusercontent.com/1001890/160192308-15381aea-db18-4967-82f2-e0ce19adc92d.png">

After adding a custom view we can explicitly ask user to upgrade: https://github.com/mondaychen/react/pull/2



Changed files:
filename: packages/react-debug-tools/src/ReactDebugHooks.js
patch: @@ -356,6 +356,23 @@ const Dispatcher: DispatcherType = {
   useId,
 };
 
+// create a proxy to throw a custom error
+// in case future versions of React adds more hooks
+const DispatcherProxyHandler = {
+  get(target, prop) {
+    if (target.hasOwnProperty(prop)) {
+      return target[prop];
+    }
+    const error = new Error('Missing method in Dispatcher: ' + prop);
+    // Note: This error name needs to stay in sync with react-devtools-shared
+    // TODO: refactor this if we ever combine the devtools and debug tools packages
+    error.name = 'UnsupportedFeatureError';
+    throw error;
+  },
+};
+
+const DispatcherProxy = new Proxy(Dispatcher, DispatcherProxyHandler);
+
 // Inspect
 
 export type HookSource = {
@@ -664,7 +681,7 @@ export function inspectHooks<Props>(
 
   const previousDispatcher = currentDispatcher.current;
   let readHookLog;
-  currentDispatcher.current = Dispatcher;
+  currentDispatcher.current = DispatcherProxy;
   let ancestorStackError;
   try {
     ancestorStackError = new Error();
@@ -708,7 +725,7 @@ function inspectHooksOfForwardRef<Props, Ref>(
 ): HooksTree {
   const previousDispatcher = currentDispatcher.current;
   let readHookLog;
-  currentDispatcher.current = Dispatcher;
+  currentDispatcher.current = DispatcherProxy;
   let ancestorStackError;
   try {
     ancestorStackError = new Error();
Repository: vercel/next.js
Pull request: [build-sourcemaps] Include codeframes in prod when sourcemaps are enabled

Sourcemaps will be far more expensive than creating the codeframe which is critical for the error to be useful at a glance.

This won't affect prod runtime unless it runs with `--enable-source-maps` which is not the default.

I haven't added any test assertions for this yet since there's more broken behavior to be fixed before the assertions will be useful for `next build`.

Changed files:
filename: packages/next/src/server/patch-error-inspect.ts
patch: @@ -184,7 +184,6 @@ function getSourcemappedFrameIfPossible(
   inspectOptions: util.InspectOptions
 ): {
   stack: IgnoreableStackFrame
-  // DEV only
   code: string | null
 } {
   const sourceMapCacheEntry = sourceMapCache.get(frame.file)
@@ -322,14 +321,11 @@ function getSourcemappedFrameIfPossible(
     ignored,
   }
 
-  const codeFrame =
-    process.env.NODE_ENV !== 'production'
-      ? getOriginalCodeFrame(
-          originalFrame,
-          sourceContent,
-          inspectOptions.colors
-        )
-      : null
+  const codeFrame = getOriginalCodeFrame(
+    originalFrame,
+    sourceContent,
+    inspectOptions.colors
+  )
 
   return {
     stack: originalFrame,
@@ -363,7 +359,7 @@ function parseAndSourceMap(
   const sourceMapCache: SourceMapCache = new Map()
 
   let sourceMappedStack = ''
-  let sourceFrameDEV: null | string = null
+  let sourceFrame: null | string = null
   for (const frame of unsourcemappedStack) {
     if (frame.file === null) {
       sourceMappedStack += '\n' + frameToString(frame)
@@ -376,13 +372,12 @@ function parseAndSourceMap(
       )
 
       if (
-        process.env.NODE_ENV !== 'production' &&
         sourcemappedFrame.code !== null &&
-        sourceFrameDEV === null &&
+        sourceFrame === null &&
         // TODO: Is this the right choice?
         !sourcemappedFrame.stack.ignored
       ) {
-        sourceFrameDEV = sourcemappedFrame.code
+        sourceFrame = sourcemappedFrame.code
       }
       if (!sourcemappedFrame.stack.ignored) {
         // TODO: Consider what happens if every frame is ignore listed.
@@ -400,7 +395,7 @@ function parseAndSourceMap(
     ': ' +
     error.message +
     sourceMappedStack +
-    (sourceFrameDEV !== null ? '\n' + sourceFrameDEV : '')
+    (sourceFrame !== null ? '\n' + sourceFrame : '')
   )
 }