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

fix(segments): Calculate absolute_offset and Position properly #593

Closed
wants to merge 8 commits into from

Conversation

h3nill
Copy link

@h3nill h3nill commented Mar 22, 2023

Type of change

  • Bug fix (non-breaking change which fixes an issue)

Checklist:

  • Formatted with cargo fmt

@stale stale bot added stale Not moving forward; blocked and removed stale Not moving forward; blocked labels Apr 11, 2023
Comment on lines +277 to +287
if self.active_segment().size() < self.max_segment_size as u64 {
Ok(Position::Done {
start,
end: (cursor.0, absolute_offset),
})
} else {
Ok(Position::Done {
start,
end: (cursor.0 + 1, absolute_offset),
})
}
Copy link
Author

Choose a reason for hiding this comment

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

if active_segment().size() >= self.max_segment_size on the next append to commitlog we will call apply_retention and new segment would be created.

@stale stale bot added the stale Not moving forward; blocked label May 8, 2023
@swanandx
Copy link
Member

@henil is the bug fix still required? most of the changes already existed in main branch, I resolved the merge conflicts, can you have a look at current state of PR and lmk if the changes are still required?

if not required, can we close the PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale Not moving forward; blocked
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants