scribe full sync failed at block 213495: db op tries to delete with incorrect existing value DELETE activated_claim_and_support #111
Labels
No labels
area: database
area: documentation
area: elasticsearch
area: herald
area: packaging
area: scribe
consider soon
critical
dependencies
good first issue
hacktoberfest
help wanted
improvement
needs: repro
new feature
priority: blocker
priority: high
priority: low
priority: medium
type: bug
type: bug-fix
type: discussion
type: feature request
type: improvement
type: new feature
type: refactor
type: task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/hub#111
Loading…
Add table
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?
Looks like the problems with scribe full sync are not over. ☹️ It seemed a lot faster though. Took only 1-2 hours to reach this point. 😆
I have the latest hub checked out:
dcd4d7a7a8
python3 -m hub.scribe --db_dir ./scribe_db/ --daemon_url https:/<user>:<pass>@localhost