Open maxnoe opened 10 months ago
Tested this locally with the large file and it works:
type = 1200 version = 0, extended=True, length = 1096
type = 1212 version = 0, extended=True, length = 696
type = 1201 version = 0, extended=True, length = 20
type = 1202 version = 0, extended=True, length = 1096
type = 1203 version = 0, extended=True, length = 16
type = 1205 version = 0, extended=True, length = 34156
type = 1204 version = 0, extended=True, length = 12576458588
type = 1205 version = 0, extended=True, length = 12576458572
type = 1209 version = 0, extended=True, length = 1096
type = 1210 version = 0, extended=True, length = 16
what about artificially creating one of those files as a test fixture? if it is time consuming, we could cache it: https://docs.github.com/en/actions/using-workflows/caching-dependencies-to-speed-up-workflows, we have 10 GB storage for the cache.
otherwise we could host one of those files publicly, download it as a test fixture, and then cache it.
Add support for extended length field.
Unfortunately, it's kind of hard to test as it is only applicable for payloads that are larger than 1 GiB.
That's also why for a long time there was a bug in the c reference writer implementation preventing these objects (fixed somewhen in 2018 I think).
I have one file that exceeds this and is using the extended bit, but it's 11 GiB large.