Turtle. A hard-fork of atuin, focusing on a more minimal feature set http://git.foss-syndicate.org/bpeetz/forks/atuin/atom/atuin-client/src/record/sync.rs?h=main 2024-04-18T15:41:28Z 2024-04-18T15:41:28Z Ellie Huxtable ellie@elliehuxtable.com 2024-04-18T15:41:28Z urn:sha1:95cc472037fcb3207b510e67f1a44af4e2a2cae9 I'd like to tidy up the root a little, and it's nice to have all the rust crates in one place 2024-04-05T14:51:57Z Yaroslav Halchenko debian@onerussian.com 2024-04-05T14:51:57Z urn:sha1:28b0b490f93fe9f7964d0593b9ba600f4b24663e * Add github action to codespell main on push and PRs * Add rudimentary codespell config * ignore crate, inbetween etc * [DATALAD RUNCMD] run codespell throughout fixing typo automagically but ignoring the failure due to ambigous typos === Do not change lines below === { "chain": [], "cmd": "codespell -w || :", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ * [DATALAD RUNCMD] Do interactive fixing of leftover ambigous typos === Do not change lines below === { "chain": [], "cmd": "codespell -w -i 3 -C 2", "exit": 0, "extra_inputs": [], "inputs": [], "outputs": [], "pwd": "." } ^^^ Do not change lines above ^^^ 2024-02-12T09:25:06Z Eric Long i@hack3r.moe 2024-02-12T09:25:06Z urn:sha1:5a805dc22c99050db0a54f35e660516c57fa4b94 Low-end devices like RISC-V SBCs are sometimes too slow to initialize SQLite in 0.1s. Option to specify a higher value allows check to pass on such devices with relaxed restrictions. 2024-02-08T13:34:41Z Ellie Huxtable ellie@elliehuxtable.com 2024-02-08T13:34:41Z urn:sha1:8460210202af4e48ea55c997bf2739a6f0570e4a Replace lots of logging with some progress bars. This looks much nicer I'd like to move it out of the atuin-client crate and into the atuin crate. But first, I want to decouple a lot of the record moving, so it can wait until that's done. 2024-02-04T20:06:47Z Ellie Huxtable ellie@elliehuxtable.com 2024-02-04T20:06:47Z urn:sha1:3ff2e2552f5b4db9c8b8e127ff833873902258c0 2024-01-29T16:38:24Z Ellie Huxtable ellie@elliehuxtable.com 2024-01-29T16:38:24Z urn:sha1:366b8ea97bbe36ad5e3dd8d45f1e787ee2a7f223 * add support for getting the total length of a store * tidy up sync * auto call init if history is ahead * fix import order, key regen * fix import order, key regen * do not delete key when user deletes account * message output * remote init store command; this is now automatic * should probs make that function return u64 at some point 2024-01-19T15:45:42Z Ellie Huxtable ellie@elliehuxtable.com 2024-01-19T15:45:42Z urn:sha1:8899ce5089091e21eae088da692468565401abba * fix: add acquire timeout to sqlite database connection This should fix #1503 I wasn't able to trigger enough IO pressure for the SQL connection to be a problem. This adds `local_timeout` to the client config. This is a float, and represents the number of seconds (units in line with the other timeouts, though those are ints). Users may well want to reduce this if they regularly have issues, but by default I think 2s is fine and avoids a non-responsive system in bad situations. * tests 2024-01-16T11:25:09Z Ellie Huxtable ellie@elliehuxtable.com 2024-01-16T11:25:09Z urn:sha1:a2578c4521d4615d8265744ab51a1cc4f291605e * feat: add history rebuild This adds a function that will 1. List all history from the store 2. Segment by create/delete 3. Insert all creates into the database 4. Delete all deleted This replaces the old history sync. Presently it's incomplete. There is no incremental rebuild, it can only do the entire thing at once. This is ran by `atuin store rebuild history` * fix tests * add incremental sync * add auto sync 2024-01-05T17:57:49Z Ellie Huxtable ellie@elliehuxtable.com 2024-01-05T17:57:49Z urn:sha1:7bc6ccdd70422f8fc763e2fd814a481bc79ce7b5 * feat: rework record sync for improved reliability So, to tell a story 1. We introduced the record sync, intended to be the new algorithm to sync history. 2. On top of this, I added the KV store. This was intended as a simple test of the record sync, and to see if people wanted that sort of functionality 3. History remained syncing via the old means, as while it had issues it worked more-or-less OK. And we are aware of its flaws 4. If KV syncing worked ok, history would be moved across KV syncing ran ok for 6mo or so, so I started to move across history. For several weeks, I ran a local fork of Atuin + the server that synced via records instead. The record store maintained ordering via a linked list, which was a mistake. It performed well in testing, but was really difficult to debug and reason about. So when a few small sync issues occured, they took an extremely long time to debug. This PR is huge, which I regret. It involves replacing the "parent" relationship that records once had (pointing to the previous record) with a simple index (generally referred to as idx). This also means we had to change the recordindex, which referenced "tails". Tails were the last item in the chain. Now that we use an "array" vs linked list, that logic was also replaced. And is much simpler :D Same for the queries that act on this data. ---- This isn't final - we still need to add 1. Proper server/client error handling, which has been lacking for a while 2. The actual history implementation on top This exists in a branch, just without deletions. Won't be much to add that, I just don't want to make this any larger than it already is The _only_ caveat here is that we basically lose data synced via the old record store. This is the KV data from before. It hasn't been deleted or anything, just no longer hooked up. So it's totally possible to write a migration script. I just need to do that. * update .gitignore * use correct endpoint * fix for stores with length of 1 * use create/delete enum for history store * lint, remove unneeded host_id * remove prints * add command to import old history * add enable/disable switch for record sync * add record sync to auto sync * satisfy the almighty clippy * remove file that I did not mean to commit * feedback 2023-09-18T07:39:19Z Ellie Huxtable ellie@elliehuxtable.com 2023-09-18T07:39:19Z urn:sha1:351b3e8a57c9e0143b7b6f3ed2160dcdce00225e * Add connect timeout and overall timeout * Make it configurable * Fix test * Add docs