Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:118893 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 71694 invoked from network); 28 Oct 2022 09:28:54 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 28 Oct 2022 09:28:54 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5D03B180054 for ; Fri, 28 Oct 2022 02:28:53 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.6 required=5.0 tests=BAYES_20,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-ej1-f51.google.com (mail-ej1-f51.google.com [209.85.218.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 28 Oct 2022 02:28:52 -0700 (PDT) Received: by mail-ej1-f51.google.com with SMTP id q9so11698012ejd.0 for ; Fri, 28 Oct 2022 02:28:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=team.bumble.com; s=google; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=rPdyj3/zWo4vEoSjF9SPzMFi9LATi3Myj1zFnxPxfsw=; b=2Pm3Olh30XBUk8u+HypLxdG3HVQ/5ejPLkSHZqyFaHYSvG8Cive8bQSbaXQh49SEtG GRFQNNS3DVuaagG6y2qowWlSR4bpjdQoplRDY+sDylxSUwMasdHK0/xLBh4Kp4/ENU/9 8qNaoTnQy6+169laGc9tOgo6qcqopmUYX1Gbo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=rPdyj3/zWo4vEoSjF9SPzMFi9LATi3Myj1zFnxPxfsw=; b=DGtLyVl0ARyb0GVoGqyfFQaZv92sX4BEq9YDLWNs03ivTMglq7I4w+wwHvQTgti4+P hbXYu0UeuF7xMIt8rYrUR9KrcpzmS4xcda+WLuUoVxsHIxyto8dK7jsdKSWMaD6PWi/+ pA+hrU7k9XxyhOUXWyqGeh41mlMQ+T8UMi2fBBL6bwLXFX47DCFujqr4FnB3Ljm7Prls Gde2ajmBcWA0oiyu1Wd38g6alz6OKDzkAvCPl2DcZvCY+HeO9NzvUxrMCMxP4E3llcm4 dC6ck4wYaSTULp0DqMDWhqBIAvgYP9axRBca8sM7g+15n7fLkyBseZ18Lm4dfhysNFoQ Rfxg== X-Gm-Message-State: ACrzQf0fKyq3+ZNnA9AI9BWPeS66NjviVZAY6sX6uJox+U+tPblJHF+U QOWsMPnMiPGQlkEMUHSy1pG4+cuBTNZvqDHSKd7VqouNpkTzPQ== X-Google-Smtp-Source: AMsMyM6KFXEPJ6dr5dBGyIoLot5G7SLQYtJnfGFcbYesgHCg4EpY/SUbCbgIFVutUlNDxJLdCDLgtkfGrJ1EVMkLA4M= X-Received: by 2002:a17:907:74e:b0:74f:83d4:cf58 with SMTP id xc14-20020a170907074e00b0074f83d4cf58mr46885392ejb.178.1666949320748; Fri, 28 Oct 2022 02:28:40 -0700 (PDT) MIME-Version: 1.0 References: <42A5DAC6-253E-478D-808C-36690FA88315@gmail.com> In-Reply-To: <42A5DAC6-253E-478D-808C-36690FA88315@gmail.com> Reply-To: Mikhail Galanin Date: Fri, 28 Oct 2022 10:28:04 +0100 Message-ID: To: Rowan Tommins Cc: internals@lists.php.net Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] Microseconds to error log From: internals@lists.php.net ("Mikhail Galanin via internals") Hello everyone, I tried following Derrek's approach (to introduce a new function). A couple of considerations: We used to have some pain when this format changed last time (I can't remember details, unfortunately) but I don't feel like making an option to provide backward compatibility is a good idea. Early or lately, we will need to drop this compatibility and the users face absolutely the same issue. I hear people don't want to have this format configurable -- I tend to agree that it's a bit overcomplication. I'm not sure if I'm ready to switch to ISO8601 but if we have a consensus here, I'm open to updating the patch. Basically, I'm open to everything, please share your opinions. Pull-request: https://github.com/php/php-src/pull/9844 On Fri, Oct 21, 2022 at 11:46 AM Rowan Tommins wr= ote: > > On 21 October 2022 08:47:30 BST, Mikhail Galanin via internals wrote: > >Basically, we have quite a high-loaded environment and we really want > >to see timestamps containing milli-/microseconds in our logs. > > > I'm not knowledgeable enough to comment on the implementation details, bu= t from a user point of view I agree the feature would be useful. It would d= efinitely need to be behind an ini setting, though, to avoid existing log p= arsers failing unexpectedly on the new format. > > Regards, > Hi Mikhail, > > -- > Rowan Tommins > [IMSoP] > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: https://www.php.net/unsub.php >