Squashed commit of the following: #2739
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
commit dc036e6
Author: Ganesha Upadhyaya ganeshrvce@gmail.com
Date: Sun Apr 5 17:18:36 2020 -0700
commit 66f26e8
Author: Rongjian Lan rongjian.lan@gmail.com
Date: Sun Apr 5 17:06:50 2020 -0700
commit f2524a8
Author: Rongjian Lan rongjian.lan@gmail.com
Date: Sun Apr 5 12:33:35 2020 -0700
commit 350b7a0
Author: Rongjian Lan rongjian.lan@gmail.com
Date: Sat Apr 4 23:41:19 2020 -0700
commit 8f5f287
Author: Leo Chen leo@harmony.one
Date: Sat Apr 4 19:09:38 2020 -0700
commit 05f2e20
Author: Rongjian Lan rongjian.lan@gmail.com
Date: Sat Apr 4 19:00:28 2020 -0700
commit 24a17fe
Author: Edgar Aroutiounian edgar.factorial@gmail.com
Date: Sat Apr 4 16:38:12 2020 -0700
commit 1f83ebf
Author: Minh Doan 40258599+mikedoan@users.noreply.github.com
Date: Sat Apr 4 14:38:55 2020 -0700
commit 3aa08e9
Author: Edgar Aroutiounian edgar.factorial@gmail.com
Date: Sat Apr 4 10:21:51 2020 -0700
commit 1a2c23a
Author: Edgar Aroutiounian edgar.factorial@gmail.com
Date: Fri Apr 3 17:49:24 2020 -0700
Issue
Test
Unit Test Coverage
Before:
After:
Test/Run Logs
Operational Checklist
Does this PR introduce backward-incompatible changes to the on-disk data structure and/or the over-the-wire protocol?. (If no, skip to question 8.)
YES|NO
Describe the migration plan.. For each flag epoch, describe what changes take place at the flag epoch, the anticipated interactions between upgraded/non-upgraded nodes, and any special operational considerations for the migration.
Describe how the plan was tested.
How much minimum baking period after the last flag epoch should we allow on Pangaea before promotion onto mainnet?
What are the planned flag epoch numbers and their ETAs on Pangaea?
What are the planned flag epoch numbers and their ETAs on mainnet?
Note that this must be enough to cover baking period on Pangaea.
What should node operators know about this planned change?
Does this PR introduce backward-incompatible changes NOT related to on-disk data structure and/or over-the-wire protocol? (If no, continue to question 11.)
YES|NO
Does the existing
node.sh
continue to work with this change?What should node operators know about this change?
Does this PR introduce significant changes to the operational requirements of the node software, such as >20% increase in CPU, memory, and/or disk usage?
TODO