Repository navigation
fix(indexing): wire PARALLEL_WORKERS config to indexing concurrency - #1376
Shashankss1205 merged 1 commit into
Conversation
|
@Sanjays2402 is attempting to deploy a commit to the shashankss1205's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
👋 Thanks for contributing to CodeGraphContext! Since this PR was opened, |
22211b0 to
06709c0
Compare
|
Rebased onto current main, now conflict-free (06709c0). The conflicts were all in files this PR never touched, so I reapplied the two real changes on top of main rather than replaying the old branch history:
|
Shashankss1205
left a comment
Shashankss1205
left a comment
There was a problem hiding this comment.
Reviewed and verified locally: merged onto current main, new config tests green. Thanks for wiring PARALLEL_WORKERS through (fixes #1340).
github-project-automation
Bot
moved this from Backlog tasks
to Done
in CGC Progress Board
|
Thanks @Sanjays2402 for this contribution — merged! 🎉 This closes a real gap (#1340). We'd love to have you contribute back again — feel free to pick up another open issue! |
Shashankss1205
added
gssoc:approved
2 participants
Fixes #1340.
PARALLEL_WORKERSis defined and validated inconfig_manager.py(default 4, range 1-32, "Number of parallel indexing workers"), butrun_tree_sitter_index_asynchardcodedconcurrency_limit = 10, so setting it had no effect on indexing.This reads the value through a small
get_parallel_workers()helper that falls back to the previous limit of 10 when the config is unset or not a usable positive integer, so a missing or malformed value never breaks indexing.Tests:
tests/unit/tools/test_pipeline_parallel_workers.pycovers valid values and each fallback case (unset, empty, non-numeric, zero, negative) — 8 passed; the module fails to import onmainwithout the change.