You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Python: DevUI - Tool call timestamps are being overwritten #1483
I've just upgraded to latest version, 1.0.0b251016, and I still see issues with times.
Observation:
User and assistant message timestamps update dynamically over time instead of remaining fixed.
All items in the Events column share the same timestamp.
Refreshing the browser doesn’t fix the issue.
First message (look at all the times in this screenshot):
About to send a new message (obviously times seen under user and assitant messages are being updated according to system time):
Just send the second message:
And all the items in events column shows same time:
I tried refreshing the browser but the weird behaviour with times is still there:
Note:
This is minor from a usability perspective but indicates a likely bug or bad practice in how timestamps are handled, either during event transformation or, most probably, in the UI rendering layer.
Could you verify that message and event timestamps in DevUI are bound to immutable per-item timestamps from the payload, rather than recomputed or shared across renders?
Activity
fix(devui): resolve timestamp overwriting and Content serialization e…
Python: DevUI Fix Serialization, Timestamp and Other Issues (#1584)
juangcarmona commentedon Oct 24, 2025
Hi, Victor Dibia (@victordibia) and Mark Wallace (@markwallace-microsoft) I'd say this oissue should be reopened (unless the fix didn't reach pypip.org).
I've just upgraded to latest version, 1.0.0b251016, and I still see issues with times.
Observation:
First message (look at all the times in this screenshot):

About to send a new message (obviously times seen under user and assitant messages are being updated according to system time):

Just send the second message:

And all the items in events column shows same time:

I tried refreshing the browser but the weird behaviour with times is still there:

Note:
This is minor from a usability perspective but indicates a likely bug or bad practice in how timestamps are handled, either during event transformation or, most probably, in the UI rendering layer.
Could you verify that message and event timestamps in DevUI are bound to immutable per-item timestamps from the payload, rather than recomputed or shared across renders?
Thanks in advance!
Python: DevUI Fix Serialization, Timestamp and Other Issues (microsof…
Python: DevUI Fix Serialization, Timestamp and Other Issues (microsof…