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
fn write_timestamp(
f: &mut dyn Write,
naive: NaiveDateTime,
timezone: Option<Tz>,
format: Option<&str>,
) -> FormatResult {
match timezone {
Some(tz) => {
let date = Utc.from_utc_datetime(&naive).with_timezone(&tz);
match format {
Some(s) => write!(f, "{}", date.format(s))?,
None => write!(f, "{}", date.to_rfc3339_opts(SecondsFormat::AutoSi, true))?,
}
}
None => match format {
Some(s) => write!(f, "{}", naive.format(s))?,
None => write!(f, "{naive:?}")?,
},
}
Ok(())
}
Heres the underlying function. I believe format will be none, so it would use the rfc3339 if it has a timezone, or otherwise it uses the default Debug impl for NaiveDateTime, which goes like 2015-06-30T23:59:60.500
The problem here is that the timestamp data itself is non timezoned. I will see if this is easily fixable
Given that the timestamps are in UTC format, I anticipate a trailing
Z
:FYI, there was a similar issue in
arrow-json
apache/arrow-rs#3449 but it has been resolved for some time now.The text was updated successfully, but these errors were encountered: