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

conversation_granularity for slack - per user | per user per channel | per user per thread #10086

Merged
merged 43 commits into from
Nov 10, 2021

Conversation

srinivasupadhya
Copy link
Contributor

@srinivasupadhya srinivasupadhya commented Nov 5, 2021

allow conversation_id to be per user | per user per channel | per user per thread

Proposed changes:

  • Allow multiple active conversations for a user on slack with bot

Status (please check what you already did):

  • added some tests for the functionality
  • updated the documentation
  • updated the changelog (please check changelog for instructions)
  • reformat files using black (please check Readme for instructions)

@srinivasupadhya srinivasupadhya requested a review from a team as a code owner November 5, 2021 06:48
@srinivasupadhya srinivasupadhya requested review from ka-bu and removed request for a team November 5, 2021 06:48
@CLAassistant
Copy link

CLAassistant commented Nov 5, 2021

CLA assistant check
All committers have signed the CLA.

@ka-bu
Copy link
Contributor

ka-bu commented Nov 8, 2021

Thanks for raising the issue and implementing the fix 🚀

What will happen next:

  • I'll enable the tests and will get some feedback from more people cause it looks to me like the conversation_id that you constructed might be a more reasonable default value for the sender_id than the current choice
  • we'll address the test issues / feedback / review items
  • we'll need to update the rasa docs (https://rasa.com/docs/rasa/connectors/slack/) and add a changelog entry

And then we can merge this into the new rasa 3.0.0 :)

rasa/core/channels/slack.py Outdated Show resolved Hide resolved
srinivasupadhya and others added 17 commits November 8, 2021 16:59
* 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]>
@srinivasupadhya
Copy link
Contributor Author

srinivasupadhya commented Nov 9, 2021

@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?

@srinivasupadhya srinivasupadhya changed the title allow conversation_id to be per user | per user per channel | per user per thread conversation_granularity for slack - per user | per user per channel | per user per thread Nov 9, 2021
@ka-bu
Copy link
Contributor

ka-bu commented Nov 10, 2021

Thanks for the quick reply and addressing the feedback!

@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.

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.

Also, is there anyway we can backport this fix to 2.8.x release?

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.

@ka-bu
Copy link
Contributor

ka-bu commented Nov 10, 2021

I like the new name for that setting and the names for the options 👍 -- Just one tiny linting issue so far from the checks.

@srinivasupadhya
Copy link
Contributor Author

srinivasupadhya commented Nov 10, 2021

@ka-bu addressed the formatting issue. thanks for the inputs. Raised #10146 for 2.8.x

@tayfun
Copy link
Contributor

tayfun commented Nov 10, 2021

@ka-bu addressed the formatting issue. thanks for the inputs, will raise a separate PR for 2.8.x.

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 black manually to check formatting issues on your own machine.

@ka-bu
Copy link
Contributor

ka-bu commented Nov 10, 2021

Reminder: We also have to add a changelog entry (i.e. a <pr number>.improvement file with a description under the changelog folder)

@srinivasupadhya
Copy link
Contributor Author

@ka-bu @tayfun everything seems to be green now. let me know if there is anymore work here.

Copy link
Contributor

@ka-bu ka-bu left a 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 🚀

changelog/10086.misc.md Outdated Show resolved Hide resolved
docs/docs/connectors/slack.mdx Show resolved Hide resolved
rasa/core/channels/slack.py Show resolved Hide resolved
Copy link
Contributor

@ka-bu ka-bu left a 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 🚀

@srinivasupadhya
Copy link
Contributor Author

@ka-bu seems like coverage report upload job failed. Not sure how to proceed. Also, #10146 is ready as well.

@tayfun tayfun enabled auto-merge (squash) November 10, 2021 15:40
@tayfun tayfun merged commit d04290f into RasaHQ:main Nov 10, 2021
aeshky added a commit that referenced this pull request Nov 11, 2021
…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
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

Successfully merging this pull request may close these issues.

9 participants