fix(plugins): Talk and plugin-loading requests fail on PostgreSQL Gateways (#201976) Settled plugin migration readiness was cached only under the deferred migration receipt. Since that receipt became a peek, it stays absent until a migration write publishes one, so the worker's startup read was never reused and every synchronous plugin load reread the ledger on the Gateway thread. PostgreSQL refuses that read, which left Talk "warming" and failed other plugin-loading requests with "must run in a worker". Key unpublished readiness by the current state read admission instead. Migration writes still publish a new receipt, and closing or replacing the database retires the admission. Closes #201969 Co-authored-by: VACInc <3279061+VACInc@users.noreply.github.com>
Current
·
C2
·2026-11
fix(plugins): Talk and plugin-loading requests fail on PostgreSQL Gat…
Find Your Interest
- Walter initially demanded $800 million,
- Behind the Scenes - A Glimpse into Tax Calculations
- Ambitions, Goals, and Themes
- Shoot yourself in the foot with iptables and kmod auto-loading
- fix: saving an agent no longer looks failed while a plugin reload is …
- Kuzma on Space, Tech and Investing
- Kettal’s Area Tables Hide Office Wiring Inside Sculptural Legs
- The original offer from Feliciano and Jones was $720 …
- fix: let PostgreSQL Gateways start with plugin-backed secrets (#201063)
- Mark Walter Could Sell The WNBA’s Los Angeles Sparks For Record $750 Million, Reports Say
Current
·
C2
·2026-11





