-
Notifications
You must be signed in to change notification settings - Fork 42
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
feat: v0.3 #173
Open
erhant
wants to merge
15
commits into
master
Choose a base branch
from
erhant/v0.3
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
feat: v0.3 #173
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
execution_time
fromTaskStats
as its depracatedexecution_ended_time
toexecution_ended_at
DriaMessage
fieldidentity
toprotocol
(because it usesprotocol().name
)node.rs
into more scoped modules for claritymakeLatest: false
option to workflowDriaMessage
struct now hassignature
field of typeString
that contains signature in hex, as well asrecovery_id
field of typeu8
that contains the recovery id for that signature. These are expected to exist, now that message authentication is not used by GossipSub / request-response so everything should be signed. The signed message is now NOT the decoded payload, but the base64 encoded payload itself.signature
fromTaskResponsePayload
as it is no longer being used, in favor ofsignature
andrecovery_id
withinDriaMessage
.new_message
function to node as a shorthand to create a signedDriaMessage
.rpc_peerids
is empty (may happen when API is down etc.).0.3.0