Timeline storage and wiring #202
No reviewers
Labels
No Label
applications
BLOCKED
bug
design
duplicate
enhancement
fixed?
funding-needed
help wanted
infrastructure
invalid
payments
qubes
question
ready-for-implementation
refactor
spam
tapir-server
testing
tor
wontfix
No Milestone
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cwtch.im/cwtch#202
Loading…
Reference in New Issue
No description provided.
Delete Branch "dan/cwtch:storage-eb"
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?
under the hood, it holds ~16kb (as per secret box recommendation) buffer and appends messages to that and saves to file, until full, then rotates files and starts again.
this completes a vast improvement, where as before we were storing all timeslines in one giant profile file which was terrible for performance (every message could trigger a full json serialization of all timelines and the profile) and far agaisnt secret box usages of 16kb chunks
the profile store initializes and manages streamstores for timelines
some basic wiring for events is now included. things should be stored and loaded properly
Drone Build Status: failure
https://build.openprivacy.ca/cwtch.im/cwtch/394
Drone Build Status: failure
https://build.openprivacy.ca/cwtch.im/cwtch/395
Drone Build Status: success
https://build.openprivacy.ca/cwtch.im/cwtch/396
updated with unit tests testing
important breaking change for ui
there is no message sent when UI creates a group, so storage engine doesn't initialize a storage engine for the group, and when it gets messages for the group that ui created but it didn't initialize for, it seg faults...
Drone Build Status: success
https://build.openprivacy.ca/cwtch.im/cwtch/397
Awesome!