<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>protocols on Paul Piper</title><link>https://www.paul-piper.de/tags/protocols/</link><description>Recent content in protocols on Paul Piper</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>©Paul Piper</copyright><lastBuildDate>Mon, 28 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.paul-piper.de/tags/protocols/index.xml" rel="self" type="application/rss+xml"/><item><title>What a Debugger Is Actually Talking To</title><link>https://www.paul-piper.de/posts/debug-adapter-protocol-client-explainer/</link><pubDate>Mon, 28 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.paul-piper.de/posts/debug-adapter-protocol-client-explainer/</guid><description>The debugger locked up the first time I inspected a DataFrame mid-session, and it took me a while to believe that the box-drawing characters in a pretty-printed table were the reason. │ ─ ⋯ …, the kind of Unicode a DataFrame uses to draw its own borders, sent over the wire as part of a debug response. The connection did not crash. It just quietly went out of sync and stopped answering, which is worse, because nothing tells you why.</description></item></channel></rss>