Query fully stops/crashes on an illegal tag length
Issue #926
duplicate
If the response of a query contains a Station Name having more than 16 characters, the full query stops. One could think of only skipping the illegal response.
Another option could be to force StationName to 16 characters (in qrscu, line 1070), then one needs to change:
rsp.station_name = get_value_kw("StationName", identifier)
to
rsp.station_name = get_value_kw("StationName", identifier)[:16]
This might also be an option for other tags that have length limitations.
(not a real bug, although I think the query should not stop fully/crash due to 1 illegal tag length)
Comments (4)
-
reporter -
Sorry for the delay @Luuk - is this a duplicate of issue
#799? In which case it is already fixed in develop… -
reporter Yes, I see. The solution is different (expanding model to 32 characters or cutting input to 16 characters), however I think both will work in practice.
-
- changed status to duplicate
Duplicate of
#799. - Log in to comment
@Ed McDonagh , @David Platten , What do you think about limiting the length of “length limited” tags in this context?
Or would it be better to fully skip that specific response or have a larger length limit in the model?