-
Notifications
You must be signed in to change notification settings - Fork 6
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
EOF error in proof-server
benchmarks
#18
Comments
I believe @storojs72 ran into the same issue while working on testing Groth16. @wwared might know better but I think this had to do with the build assets for Groth16 proof generation that were overwritten by the two proof processes. |
That's a good point, but I think @winston-h-zhang already had the sp1 artifacts previously generated and put in the right directory (the log includes that "[sp1] groth16 artifacts already seem to exist ..." message), which I think prevents that issue since it won't try to regenerate the artifacts, plus he ran with My current hunch is that this could maybe have to do with the TCP connection getting closed by the OS prematurely due to the proof taking too long to finish and no traffic flowing through the connection causing a timeout/keepalive check, but I'm not really sure, because all the connections (client and both servers) are all on localhost, which I think should prevent these issues (e.g. no routers or NAT going on that could aggressively try to prune inactive connections). @winston-h-zhang can you run the following on the GCP
The default values of 7200 and 75 should not cause this issue, since the linux keepalive probing would only kick in after 7200 seconds (2 hours) of inactivity |
I have the default values of 7200 and 75. I just updated to most recent stderr: thread '<unnamed>' panicked at src/main.rs:93:10:
stderr: verify_by_hash: could not verify proof: Root hash mismatch. Expected root hash: c8e73c36e426b1cb9e732a40b51ad14c44f0397b27795ffa882748845dc525d0. Computed root hash: 59975e09cfcf6289a231e6e1dfcce0741d9796d8da19ec10ab41cb0cb5e2797d Do I have to update some artifacts? cc/ @wwared and @tchataigner |
@winston-h-zhang: I managed to replicate both the EOF issue and the Can you also try running @tchataigner is looking into the |
@winston-h-zhang: #50 should have updated the |
I updated to newest [2024-06-25T03:38:22Z WARN sphinx_core::utils] fixed log2 rows can be potentially reduced: got 394238, expected 1048576
[sp1] plonk bn254 artifacts already seem to exist at /home/winston/.sp1/circuits/plonk_bn254/v1.0.0. if you want to re-download them, delete the directory
03:44:38 DBG constraint system solver done nbConstraints=56218745 took=13270.964617
03:47:50 DBG prover done backend=plonk curve=bn254 nbConstraints=56218745 took=239528.232008
03:47:50 DBG verifier done backend=plonk curve=bn254 took=2.093459
ignoring uninitialized slice: Vars []frontend.Variable
ignoring uninitialized slice: Vars []frontend.Variable
ignoring uninitialized slice: Vars []frontend.Variable
03:47:50 DBG verifier done backend=plonk curve=bn254 took=1.4661
Error: unexpected end of file
error: bench failed, to rerun pass `--bench proof_server`
Caused by:
process didn't exit successfully: `/home/winston/example-zk-light-clients-internal/aptos/target/release/deps/proof_server-3cf9236cb2d41cf0 --bench` (exit status: 1) cc/ @wwared |
I believe this is fixed, closing |
What I did
Followed the instructions to download Groth16 artifacts. Then in
aptos/proof-server
I runError
The bench runs for ~10 minutes, and then
I believe the error is happening here: https://github.com/lurk-lab/zk-light-clients/blob/69890d34dd39ab13b15dfc2b5d8370ee08aa1637/aptos/proof-server/benches/proof_server.rs#L204
Machine
GCP
sphinx-test-1
The text was updated successfully, but these errors were encountered: