java-codebase-rag 0.9.7__py3-none-any.whl → 0.10.0__py3-none-any.whl

java_codebase_rag/index/java_index_flow_lancedb.py

@@ -84,19 +84,16 @@ else:
 
 splitter = RecursiveSplitter()
 
-# cocoindex 1.0.7 schedules ``table.optimize()`` (a LanceDB Rewrite/compaction
-# transaction) as a *background* asyncio task after every
-# ``num_transactions_before_optimize`` mutation batches (default 50). That
-# background Rewrite races the concurrent ``table.delete()`` (Delete)
-# transactions emitted by later batches, and LanceDB does not allow a Rewrite
-# to commit concurrently with a Delete (upstream lancedb#1504), which floods
-# stderr with "Retryable commit conflict ... preempted by concurrent
-# transaction Delete". Setting this effectively to infinity disables the
-# in-flight background optimize; the serialized post-flow optimize in
-# ``lance_optimize.optimize_lance_tables`` then compacts the table with no
-# concurrent writers. ``optimize()`` is pure maintenance (compact/prune/index);
-# upsert/delete correctness via merge_insert does not depend on it.
-_NUM_TXN_BEFORE_OPTIMIZE = 10**12
+# LanceDB table optimization: cocoindex >=1.0.15 runs ``table.optimize()``
+# INLINE during merge_insert commits, gated by stats (only when small fragments
+# accumulate — see _RowHandler._maybe_optimize / _evaluate_optimize). That
+# replaces the old 1.0.7 *background* asyncio optimize that raced concurrent
+# Deletes (lancedb#1504 commit conflicts) and which we used to disable via
+# ``num_transactions_before_optimize`` (kwarg removed in 1.0.16). Being inline,
+# it no longer races anything. ``lance_optimize.optimize_lance_tables`` still
+# runs a final serialized compaction post-flow. ``optimize()`` is pure
+# maintenance (compact/prune/index); upsert/delete correctness via merge_insert
+# does not depend on it.
 
 
 # --- Vectors-phase progress emission (JCIRAG_PROGRESS kind=vectors) -----------
@@ -618,7 +615,6 @@ async def app_main() -> None:
         LANCE_DB,
         LANCE_TABLE_NAMES[0],
         java_schema,
-        num_transactions_before_optimize=_NUM_TXN_BEFORE_OPTIMIZE,
     )
 
     sql_schema = await lancedb.TableSchema.from_class(
@@ -629,7 +625,6 @@ async def app_main() -> None:
         LANCE_DB,
         LANCE_TABLE_NAMES[1],
         sql_schema,
-        num_transactions_before_optimize=_NUM_TXN_BEFORE_OPTIMIZE,
     )
 
     yaml_schema = await lancedb.TableSchema.from_class(
@@ -640,7 +635,6 @@ async def app_main() -> None:
         LANCE_DB,
         LANCE_TABLE_NAMES[2],
         yaml_schema,
-        num_transactions_before_optimize=_NUM_TXN_BEFORE_OPTIMIZE,
     )
 
     project_root = coco.use_context(PROJECT_ROOT)

java_codebase_rag/install_data/agents/explorer-rag-cli.md

@@ -95,9 +95,11 @@ The Decision Framework above tells you *which* command; reach for `--help` only
 
 **Prerequisite.** `jrag` needs an index — unindexed, every command exits 2 (`jrag status` checks; the file-system tools work without one).
 
+**Tip.** Run `jrag watch` once per session for fast, fresh queries — it keeps the index fresh on file change and serves every read command warm (no per-call model load). Optional; with no daemon running, all reads take the cold path byte-identically.
+
 **Resolve-first contract.** Every `<query>` command resolves the identifier first, then maps `one` / `many` / `none` onto one envelope: `one` → run; `many` → return candidates and stop, **no silent guess across distinct types** (a class sharing its simple name with its own constructor still resolves to the type — narrow with `--kind` / `--role` / `--fqn-contains` / `--service`); `none` → `status: not_found` (exit 0), fall back to `search` or `Grep`. Pass names (FQN / simple name / route path / topic) or prior `sym:`/`route:`/`client:`/`producer:` ids — never raw node ids. `--kind` is a true resolve input; `--role` / `--java-kind` / `--fqn-contains` post-filter client-side.
 
-**Output.** Default is compact text; `--format json` emits `{status, nodes, edges, candidates, truncated, agent_next_actions, file_location}` (empty fields dropped; `file_location` is a `filename:line` string; `agent_next_actions` suggests ≤5 next commands). `truncated` pages via `--limit` / `--offset` (`find` / `search` only).
+**Output.** Default is compact text; `--format json` emits `{status, nodes, edges, candidates, truncated, agent_next_actions, file_location}` (empty fields dropped; `file_location` is a `filename:line` string; `agent_next_actions` suggests ≤5 next commands). `truncated` pages via `--limit` / `--offset` (`find` / `search` only). Output-shaping flags (every query / listing / traversal command — not `status` / `microservices` / `vocab-index`, which reject them): `--count` prints just the result count (bare int in text; `{"status","count"}` in json), `--exists` prints `true`/`false` (`{"status","exists"}` in json) and exits 0 on a hit / 2 on a miss (scriptable existence gate — `find X --exists`, `inspect X --exists`), `--fields fqn,role,…` projects each node to a comma-separated field allowlist (overrides `--detail`; ignored with `--count`/`--exists`; primarily a `--format json` lever).
 
 **Edge semantics `--help` doesn't spell out.** `callers` / `callees` = `CALLS` in/out (on a controller/entry-point type, `callers` also lists the routes its methods `EXPOSE`). `impact` = bounded fan-in over `INJECTS` / `IMPLEMENTS` / `EXTENDS` (default depth 2; raise with `--depth`). `flow <route>` follows `EXPOSES` → `HTTP_CALLS` / `ASYNC_CALLS` → `CALLS`. `connection <microservice>` = inbound/outbound cross-service seams (its positional is a literal service name, not a query). Per-command edge mappings and the rest of the flag surface live in each command's `--help`.
 

java_codebase_rag/install_data/skills/explore-codebase-cli/SKILL.md

@@ -94,9 +94,11 @@ The Decision Framework above tells you *which* command; reach for `--help` only
 
 **Prerequisite.** `jrag` needs an index — unindexed, every command exits 2 (`jrag status` checks; the file-system tools work without one).
 
+**Tip.** Run `jrag watch` once per session for fast, fresh queries — it keeps the index fresh on file change and serves every read command warm (no per-call model load). Optional; with no daemon running, all reads take the cold path byte-identically.
+
 **Resolve-first contract.** Every `<query>` command resolves the identifier first, then maps `one` / `many` / `none` onto one envelope: `one` → run; `many` → return candidates and stop, **no silent guess across distinct types** (a class sharing its simple name with its own constructor still resolves to the type — narrow with `--kind` / `--role` / `--fqn-contains` / `--service`); `none` → `status: not_found` (exit 0), fall back to `search` or `Grep`. Pass names (FQN / simple name / route path / topic) or prior `sym:`/`route:`/`client:`/`producer:` ids — never raw node ids. `--kind` is a true resolve input; `--role` / `--java-kind` / `--fqn-contains` post-filter client-side.
 
-**Output.** Default is compact text; `--format json` emits `{status, nodes, edges, candidates, truncated, agent_next_actions, file_location}` (empty fields dropped; `file_location` is a `filename:line` string; `agent_next_actions` suggests ≤5 next commands). `truncated` pages via `--limit` / `--offset` (`find` / `search` only).
+**Output.** Default is compact text; `--format json` emits `{status, nodes, edges, candidates, truncated, agent_next_actions, file_location}` (empty fields dropped; `file_location` is a `filename:line` string; `agent_next_actions` suggests ≤5 next commands). `truncated` pages via `--limit` / `--offset` (`find` / `search` only). Output-shaping flags (every query / listing / traversal command — not `status` / `microservices` / `vocab-index`, which reject them): `--count` prints just the result count (bare int in text; `{"status","count"}` in json), `--exists` prints `true`/`false` (`{"status","exists"}` in json) and exits 0 on a hit / 2 on a miss (scriptable existence gate — `find X --exists`, `inspect X --exists`), `--fields fqn,role,…` projects each node to a comma-separated field allowlist (overrides `--detail`; ignored with `--count`/`--exists`; primarily a `--format json` lever).
 
 **Edge semantics `--help` doesn't spell out.** `callers` / `callees` = `CALLS` in/out (on a controller/entry-point type, `callers` also lists the routes its methods `EXPOSE`). `impact` = bounded fan-in over `INJECTS` / `IMPLEMENTS` / `EXTENDS` (default depth 2; raise with `--depth`). `flow <route>` follows `EXPOSES` → `HTTP_CALLS` / `ASYNC_CALLS` → `CALLS`. `connection <microservice>` = inbound/outbound cross-service seams (its positional is a literal service name, not a query). Per-command edge mappings and the rest of the flag surface live in each command's `--help`.