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

prb v3.2 #1580

Merged
merged 78 commits into from
May 31, 2024
Merged

prb v3.2 #1580

merged 78 commits into from
May 31, 2024

Conversation

nanometerzhu
Copy link
Contributor

No description provided.

1. processor: when use standalone sync, should not broadcast
2. sync headers db to newest in beginning
3. tempoarily disable full verify headers db since it's too slow
1. if no fast sync, para_headernum=0 does not mean next para_header is 0
2. if get_info got un-match status, MarkError
3. if fail to generate sync request, log; if more than 3 times, show on UI
1. do not retrogress block numbers on UI
2. send back error message if no attestation when register
1. update prb UI every time after update session info
2. correct block numbers on UI
@h4x3rotab
Copy link
Contributor

Great!

In some case, get_sync_request maybe faster than the chaintip info in
processor. After such sync, the workers may have newer block than
processor know. They should also be considered as "reached_chaintip",
and pending for broadcast.

Also, when processor received an empty request, and found that the
worker is "reached_chaintip", when it stops to request next sync, it
should also mark the worker pending for broadcast.
1. delete from UI after deleting a worker
2. restart after changing sync-only flag
@nanometerzhu nanometerzhu merged commit ff9d2f6 into master May 31, 2024
8 checks passed
@nanometerzhu nanometerzhu deleted the prb-v3.2 branch May 31, 2024 00:42
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.

2 participants