Lochness
b70f06a69e
feat: add exclude_patterns config key to mempalace.yaml
...
Allow projects to specify .gitignore-style patterns that the miner should
skip, without relying on .gitignore for mining control.
A new optional exclude_patterns list in mempalace.yaml is parsed by the
existing GitignoreMatcher class via a new from_patterns() classmethod —
same syntax, same semantics as .gitignore, no new dependency.
exclude_patterns:
- '*.md'
- '*.yaml'
- 'docs/' # dir-only: prunes entire tree without descending
- 'dist/'
- 'coverage/'
Key behaviour:
- Patterns follow .gitignore rules: anchoring (/pattern), dir-only
- dirs[:] pruning via GitignoreMatcher.matches(..., is_dir=True) so
excluded subtrees are never walked
- Checked after .gitignore filtering; force_include (--include-ignored)
bypasses exclude_patterns
- Pre-scanned files lists (init double-scan optimisation) are filtered too
- Backwards compatible: omitting exclude_patterns changes nothing
Changes:
- GitignoreMatcher.from_patterns(): new classmethod, same rule parser as
from_dir(), reads from a list instead of a file on disk
- scan_project(): builds one exclude_matcher before os.walk; used for
both dirs[:] pruning and per-file filtering
- _mine_impl(): applies the exclude matcher to pre-scanned files lists
when provided by the caller
- tests/test_miner.py: three new tests
test_scan_project_exclude_patterns_skips_matching_files
test_scan_project_exclude_patterns_prunes_entire_directory
test_scan_project_exclude_patterns_include_ignored_bypasses_exclusion
2026-07-07 15:29:30 -04:00
..
2026-05-03 17:43:00 +05:00
2026-06-05 21:41:21 -03:00
2026-06-28 18:01:59 -03:00
2026-06-28 18:24:58 -03:00
2026-05-27 19:19:17 +10:00
2026-05-31 10:41:09 +10:00
2026-06-11 13:09:40 +10:00
2026-06-05 21:41:21 -03:00
2026-06-28 18:01:59 -03:00
2026-06-28 18:13:06 -03:00
2026-06-05 14:52:06 -04:00
2026-05-17 23:20:01 -03:00
2026-06-19 13:44:52 +00:00
2026-04-19 10:34:11 +02:00
2026-06-01 17:19:10 -05:00
2026-07-06 09:23:35 -03:00
2026-06-28 19:44:11 -03:00
2026-06-25 23:59:02 -03:00
2026-05-23 12:05:34 -04:00
2026-06-14 15:17:01 -03:00
2026-04-25 00:39:37 -03:00
2026-05-30 12:44:47 -07:00
2026-04-24 11:13:51 +02:00
fix: expand tilde in palace_path when read from config file\n\nMempalaceConfig.palace_path correctly called os.path.expanduser() for\nenv-var paths but not for paths read from config.json. If config.json\nstores palace_path as '~/.mempalace/palace' (the default written by\ninit), the tilde was returned unexpanded.\n\nDownstream callers such as cli.py cmd_mine did call expanduser when\n--palace was passed explicitly, but fell through to MempalaceConfig()\nwhen no flag was given, inheriting the unexpanded string. Python's\nos.makedirs and chromadb.PersistentClient treat a leading tilde as a\nliteral directory name rather than the home directory, so the palace\nwas silently written to a CWD-relative path such as\nmy_project/~/.mempalace/palace.\n\nThe fix is a single os.path.expanduser() call on line 343 of\nconfig.py, mirroring the existing env-var branch on line 342. Since\nDEFAULT_PALACE_PATH is already expanded at module load (line 197),\nexpanduser on an absolute path is a no-op, so the default case is\nunaffected.\n\nSymptoms: scattered {project}/~/.mempalace/palace directories, palace\nalways appears empty after mine, search returns Collection does not\nexist, launchd-driven nightly mine writes to a different location than\ninteractive mine.\n\nCo-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>n ( #1865 )
2026-06-26 00:09:51 -03:00
2026-06-20 18:56:12 -03:00
2026-04-18 12:52:01 -03:00
2026-07-06 08:18:55 -03:00
2026-06-06 17:56:08 +05:00
2026-04-24 01:30:40 -03:00
2026-05-17 23:20:01 -03:00
2026-05-17 23:20:01 -03:00
2026-05-27 14:17:36 +10:00
2026-06-22 13:54:09 +10:00
2026-06-10 15:40:35 +10:00
2026-07-06 09:26:16 -03:00
2026-06-02 21:38:53 -03:00
2026-04-11 16:16:31 -07:00
2026-06-08 02:48:26 -03:00
2026-05-24 13:18:08 -03:00
2026-06-08 10:20:45 -03:00
2026-06-29 02:22:10 +00:00
2026-06-20 18:05:15 -03:00
2026-06-20 17:47:22 -03:00
2026-04-15 00:26:38 -07:00
2026-06-28 19:44:11 -03:00
2026-06-29 07:25:50 +00:00
2026-05-10 12:56:50 +02:00
2026-05-07 12:51:47 -03:00
2026-06-13 11:11:22 -04:00
2026-06-06 17:56:08 +05:00
2026-05-24 13:18:08 -03:00
2026-04-13 17:11:11 -07:00
2026-06-11 19:11:52 +00:00
2026-06-11 19:18:54 +00:00
2026-06-11 19:11:52 +00:00
2026-06-22 12:35:34 -03:00
2026-06-26 00:27:36 -03:00
2026-06-13 06:37:26 +00:00
2026-06-19 13:00:14 +00:00
2026-06-25 23:59:05 -03:00
2026-06-19 13:00:14 +00:00
2026-06-21 18:20:12 +05:00
2026-06-28 18:13:06 -03:00
2026-05-17 23:20:01 -03:00
2026-05-17 23:20:01 -03:00
2026-06-12 07:39:57 +00:00
2026-04-15 00:26:41 -07:00
2026-05-17 23:20:01 -03:00
2026-04-16 16:00:29 +05:00
2026-04-14 13:09:10 -07:00
2026-04-08 21:38:12 +03:00
2026-07-06 09:23:46 -03:00
2026-04-24 23:06:26 -03:00
2026-04-19 11:13:50 +03:00
2026-06-12 15:25:36 +00:00
2026-05-24 13:18:08 -03:00
2026-06-10 16:46:27 -07:00
2026-05-17 23:20:01 -03:00
2026-04-24 23:06:26 -03:00
2026-06-08 08:44:20 -03:00
2026-06-29 03:28:06 -03:00
2026-06-06 17:54:38 +05:00
2026-07-06 09:26:16 -03:00
2026-05-17 23:20:01 -03:00
2026-06-06 03:11:46 -03:00
2026-06-15 10:40:24 -03:00
2026-06-14 14:58:20 -03:00
2026-06-14 12:25:53 -03:00
2026-04-18 13:14:32 -03:00
2026-07-07 15:29:30 -04:00
2026-06-24 01:12:24 -03:00
2026-05-14 06:40:27 -03:00
2026-05-24 13:18:08 -03:00
2026-04-25 11:06:32 -07:00
2026-06-28 18:24:10 -03:00
2026-06-28 18:01:59 -03:00
2026-06-28 18:02:29 -03:00
2026-06-07 16:01:57 +08:00
2026-06-28 19:43:28 -03:00
2026-06-21 11:29:25 +00:00
2026-04-12 22:19:58 -03:00
2026-05-23 12:05:34 -04:00
2026-06-28 18:01:59 -03:00
2026-04-11 16:16:06 -07:00
2026-05-17 23:20:01 -03:00
2026-04-14 10:55:56 -07:00
2026-06-28 18:01:59 -03:00
2026-06-29 03:28:06 -03:00
2026-05-09 20:25:47 -03:00
2026-04-08 21:38:12 +03:00
2026-04-08 21:08:49 +03:00
2026-04-08 21:07:03 +03:00
2026-06-28 18:01:59 -03:00
2026-05-17 23:20:01 -03:00
2026-06-28 18:01:59 -03:00
2026-04-07 08:53:25 +01:00
2026-06-24 22:58:08 +02:00