TL;DR. golang.org/x/net/idna.Lookup.ToASCII runs UTS-46 NFKC mapping 0-9. A pre-IDNA net.ParseIP check rejects the NO_PROXY lists, TLS-SNI routers, and cookie-domain validators that TrimRight + ParseAddr golang.org/x/net/http/httpproxy, the canonical safe pattern, and two I ran into this one while writing a Go HTTP client for a private project. I idna.Lookup.ToASCII canonicalising the host The sha
If your local-Ollama agent has been getting quietly worse for no obvious reason — same model, same hardware, same prompts — there's a good chance you're hitting an invisible ceiling that produces no error, no warning, and no log line. Just an empty response where an answer used to be. I want to walk through how this manifests, why it's specifically painful for autonomous agent workloads (not chat)