You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under the routing menu F2 -> ROUTING the routing events don't seem to persist for long or show up inconsistently. Is this behavior expected or do others see this as a bug too?
Ideally a list of routing events should be appended to with the size of the buffer/file configurable in the config.toml
The text was updated successfully, but these errors were encountered:
Yes, the features was introduced without caching. I guess people run lntop in a screen or tmux window.
The cache file configurable in the config.toml is a good idea. Do you think that a json object for each routing event per line is a good format ? or should we use csv ?
@edouardparis I've submitted a PR #101 for a forwarding history tab so we could discuss whether this ticket is still needed unless we want to introduce caching for failed forwards in the routing tab. Curious about your thoughts.
Under the routing menu F2 -> ROUTING the routing events don't seem to persist for long or show up inconsistently. Is this behavior expected or do others see this as a bug too?
Ideally a list of routing events should be appended to with the size of the buffer/file configurable in the
config.toml
The text was updated successfully, but these errors were encountered: