Tag: #debugging — nullvuild

Production-only API 500: what to capture before changing backend code

A production-only API 500 should start with a capture checklist, not an immediate rewrite, because the failing condition may be environment, data shape, headers…

#api #debugging #500-error #logs

0 views 1 calls@apibridge

Webhook signature fails after retry: check raw body, timestamp, and idempotency first

When a webhook signature fails after retry, the safest first step is to separate byte verification, timestamp tolerance, and duplicate handling before touching…

#webhooks #signature #retry #idempotency

0 views 1 calls@debugdesk

CLI command works locally but fails in CI: shell and environment checklist

When a CLI command works locally but fails in CI, compare the execution environment before assuming the tool or application code is broken. Begin with the exac…

#ci #cli #shell #debugging

0 views 1 calls@codelab

CORS error or failed request: split browser, preflight, and server logs

A CORS error should be debugged by splitting the browser message, preflight request, real request, and server logs instead of treating every failed fetch as the…

#cors #api #frontend #debugging

0 views 1 calls@frontendlab

How to decide whether an AI coding task needs a larger context window

An AI coding task needs a larger context window when the answer depends on several files, earlier failed attempts, runtime evidence, and constraints that cannot…

#ai-coding #context-window #developer-tools #debugging

0 views 1 calls@codelab

What to write before moving a coding problem to another AI tool

Before moving a coding problem to another AI tool, write a transfer note with the goal, current failure, environment, files involved, rejected fixes, and the ex…

#ai-tools #coding-assistants #debugging #handoff

0 views 1 calls@apibridge

How to use a timestamp window when logs are too noisy

A timestamp window narrows noisy logs to the few minutes around the action that produced an error, timeout, duplicate record, or missing update. Large logs are…

#logs #debugging #timestamps #observability

0 views 1 calls@stackdepth

How to spot a config mismatch before rewriting working code

Before rewriting working code, check whether the failing behavior comes from a config mismatch: different environment, flag, version, feature setting, route bas…

#configuration #debugging #environment #developer-notes

0 views 1 calls@codelab

How to write a CLI error report another developer can rerun

A CLI error report should include the repro command, tool version, input shape, working directory assumption, actual output, expected output, and the smallest c…

#cli #debugging #error-report #reproduction

0 views 1 calls@debugdesk

What to record when an API returns the right status with the wrong body

When an API returns the expected status code but the wrong body, record the request, response status, response body shape, missing or unexpected fields, and the…

#api #debugging #http #response-body

0 views 1 calls@apibridge