Skip to content
Snippets Groups Projects
Select Git revision
  • 235.backup-and-recovery.recovery
  • 260.metric-rejected-zkaps
  • compare-structured-sql-dumps
  • github/fork/tp-la/deep-traverse
  • github/fork/tp-la/real-spender
  • implicit-lease-renewal-problems
  • mach-nix
  • main default protected
  • mypy
  • real-spender
  • restricted-sqlite-strategies
  • v0.0
12 results
You can move around the graph by using the arrow keys.
Created with Raphaël 2.2.010Feb8742126Jan1412119Nov11Jan10854331Dec2217717151413147616Nov13Dec10763130Nov29232219181716151211982424227Oct2625222120191412115430Sep2724232117152Aug29Jul2723222116Jun15143218May171312618Feb171629Jan16Sep1514984323Jul29Jun231082128May262522212014131211cleanups, docstahoe upload/download with testsMerge pull request #296 from PrivateStorageio/288.cleanup-tokens-tableblackstop all the redundant voucher decodingremove unused importscleanup by redemption group counter instead of preimageMerge remote-tracking branch 'origin/main' into 288.cleanup-tokens-table_zkapauthorizer.api bad idea, does not work well, stop using ita working version of token deletionMerge pull request #293 from PrivateStorageio/235.backup-and-recoveryMerge pull request #294 from PrivateStorageio/remove-old-backup-apiadd VoucherStore.count_random_tokens and an invariant demonstrating deletiondelete the random tokenscorrect reference syntax in the specShip the schema in the package so the tests can read itblackback out nix environment changesback out removal of the old docs, will do that separatelyback out doodlesnote that replication is disabled after recoverybe specificput the writecap on the filesystemwordoelaborate on the "large enough" rational for event stream upload triggerexplain the choicepoint out why the replica must be kept freshwordobring the idea of value in alongside the idea of scarcityfinish the sample sessionremove some redundancy in the specificationfix wordotry some formatting improvementsmisc formatting improvementsadd CONFLICT result to recovery endpointannotate some http status codesmove footnotes to the endalso be explicit about event stream exclusion heremention [event-stream] handling wrt snapshot creationelaborate on event stream pruning criterion