davidrusu

the only logging done currently is some rudimentary println's DoD: - Implement some logging system - replace println's with uses of the logging system

Similar to #7 periodic rotation of master passphrase (initiated by user) will reduce the amount of potentially compromised data.

pbkdf2 was used because it was convenient (came along with ring), fix should also add kdf versioning to gitdb so that we may support multiple kdf's

I've left `range_proof_wip` untouched for now

RM2: Could not insert module, invalid module format

5

Hi Peter, This tool has been very helpful, thanks for writing it. I'm now on an rM2 and I'm seeing this error with the pre-build release binaries: ``` reMarkable: ~/...

This PR includes an initial sketch of the native messaging api Early work, but promising :)

Only build debug representations of arguments on failing tests

4

fixes #303 This cuts my prop test run-times nearly in half! Here's the new flamegraph showing nearly 70% of time spent in test, previously this was 40%.  compare to...

debug_reprs taking up 41% of test runtime

2

It seems like we're formatting the test case arguments even on passing test runs, e.g. here is the flamegraph of a test run where the test passed, but we see...