Community database protocol: ogc-db-proto #43
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "db-proto"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
First piece of the community database (CompressDB), per the design: the crate
crates/ogc-db-proto, which the app, the intake service and the aggregator (repoLevelXStudios/ogc-db) will share. Nothing in the app uses it yet.steam:,epic:,gog:,amazon:; numeric IDs without leading zeros, so one game has one key), builds, content platform, method keys as text (btrfs-zstd:N,wof:*; the kernel's own level maps tobtrfs-zstd:3).round(4·log2(MiB))computed exactly in integers, percentages rounded to 5, the rules for poorly compressing extensions.deny_unknown_fieldsallowlist, cross-field rules, a canonical writer (sorted keys, no whitespace, pad last, exactly 1024 bytes).genblocklist, injected app-ID set; each rejection is one code of the fixed enum.Tests: golden bytes of both examples of the design, determinism across machines, proptest leak tests, every validator bound positive and negative, proof-of-work known-answer vectors checked independently in Python.
The root
Cargo.tomlbecomes a workspace (the root package is unchanged). It excludestarget/, because cargo refuses crates unpacked below a workspace (the Arch package'scargo packagetree, accesskit-c in GTK's build). CI's check job formats, lints and tests the whole workspace; the Windows jobs are unchanged. ARCHITECTURE.md has a section on the crate.