The latest articles on DEV Community by Sven Andreas (@sven_andreas_fae0d1f8019f). https://dev.to/sven_andreas_fae0d1f8019f 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%2F3441406%2F4a482cc9-accb-475b-90d6-0d25f6c3242e.png https://dev.to/sven_andreas_fae0d1f8019f en Sven Andreas Mon, 14 Sep 2026 09:45:40 +0000 https://dev.to/sven_andreas_fae0d1f8019f/the-github-issue-tax-how-we-solved-the-missing-debug-info-problem-22i https://dev.to/sven_andreas_fae0d1f8019f/the-github-issue-tax-how-we-solved-the-missing-debug-info-problem-22i <p>Hi everyone,</p> <p>I launched a new project yesterday and I'm looking for honest, blunt feedback and early beta testers. </p> <p>The project is called <strong>Podshl</strong>. It’s fully free, open-source, and there are absolutely no paywalls, premium tiers, or hidden monetization. </p> <p>Direct Link to the Repository: <a href="https://github.com/dx111ge/podshl" rel="noopener noreferrer">https://github.com/dx111ge/podshl</a></p> <h2> The Problem </h2> <p>Every maintainer knows the frustration: someone opens a GitHub issue saying "it crashes," but provides zero logs, zero environment context, and no OS details. You then spend days chasing them down for basic debug data.</p> <h2> What Podshl does </h2> <p>It’s a lightweight support client designed to bridge this gap. Instead of forcing users to copy-paste messy logs into GitHub comments, the user runs a lightweight client that securely bundles the necessary system state/logs and transmits them directly to the maintainer.</p> <h2> Current State: Early Beta </h2> <p>The project is just over 24 hours old. It's functional, but it is an <strong>early beta</strong>. </p> <ul> <li> <strong>The Client:</strong> Built with Rust and Tauri. It compiles to a binary under 7 MB because nobody wants to download a heavy framework just to send a bug report.</li> <li> <strong>The Backend:</strong> The operator backend runs inside Docker. I am hosting a public test instance at <a href="https://sdota.de" rel="noopener noreferrer">https://sdota.de</a> if you want to see how it behaves.</li> <li> <strong>Transparency:</strong> Since the client looks at system data, everything is completely open. The client, server, and protocol are all in this single repository.</li> </ul> <h2> What I need from you: </h2> <p>I don't care about stars or artificial hype. I need real developers and maintainers to tear this apart and tell me what works and what doesn't.</p> <ol> <li> <strong>Architecture/Code Review:</strong> If you know Rust or Tauri, is the way I'm bundling and sending data secure and efficient?</li> <li> <strong>Workflow Feedback:</strong> Does this actually solve the "missing debug info" problem for you, or would you handle it differently?</li> <li> <strong>Beta Testing:</strong> If you have a test project, try spinning up the Docker operator or using the client and tell me where it breaks.</li> </ol> <p>You can dive straight into the code here: <a href="https://github.com/dx111ge/podshl" rel="noopener noreferrer">https://github.com/dx111ge/podshl</a></p> <p>Looking forward to your honest thoughts. Don't hold back.</p> opensource rust programming