Scitz0
commented
3 years ago Hi,
Thanks for the suggestions.
- Consider including the next epoch blocks in the summary view once the leaderlogs are calculated for the next epoch. Currently you have to manually go in and type in the next epoch number to check for blocks assigned.
The summary page is not meant to give details like this. Each page has its purpose, summary to give an overview of block creation over time. Details page to get all details for a specific epoch and gLiveView for live tracking of next block.
2. When checking a specific epoch, consider making it easier to check the latest epoch that is calculated. The only time I use this feature is to check a future epoch, so the default isn't usually helpful.
Its design as I think most will use the details page, knowing the exact details for what blocks have been created and not should in my book default to current.
3. When checking a future epoch, putting in a big number like "34356" simply says "No blocks in epoch 34356" - this should probably give an error or some other notice if the epoch requested hasn't been calculated rather than reporting zero blocks. The situation where this is important is if I try to check for blocks in a future epoch that isn't calculated yet (like if I try to check before the current epoch is 2/3 of the way done). I may think that I have no blocks when in reality the leading slots just haven't been calculated yet.
This could be improved a bit to give better feedback. Adding a note for the future.
Some feature requests for the "Blocks" display when using the cncli-leaderlog-service:
1) Consider including the next epoch blocks in the summary view once the leaderlogs are calculated for the next epoch. Currently you have to manually go in and type in the next epoch number to check for blocks assigned.
2) When checking a specific epoch, consider making it easier to check the latest epoch that is calculated. The only time I use this feature is to check a future epoch, so the default isn't usually helpful.
3) When checking a future epoch, putting in a big number like "34356" simply says "No blocks in epoch 34356" - this should probably give an error or some other notice if the epoch requested hasn't been calculated rather than reporting zero blocks. The situation where this is important is if I try to check for blocks in a future epoch that isn't calculated yet (like if I try to check before the current epoch is 2/3 of the way done). I may think that I have no blocks when in reality the leading slots just haven't been calculated yet.
Thank you again for a great tool!