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

[CLN] Propagate errors for block get/fork #2778

Merged
merged 2 commits into from
Sep 13, 2024
Merged

[CLN] Propagate errors for block get/fork #2778

merged 2 commits into from
Sep 13, 2024

Conversation

HammadB
Copy link
Collaborator

@HammadB HammadB commented Sep 10, 2024

Description of changes

Summarize the changes made by this PR.

  • Improvements & Bug fixes
    • These errors were not properly propagated before
  • New functionality
    • None

This PR also contains stacked PRs as part of mereg
#2780
#2793

Test plan

How are these changes tested?
Non functional changes. Existing tests. We should add tests for these cases

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

Documentation Changes

None

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)

impl ChromaError for BlockLoadError {
fn code(&self) -> ErrorCodes {
match self {
BlockLoadError::IOError(_) => ErrorCodes::Internal,
Copy link
Contributor

Choose a reason for hiding this comment

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

note to self and others: Almost all of our codebase is littered with ErrorCodes::Internal, maybe evaluate if they can convey more than that?

@@ -319,11 +354,14 @@ impl<'me, K: ArrowReadableKey<'me> + Into<KeyWrapper>, V: ArrowReadableValue<'me
let target_block_id = self.sparse_index.get_target_block_id(&search_key);
Copy link
Contributor

@sanketkedia sanketkedia Sep 11, 2024

Choose a reason for hiding this comment

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

I added a task in tracker to remove Box<dyn ChromaError> and instead add specific error types

## Description of changes

*Summarize the changes made by this PR.*
 - Improvements & Bug fixes
	 - ...
 - New functionality
	 - ...

## 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
repository](https://github.com/chroma-core/docs)?*
@HammadB HammadB enabled auto-merge (squash) September 13, 2024 17:29
@HammadB HammadB merged commit 586ae7e into main Sep 13, 2024
68 checks passed
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