TAG
Debugging
Everything filed under this tag.
4 entries01Writing
Filtering kwargs with inspect.signature: a function that takes **kwargs looks like it accepts nothing, and a retry lost its model_path2026-11-08inspect.signature(f).parameters lists only declared parameters; **kwargs shows up as a single entry named kwargs. Checking by name whether a callee accepts an argument lets nothing through to the most permissive function. Autarkia’s empty-reply retry lost its model_path this way and fell back to the default model; the resulting 400s landed among upstream 503s, and that day’s error triage filed them as gateway noise.#Python#LLM#DebuggingCalibrate Your Ruler First2026-10-22Several rounds of digging in the same sandbox, and twice the measurement itself was wrong: counting the bin misses things, and the UI’s counts can scare you. What finally killed my hypothesis was a timestamp.#Forensics#Debugging
02Notes
A Clean Ping Doesn’t Mean Big Packets Get Through2026-10-27Zero packet loss and 11 ms latency, yet downloads crawled at 10–25 KB/s. Lowering the MTU to 1400 made them roughly 300 times faster.#Networking#DebuggingNon-ASCII text and parentheses in Windows batch files: commands cut into fragments after chcp 65001, and a ) inside echo closes the if block early2026-10-27When cmd reads a batch file containing multibyte characters, later lines can be read from a shifted position, producing “is not recognized” errors with half a command name; chcp 65001, UTF-8 with BOM and GBK all drifted, and only pure ASCII was stable. Autarkia hit this three times, because the checker covered one directory and wasn’t in CI.#Windows#Batch Files#Debugging