-
Notifications
You must be signed in to change notification settings - Fork 37
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
Hermes address change #1130
Hermes address change #1130
Conversation
fe99456
to
3185345
Compare
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.
out with one todo, in with another
// make sure name is registered already | ||
if current_address.read().await.0.is_none() { | ||
return Ok(()); | ||
} |
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.
This and the one for disable_zaps
has a minor race condition if the user manages to remove/switch federation before the check call has finished. Could do rechecking until .1
is true
need to see if the user is enabled or disabled with zaps to know if we need to call disable-zaps on init if they do not have a federation. other wise it keeps calling it even if the server already knows that. |
affbca6
to
ba2bf0f
Compare
No description provided.