Move checksum file related code to machi_csum_table #11
Loading…
Reference in a new issue
No description provided.
Delete branch "ku/cut-out-checksum-file"
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?
To follow up with trim command, I did some cleanup beforehand. More quickcheck tests could be added, and Unwritten bytes list could be wrapped under checksum table, but I hesitated to do that, to keep each pull request small.
Hi, Kota, I see three eunit test failures that aren't on master:
I like the change in organization. Also, dialyzer output is shorter than the master branch right now, hooray!
I like this change too - shouldn't the trim operation be in the file proxy to avoid concurrency problems?
@slfritchie sorry I was unaware of tests 👿
This code should be updated to strictly find out overlap of written chunks and queried chunks with a strict quickcheck. I want to make sure that any arbitrary set ofI changed my mind; csum table is just a table that returns known checksums. Unwritten bytes are managed separately.Offset, Size
could be queried from clients, which needs range queries.@mrallen1 in my brain, trim command is included in the file proxy.
ku/trim-commands is the branch coming up next with a trim command that works. Maybe I'd also have to include whole garbage collection, but I don't have it at once...
As the team grows larger, perhaps it will be a good idea to avoid big PRs? Putting the rest of the GC mechanism into later PRs is fine with me.
Hooray, all tests pass. WIP items are WIP, onward we march.