Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Fix user ID always default on every shell session. #5117
Fix user ID always default on every shell session. #5117
Changes from 32 commits
08eda89
4eda4ed
7d093a8
984c702
1622793
0034e33
a5b185c
3dee8fd
88a3c09
cc2f1cc
bf9945e
a1351f5
529c2e9
6c93b3f
af2b561
2f40740
cc76148
0bc6078
368efe6
a148933
0397e4d
dd52f11
d0115ab
c5fb40c
ec6590e
f50d0c0
b7ab04d
cc5e7b7
af501c7
f01166c
2104ec3
63fcf89
823379a
d2454b0
927a272
bd38b69
f4cd9e8
32be2b3
ecf01b6
ea75052
b1d32cb
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
@ricwo Would it be better to default to generating a random ID when
rasa shell
is called instead of fixing it here as a constant?The reason for this suggestion is: If you have a persistent tracker store and run
rasa shell
, you would want to start from scratch with a new conversation id and not at whichever state the last session with a default id was in.(We were also discussing that in the PR that adds such an argument for
rasa interactive
: #5243.)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.
I agree, It was the way I first changed it. @ricwo @erohmensing I am ok with changing it, What is your opinion?
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.
@chkoss yes but this is a separate functionality and should probably be controlled with a different command-line argument, something like
--assign-random-conversation-id
@VictorCoCo your initial implementation assigned a random user ID with every new shell session, and made it impossible to use a deterministic one. being able to define a conversation ID as a command-line argument and having the script choose a random one are two separate issues. whatever the default behaviour, there needs to remain the possibility of a deterministic conversation ID