Skip to content

Conversation

@sanketkedia
Copy link
Contributor

@sanketkedia sanketkedia commented Jan 5, 2026

Description of changes

Summarize the changes made by this PR.

  • Improvements & Bug fixes
    • Config name was not what was set in the yaml files. Thereby resorting to defaults which is [1.0, 1.0, 1.0]
    • Instead of changing the yaml, I changed the name in code to align with all the other fields (they all don't have _config suffix)
  • New functionality
    • ...

Test plan

How are these changes tested?

  • Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Migration plan

None

Observability plan

None

Documentation Changes

None

@github-actions
Copy link

github-actions bot commented Jan 5, 2026

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

  • Can you think of any use case in which the code does not behave as intended? Have they been tested?
  • Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
  • If appropriate, are there adequate property based tests?
  • If appropriate, are there adequate unit tests?
  • Should any logging, debugging, tracing information be added or removed?
  • Are error messages user-friendly?
  • Have all documentation changes needed been made?
  • Have all non-obvious changes been commented?

System Compatibility

  • Are there any potential impacts on other parts of the system or backward compatibility?
  • Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

  • Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

Copy link
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@sanketkedia sanketkedia marked this pull request as ready for review January 5, 2026 21:50
@propel-code-bot
Copy link
Contributor

This update also ensures the distributed executor reads the renamed client_selection field so YAML-defined values populate the intended ClientSelectionConfig instead of falling back to defaults.

Affected Areas

• rust/frontend/src/executor/config.rs
• rust/frontend/src/executor/distributed.rs

This summary was automatically generated by @propel-code-bot

let retry_config = &config.retry;
let backoff = retry_config.into();
let client_selection_config = config.client_selection_config.clone();
let client_selection_config = config.client_selection.clone();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Recommended

[Maintainability] For consistency with the change you made in DistributedExecutorConfig, consider also renaming the field in the DistributedExecutor struct from client_selection_config to client_selection. This would make the naming consistent across both the config and the executor struct itself.

This would involve:

  1. Changing the field in the DistributedExecutor struct definition.
  2. Updating the local variable name and field initialization in try_from_config.
  3. Updating self.client_selection_config to self.client_selection in the count, get, knn, and search methods.
Context for Agents
For consistency with the change you made in `DistributedExecutorConfig`, consider also renaming the field in the `DistributedExecutor` struct from `client_selection_config` to `client_selection`. This would make the naming consistent across both the config and the executor struct itself.

This would involve:
1.  Changing the field in the `DistributedExecutor` struct definition.
2.  Updating the local variable name and field initialization in `try_from_config`.
3.  Updating `self.client_selection_config` to `self.client_selection` in the `count`, `get`, `knn`, and `search` methods.

File: rust/frontend/src/executor/distributed.rs
Line: 96

@sanketkedia sanketkedia merged commit da85e49 into main Jan 5, 2026
67 checks passed
chroma-droid pushed a commit that referenced this pull request Jan 5, 2026
## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
- Config name was not what was set in the yaml files. Thereby resorting
to defaults which is [1.0, 1.0, 1.0]
- Instead of changing the yaml, I changed the name in code to align with
all the other fields (they all don't have _config suffix)
- New functionality
  - ...

## Test plan
_How are these changes tested?_
- [x] Tests pass locally with `pytest` for python, `yarn test` for js,
`cargo test` for rust

## Migration plan
None

## Observability plan
None

## Documentation Changes
None
sanketkedia added a commit that referenced this pull request Jan 5, 2026
This PR cherry-picks the commit da85e49
onto release/2026-01-02. If there are unresolved conflicts, please
resolve them manually.

Co-authored-by: Sanket Kedia <kediasanket11121993@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants