BUG - GLOWS DE LEN=0 handling

[maxinelasp]

Description of the issue

From Marek Strumik:
"In DE packets there are two fields: LEN and SEQ (after CCSDS header and
SEC field). These are items 2 and 3 in Sec. 3.4.2 in the algorithm doc
v. 4.4.7. In lines 583-585 an explicit explanation has been added in v.
4.4.7 that LEN can happen to be zero. LEN=0 means that SEQ is the last
field to be read from CCSDS packet. Neither data_every_second structure
nor direct events are expected for LEN=0 in a given CCSDS packet
because SEC was not found in the instrument memory and we have a sort of
"empty" DE packet.

It could be that when writing DE handler in your code you already
defined a behavior for LEN=0. If so, then please check if it is
consistent with the description above. If LEN=0 is not handled in any
specific way or leads to an error/exception, then we kindly ask you to
follow what was defined above."

Check in GLOWS L1A DE code to see if LEN=0 is handled gracefully.

Steps to reproduce the issue

No response

Expected behavior (What should happen)

No response

Actual behavior (What does happen)

No response

Code Snippet:

Code

Additional notes, affected areas, and suggested fixes

No response