-
Notifications
You must be signed in to change notification settings - Fork 5
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
Some errors was found #24
Comments
Thank you for your detailed description of the problem. |
Hi. I used the latest version (master), ran through docker compose as in the readme example. |
Ok. First of all I'd recommend you to disable cache. You can do it by setting |
@sm1ck Do you still have any of the errors described above? |
Ok. I'll try to reproduce this error locally and think about fix it. |
@sm1ck unfortunately I can't reproduce the error locally and the error is absent on our server with indexer. I think something went wrong when cache was been enabled. It looks like your database was indexed incorrectly due to enabled cache. If decoded data is necessary for you I'd recommend you to re-index full starknet with disabled cache. If it's not important for you I think your changes will be good solution. |
Hello. I start using your indexer, so following errors was occured:
And others many. These errors can be fixed by restarting the indexer.
But one error in internal_tx.go on this line: case errors.Is(err, decode.ErrUnknownSelector): cannot be fixed by restart. It is important to note that when an error occurs, the indexer goes into an infinite loop.
Thus the indexer very often gets into infinite loops and sometimes it is fixed, sometimes it is not. Maybe there is a setting to skip problematic transactions?
The text was updated successfully, but these errors were encountered: