-
Notifications
You must be signed in to change notification settings - Fork 1
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
Process fetch responses #64
base: feat/fetch-response-queue
Are you sure you want to change the base?
Conversation
…actor/fetch-improvements
…actor/improve-fetch-back-off-backon
59c92a7
to
153b705
Compare
@@ -69,6 +70,7 @@ impl PartialOrd for StoredOp { | |||
} | |||
|
|||
/// The API that a kitsune2 host must implement to provide data persistence for kitsune2. | |||
#[automock] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Auto-mocking this trait. I'll refactor the other fetch test files using automock too.
153b705
to
85f839e
Compare
4e00657
to
57b3547
Compare
85f839e
to
f338b3a
Compare
ops: Vec<op_store::MetaOp>, | ||
) -> BoxFut<'_, K2Result<()>> { | ||
Box::pin(async move { | ||
match self.op_store.process_incoming_ops(ops.clone()).await { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was wondering if there should be some protection against invalid ops or DoS attacks here. But it should probably be in the module that owns the fetch module.
a3ee21f
to
8631869
Compare
Process incoming responses to fetch requests. This completes the cycle from sending fetch request -> sending fetch response -> receiving fetch response.
A next step could be an integration test of all three parts.
depends on #63
resolves #62