TryBugHunt

The Scrambled Stream Pipeline

Easyjavascript

Fan-Out Batch Pipeline with In-Place Array Mutation

0:00
Step 1: Test Traffic & Expose Flaw
/**
 * Batch Stream Context & Message Schemas
 */
class MessageBatch {
  constructor(batchId, messages) {
    this.batchId = batchId;
    this.messages = messages;
  }

  getMessageIds() {
    return this.messages.map((m) => m.id);
  }
}

module.exports = { MessageBatch };
Step 1: Test Traffic & Expose FlawClient-side WASM

Run a scenario below to trace stream fan-out. Prove that a priority subscriber mutates the shared batch and scrambles the order for FIFO subscribers.

Choose Traffic Scenario to TestClick to simulate
Architectural Guide & Interview Notes

Deep Dive: The Scrambled Stream Pipeline

An engineering analysis of why this AI-generated Pull Request passed isolated unit tests, how multi-tenant traffic exposes the architectural flaw, and how interviewers score your response.

The Root Cause Anti-Pattern

In JavaScript, Array.prototype.sort() sorts in-place, mutating the original array reference. In streaming and batch processing, sorting a shared batch for a priority subscriber silently corrupts arrival sequence ordering for downstream FIFO consumer queues.

The Interviewer's Scoring Rubric

Candidates are assessed on whether they jump to trial-and-error editing or follow a hypothesis-driven approach. A "Strong Hire" candidate restates the data flow between modules, explains why single-client unit tests passed, crafts an adversarial probe showing cross-tenant leakage, and implements a surgical 1-line patch without breaking existing contracts.

Candidate Strategy for the Code Comprehension Round

  1. 1Map Module ContractsTrace how the gateway invokes the underlying service. Note what data is passed by reference vs. by value.
  2. 2Break It With An Adversarial ProbeSimulate concurrent or sequential traffic across multiple identities to force shared state mutation.
  3. 3Deliver a Surgical PatchMake the minimal required diff to ensure proper per-client state isolation without refactoring unnecessary files.