Version: Rasa X 0.28.5
I have deployed rasa x on my server and even connected it to my git but still it doesnot show the data of git in rasa x
Version: Rasa X 0.28.5
I have deployed rasa x on my server and even connected it to my git but still it doesnot show the data of git in rasa x
Hey @shivani.python, could you give some more details? how did you set up the connection? Were there any errors?
No there were no errors i have followed all the steps as mentioned in the masterclass video but still can’t load the data from git repo
This is the same issue I have been having and have impossible to resolve.
@ig-shaun @shivani.python are you both still experiencing issues? I know the reply is a little late, but I’ve been a bit busy the past month, sorry about that.
I am facing the same issue @akelad I am using version 0.29.3
My project structure is same as mentioned in rasa master class except the fact that since I have multiple project in our application so all my rasa related things are in subdirectory i.e. not at root level.
The other weird thing is that I facing problem with NLU data as rasa-x is showing NLU data and story tab as empty but rasa-x is able to pick domain.yml as these details are shown in respective tabs in rasa-x i.e. responses and domain.
One more weird thing is rasa-x configuration file and my configuration file do not match not sure how rasa-x is creating it.
Let me know if any other details are required.
How is your Rasa X instance deployed and how is your git repo configured?
What does the structure of your repository look? If it’s not in the root of the repository, then that is probably why it’s not syncing
I am having the same issue. My flow:
rasa init --no-promptcurl -s get-rasa-x.rasa.com | sudo bash
@Btibert3 can you check the logs for rasa-production and rasa-x and paste them here?
So what is interesting here is that I spun up a new server and while some of the data can be seen (e.g. NLU data, stories), Rasa X is telling me that a model needs to be trained, even though one is in the repo. For some reason, the model is not identified this time around.
Regardless, the logs (I believe)
INFO:alembic.runtime.migration:Context impl PostgresqlImpl.
INFO:alembic.runtime.migration:Will assume transactional DDL.
INFO:alembic.runtime.migration:Running upgrade -> 2a216ed121dd, Initial migration
INFO:alembic.runtime.migration:Running upgrade 2a216ed121dd -> 9d4a16758d6e, Addition of `is_default` and `description` columns to `user_role` table.
INFO:alembic.runtime.migration:Running upgrade 9d4a16758d6e -> e3a3a2789e20, Add index to `conversation_id` column of table `conversation_event`.
INFO:alembic.runtime.migration:Running upgrade e3a3a2789e20 -> 59b7be3ad5fc, Add `extractor` column to table `nlu_training_data_entity`.
INFO:alembic.runtime.migration:Running upgrade 59b7be3ad5fc -> 1dfbf67d6ae2, Support for individually unfeaturized entities in domain.
INFO:alembic.runtime.migration:Running upgrade 1dfbf67d6ae2 -> b4a9bd47b6e0, Indexes for faster NLU logs and training data queries.
INFO:alembic.runtime.migration:Running upgrade b4a9bd47b6e0 -> 8b528d137850, Add single column id for domain objects such as actions, slots, etc.
INFO:alembic.runtime.migration:Running upgrade 8b528d137850 -> 45546b047abe, Add index to `timestamp` column in `conversation_event` table.
INFO:alembic.runtime.migration:Running upgrade 45546b047abe -> 213f246e1490, Remove duplicated log entries keeping only most recent unique user messages.
INFO:alembic.runtime.migration:Running upgrade 213f246e1490 -> ffddc4250349, Add a column for `triggers` to the domain intents.
INFO:alembic.runtime.migration:Running upgrade ffddc4250349 -> 35a1c7937594, Add `edited_since_last_training` column to `template` table.
INFO:alembic.runtime.migration:Running upgrade 35a1c7937594 -> 6fce9679db61, Add column to `lookup_table` table which contains the number of elements in a table.
INFO:alembic.runtime.migration:Running upgrade 6fce9679db61 -> 4daabca814ee, Oracle Migrations.
INFO:alembic.runtime.migration:Running upgrade 4daabca814ee -> 1d990f240f4d, Change datatype of the `text` column in the table `template` from `String` to `Text`
INFO:alembic.runtime.migration:Running upgrade 1d990f240f4d -> 36c070bd6363, Rename too-long table name `conversation_message_correction`.
INFO:alembic.runtime.migration:Running upgrade 36c070bd6363 -> d45a0bf21e89, Add unique ID to EntitySynonyms
INFO:alembic.runtime.migration:Running upgrade d45a0bf21e89 -> 3b15f8e56784, Add `original_value` field to training data entities.
INFO:alembic.runtime.migration:Running upgrade 3b15f8e56784 -> a86c9fac00fa, Add `rasa_environment` column to `conversation_event` table.
INFO:alembic.runtime.migration:Running upgrade a86c9fac00fa -> a813c6c15a4c, Add a column to store the foreign key of a used synonym.
INFO:alembic.runtime.migration:Running upgrade a813c6c15a4c -> cffc160af576, Add data column to User
INFO:alembic.runtime.migration:Running upgrade cffc160af576 -> 945ef2034d57, Add `git_repository` table.
INFO:alembic.runtime.migration:Running upgrade 945ef2034d57 -> 99e6a52a2eb7, Drop 'attributes' column in 'rasa_x_user' table.
INFO:alembic.runtime.migration:Running upgrade 99e6a52a2eb7 -> d9d7b3d9cadd, Add `session_expiration_time` and `carry_over_slots_to_new_session` columns to table `domain`.
INFO:alembic.runtime.migration:Running upgrade d9d7b3d9cadd -> acd80348b093, Add configuration values table.
INFO:alembic.runtime.migration:Running upgrade acd80348b093 -> 443af39e50e3, This migration is left empty because of issue with 0.25.0 release.
INFO:alembic.runtime.migration:Running upgrade 443af39e50e3 -> 22e9e6ea593c, This migration is left empty because of issue with 0.25.0 release.
INFO:alembic.runtime.migration:Running upgrade 22e9e6ea593c -> 8893bba2a522, Rename column `carry_over_slots_to_new_session` and index `nlu_train_data_ent_orig_val_idx`.
INFO:alembic.runtime.migration:Running upgrade 8893bba2a522 -> d5160f2d00b8, Remove duplicate responses.
INFO:alembic.runtime.migration:Running upgrade d5160f2d00b8 -> 8a260b1a797a, FIXED Remove is_unflagged field from Conversations
INFO:alembic.runtime.migration:Running upgrade 8a260b1a797a -> 0b35090e53cf, FIXED Add tables to store conversation tags.
INFO:alembic.runtime.migration:Running upgrade 0b35090e53cf -> 1a712f7b70e9, Delete duplicate events and add unique constraint to `conversation_event` table.
INFO:alembic.runtime.migration:Running upgrade 1a712f7b70e9 -> 6738be716c3f, Add slot name and value to ConversationEvent
INFO:alembic.runtime.migration:Running upgrade 6738be716c3f -> 304e0754a200, Add columns for the updated Integrated Version Control features.
INFO:alembic.runtime.migration:Running upgrade 304e0754a200 -> b49ca6b367e3, Add index for flagged conversation events
INFO:alembic.runtime.migration:Running upgrade b49ca6b367e3 -> 37b34bf8df43, Add columns and indices for NLU/Core confidences
/usr/local/lib/python3.7/site-packages/sqlalchemy/dialects/postgresql/base.py:3470: SAWarning: Predicate of partial index conversation_event_flag_index ignored during reflection
% idx_name
INFO:alembic.runtime.migration:Running upgrade 37b34bf8df43 -> 68a8a531a5ee, Add `in_training_data` column to `conversation_session` table.
INFO:alembic.runtime.migration:Running upgrade 68a8a531a5ee -> 66bada3d94ae, Add new `tests.*` permission for admins
INFO:alembic.runtime.migration:Running upgrade 304e0754a200 -> 3fbc8790762e, This migration is left empty because of issues with the 0.26.2 release.
INFO:alembic.runtime.migration:Running upgrade 3fbc8790762e -> ef93223786ba, Remove slot value index completely
INFO:alembic.runtime.migration:Running upgrade ef93223786ba, 66bada3d94ae -> 73f46e0b7789, Merge migrations from 0.26.x
INFO:alembic.runtime.migration:Running upgrade 73f46e0b7789 -> b092b0fe590d, Remove duplicate responses.
INFO:alembic.runtime.migration:Running upgrade b092b0fe590d -> 36fa577b374d, Rename table name `template` and column `template`.
INFO:alembic.runtime.migration:Running upgrade 36fa577b374d -> 425bd8f628db, Add missing permissions for `tester` and `annotator` roles.
INFO:alembic.runtime.migration:Running upgrade 425bd8f628db -> 7b2497cd88dc, Add `username` field to `conversation` table.
INFO:alembic.runtime.migration:Running upgrade 7b2497cd88dc -> ac3fba1c2b86, Add index for `created_by` foreign key.
INFO:alembic.runtime.migration:Running upgrade 8893bba2a522 -> b67a67032c7f, This migration comes from RBAC backport for `0.24.x`.
It is empty because all the permissions that are required for
role-based access control fixes were already added before.
INFO:alembic.runtime.migration:Running upgrade ac3fba1c2b86, b67a67032c7f -> 9e7a97234e85, Merge the migrations from the 0.24.x patch release with
Rasa X databases which didn't run this backported migration.
INFO:alembic.runtime.migration:Running upgrade 9e7a97234e85 -> 8a8562256a8e, Add `hash` column and an index for it to `response` table.
INFO:alembic.runtime.migration:Running upgrade ac3fba1c2b86 -> af3596f6982f, Add the column `in_training_data` to the table `message_log`.
INFO:alembic.runtime.migration:Running upgrade af3596f6982f, 8a8562256a8e -> eb2b98905e7e, Merge heads af3596f6982f and 8a8562256a8e.
INFO:alembic.runtime.migration:Running upgrade eb2b98905e7e -> 479084222950, Add `model` column to table `message_log`.
INFO:alembic.runtime.migration:Running upgrade 479084222950 -> 90b60aff4920, Add a 'review_status' column to the 'conversation' table.
INFO:alembic.runtime.migration:Running upgrade 90b60aff4920 -> 473b15141809, Add `conversations.view.metadata.get` permission to `annotator` role.
Starting Rasa X server... 🚀
/usr/local/lib/python3.7/site-packages/rasax/community/services/test_service.py:43: UserWarning: Unable to get tests from tests/conversation_tests.md:
File 'tests/conversation_tests.md' does not exist. Please, make sure you have end-to-end tests added to your assistant. See https://rasa.com/docs/rasa-x/user-guide/test-assistant for more information.
UserWarning,
INFO:rasax.community.services.integrated_version_control.git_service:Cloning git repository from URL 'git@github.com:Btibert3/rasa-golf-booking.git'.
Oh @Btibert3 so the data is there now? It’s not going to pull a model, that needs to be uploaded separately.
data is not coming from git repo but in rasa x its showing that it is connected to the repo what to do in this case?