Group tag block is only partially read since 0bba7e1 about aislib HOT 6 OPEN

I got that, I just need to figure out what's wrong to produce a change that works in both cases - thanks for providing an example for that :)

I'll probably have a look at this next week.

from aislib.

We had a problem in our system parsing the messages with comment blocks that start with the \g: prefix. With that commit our problems has been resolved. Please feel free to apply a pull request in order to completely fix the issue! Thanks in advance!

from aislib.

Happy to contribute that, however I need to know what exactly was broken for you (I don't see anything obviously wrong with messages starting with \g:) - could you provide some test data that failed and what you'd expect from it (or a unit test)?

from aislib.

I just checked and the unit test that failed with the new version on my side is also a comment block starting with \g:, and it was working fine before. So I'll definitely need some example to reproduce your issue.

from aislib.

this is an actual message 24 with comment block that starts with \g:

\g:1-1-21,s:47450,c:1699113260,i:SXSPA:1699115144 I:1699115146 D:1699115146 L:FM136 G:hndgs T:0 1261!AIVDM,1,1,,A,H7Oks<0hTtpE=<0000000000000,24C

Beforehand our system wasn't able to decode and produce the JSON output for that kind of sentence. And we are parsing millions of them in a daily basis. As I already said currently everything works properly in comparison with the previous code.

from aislib.

Obviously that "next week" prediction didn't pan out xD.
It's basically in my backlog now, but given no-one else seems to be affected it anyway is hardly time-critical.

from aislib.