Using keyword "my" results in regex problems about adapt

[stratus-ss]

The Grocery List exists and works with the word 'the'
console output from a successful add:

 add stuff to the grocery list                                                     
 >> Adding stuff to your list                                                              

15:06:59.291 | INFO     | 116927 | __main__:handle_wakeword:67 | Wakeword Detected: hey jarvis
 15:06:59.661 | INFO     | 116927 | __main__:handle_record_begin:37 | Begin Recording...
 15:07:01.896 | INFO     | 116927 | __main__:handle_record_end:45 | End Recording...
~~~~| INFO     | 116927 | __main__:handle_utterance:72 | Utterance: ['add stuff to the grocery list']
 15:07:03.732 | INFO     | 116919 | OurGroceriesSkill | List is 14819 minutes old
Updating groceries list as it is older than 10 minutes
 15:07:03.974 | INFO     | 116919 | OurGroceriesSkill | List is 2 minutes old
categories list under 10 minutes old... skipping refresh
 15:07:04.247 | INFO     | 116919 | OurGroceriesSkill | -----> Added item <------

audio.log
bus.log
enclosure.log
skills.log
voice.log

However, using the keyword "my" causes the same skill to fail

 add stuff to my grocery list                                                                       
 >> Sorry the my grocery list list does not exist  

 15:07:09.411 | INFO     | 116927 | __main__:handle_wakeword:67 | Wakeword Detected: hey jarvis
 15:07:09.779 | INFO     | 116927 | __main__:handle_record_begin:37 | Begin Recording...
 15:07:14.021 | INFO     | 116927 | __main__:handle_record_end:45 | End Recording...
~~~~ | INFO     | 116927 | __main__:handle_utterance:72 | Utterance: ['add stuff to my grocery list']

[clusterfudge]

Can you include logs with at the DEBUG level? I'm not seeing the events from the intent parser.

[stratus-ss]

how do I enable debug?

The only thing I found was self.log.debug(). Do I need a bunch of these statements? if so, where would you like these included?

[clusterfudge]

You should be able to configure via a mycroft.conf file like so:
https://github.com/MycroftAI/mycroft-core/blob/dev/mycroft/configuration/mycroft.conf#L253

[stratus-ss]

These are the logs while testing the "the" keyword after setting Debug as suggested

the_keyword_voice.log
the_keyword_skills.log
the_keyword_enclosure.log
the_keyword_bus.log
the_keyword_audio.log

[stratus-ss]

these are the logs from the two tests
with the trigger "add stuff to my grocery list"
voice.log
skills.log
enclosure.log
bus.log
audio.log

Here are the regex during today's tests

add (?P<Food>.*) (to my) (?P<ShoppingList>.*) list
add (?P<Food>.*) (to the) (?P<ShoppingList>.*) list

[clusterfudge]

Unfortunately, the log lines I was expecting are not present; it appears that almost all DEBUG logs have been removed from mycroft-core, which makes this a bit more difficult to diagnose with tinkering. Also, just to confirm, you restarted each of the processes after changing the configuration? I believe this config change requires a restart.

Adapt emits a couple of events that will be helpful, that show the intermediate state of the parser. Hopefully, they're wired up enough that you can add logging for them somewhere.

You'll want to add an event handler for
tagged_entities to the instance of IntentDeterminationEngine held in the intent service. I'm no longer familiar enough with mycroft-core to point out where that happens, and unfortunately it does not appear that the internal emitter is bound to the message bus (which would've made this a lot easier).

[clusterfudge]

hey @stratus-ss did you have any luck with this? If you're still seeing this issue, please let us know and we'll try to address it prior to 1.0.0. I suspect this is similar to what you reported #102, and I'll have the same sad answer for you.

[clusterfudge]

I'm going to close this out as cannot reproduce, as we're no longer getting any notes from the reporter.