taikoxyz / taiko-geth

An L2 execution engine implementation for the Taiko protocol. 🚚
https://geth.taiko.xyz
GNU Lesser General Public License v3.0
215 stars 146 forks source link

bug: error: unexpected argument '--taiko' found #206

Closed dantaik closed 5 months ago

dantaik commented 5 months ago

This bug was reported by bigdreams006 and migrated from https://github.com/taikoxyz/taiko-mono/issues/16482.

Describe the bug

Description of the bug here. node refusing to load node

Steps to reproduce

Steps to reproduce here. chech and update syntax

Spam policy

This is becoming a rule now. Everytime the node is syncing, it syncs to a point, where it says that it has fully synced, and then it stays there. It doesn't sync any more blocks, taiko_client_driver-1 | ERROR[03-19|09:01:15.688] Block batch iterator callback error error="failed to check whether iterator.current cursor has been reorged: context deadline exceeded" many get this error constantly It used to dissapear after a restart, and now it doesnt Or is the docker method not supported anymore?

RogerLamTd commented 5 months ago

@bigdreams006 could you verify that you are using an updated version of simple-taiko-node? Also, which image d8eebc89ac3d is referring to?

RogerLamTd commented 5 months ago

Was unable to reproduce the issue, I think it has to do with using an outdated version of simple-taiko-node; closing for now, if the issue crops up again feel free to reopen.

bigdreams006 commented 5 months ago

Alright thank you On Thu, 4 Apr 2024 at 02:00, Roger @.***> wrote:

Was unable to reproduce the issue, I think it has to do with using an outdated version of simple-taiko-node; closing for now, if the issue crops up again feel free to reopen.

— Reply to this email directly, view it on GitHub https://github.com/taikoxyz/taiko-geth/issues/206#issuecomment-2035892586, or unsubscribe https://github.com/notifications/unsubscribe-auth/A7MXNJBOGS2KS6OS7FPBYPDY3SQ4LAVCNFSM6AAAAABFREYDDCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVHA4TENJYGY . You are receiving this because you were mentioned.Message ID: @.***>