"How Do You Fix 70% Data Loss Across 1 Million Concurrent Connections?" - this is a question a Production @AkkaDotNET Support customer asked us earlier this year. We solved it.
Here's how we did it:
One of the worst testing anti-patterns we see when working with networking code: "test-and-reserve free port"
Didn't work when humans wrote it, doesn't work when AI does it. Just bind to port 0 and fetch the bound address back if you need it, rather than do it twice.
I've been wanting to get this video out the door like at least 6 weeks:
"Introducing Netclaw: Always-on, Autonomous Agent Powered by @AkkaDotNET "
Why have I spent hundreds of hours working on it, how does it help me, how does it work, and how can Netclaw help you?
Netclaw v0.24.0 is now live!
Big features in this release are all UX related:
1. Vastly simplified onboarding via `netclaw init`
2. Edit / update config any time via `netclaw config`
3. All channels (Discord / Slack / etc) have identical tooling + full parity
4. Tons of fixes
New YouTube video: "Debug Akka.Streams in Production with OpenTelemetry"
Covers the new OTEL support we added for visualizing @AkkaDotNET streams in Akka .NET v1.5.66.
We capture the full rendering of the real streams flow so you can properly debug and measure these.
A thing I haven't talked much about yet: Netclaw ships an open source "skill server" that exposes the proposed @Cloudflare agent skills standard for being able to discover / version skills just like a package feed essentially.
Idea is to make it trivial to sync skills across org
New video / blog post: "Why We Removed FluentAssertions from @AkkaDotNET "
Akka .NET 1.5.64 removed FluentAssertions from every TestKit package.
FA went commercial, and we were the 2nd-largest consumer of it on NuGet. No shade. But we won't hand a commercial dependency to every
Using SkiaSharp to resize / compress images for multi-modal LLMs in Netclaw github.com/netclaw-dev/ne…
Should make uploads more token and bandwidth-efficient
Netclaw v0.23.0 is out - lots of bug fixes and improvements in this release, including public beta build feed access:
1. Fixed numerous Docker issues (i.e. zombie processes)
2. High memory usage in tool-heavy call sessions fixed
3. Fixed Codex HTTP compat issues
4. More!
If Incremenalist suddenly broke for you, it's because changes to the most recent .NET 10 SDKs moved some MSBuild bits around. Several MSFT-hosted AzDo images all got upgraded to use that SDK.
Update to Incrementalist 1.2.1 and that'll fix it. Please RT