[Bug]: activity chart may show incorrect date depending on browser timezone

[xmcp]

What happened?

If the browser timezone is a positive value, the date shown in the activity charts will be off by one:

This bug is due to the standardizeDate function:

...
const fullDate = new Date(year, monthIndex, parseInt(day));
return fullDate.toISOString().split('T')[0];

Since new Date constructs the Date object in local timezone and toISOString converts it to GMT+0, it will become the previous day if the browser timezone is >0. We should use Date.UTC instead.

Other calls to toISOString may have the same problem, but I didn't check them individually.

Relevant log output

N/A

Are you a ML Ops Team?

Yes

What LiteLLM version are you on ?

v1.60.2

Twitter / LinkedIn details

No response

[quocnguyendinh-ct]

I also the same this issue