Conversation
…visory Two blocking CI jobs were red on main after #3 merged: test (ubuntu + macOS): the previous HOME/TMP override does NOT isolate the per-user brain on Linux — the `home` crate resolves the home dir via getpwuid (/etc/passwd), ignoring $HOME. So CI kept resolving ~/.kimetsu and parallel test binaries contended on ~/.kimetsu/project.lock ("project writer lock is already held"). Fix: set KIMETSU_USER_BRAIN=0 for the test job (the documented toggle); every test then uses only its own per-test project root. Verified locally: full workspace all-green (14 test blocks, 0 failures). cargo-audit: RUSTSEC-2024-0384 (`instant` unmaintained) — a transitive, embeddings-only dep (fastembed -> sled 0.34 -> parking_lot 0.11 -> instant). Not an exploitable vuln and no upgrade path until fastembed bumps sled. Ignored with a documented reason; re-evaluate on fastembed update. clippy + cargo-deny remain advisory (continue-on-error) pending a cleanup PR. After this, the blocking checks (fmt, test, audit) are green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The audit-ignore in the prior commit named the wrong advisory. cargo-audit reports zero vulnerabilities; the only finding is an informational "unmaintained" notice for `paste` (RUSTSEC-2024-0436) — a transitive proc-macro dep via fastembed -> tokenizers -> macro_rules_attribute -> paste, with no first-party use and no drop-in replacement. Ignore the correct id so the audit job is green on the informational notice. Also gitignore **/.fastembed_cache/ — the BGE model cache fastembed writes under the crate dir on first embed call during tests/runs. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The 'test' job failed on ubuntu + macos at project.rs with
'noop embedder must not generate conflicts; got 1 rows' (97 passed,
1 failed). Root cause is Cargo feature unification, not the lock
contention the old ci.yml comment claimed: 'cargo test --workspace'
unifies features across the graph, and kimetsu-cli enables
'kimetsu-brain/embeddings' by default. So kimetsu-brain's own test
binary builds WITH the real fastembed embedder, never the noop the
test assumed. The two near-duplicate texts ('thiserror' vs 'anyhow'
error types) then exceed the 0.82 cosine threshold and a conflict
row is recorded -> assertion fails.
Make the plumbing test deterministic under any embedder: use two
unrelated-topic memories (cosine well under threshold for a real
embedder, trivially zero for the noop), rename to
add_memory_distinct_texts_no_conflicts, and rewrite the doc/inline
comments. Fix the misleading ci.yml comment to describe feature
unification + the KIMETSU_USER_BRAIN=0 / --test-threads=1 hygiene.
Verified: cargo test -p kimetsu-brain --features embeddings ->
98 passed, 0 failed (the exact CI build condition).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
RodCor
pushed a commit
that referenced
this pull request
Jul 3, 2026
…abot #5) Next.js transitively pins postcss 8.4.31 (< 8.5.10, vulnerable to XSS via unescaped </style> in stringify output). An npm override forces the whole tree onto ^8.5.15. npm audit reports zero vulnerabilities; site builds green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.