Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113130 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 75614 invoked from network); 10 Feb 2021 13:50:55 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 10 Feb 2021 13:50:55 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 1F9171804DC for ; Wed, 10 Feb 2021 05:36:09 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.2 required=5.0 tests=BAYES_40,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM, HTML_FONT_LOW_CONTRAST,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-ot1-f46.google.com (mail-ot1-f46.google.com [209.85.210.46]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 10 Feb 2021 05:36:08 -0800 (PST) Received: by mail-ot1-f46.google.com with SMTP id e4so1768132ote.5 for ; Wed, 10 Feb 2021 05:36:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=grwF1opTYPpauZMYA8pMwu4blo3brkTW9bOe22cjEJY=; b=o0raqYYgcw83QGLda6/kQskJic6cy8TVFCoqb2PdzidzrS3TfN48ZrnAduY+rALiCR eYD/ljpbBAEP5sQ1sT9vyP8z3eEY1zrOKCeRjfp2ypQpqTKAfU6BmnZGJIHUsIzURIui R0GYTG8st6xQZMDAAiKIiKN0AdZ+RplE22Y4TX7EVH6/2QRK21YKUvEG2uBBSf5wbWjY FhgVECEAUPT+HAOgwWAWWmzt1l4W+9qVvV871pqJo9zGGeeanKp8AnMavNkFp1Qsg29t jD2J/0B8hfKZYIcKtaf6L89tdrWTGTAmEpt5F7+eXqTbCm/nVm4ioHTH8CO7KMU0kpTN p/7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=grwF1opTYPpauZMYA8pMwu4blo3brkTW9bOe22cjEJY=; b=Zt8t1TjBjiH2a7zDdkB803lKf/WVmy3q/t/ksqPElYVK56/72KfzfL6trk/E/Q/X5a 3oiPQ36R7XqOx56ByyE6C9DFKWlgoQWkiv8Xm+sDwtg+tqFGvVWqkbdGBNN2coCBflBN jWW928IufByZEutb216AJP0IzcUrvS2xSx5Uqp+veKt/8j3Bi0hEpcEu2Y/vLSnipm+e 7lhfUQLlj7sM/7ziXo0CguedQ8gIylEw+HXsRCsYjxiRHVxP6CpdWyxeD5+ZIEzxgqqo 2npjNVNUJ25nw7stoS+Ago6H178cgaetHYX4XCJac6ndg0E4gR+F5VNqwZ8FY414ruk3 uyFQ== X-Gm-Message-State: AOAM530QyMnPRTQ1mdyevM1xGBd9/Ccb8ipnL0kAEQmZqN5Ztndzu6Ss /B2txDr7gBEFkDYMd56dzzDYmS16QyWkY3siVAPX66+iFgM= X-Google-Smtp-Source: ABdhPJyGqsWUXe90WsSNDumN7oVoQtFkIVAzrjMTegaxb9YkYG+p3t6Vz5B1TyfVrJzCpucpdqAmMOaE4Lwus7p8V2s= X-Received: by 2002:a9d:6f93:: with SMTP id h19mr2083274otq.236.1612964167577; Wed, 10 Feb 2021 05:36:07 -0800 (PST) MIME-Version: 1.0 Date: Wed, 10 Feb 2021 13:35:56 +0000 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="0000000000003e758305bafb7c7c" Subject: Re: [PHP-DEV] [RFC] fsync function From: davidgebler@gmail.com (David Gebler) --0000000000003e758305bafb7c7c Content-Type: text/plain; charset="UTF-8" Hi all, Giving this one a little bump as I haven't had any particular feedback or comments about it so far. I know it's not the biggest or most exciting change in the world but it's implemented and I'd like to progress it to a vote in another week or so if there are no objections or clarifications? To summarise: - Adds fsync() and fdatasync() for plain file streams on Unix systems. - Adds fsync() on Windows with fdatasync() as an alias. Thank you. RFC ref: https://wiki.php.net/rfc/fsync_function PR ref: https://github.com/php/php-src/pull/6650 -Dave On Wed, Feb 3, 2021 at 5:46 PM David Gebler wrote: > RFC ref: https://wiki.php.net/rfc/fsync_function > PR ref: https://github.com/php/php-src/pull/6650 > > I think this one is pretty much good now and passing builds; when I first > proposed adding fsync some time ago, there was a suggestion from a couple > contributors that an RFC might be overkill/unnecessary for this feature > (and I'd certainly be happy for it to just be accepted as a pull request) > but want to make sure everyone has had a good chance to look over the RFC > and implementation and specifically whether anyone has any significant > concerns or objections? > > Thanks. > > Dave > > On Mon, Feb 1, 2021 at 5:35 PM David Gebler wrote: > >> Hi internals, >> I have updated the GitHub PR and wiki RFC to also include an >> implementation of fdatasync. >> >> On another note, I note my PR builds are failing on MACOS_DEBUG_NTS with >> a test in ext/zend_test/tests/observer_error_05.phpt- this does not >> appear to be related to my changes and I'm wondering if anyone can shed >> any light on this? I'm seeing it on some other open PRs too so I'm guessing >> it's a known issue? Cheers. >> >> David Gebler >> davidgebler@gmail.com >> >> >> On Sat, Jan 30, 2021 at 6:34 PM David Gebler >> wrote: >> >>> Updated the PR https://github.com/php/php-src/pull/6650 following >>> comment from Nikita, added basic tests, would appreciate further review >>> from contributors, have updated the RFC >>> https://wiki.php.net/rfc/fsync_function to under discussion, cheers. >>> >>> David Gebler >>> davidgebler@gmail.com >>> >>> >>> On Sat, Jan 30, 2021 at 1:58 AM David Gebler >>> wrote: >>> >>>> Hi internals, >>>> Some time back I asked for commentary on a proposal to add fsync() to >>>> PHP, I have now submitted a draft RFC >>>> https://wiki.php.net/rfc/fsync_function alongside an in-progress proof >>>> of concept PR (current status: can compile locally and run but the branch >>>> needs more work to bring it up to standard, as well as tests and >>>> documentation) which I would like to open up for review and discussion. >>>> >>>> Thanks. >>>> >>>> David Gebler >>>> davidgebler@gmail.com >>>> >>>> --0000000000003e758305bafb7c7c--