helloadhavan/github_issues huggingface dataset:
Repository: vercel/next.js
Pull request: Add test for external middleware rewrite with changed headers

### What?

Within Issue https://github.com/vercel/next.js/issues/48040 / PR #49487 the middleware proxy for external rewrites was fixed. Unfortunately, this does not work when you change the headers in your middleware (according to https://vercel.com/templates/next.js/edge-functions-modify-request-header)

### Why?

We still have issues with the latest canary

### How?

Unfortunately I was not able to find the issue, just recreating the bug in a testcase

Changed files:
filename: test/e2e/middleware-rewrites/app/middleware.js
patch: @@ -23,6 +23,44 @@ export async function middleware(request) {
     })
   }
 
+  if (
+    url.pathname.includes(
+      '/middleware-external-rewrite-body-headers-return-body'
+    )
+  ) {
+    const tmpHeaders = new Headers(request.headers)
+
+    tmpHeaders.set('x-hello-from-middleware1', 'hello')
+
+    return NextResponse.rewrite(
+      'https://next-data-api-endpoint.vercel.app/api/echo-body',
+      {
+        request: {
+          headers: tmpHeaders,
+        },
+      }
+    )
+  }
+
+  if (
+    url.pathname.includes(
+      '/middleware-external-rewrite-body-headers-return-headers'
+    )
+  ) {
+    const tmpHeaders = new Headers(request.headers)
+
+    tmpHeaders.set('x-hello-from-middleware1', 'hello')
+
+    return NextResponse.rewrite(
+      'https://next-data-api-endpoint.vercel.app/api/echo-headers',
+      {
+        request: {
+          headers: tmpHeaders,
+        },
+      }
+    )
+  }
+
   if (url.pathname.includes('/middleware-external-rewrite-body')) {
     return NextResponse.rewrite(
       'https://next-data-api-endpoint.vercel.app/api/echo-body'

filename: test/e2e/middleware-rewrites/test/index.test.ts
patch: @@ -72,6 +72,34 @@ describe('Middleware Rewrite', () => {
       expect(await res.text()).toEqual(body)
     })
 
+    it('should handle middleware rewrite with body and headers correctly', async () => {
+      const body = JSON.stringify({ hello: 'world' })
+      const res = await next.fetch(
+        '/middleware-external-rewrite-body-headers-return-body',
+        {
+          redirect: 'manual',
+          method: 'POST',
+          body,
+        }
+      )
+
+      expect(res.status).toBe(200)
+      expect(await res.text()).toEqual(body)
+
+      const resWithHeaders = await next.fetch(
+        '/middleware-external-rewrite-body-headers-return-headers',
+        {
+          redirect: 'manual',
+          method: 'POST',
+          body,
+        }
+      )
+
+      expect(resWithHeaders.status).toBe(200)
+      const json = await resWithHeaders.json()
+      expect(json.headers['x-hello-from-middleware1']).toBe('hello')
+    })
+
     it('should handle static dynamic rewrite from middleware correctly', async () => {
       const browser = await webdriver(next.url, '/rewrite-to-static')
Repository: nodejs/node
Pull request: doc,crypto: link keygen to supported types

This removes the inline enum of supported asymmetric key types in favour of the dedicated anchor established in #59492

Changed files:
filename: doc/api/crypto.md
patch: @@ -4009,8 +4009,8 @@ changes:
   * `publicKey` {string | Buffer | KeyObject}
   * `privateKey` {string | Buffer | KeyObject}
 
-Generates a new asymmetric key pair of the given `type`. RSA, RSA-PSS, DSA, EC,
-Ed25519, Ed448, X25519, X448, and DH are currently supported.
+Generates a new asymmetric key pair of the given `type`. See the
+supported [asymmetric key types][].
 
 If a `publicKeyEncoding` or `privateKeyEncoding` was specified, this function
 behaves as if [`keyObject.export()`][] had been called on its result. Otherwise,
@@ -4131,8 +4131,8 @@ changes:
   * `publicKey` {string | Buffer | KeyObject}
   * `privateKey` {string | Buffer | KeyObject}
 
-Generates a new asymmetric key pair of the given `type`. RSA, RSA-PSS, DSA, EC,
-Ed25519, Ed448, X25519, X448, DH, and ML-DSA[^openssl35] are currently supported.
+Generates a new asymmetric key pair of the given `type`. See the
+supported [asymmetric key types][].
 
 If a `publicKeyEncoding` or `privateKeyEncoding` was specified, this function
 behaves as if [`keyObject.export()`][] had been called on its result. Otherwise,
Repository: facebook/react
Pull request: Export addTransitionType for www

need dis based api

Changed files:
filename: packages/react/index.fb.js
patch: @@ -39,6 +39,7 @@ export {
   unstable_SuspenseList,
   unstable_ViewTransition,
   unstable_TracingMarker,
+  unstable_addTransitionType,
   unstable_useCacheRefresh,
   use,
   useActionState,
Repository: ggml-org/llama.cpp
Pull request: docker : fix vulkan build

Add now required `python3-dev` package.

Successful image build:
https://github.com/CISC/llama.cpp/actions/runs/21703843820/job/62590016764

Changed files:
filename: .devops/vulkan.Dockerfile
patch: @@ -54,6 +54,7 @@ RUN apt-get update \
     build-essential \
     git \
     python3 \
+    python3-dev \
     python3-pip \
     python3-wheel \
     && pip install --break-system-packages --upgrade setuptools \
Repository: vuejs/vue
Pull request: Update LICENSE


Changed files:
filename: LICENSE
patch: @@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2013-2016 Yuxi Evan You
+Copyright (c) 2013-2017 Yuxi Evan You
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
Repository: ggml-org/llama.cpp
Pull request: vendor : update BoringSSL to 0.20260204.0


Changed files:
filename: vendor/cpp-httplib/CMakeLists.txt
patch: @@ -39,7 +39,7 @@ if (LLAMA_BUILD_BORINGSSL)
     set(FIPS OFF CACHE BOOL "Enable FIPS (BoringSSL)")
 
     set(BORINGSSL_GIT "https://boringssl.googlesource.com/boringssl" CACHE STRING "BoringSSL git repository")
-    set(BORINGSSL_VERSION "0.20251002.0" CACHE STRING "BoringSSL version")
+    set(BORINGSSL_VERSION "0.20260204.0" CACHE STRING "BoringSSL version")
 
     message(STATUS "Fetching BoringSSL version ${BORINGSSL_VERSION}")
Repository: vuejs/vue
Pull request: [weex] fix the removeChild logic for text node

Fix #4046 . Should check the nodeType of child, not the node itself.


Changed files:
filename: src/platforms/weex/runtime/node-ops.js
patch: @@ -34,8 +34,8 @@ export function insertBefore (node, target, before) {
 }
 
 export function removeChild (node, child) {
-  if (node.nodeType === 3) {
-    node.parentNode.setAttr('value', '')
+  if (child.nodeType === 3) {
+    node.setAttr('value', '')
     return
   }
   node.removeChild(child)
Repository: ggml-org/llama.cpp
Pull request: vulkan: fix GPU deduplication logic.

As reported in https://github.com/ggml-org/llama.cpp/issues/19221, the (same uuid, same driver) logic is problematic for windows+intel igpu.

Let's just avoid filtering for MoltenVK which is apple-specific, and keep the logic the  same as before 88d23ad5 - just dedup based on UUID.

Verified that MacOS + 4xVega still reports 4 GPUs with this version.

*Make sure to read the [contributing guidelines](https://github.com/ggml-org/llama.cpp/blob/master/CONTRIBUTING.md) before submitting a PR*


Changed files:
filename: ggml/src/ggml-vulkan/ggml-vulkan.cpp
patch: @@ -5561,9 +5561,9 @@ static void ggml_vk_instance_init() {
                 // Check if there are two physical devices corresponding to the same GPU
                 // This handles the case where the same GPU appears with different drivers (e.g., RADV + AMDVLK on Linux),
                 // see https://github.com/ggml-org/llama.cpp/pull/7582 for original deduplication.
-                // However, for MoltenVK on macOS, multiple GPUs on the same card may report the same UUID,
-                // see https://github.com/KhronosGroup/MoltenVK/issues/2683. Until this is fixed, we'll only deduplicate
-                // when drivers differ (same driver + same UUID = likely different GPUs)
+                // MoltenVK on macOS may report the same UUID for distinct GPUs on multi-GPU cards,
+                // see https://github.com/KhronosGroup/MoltenVK/issues/2683. Skip when both old/new
+                // driver is MoltenVK
                 auto old_device = std::find_if(
                     vk_instance.device_indices.begin(),
                     vk_instance.device_indices.end(),
@@ -5580,11 +5580,9 @@ static void ggml_vk_instance_init() {
                             old_id.deviceLUIDValid && new_id.deviceLUIDValid &&
                             std::equal(std::begin(old_id.deviceLUID), std::end(old_id.deviceLUID), std::begin(new_id.deviceLUID))
                         );
+                        bool both_molten_vk = (new_driver.driverID == vk::DriverId::eMoltenvk && old_driver.driverID == vk::DriverId::eMoltenvk);
 
-                        // Only deduplicate if same UUID AND different drivers
-                        // (same driver + same UUID on MoltenVK = likely different GPUs on multi-GPU card)
-                        bool different_driver = (old_driver.driverID != new_driver.driverID);
-                        return same_uuid && different_driver;
+                        return same_uuid && !both_molten_vk;
                     }
                 );
                 if (old_device == vk_instance.device_indices.end()) {
Repository: facebook/react
Pull request: Codesandbox: upgrade to Node.js 18

Turns out Codesandbox didn't support `String.prototype.replaceAll` in #26329.

This updates the config to use Node.js 18 for Codesandbox builds.

Changed files:
filename: .codesandbox/ci.json
patch: @@ -1,7 +1,7 @@
 {
   "packages": ["packages/react", "packages/react-dom", "packages/scheduler"],
   "buildCommand": "download-build-in-codesandbox-ci",
-  "node": "14",
+  "node": "18",
   "publishDirectory": {
     "react": "build/oss-experimental/react",
     "react-dom": "build/oss-experimental/react-dom",
Repository: ollama/ollama
Pull request: Add Nix and Flox to package manager listing

Ollama is available in both the Nix and Flox package manager.
I thought it'd be a good idea to list them here as well. 😁

Changed files:
filename: README.md
patch: @@ -337,6 +337,8 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Pacman](https://archlinux.org/packages/extra/x86_64/ollama/)
 - [Helm Chart](https://artifacthub.io/packages/helm/ollama-helm/ollama)
 - [Guix channel](https://codeberg.org/tusharhero/ollama-guix)
+- [Nix package](https://search.nixos.org/packages?channel=24.05&show=ollama&from=0&size=50&sort=relevance&type=packages&query=ollama)
+- [Flox](https://flox.dev/blog/ollama-part-one)
 
 ### Libraries
Repository: facebook/react
Pull request: Set enableViewTransition to dynamic for www

Unblocks internal experimentation

Changed files:
filename: packages/react/index.fb.js
patch: @@ -37,6 +37,7 @@ export {
   unstable_LegacyHidden,
   unstable_Scope,
   unstable_SuspenseList,
+  unstable_ViewTransition,
   unstable_TracingMarker,
   unstable_useCacheRefresh,
   use,

filename: packages/shared/forks/ReactFeatureFlags.www-dynamic.js
patch: @@ -39,6 +39,7 @@ export const enableSiblingPrerendering = __VARIANT__;
 export const enableUseResourceEffectHook = __VARIANT__;
 export const enableRemoveConsolePatches = __VARIANT__;
 export const enableFastAddPropertiesInDiffing = __VARIANT__;
+export const enableViewTransition = __VARIANT__;
 
 // TODO: These flags are hard-coded to the default values used in open source.
 // Update the tests so that they pass in either mode, then set these

filename: packages/shared/forks/ReactFeatureFlags.www.js
patch: @@ -38,6 +38,7 @@ export const {
   enableOwnerStacks,
   enableRemoveConsolePatches,
   enableFastAddPropertiesInDiffing,
+  enableViewTransition,
 } = dynamicFeatureFlags;
 
 // On WWW, __EXPERIMENTAL__ is used for a new modern build.
@@ -60,7 +61,6 @@ export const enableLegacyFBSupport = true;
 export const enableYieldingBeforePassive = false;
 
 export const enableThrottledScheduling = false;
-export const enableViewTransition = false;
 
 export const enableHydrationLaneScheduling = true;
Repository: ggml-org/llama.cpp
Pull request: model: (qwen3next) correct vectorized key_gdiff calculation

Testing with the provided prompt from https://github.com/ggml-org/llama.cpp/issues/19305

<img width="837" height="437" alt="image" src="https://github.com/user-attachments/assets/54f19beb-a9d0-4f10-bc33-747057f36fe7" />



Changed files:
filename: src/models/qwen3next.cpp
patch: @@ -265,9 +265,15 @@ std::pair<ggml_tensor *, ggml_tensor *> llm_build_qwen3next::build_delta_net_chu
     cb(g_diff, "g_diff", il); // shape: (chunk_size, 1, n_chunks, H_v * n_seqs)
 
     ggml_tensor * g_diff_exp = ggml_exp(ctx0, g_diff);
-    ggml_tensor * key_gdiff = ggml_mul(ctx0, k, g_diff_exp);
+    ggml_tensor * g_diff_exp_t = ggml_reshape_4d(ctx0, g_diff_exp, 
+                                                 1, chunk_size, n_chunks, g_diff_exp->ne[3]);
+
+    ggml_tensor * key_gdiff = ggml_mul(ctx0, k, g_diff_exp_t);
     cb(key_gdiff, "key_gdiff", il); // shape: (S_k, chunk_size, n_chunks, H_v * n_seqs)
 
+    ggml_tensor * key_gdiff_t = ggml_cont(ctx0, ggml_transpose(ctx0, key_gdiff)); 
+    cb(key_gdiff_t, "key_gdiff_t", il); // shape: (chunk_size, S_k, n_chunks, H_v * n_seqs)
+
 
     // state to be updated per chunk
     ggml_tensor * new_state = state; // ggml_dup(ctx0, state);
@@ -322,9 +328,9 @@ std::pair<ggml_tensor *, ggml_tensor *> llm_build_qwen3next::build_delta_net_chu
             : ggml_concat(ctx0, core_attn_out, core_attn_out_chunk, 2);
 
         // kgdmulvnew = (key_gdiff).transpose(-1, -2) @ v_new
-        ggml_tensor * k_gdiff = ggml_cont(ctx0, get_slice_2d(ctx0, key_gdiff, chunk));
+        ggml_tensor * k_gdiff_t = get_slice_2d(ctx0, key_gdiff_t, chunk);
         //ggml_tensor * kgdmulvnew = ggml_mul_mat(ctx0, k_gdiff, v_new); // this is slower on metal, why?
-        ggml_tensor * kgdmulvnew = ggml_mul_mat(ctx0, v_new_t, ggml_cont(ctx0, ggml_transpose(ctx0, k_gdiff)));
+        ggml_tensor * kgdmulvnew = ggml_mul_mat(ctx0, v_new_t, k_gdiff_t);
 
         // last_recurrent_state = last_recurrent_state * g_last + kgdmulvnew
         ggml_tensor * gexp_last_chunk = ggml_cont(ctx0, get_slice_2d(ctx0, g_last_exp, chunk));
Repository: vercel/next.js
Pull request: Fix typed routes test expectations

Follow up to https://github.com/vercel/next.js/pull/86273

The typed routes test was checking for `/project/[slug]` in the `RedirectRoutes` type, but this route doesn't actually exist in the test fixture anymore. The test fixture only has redirects defined for `/blog/[category]/[[...slug]]`.

When Next.js generates the typed routes during the build, it only includes routes that actually exist in the project structure. The test was expecting a route that wasn't present, which would cause the test to fail if the generated types were correct.

This removes `/project/[slug]` from the expected `RedirectRoutes` type so the test expectations match what's actually generated.

Also includes a minor formatting fix in `apps/bundle-analyzer/next-env.d.ts` to use consistent semicolons and double quotes per the project's style guidelines.

Changed files:
filename: test/e2e/app-dir/typed-routes/typed-routes.test.ts
patch: @@ -6,7 +6,7 @@ type AppRoutes = "/" | "/_shop/[[...category]]" | "/dashboard" | "/dashboard/set
 type AppRouteHandlerRoutes = "/api-test" | "/api/docs/[...slug]" | "/api/shop/[[...category]]" | "/api/users/[id]"
 type PageRoutes = "/about" | "/users/[id]"
 type LayoutRoutes = "/" | "/dashboard"
-type RedirectRoutes = "/blog/[category]/[[...slug]]" | "/project/[slug]"
+type RedirectRoutes = "/blog/[category]/[[...slug]]"
 type RewriteRoutes = "/api-legacy/[version]/[[...endpoint]]" | "/docs-old/[...path]"
 type Routes = AppRoutes | PageRoutes | LayoutRoutes | RedirectRoutes | RewriteRoutes | AppRouteHandlerRoutes
 `
Repository: electron/electron
Pull request: fix: remove `killed` check to allow multiple signals

#### Description of Change

<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

Multiple instances of `SIGUSR2` must be handled for a good HMR experience. I can't think of a compelling reason to make signal forwarding contingent on the value of `child.killed`.

See: https://github.com/electron/electron/pull/33589

notes: none


Changed files:
filename: npm/cli.js
patch: @@ -5,7 +5,9 @@ const proc = require('child_process');
 const electron = require('./');
 
 const child = proc.spawn(electron, process.argv.slice(2), { stdio: 'inherit', windowsHide: false });
+let childClosed = false;
 child.on('close', function (code, signal) {
+  childClosed = true;
   if (code === null) {
     console.error(electron, 'exited with signal', signal);
     process.exit(1);
@@ -15,11 +17,12 @@ child.on('close', function (code, signal) {
 
 const handleTerminationSignal = function (signal) {
   process.on(signal, function signalHandler () {
-    if (!child.killed) {
+    if (!childClosed) {
       child.kill(signal);
     }
   });
 };
 
 handleTerminationSignal('SIGINT');
 handleTerminationSignal('SIGTERM');
+handleTerminationSignal('SIGUSR2');

filename: script/start.js
patch: @@ -5,11 +5,15 @@ const utils = require('./lib/utils');
 const electronPath = utils.getAbsoluteElectronExec();
 
 const child = cp.spawn(electronPath, process.argv.slice(2), { stdio: 'inherit' });
-child.on('close', (code) => process.exit(code));
+let childClosed = false;
+child.on('close', (code) => {
+  childClosed = true;
+  process.exit(code);
+});
 
 const handleTerminationSignal = (signal) =>
   process.on(signal, () => {
-    if (!child.killed) {
+    if (!childClosed) {
       child.kill(signal);
     }
   });
Repository: ollama/ollama
Pull request: fix(test): do not clobber models directory

these tests create these blobs in the user's blobs directory

```
sha256-4e06a933feaf7e21f9ea4442bec46e1a5c99f5931d06caecb5603653628ad9f1
sha256-5738747671c0649396ed0b138cf8daed5bdb7140df5ee18d0a520295045feac3
sha256-d45102d885e542798514de3c17c3d431732d90ff3bd5c743e411dcd93c7f8d1a
```

Changed files:
filename: server/model_test.go
patch: @@ -139,6 +139,7 @@ The temperature in San Francisco, CA is 70°F and in Toronto, Canada is 20°C.`,
 
 func TestParseFromFileFromLayer(t *testing.T) {
 	tempModels := t.TempDir()
+	t.Setenv("OLLAMA_MODELS", tempModels)
 
 	file, err := os.CreateTemp(tempModels, "")
 	if err != nil {
@@ -189,6 +190,7 @@ func TestParseFromFileFromLayer(t *testing.T) {
 
 func TestParseLayerFromCopy(t *testing.T) {
 	tempModels := t.TempDir()
+	t.Setenv("OLLAMA_MODELS", tempModels)
 
 	file2, err := os.CreateTemp(tempModels, "")
 	if err != nil {
Repository: huggingface/transformers
Pull request: Fix gpt2 tokenizer `add_prefix_space` default value 

# What does this PR do?

This PR fixes a regression wrt gpt2 tokenizer. `add_prefix_space` should be `False`, not sure if there are other regression like that cc @itazap 

Changed files:
filename: src/transformers/models/gpt2/tokenization_gpt2.py
patch: @@ -101,7 +101,7 @@ def __init__(
         bos_token="
",
         eos_token="
",
         pad_token=None,
-        add_prefix_space=True,
+        add_prefix_space=False,
         add_bos_token=False,
         vocab: Optional[dict] = None,
         merges: Optional[list] = None,
Repository: vuejs/vue
Pull request: tweak comment of coverage setting

As a bit something, I found a consistency disagreement in the comment. 😉 

Changed files:
filename: build/karma.cover.config.js
patch: @@ -13,7 +13,7 @@ module.exports = function (config) {
     singleRun: true
   })
 
-  // add babel-plugin-coverage for code intrumentation
+  // add babel-plugin-istanbul for code intrumentation
   options.webpack.babel = {
     plugins: [['istanbul', {
       exclude: [
Repository: ggml-org/llama.cpp
Pull request: vendor : add missing llama_add_compile_flags

~Hopefully fixes CI~Ensure `httplib` and `boringssl`/`libressl` are built with sanitizer options, see https://github.com/ggml-org/llama.cpp/pull/19291#discussion_r2761613566

Changed files:
filename: vendor/cpp-httplib/CMakeLists.txt
patch: @@ -3,9 +3,14 @@ license_add_file("cpp-httplib" "LICENSE")
 
 find_package(Threads REQUIRED)
 
+llama_add_compile_flags()
+
 add_library(${TARGET} STATIC httplib.cpp httplib.h)
-if (NOT MSVC)
-    # disable warnings in 3rd party code
+
+# disable warnings in 3rd party code
+if (CMAKE_CXX_COMPILER_ID STREQUAL "MSVC")
+    target_compile_options(${TARGET} PRIVATE /w)
+else()
     target_compile_options(${TARGET} PRIVATE -w)
 endif()
 
@@ -146,6 +151,23 @@ elseif (LLAMA_OPENSSL)
     endif()
 endif()
 
+# disable warnings in 3rd party code
+if(LLAMA_BUILD_BORINGSSL OR LLAMA_BUILD_LIBRESSL)
+    if (CMAKE_CXX_COMPILER_ID STREQUAL "MSVC")
+        target_compile_options(ssl PRIVATE /w)
+        target_compile_options(crypto PRIVATE /w)
+        if(LLAMA_BUILD_BORINGSSL)
+            target_compile_options(fipsmodule PRIVATE /w)
+        endif()
+    else()
+        target_compile_options(ssl PRIVATE -w)
+        target_compile_options(crypto PRIVATE -w)
+        if(LLAMA_BUILD_BORINGSSL)
+            target_compile_options(fipsmodule PRIVATE -w)
+        endif()
+    endif()
+endif()
+
 if (CPPHTTPLIB_OPENSSL_SUPPORT)
     target_compile_definitions(${TARGET} PUBLIC CPPHTTPLIB_OPENSSL_SUPPORT) # used in server.cpp
     if (APPLE AND CMAKE_SYSTEM_NAME STREQUAL "Darwin")
Repository: huggingface/transformers
Pull request: [quantization] make torchao tests slow

# What does this PR do?

Simply makes the tests slow

Changed files:
filename: tests/quantization/torchao_integration/test_torchao.py
patch: @@ -29,6 +29,7 @@
     require_torch_multi_accelerator,
     require_torchao,
     require_torchao_version_greater_or_equal,
+    slow,
     torch_device,
 )
 from transformers.utils import is_torch_available, is_torchao_available
@@ -139,6 +140,7 @@ def test_json_serializable(self):
 
 @require_torchao
 @require_torchao_version_greater_or_equal("0.8.0")
+@slow
 class TorchAoTest(unittest.TestCase):
     input_text = "What are we having for dinner?"
     max_new_tokens = 10
@@ -674,6 +676,7 @@ def test_autoquant(self):
 
 
 @require_torchao_version_greater_or_equal("0.11.0")
+@slow
 class TorchAoSerializationTest(unittest.TestCase):
     input_text = "What are we having for dinner?"
     max_new_tokens = 10
Repository: vuejs/vue
Pull request: [weex] Fix the text node could not be removed properly

In Weex, the `TEXT_NODE` must be the child of `<text>`.

Added special treatment of `TEXT_NODE` in `removeChild`.

Changed files:
filename: src/platforms/weex/runtime/node-ops.js
patch: @@ -34,6 +34,10 @@ export function insertBefore (node, target, before) {
 }
 
 export function removeChild (node, child) {
+  if (node.nodeType === 3) {
+    node.parentNode.setAttr('value', '')
+    return
+  }
   node.removeChild(child)
 }