simple-taiko-node: Prover not working with panick mode on Raiko
Describe the bug
Prover just working and suddenly stop working with error on Raiko container :
# Generating proof for block 79103 on taiko_a7
Generating input...
thread 'tokio-runtime-worker' panicked at host/src/preflight.rs:44:56:
invalid rpc url: RelativeUrlWithoutBase
Error: task 9978 panicked
# Generating proof for block 79073 on taiko_a7
Generating input...
thread 'tokio-runtime-worker' panicked at host/src/preflight.rs:44:56:
invalid rpc url: RelativeUrlWithoutBase
Error: task 9979 panicked
thread 'tokio-runtime-worker' panicked at host/src/preflight.rs:44:56:
invalid rpc url: RelativeUrlWithoutBase
# Generating proof for block 80046 on taiko_a7
Generating input...
Error: task 9980 panicked
# Generating proof for block 78974 on taiko_a7
Generating input...
Error: task 9981 panicked
thread 'tokio-runtime-worker' panicked at host/src/preflight.rs:44:56:
invalid rpc url: RelativeUrlWithoutBase
for this env TAIKO_NODE_IP=xx.xx.xx.xx I input IP only without HTTP:// not sure if related to this issue… because I only see above error after successful prove some proof
Steps to reproduce
Steps to reproduce here.
Spam policy
- I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 15 (10 by maintainers)
Adding
httpactually fixed the error for me too! Thanx!Hello I will close this issue now. Since no more issue after added
http://thanksI have had the same error after stopping the containers and re-initializing them, doing the bootstrap again and registering it again, it already catches the requests
I saw the same error message a couple of days ago when I was trying to generate an SGX proof without running setup/bootstrap first. I don’t know however why the error message is so bad though if this would be the case, you would expect a better error message for something like this so something we need to look into if that’s the case.
That’s strange… as far as I know only the null entrypoint (especially the beacon one as we call it directly) could report error like these. Let me know if it happens again. Thanks!