SpacetimeDB
SpacetimeDB copied to clipboard
clockworklabs
Multiplayer at the speed of light
Per @bfops report: > 1. Try publishing a module with a broken client visibility filter, get an error: > ``` > Build finished successfully. > Uploading to local => http://127.0.0.1:3000...
[Tyler recently mentioned](https://news.ycombinator.com/item?id=43633625): > [the SpacetimeDB team is] definitely inspired by Elixir/BEAM. IMC (inter-module communication) is directly inspired by it. The current list of [server modules](https://spacetimedb.com/docs/modules) is: - Rust -...
# Description of Changes Heap profiling performed by @jsdt revealed that we had a memory leak in `InstanceEnv::datastore_index_scan_range_bsatn_chunks`. A bit of spelunking pointed to `ChunkPool`, a pool of buffers, which...
We noticed that, although the install scripts are tracked in the repo, we're not confident that the deployed ones were deployed from the repo. # Definition of "Done" - We...
Hi team, I'm trying to authenticate a Supabase user with SpacetimeDB using their JWT (access_token) via the /v1/identity endpoint. However, I'm encountering this error: ``` 2025-04-13T13:43:47.145222Z DEBUG crates/core/src/auth/token_validation.rs:231: Getting validator...
I followed the demo at https://spacetimedb.com/docs/modules/c-sharp/quickstart and created a module using the command: spacetime init --lang csharp server. However, following the tutorial, I couldn't find ReducerContext. I was able to...
I've been going through https://spacetimedb.com/docs/unity/part-3. When opening the `server-csharp` folder in VS Code: ```powershell cd C:\dev\unity-games\blackholio\server-csharp code . ``` It (C# DevKit?) automatically creates a `server-csharp.sln` file in the same...
**EDIT:** future updates of this patch will be here: https://github.com/dare3path/spacetimedb-tls-patch because it's becoming too dependent on locally cloned modified/patched repos(for crates like `rustls-pki-types`, `hyper-util`) and these shouldn't have to be...
Starting from the parsing, we should carry the original `sql` fragment that is the source of the error. Eventually we should also show the fragment where the error originated.
