!!!! bug: Last messages in past conversations do not appear
@VictoriaDemierbe reports that in all the conversations (conv id= 19 + 20 +22 + 34 +42), when she or Tyler opens them later on to view the logged convo, the last few messages do not appear (e.g., in id=19 after 10:54, in id=20 after 10:50, in id=42 after 10:54, etc.).
- Something seems to be happening around the 50-55 minute mark, or maybe after a certain number of messages have been sent?
- Are the next messages correctly logged (in the DB)?
- Reason for them not appearing in the interface?
Activité
changed milestone to %0.3: Improved User Experience
added Bug label
assigned to @bridubois
During our last session, @VictoriaDemierbe left the conversation to update her availability in the planner. When she returned to the conversation, she could not see any of the messages which had been sent after 10:54. As I had not left the chat window, I could still see all the messages. (In other words, they didn't suddenly disappear for me.)
mentioned in issue #112 (closed)
After completing the other reports, I wanted to see if messages disappeared from our conversation. I went to the dashboard and tried to open both chat sessions that had been started, but I saw the following:
I received the same error when I tried to refresh a tab that was already open with the conversation.I went back to look at the chat sessions from yesterday, and I observe two things:
1. Victoria had 'sent' the 'Bonne semaine' message four times, all of which had the timestamp 11:02. However, when I go back to the chat now, I can see only three of them. I don't know why it decided to cut off the transcript at this point.2. Until now, the transcripts have been cut off usually somewhere between the 10:50 and 10:55 mark. This time, the transcript cuts off at 11:02, which is the latest we've had saved messages thus far. The conversation started at the same time as always (10:00 Belgium time).
To recap:
Session ID Date Conversation started Last saved message Duration recorded Message count
(count in Word)
19 22/8 11:59 12:54 55 min 99 (101) 20 29/8 11:59 12:50 51 min 100 (100) 22 2/9 11:59 12:52 53 min 96 (104) 34 12/9 11:59 12:53 54 min 98 (102) 39 19/9 12:00 12:55 55 min 89 (110) 42 23/9 9:59 10:54 55 min 97 (103) 45 30/9 10:00 11:02 62 min 95 (105) For the message count: I counted the messages in each chat manually. Then I copied and pasted the whole transcript into Word and searched for the date component of the timestamp. The number of hits is indicated (in brackets). The discrepancy between the counts seems to be related to edited messages: when I copy and paste an edited message into Word, it also shows the edit history of the message (and each edit also has a timestamp).
Another thing I notice is that the timestamps on the conversations in August and September are not accurate: each of our sessions has started at 10:00 Belgian time. The saved records have shifted to two hours later for some reason.
closed with commit 98ea217a
The timestamp shift for August and September is normal. To allow sessions to works anywhere in the world, the sessions now use the UTC time rather than the Belgian one (UTC+2) as reference, so the previous sessions have been shifted by two hours, but it shouldn't happens on new sessions.
The main error should be fixed now: the issue was that the server returned a maximum of 100 messages at once. And indeed, the average of the manual and word count was always 100 in your examples. (99 & 101, 95 & 105, ...)
Modifié par Brieuc Duboismentioned in commit 98ea217a
