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

Print peers count. #4719

Draft
wants to merge 68 commits into
base: main
Choose a base branch
from
Draft

Conversation

Frozen
Copy link
Contributor

@Frozen Frozen commented Jul 23, 2024

Issue

Test

Unit Test Coverage

Before:

<!-- copy/paste 'go test -cover' result in the directory you made change -->

After:

<!-- copy/paste 'go test -cover' result in the directory you made change -->

Test/Run Logs

Operational Checklist

  1. 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

  2. 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.

  3. Describe how the plan was tested.

  4. How much minimum baking period after the last flag epoch should we allow on Pangaea before promotion onto mainnet?

  5. What are the planned flag epoch numbers and their ETAs on Pangaea?

  6. What are the planned flag epoch numbers and their ETAs on mainnet?

    Note that this must be enough to cover baking period on Pangaea.

  7. What should node operators know about this planned change?

  8. 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

  9. Does the existing node.sh continue to work with this change?

  10. What should node operators know about this change?

  11. 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

Frozen and others added 30 commits March 7, 2024 10:16
* add hardfork to make devnet external

* add hardfork to make devnet external
* enable leader rotation and testnet external epochs
* bring back the lost maxRate epochs

* fix epoch testnet
Update devnet internal vote power back to 90%
* Additional logs and cleanup.

* Fixed tests.
Co-authored-by: Casey Gardiner <117784577+ONECasey@users.noreply.github.com>
* disable stream sync for partner network and other networks
* remove unused tx in block manager
* add log for staged sync creation
* change bucket for stroring progress in staged stream sync, fix saveBlocks tx issue
* refactor stream sync db initialization
* set SnapshotLimit to zero for localnet
* add new logs for stream request manager
* Fix for crosslink snap db.

* Fix for possible race for new block post consensus job.
* Extracts `GetAddressForBLSKey` functionality from `Node` struct.
* Fix for panic.
* Fixed crosslink sending.

* Removed threshold 10 epochs.

* Fix.

* Fixed crosslink issue.

* Additional error log.
* change muxer flag to string to support multiple muxers
* fixed muxer usage description
@Frozen Frozen changed the title Feature/moved tests in project count peers Print peers count. Jul 23, 2024
@Frozen Frozen force-pushed the feature/moved-tests-in-project-count-peers branch from 19ff073 to edceca8 Compare July 23, 2024 16:51
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.

7 participants