You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Blake Bender (Jira)" <ji...@apache.org> on 2021/08/12 19:09:00 UTC

[jira] [Closed] (GEODE-9487) Timezone is potentially invalid string in log files for non-English locales

     [ https://issues.apache.org/jira/browse/GEODE-9487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Blake Bender closed GEODE-9487.
-------------------------------

> Timezone is potentially invalid string in log files for non-English locales 
> ----------------------------------------------------------------------------
>
>                 Key: GEODE-9487
>                 URL: https://issues.apache.org/jira/browse/GEODE-9487
>             Project: Geode
>          Issue Type: Improvement
>          Components: native client
>            Reporter: Blake Bender
>            Assignee: Blake Bender
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.15.0
>
>
> The native client logger was rewritten several months ago to use, among other things, `std::put_time` when formatting log strings, specifically using the "%Z" formatting for timezone.  The documentation for this formatting says "writes locale-dependent time zone name or abbreviation, or no characters if the time zone information is not available," and indeed it does.  We just received a log file from a customer machine in APJ region, i.e. locale is set to something like Traditional Chinese.  These strings are dumped into the log file as is, in some unknown MBCS encoding, and contain invalid utf-8 start codes, throwing off our Python-based parsing tool.
> We should probably just drop time zone from our logs, or normalize everything somehow.  In any case, we need to write valid utf-8, just to play well with others.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)