Skip to content

2.5.1 — A neuron missing from the index is indexed; the guard ignores bare flags

Choose a tag to compare

@Octonove Octonove released this 20 Sep 02:28
· 118 commits to master since this release

Two things found by using 2.5.0 on the brain it was built from, the same night.

A neuron missing from the index is indexed, whatever its date says. The catch-up added in 2.5.0 goes by file dates. But an index file written by a process that never saw a neuron is newer than that neuron and does not contain it — no date would ever bring it back. That is what a 2.4 server still running does to a brain compacted under it: its next persist writes its own in-memory index over the new one. Every neuron has at least a header chunk, so "no chunks at all" means "not indexed", and the catch-up now indexes it.

The guard ignores bare flags. curl -s and grep -n are not actions; a flag only makes a key where it changes what the program does to your files (rm -rf, node --check, python -m…).

UNABLE_TO_VERIFY_LEAF_SIGNATURE when running npx crbro-memory? Not CRBRO and not npm: an antivirus web shield (Avast, in the case that found it) re-signing HTTPS with a root your OS trusts and Node does not. setx NODE_USE_SYSTEM_CA 1 (Windows) or export NODE_USE_SYSTEM_CA=1 makes Node trust the system store; it turns no check off. The README has the details.

420 tests. Blind retrieval benchmark unchanged.