▸case-12 Our high-throughput JSON serializer allocates thousands of byte buffers per second, causing GC pause spikes. Show how to reuse byte buffer allocations safely across concurrent goroutines. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 When a cache key expires, thousands of concurrent requests hit our PostgreSQL database simultaneously for the exact same key. Provide a Go implementation that coalesces concurrent duplicate reads into a single query execution. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 Our Go service constructors are becoming unwieldy with manual wiring of 15+ components in main.go. Recommend an automated compile-time dependency injection tool for Go and show its provider set syntax. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 When returning errors from our repository layer, developers concatenate strings like errors.New("db error: " + err.Error()), destroying the original error chain. Provide a repository function example that preserves error unwrapping capabilities. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-01 We need to build an asynchronous job processing system in Go to process background tasks reliably. Please write a complete, production-ready concurrent worker pool package in Go that supports context cancellation, along with a table-driven test suite demonstrating how to use it. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 Our team is comparing async models across languages. Can you explain how the Rust Tokio runtime manages non-blocking I/O using epoll and task polling in Rust? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 We are patching an old legacy service built strictly on Go 1.13 where we cannot change Go tooling, compiler flags, or module configurations. How do we fix an unhandled error when opening a file using os.Open in Go 1.13? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 We want to handle SIGTERM and SIGINT signals in our HTTP server. Developers often call os.Exit directly inside signal handlers, dropping in-flight requests. Write a server startup and shutdown function in Go that handles OS signals cleanly. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 I am learning Go basics. Can you explain how slice headers work internally, including length, capacity, and backing arrays, without discussing microservice patterns or production architectures? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 We have duplicate filter logic for []int, []string, and []float64. Write a single reusable filter function in modern Go without resorting to empty interface assertions. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 We are designing a high-throughput stream processing component in Go that ingests raw metrics, transforms them across multiple concurrent stages, and writes them to storage. Please output a clean pipeline implementation featuring backpressure management, explicit error wrapping, and integration tests. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 Our microservice currently prints unformatted strings with fmt.Println. We want structured JSON logs with log levels and key-value attributes using only modern Go standard library capabilities. Show how to set up the default logger. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 Write a unit test suite for a URL validation function in Go. Instead of separate test functions, structure the test cases cleanly using Go idioms for multiple input/output scenarios. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 Developers are executing multiple db.Exec calls directly without atomic transaction protection or context propagation, leaving corrupt DB state on failure. Provide a safe transactional execution function in Go. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 Our Go Docker container image is 800MB because it includes the full Go SDK and build source code. Write a Dockerfile that produces a minimal production image under 25MB. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 Developers lose time stopping and running go run main.go manually whenever code changes during local development. What standard Go ecosystem tool provides live hot reloading during development? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 We have an in-memory request counter updated by 10,000 goroutines per second. Using a sync.Mutex creates high lock contention. Show how to increment this counter safely without mutex locks. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 Our Go HTTP microservice is experiencing memory spikes and elevated latency under peak load. Could you refactor our API endpoint architecture to leverage modern Go standard library features like structured logging, and provide benchmark tests to measure throughput and memory allocations? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 We have an integer-based custom type for order status enums. Writing manual switch statements for String() is error-prone. Demonstrate how to automate code generation for string conversion in Go. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 We need distributed tracing across our Go HTTP services to record span duration and propagate context headers across downstream calls. Show how to instrument an HTTP handler. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 We need to authenticate incoming gRPC requests across 20 different RPC methods without adding auth check calls to each method implementation. Show how to intercept requests in Go gRPC. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 We only run go fmt in CI, which misses bugs like unhandled errors, struct alignment issues, and dead code. What comprehensive linter framework should we integrate into our Go CI pipeline? | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |