-
Notifications
You must be signed in to change notification settings - Fork 84
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* update query-service to ab/sqlite-support * .. * use embedded-db for devnode * uncomment marketplace builder tests * point query-service to ab/sqlite-support * migrations to update state tables columns * update comments for sql options * update justfile * enable embedded-db for devnode * fix record action query for postgres * fix record action query for postgres * try with only testing feature * rm settings.json * lint * add process-compose for sqlite, fix migration, update query-service * update query-service * pass persistence to init_node(), fix migrations, rm create_catchup_provider() * fix migration version * fix migration version * fix migration * fix migration * sequencer-sqlite * update sequencer-sqlite lockfile * fix archive name * fix archive name * update name * fix test_integration ci * fix sequencer-sqlite dockerfile * try with disabling aggregator * fix sqlite migration for merkle root columns && enable restart_tests * enable aggregator * set ESPRESSO_STATE_SIGNATURE_TOTAL_STAKE to 7 * fix merkel_root_columns && use same persistence in test_restart * set connection parameters, revert tx delay to 2s, update query-service * comment out max connections setting * set max_connections for tmp db options * add sqlite nodes in docker-compose * enable embedded-db feature for devnode * merge origin/main * nix: fix process-compose demo - Add `test` profile to sequencer-sqlite crate to avoid compiling everything twice. - Rewrite just build / native demo commands to to work with the nix dev env. * ci: compile diff-test with test profile We previously changed the flake.nix to add `./target/nix/debug` to the PATH instead of `release`. * remove docker pull from integration test * comment out cleaning up tempdir in demo-native * update hotshot-query-service * ci: don't clean up process compose storage dir * ci: upload demo native process compose logs * ci: dump logs to terminal instead - reduce timeout: the whole job takes 5 minutes on main now. - remove `process compose down`: I don't think the CI minds if we don't run it and it will save some time. * ci: dump logs of process compose services * script for running sequencer binaries based on flag * increase blocks timeout to 180s, update query-service * adjust sequencer_blocks_timeout * try with timeout=25 * revert timeout * try2 * update query-service * max connections as env * wait 5s * update query-service to 0.1.74 * logging * cargo sort * more logging * catchup from sequencer0 * catchup from seq0 * catchup from seq5 * exit if any one of the node has seen the upgrade * catchup from seq0 * remove test from archive in integration test * Upload logs as archive For me the logs are always truncated if I download them from the browser. * integration test: more debug output * use archive * set max connections to 3 for sqlite * try with 5nodes * sequencer_clients * slow statement threshold * fix state peer * use embedded-db instead of all features * lint * make seq0 state peer for seq3 * add api peers for seq3 and seq4 * try with only 1 sqlite node * remove seq3 and 4 from clients * update docker-compose * catchup from seq4, set slow_statement_threshold to 1s * pass storage-sql in the sequencer-entrypoint for sqlite * use sqlite sub dir * create sqlite sub-dir if it does not exist * create_dir_all * set default slow threshold * fix dev node test * fix dockerfile --------- Co-authored-by: sveitser <[email protected]>
- Loading branch information
1 parent
abf9a9b
commit d6a7a18
Showing
76 changed files
with
12,482 additions
and
678 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
Oops, something went wrong.