Chase Granberry

#bigquery #streaminganalytics #logsaremetrics #structuredlogging @elixirlang @elixirphoenix #myelixirstatus

5/ One problem: just-bash is TypeScript. Knock is Elixir. But a bash interpreter with a thorough test suite is a perfect target for an agent-assisted port. @ivarvong took the bait. Many tokens later: just_bash, a full bash + virtual FS in Elixir. github.com/elixir-ai-tool…

we've upgraded the logs interface in supabase opt-in new interface via a toggle. feedback welcome key features: ◆ all logs in a single unified interface ◆ easier filtering ◆ log enrichment (eg: with authenticated user info)

We have a forking 🍴 feature landing end of the month. It allows you to transparently fork any running VM in ~10ms, even at scale, without interrupting the parent VM you spawned the forked (children) VMs from. And you can do this recursively, spawning VMs from VMs. The mechanism is powerful, and useful for many use cases, including launching sub-agents and cloning/forking production DBs for (safely) doing development work on them. We also wanted to test its limits: what about forking a 1TB VM/DB? That's also possible in a super nimble < 200ms ⚡️: check the video below out!

We worked with @supabase to improve the performance of Logflare, a large distributed Elixir app that handles log processing across their entire infrastructure. 📈 The problem? The ingestion pipeline was going through every filtering rule for every single incoming event, so we restructured it to skip rules that clearly don't apply. 👀 We also moved the BigQuery integration to a newer API and shipped the adapters that became the foundation for Log Drains destinations. Link to the full case study in 🧵

Ale was the main engineer behind Livebook Teams. He implemented the client-server protocol (over protobuf), enterprise controls via OpenID Connect, and production monitoring + instrumentation. Strong recommendation for a backend engineer role.

One of the first Elixir libraries I wrote was a NIF for the Arcade Learning Environment. It was really bad Elixir. Anyway, I revamped it and here's a video of Axon playing Breakout from a Livebook

QuackDB 0.5 is out 🦆 I’m increasingly convinced that @duckdb is becoming one of the best storage choices for hobby to medium-sized projects. Postgres is still the obvious default for highly concurrent OLTP systems, but many small and medium products are read-heavy, append-heavy, analytical, or operated by a small team. For those workloads, DuckDB’s columnar execution model, vectorized engine, rich SQL surface, and embedded/local-first deployment model can be a much better fit. I intend to use DuckDB as the primary storage layer for the platform I’m building, so QuackDB focuses on the parts I need in a real Elixir app: supervision, connection pooling, Ecto, fast append paths, dataframes, telemetry, and helpers for DuckDB’s analytical SQL. 0.5 focuses on making the Ecto and analytical side much more complete: - append through Ecto with defaults and returning - using an Ecto repo directly with QuackDB native query/append APIs - advanced join patterns, including semi/anti and ASOF-style queries - DuckDB star/COLUMNS expressions in SQL and Ecto - broader LIST/MAP/STRUCT helpers - PIVOT, UNPIVOT, GROUPING SETS, ROLLUP, and CUBE builders - LIST lambdas in Ecto with `fn` syntax and `case_when` - better nullable/schema type handling for append-heavy workloads QuackDB also continues to cover the broader integration surface: supervised DuckDB, DBConnection/Ecto, native append, Explorer dataframes, Table.Reader results, Geo/WKB, telemetry, managed DuckDB binaries, and DuckDB-specific SQL helpers. github.com/elixir-vibe/qu…

Announcing deflua.com 🎉 The new home for Lua, the pure-Elixir Lua 5.3 VM for @elixirlang. Scriptable, sandboxed, stupid easy. Embed untrusted code (AI agent tools, user formulas, plugins) all on the BEAM, zero NIFs. Plus a live playground 👇

Slack needs to auto tag messages that were AI generated.

Have it build tools for itself. What are we calling this now? Code mode?

I'm pretty sure the only reason to use Kafka for telemetry data in 2026 is muscle memory. A simple, open source, S3-backed pipeline can shuttle 1Gb/s of logs to @ClickHouseDB for $200/mo with 2.8s p50 latency. Fast enough for us. opendata.dev/blog/ingesting…

you mean there is nuance in the compute storage separation discourse? strange

wait wut

Email > Slack I’ll fight for this one

@simpsoka No way my mom is target market!

@chasers Are you calling me a boomer chase?

Been thinking about an email interface to Slack for boomers

@zeeg Have it hallucinate tools in the background maybe it’ll give you ideas for new ones!!

Pushed a change to the Sentry MCP that bridges the gap between embedded agents (~subagents) and composable tools. All `search_` tools now run an LLM across the query input, meaning they support structured params + natural language, and the LLM can pull in all the various tool calls to course correct it as needed. If you notice any wacky behaviors here let me know. This is all pretty greenfield!

Until now, LiveVue supported only two SSR modes: ➡️ Vitejs-based (for development) ➡️ Nodejs (for production) Now I'm introducting a third one: ✅ QuickBeam It's running QuickJS as NIF, which is more performant. Now a default mode! Thanks @dan_note for contribution!

@SamRose I’ve wanted an excuse to

Are elixir folks out there still actively using and working with github.com/lucaong/cubdb ?

erlang_quic 1.3.0 is out. First production-ready release. Pure-Erlang QUIC + HTTP/3, zero C deps. - RFC 9000 / 9001 + 9114 / 9204 - Priorities, datagrams, CONNECT - -proto_dist quic for clusters - OTP 27+ github.com/benoitc/erlang…