-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
conversation_granularity for slack - per user | per user per channel | per user per thread #10086
Conversation
Thanks for raising the issue and implementing the fix 🚀 What will happen next:
And then we can merge this into the new rasa 3.0.0 :) |
* Handle syslog writing from the command line * add an arg in the command line to use syslog * respect standards * line was too long * new arg for command line * add sanic logs to syslog * del useless statement * quick fix * too many blank line * Use default communication with syslog * possibility to use a syslog server * fix indent * Fix for constants access * fix typo Co-authored-by: Joe Juzl <[email protected]> * fix typo * fix for constant definition in bad file * Black linter compliant * Function add_server_arguments had 26 lines of code (exceeds 25 allowed). * fix for bad merge * for lint compliance * add required param * adapt test for log enhancement Co-authored-by: Joe Juzl <[email protected]>
* Markers telemetry * Everything without tests * Specified events.json * Test added * Changelog entry * Naming fixes * Fix lint, fix CLI bug No way to actually change config path, now fixed with nargs * Add markers parsed telemetry * Document telemetry functions * always add ANY_MARKER; add test * Add complexity telemetry * Skip root marker to avoid double reporting total marker count Co-authored-by: Matthew Summers <[email protected]> Co-authored-by: ka-bu <[email protected]>
@ka-bu added docs for the config. Changing default would be backward incompatible (new rasa with old conversations in tracker store) & hence haven't changed this. Also, is there anyway we can backport this fix to 2.8.x release? |
Thanks for the quick reply and addressing the feedback!
Great that you thought of this :) . I've been trying to get some feedback in the meantime on whether it is ok to make that breaking change for 3.0. For now, there is no feedback so your non-breaking version is what we proceed with, it seems.
If you like, you can open another PR and apply the same changes there to get this merged into 2.8.x. as well (by choosing that version as a target for your merge then). Otherwise, we can open an issue and someone from our team will pick that up. |
I like the new name for that setting and the names for the options 👍 -- Just one tiny linting issue so far from the checks. |
…adhya/rasa into slack_conversation_id
Thanks for your contributions! Once this is merged you can cherry-pick your commit and create a new PR for 2.8.x and we should be quick to get that one in. By the way, you can use pre-commit hooks to run checks locally or just use |
Reminder: We also have to add a changelog entry (i.e. a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some tiny suggestions. Otherwise looks good to me 🚀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to squash merge when ready 🚀
…markers_bugfix * 'markers_bugfix' of https://github.com/RasaHQ/rasa: Fix model dir (#10164) add changelog entry about tf2.6 update (#10153) conversation_granularity for slack - per user | per user per channel | per user per thread (#10086) add changelog fragment for docs changes in 3.0 fix syntax in training data example in the docs
allow conversation_id to be per user | per user per channel | per user per thread
Proposed changes:
Status (please check what you already did):
black
(please check Readme for instructions)