From 88de03a21335fd417588362523c941150983b0ec Mon Sep 17 00:00:00 2001
From: Isaac Francisco <78627776+isahers1@users.noreply.github.com>
Date: Wed, 18 Dec 2024 17:59:18 -0800
Subject: [PATCH] Update backtesting.mdx

---
 docs/evaluation/tutorials/backtesting.mdx | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/docs/evaluation/tutorials/backtesting.mdx b/docs/evaluation/tutorials/backtesting.mdx
index f4fc090a..874d7025 100644
--- a/docs/evaluation/tutorials/backtesting.mdx
+++ b/docs/evaluation/tutorials/backtesting.mdx
@@ -226,7 +226,6 @@ gpt_4o = ChatOpenAI(model="gpt-4o")
 new_agent = create_react_agent(gpt_4o, tools=tools, state_modifier=modifier)
 
 def new_target(inputs):
-    rate_limiter.acquire()
     raw = new_agent.invoke(inputs)
     return {"messages": convert_to_openai_messages(raw['messages'])}
 
@@ -255,4 +254,4 @@ which GPT-4o is better than GPT-3.5:
 This was a simple example to show how you could backtest your production system against a new system.
 There are many different ways to do this backtesting, including using targeted filters
 to select the production runs you want to improve on, or using human preference
-data instead of evlautors defined in code.
\ No newline at end of file
+data instead of evlautors defined in code.