Skip to content
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

[ENH]: Enable cluster property test for collection #2004

Merged
merged 4 commits into from
Apr 25, 2024

Conversation

nicolasgere
Copy link
Contributor

@nicolasgere nicolasgere commented Apr 11, 2024

Description of changes

Summarize the changes made by this PR.

  • Improvements & Bug fixes
    • Enable and fix property test for collection and sysdb

Copy link
Contributor Author

nicolasgere commented Apr 11, 2024

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

Join @nicolasgere and the rest of your teammates on Graphite Graphite

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

@nicolasgere nicolasgere changed the title fix property test [ENH]: Enable cluster property test for collection Apr 11, 2024
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)

@nicolasgere nicolasgere marked this pull request as ready for review April 11, 2024 22:50
@nicolasgere nicolasgere force-pushed the 04-10-enable-collection-property-test branch from 946162a to bef34ef Compare April 16, 2024 23:23
@nicolasgere nicolasgere changed the base branch from 04-10-add-offset-limit-sysdb to main April 16, 2024 23:24
@nicolasgere nicolasgere force-pushed the 04-10-enable-collection-property-test branch from 85264c5 to 1871d6e Compare April 17, 2024 18:37
@nicolasgere nicolasgere force-pushed the 04-10-enable-collection-property-test branch from 3e0299b to 1cb89f1 Compare April 25, 2024 16:36
@nicolasgere nicolasgere force-pushed the 04-10-enable-collection-property-test branch from b145387 to 0aa1214 Compare April 25, 2024 16:46
@nicolasgere nicolasgere merged commit ef24ce2 into main Apr 25, 2024
124 checks passed
This pull request was closed.
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