Apply Dynamic cfg to p2 & p3 cases #711
Open
Conversation
This file contains hidden or 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
Contributor
Author
|
I will add a test for the eth_client by moving money between wallets and back after a failover (how many lotus nodes, stop). |
Contributor
Then reverting back to main: 
|
Contributor
Author
|
Reiers testing: |
magik6k
reviewed
Dec 8, 2025
Collaborator
magik6k
left a comment
magik6k
left a comment
There was a problem hiding this comment.
Few minor things to address, looks really great!
Collaborator
There was a problem hiding this comment.
Definitely must do some manual testing on this
Contributor
Author
There was a problem hiding this comment.
I have no idea how, so review itests/eth_test.go
Collaborator
There was a problem hiding this comment.
This just adds a 'on new insert' handling? Any issue this is fixing?
Contributor
Author
There was a problem hiding this comment.
AI talked me into something that i should not have been. It thought some test failure was related to this AFTER trigger needing to be a BEFORE, then the test cleaned-up, but I think that line of thinking was garbage: file deleted
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.
This builds atop PR #710 (which implemented P1 items) to implement P2 & P3 items of the following punchlist.
Logic fixes: forgot 'base' changes! Atomic where better.
New component: working with Dynamic[struct{...}] required a new approach.
Misc_Included_Commits
Better testing separation by guaranteeing different databases used.
SQL:
PunchList
The remaining items are P4-5 and "No need"
Subsystems
Fees - all P2, easy, done
Addresses - all P1, hard, done
Proving - all, P4, easy
Http - no need
Market
-- MK12 - all here, P3, easy-ish, done
-- MK2, P3, done
Ingest - P1, done
Seal - No need
APIs->Chain - P2, medium-hard, done
Alerting - P3, easy, done
Batching - P2, easy, done
todo: startup fails?