Skip to content

[DBG] Add temporary trace for filter argument #4548

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

Sicheng-Pan
Copy link
Contributor

@Sicheng-Pan Sicheng-Pan commented May 14, 2025

Description of changes

Summarize the changes made by this PR.

  • Improvements & Bug fixes
    • Add temporary traces to log filter arguments. We suspect certain filters are not handled properly.
    • Add projection error variant for clarity
  • New functionality
    • N/A

Test plan

How are these changes tested?

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

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

Copy link

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.

Copy link

Please tag your PR title with one of: [ENH | BUG | DOC | TST | BLD | PERF | TYP | CLN | CHORE]. See https://docs.trychroma.com/contributing#contributing-code-and-ideas

@Sicheng-Pan Sicheng-Pan marked this pull request as ready for review May 14, 2025 20:56
Copy link
Contributor

This PR adds temporary logging to help diagnose suspected issues with certain filters in the FTS algorithm. It also adds a more specific projection error variant for phantom records.

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

@Sicheng-Pan Sicheng-Pan merged commit 1880120 into main May 14, 2025
66 of 71 checks passed
chroma-droid pushed a commit that referenced this pull request May 14, 2025
## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
  - Add temporary traces to log filter arguments. We suspect certain filters are not handled properly.
  - Add projection error variant for clarity
- New functionality
  - N/A

## Test plan

_How are these changes tested?_

- [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust

## Documentation Changes

_Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_
Sicheng-Pan added a commit that referenced this pull request May 14, 2025
This PR cherry-picks the commit 1880120
onto release/2025-05-09. If there are unresolved conflicts, please
resolve them manually.

Co-authored-by: Macronova <[email protected]>
@Sicheng-Pan Sicheng-Pan deleted the sicheng/05-14-_dbg_add_temporary_trace_for_filter_argument branch May 28, 2025 23:26
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.

2 participants