Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
feat: add send epoch, time, elapsed epoch and elapsed time for each message in mpool to UI #1523
feat: add send epoch, time, elapsed epoch and elapsed time for each message in mpool to UI #1523
Changes from 2 commits
15aa362
6ae47d6
33309fc
d0a25ec
a5a9f53
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Why pool every 4 seconds? This should be at least 15sec. given that block time is 30sec.
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.
Actually, this accounts for devnet as well. Ideally, I wanted to use build.BlockDelaySecs but that comes from MpoolQuery so I went with shortest available number. Even with 4 seconds, it should not be too aggressive as we are not polling directly to lotus node.
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.
Why do we care about this feature at all on a devnet? There should be no alerts or backlogged messages on a devnet. I'd rather we don't spam Lotus with unnecessary API calls -- all the pages start to add up at some point.
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.
I am pushing one more commit to remove all messages page and everything related to that. I will also update the polling time.
This page does not make a call to lotus API directly. It uses cached entries in mpoolManager with Boost.
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.
@nonsense I have adjusted the polling time and moving the other changes (Removing all messages) to a new PR.