7076e4b283* perf(daemon): coalesce metadata writes * refactor(metadata): split repository ops * fix(metadata): harden repository invariants * feat: test coverage and continued refactor work in metadata code * fix(graph): handle path-like explore queries - prefer file path symbol lookup for graph explore\n- sanitize alias FTS queries before MATCH * fix(daemon): quiesce shutdown background work - Interrupt pending DB acquires before worker shutdown - Wait for tracked background coroutines and timers to drain * fix(daemon): cancel repair work on shutdown Blocked embed and post-ingest queues could keep salvage and\nstuck-doc repair alive during shutdown. Consume cancellation in\nrepair retry loops and lock the integrated ServiceManager path\nwith regressions so shutdown fails fast instead of drifting. * perf(metadata): reduce sqlite lock contention * perf(metadata): flatten batch content retries * fix(daemon): align shutdown wait budgets A low shutdown timeout override could expire before ServiceManager\nfinished its 5s+30s WorkCoordinator join path. Share the join\nbudget constants, clamp graceful lifecycle waits to that floor,\nand lock the behavior with a daemon regression. * perf(metadata): bound feedback write waits * perf(metadata): prep batch content before tx * fix(daemon): honor no-embeddings tasks Post-ingest queue tasks dropped the per-task noEmbeddings flag,\nso focused extraction tests still emitted embed jobs and Windows\nCI exercised extra async paths. Preserve the flag through the bus,\nskip embed dispatch when requested, and wake the extraction poller\nimmediately after successful queueing. * perf(daemon): batch fallback metadata writes * feat(perf,docs): optimizations for metadata writes, prompt updates and test improvements * perf(metadata): flatten insert retries * fix(metadata): clear CI portability blockers Use the shared portable ScopedEnvVar in metadata search-query helper tests, add mutators for test reuse, and normalize Statement::bindAll integral dispatch so long long arguments bind consistently across platforms. Add focused regression coverage for the bindAll long long path. * perf(metadata): batch writes and steady bench * fix(daemon): skip inactive post-ingest pollers * perf(metadata): tighten tag and path caches * perf(metadata): cache small batch upserts * fix(daemon): harden embedded host teardown * feat(docs): updating docs policies and language * perf(metadata): tune doc update retries * perf(metadata): bound download retries * perf(metadata): bound download metadata waits * bench(metadata): scope post-ingest content path * fix(daemon): export embedded test hooks * fix(daemon): harden test helper linkage * fix(build): add missing standard includes
1.6 KiB
Code of Conduct
YAMS is committed to being a respectful, welcoming, and constructive community.
We want contributors, users, and maintainers to feel comfortable asking questions, sharing ideas, reporting problems, and participating in good-faith technical disagreement.
Our standards
Examples of behavior that help create a positive environment include:
- being respectful, patient, and curious
- assuming good intent while still giving clear feedback
- welcoming newcomers and helping them get oriented
- accepting constructive criticism gracefully
- focusing discussion on the work, not the person
Examples of unacceptable behavior include:
- harassment, discrimination, or personal attacks
- insulting or demeaning language
- deliberate intimidation or exclusion
- publishing private information without permission
- sustained disruptive or bad-faith behavior
Scope
This Code of Conduct applies to project spaces and to public or private interactions that are directly connected to the project.
Reporting
If you experience or witness unacceptable behavior, please contact the maintainers at:
admin@yamsmemory.ai
Reports will be reviewed as promptly and discreetly as possible. We will make a good-faith effort to protect reporter privacy and to respond fairly.
Enforcement
Maintainers may remove, edit, or reject comments, commits, code, issues, or other contributions that violate this Code of Conduct. Repeated or severe violations may lead to temporary or permanent exclusion from project spaces.
Attribution
This document is adapted from the Contributor Covenant v2.1.