From 194fdb8217b1f50ca9fa72604d49e6af89fb37c3 Mon Sep 17 00:00:00 2001 From: Emil Lerch Date: Wed, 2 Aug 2023 13:55:14 -0700 Subject: [PATCH] calculate server requests based on lambda requests --- src/lambda.zig | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/src/lambda.zig b/src/lambda.zig index 254b207..a54dd24 100644 --- a/src/lambda.zig +++ b/src/lambda.zig @@ -344,7 +344,11 @@ fn lambda_request(allocator: std.mem.Allocator, request: []const u8) ![]u8 { // booleans to know when to shut down. This function is designed for a // single request/response pair only - server_remaining_requests = 2; // Tell our server to run for just two requests + lambda_remaining_requests = 1; // in case anyone messed with this, we will make sure we start + server_remaining_requests = lambda_remaining_requests.? * 2; // Lambda functions + // fetch from the server, + // then post back. Always + // 2, no more, no less server_response = request; // set our instructions to lambda, which in our // physical model above, is the server response defer server_response = "unset"; // set it back so we don't get confused later @@ -359,7 +363,6 @@ fn lambda_request(allocator: std.mem.Allocator, request: []const u8) ![]u8 { defer server_thread.join(); // we'll be shutting everything down before we exit // Now we need to start the lambda framework, following a siimilar pattern - lambda_remaining_requests = 1; // in case anyone messed with this, we will make sure we start const lambda_thread = try test_run(allocator, handler); // We want our function under test to report leaks lambda_thread.join(); return server_request_aka_lambda_response;