-
Notifications
You must be signed in to change notification settings - Fork 28
port iota integration into xaynet os repo #636
base: master
Are you sure you want to change the base?
Conversation
a4f1389
to
6224427
Compare
Codecov Report
@@ Coverage Diff @@
## master #636 +/- ##
==========================================
- Coverage 61.51% 61.00% -0.52%
==========================================
Files 102 102
Lines 4563 4559 -4
==========================================
- Hits 2807 2781 -26
- Misses 1756 1778 +22
Continue to review full report at Codecov.
|
6224427
to
c796cfd
Compare
/deploy COORDINATOR_FEATURES=metrics,iota |
1ef0cca
to
4c5beb5
Compare
/deploy COORDINATOR_FEATURES=metrics,iota |
22c351c
to
09a43f4
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.
Thanks a lot! LGTM, but perhaps seek the approval of someone else too?
} | ||
|
||
#[async_trait] | ||
pub trait Storage: CoordinatorStorage + ModelStorage + TrustAnchor { |
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.
Very neat :) Funny how such an innocent looking trait leads to such improvement through the entire state machine. Why is the is_ready
needed though? CoordinatorStorage, ModelStorage and TrustAnchor all have an is_ready
method already.
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.
Very neat :) Funny how such an innocent looking trait leads to such improvement through the entire state machine.
Yeah I agree😊. It is awesome to see that it work this way without dynamic dispatch.
The is_ready
method combines the is_ready
methods of CoordinatorStorage
, ModelStorage
and TrustAnchor
and is called in the state machine error phase.
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.
@little-dude !! are you dynamically dispatching meals to people doorsteps already?
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 great. I don't have much domain knowledge around the iota parts, so can't say much there. perhaps more docstrings there (particularly for pub
functions) would be helpful, but you don't need to do it straight away. Also I wasn't able to see your lovely module documentation when i did cargo doc
, maybe just a problem with my setup, or was this intentional? I agree with @little-dude 's comment that the changes to the state machine make it simpler and more extensible, which is great.
@@ -139,22 +135,20 @@ where | |||
/// | |||
/// This contains the state-dependent `private` state and the state-independent `shared` state | |||
/// which is shared across state transitions. | |||
pub struct PhaseState<S, C, M> | |||
pub struct PhaseState<State, Store> |
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.
personally for consistency i would say <S, T>
and add a comment on what they represent, but I'm ok with this too if you prefer it.
/// XAYNET_TRUST_ANCHOR__IOTA__NETWORK=Devnet | ||
/// ``` | ||
pub network: Network, | ||
/// The seed of the author. Allowed characters are: `A-Z` and `9`. |
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.
A-Z and just 9? that's quirky...
3c89d29
to
f96b127
Compare
e54b430
to
93bb352
Compare
Co-authored-by: kwok <[email protected]>
Co-authored-by: kwok <[email protected]>
Co-authored-by: kwok <[email protected]>
Co-authored-by: kwok <[email protected]>
Co-authored-by: kwok <[email protected]>
Co-authored-by: kwok <[email protected]>
Co-authored-by: kwok <[email protected]>
Co-authored-by: kwok <[email protected]>
8fb5d79
to
8feec80
Compare
No description provided.