Conversation
* Make `communication_for` exit when we end a round * Fix compilation
@shawntabrizi would be good to get tests in for funds that span multiple auctions and funds that begin prior to any auction. |
Yes, I can do this asap. |
This makes sense to me, but now I struggle to understand how best to teach a concept like this to new runtime developers. Will follow up with you offline.
You are right it does not work over multiple auctions. The updated logic you introduced makes sense to me, and handles this situation well. I will write tests to check it. |
@gavofyork a crowdfund with an end date longer than a single auction seems to work with the last test I added. However, from one action end to the next auction, there must be a contribution to the fund in order for it to be added to Is this okay? |
The decision on when/whether to place an item in |
ok - i'm reasonably happy with it. |
@shawntabrizi once you're happy with it, give it a final review and we can merge. |
Note: Right now only |
…aritytech#315) * Block announce validation should use the correct `Validation` result The error variant is just for internal errors and we need to return `Failure` always when the other node send us an invalid statement. * Update network/src/lib.rs Co-authored-by: Sergei Shulepov <sergei@parity.io> Co-authored-by: Sergei Shulepov <sergei@parity.io>
No description provided.