-
Notifications
You must be signed in to change notification settings - Fork 32
Ability to persist CT indexes and resume from the saved index file #49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ability to persist CT indexes and resume from the saved index file #49
Conversation
messede-degod
commented
Jan 14, 2025
- Allows CT index to persisted.
- CT indexes are dumped to disk every 30 seconds
- Future sessions resume from last saved CT index.
|
Thank you for your contribution :) I appreciate it a lot. I left some comments on the code. Feel free to reply and/or fix. |
|
I've addressed all your comments, please do take a look and let me know what you think. |
|
Quick update: I did not forget about this PR, I just had a lot of life going on. Tonight I thought about this PR a bit, and some things need a few more thoughts.
I'll add these missing features asap |
This is useful in order to not start pulling each log after the first run at index 0 but still have newly discovered logs download from 0.
9d6d11f to
4bfea45
Compare
|
Sorry for the force push. Was the easiest way to get the rebase done. This PR should now be ready to be merged. Mind taking a look at the new changes and stating your opinion? Thanks a lot! |
|
looks great, but i have to admit that it looks nothing like what it started off as 😄 . |