New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cleanup Adapt ContextManager implementation #2886
base: dev
Are you sure you want to change the base?
Conversation
Voight Kampff Integration Test Succeeded (Results) |
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
cherry pick of MycroftAI#2886 Timed Context Manager Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects _only_ the modifications done to integrate the context with the Mycroft intent system. The key differences from the default Adapt context manager are - Frames are timedout after a set time - get_context will only return the latest match - methods for removing context (all and specific)
e05e323
to
c88f703
Compare
Codecov Report
@@ Coverage Diff @@
## dev #2886 +/- ##
==========================================
- Coverage 52.85% 52.84% -0.02%
==========================================
Files 123 123
Lines 11043 11014 -29
==========================================
- Hits 5837 5820 -17
+ Misses 5206 5194 -12
Continue to review full report at Codecov.
|
bc97282
to
c88f703
Compare
Description
Makes the Mycroft-core Adapt Context Manager depend on the ContextManager in Adapt. This removes a bunch of duplicated code. The current state of the class reflects only the modifications done to integrate the context with the Mycroft intent system. The handling of timeout has been moved into the earlier weird tuple-thing into the context frame metadata.
The key differences from the default Adapt context manager are
get_context()
will only return the latest matchThis keeps the current implementation as-is, I need to dig into the history to see why point 2 was added and will be working to integrate some of the functionality in the context manager from adapt. (clear, remove and maybe a canonical way to limit the frame_stack)
I do however think this is a good first step.
How to test
Ensure unit tests still work, check that wikipedia skill "tell more" functionality works
Contributor license agreement signed?
CLA [ Yes ]