-
-
Notifications
You must be signed in to change notification settings - Fork 123
Fix Timestamp issue in chat interface #14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
That's great, @Aastha-1411 you've done a great job❕But:
|
I have pulled the latest changes and linked my PR to the issue. You can now merge my PR. |
![]() Now the changes are there, you can check the link too : https://talkheal-kfiantnh6xkhtd3tzbg5bd.streamlit.app/ Thanks for your time and patience.
![]() Now you can see the delete option. The deployed link is here: https://talkheal-kfiantnh6xkhtd3tzbg5bd.streamlit.app/ Thanks for your time and patience. |
@Aastha-1411 Happy that the issue is successfully resolved, great job, thanks❕ |
Closes: #7
This PR addresses the issue with incorrect timestamp display by ensuring the time shown is based on the user's local time, not the server’s. The app now correctly renders local timestamps both locally and after deployment.
Changes Made:
Replaced the old timestamp logic with one that considers the user's local timezone using st.context.timezone_offset. This ensures that the time displayed is accurate for the end-user, not just the server's timezone (e.g., UTC on Streamlit Cloud).
I verified the change by deploying the project myself on community cloud to check if .
it is making chnages as per the given time. You can see the image below.
I was chatting with the bot on 7:04 PM only. So its working fine.