From issues-return-54503-archive-asf-public=cust-asf.ponee.io@geode.apache.org Fri Oct 18 22:20:02 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id B485F1804BB for ; Sat, 19 Oct 2019 00:20:01 +0200 (CEST) Received: (qmail 95521 invoked by uid 500); 18 Oct 2019 22:20:01 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 95499 invoked by uid 99); 18 Oct 2019 22:20:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Oct 2019 22:20:01 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 83BC3E0EAA for ; Fri, 18 Oct 2019 22:20:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 0376F7801F8 for ; Fri, 18 Oct 2019 22:20:00 +0000 (UTC) Date: Fri, 18 Oct 2019 22:20:00 +0000 (UTC) From: "Blake Bender (Jira)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (GEODE-7324) FIx invalid encoding in log files MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Blake Bender created GEODE-7324: ----------------------------------- Summary: FIx invalid encoding in log files Key: GEODE-7324 URL: https://issues.apache.org/jira/browse/GEODE-7324 Project: Geode Issue Type: Bug Components: native client Reporter: Blake Bender As a developer, I wish to be able to write log parsing utilities for the na= tive client if need be.=C2=A0 To do this, I need to be able to read the tex= t in the log files via standard languages like Python, C#, etc.=C2=A0 Unfor= tunately, recent changes to some log statements in the native client code w= ill cause invalid utf-8 bytes to be written to the log in some circumstance= s, making reading the log very difficult. =C2=A0 repro steps: i. Enable debug-level logging in NC integration tests, and set log-file to = a known filename ii. Run a test case, to generate the log file iii.=C2=A0 Attempt to parse the file as utf-8 in Python =C2=A0 Expected result: * File parses correctly Actual result: * Python throws an exception, saying it has encountered an invalid start b= yte =C2=A0 This is known to happen when using the '%zu' format specifier to log a valu= e of type std::chrono::Rep on MacOS.=C2=A0 Other compilers/OSes/types may o= r may not display this behavior. =C2=A0 -- This message was sent by Atlassian Jira (v8.3.4#803005)