The GitHub Issue Tax: How We Solved the "Missing Debug Info" Problem

rust dev.to

Hi everyone,

I launched a new project yesterday and I'm looking for honest, blunt feedback and early beta testers.

The project is called Podshl. It’s fully free, open-source, and there are absolutely no paywalls, premium tiers, or hidden monetization.

Direct Link to the Repository: https://github.com/dx111ge/podshl

The Problem

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.

What Podshl does

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.

Current State: Early Beta

The project is just over 24 hours old. It's functional, but it is an early beta.

  • The Client: 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.
  • The Backend: The operator backend runs inside Docker. I am hosting a public test instance at https://sdota.de if you want to see how it behaves.
  • Transparency: Since the client looks at system data, everything is completely open. The client, server, and protocol are all in this single repository.

What I need from you:

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.

  1. Architecture/Code Review: If you know Rust or Tauri, is the way I'm bundling and sending data secure and efficient?
  2. Workflow Feedback: Does this actually solve the "missing debug info" problem for you, or would you handle it differently?
  3. Beta Testing: If you have a test project, try spinning up the Docker operator or using the client and tell me where it breaks.

You can dive straight into the code here: https://github.com/dx111ge/podshl

Looking forward to your honest thoughts. Don't hold back.

Source: dev.to

arrow_back Back to Tutorials