forked from ava-labs/subnet-evm
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Sync upstream v0.6.2 #170
Closed
Closed
Sync upstream v0.6.2 #170
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* e2e: Switch warp test to use tmpnet fixture * e2e: Switch load test to use the tmpnet fixture * Add readme describing use of existing network * e2e: Remove network manager and dependency on ANR * fixup: Switch from VMName to VMID with tmpnet.Chain * fixup: Respond to review comments * fixup: Use 5 nodes for load testing * fixup: Fix shellcheck errors * cleanup artifact dirs * fixup: Update to reflect tmpnet configuration changes * fixup: go mod tidy * fixup: Use the default evm logging level for load testing * fixup: Lower the avalanchego logging levels for load testing * fixup: respond to review comments * fixup: Respond to review comments #2 * fixup: Disable unnecessary stdout logging --------- Co-authored-by: Ceyhun Onur <[email protected]>
* remove allowlist events * add signature to topic count
* sync coreth v0.13.1-rc.5 * fix tests * fix upgrade bytes test * bump subnet-evm version * sort default configs * sort default configs
* tresor, kitkat, berghain * resolve debas comments * chain config * slight refactor * resolve lumos comments
debaghtk
force-pushed
the
sync-upstream-v0.6.2
branch
from
March 14, 2024 08:46
ec46047
to
b0f895d
Compare
atvanguard
force-pushed
the
aylin
branch
2 times, most recently
from
March 15, 2024 06:19
94dfbac
to
7d58776
Compare
debaghtk
force-pushed
the
sync-upstream-v0.6.2
branch
from
March 18, 2024 06:30
9b689cb
to
d6249e5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why this should be merged
this PR is to merge subnet-evm v0.6.2. There were a bunch of resolve conflicts due to change in gossip mechanism introduced in avalanche-go which impacted coreth as well as subnet-evm
How this works
this PR only resolves the merge conflicts and keeps the original order gossip logic untouched in an attempt to simplify things. The order gossip logic is also prefixed with legacy. The order gossip logic has been updated in this PR
Context
avalanche had a downtime - link
patch released in avalanche go - link
push gossip redesign in avalanche go - link
changes coming into hubblenet from subnet-evm - link
How this was tested
tested locally
Items Pending
merge my commits in one single commit to preserve history from avax devs
decide on config of validator , non validator, peer for app gossip