Petr Pučil

@ams-tschoening: > Don't you think normalizing paths would be worth another hack? JSON itself is OS-independent, so providing such paths as well seems the right thing to do. We do...

I believe the proposed solution of "treating paths as opaque strings" is now fully implemented in KSC by commits https://github.com/kaitai-io/kaitai_struct_compiler/compare/7071a9de11de3bafa711b6eb21961bbf7680623a...2b84e0a1e29712304debf709c143d9505e3062ca. The band-aid commit in `ksv` trying to add support for...

@KOLANICH: > There exists https://github.com/kaitai-io/kaitai_struct_samples , but yes, if we put all the files there, it soon will be pretty big. So if we centralize samples in a single repo,...

@KOLANICH: > But LFS is a feature of repos which usage is limimed. It looks like it - and quite severely, at least on GitHub. From https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage I understand that...

So using Git LFS on GitHub Free doesn't seem to bring any advantages - it's just more limited. Normally, you can have files [up to 100 MiB](https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-large-files-on-github#file-size-limits): > GitHub blocks...

For the record, the second error reported in https://github.com/kaitai-io/kaitai_struct/issues/414#issue-312746847 (`error: assigning to 'kscbug_t::filemiddlething_t *' from incompatible type 'kscbug_t::payload_bytes_t *'`) has been fixed a while ago - it's no longer reproducible...

Otherwise @Mingun is right, the primary problem demonstrated in this issue is the same as reported in #961. More specifically, the `payload` type in https://github.com/kaitai-io/kaitai_struct/issues/414#issue-312746847 is unreachable (unused) from root...

Duplicate of #961

@wader: > Hi, is there any more detailed description of how instances without a `pos` work? See https://github.com/kaitai-io/kaitai_struct/issues/544. I guess the general consensus is that "parse" `instances` without `pos` must...

> So in other words and for understanding: An instance can only refer to things that have already been parsed, it's not allowed (but not enforced atm) to "trigger" new...