Skip to content
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

When a recipe or a corpus is modified the changes are not put into operation until the plug-in is reloaded. Modifications should trigger a reload and retrain. #27

Open
schue opened this issue Jul 13, 2017 · 0 comments

Comments

@schue
Copy link
Contributor

schue commented Jul 13, 2017

No description provided.

schue added a commit that referenced this issue Sep 20, 2017
This update hooks into actions to trigger retraining of recipes.
There is still some delay in the state being shown in the pop-up
so there should still be some work done to have their status show
as "processing..." if analysis is underway.

Refs: #27
schue added a commit that referenced this issue Sep 20, 2017
#27 Rework recipe retraining and content analysis to hook into actions instead of monitoring state
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant