<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debugging on Random Ramblings</title><link>https://blog.foundev.pro/tags/debugging.html</link><description>Recent content in Debugging on Random Ramblings</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 27 Dec 2019 09:30:00 -0600</lastBuildDate><atom:link href="https://blog.foundev.pro/tags/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>Snakeyaml error handling is tough</title><link>https://blog.foundev.pro/2019/12/27/snakeyaml-perms.html</link><pubDate>Fri, 27 Dec 2019 09:30:00 -0600</pubDate><guid>https://blog.foundev.pro/2019/12/27/snakeyaml-perms.html</guid><description>&lt;h1&gt;"Snakeyaml error handling is tough"&lt;/h1&gt;&#10;&lt;p&gt;Cassandra for years has relied on snakeyaml to parse configuration files, and it does a fine job, really not a lot of complaints. Until one day a colleague of mine discovered an issue where a permission issue incorrectly reported as an invalid yaml file (complete with the supposedly offending key). Digging into the source code and trying to match up the message. I found that &lt;a href="https://github.com/apache/cassandra/blob/06209037ea56b5a2a49615a99f1542d6ea1b2947/src/java/org/apache/cassandra/config/YamlConfigurationLoader.java#L128"&gt;we were handling YAMLException&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>