building Weave : a p2p overlay network in rust. packets, routing, peer discovery, handling nodes going offline. the whole thing. starting from the basics and seeing how far i can take it.

added a web UI for forgequeue we going big this time

proposal for the Oppiabot Consolidation Project got accepted :) starting my internship at Oppia Foundation, where I'll be working on a unified TypeScript Core Engine + Plugin Framework for Oppiabot. gonna be working on the architecture, plugin system, GitHub integrations, and migrating the existing workflows over to it. should be a pretty interesting few months :)

was inactive due to some days due to fuckass college but now --> finished the ownership and fencing part, so an old worker can't keep renewing or acknowledging a task after its lease has been replaced --> made recovery race-safe too : recovery now checks the lease again before requeueing, instead of trusting the result of an earlier expiry scan --> connected lease loss to the actual handler, so a worker losing ownership can cancel the task it's currently running --> after getting the failure path into a decent state, I started looking at performance and found another unnecessary Redis trip in the normal execution path --> changed the claim script to return the task body along with the lease, then ran the benchmark properly — ~8.26k tasks/sec vs ~7.86k before --> also started doing proper head-to-head runs against BullMQ. we're currently pretty close on a quiet machine, which gives me a much better baseline for figuring out where the next gains actually are --> turns out the interesting part isn't really Go vs Node it's actually how much Redis work we're doing per task next: batching that work and seeing how far the numbers actually move then add dead letter queue and metrics etc and then maybe some more optimizations till we are better