Handle zero nlocktime txs

[lewixlabs]

Ok thanks, being an encrypted file i didn't know had 0 transactions inside (or does garecovery can check this?). I found in my emails another nLocktimes file which has a valid (i think) content > 0 (644 bytes instead of 100). I will try.

Il giorno ven 1 set 2017 alle ore 18:09 jkauffman1 notifications@github.com ha scritto:

---

You can view, comment on, or merge this pull request online at:

https://github.com/greenaddress/garecovery/pull/10 Commit Summary

• Do not read bitcoin config files from filesystem during testing
• Handle case of nlocktimes file with zero transactions better

File Changes

• M garecovery/tests/test_2of2.py https://github.com/greenaddress/garecovery/pull/10/files#diff-0 (12)
• M garecovery/tests/test_2of3.py https://github.com/greenaddress/garecovery/pull/10/files#diff-1 (6)
• A garecovery/tests/test_data/empty_nlocktimes.zip https://github.com/greenaddress/garecovery/pull/10/files#diff-2 (0)
• A garecovery/tests/test_data/mnemonic_12.txt https://github.com/greenaddress/garecovery/pull/10/files#diff-3 (1)
• M garecovery/two_of_two.py https://github.com/greenaddress/garecovery/pull/10/files#diff-4 (4)

Patch Links:

• https://github.com/greenaddress/garecovery/pull/10.patch
• https://github.com/greenaddress/garecovery/pull/10.diff

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/greenaddress/garecovery/pull/10, or mute the thread https://github.com/notifications/unsubscribe-auth/AHB5z8e9Hv-HEIelTgRNyO9z42SQVBsSks5seCwrgaJpZM4PKWRI .