-
Notifications
You must be signed in to change notification settings - Fork 626
feat(cache and trace api): Add redis cache in database and add trace api in bridge.l2backend. #228
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
Conversation
Co-authored-by: HAOYUatHZ <[email protected]>
Thx, and could you give me the link to get more detail. |
The link: http://jenkins.scroll.tech:8080/job/scroll-tests/job/scroll/2797/console |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
5823282
Co-authored-by: HAOYUatHZ [email protected]
Since the trace does not need to be stored all the time, I understand it as just putting it in the cache, so the system is strongly dependent on the cache, what is your point? Welcome to give comments :)
Changes:
GetTracesByBatchIndex
) in bridge.l2 module.