David Zurow

As this fix is for the CLI authorization workflow, I'm not quite sure where to add the tests. They should be pretty clear from trying to run the manual workflow.

@kendonB You can read the background at https://github.com/dictation-toolbox/dragonfly/issues/182 and https://github.com/dictation-toolbox/Caster/issues/774. I currently can't reproduce it myself. I welcome any help trying to track it down. Apparently, removing or disabling that...

@kendonB I can't reproduce it on my dev system currently, although it was happening in the past, both without caster.

@kendonB I should have been clearer. To "re-enable" the problem, you should only need to do one of (although your way should work too, modulo the craziness of this bug...

@kendonB No, just add that line somewhere in your loader file or a grammar file, as long as it is executed after the logging initialization. But I am not experienced...

> This may have fixed it: > [dictation-toolbox/dragonfly#182 (comment)](https://github.com/dictation-toolbox/dragonfly/issues/182#issuecomment-589483348) I don't think that fixed it, because I think I still had it happen after that change, and reverting that change...

FWIW, I don't know the details of Caster, but I think there's something to be said for having a single, central place for keeping state. In addition to making it...

I have been working some on this for the Kaldi backend, as part of trying to improve its dictation capabilities. But you're right, it really should be generalized to work...

> Another item that would be nice would be ability to use Kaldi for commands, but DNS for dictation - similar to how I believe Kaldi can be used with...

Yeah, different engines handle ambiguous grammars differently. The current recommended way to handle this in Kaldi is to set a weight on one of them, to determine which should take...