Possible to Crash Logic 2 with an Analyzer

[BitBob]

@baebiebrian

Unfortunately, I haven’t been able to find much in the way of clear documentation about the correct syntax for that setting

See an older post regarding format string:

HLA bubble text doesn't display zero (0) value?

While experimenting with high-level analyzer (HLA) for quadrature decoder (see other thread), I noticed that a zero value didn’t display in the bubble text of my draft HLA: [image] as the zero value (0) was in the scaled_position data – see Data table view: [image] (Note: original thread only had position column showing, while technically scaled_position is output) Some snippets from the analyzer python script: The result_types definition: result_types = { 'QuadEncoder': { …

… but I didn’t hear back anything to confirm or deny my suspicions of the format syntax used:

@BitBob

Trying to answer that question, I did a different workaround that might be preferred (and seems to indicate that the ‘Template Engine’ is Handlebars JS or some other derivative)

Note: For more info on Handlebars JS:

Handlebars

(Which may or may not be the right syntax for this)

Finally, this could explain the harder crashing: if the Logic application (running in Electron/JavaScript) is natively executing/interpreting the ‘format’ returned from the python HLA, then the error handling & validation of a bad ‘format’ strings may be missing on the JavaScript side (vs. caught/handled on the python side).

However, I agree – the JS side could do more to catch/validate bad format exceptions from python/HLAs to mitigate hard crashes, and/or hopefully Saleae could at least document (or disclose) the right ‘format’ syntax to use to avoid causing them in the first place.