Skip to content

Conversation

@Sicheng-Pan
Copy link
Contributor

@Sicheng-Pan Sicheng-Pan commented Jun 11, 2025

Description of changes

Summarize the changes made by this PR.

  • Improvements & Bug fixes
    • Add instrumentation for s3 copy, delete, and rename (which is copy + delete)
  • 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
Contributor Author

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

@github-actions
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)

@Sicheng-Pan Sicheng-Pan marked this pull request as ready for review June 11, 2025 00:16
@Sicheng-Pan Sicheng-Pan requested a review from rescrv June 11, 2025 00:16
@propel-code-bot
Copy link
Contributor

This PR adds #[tracing::instrument(skip(self))] annotations to the S3Storage struct's copy, delete, and rename async methods. These changes enable more detailed tracing and observability for S3 operations, allowing developers to capture method-level telemetry when copy, delete, or rename (copy + delete) actions are performed on S3 objects. No functional logic or API signatures are changed.

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

@HammadB HammadB merged commit 6901579 into main Jun 11, 2025
59 checks passed
@Sicheng-Pan Sicheng-Pan deleted the sicheng/06-10-_enh_instrument_s3_copy_and_delete branch June 11, 2025 18:01
Inventrohyder pushed a commit to Inventrohyder/chroma that referenced this pull request Aug 5, 2025
## Description of changes

_Summarize the changes made by this PR._

- Improvements & Bug fixes
- Add instrumentation for s3 copy, delete, and rename (which is copy +
delete)
- 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)?_

Co-authored-by: sicheng <[email protected]>
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.

4 participants