<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rahul Chaube</title>
    <description>The latest articles on DEV Community by Rahul Chaube (@rahul_chaube_).</description>
    <link>https://dev.to/rahul_chaube_</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F2082429%2F5e49d213-c479-45b9-b9e5-e123018bba01.png</url>
      <title>DEV Community: Rahul Chaube</title>
      <link>https://dev.to/rahul_chaube_</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rahul_chaube_"/>
    <language>en</language>
    <item>
      <title>A passing build didn’t tell me whether my Rust CLI could read a URL</title>
      <dc:creator>Rahul Chaube</dc:creator>
      <pubDate>Wed, 18 Nov 2026 12:50:52 +0000</pubDate>
      <link>https://dev.to/rahul_chaube_/a-passing-build-didnt-tell-me-whether-my-rust-cli-could-read-a-url-4959</link>
      <guid>https://dev.to/rahul_chaube_/a-passing-build-didnt-tell-me-whether-my-rust-cli-could-read-a-url-4959</guid>
      <description>&lt;p&gt;I’ve been working on &lt;a href="https://github.com/Rahulchaube1/Ridgewire" rel="noopener noreferrer"&gt;Ridgewire&lt;/a&gt;, a read-only Rust CLI for gathering sources. Two runs taught me more about it than a green build alone.&lt;/p&gt;

&lt;p&gt;On a fresh Linux CI runner, Ridgewire fetched a public GitHub README. That gave me a check I could point people to: the binary started, reached GitHub and got content back. &lt;a href="https://github.com/Rahulchaube1/Ridgewire/actions/runs/44284242189" rel="noopener noreferrer"&gt;Here’s the run&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;Then I tried a public Instagram Reel in a restricted environment. Ridgewire recognized the URL, but the request failed. I got no frames or caption. From the caller’s point of view, recognizing the URL was only the first step.&lt;/p&gt;

&lt;p&gt;This matters if you’re passing the output to an LLM. When a fetch fails, the model still has a plausible-looking URL to talk about. I want to know whether the tool returned enough evidence to answer the question. For a batch, I also want to be able to match each result back to the input that produced it. Ridgewire keeps those results in input order.&lt;/p&gt;

&lt;p&gt;If you want to reproduce the GitHub case, the README has the install steps and a runnable example. Try it on a repo you know. If it fails, the OS, command and error message are the three things I’d most like to see in an issue.&lt;/p&gt;

</description>
      <category>cli</category>
      <category>githubactions</category>
      <category>rust</category>
      <category>testing</category>
    </item>
  </channel>
</rss>
