-
Notifications
You must be signed in to change notification settings - Fork 4
Loading Smarti fails for empty conversations #258
Comments
@ruKurz Could you please provide some steps to reproduce it? |
@Peym4n In updated the description of this issue. Does that fir fore you? |
I'm not able to reproduce the Smarti error by creating a new empty request. |
@Peym4n what does happen if you're creating a new topic? |
After creating a topic (request) with no initial message, I just get the widget notification that is shown above, but no errors in Smarti. |
I'll recheck with an empty MongoDB, just to assure that it's no "works not on my machine" problem. And come back soon. Just a remark: A |
Yes, I tried creating a new topic as well. And the result was the same. I get the widget notification but no Smarti error. btw, in the
But a topic cannot have an initial message, just a request can. That's why I thought you are talking about creating a new request with no initial message. |
I'm using our |
Right!
The error seems to occure each time an analysis for an empty conversation is returned from the Smarti server to the widget.
Since I get the error without deleting a RC message or calling DELETE on Smarti API I do not see a relation between this issue and the deletion. Before creating a new issue, I want to validate that this error is not caused by an empty conversation/analysis result. Background Until now we did not create a conversation when a new topic has been created. Smarti: 16fc08d Assistify.Chat: assistify/Rocket.Chat@43fe233 @Peym4n could you please use these versions for testing? |
I will fix the reported Exception by not performing an actual query if the context is an empty text but rather assume an empty result - resulting in an empty |
* now `""` is returned in case of an empty context. As this will be used as `q.alt` the fallback query will not return any results * An empty context query is now also returned in case a SolrException is thrown while building the context query.
@ruKurz my change only fixed the After checking with the MongoDB the Server-side code and the Rocket.Chat integration the behaviour originates from the fact that: The Rocket.Chat integration only creates a Smarti Conversation when a Message is sent for a Channel. Channel create/delete events are not processed. Because of this Smarti shows the Information that this room is not available in the knowledge base. To fully solve this we would need to adapt the integration to also react on Channel level events |
I started RC and Smarti using the commits that you provided. |
@ruKurz ok. I will change the widget notification to info, when no conversation is found. |
@Peym4n I installed the Smarti develop and Rocket.Chat https://github.com/assistify/Rocket.Chat/tree/fix/smarti-results-not-loaded on the test server and was able to verify that no Smarti Conversation is created when a new Channel is created in Rocket.Chat. Only when the first Message is sent to the Channel the Conversation + Message are created with Smarti. This is the reason for the Error message as shown in this Issue |
@ruKurz We found out that when And can this issue be in review now? or are any more changes from our side needed? |
So from my point of view we can move this issue into review. |
@Peym4n I tested the info message. It's now in another color. But the info text is semantically not correct. It says: "Dieser Raum ist im Wissensbasis nicht verfügbar." A semantically correct message would be: "Starte die Unterhaltung, damit Vorschläge aus der Wissensbasis vorgeschlagen werden." BTW: The sentence "Dieser Raum ist im Wissensbasis nicht verfügbar." is grammatically incorrect. |
Hi Rüdiger With the following environment:
and the following process:
results for me in the state as shown in the following screenshot I do not see any message that the channel is not available in the knowledge base. In my opinion this is the expected behaviour. Unrelated to this we should fix the info message to be grammatically correct |
On our IAT we did not yet install https://github.com/assistify/Rocket.Chat.git/fix/smarti-results-not-loaded. So we will retest hopefully this day. |
Regarding the "info". We must handle several cases:
I would like to see this improvement within the current release. |
@ruKurz I'm working on it. But could you please create a new issue for that? Just to keep things separated. |
Loading the Smarti Widget fails when the conversation is empty:
Expected behavior
If a new "topic", "help-request", "thread" is started in Assistify.Chat that does not have any messages in it yet. The smarti widget should inform the user that the "Knowledge Base" is working, but that there are no messages within the room, that can be analyzed.
Actual behavior
The Smarti Widget show an error message that is misleading. It suggests that there is some problem with the knowledge base, but actually everything went well and there are just being no results to be displayed yet.
![smarti not loaded](https://user-images.githubusercontent.com/853776/41296515-60bdb012-6e5d-11e8-8a3a-f830021db4d1.png)
Steps to reproduce
Cause assumption
When creating a new topic there is printed out an error into the Smarti server log. It seems as there is a valid analysis coming back, but instead of checking if the client gets an valid Solr query, the client purely tries to execute a similarity search without any "q" or "q.alt" parameters present.
The text was updated successfully, but these errors were encountered: