You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When fetching the VssPath Property (non-specification) Vehicle with Field.VALUE and Field.METADATA a result with 270_000 characters is returned. This is to much to put into the log, which will simply crash because it can not provide the corresponding height. To fix the crash a workaround was implemented, which truncates to long textes (see: OutputViewModel#sanitizeString). If Field.METADATA is removed it's roughly 80k which should easily be representable inside the ScrollView of the Log Output.
We should try to fix the root cause here and remove the truncation logic if feasible.
Instead of sending a single query with Field.METADATA and Field.VALUE maybe two queries should be send, one to set the datatype (which uses Field.METADATA) of the field and one to fetch and log the value.
To Reproduce
Steps to reproduce the behavior:
Remove Sanitization Logic in OutputViewModel (e.g. return text)
Connect to DataBroker
Get "Vehicle"
Crash
Expected behavior
4. No Crash, Output is logged into Output View
The text was updated successfully, but these errors were encountered:
Splitting up fetching the FIELD_TYPE and fetching the actual
query from the user into two separate ones.
Unfortunately this did not fix the crash when logging vehicle
because the json contained to many lineBreaks ("\n").
Closes: eclipse-kuksa#24
Signed-off-by: Andre Weber <andre.weber3@etas.com>
Describe the bug
When fetching the VssPath Property (non-specification) Vehicle with Field.VALUE and Field.METADATA a result with 270_000 characters is returned. This is to much to put into the log, which will simply crash because it can not provide the corresponding height. To fix the crash a workaround was implemented, which truncates to long textes (see: OutputViewModel#sanitizeString). If Field.METADATA is removed it's roughly 80k which should easily be representable inside the ScrollView of the Log Output.
We should try to fix the root cause here and remove the truncation logic if feasible.
Instead of sending a single query with Field.METADATA and Field.VALUE maybe two queries should be send, one to set the datatype (which uses Field.METADATA) of the field and one to fetch and log the value.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
4. No Crash, Output is logged into Output View
The text was updated successfully, but these errors were encountered: