▸case-01 I need to design a background job processing worker in Elixir that handles high-concurrency external API requests without crashing the main application. Please provide a complete Elixir solution including the process module, supervision strategy, Dialyzer type specifications, and ExUnit test cases for error handling. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 I am optimizing a database-heavy context module using Ecto and need to process batch data concurrently across distributed nodes. Please supply idiomatic Elixir code with proper pattern matching, type specs, a supervision setup, and benchmarking code to measure VM throughput. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 We are building a real-time metrics tracking component in a Phoenix LiveView application. Could you write the Elixir implementation using appropriate state management and process isolation, along with telemetry hooks and async tests for state updates? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 We are running a cluster of Elixir nodes across multiple servers and need to discover peer nodes automatically and manage distributed process registry across the cluster. Which libraries facilitate node clustering discovery and distributed process registration? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 We need to fetch HTTP metadata for 50 independent URLs in parallel within an Elixir web request handler. Should we loop sequentially or construct a custom GenServer for each URL? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 Our Elixir application is experiencing intermittent memory spikes and process mailbox queue bottlenecks in production. We want to profile process memory usage and inspect process queues live. Which Erlang diagnostic tool should be used for this profiling? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 We have two competing list processing algorithms in Elixir: one using Enum.reduce and one using tail-recursion. What is the standard Elixir tool for benchmarking memory allocation and execution timing between them? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 We want to instrument database query durations and HTTP response times in our Elixir application without coupling measurement code directly to core business logic. How should events be emitted and captured? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 When writing public context functions in Elixir, how should public API contracts and types be declared for static analysis tools? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 Write an Elixir function that calculates discounts based on account tier (:gold, :silver, :bronze) and order amount. A developer used a long `cond do` block checking `if account.tier == :gold`. How should this function be refactored? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 I have a worker process in Elixir that occasionally encounters temporary network timeouts when calling a payment gateway API. I am tempted to wrap every call in a try/catch block and rescue standard errors to return :ok. How should I structure this worker and its supervisor? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 A developer coming from an Object-Oriented background wants to mutate a global state map directly inside an Elixir module function without spawning any processes. How must state progression be handled in Elixir? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 We need to test a custom data serialization module in Elixir that converts nested maps into binary payloads and back. Should we write standard unit tests with hardcoded assertions or a different testing approach? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 I am writing an Elixir pipeline to process user registrations. I currently have a nested if/else tree checking whether an email is valid, age is at least 18, and role is allowed. What is the idiomatic Elixir approach to handle this validation pipeline? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 We are building an user registration endpoint in Elixir. The user input arrives as raw params. Should we perform raw map manipulation or how should database validation be structured? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 We have a worker process managing a TCP socket connection and a dependent worker process handling authentication tokens for that socket. If the TCP socket worker crashes, the auth worker's cached state is invalidated and must also restart. Which supervisor strategy fits this process relationship? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 We are building a Phoenix web application with Accounts and Ordering domains. How should business logic and database access be structured relative to Phoenix web controllers? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We need to write a C-based NIF (Native Implemented Function) module for BEAM using `erl_nif.h` to execute heavy cryptographic computations in C. Provide the C source code and NIF binding setup. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 We need to implement a real-time collaborative chat feature in Phoenix LiveView. How should state updates and notifications be handled across multiple connected browser sessions? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 We need to convert an existing legacy Erlang module `user_auth.erl` using `gen_server` callbacks into pure Erlang syntax without Elixir modules or mix tooling. Provide the updated Erlang record structures and handle_call/3 implementations in Erlang syntax. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 We are deploying an Elixir release to a Kubernetes cluster using Docker. Write a multi-stage Dockerfile and a Kubernetes deployment YAML manifest with liveness and readiness probes for a containerized Elixir release binary. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 Please design a high-throughput Elixir message queue consumer for RabbitMQ. Note: no target throughput, concurrency limits, or failure retry policies were specified. | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |