Try to only keep one copy of each claim in the store #149
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#149
Loading…
Reference in a new issue
No description provided.
Delete branch "fetch-claim-list-mine"
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?
I think it would be cool to try to only keep one copy of any object in the store, to avoid weird problems later on with the same thing having different properties.
@ -53,1 +62,4 @@
myClaims.add(uri)
byUri[uri] = claim
})
I suspect this will cause misses, since they are not typically built with claimSequence and claimId.
This is a good change and could probably be shipped as-is. Just want to take one more day to think or dig a little deeper about it before merging.
@ -53,1 +62,4 @@
myClaims.add(uri)
byUri[uri] = claim
})
I think rather than misses, this is going to cause duplicates. So rather than having dupes separated into
claimsByUri
andmyClaims
now we've just moved the duplication problem into theclaimsByUri
object, but a step in the right direction perhaps for removing dupes?I think long term it might be better to store claims in
claims.byId
and then mapbyUri
,myClaims
, etc, to claim ids.@ -22,1 +21,4 @@
const { outpoint } = fileInfo
if (outpoint) newFileInfos[fileInfo.outpoint] = fileInfo
})
I have a file with no outpoint locally. It's one that I tried to upload but it didn't work for some reason.
@ -53,1 +62,4 @@
myClaims.add(uri)
byUri[uri] = claim
})
We were saying the same thing here.