# Diffs between git and nlu data displayed and used by Rasa X

**URL:** https://forum.rasa.com/t/diffs-between-git-and-nlu-data-displayed-and-used-by-rasa-x/50472
**Category:** \[Deprecated\] Rasa X Community Edition
**Created:** [January 10, 2022, 5:18pm UTC](https://forum.rasa.com/t/diffs-between-git-and-nlu-data-displayed-and-used-by-rasa-x/50472 "2022-01-10T17:18:23Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![spf](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/spf/32/18610_2.png) [@spf](https://forum.rasa.com/u/spf)
#### Post date: [January 10, 2022, 5:18pm UTC](https://forum.rasa.com/t/diffs-between-git-and-nlu-data-displayed-and-used-by-rasa-x/50472/1 "2022-01-10T17:18:23Z")

</div>

Hi, I ve connected my rasa x instance to a git repo, but after a my last sync I see a lot of differences between the nlu data from git and what is displayed in the rasa x UI … problem is I cannot sync or train a model any longer … I checked the git folder in der docker container, which exactly mirrors the git.

my question: where does rasa x store the other files (the data that is displayed in the UI) … I would like to clean them up, if that is possible

I’m using Rasa 1.0.1 btw

---

<div class="post-metadata">

### Author: ![nik202](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/nik202/32/16098_2.png) [@nik202](https://forum.rasa.com/u/nik202)
#### Post date: [January 10, 2022, 6:26pm UTC](https://forum.rasa.com/t/diffs-between-git-and-nlu-data-displayed-and-used-by-rasa-x/50472/2 "2022-01-10T18:26:59Z")

</div>

@spf If you have pushed the data in Git repo and your repo is connected with Rasa X, then the only known the issue is domain.yml in that intents and slots synchronized according to amending order of the alphabets or even add some default syntax. On the other hand, if you trained the model based on your git repo and if you have updated something, you will see that it will give you notification for update the git server, so you need to update the same and on git repo, you need to merge that branch as it will not push on the main thread.

@spf If your issue persists, I’d recommend disconnecting the Git repo with rasa x and then generate the new deploy key and connecting again with rasa x and train.

@spf even you can delete the cache or cookies [I’m not it will be helpful or not]

Please keep me in loop as you troubleshoot. Good Luck!

---

<div class="post-metadata">

### Author: ![spf](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/spf/32/18610_2.png) [@spf](https://forum.rasa.com/u/spf)
#### Post date: [January 11, 2022, 9:35am UTC](https://forum.rasa.com/t/diffs-between-git-and-nlu-data-displayed-and-used-by-rasa-x/50472/3 "2022-01-11T09:35:14Z")

</div>

@nik202 thanks for the quick response … but unfortunately this does not solve the problem … I reconnected the git repo (no problems, the git files are synced exactly as in the repo) … BUT … rasa-x tries and fails to validate a corrupt story file that is not part of the repo … afterwards it seems like rasa-x stops reading any of the files of the repo … this corrupt file (or information) must be located somewhere, may be in the database?

I have a log trace that shows the issue:

[2022-01-11 09:25:03 +0000] - (sanic.access)[INFO][REDACTED]: GET [http://REDACTED/api/git-repositories/3/status](http://REDACTED/api/git-repositories/3/status) 200 240  
rasa-x\_1 | ERROR:rasax.community.utils.common:Could not complete the coroutine: ‘’.  
rasa-x\_1 | Traceback (most recent call last):  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasa/shared/utils/validation.py”, line 170, in validate\_yaml\_schema  
rasa-x\_1 | c.validate(raise\_exception=True)  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/pykwalify/core.py”, line 194, in validate  
rasa-x\_1 | raise SchemaError(u"Schema validation failed:\n - {error\_msg}.".format(  
rasa-x\_1 | pykwalify.errors.SchemaError: \<SchemaError: error code 2: Schema validation failed:  
rasa-x\_1 | - Value '[ordereddict([(‘intent’, ‘REDACTED’)]), ordereddict([(‘action’, ‘REDACTED’)]), … ’ is not of type ‘str’. Path: ‘/stories/22/story’.: Path: ‘/’\>  
rasa-x\_1 |  
rasa-x\_1 | During handling of the above exception, another exception occurred:  
rasa-x\_1 |  
rasa-x\_1 | Traceback (most recent call last):  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/story\_service.py”, line 135, in \_reader\_read\_from\_string  
rasa-x\_1 | return reader.read\_from\_file(temp\_path, skip\_validation=skip\_validation)  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasa/shared/core/training\_data/story\_reader/yaml\_story\_reader.py”, line 107, in read\_from\_file  
rasa-x\_1 | raise e  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasa/shared/core/training\_data/story\_reader/yaml\_story\_reader.py”, line 99, in read\_from\_file  
rasa-x\_1 | return self.read\_from\_string(  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasa/shared/core/training\_data/story\_reader/yaml\_story\_reader.py”, line 123, in read\_from\_string  
rasa-x\_1 | rasa.shared.utils.validation.validate\_yaml\_schema(string, CORE\_SCHEMA\_FILE)  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasa/shared/utils/validation.py”, line 172, in validate\_yaml\_schema  
rasa-x\_1 | raise YamlValidationException(  
rasa-x\_1 | rasa.shared.utils.validation.YamlValidationException: Failed to validate ‘/tmp/tmppaj69plq’. Please make sure the file is correct and all mandatory parameters are specified. Here are the errors found during validation:  
rasa-x\_1 | in /tmp/tmppaj69plq:343:  
rasa-x\_1 | Value '[ordereddict([(‘intent’, ‘REDACTED’)]), ordereddict([(‘action’, ‘REDACTED’)]), … ’ is not of type ‘str’. Path: ‘/stories/22/story’  
rasa-x\_1 |  
rasa-x\_1 | During handling of the above exception, another exception occurred:  
rasa-x\_1 |  
rasa-x\_1 | Traceback (most recent call last):  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/story\_service.py”, line 217, in get\_story\_steps  
rasa-x\_1 | return StoryService.\_reader\_read\_from\_string(  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/story\_service.py”, line 137, in \_reader\_read\_from\_string  
rasa-x\_1 | raise StoryParseError(str(e))  
rasa-x\_1 | rasa.shared.core.training\_data.story\_reader.story\_reader.StoryParseError  
rasa-x\_1 |  
rasa-x\_1 | During handling of the above exception, another exception occurred:  
rasa-x\_1 |  
rasa-x\_1 | Traceback (most recent call last):  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/utils/common.py”, line 886, in run\_in\_loop  
rasa-x\_1 | return loop.run\_until\_complete(coro)  
rasa-x\_1 | File “uvloop/loop.pyx”, line 1456, in uvloop.loop.Loop.run\_until\_complete  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/integrated\_version\_control/git\_service.py”, line 1203, in synchronize\_project  
rasa-x\_1 | return await self.\_force\_inject\_latest\_remote\_changes()  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/integrated\_version\_control/git\_service.py”, line 1261, in \_force\_inject\_latest\_remote\_changes  
rasa-x\_1 | await self.\_inject\_data()  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/integrated\_version\_control/git\_service.py”, line 1233, in \_inject\_data  
rasa-x\_1 | await rasax.initialise.inject\_files\_from\_disk(  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/initialise.py”, line 454, in inject\_files\_from\_disk  
rasa-x\_1 | await inject\_stories(  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/initialise.py”, line 277, in inject\_stories  
rasa-x\_1 | test\_story\_blocks = await story\_service.save\_stories\_from\_files(  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/story\_service.py”, line 559, in save\_stories\_from\_files  
rasa-x\_1 | additional\_blocks = await self.save\_stories(  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/story\_service.py”, line 452, in save\_stories  
rasa-x\_1 | processed\_stories = await self.\_extract\_stories\_yaml(  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/story\_service.py”, line 375, in \_extract\_stories\_yaml  
rasa-x\_1 | steps\_list = self.get\_story\_steps(  
rasa-x\_1 | File “/usr/local/lib/python3.8/dist-packages/rasax/community/services/story\_service.py”, line 221, in get\_story\_steps  
rasa-x\_1 | raise StoryParseError(  
rasa-x\_1 | rasa.shared.core.training\_data.story\_reader.story\_reader.StoryParseError

---

<div class="post-metadata">

### Author: ![spf](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/spf/32/18610_2.png) [@spf](https://forum.rasa.com/u/spf)
#### Post date: [January 12, 2022, 8:03am UTC](https://forum.rasa.com/t/diffs-between-git-and-nlu-data-displayed-and-used-by-rasa-x/50472/4 "2022-01-12T08:03:51Z")

</div>

@nik202 Sorry for the unformatted log … I fixed this 😃

I’ve tried to find the corrupt story file (path: ‘/stories/22/story) without success

I’ve tried the following

- recreate all pods: the error persists
- search the rasa-x docker pod for a file: there isn’t
- search the “story” table in the database: it’s not there either
- deleted all story files from the “story” table in the database: the table got correctly refilled with the stories from the connected git
- searched through other db tables that seemed relevant: nothing found

I’m really running out of options here

I could setup the whole thing from scratch, but I don’t want to loose my conversations 😕

Any Ideas

---

<div class="post-metadata">

### Author: ![spf](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.rasa.com/spf/32/18610_2.png) [@spf](https://forum.rasa.com/u/spf)
#### Post date: [January 12, 2022, 10:28am UTC](https://forum.rasa.com/t/diffs-between-git-and-nlu-data-displayed-and-used-by-rasa-x/50472/5 "2022-01-12T10:28:14Z")

</div>

Whoa … found it

It was a test story! which rasa-x tried to interpret as a training story.

my git repo structure looks like it should:

- data
  - nly.yml
  - …
  - stories.yml

- tests
  - test\_stories.yml

Hope someone from rasa is listening, and the bug gets fixed
