HashXHistoryPrefixRow issue with endianness of TxNums written to DB
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Compare the Python scribe's HashXHistoryPrefixRow serialization with the HashXHistoryValue implementation in herald.go, focusing on how TxNums are encoded and read. Determine the intended byte order for database values and verify that the chosen representation is consistent across platforms and implementations.
Written by the indexing model from the issue text.
Description
Python scribe when run on my machine (MacOS ARM64) produces little-endian txnums for hashXhistory prefix. (I just looked up M1 mac behavior, and it's little-endian by default) But there could be some more exotic platform that writes txnums big-endian fashion.
The endianness should be corrected to big-endian like other numbers in the database OR it should be locked to be little-endian specifically.
For now, I am correcting (herald.go) HashXHistoryValue implementation to read TxNums in little-endian form.
- Dominant language
- Python
- Stars
- 15
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lbryio/hub
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Bump to protobuf==3.18.3 within lbry-sdk repo causes MacOS unit test failuresPossibly taken @moodyjon claimed this 1377 days ago. Openpriority: high
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Herald needs to accept ipv6 ping and reply with an ipv6 pongPossibly taken @moodyjon claimed this 1403 days ago. Openarea: herald new feature
-
area: herald type: bug
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
intake mcp-intake needs-ac needs-human-review priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Ikalus1988/MisakaNet#3848 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
521xueweihan/HelloGitHub#4105 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
igormcsouza/bookloud#54 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
aws-samples/sample-per-model-bedrock#526 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ok-oldking/ok-wuthering-waves#1802 ·
Maintainers usually reply within 2 days