feat(consensus): add sync_topic to test config

[matan-starkware]

This change is 

[matan-starkware]

• feat(consensus): add metric for sync in consensus and update the simulation script #490
• refactor(consensus): rename notify_decision to decision_reached #465
• feat(consensus): simulations with the test config will use the fake consensus sync #414
• feat(consensus): add sync sender to context to broadcast on decision #413
• feat(consensus): add sync_topic to test config #412 👈
• refactor(consensus): consensus handles its network registrations on its own #409
• refactor(consensus): rename topic in config to network_topic #406
• feat(consensus): redefine consensus height metric to working height #404
• feat(consensus): add sync receiver to consensus #389 : 1 other dependent PR (#403 )
• feat(consensus): add decision fn to consensus context API #387
• refactor(consensus): move run_consensus out of lib.rs #386
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @matan-starkware and the rest of your teammates on Graphite

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.63%. Comparing base (7aaa7cc) to head (e6893b3).
Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #412      +/-   ##
==========================================
- Coverage   76.63%   76.63%   -0.01%     
==========================================
  Files         348      348              
  Lines       36298    36310      +12     
  Branches    36298    36310      +12     
==========================================
+ Hits        27816    27825       +9     
- Misses       6173     6176       +3     
  Partials     2309     2309              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[DvirYo-starkware]

Reviewed 3 of 3 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @asmaastarkware and @matan-starkware)

a discussion (no related file):
Consider using &str as the time instead of String

---

[matan-starkware]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @asmaastarkware and @DvirYo-starkware)

a discussion (no related file):

Previously, DvirYo-starkware wrote…

Consider using &str as the time instead of String

I assume time should be type? Meaning sync_topic: &str? I'm not sure how this would work, since I think the config needs to own the data. This would be ok in Default since we have a static &str, but if we actually need to use a command line flag then we would need a real lifetime for the &str.

I checked all of the papyrus configs and they always use String not &str.

---

[asmaastarkware]

Reviewed all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @DvirYo-starkware)

[asmaastarkware]

Reviewed all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved (waiting on @matan-starkware)

[matan-starkware]

Merge activity

• Aug 15, 9:10 AM EDT: @matan-starkware started a stack merge that includes this pull request via Graphite.
• Aug 15, 9:10 AM EDT: @matan-starkware merged this pull request with Graphite.