KyleAMathews

Now I have the complete picture. Let me write the investigation report.

Issue #3433: Container error: Stack not ready after 5000ms. Reason: Timeout waiting for shape data to be loaded

Summary

The Electric container enters an unrecoverable error state after restart, emitting Stack not ready after 5000ms. Reason: Timeout waiting for shape data to be loaded. A simple docker compose restart doesn't fix it because persistent shape data survives the restart; only docker compose down && docker compose up (which removes volumes/data) resolves the issue. All API requests get 503 responses indefinitely.

Root cause analysis

KyleAMathews

Now I have a complete picture. Let me write the investigation.

---

Issue #1012: type errors when using ts project references / declaration

Summary

When consumers use declaration: true in their tsconfig.json (common with TS project references), TypeScript emits errors like "The inferred type of 'xyz' cannot be named without a reference to .../node_modules/@tanstack/db/dist/esm/query/builder/types". This happens specifically when using query joins and select. The root problem is that several types used in public method return signatures are not re-exported from the package's public API.

KyleAMathews

Durable Streams: Epoch/Caching Discussion Analysis

Review of the conversation about whether epoch/must-refetch should be part of the core Durable Streams protocol or remain an implementation detail.

Missing Technical Arguments

1. Error Code Semantics

The discussion mentions 400 vs 410 but doesn't explore that 410 Gone is actually cacheable by CDNs per HTTP spec. This could be important - a cached 410 tells clients "don't bother asking again" which has different implications than an uncacheable 400.

2. The Redirect Option Was Dropped

KyleAMathews

Deep Dive: Cacao Roasting Theory

A comprehensive summary of roasting guides from Chocolate Alchemy and Dandelion Chocolate, focused on the science of what happens during roasting, with special attention to acetic acid removal, heat penetration, and flavor development.

---

The Core Problem: Under-Roasting

The most common issue in craft chocolate is under-roasting — not in duration, but in heat penetration. Without monitoring actual bean temperature, roasters often stop when the surface seems done while the interior remains under-roasted.

KyleAMathews

Actual Code Excerpts from Electric TypeScript Client Tests

All examples are taken directly from: ~/programs/electric/packages/typescript-client/test

1. Vitest Configuration (vitest.config.ts)

import { defineConfig } from 'vitest/config'

export default defineConfig({

KyleAMathews

#!/bin/sh

# This script is for installing the latest version of Turso CLI on your machine.

set -e

# Terminal ANSI escape codes.
reset="\033[0m"
bright_blue="${reset}\033[34;1m"

KyleAMathews

let mapleader = ','

if empty(glob('~/.vim/autoload/plug.vim'))
  silent !curl -fLo ~/.vim/autoload/plug.vim --create-dirs
    \ https://raw.githubusercontent.com/junegunn/vim-plug/master/plug.vim
  autocmd VimEnter * PlugInstall --sync | source $MYVIMRC
endif

call plug#begin('~/.config/nvim/plugged')

KyleAMathews

  // Available variables:
  // - Machine
  // - interpret
  // - assign
  // - send
  // - sendParent
  // - spawn
  // - raise
  // - actions

KyleAMathews

diff --git a/packages/gatsby-recipes/src/gui.js b/packages/gatsby-recipes/src/gui.js
index a7baf92b1..378477678 100644
--- a/packages/gatsby-recipes/src/gui.js
+++ b/packages/gatsby-recipes/src/gui.js
@@ -26,6 +26,7 @@ const {
   defaultExchanges,
   subscriptionExchange,
 } = require(`urql`)
+const UrqlProvider = Provider
 const { SubscriptionClient } = require(`subscriptions-transport-ws`)

KyleAMathews

/Users/kylemathews/programs/recipes-test/node_modules/trough/wrap.js:33
        throw error
        ^

SyntaxError: unknown: Unexpected token (31:2)

  29 | />
  30 | export const FileTest = () => {
> 31 |   const data = useInputByUuid("blog-title")
     |   ^