@kensio/yulin 1.21.2 → 1.21.4

package/dist/service/lambda/event-source/stream/kinesis/sim-lambda-kinesis-event-source-rules.d.ts

@@ -1,4 +1,5 @@
 import { SimLambdaEventSourceBatchRules } from "../../sim-lambda-event-source-batch-rules.js";
+import { SimLambdaStreamRetryLimitRules } from "../../sim-lambda-event-source-retry-limits.js";
 import { SimLambdaStreamStartingPosition } from "../../sim-lambda-event-source-starting-position.js";
 /**
  * What a function's execution role has to be allowed to do on a stream for
@@ -25,3 +26,8 @@ export declare const kinesisStreamBatchRules: SimLambdaEventSourceBatchRules;
  * its records carry the instant they arrived.
  */
 export declare const kinesisStreamStartingPositionRules: SimLambdaStreamStartingPosition;
+/**
+ * A Kinesis stream mapping counts a failed batch's attempts itself, so it takes
+ * both of Lambda's failed-batch limits.
+ */
+export declare const kinesisStreamRetryLimitRules: SimLambdaStreamRetryLimitRules;

package/dist/service/lambda/event-source/stream/kinesis/sim-lambda-kinesis-event-source-rules.js

@@ -1,4 +1,5 @@
 import { SimLambdaEventSourceBatchRules } from "../../sim-lambda-event-source-batch-rules.js";
+import { SimLambdaStreamRetryLimitRules } from "../../sim-lambda-event-source-retry-limits.js";
 import { SimLambdaStreamStartingPosition } from "../../sim-lambda-event-source-starting-position.js";
 /**
  * What a function's execution role has to be allowed to do on a stream for
@@ -37,3 +38,8 @@ export const kinesisStreamStartingPositionRules = new SimLambdaStreamStartingPos
     positions: ["TRIM_HORIZON", "LATEST", "AT_TIMESTAMP"],
     sourceDescription: "a Kinesis stream",
 });
+/**
+ * A Kinesis stream mapping counts a failed batch's attempts itself, so it takes
+ * both of Lambda's failed-batch limits.
+ */
+export const kinesisStreamRetryLimitRules = new SimLambdaStreamRetryLimitRules();

package/dist/service/lambda/event-source/stream/sim-lambda-dynamodb-stream-event-source-arn.d.ts

@@ -1,5 +1,6 @@
 import type { SimLambdaEventSourceBatchRules } from "../sim-lambda-event-source-batch-rules.js";
-import { SimLambdaEventSourcePollingPermission } from "../sim-lambda-event-source-polling-permission.js";
+import type { SimLambdaEventSourcePollingPermission } from "../sim-lambda-event-source-polling-permission.js";
+import type { SimLambdaEventSourceRetryLimitRules } from "../sim-lambda-event-source-retry-limits.js";
 import type { SimLambdaEventSourceStartingPositionRules } from "../sim-lambda-event-source-starting-position.js";
 /**
  * The DynamoDB stream ARN an event source mapping is created for.
@@ -44,6 +45,10 @@ export declare class SimLambdaDynamoDbStreamEventSourceArn {
      * The starting positions a mapping on this stream may be created with.
      */
     get startingPositionRules(): SimLambdaEventSourceStartingPositionRules;
+    /**
+     * The failed-batch limits a mapping on this stream may be created with.
+     */
+    get retryLimitRules(): SimLambdaEventSourceRetryLimitRules;
     /**
      * Whether this stream is in an Account and Region.
      */

package/dist/service/lambda/event-source/stream/sim-lambda-dynamodb-stream-event-source-arn.js

@@ -1,6 +1,5 @@
 import { SimLambdaInvalidParameterValueException } from "../../error/sim-lambda.error.js";
-import { SimLambdaEventSourcePollingPermission } from "../sim-lambda-event-source-polling-permission.js";
-import { dynamoDbStreamBatchRules, dynamoDbStreamPollingOperations, dynamoDbStreamStartingPositionRules, } from "./sim-lambda-dynamodb-stream-event-source-rules.js";
+import { dynamoDbStreamBatchRules, dynamoDbStreamPollingPermissions, dynamoDbStreamRetryLimitRules, dynamoDbStreamStartingPositionRules, } from "./sim-lambda-dynamodb-stream-event-source-rules.js";
 /**
  * A stream ARN is a table ARN with a label after it, and the label is an ISO
  * timestamp carrying two colons of its own. Splitting the ARN on colons
@@ -37,10 +36,7 @@ export class SimLambdaDynamoDbStreamEventSourceArn {
         this.accountId = parts["account"] ?? "";
         this.tableName = parts["table"] ?? "";
         this.label = parts["label"] ?? "";
-        this.pollingPermissions = [
-            ...dynamoDbStreamPollingOperations.map((operation) => new SimLambdaEventSourcePollingPermission(`dynamodb:${operation}`, value)),
-            new SimLambdaEventSourcePollingPermission("dynamodb:ListStreams", "*"),
-        ];
+        this.pollingPermissions = dynamoDbStreamPollingPermissions(value);
     }
     /**
      * Read a stream ARN, answering with nothing when the ARN names something
@@ -78,6 +74,12 @@ export class SimLambdaDynamoDbStreamEventSourceArn {
     get startingPositionRules() {
         return dynamoDbStreamStartingPositionRules;
     }
+    /**
+     * The failed-batch limits a mapping on this stream may be created with.
+     */
+    get retryLimitRules() {
+        return dynamoDbStreamRetryLimitRules;
+    }
     /**
      * Whether this stream is in an Account and Region.
      */

package/dist/service/lambda/event-source/stream/sim-lambda-dynamodb-stream-event-source-rules.d.ts

@@ -1,15 +1,12 @@
 import { SimLambdaEventSourceBatchRules } from "../sim-lambda-event-source-batch-rules.js";
+import { SimLambdaEventSourcePollingPermission } from "../sim-lambda-event-source-polling-permission.js";
+import { SimLambdaStreamRetryLimitRules } from "../sim-lambda-event-source-retry-limits.js";
 import { SimLambdaStreamStartingPosition } from "../sim-lambda-event-source-starting-position.js";
 /**
- * What a function's execution role has to be allowed to do on a stream for
- * Lambda to poll it.
- *
- * These are the three operations a poller performs on the stream itself.
- * `ListStreams` goes with them, on every stream rather than on one: nothing
- * here ever calls it, but both the AWS managed policy and CDK's own grant
- * include it, so a role that would work on AWS is a role that works here.
+ * What an execution role has to be allowed before a mapping on one stream can
+ * be created, as the permissions simulated IAM is asked for.
  */
-export declare const dynamoDbStreamPollingOperations: readonly ["DescribeStream", "GetRecords", "GetShardIterator"];
+export declare function dynamoDbStreamPollingPermissions(streamArn: string): readonly SimLambdaEventSourcePollingPermission[];
 /**
  * The batch sizes a DynamoDB stream event source delivers with.
  *
@@ -25,3 +22,8 @@ export declare const dynamoDbStreamBatchRules: SimLambdaEventSourceBatchRules;
  * Kinesis stream, and real Lambda refuses it here.
  */
 export declare const dynamoDbStreamStartingPositionRules: SimLambdaStreamStartingPosition;
+/**
+ * A DynamoDB stream mapping counts a failed batch's attempts itself, so it
+ * takes both of Lambda's failed-batch limits.
+ */
+export declare const dynamoDbStreamRetryLimitRules: SimLambdaStreamRetryLimitRules;

package/dist/service/lambda/event-source/stream/sim-lambda-dynamodb-stream-event-source-rules.js

@@ -1,4 +1,6 @@
 import { SimLambdaEventSourceBatchRules } from "../sim-lambda-event-source-batch-rules.js";
+import { SimLambdaEventSourcePollingPermission } from "../sim-lambda-event-source-polling-permission.js";
+import { SimLambdaStreamRetryLimitRules } from "../sim-lambda-event-source-retry-limits.js";
 import { SimLambdaStreamStartingPosition } from "../sim-lambda-event-source-starting-position.js";
 /**
  * What a function's execution role has to be allowed to do on a stream for
@@ -9,11 +11,21 @@ import { SimLambdaStreamStartingPosition } from "../sim-lambda-event-source-star
  * here ever calls it, but both the AWS managed policy and CDK's own grant
  * include it, so a role that would work on AWS is a role that works here.
  */
-export const dynamoDbStreamPollingOperations = [
+const dynamoDbStreamPollingOperations = [
     "DescribeStream",
     "GetRecords",
     "GetShardIterator",
 ];
+/**
+ * What an execution role has to be allowed before a mapping on one stream can
+ * be created, as the permissions simulated IAM is asked for.
+ */
+export function dynamoDbStreamPollingPermissions(streamArn) {
+    return [
+        ...dynamoDbStreamPollingOperations.map((operation) => new SimLambdaEventSourcePollingPermission(`dynamodb:${operation}`, streamArn)),
+        new SimLambdaEventSourcePollingPermission("dynamodb:ListStreams", "*"),
+    ];
+}
 /**
  * The batch sizes a DynamoDB stream event source delivers with.
  *
@@ -38,3 +50,8 @@ export const dynamoDbStreamStartingPositionRules = new SimLambdaStreamStartingPo
     sourceDescription: "a DynamoDB stream",
     positionElsewhere: "AT_TIMESTAMP is for a Kinesis stream",
 });
+/**
+ * A DynamoDB stream mapping counts a failed batch's attempts itself, so it
+ * takes both of Lambda's failed-batch limits.
+ */
+export const dynamoDbStreamRetryLimitRules = new SimLambdaStreamRetryLimitRules();

package/dist/service/lambda/function/code/sim-lambda-executable-code.d.ts

@@ -1,4 +1,5 @@
 import type { SimLambdaEnvironment } from "../environment/sim-lambda-environment.js";
+import type { SimLambdaOutput } from "../logging/sim-lambda-output.js";
 import type { SimLambdaOutputSink } from "../logging/sim-lambda-output-sink.js";
 import type { SimLambdaHandler } from "../sim-lambda-handler.type.js";
 /**
@@ -32,8 +33,12 @@ export interface SimLambdaExecutableCode {
     /**
      * Record what this code writes to its standard streams, so an invocation's
      * output reaches the function's log group.
+     *
+     * The output settings come with the sink because they decide what happens to
+     * a line once it has been recorded, and only code with somewhere to record
+     * is ever given either.
      */
-    recordOutputTo(sink: SimLambdaOutputSink): void;
+    recordOutputTo(sink: SimLambdaOutputSink, output: SimLambdaOutput): void;
     /**
      * This code under changed function settings, cold rather than warm.
      *
@@ -63,7 +68,8 @@ export declare class SimLambdaHandlerReferenceCode implements SimLambdaExecutabl
      * function closing over the test's own module scope, and it prints through
      * the process console and the process standard streams. Its invocation is
      * run with those bridged to the function's sink instead, the way the clock
-     * and process.env are bridged for the same code.
+     * and process.env are bridged for the same code. The output settings reach
+     * that bridge by the same route.
      */
     recordOutputTo(): void;
     /**

package/dist/service/lambda/function/code/sim-lambda-executable-code.js

@@ -18,7 +18,8 @@ export class SimLambdaHandlerReferenceCode {
      * function closing over the test's own module scope, and it prints through
      * the process console and the process standard streams. Its invocation is
      * run with those bridged to the function's sink instead, the way the clock
-     * and process.env are bridged for the same code.
+     * and process.env are bridged for the same code. The output settings reach
+     * that bridge by the same route.
      */
     recordOutputTo() {
         // Recorded by the invocation, from the process globals.

package/dist/service/lambda/function/code/sim-lambda-vm-zip-code.d.ts

@@ -3,6 +3,7 @@ import type { SimLambdaHandler } from "../sim-lambda-handler.type.js";
 import { type SimLambdaVmSdkModuleProvider } from "./vm/sdk/sim-lambda-vm-sdk-module-provider.js";
 import type { SimLambdaCodeConfiguration, SimLambdaExecutableCode } from "./sim-lambda-executable-code.js";
 import { type SimLambdaVmContextProperties } from "./vm/sim-lambda-vm-context.js";
+import type { SimLambdaOutput } from "../logging/sim-lambda-output.js";
 import { type SimLambdaOutputSink } from "../logging/sim-lambda-output-sink.js";
 /**
  * The archive and handler this code runs, on top of everything its sandbox is
@@ -37,7 +38,7 @@ export declare class SimLambdaVmZipCode implements SimLambdaExecutableCode {
      * asks for the handler, so the streams function code is handed already carry
      * the sink by the time any of it runs.
      */
-    recordOutputTo(sink: SimLambdaOutputSink): void;
+    recordOutputTo(sink: SimLambdaOutputSink, output: SimLambdaOutput): void;
     /**
      * This archive under changed function settings, ready to cold start again.
      *
@@ -53,15 +54,5 @@ export declare class SimLambdaVmZipCode implements SimLambdaExecutableCode {
      */
     handlerFunction(): SimLambdaHandler;
     private coldStart;
-    /**
-     * Look up the handler export, tolerating a module that exported a nullish
-     * value so the lookup still reports Runtime.HandlerNotFound.
-     *
-     * Only own exports count. Walking the prototype chain would let a handler
-     * name like `index.constructor` resolve to an `Object.prototype` member and
-     * be invoked as the handler, where real Lambda reports HandlerNotFound.
-     */
-    private exportedHandler;
-    private importHandlerModule;
 }
 export {};

package/dist/service/lambda/function/code/sim-lambda-vm-zip-code.js

@@ -4,6 +4,7 @@ import { parseLambdaHandlerName } from "./sim-lambda-handler-name.js";
 import { makeSimLambdaVmContext, } from "./vm/sim-lambda-vm-context.js";
 import { simLambdaNoOutputSink, } from "../logging/sim-lambda-output-sink.js";
 import { SimLambdaVmModules } from "./vm/sim-lambda-vm-modules.js";
+import { importSimLambdaHandlerModule, simLambdaExportedHandler, } from "./vm/sim-lambda-vm-handler-lookup.js";
 /**
  * Executable sim Lambda code compiled from a zip archive in a vm context.
  *
@@ -20,7 +21,10 @@ export class SimLambdaVmZipCode {
      */
     runsInHostScope = false;
     #handler;
-    #sink = simLambdaNoOutputSink;
+    /** Where this execution environment's output goes, and what happens to it. */
+    #recording = {
+        sink: simLambdaNoOutputSink,
+    };
     constructor(properties) {
         this.properties = properties;
     }
@@ -31,8 +35,8 @@ export class SimLambdaVmZipCode {
      * asks for the handler, so the streams function code is handed already carry
      * the sink by the time any of it runs.
      */
-    recordOutputTo(sink) {
-        this.#sink = sink;
+    recordOutputTo(sink, output) {
+        this.#recording = { sink, output };
     }
     /**
      * This archive under changed function settings, ready to cold start again.
@@ -62,47 +66,17 @@ export class SimLambdaVmZipCode {
         const parsedName = parseLambdaHandlerName(handlerName);
         const modules = new SimLambdaVmModules({
             archive,
-            context: makeSimLambdaVmContext({ ...this.properties, sink: this.#sink }),
+            context: makeSimLambdaVmContext({
+                ...this.properties,
+                ...this.#recording,
+            }),
             sdkModuleProvider: sdkModuleProvider ?? new SimLambdaNoVmSdkModuleProvider(),
         });
-        const moduleExports = this.importHandlerModule(modules, parsedName.modulePath);
-        const handler = this.exportedHandler(moduleExports, parsedName.exportName);
+        const moduleExports = importSimLambdaHandlerModule(modules, parsedName.modulePath);
+        const handler = simLambdaExportedHandler(moduleExports, parsedName.exportName);
         if (typeof handler !== "function") {
             throw new SimLambdaRuntimeError("Runtime.HandlerNotFound", `${handlerName} is undefined or not exported by ${parsedName.modulePath}`);
         }
         return handler;
     }
-    /**
-     * Look up the handler export, tolerating a module that exported a nullish
-     * value so the lookup still reports Runtime.HandlerNotFound.
-     *
-     * Only own exports count. Walking the prototype chain would let a handler
-     * name like `index.constructor` resolve to an `Object.prototype` member and
-     * be invoked as the handler, where real Lambda reports HandlerNotFound.
-     */
-    exportedHandler(moduleExports, exportName) {
-        if (moduleExports === null || moduleExports === undefined) {
-            return undefined;
-        }
-        const exportedValues = moduleExports;
-        if (!Object.hasOwn(exportedValues, exportName)) {
-            return undefined;
-        }
-        return Reflect.get(exportedValues, exportName);
-    }
-    importHandlerModule(modules, modulePath) {
-        try {
-            return modules.requireModule(`./${modulePath}`);
-        }
-        catch (error) {
-            if (error instanceof SimLambdaRuntimeError) {
-                throw error;
-            }
-            let message = String(error);
-            if (error instanceof Error) {
-                message = error.message;
-            }
-            throw new SimLambdaRuntimeError("Runtime.ImportModuleError", message);
-        }
-    }
 }

package/dist/service/lambda/function/code/vm/sim-lambda-vm-context.d.ts

@@ -1,6 +1,7 @@
 import vm from "node:vm";
 import { type SimClock } from "../../../../../util/clock/sim-clock.js";
 import type { SimLambdaEnvironment } from "../../environment/sim-lambda-environment.js";
+import type { SimLambdaOutput } from "../../logging/sim-lambda-output.js";
 import { type SimLambdaOutputSink } from "../../logging/sim-lambda-output-sink.js";
 import type { SimLambdaOutboundHttp } from "../../outbound/sim-lambda-outbound-http.js";
 /**
@@ -12,6 +13,12 @@ export interface SimLambdaVmContextProperties {
     readonly clock?: SimClock | undefined;
     /** Where the sandbox's output is recorded, nowhere by default. */
     readonly sink?: SimLambdaOutputSink | undefined;
+    /**
+     * Whether what the sandbox prints also reaches the host standard streams.
+     * A sandbox given none forwards everything, which is what a function with
+     * nowhere to record its output needs.
+     */
+    readonly output?: SimLambdaOutput | undefined;
     /**
      * Where the sandbox's `fetch` requests to hostnames the simulation serves
      * are answered. Without one every request reaches the network, as the host

package/dist/service/lambda/function/code/vm/sim-lambda-vm-context.js

@@ -4,6 +4,8 @@ import { makeSimClockDate } from "../../../../../util/clock/sim-clock-date.js";
 import { SimRealClock, } from "../../../../../util/clock/sim-clock.js";
 import { simLambdaNoOutputSink, } from "../../logging/sim-lambda-output-sink.js";
 import { makeSimLambdaOutboundFetch } from "../../outbound/sim-lambda-outbound-fetch.js";
+import { simLambdaClearInterval, simLambdaClearTimeout, } from "../../invoke/timer/sim-lambda-clear-timer.js";
+import { simLambdaSetInterval, simLambdaSetTimeout, } from "../../invoke/timer/sim-lambda-process-timers.js";
 import { SimLambdaVmOutputStream } from "./sim-lambda-vm-output-stream.js";
 /**
  * Create the sandbox vm context that sim Lambda function code runs in.
@@ -22,12 +24,12 @@ import { SimLambdaVmOutputStream } from "./sim-lambda-vm-output-stream.js";
  * from the simulation for the hostnames the simulation serves.
  */
 export function makeSimLambdaVmContext(properties) {
-    const { environment, clock = new SimRealClock(), sink = simLambdaNoOutputSink, outboundHttp, } = properties;
+    const { environment, clock = new SimRealClock(), sink = simLambdaNoOutputSink, output, outboundHttp, } = properties;
     // Writable standard streams, as the real runtime provides. Code that builds
     // its own console over them, as AWS Lambda Powertools' logger does, throws
     // at module load without them.
-    const stdout = new SimLambdaVmOutputStream(() => process.stdout);
-    const stderr = new SimLambdaVmOutputStream(() => process.stderr);
+    const stdout = new SimLambdaVmOutputStream(() => process.stdout, output);
+    const stderr = new SimLambdaVmOutputStream(() => process.stderr, output);
     // What function code writes reaches the function's log group through here.
     stdout.recordTo(sink);
     stderr.recordTo(sink);
@@ -45,10 +47,14 @@ export function makeSimLambdaVmContext(properties) {
         // Function code asking JavaScript for the time gets the simulation's
         // time, so a frozen or advanced clock reaches the code under test.
         Date: makeSimClockDate(clock),
-        setTimeout,
-        clearTimeout,
-        setInterval,
-        clearInterval,
+        // Timers wait on the simulation's clock too, so a sandboxed handler that
+        // sleeps is released by a test advancing time rather than by the host.
+        // They belong to whichever invocation is running in the sandbox, which is
+        // why they are resolved per call rather than built into it.
+        setTimeout: simLambdaSetTimeout,
+        clearTimeout: simLambdaClearTimeout,
+        setInterval: simLambdaSetInterval,
+        clearInterval: simLambdaClearInterval,
         setImmediate,
         queueMicrotask,
         TextEncoder,

package/dist/service/lambda/function/code/vm/sim-lambda-vm-handler-lookup.d.ts

@@ -0,0 +1,23 @@
+import type { SimLambdaVmModules } from "./sim-lambda-vm-modules.js";
+/**
+ * Importing a function's handler module and finding the export it names.
+ *
+ * Both steps report the AWS-like `Runtime.*` error a real cold start reports,
+ * which is why they sit together.
+ */
+/**
+ * Import the module a handler name points at.
+ *
+ * Anything the import threw that is not already a runtime error becomes a
+ * `Runtime.ImportModuleError`, as it does on real Lambda.
+ */
+export declare function importSimLambdaHandlerModule(modules: SimLambdaVmModules, modulePath: string): unknown;
+/**
+ * Look up the handler export, tolerating a module that exported a nullish
+ * value so the lookup still reports Runtime.HandlerNotFound.
+ *
+ * Only own exports count. Walking the prototype chain would let a handler
+ * name like `index.constructor` resolve to an `Object.prototype` member and
+ * be invoked as the handler, where real Lambda reports HandlerNotFound.
+ */
+export declare function simLambdaExportedHandler(moduleExports: unknown, exportName: string): unknown;

package/dist/service/lambda/function/code/vm/sim-lambda-vm-handler-lookup.js

@@ -0,0 +1,42 @@
+import { SimLambdaRuntimeError } from "../../../error/sim-lambda-runtime.error.js";
+/**
+ * Importing a function's handler module and finding the export it names.
+ *
+ * Both steps report the AWS-like `Runtime.*` error a real cold start reports,
+ * which is why they sit together.
+ */
+/**
+ * Import the module a handler name points at.
+ *
+ * Anything the import threw that is not already a runtime error becomes a
+ * `Runtime.ImportModuleError`, as it does on real Lambda.
+ */
+export function importSimLambdaHandlerModule(modules, modulePath) {
+    try {
+        return modules.requireModule(`./${modulePath}`);
+    }
+    catch (error) {
+        if (error instanceof SimLambdaRuntimeError) {
+            throw error;
+        }
+        throw new SimLambdaRuntimeError("Runtime.ImportModuleError", error instanceof Error ? error.message : String(error));
+    }
+}
+/**
+ * Look up the handler export, tolerating a module that exported a nullish
+ * value so the lookup still reports Runtime.HandlerNotFound.
+ *
+ * Only own exports count. Walking the prototype chain would let a handler
+ * name like `index.constructor` resolve to an `Object.prototype` member and
+ * be invoked as the handler, where real Lambda reports HandlerNotFound.
+ */
+export function simLambdaExportedHandler(moduleExports, exportName) {
+    if (moduleExports === null || moduleExports === undefined) {
+        return undefined;
+    }
+    const exportedValues = moduleExports;
+    if (!Object.hasOwn(exportedValues, exportName)) {
+        return undefined;
+    }
+    return Reflect.get(exportedValues, exportName);
+}

package/dist/service/lambda/function/code/vm/sim-lambda-vm-output-stream.d.ts

@@ -1,4 +1,5 @@
 import { Writable } from "node:stream";
+import type { SimLambdaOutput } from "../../logging/sim-lambda-output.js";
 import { type SimLambdaOutputSink } from "../../logging/sim-lambda-output-sink.js";
 /**
  * One of the standard output streams the sim Lambda vm sandbox gives function
@@ -20,19 +21,26 @@ import { type SimLambdaOutputSink } from "../../logging/sim-lambda-output-sink.j
  * standard output to standard output and standard error to standard error, and
  * recorded to the sink the code was given, which is what puts a handler's
  * output in its log group. Forwarding to the host is a tee rather than a
- * redirect: real Lambda sends output to CloudWatch Logs and nowhere else, but
- * a test tool that swallowed it would make a failing test harder to debug than
- * it is with none of this.
+ * redirect. Real Lambda sends output to CloudWatch Logs and nowhere else, and a
+ * test tool that swallowed it would make a failing test harder to debug than it
+ * is with none of this.
  * The sandbox's own console is built over these streams too, so a handler's
  * output arrives there whether it printed through the console or wrote to the
  * stream itself, instead of one of the two disappearing. The host stream is
  * read per write, so a test that starts capturing host output after the
  * function has cold-started still sees what the handler writes.
+ *
+ * A simulated Lambda told to capture only (see `SimLambdaOutput`) drops the
+ * forwarding and carries on recording. Those settings are read per write as
+ * well, so a sandbox that has already cold started follows a change. A stream
+ * built without them forwards everything, which is what a function with
+ * nowhere to record its output needs.
  */
 export declare class SimLambdaVmOutputStream extends Writable {
     #private;
     private readonly hostStream;
-    constructor(hostStream: () => NodeJS.WritableStream);
+    private readonly output?;
+    constructor(hostStream: () => NodeJS.WritableStream, output?: SimLambdaOutput | undefined);
     /**
      * Record everything written here to a sink from now on.
      */

package/dist/service/lambda/function/code/vm/sim-lambda-vm-output-stream.js

@@ -21,17 +21,24 @@ import { simLambdaNoOutputSink, } from "../../logging/sim-lambda-output-sink.js"
  * standard output to standard output and standard error to standard error, and
  * recorded to the sink the code was given, which is what puts a handler's
  * output in its log group. Forwarding to the host is a tee rather than a
- * redirect: real Lambda sends output to CloudWatch Logs and nowhere else, but
- * a test tool that swallowed it would make a failing test harder to debug than
- * it is with none of this.
+ * redirect. Real Lambda sends output to CloudWatch Logs and nowhere else, and a
+ * test tool that swallowed it would make a failing test harder to debug than it
+ * is with none of this.
  * The sandbox's own console is built over these streams too, so a handler's
  * output arrives there whether it printed through the console or wrote to the
  * stream itself, instead of one of the two disappearing. The host stream is
  * read per write, so a test that starts capturing host output after the
  * function has cold-started still sees what the handler writes.
+ *
+ * A simulated Lambda told to capture only (see `SimLambdaOutput`) drops the
+ * forwarding and carries on recording. Those settings are read per write as
+ * well, so a sandbox that has already cold started follows a change. A stream
+ * built without them forwards everything, which is what a function with
+ * nowhere to record its output needs.
  */
 export class SimLambdaVmOutputStream extends Writable {
     hostStream;
+    output;
     #sink = simLambdaNoOutputSink;
     /**
      * Decodes what is recorded, rather than each chunk being decoded on its own.
@@ -44,9 +51,10 @@ export class SimLambdaVmOutputStream extends Writable {
      * bytes left over at the end of an invocation belong to the next one.
      */
     #decoder = new StringDecoder("utf8");
-    constructor(hostStream) {
+    constructor(hostStream, output) {
         super();
         this.hostStream = hostStream;
+        this.output = output;
     }
     /**
      * Record everything written here to a sink from now on.
@@ -65,7 +73,9 @@ export class SimLambdaVmOutputStream extends Writable {
      */
     _write(chunk, _encoding, done) {
         this.#sink.write(this.#decoder.write(chunk));
-        this.hostStream().write(chunk);
+        if (this.output?.reachesHost() ?? true) {
+            this.hostStream().write(chunk);
+        }
         done();
     }
 }

package/dist/service/lambda/function/invoke/sim-lambda-host-scope.d.ts

@@ -1,4 +1,5 @@
 import type { SimClock } from "../../../../util/clock/sim-clock.js";
+import type { SimLambdaOutput } from "../logging/sim-lambda-output.js";
 import type { SimLambdaOutputSink } from "../logging/sim-lambda-output-sink.js";
 import type { SimLambdaOutboundHttp } from "../outbound/sim-lambda-outbound-http.js";
 /**
@@ -19,6 +20,12 @@ interface SimLambdaHostScope {
      * and its output reaches the host console alone.
      */
     readonly output: SimLambdaOutputSink | undefined;
+    /**
+     * Whether what the invocation prints also reaches the host console once it
+     * has been recorded. Read only where there is a sink, because a function
+     * with nowhere to record has the host console alone.
+     */
+    readonly outputSettings: SimLambdaOutput;
 }
 /**
  * Run an invocation of code in the host scope with the process globals it

package/dist/service/lambda/function/invoke/sim-lambda-host-scope.js

@@ -1,6 +1,7 @@
 import { simLambdaProcessClock } from "./sim-lambda-process-clock.js";
 import { simLambdaProcessOutbound } from "./sim-lambda-process-outbound.js";
 import { simLambdaProcessOutput } from "./sim-lambda-process-output.js";
+import { simLambdaProcessTimers } from "./timer/sim-lambda-process-timers.js";
 /**
  * Run an invocation of code in the host scope with the process globals it
  * reads bridged to its simulation.
@@ -11,10 +12,13 @@ import { simLambdaProcessOutput } from "./sim-lambda-process-output.js";
  * here.
  */
 export async function runSimLambdaInHostScope(scope, run) {
-    const { clock, outboundHttp, output } = scope;
+    const { clock, outboundHttp, output, outputSettings } = scope;
+    // Host-scope code reaches for the global timer functions, so the invocation
+    // its handler runs in has to be findable from them.
+    simLambdaProcessTimers.install();
     const recording = output === undefined
         ? run
-        : async () => await simLambdaProcessOutput.run(output, run);
+        : async () => await simLambdaProcessOutput.run(output, outputSettings, run);
     const reachingTheSimulation = outboundHttp === undefined
         ? recording
         : async () => await simLambdaProcessOutbound.run(outboundHttp, recording);

package/dist/service/lambda/function/invoke/sim-lambda-invocation-deadline.d.ts

@@ -0,0 +1,26 @@
+import type { BackgroundScheduler } from "../../../../util/background/background.js";
+interface SimLambdaInvocationDeadlineProperties {
+    readonly background: BackgroundScheduler;
+    readonly timeoutSeconds: number;
+    readonly awsRequestId: string;
+}
+/**
+ * The time one invocation has to finish in, and the timers it gets while it
+ * runs.
+ *
+ * Both wait on the simulation's clock. Whichever arrives first decides: a
+ * handler that answers in time is answered with, and a deadline that arrives
+ * first ends the invocation in the timeout error real Lambda reports. Nothing
+ * waits for a handler that has been timed out, and what it goes on to do
+ * reaches nobody, which is the closest an in-process simulation gets to an
+ * execution environment being taken away.
+ */
+export declare class SimLambdaInvocationDeadline {
+    #private;
+    constructor(properties: SimLambdaInvocationDeadlineProperties);
+    /**
+     * Run the handler with timers of its own, up to this deadline.
+     */
+    around<T>(handler: () => Promise<T>): Promise<T>;
+}
+export {};