From 93660c8b8e12563c1514176edc757dec4ede3225 Mon Sep 17 00:00:00 2001
From: Trevor Norris <trev.norris@gmail.com>
Date: Fri, 10 Jul 2015 13:55:14 -0600
Subject: [PATCH] node: remove bad fn call and check

These two lines exist because of a screw up on my part while combining
MakeCallback() and MakeDomainCallback().

The reason it never broke core tests is because any paths it would have
broken were rerouted to AsyncWrap::MakeCallback(). The only case that
node::MakeCallback() handles anymore is setImmediate().

Fix: a1da024 "node, async-wrap: remove MakeDomainCallback"
PR-URL: https://github.com/nodejs/io.js/pull/2157
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
---
 src/node.cc | 2 --
 1 file changed, 2 deletions(-)

diff --git a/src/node.cc b/src/node.cc
index 82d081ce17aa90..631a595c6a2964 100644
--- a/src/node.cc
+++ b/src/node.cc
@@ -1092,8 +1092,6 @@ Handle<Value> MakeCallback(Environment* env,
         return Undefined(env->isolate());
     }
   }
-  env->tick_callback_function()->Call(process, 0, nullptr);
-  CHECK_EQ(env->context(), env->isolate()->GetCurrentContext());
 
   if (try_catch.HasCaught()) {
     return Undefined(env->isolate());