Skip to content

[ENH] Implement log forking #4326

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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: sicheng/04-17-_enh_wire_up_collection_forking_for_python
Choose a base branch
from
Open

[ENH] Implement log forking #4326

wants to merge 1 commit into from

Conversation

Sicheng-Pan
Copy link
Contributor

@Sicheng-Pan Sicheng-Pan commented Apr 18, 2025 •
edited
Loading

Description of changes

Summarize the changes made by this PR.

  • Improvements & Bug fixes
    • N/A
  • New functionality
    • Implement log forking. Currently it is only implemented for legacy log service, by naively cloning the log offsets and records.

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?

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

This was referenced Apr 18, 2025
Open
Open
Open
Open
@Sicheng-Pan Graphite App
Copy link
Contributor Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

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

@Sicheng-Pan Sicheng-Pan marked this pull request as ready for review April 18, 2025 23:26
@Sicheng-Pan Sicheng-Pan force-pushed the sicheng/04-18-_enh_implement_log_forking branch from 9840862 to 5c80da6 Compare April 21, 2025 17:25
@Sicheng-Pan Sicheng-Pan force-pushed the sicheng/04-17-_enh_wire_up_collection_forking_for_python branch from a41a043 to a6aadbd Compare April 21, 2025 17:25
@Sicheng-Pan Sicheng-Pan force-pushed the sicheng/04-18-_enh_implement_log_forking branch from 5c80da6 to d47ad9a Compare April 21, 2025 17:53
@Sicheng-Pan Sicheng-Pan force-pushed the sicheng/04-17-_enh_wire_up_collection_forking_for_python branch from a6aadbd to ffdcc6c Compare April 21, 2025 17:53
@Sicheng-Pan Sicheng-Pan force-pushed the sicheng/04-18-_enh_implement_log_forking branch from d47ad9a to 67eba39 Compare April 21, 2025 18:24
@Sicheng-Pan Sicheng-Pan force-pushed the sicheng/04-17-_enh_wire_up_collection_forking_for_python branch from ffdcc6c to c9b045b Compare April 21, 2025 18:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Sicheng-Pan