-
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
#15: Publish multiple commands #16
base: main
Are you sure you want to change the base?
Conversation
Add test that publishes multiple types of commands (per @gknopf-aranya)
|
2dcc829
to
726b3b2
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.
Otherwise, this looks good.
- The VM now `Yield`s to the runtime when it publishes a command. The runtime is responsible for sealing the command, updating the facts database, then resuming the VM so it can process the next command. - FFI `call`s now take an immutable self.
…nState (to potentially publish more). But the context's head_id needed to be updated to the new command's ID - this is now being done. That was difficult with the context being a reference, because the new context doesn't live long enough. So the RunState now owns the context.
c971a30
to
74ded88
Compare
4c3afc1
to
cd96acd
Compare
cd96acd
to
cc082d8
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.
Looks good!
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 looks good otherwise!
@@ -1414,6 +1414,8 @@ fn should_create_clients_with_args() { | |||
assert_eq!(effects, expected); | |||
} | |||
|
|||
/// Test for <https://git.spideroak-inc.com/spideroak-inc/flow3-rs/issues/917>. |
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.
Since we're working in the public repo, this should probably point to a public issue or just refer to the issue without a URL.
Yield
s to the runtime when it publishes a command. The runtime is responsible for sealing the command, updating the facts database, then resuming the VM so it can process the next command.call
s now take an immutable self.