This topic contains 3 replies, has 3 voices, and was last updated by  Eliot Muir 3 years ago.

Stack traces in logs for translator exceptions in production

  • This was a nice suggestion from Rafal of Seamless Medical that made sense to me for us to do it. Jon Scalise has been working on the feature and I thought I would show what the stack trace would look like:

    Translator error occurred in module "main.lua", line 23:
    attempt to call global 'arr' (a nil value)
    stack traceback:
            main.lua:23: in function 'three'
            shared/other.lua:4: in function 'two'
            main.lua:12: in function 'one'
            main.lua:6: in function <main:5>
    

    Thoughts and opinions are welcome. We’re intending to push this out into a point release when the functionality is ready.

    neat. takes the guesswork away.

    I approve!

    Will this be the default, or will we need to enable Debug-level logging in the channel configuration?

    Jeff Drumm ◊ VP and COO ◊ HICG, LLC. ◊ http://www.hicgrp.com

    It will on by default with or without debug mode. Sorry for slow reply – weekend followed by RSNA…

    One could use pcall yourself in the script and override this exception handling (in fact with pcall one could actually generate this type of stack trace oneself in theory…).

You must be logged in to reply to this topic.