-
Notifications
You must be signed in to change notification settings - Fork 976
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
refactor(swamp): use celestia-app instead of the kvstore #1160
refactor(swamp): use celestia-app instead of the kvstore #1160
Conversation
the current refactor in this PR is using fwiw, I could not find yet find the reason why the cosmos-sdk's there are a few weird things about this bug:
Still not sure if we should fix this, or go with our own proprietary option that we have already started on. |
cedaa8b
to
4e77a0c
Compare
had some time to work on this, and the last bug ended up being that we needed to change a the consensus parameter There was another issue where the cosmos-sdk will override this value while collecting the gentxs if using the this genutil func. both of those are fixed and now we have block using 100ms. This did fix a few swamp tests, but I'm still seeing some errors the last test that it would be useful to get a second pair of eyes on. I'm getting either of these errors
|
@evan-forbes, I will checkout the branch and try to reproduce this |
thanks! this PR is using this branch on the application to have a working version of the new testnode on v0.7.0-rc-1 |
update: I'll try and work on this tmrw/later this week. The branch of the app that it uses needs to be slightly updated to something closer to celestiaorg/celestia-app#824. |
@evan-forbes, why do we need 10k of funded accounts in the |
@evan-forbes, so the issue with It's unclear why timeouts from Swamp's config are set incorrectly, but I am digging into |
Ok, so I could slow down block production by changing |
So I pushed fixes for the synchronization logic. Now the reconstruction tests cause issues. It succeeds, but it takes muuuch longer than it should. The reason is somewhere in PFDs and FillBlocks implementation. EDIT: The issue is in |
dc618fc
to
11543be
Compare
Ok, now the reconstruction tests work correctly, and the last one to fix are BEFP related |
Cool, so this migration uncovered a bug related to services shutdown on FraudProof arrival |
Codecov Report
@@ Coverage Diff @@
## main #1160 +/- ##
==========================================
+ Coverage 55.51% 55.61% +0.10%
==========================================
Files 161 161
Lines 9582 9582
==========================================
+ Hits 5319 5329 +10
+ Misses 3735 3727 -8
+ Partials 528 526 -2
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
9c5ac32
to
0604706
Compare
a427e14
to
5316e63
Compare
I've included one commit that fixes CI on the main to see that all the tests here reliably pass. It will remove it before merging. |
I also rebased it on the main and desperately trying to make CI green. Locally everything works fine! |
I should have time today or tmrw to continue debugging this. Will likely end up trying quite a few temporary commits to fix the CI. I can create another branch if we need to try different things in parallel. |
Hey @evan-forbes. Thanks. I will also continue debugging. I feel like I am very close |
8b9aa1e
to
18ea261
Compare
Rebased. Removing temporary commit |
87a9a06
to
d44a893
Compare
The last change here, I hope. I updated timeouts and tide up the go.mod |
…ction rate By setting the trustedHash with height 1 we make synchronization work with any block production rate. `SkipTimeoutCommit` as `false` ensures `TimeoutCommit` for longer block times is respected Also sort some imports
…eallocated accounts FillBlocks was generating much more blocks than expected. Calling of testnode.FillBlock once with block amount of accounts fixes it. Also, the amount of preallocated accounts was increased, to ensure enough blocks can be generated. Additionally, the blocktime was increased to avoid over production of blocks.
…ase it to 5 mins It's very likely that introduction of new App into Swamp brings more CPU usage subsequently increasing the time CI needs to finish tests
5529971
to
f97750f
Compare
refactors the swamp test to use celestia-app and a normal tendermint node instead of the kvstore and the rpc test tendermint node.
close #628