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
When the post xml files lack a field, the post sends an empty string as a key to the g2tmpl library to get the numeric equivalent. The g2tmpl library expects that keys will never be empty, and it lacks error checking to handle invalid keys. Sometimes errors are reported, but the g2tmpl usually won't write anything to the output value. Some of that is invisible to the post because g2tmpl routines call other routines. (For example, the template 4.9 routines will look up the integer values of keys for each field.)
The fix for this is:
UPP sends valid keys.
g2tmpl has reasonable behavior for invalid keys.
g2tmpl reports to UPP if any error that occurs within a subroutine call, not just the last call a subroutine makes.
The text was updated successfully, but these errors were encountered:
When the post xml files lack a field, the post sends an empty string as a key to the g2tmpl library to get the numeric equivalent. The g2tmpl library expects that keys will never be empty, and it lacks error checking to handle invalid keys. Sometimes errors are reported, but the g2tmpl usually won't write anything to the output value. Some of that is invisible to the post because g2tmpl routines call other routines. (For example, the template 4.9 routines will look up the integer values of keys for each field.)
The fix for this is:
The text was updated successfully, but these errors were encountered: