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

Use espresso-dev-node in CI #17

Open
miltonjonat opened this issue Feb 3, 2025 · 13 comments
Open

Use espresso-dev-node in CI #17

miltonjonat opened this issue Feb 3, 2025 · 13 comments
Assignees

Comments

@miltonjonat
Copy link
Collaborator

CI currently uses the live Decaf testnet for integration tests. We should use a local environment using the espresso-dev-node.

@fabiooshiro
Copy link
Collaborator

I'm running:

docker run --network=host -e ESPRESSO_SEQUENCER_L1_PROVIDER=http://localhost:8545/ -e ESPRESSO_SEQUENCER_API_PORT=1999 ghcr.io/espressosystems/espresso-sequencer/espresso-dev-node:main

I got this error:

thread 'main' panicked at /home/runner/actions-runner/_work/espresso-sequencer/espresso-sequencer/sequencer/src/api.rs:737:34:
called `Result::unwrap()` on an `Err` value: error returned from database: (code: 1) no such table: header

Full log
full-error-log.txt

Is it ok to open an issue on the Espresso repo?

@tuler
Copy link
Member

tuler commented Feb 4, 2025

ghcr.io/espressosystems/espresso-sequencer/espresso-dev-node:main

I highly suggest using a tag, not main.

no such table: header

Did you create the espresso database?

I suggest you look at https://github.com/cartesi/cli/blob/prerelease/v2-alpha/apps/cli/src/node/docker-compose-espresso.yaml

@fabiooshiro
Copy link
Collaborator

ghcr.io/espressosystems/espresso-sequencer/espresso-dev-node:main

I highly suggest using a tag, not main.

no such table: header

Did you create the espresso database?

I suggest you look at https://github.com/cartesi/cli/blob/prerelease/v2-alpha/apps/cli/src/node/docker-compose-espresso.yaml

The docker file has the postgres as a base image. In the logs we can see the migration running ok, but the code does not recognize the table.

@fabiooshiro
Copy link
Collaborator

ghcr.io/espressosystems/espresso-sequencer/espresso-dev-node:main

I highly suggest using a tag, not main.

They advised using the main tag....
It's better to follow you, what tag are you using?

@fabiooshiro
Copy link
Collaborator

@fabiooshiro
Copy link
Collaborator

YZZ7cfXToXxRTtb_mwRR leader_mnemonic="mayor-program-quota--castro-reflex-garbo" view_number=43 num_timeouts_tracked=1
2025-02-04T13:34:27.801641Z ERROR Consensus replica task{id=0 cur_view=43 last_decided_view=39}:handle_timeout: hotshot_task_impls::consensus::handlers: We did not receive evidence for view 43 in time, sending timeout vote for that view!
2025-02-04T13:34:27.807233Z ERROR Consensus replica task{id=1 cur_view=43 last_decided_view=39}:handle_timeout: hotshot_task_impls::consensus::handlers: We did not receive evidence for view 43 in time, sending timeout vote for that view!

full-logs.txt

@tuler
Copy link
Member

tuler commented Feb 4, 2025

YZZ7cfXToXxRTtb_mwRR leader_mnemonic="mayor-program-quota--castro-reflex-garbo" view_number=43 num_timeouts_tracked=1
2025-02-04T13:34:27.801641Z ERROR Consensus replica task{id=0 cur_view=43 last_decided_view=39}:handle_timeout: hotshot_task_impls::consensus::handlers: We did not receive evidence for view 43 in time, sending timeout vote for that view!
2025-02-04T13:34:27.807233Z ERROR Consensus replica task{id=1 cur_view=43 last_decided_view=39}:handle_timeout: hotshot_task_impls::consensus::handlers: We did not receive evidence for view 43 in time, sending timeout vote for that view!

I did not go deep on that error analysis.
Two URLs seems to fail:

http://localhost:22013/api/state
http://localhost:25000/marketplace-solver/auction_results/1

Are services running on those ports?

@fabiooshiro
Copy link
Collaborator

Hi @lynoferraz!
Which version are you running? And what kind of problem are you facing?

@miltonjonat
Copy link
Collaborator Author

@fabiooshiro Espresso told me that the version running on Decaf is 20241120-patch2. But they just tagged a new version some days ago, 20241120-patch4.

@lynoferraz
Copy link
Collaborator

I'm running 20241120-patch3

@fabiooshiro
Copy link
Collaborator

Now we are on the same page as @lynoferraz.

Run Anvil:

docker run --rm --name devnet -p 8545:8545 -d cartesi/rollups-node-devnet:devel

Run Espresso dev node 20241120-patch5

docker run -d --network=host -e ESPRESSO_SEQUENCER_L1_PROVIDER=http://localhost:8545/ -e ESPRESSO_SEQUENCER_API_PORT=24000 --name espresso-dev-node ghcr.io/espressosystems/espresso-sequencer/espresso-dev-node:20241120-patch5

Wait for a while and then run:

SELECT height, timestamp FROM hotshot.header ORDER BY height;

Using docker:

docker exec -i espresso-dev-node psql -U root -d root -t -c "SELECT height, timestamp FROM hotshot.header ORDER BY height;"

Missing blocks 116... 469... 599... 625... 629... 633...

header.txt

Image

@miltonjonat
Copy link
Collaborator Author

@fabiooshiro was this closed by #29?

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

No branches or pull requests

6 participants