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

Finalize actor documentation #1908

Merged
merged 7 commits into from
May 2, 2023

Conversation

didier-wenzek
Copy link
Contributor

Proposed changes

  • Sync code with doc about message boxes
  • Document actor builders
  • Document the runtime
  • Document test-helpers

Types of changes

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Improvement (general improvements like code refactoring that doesn't explicitly fix a bug or add any new functionality)
  • Documentation Update (if none of the other choices apply)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Paste Link to the issue


Checklist

  • I have read the CONTRIBUTING doc
  • I have signed the CLA (in all commits with git commit -s)
  • I ran cargo fmt as mentioned in CODING_GUIDELINES
  • I used cargo clippy as mentioned in CODING_GUIDELINES
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

Further comments

@didier-wenzek didier-wenzek temporarily deployed to Test Pull Request April 13, 2023 20:44 — with GitHub Actions Inactive
@didier-wenzek didier-wenzek marked this pull request as ready for review April 14, 2023 05:50
@github-actions
Copy link
Contributor

github-actions bot commented Apr 14, 2023

Robot Results

✅ Passed ❌ Failed ⏭️ Skipped Total Pass %
186 0 5 186 100

Passed Tests

Name ⏱️ Duration Suite
Define Child device 1 ID 0.016 s C8Y Child Alarms Rpi
Normal case when the child device does not exist on c8y cloud 3.017 s C8Y Child Alarms Rpi
Normal case when the child device already exists 1.395 s C8Y Child Alarms Rpi
Reconciliation when the new alarm message arrives, restart the mapper 3.152 s C8Y Child Alarms Rpi
Reconciliation when the alarm that is cleared 6.111 s C8Y Child Alarms Rpi
Prerequisite Parent 80.694 s Child Conf Mgmt Plugin
Prerequisite Child 0.423 s Child Conf Mgmt Plugin
Child device bootstrapping 15.876 s Child Conf Mgmt Plugin
Snapshot from device 61.369 s Child Conf Mgmt Plugin
Child device config update 62.821 s Child Conf Mgmt Plugin
Configuration types should be detected on file change (without restarting service) 123.229 s Inotify Crate
Check lock file existence in default folder 2.469 s Lock File
Check PID number in lock file 3.5060000000000002 s Lock File
Check PID number in lock file after restarting the services 3.844 s Lock File
Check starting same service twice 1.841 s Lock File
Switch off lock file creation 3.002 s Lock File
Set configuration when file exists 53.288 s Configuration Operation
Set configuration when file does not exist 6.476 s Configuration Operation
Set configuration with broken url 8.382 s Configuration Operation
Get configuration 7.676 s Configuration Operation
Get non existent configuration file 5.648 s Configuration Operation
Get non existent configuration type 5.721 s Configuration Operation
Update configuration plugin config via cloud 6.27 s Configuration Operation
Modify configuration plugin config via local filesystem modify inplace 3.052 s Configuration Operation
Modify configuration plugin config via local filesystem overwrite 3.636 s Configuration Operation
Update configuration plugin config via local filesystem copy 3.15 s Configuration Operation
Update configuration plugin config via local filesystem move (different directory) 3.067 s Configuration Operation
Update configuration plugin config via local filesystem move (same directory) 3.46 s Configuration Operation
Successful firmware operation 81.488 s Firmware Operation
Install with empty firmware name 63.418 s Firmware Operation
Prerequisite Parent 22.276 s Firmware Operation Child Device
Prerequisite Child 8.554 s Firmware Operation Child Device
Child device firmware update 6.776 s Firmware Operation Child Device
Child device firmware update with cache 6.295 s Firmware Operation Child Device
Update Inventory data via inventory.json 3.86 s Inventory Update
Retrieve a JWT tokens 126.252 s Jwt Request
Main device registration 2.864 s Device Registration
Child device registration 3.219 s Device Registration
Supports restarting the device 138.265 s Restart Device
Update tedge version from previous using Cumulocity 110.561 s Tedge Self Update
Test if all c8y services are up 119.88 s Service Monitoring
Test if all c8y services are down 137.115 s Service Monitoring
Test if all c8y services are using configured service type 132.112 s Service Monitoring
Test if all c8y services using default service type when service type configured as empty 99.235 s Service Monitoring
Check health status of tedge-mapper-c8y service on broker stop start 37.711 s Service Monitoring
Check health status of tedge-mapper-c8y service on broker restart 39.462 s Service Monitoring
Check health status of child device service 30.879 s Service Monitoring
Successful shell command with output 4.291 s Shell Operation
Check Successful shell command with literal double quotes output 3.945 s Shell Operation
Execute multiline shell command 3.714 s Shell Operation
Failed shell command 3.857 s Shell Operation
Software list should be populated during startup 51.674 s Software
Install software via Cumulocity 76.224 s Software
Software list should only show currently installed software and not candidates 58.091 s Software
Child devices support sending simple measurements 1.851 s Child Device Telemetry
Child devices support sending custom measurements 1.6760000000000002 s Child Device Telemetry
Child devices support sending custom events 1.545 s Child Device Telemetry
Child devices support sending custom events overriding the type 1.642 s Child Device Telemetry
Child devices support sending custom alarms #1699 1.791 s Child Device Telemetry
Child devices support sending inventory data via c8y topic 1.583 s Child Device Telemetry
Main device support sending inventory data via c8y topic 2.193 s Child Device Telemetry
Child device supports sending custom child device measurements directly to c8y 2.259 s Child Device Telemetry
Main device supports sending custom child device measurements directly to c8y 1.859 s Child Device Telemetry
Check retained alarms 57.433 s Raise Alarms
Validate updated data path used by tedge-agent 1.154 s Data Path Config
Validate updated data path used by c8y-firmware-plugin 12.3 s Data Path Config
Stop tedge-agent service 0.532 s Log Path Config
Customize the log path 0.149 s Log Path Config
Initialize tedge-agent 0.198 s Log Path Config
Check created folders 0.115 s Log Path Config
Remove created custom folders 0.193 s Log Path Config
Install thin-edge via apt 64.374 s Install Apt
Install latest via script (from current branch) 38.955 s Install Tedge
Install specific version via script (from current branch) 26.296 s Install Tedge
Install latest tedge via script (from main branch) 32.404 s Install Tedge
Install then uninstall latest tedge via script (from main branch) 72.893 s Install Tedge
Support starting and stopping services 55.881 s Service-Control
Supports a reconnect 73.822 s Test-Commands
Supports disconnect then connect 48.318 s Test-Commands
Update unknown setting 59.421 s Test-Commands
Update known setting 35.789 s Test-Commands
Stop c8y-configuration-plugin 60.247 s Health C8Y-Configuration-Plugin
Update the service file 0.237 s Health C8Y-Configuration-Plugin
Reload systemd files 0.445 s Health C8Y-Configuration-Plugin
Start c8y-configuration-plugin 0.154 s Health C8Y-Configuration-Plugin
Start watchdog service 10.286 s Health C8Y-Configuration-Plugin
Check PID of c8y-configuration-plugin 0.259 s Health C8Y-Configuration-Plugin
Kill the PID 0.562 s Health C8Y-Configuration-Plugin
Recheck PID of c8y-configuration-plugin 6.789 s Health C8Y-Configuration-Plugin
Compare PID change 0.003 s Health C8Y-Configuration-Plugin
Stop watchdog service 0.283 s Health C8Y-Configuration-Plugin
Remove entry from service file 0.201 s Health C8Y-Configuration-Plugin
Stop c8y-log-plugin 60.314 s Health C8Y-Log-Plugin
Update the service file 0.272 s Health C8Y-Log-Plugin
Reload systemd files 0.872 s Health C8Y-Log-Plugin
Start c8y-log-plugin 0.259 s Health C8Y-Log-Plugin
Start watchdog service 10.275 s Health C8Y-Log-Plugin
Check PID of c8y-log-plugin 0.135 s Health C8Y-Log-Plugin
Kill the PID 0.436 s Health C8Y-Log-Plugin
Recheck PID of c8y-log-plugin 6.8309999999999995 s Health C8Y-Log-Plugin
Compare PID change 0.001 s Health C8Y-Log-Plugin
Stop watchdog service 0.283 s Health C8Y-Log-Plugin
Remove entry from service file 0.274 s Health C8Y-Log-Plugin
Stop tedge-mapper 0.204 s Health Tedge Mapper C8Y
Update the service file 0.293 s Health Tedge Mapper C8Y
Reload systemd files 0.567 s Health Tedge Mapper C8Y
Start tedge-mapper 0.399 s Health Tedge Mapper C8Y
Start watchdog service 10.432 s Health Tedge Mapper C8Y
Check PID of tedge-mapper 0.095 s Health Tedge Mapper C8Y
Kill the PID 0.329 s Health Tedge Mapper C8Y
Recheck PID of tedge-mapper 6.463 s Health Tedge Mapper C8Y
Compare PID change 0.001 s Health Tedge Mapper C8Y
Stop watchdog service 0.209 s Health Tedge Mapper C8Y
Remove entry from service file 0.141 s Health Tedge Mapper C8Y
Stop tedge-agent 0.355 s Health Tedge-Agent
Update the service file 0.115 s Health Tedge-Agent
Reload systemd files 0.602 s Health Tedge-Agent
Start tedge-agent 0.332 s Health Tedge-Agent
Start watchdog service 10.659 s Health Tedge-Agent
Check PID of tedge-mapper 0.181 s Health Tedge-Agent
Kill the PID 0.479 s Health Tedge-Agent
Recheck PID of tedge-agent 6.594 s Health Tedge-Agent
Compare PID change 0.001 s Health Tedge-Agent
Stop watchdog service 0.164 s Health Tedge-Agent
Remove entry from service file 0.169 s Health Tedge-Agent
Stop tedge-mapper-az 0.192 s Health Tedge-Mapper-Az
Update the service file 0.203 s Health Tedge-Mapper-Az
Reload systemd files 0.657 s Health Tedge-Mapper-Az
Start tedge-mapper-az 0.286 s Health Tedge-Mapper-Az
Start watchdog service 10.375 s Health Tedge-Mapper-Az
Check PID of tedge-mapper-az 0.143 s Health Tedge-Mapper-Az
Kill the PID 0.3 s Health Tedge-Mapper-Az
Recheck PID of tedge-agent 6.558 s Health Tedge-Mapper-Az
Compare PID change 0.001 s Health Tedge-Mapper-Az
Stop watchdog service 0.304 s Health Tedge-Mapper-Az
Remove entry from service file 0.165 s Health Tedge-Mapper-Az
Stop tedge-mapper-collectd 0.182 s Health Tedge-Mapper-Collectd
Update the service file 0.177 s Health Tedge-Mapper-Collectd
Reload systemd files 0.423 s Health Tedge-Mapper-Collectd
Start tedge-mapper-collectd 0.203 s Health Tedge-Mapper-Collectd
Start watchdog service 10.189 s Health Tedge-Mapper-Collectd
Check PID of tedge-mapper-collectd 0.22 s Health Tedge-Mapper-Collectd
Kill the PID 0.563 s Health Tedge-Mapper-Collectd
Recheck PID of tedge-mapper-collectd 6.904 s Health Tedge-Mapper-Collectd
Compare PID change 0.001 s Health Tedge-Mapper-Collectd
Stop watchdog service 0.214 s Health Tedge-Mapper-Collectd
Remove entry from service file 0.139 s Health Tedge-Mapper-Collectd
tedge-collectd-mapper health status 6.051 s Health Tedge-Mapper-Collectd
c8y-log-plugin health status 6.64 s MQTT health endpoints
c8y-configuration-plugin health status 6.355 s MQTT health endpoints
Publish on a local insecure broker 0.797 s Basic Pub Sub
Publish on a local secure broker 6.558 s Basic Pub Sub
Publish on a local secure broker with client authentication 3.773 s Basic Pub Sub
Check remote mqtt broker #1773 5.219 s Remote Mqtt Broker
Wrong package name 0.161 s Improve Tedge Apt Plugin Error Messages
Wrong version 0.153 s Improve Tedge Apt Plugin Error Messages
Wrong type 0.446 s Improve Tedge Apt Plugin Error Messages
tedge_connect_test_positive 0.224 s Tedge Connect Test
tedge_connect_test_negative 0.787 s Tedge Connect Test
tedge_connect_test_sm_services 7.9879999999999995 s Tedge Connect Test
tedge_disconnect_test_sm_services 1.689 s Tedge Connect Test
Install thin-edge.io 27.801 s Call Tedge
call tedge -V 0.14 s Call Tedge
call tedge -h 0.131 s Call Tedge
call tedge -h -V 0.102 s Call Tedge
call tedge help 0.139 s Call Tedge
tedge config list 0.164 s Call Tedge Config List
tedge config list --all 0.15 s Call Tedge Config List
set/unset device.type 0.458 s Call Tedge Config List
set/unset device.key.path 0.53 s Call Tedge Config List
set/unset device.cert.path 0.45 s Call Tedge Config List
set/unset c8y.root.cert.path 0.516 s Call Tedge Config List
set/unset c8y.smartrest.templates 0.511 s Call Tedge Config List
set/unset az.root.cert.path 0.466 s Call Tedge Config List
set/unset az.mapper.timestamp 0.455 s Call Tedge Config List
set/unset mqtt.bind_address 0.49 s Call Tedge Config List
set/unset mqtt.port 0.337 s Call Tedge Config List
set/unset tmp.path 0.571 s Call Tedge Config List
set/unset logs.path 0.712 s Call Tedge Config List
set/unset run.path 1.035 s Call Tedge Config List
Get Put Delete 4.215 s Http File Transfer Api
Set keys should return value on stdout 0.171 s Tedge Config Get
Unset keys should not return anything on stdout and warnings on stderr 0.442 s Tedge Config Get
Invalid keys should not return anything on stdout and warnings on stderr 0.354 s Tedge Config Get
Set configuration via environment variables 1.29 s Tedge Config Get
Set unknown configuration via environment variables 0.09 s Tedge Config Get

Copy link
Member

@rina23q rina23q left a comment

Choose a reason for hiding this comment

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

LGTM

crates/core/tedge_actors/src/lib.rs Outdated Show resolved Hide resolved
}

pub struct Concurrent;
pub struct Sequential;
Copy link
Member

Choose a reason for hiding this comment

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

max_concurrency = 1 means sequential? Then, why do we need to have this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, there is something to improve here.

@@ -1,3 +1,59 @@
//! Actors that convert each input message into a sequence of output messages
Copy link
Member

Choose a reason for hiding this comment

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

I didn't know the converter, now I know it! Looks so nice!!!

@didier-wenzek didier-wenzek temporarily deployed to Test Pull Request April 17, 2023 14:06 — with GitHub Actions Inactive
@didier-wenzek didier-wenzek temporarily deployed to Test Pull Request April 27, 2023 12:15 — with GitHub Actions Inactive
/// The builder of a MessageBox must implement this trait for every message type that can be sent to it
/// The [Builder] of an [Actor](crate::Actor) must implement this trait for every message type that can be sent to it
///
/// A sink might be interested only by a subset of the messages emitted by the source.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// A sink might be interested only by a subset of the messages emitted by the source.
/// A sink might be interested only in a subset of the messages emitted by the source.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

crates/core/tedge_actors/src/builders.rs Show resolved Hide resolved
Comment on lines 189 to 190
/// The builder of an [Actor](crate::Actor) must implement this trait
/// for every message type that it can receive from its peers
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// The builder of an [Actor](crate::Actor) must implement this trait
/// for every message type that it can receive from its peers
/// The builder of an [Actor](crate::Actor) must implement this trait
/// for every message type that it can emit to its peers.
/// To receive messages from a `MessageSource<M, C>`, the peer must be a `MessageSink<M, C>`

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

@@ -153,13 +198,15 @@ pub trait MessageSource<M: Message, Config> {
}
}

/// The builder of a MessageBox must implement this trait to receive requests from the runtime
/// The builder of an [Actor](crate::Actor) must implement this trait
/// to receive [runtime requests](crate::RuntimeRequest] from the [Runtime](crate::Runtime)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// to receive [runtime requests](crate::RuntimeRequest] from the [Runtime](crate::Runtime)
/// to receive [runtime requests](crate::RuntimeRequest]s like shutdown requests from the [Runtime](crate::Runtime)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

Comment on lines 208 to 209
/// A trait to connect an actor under-construction to peer actors
/// that use the service provided by this actor.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// A trait to connect an actor under-construction to peer actors
/// that use the service provided by this actor.
/// A trait that defines that an actor provides a service by accepting `Request` messages and sending `Response` from/to its peers.
/// In order to connect to a to `ServiceProvider<Req, Res, Conf>` and avail its services, the peer must be a `ServiceConsumer<Req, Res, Conf>`.
/// The config parameter is typically used by the `ServiceConsumer` to register any message filtering criteria to the `ServiceProvider`.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Applied the suggestion

}
}

/// Build a message box ready to be used by the service actor
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// Build a message box ready to be used by the service actor
/// Build a message box ready to be used by the server actor

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

Comment on lines 37 to 38
/// Start to build a new message box for a service
pub fn new(service_name: &str, capacity: usize) -> Self {
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// Start to build a new message box for a service
pub fn new(service_name: &str, capacity: usize) -> Self {
/// Start to build a new message box for the server actor
pub fn new(server_name: &str, capacity: usize) -> Self {

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

}

/// Build a message box ready to be used by the service actor
fn build_service(self) -> ServerMessageBox<Request, Response> {
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
fn build_service(self) -> ServerMessageBox<Request, Response> {
fn build(self) -> ServerMessageBox<Request, Response> {

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Renamed build_server to avoid confusion with the Builder::build() method also implemented by this struct.

Comment on lines 114 to 115
/// An actor which builder is a `MessageSink<M, C>` can be connected to any other actor
/// which builder is a `MessageSource<M, C>` so that the sink can receive messages from that source.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
/// An actor which builder is a `MessageSink<M, C>` can be connected to any other actor
/// which builder is a `MessageSource<M, C>` so that the sink can receive messages from that source.
/// An actor whose builder is a `MessageSink<M, C>` can be connected to any other actor
/// whose builder is a `MessageSource<M, C>` so that the sink can receive messages from that source.

ChatGPT confirmed that it is grammatically okay to use "whose" in this context ;)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

//!
//! ```
//! # use crate::tedge_actors::{Actor, RuntimeError, MessageReceiver, RuntimeRequest, Sender, SimpleMessageBox};
//! # use async_trait::async_trait;
//! #
//! /// State of the calculator actor
//! /// State of the calculator actor along its message box
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
//! /// State of the calculator actor along its message box
//! /// State of the calculator actor along with its message box

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

//! /// from where input messages are received
//! /// and to which output messages are sent.
//! ///
//! /// More sophisticated actors might used specific boxes,
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
//! /// More sophisticated actors might used specific boxes,
//! /// More sophisticated actors might use specific boxes,

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

//! - Two actor builders, a `consumer: ServiceConsumer<I,O,C>` and a `producer: ServiceProvider<I,O,C>`
//! can then be connected to each other : `consumer.set_connection(producer)`
//! The connection builder traits work by pairs:
//! - A [MessageSink](crate::MessageSink) connects a [MessageSource](crate::MessageSource),
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
//! - A [MessageSink](crate::MessageSink) connects a [MessageSource](crate::MessageSource),
//! - A [MessageSink](crate::MessageSink) connects to a [MessageSource](crate::MessageSource),

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

//! The connection builder traits work by pairs:
//! - A [MessageSink](crate::MessageSink) connects a [MessageSource](crate::MessageSource),
//! so the messages sent by the latter will be received by the former.
//! - A [ServiceConsumer](crate::ServiceConsumer) connects a [ServiceProvider](crate::ServiceProvider),
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
//! - A [ServiceConsumer](crate::ServiceConsumer) connects a [ServiceProvider](crate::ServiceProvider),
//! - A [ServiceConsumer](crate::ServiceConsumer) connects to a [ServiceProvider](crate::ServiceProvider),

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

//! impl ServiceProvider<SomeInput,SomeOutput,SomeConfig> for SomeActorBuilder {
//! /// Exchange two message senders with the new peer, so each can send messages to the other
//! ///
//! /// The service registers the new consumer and ist sender (i.e. where to send response),
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
//! /// The service registers the new consumer and ist sender (i.e. where to send response),
//! /// The service registers the new consumer and its sender (i.e. where to send response),

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

//! - Any actor can send [RuntimeAction] to the runtime,
//! to spawn a new actor or to request a global shutdown of the application.
//! - An actor can subscribe to the [RuntimeEvent] published by the runtime,
//! to be notified of actor events as start, termination or crash.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
//! to be notified of actor events as start, termination or crash.
//! to be notified of actor events such as start, termination or crash.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

added

//!
//! To run an actor `A` using the [tedge_actors::Runtime](crate::Runtime) requires more than just
//! an [Actor] implementation. One needs an [actor builder](crate::builders) that implements:
//! - `Builder<A>` to let the runtime creates the actor instance,
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
//! - `Builder<A>` to let the runtime creates the actor instance,
//! - `Builder<A>` to let the runtime create the actor instance,

Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
The Calculator can no more implement the Actor and Server traits
as the former expects the message box to be owned by the actor
while the latter wraps the server with an external message box.

Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
Signed-off-by: Didier Wenzek <didier.wenzek@free.fr>
@didier-wenzek didier-wenzek temporarily deployed to Test Pull Request May 2, 2023 17:13 — with GitHub Actions Inactive
@didier-wenzek didier-wenzek merged commit 0e244cd into thin-edge:main May 2, 2023
15 checks passed
@didier-wenzek didier-wenzek deleted the actors/finalize-doc branch May 2, 2023 17:35
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.

None yet

4 participants