Skip to content
- Docs at docs.pitomd.com: install on each platform, ten guides from writing a source to testing one, the file formats, and the API reference. Every GitHub Release carries them as
docs-vX.Y.Z.tar.gz.
- The
numbers example measures the crate on your machine: cargo run --release --example numbers.
- pito-sync reaches 1.0.0; the API is the same as 0.1.5.
- The README shows every feature with a chart, a clip or code and its output, and leads with measured numbers: a UI read takes 47 µs while a source writes 10,000 rows back to back.
- The brand now reads PITO MD.
- The
feed example: a source on its own thread, a secret handed in after start, resyncs, a failed pass that keeps its rows, and a UI that only reads.
- MIT licence, CI on Linux and macOS, and a GitHub Release for every tag.
- The README is written for anyone who wants to use the crate, with an animated run of the example.
- The tests run with cargo-nextest, and the doctests with cargo test.
spawn_checked opens the database on the calling thread and returns the open error, or moves the connection into the runner thread; spawn is unchanged.
pass_once runs one pass on the calling thread (mark started, run the pass, record a failure), and the runner wraps exactly that with its two Changed sends.
- An explicit
Resync always runs, even right after a pass.
- A failed pass records its finish, the runner announces each pass’s start, and the first pass runs at once.
- The local-SQLite sync layer: one database per app, opened private with WAL and rebuilt when its version changes, sources on their own threads,
Changed and Resync.
