determine steps to fix getDelayForName in 17.3; we still work around a bug there #400
Labels
No labels
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
Epic
good first issue
hacktoberfest
hard fork
help wanted
icebox
Invalid
level: 0
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
soft fork
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
work in progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbrycrd#400
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The 17.4+ codebase had to work around a bug that exists in the previous versions. See https://github.com/lbryio/lbrycrd/blame/v17_master/src/claimtrie/trie.cpp#L921 . It would be nice if we could hard-fork this out in both 17.3 and 17.4+ (aka, v17_master and v19_master) in our next hard fork, but we need to identify the proper fix for it in the 17.3 codebase (aka, master).