Skip to content

Split ReplicationChannel into ServerChannel and ClientChannel #490

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

Merged
merged 3 commits into from
May 22, 2025

Conversation

Shatur
Copy link
Contributor

@Shatur Shatur commented May 18, 2025

For clarity. While doing so, I noticed that we register an extra client channel. While the server requires two channels, the client only needs one, the client only needs one for the acks.

Based on #488 to avoid too many conflicts.

@Shatur Shatur requested a review from UkoeHB May 18, 2025 18:14
Copy link

codecov bot commented May 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.70%. Comparing base (1e5ef0b) to head (858135d).
Report is 1 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #490      +/-   ##
==========================================
+ Coverage   81.18%   81.70%   +0.52%     
==========================================
  Files          52       52              
  Lines        2992     2996       +4     
==========================================
+ Hits         2429     2448      +19     
+ Misses        563      548      -15     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Shatur Shatur force-pushed the channels-finish branch from b187ee1 to 9cac765 Compare May 21, 2025 21:05
For clarity. While doing so, I noticed that we register an extra client
channel. While the server requires two channels, the client only needs
one.

I also removed wrong comment about receive functions.
They aren't called by backends.
@Shatur Shatur force-pushed the channels-finish branch from 9cac765 to 5eba736 Compare May 21, 2025 21:33
Base automatically changed from channels-finish to master May 21, 2025 22:33
///
/// <div class="warning">
///
/// Should only be called from the messaging backend.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why remove this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's not called by messaging backends. It's called by Replicon to read the messages. Maybe I should even make it private 🤔

Copy link
Collaborator

@UkoeHB UkoeHB May 22, 2025

Choose a reason for hiding this comment

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

Yeah make it private if it's not for the public or backend APIs.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done!

///
/// <div class="warning">
///
/// Should only be called from the messaging backend.
Copy link
Collaborator

Choose a reason for hiding this comment

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

And this

Shatur added 2 commits May 22, 2025 20:06
I had to reorganize test since integration tests
don't have access to private methods.
@Shatur Shatur requested a review from UkoeHB May 22, 2025 19:25
@Shatur Shatur merged commit 0f9b81b into master May 22, 2025
8 checks passed
@Shatur Shatur deleted the channels-split branch May 22, 2025 20:39
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