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

Add {function_name}_with_fn type functions for RemoteExt #208

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

tbraun96
Copy link
Contributor

No description provided.

self.can_use_revfs()?;
let request = NodeRequest::DeleteObject(DeleteObject {
v_conn: *self.user(),
virtual_dir: virtual_directory.into(),
security_level: Default::default(),
});
let status = self.remote().send_callback(request).await?;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Recall that our issue is that when peers are behind the same kernel, there can be false positive matches when the tickets match. We also needed to check CIDs. The send_callback and send_callback_subscription functions only check for ticket matching; send_callback only waits for the first signal to come back, whereas send_callback_subscription streams signals until a signal we want comes through. Since we now require the possibility of multiple signals, we will need to upgrade send_callback to send_callback_subscription, since in the IS, we may get a ticket match but not a CID match and will need to reroute that signal, then keep waiting. So, everywhere that we do a send_callback, we will need to upgrade it to the streaming version.

@@ -351,8 +351,8 @@ pub enum KemAlgorithm {
)]
pub enum SigAlgorithm {
#[default]
None = 0,
Falcon1024 = 1,
Falcon1024 = 0,
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Keep None as 0, just shift the default tag down to Falcon. This keeps the encoding consistent between protocol versions, so there are no surprises. Otherwise, we would need to update the protocol versions.

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