[FIX] Timestamps on chat response are the same as the timestamp of the preceeding query about khoj HOT 4 CLOSED

from khoj.

Thanks for opening an issue on this, Nick! This is because we're storing the datetime of the message in UTC in the backend. We'll need to parse the DT in the client's time zone when rendering..

from khoj.

Really, it's related to timezone?

The timestamp of the original query gets changed to the timestamp of the final response. You can see it was 16:10 in the first screenshot then in the last screenshot you can see that it had changed to match the timestamp of the last response (21:19).

I guess that huge jump can be accounted for by a timezone different, but the timestamp displayed for my query shouldn't change.

Here it is highlighted:

from khoj.

The difference is due to the way in which the message is rendering. When it's first rendered in the UI, it's using new Date(), which will automatically use the local time zone. When you refresh it and come back to the chat session, it's loading it from the database and using new Date(chat_log.created), which is going to be in the timezone for UTC.

The timestamp being correct the first time is kind of like an illusion, you could say. We just need to let the JS function now that the timestamp of that created field is UTC and it should correct the rendering. This would be the same issue in both desktop/chat.html and the web chat.html.

Will get this fixed in the next release! Thanks for reporting.

from khoj.