Ashish Yadav’s Post

If you've checked HackerNews or Lobsters this morning you'll see that GitHub has finally launched a stacked pull request in private preview. The long-awaited coding workflow is wait-list only at the moment, but that hasn't stopped devs and users from weighing in. The full story is on The Stack now. https://lnkd.in/e6m8qPP8

I’m excited to share a recent third (3)contribution to the OpenClaw codebase addressing a subtle but impactful concurrency issue in the Discord gateway integration. A pull request titled “fix(discord): clear stale heartbeat timers in SafeGatewayPlugin.connect()” has been merged into the main branch. This fix improves the stability and reliability of the Discord gateway connection layer by addressing a race condition in heartbeat initialization. The core problem was that stale heartbeat timers were not being properly cleared during the reconnect lifecycle inside SafeGatewayPlugin.connect(). As a result, intermittent uncaught exceptions could occur, leading to gateway process crashes and disrupted in-flight responses. This type of issue is particularly difficult to reproduce because it manifests under timing-sensitive conditions in asynchronous execution. The solution introduces a controlled override of the connect flow, ensuring that any previously active heartbeat intervals are explicitly cleared before establishing a new connection. This eliminates overlapping timers and prevents inconsistent state transitions in the gateway lifecycle. Key impact of this change: - Improves gateway stability under reconnect scenarios   - Eliminates race conditions in heartbeat scheduling   - Prevents unexpected crashes caused by stale interval execution   - Enhances reliability of real-time communication handling  This is a good example of how small lifecycle management issues in asynchronous systems can cascade into production-level instability, especially in distributed event-driven architectures. Overall, the fix strengthens the robustness of the Discord integration layer and contributes to more predictable system behavior under load and reconnect conditions. Hashtags: #OpenSource #GitHub #SoftwareEngineering #BackendDevelopment #SystemDesign #DistributedSystems #Concurrency #AsyncProgramming #NodeJS #TypeScript #Debugging #BugFix #ReliabilityEngineering #DevOps #EventDrivenArchitecture #CodeQuality

🚀 Day 93 of #1000DaysOfCoding Today was less about coding… and more about becoming a real developer. I finally moved my full-stack project from local to GitHub — sounds simple, but the journey was full of real-world challenges: 💥 Faced Git errors like large file limits 💥 Accidentally pushed node_modules (never again 😅) 💥 Learned why .gitignore is not optional 💥 Understood how Git actually tracks history (not just files) 💥 Fixed branch & remote issues like a pro And the best part? ✅ Clean repo structure ✅ Proper version control setup ✅ Ready for deployment 🚀 This wasn’t just “uploading code” — It was understanding how developers actually work in production. 💡 Small lesson: If your code works locally but you can’t version or deploy it — you’re not done yet. Next step: 👉 Deploying this project live (Frontend + Backend + DB) Let’s see how it goes 🔥 #1000DaysOfCoding #Day93 #Git #GitHub #FullStackDevelopment #SpringBoot #ReactJS #MongoDB #LearningInPublic #DeveloperJourney

The Problem We've all been there: dozens of old repos from tutorials, abandoned side projects, and test experiments piling up. Cleaning them up one by one through the GitHub UI is painfully slow — especially when you need to delete 20+ at once. The Solution I got tired of the manual process, so I built GitHub Repo Bulk Deleter — a lightweight local web tool that lets you wipe out multiple repositories in seconds. How it works: Paste your GitHub token → your repos load automatically Search, filter by Public/Private, and tick the ones you want gone Confirm with a safety prompt → watch them delete in real time Key Features ✅ Auto-load: Fetches your entire repo list with one click — no URL copy-pasting ✅ Smart Select: Search, filter by visibility, or hit Select All ✅ Real-time Progress: Each deletion streams live via Server-Sent Events ✅ Safe by Design: Requires typing DELETE before anything is removed ✅ CLI Mode: Scriptable via file input or stdin for automation use cases Tech Stack Built with #NodeJS, #ExpressJS, and the #GitHubAPI — zero frontend frameworks, no build step required. Open Source The project is free, open-source, and ready for feedback! 👇 https://lnkd.in/gbX8MgNc #WebDev #SoftwareEngineering #OpenSource #CleanCode #Automation #GitHub #DeveloperTools #NodeJS

I just helped close a bug that had a developer stuck for 3 weeks. Not by writing a single line of code. Just by debugging it the right way. 🧠 Here's what was happening 👇 A developer was calling Appwrite's Users API with pagination. ✅ Without query params → 200 OK ❌ With query params → 401 Unauthorized Same API key. Same endpoint. Different result. He tried 5 different approaches over 3 weeks. Nothing worked. When I looked at it, the fix was one line. # ❌ What he was using queries[]=limit(1) # ✅ What actually works queries[0]={"method":"limit","values":[1]} Appwrite 1.x moved to JSON query format. He was still using the old 0.x shorthand syntax. 3 weeks. One syntax change. Issue closed. ✅ This is what I love about open source. You don't always need to write code to contribute. Sometimes showing up and helping someone debug is the most valuable thing you can do. If you're a developer, go contribute to open source. Comment on issues. Help others debug. You'll learn more from real bugs than from any tutorial. #OpenSource #GitHub #Appwrite #BackendDevelopment #BuildInPublic #SoftwareEngineering #DevCommunity #100DaysOfCode #Programming #APIDevelopment

🚀 6 Free GitHub Repos That Can Save You $100+/Month on Claude Code If you're deep in Claude for daily coding and your token bill is creeping up, this one's for you. I came across this brilliant hand-drawn breakdown (image above) and had to share it. These 6 open-source tools are quietly helping developers cut costs while getting sharper, faster, and more useful outputs. Here’s the quick hit list: 1. vercel-labs/agent-browser Replaces Claude in Chrome. Uses the accessibility tree instead of screenshots or messy HTML. Clean context, zero noise. 2. rtk-ai/rtk 60-90% faster on common commands (npm run, git commit, pnpm test, etc.). Real-world savings of 20-30% in actual workflows. 3. juliusbrussee/caveman The “terse-output” skill we all needed. Drops the fluff and filler. Responses become direct: “use map(), not filter(). Return acc.” 4. tirth8205/code-review-graph Up to 49× fewer tokens on daily coding tasks via AST mapping. One of the biggest efficiency wins on the list. 5. Gronsten/claude-usage-monitor Real-time 5-hour usage window + live active-session token tracking. Know exactly where you stand before you hit the cap. 6. phuryn/claude-usage Historical breakdowns by session, day, and week. Beautiful charts showing exactly where your tokens (and money) went — and what to fix. The real magic? Stack them. Use what you need. Save money. Ship more. Compounding wins. These are all free, actively maintained, and built by the community. If you’re serious about getting more signal and less spend from Claude, go star them now. Which one are you trying first? Or drop your own favorite Claude optimization tool in the comments 👇 Let’s help each other build faster and cheaper. #ClaudeAI #Anthropic #AIforDevelopers #GitHub #DeveloperTools #TokenOptimization #Productivity #OpenSource #SaveMoney

🚀 Just shipped Auto-Deploy on Nexus — push to GitHub, go live automatically. I've been building Nexus, a full-stack deployment platform (think a self-hosted Vercel), and today I shipped a feature that completes the CI/CD loop: ⚡ GitHub Auto-Deploy via Webhooks Here's what it does: → Connect your GitHub repo to a Nexus project → Enable Auto-Deploy with one toggle → Get a unique webhook URL + HMAC-SHA256 secret → Paste it into GitHub's webhook settings → From that moment, every push to your tracked branch triggers an automatic deployment — no manual clicking required And the engineering behind it wasn't trivial: 🔐 Secure by design — Every incoming webhook is verified using HMAC-SHA256 signature validation (timing-safe compare). Invalid signatures are rejected before any logic runs. 🧱 Middleware ordering matters — The biggest gotcha was that Express's express.json() consumes the raw body stream, making HMAC verification impossible. The fix was registering the webhook route with express.raw() before the JSON middleware — the same pattern used for Stripe/Razorpay webhooks. 🛡️ Multiple safety layers: Branch matching (only deploy on the right branch) Repo URL identity check (no cross-repo spoofing) Build quota enforcement before triggering Branch deletion events are gracefully skipped 📦 Full stack: TypeScript, Node.js, Express, MongoDB, React — deployed with its own infrastructure. If you're building something and tired of manually clicking "redeploy" every time you push — this is the workflow you want. 👉 I'm looking for early testers: If you want to try Nexus and ship your frontend projects with one push, here's the link https://madhavkumar.tech #buildinpublic #webdev #devtools #nodejs #typescript #cicd #opensource #deployment #javascript #react #github

🚀 GitHub just made code reviews a lot smarter with Stacked PRs (gh stack) If you’ve ever opened a massive PR and thought: Who is going to review this? you’re not alone. That’s exactly the problem GitHub is solving with stacked pull requests. 💡 Instead of one huge PR: You break your work into small, logical layers, each as its own PR, stacked on top of each other. 👉 Example: PR #1 → Auth logic PR #2 → API endpoints (depends on #1) PR #3 → Frontend (depends on #2) Each PR is: ✔ Easier to review ✔ Faster to merge ✔ Less prone to conflicts And the best part? 🔧 GitHub now supports this natively with: • A stack-aware UI (navigate layers easily) • Cascading rebases with one click • CLI support via `gh stack` • Ability to merge the entire stack together No more messy rebasing or waiting for one PR to merge before starting the next. 🔥 Why this matters: • Improves developer velocity • Makes code reviews actually meaningful • Reduces “PR fatigue” in teams This feels like a big step toward how modern teams should be shipping code. 🔗 gh stack: https://lnkd.in/dRvP8Cny #GitHub #SoftwareEngineering #DevWorkflow #CodeReview #Developers #Tech

"i have about 15 actively developed repos under cyberwitchery, most of them rust libraries that need the usual routine maintenance: dep bumps, clippy warnings, typos, missing tests, the occasional half-implemented feature someone (me) left behind. i wanted something that would chip away at that backlog steadily in the background, without me having to remember or schedule it." This is from Veit Heller's writeup on his own Heartbeat project (check the link). I would've been dismissive like a lot of the software engineers I know (and respect) if it wasn't for Veit, Mitchell Hashimoto, Thorsten Ball and others who find legit ways to use LLMs for coding. This is not your marketing manager vibe coding a website for themselves (also legit way). These are hardcore super devs experimenting and figuring things out and finding out what works for them and what doesn't. Without hype and without trying to sell anyone any vaporware. #softwaredevelopment #itisjustanothertool #yallneedtochilloutonthehypemode #eatarepasandsmile https://lnkd.in/dEdf5AKf