mirror of
https://github.com/hanzoai/collab.git
synced 2026-10-30 18:44:20 +00:00
zeekayandHanzo Dev
3d02cf7c01
A document was one blob that every frame rewrote whole, from a goroutine started per frame, with nothing capping the blob or the file. Any IAM user could stream frames at doc ids under their own org and fill the disk the volume sits on, or stream at one doc until the goroutines queued behind the write lock ran the pod out of memory. Each frame is now its own row, so an append writes the frame and nothing else. The reader persists a frame before it reads the next, so a connection has at most one append in flight, and one database connection serializes them. Four bounds hold: a frame over 1 MiB closes the connection (1009), more than 50 frames a second past a burst of 200 closes it (1008), a document stores at most 16 MiB, and max_page_count holds the file to COLLAB_STORE_BYTES. The journal is a rollback journal, so the files never pass twice that. The store applies its pragmas per connection through hanzoai/sqlite's OpenPragma, which both driver backends honour; a DSN carries them only on the pure-Go one. Only frames that carry document content are stored: y-websocket sync step 2 and update. Awareness, sent on every cursor move, and sync step 1 are relayed and dropped, since replaying them rebuilds nothing. A joining peer gets each stored frame as its own message. They used to be concatenated into one, and y-websocket decodes one message per frame, so a client applied the first and lost the rest. A token is read from the Authorization header or from a bearer.<token> entry in the subprotocol list a browser offers beside yjs, never from the query string, which the edge writes to its access log. When a JWKS refresh fails, the keys of the last good fetch keep verifying, so an IAM outage past the cache TTL no longer refuses every token for the refresh window. A refresh that succeeds and drops a key still revokes it. The S3 adapter goes: production runs SQLite, and the adapter had never stored anything. The tables are new (doc, frame); a database written by 0.1.x keeps its docs table, which nothing reads. Co-authored-by: Hanzo Dev <[email protected]>
40 lines
1.4 KiB
AMPL
40 lines
1.4 KiB
AMPL
module github.com/hanzoai/collab
|
|
|
|
go 1.27.1
|
|
|
|
require (
|
|
github.com/coder/websocket v1.8.12
|
|
github.com/golang-jwt/jwt/v5 v5.3.1
|
|
github.com/hanzoai/sqlite v0.3.0
|
|
github.com/luxfi/metric v1.7.0
|
|
)
|
|
|
|
require (
|
|
github.com/cenkalti/backoff v2.2.1+incompatible // indirect
|
|
github.com/cloudflare/circl v1.6.3 // indirect
|
|
github.com/dustin/go-humanize v1.0.1 // indirect
|
|
github.com/google/uuid v1.6.0 // indirect
|
|
github.com/gorilla/rpc v1.2.1 // indirect
|
|
github.com/grandcat/zeroconf v1.0.0 // indirect
|
|
github.com/hanzoai/csqlite v0.1.0 // indirect
|
|
github.com/luxfi/accel v1.2.4 // indirect
|
|
github.com/luxfi/crypto v1.19.26 // indirect
|
|
github.com/luxfi/mdns v0.1.1 // indirect
|
|
github.com/luxfi/zap v0.7.2 // indirect
|
|
github.com/mattn/go-isatty v0.0.21 // indirect
|
|
github.com/miekg/dns v1.1.72 // indirect
|
|
github.com/ncruces/go-strftime v1.0.0 // indirect
|
|
github.com/remyoudompheng/bigfft v0.0.0-20230129092748-24d4a6f8daec // indirect
|
|
golang.org/x/crypto v0.52.0 // indirect
|
|
golang.org/x/mod v0.36.0 // indirect
|
|
golang.org/x/net v0.55.0 // indirect
|
|
golang.org/x/sync v0.20.0 // indirect
|
|
golang.org/x/sys v0.45.0 // indirect
|
|
golang.org/x/tools v0.45.0 // indirect
|
|
google.golang.org/protobuf v1.36.11 // indirect
|
|
modernc.org/libc v1.70.0 // indirect
|
|
modernc.org/mathutil v1.7.1 // indirect
|
|
modernc.org/memory v1.11.0 // indirect
|
|
modernc.org/sqlite v1.48.1 // indirect
|
|
)
|