This is most easily reproduced by running PhpBackendUnitTest, which fails on Windows resulting in a error similar to:

rename(sites/simpletest/454911/files/php/cache_page/.2182f2ee82,sites/simpletest/454911/files/php/cache_page/4DdMbToh62rmlatZJ9JZhKIsaANqRJmDb53GpRYrTfI/77b96f84dee112a2bc5cbb6c09722bee07bde3bd8bc78675274980ca21cf3378.php): Access is denied. (code: 5)

This is because rename() on Windows incorrectly uses the target file permissions rather than the containing directory permissions. See this PHP bug report.

CommentFileSizeAuthor
#14 2629240--local_history.patch1.55 KBrichard.lampitt
#2 2629240-1.patch1.72 KBmikeker
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

mikeker created an issue. See original summary.

mikeker’s picture

mikeker CreditAttribution: mikeker as a volunteer commented
Status: Active » Needs review
FileSize
2629240-1.patch1.72 KB
xjm’s picture

xjm
she/her
Primary language English
CreditAttribution: xjm at Acquia commented
Issue tags: -rc target triage

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
richard.lampitt’s picture

richard.lampitt CreditAttribution: richard.lampitt at SIRUSS commented
FileSize
2629240--local_history.patch1.55 KB

Updated the patch in #2 to work with Drupal 9.3

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave CreditAttribution: smustgrave at Mobomo commented
Status: Needs review » Needs work
Issue tags: +Needs Review Queue Initiative, +Needs tests

This issue is being reviewed by the kind folks in Slack, #needs-review-queue-initiative. We are working to keep the size of Needs Review queue [2700+ issues] to around 400 (1 month or less), following Review a patch or merge request as a guide.

This will need a test case to show the issue. Would recommend the #testing channel on slack for how to write a windows only test.

crutch’s picture

crutch CreditAttribution: crutch commented

Experiencing this now on local windows dev machine using XAMPP v3.3.0, D9.5.5, PHP 8.1. #14 isn't applying.

Scenario
When trying to generate video thumbnails using core media, I ran into an issue with the file system. After adding/using the video field "media_oembed_video" and saving, I edited the media item and changed the suggested file path which was public://oembed_thumbnails or public://oembed_thumbnails/videos to use a custom location. I then deleted the files and folders from the suggested locations above and in the styles directory expecting auto-regeneration of the folders and files. Now getting error...

Warning: rename(sites/default/files/php/twig/.r3Zx1jkE6kBEezw2NmPNEuratkI,sites/default/files/php/twig/641488bb00721_status-messages--alerts.h_kDfXO1DP-OaUrNTKHNGCTb_0Q/TcuRT0AQzFp7awBIpnkgIIYABxTnucXuVfQO6jOzM7I.php): Access is denied (code: 5) in Drupal\Component\PhpStorage\MTimeProtectedFastFileStorage->save() (line 88 of C:\xampp\htdocs\web\core\lib\Drupal\Component\PhpStorage\MTimeProtectedFastFileStorage.php)

references: https://www.drupal.org/project/drupal/issues/2700019, https://www.drupal.org/project/drupal/issues/2606772, https://www.drupal.org/project/drupal/issues/3214257#comment-14978745

Grabby’s picture

Grabby CreditAttribution: Grabby as a volunteer commented

I’m running D9.5.10 (PHP 8.1.21) with Laragon on a Windows box and tried #14, but I’m still getting

Warning: rename(tmp//twig/.4zqGXfPLZK7G4mnjw2abMtYMKkU,tmp//twig/64d68a2a2a255___string_template__1e7a22_5NnBESfxNIwNCEGCXhF2pxNyN/hXVFktFf4R1YIAvzgQqXtx4ksD18LS7FG6vvGU5r9og.php): Access is denied (code: 5) in Drupal\Component\PhpStorage\MTimeProtectedFastFileStorage->save() (line 105 of mysite\web\core\lib\Drupal\Component\PhpStorage\MTimeProtectedFastFileStorage.php)

In my case it’s triggered by adding or configuring blocks in layout builder.

Version: 9.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.