python
9 minDebugging Flaky Python Tests: Time, State, Concurrency, and Isolation
Find the hidden shared state, clock assumptions, race, or nondeterministic dependency behind tests that fail only sometimes.
Search the library
35 matching resultsArticles and interview answers
java
10 minJava Exception Debugging: Trace the Root Cause and Fix the Boundary
A practical method for investigating wrapped exceptions, null failures, resource exhaustion, and misleading catch blocks in JVM services.
Q&A
Q&AHow do you debug a shell script without leaking secrets?
Trace selectively, preserve quoting and exit status, and avoid dumping sensitive expanded arguments.
Read the concise answer
Check the intended interpreter and run a syntax check first. Enable xtrace only around the suspect section because it prints expanded values; redirect diagnostics securely and mask credentials. Reproduce with controlled input, inspect each command status, and use ShellCheck to catch common quoting and portability issues.
Q&A
Q&AHow do TCP and UDP differ when debugging a service?
TCP establishes an ordered byte stream; UDP sends datagrams without delivery acknowledgement from the transport.
Read the concise answer
TCP connection establishment and retransmission make a port-connectivity test meaningful, but application message boundaries still need framing. UDP has no handshake, so silence may mean a dropped packet, invalid request, or a service that does not answer probes. Test using a valid protocol request and inspect both ends when possible.
python
9 minPython Error Debugging: Tracebacks, Root Causes, and Safe Fixes
Turn Python exceptions into a reproducible diagnosis using traceback frames, minimal experiments, structured logging, and boundary validation.
java
9 minJava equals and hashCode: Fix Broken HashMap and HashSet Lookups
Diagnose collection bugs caused by inconsistent equality, mutable keys, inheritance, and accidental identity comparisons.
Q&A
Q&AHow do you debug a Java exception wrapped by a framework?
Follow the complete cause chain to the deepest relevant failure and retain contextual stack traces.
Read the concise answer
Read the top exception and every Caused by section. Framework and future wrappers often report where failure surfaced, not its origin. Preserve stack trace, request identifier, runtime version, and safe configuration context. When translating an exception, chain the original cause rather than logging only its message.
unix
9 minShell Script Debugging: Trace Failures, Preserve Exit Codes, and Fix Safely
A root-cause workflow for shell failures involving quoting, pipelines, unset variables, traps, temporary files, and partial work.