Drop old txo-fetch results #396
No reviewers
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
dependencies
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-redux#396
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "ip-txo-fetch-id"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Issue
Closes lbry-desktop 4317: Transaction list shows previously requested data / pages
Approach
A naive approach of creating a random transaction ID for each fetch. The latest ID, stored in
state
, will be the expected one -- any other transaction results will be dropped.The loading spinner will continue to spin until the latest ID's results are fetched.
Sample
Example of 3 fast filter switches:

??
This assumes there's no quick, built-in way to abort dispatched tasks (only did a quick Google search for it). The ability to abort would speed up the wait-time.
currently testing on bob
<3 looks great!
👍