Eric P Green
Eric P Green
Rather than showing a raw JSON string, we should have a more presentable error component. 
For capturing runtime errors: - Svelte does not have a native error boundary. See: https://github.com/sveltejs/rfcs/pull/46. - The oft-cited third-party Svelte library is the [Crown Framework](https://github.com/CrownFramework/svelte-error-boundary), but it is unmaintained. -...
A deployed example will: - Help showcase what the embed code looks like end-to-end (frontend and backend) - Help us test embeds in a production environment

JAM video: https://jam.dev/c/7caa6124-464b-4208-be58-295ecb67d8ec In the video, note that filtering for "New cases" > 0, both 'Panama' (50 new cases) and 'Turks and Caicos Islands' (10 new cases) get filtered out....
Our current state management package suffers from unnecessary derived store updates, which has numerous downstream performance impacts. It's described in "Problem 1" of https://github.com/rilldata/rill/issues/3960. Rather than one monolithic store to...
Our current state management package suffers from unnecessary derived store updates, which has numerous downstream performance impacts. It's described in "Problem 1" of #3960. We have a hypothesis that Immer...
[As described in Slack](https://rilldata.slack.com/archives/C02T907FEUB/p1704802388816389)
This happens because of a race condition: we're refreshing the JWT and firing runtime queries at the same time. To fix: 1. When setting a runtime JWT in the client-side...